Methods, systems and related devices for processing user services

Abstract

Embodiments of the present application disclose a service processing method and related products, which are applied to the billing field. A policy control device generates a first policy for a user service and sends the first policy to a session management function device to instruct the session management function device to perform a first quota management mode on the user service. The policy control device receives relevant information about a second quota management mode of a user or a user service for changing the first quota management mode sent by a charging processing device, and determines the second quota management mode according to the relevant information about the second quota management mode of the user service. The policy control device generates a second policy for the user service according to the second quota management mode, and the second policy is used to update or replace the first policy. According to this method, the quota management mode of the user service can be made time-sensitive, and the balance between delay requirements and credit control risks can be ensured.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular, to a method, a system, and related devices for processing user services in a charging system. Background Art

[0002] According to the 3GPP (3rd Generation Partnership Project) standard specifications, a Session Management Function (SMF) device usually uses a blocking mode for quota application for user services. That is, the SMF device needs to apply for a quota before the user service starts. The quota application in the blocking mode helps to reduce the credit control risk and the possibility of losses suffered by the operator, but it will increase the access delay of the user service, affect the provision of delay-sensitive services, and affect the user experience.

[0003] The delay-sensitive services supported by the 5G (5th Generation) network, such as uRLLC (ultraHigh-Reliability and Low-Latency Communication) services, have relatively high requirements for access delay. For this reason, the 3GPP standard specifications define a non-blocking mode for quota application and a suspended quota management mode for online charging services. For the non-blocking mode of quota application, the Session Management Function device does not need to start the user service after obtaining the quota authorization for the user service. That is to say, the Session Management Function device can start the user service first and apply for the quota of the user service at the same time or afterwards, which is beneficial to reducing the access delay of the user service. For the suspended quota management of online charging services, the Session Management Function device can regard the user service as a temporary offline charging user service or an unlimited quota user service, and there is no need for the Session Management Function device to frequently apply for a quota for the user service during the use of the user service.

[0004] However, on the other hand, if the non-blocking mode of initial quota application is blindly adopted, there are the following problems: the SMF device may find that the quota acquisition fails after the user service starts, which may not only cause resource waste, but also may cause malicious users to perform a DoS (Denial of Service) attack on the network. And adopting the suspended quota management mode may cause serious resource waste and losses to the operator.

[0005] How to balance the network element performance burden, the access delay requirements of user services, credit control risks, and network security is a technical problem that urgently needs to be solved. Summary of the Invention

[0006] In view of this, it is necessary to provide a method for processing user services to determine the quota management mode of user services and achieve a balance among the performance burden of the charging system, the access delay requirements of user services, and the credit control risk.

[0007] In a first aspect, an embodiment of the present application provides a service processing method executed by a policy control device. The policy control device generates a first policy for a user service and sends the first policy to a session management function device. The first policy indicates to execute the first quota management mode for the user service of the user. During the execution of the service, the policy control device receives relevant information of a second quota management mode of the user or the user service sent by the charging processing device for changing the first quota management mode, and determines the second quota management mode according to the relevant information of the second quota management mode of the user or the user service. The policy control device generates a second policy for the user service according to the second quota management mode. The second policy is used to update or replace the first policy and indicate to execute the second quota management mode for the user service. According to this method, during the execution of the service, the charging processing device sends a second quota management mode for changing the first quota management mode. Then the policy control device generates a second policy according to the second quota management mode to update or replace the first policy that has been executed. Thus, the quota management mode of the user service has timeliness, and the balance of delay requirements and credit control risk can be ensured.

[0008] In a possible implementation, the policy control device also receives relevant information of the first quota management mode of the user or the user service sent by the charging processing device. The policy control device determines the first quota management mode of the user service according to the relevant information of the first quota management mode of the user or the user service. Therefore, the first quota management mode is determined by the charging processing device, ensuring the timeliness of the determination of the first quota management mode.

[0009] In a possible implementation, the first quota management mode is a first initial quota application mode, and the second quota management mode is a second initial quota application mode. The first initial quota application mode is a blocking mode and the second initial quota application mode is a non-blocking mode, or the first initial quota application mode is a non-blocking mode and the second initial quota application mode is a blocking mode.

[0010] In a possible implementation, the first quota management mode is suspended quota management and the second quota management mode is enabled quota management, or the first quota management mode is enabled quota management and the second quota management mode is suspended quota management.

[0011] By different first quota management modes, different quota management modes for different services can be realized, thus meeting the diversity of services and user requirements.

[0012] In a possible implementation, the policy control device further sends a request message to the charging processing device. The policy control device receives a response message sent by the charging processing device, and the response message carries information related to the first quota management mode of the user or the user service. The policy control device determines the first quota management mode of the user service according to the information related to the first quota management mode of the user or the user service. Through this method, the policy control device requests and obtains information related to the first quota management mode from the charging processing device.

[0013] In a possible implementation, the first quota management mode is the first initial quota application mode, and the request message further carries an indication for obtaining the first quota management mode. The indication for obtaining is the identification of the user and the indication information for obtaining the service list of the non-blocking mode of the user. The information related to the first quota management mode carried by the response message is the service list of the first initial quota application mode that allows the user to use the non-blocking mode. Or the indication for obtaining is the identification of the user service and the indication information for obtaining whether the user service is allowed to use the first initial quota application mode of the non-blocking mode. The information related to the first quota management mode carried by the response message is the indication information for whether the user service is allowed to use the first initial quota application mode of the non-blocking mode. The indication for obtaining is the identification of the user and the indication information for obtaining whether the service of the user is allowed to use the first initial quota application mode of the non-blocking mode. The information related to the first quota management mode carried by the response message is the indication information for whether the service of the user is allowed to use the first initial quota application mode of the non-blocking mode. The indication for obtaining is the identification of the user service and the indication information for obtaining the first initial quota application mode of the user service. The information related to the first quota management mode carried by the response message is the first initial quota application mode of the user service, and the first initial quota application mode is a blocking mode or a non-blocking mode. The indication for obtaining is the identification of the user and the indication information for obtaining the first initial quota application mode of each service of the user. The information related to the first quota management mode carried by the response message is the first initial quota application mode of each service of the user, and the first initial quota application mode is a blocking mode or a non-blocking mode. Through this method, the policy control device can obtain the first initial quota application mode through various indications. In addition, the first quota management mode is the first initial quota management mode, so that the user service can use the blocking mode or the non-blocking mode to meet the needs of different user services.

[0014] In a possible implementation manner, the first quota management mode is to suspend or enable quota management, and the request message further carries an indication for obtaining the first quota management mode. The indication for obtaining is the identification of the user and the indication information for obtaining the service list that allows the user to suspend quota management. The relevant information of the first quota management mode carried in the response message is the service list that allows the user to suspend quota management. Or the indication for obtaining is the identification of the user service and the indication information for obtaining whether the user service is allowed to suspend quota management. The relevant information of the first quota management mode carried in the response message is the indication information for whether the quota management of the user service is allowed to be suspended. Or the indication for obtaining is the identification of the user and the indication information for obtaining whether the quota management of the user's service is allowed to be suspended. The relevant information of the first quota management mode carried in the response message is the indication information for whether the quota management of the user's service is allowed to be suspended. Or the indication for obtaining is the identification of the user service and the indication information for obtaining the first quota management mode of the user service. The relevant information of the first quota management mode carried in the response message is the first quota management mode of the user service, and the first quota management mode is to suspend quota management or enable quota management. Or the indication for obtaining is the identification of the user and the quota management modes of the user's various services. The relevant information of the first quota management mode carried in the response message is the information of the first quota management modes of the user's various services, and the first quota management mode is to suspend quota management or start quota management. Through this method, the policy control device can obtain the suspension or enabling of quota management through various indications. In addition, the first quota management mode is to suspend or enable quota management, so that the user service can use the suspended quota management or the enabled quota management to meet the requirements of different user services.

[0015] In a possible implementation manner, the relevant information of the first quota management mode of the user or the user service is: the indication information for whether the user's service is allowed to use the non-blocking mode, or the indication information for whether the quota management of the user's service is allowed to be suspended.

[0016] In a possible implementation manner, if the first quota management mode is the first initial quota application mode, the first policy includes an indication of the first initial quota application mode, and the first initial quota application mode is a non-blocking mode or a blocking mode. If the first quota management mode of the user service is to suspend quota management, the first policy includes that the charging method of the user service is offline charging or temporary offline charging. If the first quota management mode of the user service is to enable quota management, the first policy includes that the charging method of the user service is online charging. The first quota management mode is indicated by the first policy, so that the user service can be executed according to the first quota management mode. Thus, the execution of the service not only meets the requirements of the service, but also meets the requirements of the user.

[0017] In a possible implementation, the relevant information about the second quota management mode for changing the first quota management mode received by the policy control device from the charging processing device includes: the policy control device receives a notification message sent by the charging processing device for a user or a user service, and the notification message carries the relevant information about the second quota management mode of the user service. Through this method, the policy control device obtains the second quota management mode from the charging processing device, so that the first quota management mode is replaced, thereby ensuring the real-time nature of the quota management mode of the user service.

[0018] In a possible implementation, the first quota management mode is the first initial quota application mode of the blocking mode or the non-blocking mode, and the relevant information about the second quota management mode of the user service includes any of the following: a service list of the user allowing the use of the non-blocking second initial quota application mode; an indication information on whether to allow the user service to use the non-blocking second initial quota application mode; an indication information on whether to allow the user service to use the non-blocking second initial quota application mode; or the second initial quota application mode of the user service. Through this method, the policy control device can obtain the second initial quota application mode through various indications. In addition, the second quota management mode is the second initial quota management mode, so that the user service can use the blocking mode or the non-blocking mode to meet the needs of different user services.

[0019] In a possible implementation, the first quota management mode is to suspend or enable quota management, and the relevant information about the second quota management mode of the user service includes any of the following: a service list of the user allowing the suspension of quota management; an indication information on whether to allow the suspension of the quota management of the user service; an indication information on whether to allow the suspension of the quota management of the user's service; or the quota management mode of the user service for suspending or enabling quota management. Through this method, the policy control device can obtain various second quota management modes. In addition, the second quota management mode is to suspend or enable quota management, so that the user service can use the suspended quota management or the enabled quota management to meet the needs of different user services and different scenario requirements.

[0020] In a possible implementation, the policy control device saves the second quota management mode of the user service. So that the user service can use the second quota management mode next time, thereby making the determination of the quota management mode of the user service faster and saving network resources.

[0021] In a possible implementation, if the second quota management mode is the second initial quota application mode, the second policy includes the second initial quota application mode of the user service, and the second initial quota application mode is a blocking mode or a non-blocking mode; if the second quota management mode of the user service is the suspended quota management, the second policy includes that the charging method of the user service is the offline charging or the temporary offline charging; or, if the second quota management mode of the user service is the enabled quota management, the charging method of the user service included in the second policy is the online charging. The second quota management mode is indicated by the second policy, so that the user service can be executed according to the first quota management mode. Thus, the execution of the service not only meets the requirements of the service, but also meets the requirements of the user.

[0022] In a possible implementation, the second policy is sent to the session management function device, and the second policy is used to update the first policy of the user service. Alternatively, a deactivation instruction for the first policy and an activation instruction for the second policy are sent to the session management function device.

[0023] In a second aspect, an embodiment of the present invention provides a method for processing a user service executed by a charging processing device. In this method, the charging processing device determines that the first quota management mode of the user service of the user needs to be changed to the second quota management mode, and sends a notification message to the policy control device. The notification message carries the relevant information of the second quota management mode of the user or the user service, and the second quota management mode is used to change the first quota management mode. According to this method, during the execution of the service, the charging processing device sends the second quota management mode for changing the first quota management mode. Thus, the quota management mode of the user service has timeliness, and the balance between the delay requirement and the credit control risk can be ensured.

[0024] In a possible implementation, the first quota management mode is the first initial quota application mode, and the second quota management mode is the second initial quota application mode. The first initial quota application mode is a blocking mode and the second initial quota application mode is a non-blocking mode, or, the first initial quota application mode is a non-blocking mode and the second initial quota application mode is a blocking mode.

[0025] In a possible implementation, the first quota management mode is the suspended quota management and the second quota management mode is the enabled quota management, or, the first quota management mode is the enabled quota management and the second quota management mode is the suspended quota management.

[0026] In a possible implementation, when the charging processing device processes the charging request of the user service, or processes the charging request of other services of the user, or executes the charging management process for the user account, it determines that it is necessary to change the first quota management mode of the user service. Through this method, it is ensured that the first quota management mode can be changed in multiple scenarios, so that the quota management mode of the user service has timeliness, and the balance between delay requirements and credit control risks can be ensured.

[0027] In a possible implementation, the charging processing device receives the charging request of the user service, and the charging request includes the indication information of the first quota management mode used by the user service; and based on the indication information of the first quota management mode, it determines that it is necessary to change the first quota management mode of the user service to the second quota management mode. Or the charging processing device determines that it has sent the relevant information of the first quota management mode of the user service to the policy control device, and based on the first quota management mode, the charging processing device determines to change the first quota management mode of the user service to the second quota management mode. Through this method, multiple charging processing devices can be provided to determine to change the first quota management mode, so as to achieve the flexibility of determination and meet the needs of multiple user services.

[0028] In a possible implementation, the charging processing device saves the second quota management mode of the user service. So that the second quota management mode can be used for the next user service, thus making the determination of the quota management mode of the user service faster and saving network resources.

[0029] In a possible implementation, the charging processing device determines that there are resources created for the user. The charging processing device sends a notification message to the policy control device through the notification address corresponding to the resources.

[0030] In a possible implementation, the charging processing device receives the request message sent by the policy control device and sends a response message to the policy control device. The response message carries the relevant information of the first quota management mode of the user or the user service.

[0031] In a third aspect, a policy control device is provided. The device body has the function of implementing the policy control device in the first aspect above. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0032] In a fourth aspect, a charging processing device is provided. The device body has the function of implementing the charging processing device in the second aspect above. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0033] Fifth aspect, an embodiment of the present application provides a user service processing method. In this method, a policy control device determines a first quota management mode of a user service, generates a first policy for the user service according to the first quota management mode, and sends the first policy to a session management function device. The first policy is used to indicate to execute the first quota management mode for the user service. Then, a charging processing device sends information related to a second quota management mode of the user service for changing the first quota management mode to the policy control device. After receiving the information related to the second quota management mode, the policy control device determines the second quota management mode according to the information related to the second quota management mode of the user service, and generates a second policy for the user service according to the second quota management mode. The second policy is used to update or replace the first policy.

[0034] Sixth aspect, an embodiment of the present application provides a user service processing system, including a policy control device and a charging processing device. The policy control device can execute the method executed by the policy control device in the first aspect or any possible solution in the first aspect. The charging processing device can execute the method executed by the charging processing device in the second aspect or any possible solution in the second aspect.

[0035] Seventh aspect, an embodiment of the present application provides a user service processing system, including: a policy control device and a session function management device. The policy control device can execute the method executed by the policy control device in the first aspect or any possible solution in the first aspect. The session function management device is configured to receive the first policy or the second policy sent by the policy control device.

[0036] In a possible implementation, the session management function device can also execute Figures 2 - 6 any steps or methods that the session management device can execute.

[0037] Eighth aspect, an embodiment of the present application provides a user service processing system, including a policy control device, a session management function device, and a charging processing device. The policy control device can execute the method executed by the policy control device in the first aspect or any possible solution in the first aspect. The charging processing device can execute the method executed by the charging processing device in the second aspect or any possible solution in the second aspect. The session function management device is configured to receive the first policy or the second policy sent by the policy control device.

[0038] In a possible implementation, the session management function device can also execute Figures 2 - 6 any steps or methods that the session management device can execute.

[0039] Ninth aspect, an embodiment of the present application provides a charging processing device (101), including a processor and a memory, wherein:

[0040] A memory for storing program instructions;

[0041] A processor for invoking and executing the program instructions stored in the memory, so that the charging processing device (101) executes the method for processing user services in the second aspect or any possible solution in the second aspect.

[0042] In a tenth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions which, when running on a computer, cause the computer to execute the method for processing user services in the second aspect or any possible solution in the second aspect.

[0043] In an eleventh aspect, an embodiment of the present application provides a policy control device (104), including a processor and a memory, wherein:

[0044] A memory for storing program instructions;

[0045] A processor for invoking and executing the program instructions stored in the memory, so that the session management function device (102) executes the method for processing user services in the first aspect or any possible solution in the first aspect.

[0046] In a twelfth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions which, when running on a computer, cause the computer to execute the method for processing user services in the first aspect or any possible solution in the first aspect.

[0047] In a thirteenth aspect, an embodiment of the present application provides a chip which, when running, is used to implement the methods in the first aspect, the second aspect, any possible implementation solution of the first aspect or any possible implementation solution of the second aspect. Description of the Drawings

[0048] Figure 1A is a schematic diagram of a system architecture applying an embodiment of the present application;

[0049] Figure 1B is a schematic diagram of the architecture of a 5G system applying the present application;

[0050] Figure 2 is a flowchart of the method for processing user services provided by an embodiment of the present application;

[0051] Figure 3A is a flowchart of the method for the policy control device provided by an embodiment of the present application to determine the first quota management mode of user services;

[0052] Figure 3B is a flowchart of the method for the charging processing device provided by an embodiment of the present application to determine to change the first quota management mode of user services;

[0053] Figure 4 Flowchart of a method for determining the first quota management mode and the second quota management mode of a user service provided by an embodiment of the present application;

[0054] Figure 5A Another flowchart of a method for a policy control device provided by an embodiment of the present application to determine the first quota management mode of a user service;

[0055] Figure 5B Another flowchart of a method for a charging processing device provided by an embodiment of the present application to determine to change the first quota management mode of a user service;

[0056] Figure 6 Another flowchart of a method for determining the first quota management mode and the second quota management mode of a user service provided by an embodiment of the present application;

[0057] Figure 7 Schematic diagram of the hardware structure of a session management function device, a charging processing device, or a policy control device provided by an embodiment of the present application;

[0058] Figure 8 Schematic diagram of the logical structure of a charging processing device provided by an embodiment of the present application;

[0059] Figure 9 Schematic diagram of the logical structure of a policy control device provided by an embodiment of the present application. Detailed implementation manners

[0060] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application. Among them, in the description of the present application, unless otherwise specified, " / " means that the objects associated before and after are in an "or" relationship. For example, A / B may represent A or B; "and / or" in the present application is an association relationship describing associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. Among them, A and B may be singular or plural. And, in the description of the present application, unless otherwise specified, "a plurality of" means two or more than two. In addition, in order to clearly describe the technical solutions in the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the words such as "first" and "second" do not limit the quantity and execution order, and the words such as "first" and "second" do not necessarily limit to be different.

[0061] Figure 1 is an architecture diagram of the charging system provided by the embodiment of the present application, which is used to control the session management function device to process user services. It includes a charging processing device 101, a session management function device 102, a user device 103, and a policy control device 104. The main functions of these devices are described as follows.

[0062] Charging processing device 101: Communicates and connects with the session management function device 102 and the policy control device 104. The charging processing device 101 is used to receive the quota application information, usage information, etc. reported by the session management function device, and perform charging processing on user services. In addition, the charging processing device 101 determines or changes the quota management mode of user services according to the user's account information, and sends the quota management mode of user services to the policy control device 104, or sends the user's account information to the policy control device 104 so that the policy control device 104 determines the quota management mode of user services.

[0063] The charging processing device 101 can be a CHF (Charging Function) device defined by the 3GPP standard specification, or a CCS (Converged Charging System) device defined by the 3GPP standard specification, which includes the functions of the CHF device.

[0064] It should be understood that in practical applications, the charging system shown in Figure 1 can have more charging processing devices 101. For example, a cluster can be constructed, which includes multiple charging processing devices 101 that back up each other, thereby improving the disaster tolerance ability and achieving high availability.

[0065] For the convenience of narration, in the embodiment of the present application, sometimes the charging processing device 101 is also directly referred to as the CHF device.

[0066] Session management function device 102: Communicates and connects with the charging processing device 101, the policy control device 104, and the user device 103. This device can be used for:

[0067] (1) Receive the start request of the user service from the user device 103 (i.e., the request message used to request the session management function device to start the user service), start the user service according to the start request, and perform charging operations such as quota management and usage reporting on the user service;

[0068] (2) Carry the quota management mode adopted for the user service in the charging request to the charging processing device 101, so that the charging processing device 101 changes the quota management mode of the user service according to the user's account information and / or the usage information of the user service;

[0069] (3) Request the policy of the user service from the policy device 104, and perform quota management on the user service according to the policy or updated policy sent by the policy device 104 and the quota management mode carried in the policy or updated policy.

[0070] It should be understood that in practical applications, the charging system shown in FIG. 1 may have more session management function devices. They can be communicatively connected to the same charging processing device 101 (such as the charging processing device 101), or communicatively connected to different charging processing devices 101. Multiple service start requests initiated by the same user device for the same user service may be processed by the same or different session management function devices.

[0071] User device 103: Connected to the session management function device, used to send a start request for the user service to the session management function device, and access or use the user service through the session management function device.

[0072] The user device 103 may be a user equipment (UE) defined by the 3GPP standard specification, may be a wireless access device with wireless communication function or a wired access device without wireless communication function, including handheld devices, vehicle-mounted devices, wearable devices or computing devices; exemplarily, it may be a mobile phone, a tablet computer or a computer with wireless transceiver function; the user device 103 may also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in remote medical treatment, a wireless terminal in smart grid, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0073] It should be understood that in practical applications, the charging system shown in FIG. 1 may have more user devices.

[0074] Policy control device 104: Communicatively connected to the session management function device 102 and the charging processing device 101, used to provide the charging policy of the user service for the session management function device 102, and also used to provide the relevant information of the quota management mode corresponding to the user service or the user's service for the session management function device 102.

[0075] The policy control device 104 may be a Policy Control Function (PCF) device defined by the 3GPP standard specification, or a Policy and Charging rules Function (PCRF) device.

[0076] It should be noted that the "connection" or "linkage" mentioned above includes direct connection or communication connection through one or more intermediate network devices.

[0077] Figure 1B The schematic diagram of the architecture of a basic 5G system is shown. As Figure 1B shown, the system includes: Access and Mobility Management Function (AMF), Session Management Function (SMF), Radio Access Network (RAN), Unified Data Management (UDM), Policy Control Function (PCF), Data Network (DN), User Plane Function (UPF), UE, Application Function (AF), Unified Data Repository (UDR), and Charging Function (CHF). Optionally, Figure 1B it may also include the following functions ( Figure 1B not shown in the figure): Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), Network Exposure Function (NEF), NF Repository Function (NRF).

[0078] Among them, the main functions of each network element are described as follows:

[0079] AF: It can be understood as the naming of the application function network element in the 5G architecture. Among them, the application function network element mainly transmits the requirements of the application side for the network side, such as Quality of Service (QoS) requirements, etc. AF can be a third-party functional entity or an application service deployed by the operator, such as the IP Multimedia Subsystem (IMS) voice call service.

[0080] UDM: It can be understood as the naming of the Unified Data Management Network Element in the 5G architecture. Among them, the Unified Data Management Network Element mainly includes the following functions: unified data management, supporting the processing of authentication credentials in the 3GPP authentication and key negotiation mechanism, user identity processing, access authorization, registration and mobility management, subscription management, short message management, etc.

[0081] UDR: It can be understood as the naming of the Unified Data Repository Network Element in the 5G architecture. Among them, the Unified Data Repository Network Element mainly includes the following functions: the access functions for types of data such as subscription data, policy data, and application data.

[0082] PCF: It can be understood as the naming of the Policy Control Function Network Element in the 5G architecture. Among them, the Policy Control Function Network Element is mainly responsible for policy control functions such as charging, QoS bandwidth guarantee, and mobility management, and UE policy decision-making at the session and service flow levels. In this system, the PCFs connected to the AMF and the SMF are the Access and Mobility Control PCF (PCF for access and mobility control, AM PCF) and the Session Management PCF (PCF for session management, SM PCF) respectively. In actual deployment, the AM PCF and the SM PCF may not be the same PCF entity.

[0083] SMF: It can be understood as the naming of the Session Management Network Element in the 5G architecture. Among them, the Session Management Network Element mainly performs functions such as session management, execution of the control policies issued by the PCF, selection of the UPF, and UE IP address allocation.

[0084] AMF: It can be understood as the naming of the Access and Mobility Management Function Network Element in the 5G architecture. Among them, the Access and Mobility Management Function Network Element mainly includes the following functions: access and mobility-related functions such as connection management, mobility management, registration management, access authentication and authorization, reachability management, and security context management.

[0085] UPF: It can be understood as the naming of the User Plane Function Network Element in the 5G architecture. Among them, the User Plane Function Network Element mainly includes the following functions: user plane-related functions such as packet routing and transmission, packet detection, service usage reporting, QoS processing, lawful interception, uplink packet detection, and downlink packet storage.

[0086] (R)AN: (Radio) Access Network, corresponding to different access networks in 5G, such as wired access, radio base station access, and other methods.

[0087] DN: Data Network, which is used to identify the operator network access point name. In this application, DN may also include the functions of an Authentication, Authorization, and Accounting (AAA) server, which is responsible for performing secondary authentication on users.

[0088] CHF: Charging Function. It is responsible for reporting charging status information to the PCF and interacting with the SMF to implement quota management and charging control.

[0089] Among them, the functions of each interface are described as follows:

[0090] N7: The interface between the PCF and the SMF, which is used to issue PDU session granularity and service data flow granularity control policies.

[0091] N15: The interface between the PCF and the AMF, which is used to issue UE policies and access control related policies.

[0092] N5: The interface between the AF and the PCF, which is used to issue application service requests and report network events.

[0093] N4: The interface between the SMF and the UPF, which is used to transfer information between the control plane and the user plane, including the issuance of forwarding rules from the control plane to the user plane, QoS control rules, traffic statistics rules, etc., and the reporting of user plane information.

[0094] N11: The interface between the SMF and the AMF, which is used to transfer PDU session tunnel information between the RAN and the UPF, transfer control messages sent to the UE, transfer radio resource control information sent to the RAN, etc.

[0095] N2: The interface between the AMF and the RAN, which is used to transfer radio bearer control information from the core network side to the RAN, etc.

[0096] N1: The interface between the AMF and the UE, which is access-independent and is used to transfer QoS control rules, etc., to the UE.

[0097] N8: The interface between the AMF and the UDM, which is used for the AMF to obtain subscription data and authentication data related to access and mobility management from the UDM, and for the AMF to register the current mobility management related information of the UE with the UDM, etc.

[0098] N10: The interface between the SMF and the UDM, which is used for the SMF to obtain subscription data related to session management from the UDM, and for the SMF to register the current session related information of the UE with the UDM, etc.

[0099] N35: The interface between the UDM and the UDR, which is used for the UDM to obtain user subscription data information from the UDR.

[0100] N36: The interface between the PCF and the UDR, which is used for the PCF to obtain policy-related subscription data and application data-related information from the UDR.

[0101] N3: The interface between the RAN and the UPF, which is used to transfer user plane data between the RAN and the UPF.

[0102] N6: The interface between the UPF and the DN connection, which is used to transfer user plane data between the UPF and the DN.

[0103] N9: The interface between UPFs, such as the interface between the visited-policy control function (V-PCF) and the home-policy control function (H-PCF), or the interface between the UPF connected to the DN and the UPF connected to the RAN, which is used to transfer user plane data between UPFs.

[0104] N28: The interface between the PCF and the CHF, which is used for the PCF to subscribe to charging status (Policy Counter) information from the UDR, such as user balance status, remaining traffic status, etc.

[0105] N40: The interface between the SMF and the CHF, which is used for the SMF to report charging information (Charging data) to the CHF and obtain the quota (Credit) threshold from the CHF.

[0106] Figure 1A Or Figure 1B The shown charging system architecture enables the charging processing device 101 and / or the policy device to timely and dynamically determine the quota management mode of the user service. For example, during the use of the service, the quota management mode of the user service is determined or changed according to the user's account information and / or the usage information of the user service. Thus, it is possible to adopt a non-blocking mode for initial quota application or suspended quota management when the credit control risk of the user service is relatively low, and adopt a blocking mode for quota application or enable quota management when the credit control risk of the user service is relatively high. Therefore, it is possible to balance the requirements of the user service for access delay, the operator's requirements for system performance and credit risk control.

[0107] To facilitate the understanding of the embodiments of the present application, some concepts are explained below.

[0108] A user service refers to a service accessed or used by a user equipment 103 through a network device (such as a session management function device 102, or a user plane device not shown in FIG. 1). The user service may be a service in a Protocol Data Unit (PDU) session. For example, one or more data streams corresponding to a certain Rating Group (RG) in a PDU session, or a data stream corresponding to a certain RG and a service identifier in a PDU session, can be understood as the user service in the embodiments of the present application. In the embodiments of the present application, the "user service in a PDU session" and the "service in a PDU session" refer to multiple data streams corresponding to a certain RG in a PDU session, or a data stream corresponding to a certain service identifier in multiple data streams corresponding to a certain RG.

[0109] For the convenience of description, in the embodiments of the present application, sometimes the user service is also simply referred to as "service".

[0110] Regarding the user service accessed or used by the user equipment 103, the embodiments of the present application will mainly use the data connection service in a 5G network as an example for illustration; correspondingly, regarding the charging data, the embodiments of the present application will mainly use the information related to data traffic as an example for illustration. The information related to data traffic includes but is not limited to: the information of the PDU session collected by the session management function device, the usage amount of the allowed service unit in the PDU session, the charging trigger condition, the timestamp, etc.

[0111] The user's service refers to one or more services subscribed by the user. The user's service may be the user service in the PDU session being used, or the user-subscribed service that has not been used yet.

[0112] Starting a user service means that the session management function device allows the user service to pass through after receiving the start request of the user service. Allowing the user service to pass through includes allowing the signaling or data of the user service to pass through. For example: when the user service is the above-mentioned data connection service, "starting a user service" includes enabling the establishment or update operation of the PDU session for the data connection service to continue (if the PDU session is unavailable) or allowing the service data stream to pass through (if the PDU session is already available).

[0113] Quota Management Mode (QMM) refers to the method by which the session management function device 102 (which can also be a charging trigger device) processes the online charging user service. Specifically, in this application, the quota management mode can be the Initial Quota Request Mode (IQRM) (which can also be the initial quota application mode) for the online charging user service. The quota management mode can also be the Suspend / Resume Quota Management (SRQM) for the online charging user service. Among them, the initial quota application mode is the mode of applying for quota for the user service for the first time after receiving the start request of the user service. The initial quota application mode can be a blocking mode quota application or a non-blocking mode quota application, which are described separately as follows:

[0114] Blocking Mode Initial Quota Request (BLIQR) means that the session management function device 102 responds to the start request of the user service received from the user device 103, first applies for quota for the user service to the charging processing device 101, and only starts the user service after receiving the quota granted by the charging processing device 101 for the user service.

[0115] Non-Blocking Mode Initial Quota Request (NBIQR) means that the session management function device 102 responds to the start request of the user service received from the user device 103, does not give priority to applying for quota for the user service to the charging processing device 101, but gives priority to starting the user service, or applies for quota for the user service to the charging processing device 101 while starting the user service.

[0116] Suspend / Resume Quota Management (SRQM) means that for the online charging user service, when the balance is sufficient or there is no credit control risk, the quota management can be suspended or resumed. When the user service adopts the suspended quota management, the user service can be regarded as temporary offline charging or unlimited quota, and the session management function device 102 will not apply for quota for the user service to the charging processing device 101. When the balance of the user account is insufficient or the user has a credit control risk, the quota management is restored / resumed, and the normal quota management is started for the user service.

[0117] Quota Management Mode Indication Information (QMMInd) refers to the indication information of which quota management mode (such as IQRM or SRQM) has been adopted for a user service when the session management function device 102 receives a start request for the user service; the quota management mode indication information may only include the values of IQRM or SRQM, may also include the IQRMod field and its value, and may also include the SID (identification of the user service) field and its value. The embodiments of the present application do not limit the data structure of the quota management mode indication information.

[0118] Note that for the convenience of description, in the embodiments of the present application, sometimes "adopting a certain quota management mode for a certain user service" is described as "adopting an initial quota application of a certain mode for a certain user service".

[0119] The following further describes an example of the method flow that can be implemented based on the charging system architecture shown in FIG. 1, such as Figure 2 、 Figures 3A - 3B 、 Figure 4 and Figures 5A - 5B shown, where the session management function entity in the method flow corresponding to each figure corresponds to the session management function device 102 in FIG. 1, the charging processing device 101 corresponds to the charging processing device 101 in FIG. 1, the user equipment corresponds to the user equipment 103 in FIG. 1, and the policy control device 104 corresponds to the policy control device 104 in FIG. 1. The following description of these method flows will not be repeated.

[0120] Figure 2 In the corresponding method flow, the policy control device 104 generates a second policy based on the relevant information of the second quota management mode sent by the charging processing device 101 to update or replace the first policy that has been executed by the session management function device 102. The method flow mainly includes the following steps:

[0121] Step 202, the policy control device 104 determines the first quota management mode of the user service. The first quota management mode of the user service is the quota management mode determined by the policy control device 104 for the user service before the start of the user service.

[0122] The first quota management mode may be the first initial quota application mode. The first initial quota application mode may be: non-blocking mode or blocking mode. The blocking mode of the first initial quota application mode indicates that the user service needs to obtain the quota granted by the charging processing device 101 before starting. The non-blocking mode of the first initial quota application mode means that the user service does not need to obtain the quota granted by the charging processing device 101 before starting.

[0123] The first quota management mode can also be used for suspending / enabling quota management. Suspending quota management means that the user service can be regarded as temporary off-line charging or unlimited quota, and the session management function device 102 will not apply for quota for the user service to the charging processing device 101. Enabling quota management means starting to perform normal quota management for the user service.

[0124] As an example, before executing step 202, the policy control device 104 receives the relevant information of the first quota management mode of the user or user service sent by the charging processing device 101. Then, the policy control device 104 determines the first quota management mode of the user service according to the relevant information of the first quota management mode of the user or user service.

[0125] As another example, before executing step 202, the policy control device 104 obtains the account information of the user or the configuration information of the user from the charging processing device 101 or other network devices. Then, the policy control device 104 determines the first quota management mode of the user service according to the obtained account information or configuration information of the user.

[0126] As an option, before executing step 202, the policy control device 104 sends a request message to the charging processing device 101. The policy control device 104 receives the response message sent by the charging processing device 101, and the response message carries the relevant information of the first quota management mode of the user or user service.

[0127] Step 204: The policy control device 104 generates a first policy, and the first policy is used to indicate to perform the first quota management mode on the user service.

[0128] If the first quota management mode is the first initial quota application mode, the first policy includes an indication of the first initial quota application mode, and the first initial quota application mode is a non-blocking mode or a blocking mode. If the first quota management mode of the user service is suspending quota management, the first policy includes that the charging method of the user service is off-line charging or temporary off-line charging. If the first quota management mode of the user service is enabling quota management, the first policy includes that the charging method of the user service is on-line charging.

[0129] Step 206: The policy control device 104 sends the first policy to the session management function device 102.

[0130] Step 208: The policy control device 104 receives the relevant information of the second quota management mode of the user service for changing the first quota management mode sent by the charging processing device 101. The second quota management mode refers to changing or replacing the previously determined first quota management mode after the service starts.

[0131] In this step, the policy control device 104 receives a notification message sent by the charging processing device 101 for a user or a user service. The notification message carries information related to the second quota management mode of the user service.

[0132] In an alternative manner, the first quota management mode is the first initial quota application mode, and the second quota management mode is the second initial quota application mode. The first initial quota application mode is a blocking mode and the second initial quota application mode is a non-blocking mode, or the first initial quota application mode is a non-blocking mode and the second initial quota application mode is a blocking mode. Or,

[0133] In another alternative manner, the first quota management mode is suspended quota management and the second quota management mode is enabled quota management. Or the first quota management mode is enabled quota management and the second quota management mode is suspended quota management.

[0134] Step 210: The policy control device 104 determines the second quota management mode according to the information related to the second quota management mode of the user service.

[0135] Step 212: The policy control device 104 generates a second policy for the user service. The second policy is used to update or replace the first policy, and the second policy is also used to indicate the execution of the second quota management mode for the user service.

[0136] If the second quota management mode is the second initial quota application mode, the second policy includes the second initial quota application mode of the user service, and the second initial quota application mode is a blocking mode or a non-blocking mode. If the second quota management mode of the user service is suspended quota management, the second policy includes that the charging method of the user service is offline charging or temporary offline charging. If the second quota management mode of the user service is enabled quota management, the charging method of the user service included in the second policy is online charging.

[0137] The second policy includes a policy identifier that is the same as the identifier of the first policy, and the second policy is sent to the session management function device 102. The identifier related to the first policy indicates that the second policy is used to update the first policy of the user service. As another example, the policy control device 104 assigns a second policy identifier to the second policy. The policy control device 104 sends the second policy and the second policy identifier to the session management function device 102, and the second policy identifier indicates that the second policy is used to replace the first policy that has been executed. For example, the session management function device 102 can deactivate the first policy and activate the second policy according to the indication of the second policy identifier.

[0138] The above Figure 2The corresponding method flow enables the policy control device 104 to determine the second quota management mode based on the relevant information of the second quota management mode of the user service for changing the first quota management mode sent by the charging processing device 101, and generate a second policy to replace or update the first policy, so as to dynamically change the quota management mode, thereby helping to balance the relationship between the end - user's demand for access delay, the operator's demand for system performance and credit risk control in real - time and dynamically.

[0139] Regarding the above Figure 2 corresponding method flow, reference can be further made to the Figures 3A - 3B 、 Figure 4 , Figure 5A , Figure 5B and Figure 6 corresponding method flow.

[0140] Figure 3A This is the method flow chart for the policy control device 104 provided by the embodiments of the present application to determine the quota management mode of user services. Figure 3A In the corresponding method flow, the quota management mode is the initial quota request mode (IQRM). The policy control device 104 receives the IQRM information of the user or user service from the charging processing device 101, then determines the initial quota request mode of the user service, and generates a policy according to the determined initial quota request mode of the user service. The method flow mainly includes the following steps:

[0141] Step 300: The policy control device 104 determines that it needs to send a request message to the charging processing device 101.

[0142] Specifically, after receiving a policy acquisition request or a policy update request for a user service sent by the session management function device 102, in response to the policy acquisition request or the policy update request, the policy control device 104 determines that it needs to obtain information from the charging processing device 101. Usually, when receiving a request to establish a PDU session for a user, the session management function device 102 can send a policy acquisition request to the policy control device 104. The session management function device 102 can also send a policy acquisition request to the policy control device 104 after receiving a service start request. The session management function device 102 can carry user identification, information of the PDU session (such as the type of the PDU session) in the policy acquisition request sent to the policy control device 104.

[0143] Optionally, the policy control device 104 also determines that it needs to obtain the IQRM information of the user service from the charging processing device 101, and carries an indication of obtaining the IQRM - related information of the user service in the request message sent to the charging processing device 101.

[0144] Optionally, the policy control device 104 determines, according to the configuration information, that it is necessary to send a request message to the charging processing device 101 and determine that it is necessary to obtain relevant information of the IQRM. The configuration information may be the local configuration information of the policy control device 104 or the configuration information of this user obtained from the UDR. Alternatively, if the policy control device 104 determines that there is no stored relevant information about the user service or the user's IQRM, it determines that it is necessary to obtain the IQRM information of the user service from the charging processing device 101.

[0145] Step 302: The policy control device 104 sends a request message to the charging processing device 101.

[0146] Specifically, the request message can be used to obtain and subscribe to the current status and status change of the counter Counter from the charging processing device 101. This request may not carry an indication for obtaining the IQRM.

[0147] Furthermore, the request message can also be used to obtain relevant information of the IQRM of this user or this user service from the charging processing device 101. For example, if in step 300 the policy control device 104 determines that it is necessary to obtain the information of the first IQRM of the user service from the charging processing device 101, the request message can also carry an indication for obtaining the IQRM of the user service. The IQRM acquisition indication can be any of the indications in the following table:

[0148]

[0149] As an example, after receiving a policy acquisition request or a policy update request of a user sent by the session management function device 102, if the policy control device 104 determines that it is necessary to obtain the service list of the NB type service of the current user from the charging processing device 101, it sends a first acquisition indication of IQRM-related information to the charging processing device 101. The first acquisition indication of IQRM-related information carries the identification of the user and the indication information for obtaining the service list of the user's NB. Refer to the following example:

[0150]

[0151] Among them, the userID field represents the user identification. The value of RequestedNBM is true, indicating to obtain the service list of the user's IQRM as NB.

[0152] As another example, after receiving a policy acquisition request or a policy update request of a user sent by the session management function device 102, the policy control device 104 determines whether the current user or user service can use the non-blocking mode, and sends a second acquisition indication of IQRM-related information to the charging processing device 101. The second acquisition indication of IQRM-related information carries the identifier of the user service and / or the user identifier, and the indication information for acquiring the first initial quota application for whether to allow the user service or the user to use the non-blocking mode. For example, if the request message carries the user identifier and the identifier of the user service, it means that it is necessary to determine whether the current user service can use the non-blocking mode. If the request message carries the user identifier but does not carry the identifier of the user service, it means that it is necessary to determine whether the current user can use the non-blocking mode.

[0153] Refer to the following example:

[0154]

[0155] Among them, the userID field represents the user identifier. "InitialQRMMode" indicates that the charging processing device 101 needs to determine whether the user service or the user indicated in the request message can use the non-blocking mode. "RatingGroup" represents the user service corresponding to the ratinggroup. "Service ID" represents the user service corresponding to the identifier. For example, when the request carries "InitialQRMMode" and "RatingGroup", it indicates that the charging processing device 101 needs to determine whether the user service corresponding to the ratinggroup can use the non-blocking mode. When the request carries "InitialQRMMode" and "Service ID", it indicates that the charging processing device 101 needs to confirm whether the service indicated by the "Service ID" can use the non-blocking mode. When the request message does not carry "Service ID" and "RatingGroup", it indicates that the charging processing device 101 needs to confirm whether the user indicated by the "userID" can use the non-blocking mode.

[0156] As an option, after receiving a policy acquisition request or a policy update request of a user sent by the session management function device 102, the policy control device 104 determines that it is necessary to obtain relevant information of the first IQRM of the user service, and sends a third acquisition indication of IQRM-related information to the charging processing device 101 to obtain the first IQRM information of the user service. The third acquisition indication carries the identifier of the user service and the indication information for acquiring the first initial quota application mode of the user service. The first IQRM of the user service can be in a blocking mode or a non-blocking mode. Among them, the user service identifier can be a service identifier or a corresponding rate group or other identifiers that can identify the user service. Refer to the following examples:

[0157]

[0158] "IntialQRMMAuthorization" means that the charging processing device 101 needs to determine whether the user service indicated in the request message uses a non-blocking mode or a blocking mode. The user service indicated in the request message can be the user service corresponding to the ratinggroup in the "RatingGroup" or the user service corresponding to the user identifier in the "Service ID". For example, when the request carries "IntialQRMMAuthorizatione" and "RatingGroup", it indicates that the charging processing device 101 needs to determine and return whether the IQRM of the user service corresponding to the ratinggroup is in a blocking mode or a non-blocking mode. When the request carries "IntialQRMMAuthorization" and "Service ID", it indicates that the charging processing device 101 needs to confirm and return whether the IQRM of the service indicated by the "Service ID" is in a blocking mode or a non-blocking mode.

[0159] As another example, after receiving a policy acquisition request or a policy update request of a user sent by the session management function device 102, the policy control device 104 determines that it is necessary to obtain the first IQRM of each service of the user from the charging processing device 101, and then sends a fourth acquisition indication of IQRM-related information to the CHF to obtain the relevant information of the first IQRM of each service of the user. The fourth acquisition indication of IQRM-related information carries the user identifier and the indication information for acquiring the IQRM of each service of the user. The fourth IQRM acquisition indication can be in the following form:

[0160]

[0161] Among them, the userID field is the user identifier. "InitialQRMMode" being true indicates that the charging processing device 101 needs to determine the value of the initial quota application mode for each service of the user. This request message indicates that the charging processing device 101 needs to determine whether the first IQRM of each service of the user is a non-blocking mode or a blocking mode.

[0162] Step 304: After receiving the request message, the charging processing device 101 performs corresponding processing according to the request message to determine the relevant information of the first IQRM of the user service.

[0163] Specifically, if the request message does not carry the acquisition indication of the relevant information of the quota management mode (the first IQRM in this embodiment), the charging processing device 101 may not return or actively determine and return whether to allow the user's service to use the non-blocking mode. If the charging processing device 101 stores the IQRM information of each service, the charging processing device 101 determines whether the user or the user service can use the non-blocking mode according to the stored IQRM of each service. If the charging processing device 101 does not store the IQRM information of the service, the charging processing device 101 determines whether the user or the user service can use the non-blocking mode according to the user's account information and / or service type.

[0164] Furthermore, if the request message carries the acquisition indication of the quota management mode, the relevant information of the IQRM of the user or the user service is determined and returned according to the acquisition indication. For the specific processing, refer to the following table

[0165]

[0166] Step 306: The charging processing device 101 sends a response message to the policy control device 104 for the request message.

[0167] Specifically, the response message carries the relevant information of the first IQRM of the user or the user service obtained in step 304.

[0168] If the request message does not carry the acquisition indication of the first quota management mode, the response message carries the indication information of whether to allow the user's service to use the non-blocking mode. If the request message carries the acquisition indication of the first quota management mode, the response message carries the relevant information of the IQRM corresponding to the acquisition indication.

[0169] If the charging processing device 101 receives the acquisition indication of the IQRM relevant information in step 302, the content carried in the response message refers to the following table:

[0170]

[0171] The first IQRM response message can refer to the following form:

[0172]

[0173] Among them, "NBMserviceList" indicates that the carried list is for user services that can use the non-blocking mode.

[0174] The second response message can refer to the following form:

[0175]

[0176] Among them, the value of "NBModeAuthResult" is "yes", indicating that any online charging service of the user can use the non-blocking mode.

[0177] If the second IQRM acquisition indication carries a rate group or a service identifier, the second IQRM response message can refer to the following form:

[0178]

[0179] If the value of "RatingGroup" or "ServiceID" is 1 and the value of "ServiceResult" is "yes", it indicates that the user service with a service identifier of 1 or a rate group of 1 can use the non-blocking mode. If the value of "RatingGroup" or "ServiceID" is 2 and the value of "ServiceResult" is "no", it indicates that the user service with a service identifier of 2 or a rate group of 2 can use the non-blocking mode.

[0180] The third response message can refer to the following form:

[0181]

[0182] Among them, the value of "IQRMValue" is "NB", indicating that the first initial quota application mode for the service corresponding to the rate group "RatingGroup" or the service indicated by the service identifier "ServiceID" is the non-blocking mode.

[0183] The fourth IQRM response message can refer to the following form:

[0184]

[0185]

[0186] Among them, the value of "IQRMValue" is "NB", indicating that the service corresponding to the rating group "RatingGroup" with a value of 1 or the service indicated by the service identifier 1 uses the non-blocking mode. The value of "IQRMValue" is "B", indicating that the service corresponding to the rating group "RatingGroup" with a value of 2 or the service indicated by the service identifier 2 uses the blocking mode.

[0187] Step 308, the policy control device 104 determines the first quota management mode of the user service and generates the first policy for the user service. The first policy is used to indicate the execution of the first quota management mode for the user service.

[0188] Specifically, if the response message returned by the charging processing device 101 carries the relevant information of the first IQRM of the user or the user service, the policy control device 104 determines the first quota management mode of the user service according to the relevant information of the first IQRM of the user or the user service.

[0189] Specifically, the policy control device 104 generates the first policy, and the first policy includes the first quota management mode of the user service. Here, the quota management mode is the first initial quota application mode, and the first initial quota application mode is the blocking mode or the non-blocking mode.

[0190] Step 310, the policy control device 104 sends the first policy to the session management function device 102.

[0191] Specifically, the policy control device 104 sends the first policy to the session management function device 102 to indicate that the session management function device 102 executes the first quota management mode for the user service;

[0192] Specifically, the control policy sent to the session management function device 102 can refer to the following form:

[0193]

[0194] Among them, the value of "sdfHandl" is true, indicating that the IQRM of the service indicated by the service identifier or the service indicated by the rating group is the blocking mode.

[0195] Through the embodiments of the present application, the policy control device 104 obtains the IQRM information of the user service from the charging processing device 101 before issuing the policy and sends the IQRM information of the user service to the session management function device 102 in the policy. Through the embodiments of the present application, the IQRM information carried in the policy sent by the policy control device 104 to the session management function device 102 is more accurate, which can avoid risks during the service usage process.

[0196] Figure 3BThis is a flowchart of a method for a charging processing device 101 provided in an embodiment of the present application to determine to change the first quota management mode of a user service. In combination with Figure 3A combined with Figure 3B In the corresponding method flow, the first quota management mode is the initial quota application mode (IQRM). For example, the charging processing device 101 makes a real-time decision to change the first IQRM of the user service to the blocking mode, or the charging processing device 101 makes a real-time decision on whether to prohibit the use of the non-blocking mode of the user service. When the charging processing device 101 determines to change the first IQRM of the user service to the blocking mode or the service quota management mode of the user service prohibits the first IQRM from being the non-blocking mode, the charging processing device 101 notifies the policy control device 104 so that the policy control device 104 can determine the second quota management mode of the user service (in this embodiment, it is the second IQRM) according to the second IQRM-related information of the user service, and further determine whether to generate a second policy. The method flow mainly includes the following steps:

[0197] Step 351, The session management function device 102 receives a start request for a user service.

[0198] After the session management function device 102 receives the service start request, it determines that it has obtained the information of the first quota management mode (in this embodiment, it is the first IQRM) of the user service (such as service A), for example, the first IQRM information of the user service included in step 310 in Figure 3A The session management function device 102 performs corresponding processing according to the information of the first IQRM of the user service. If the session management function device 102 determines that it has not obtained the first IQRM information of the service, it can execute the process in Figure 3A to obtain the IQRM information of the user's service.

[0199] If the session management function device 102 determines that the first IQRM information of the obtained service indicates that the IQRM of the user service is the non-blocking mode, the session management function device 102 first starts the user service, and then sends a quota application request to the charging processing device 101 to apply for a quota for the user service or sends a quota request to the charging processing device 101 at the same time as starting the service to apply for a quota for the user service. If the session management function device 102 determines that the first IQRM information of the obtained user service indicates that the IQRM of the user service is the blocking mode, the session management function device 102 first sends a quota application request to the charging processing device 101 to apply for a quota for the user service, and starts the user service after receiving the quota allocated by the charging processing device 101.

[0200] Step 352, The session management function device 102 sends a charging request for the user service to the charging processing device 101.

[0201] The charging request may be an initial charging request (i.e., the first charging request for a user to use a certain service), or an updated charging request after the initial charging request. Embodiments of the present invention do not make any limitations here.

[0202] As an alternative, the charging request also carries information of the first IQRM of the user service, so as to indicate the IQRM currently used by the user service (such as user service A). Embodiments of the present application take the IQRM of service A as a non-blocking mode as an example for illustration. That is, the IQRM information of service A carried in the charging request is in a non-blocking mode.

[0203] Step 353: The charging processing device 101 performs corresponding charging processing according to the charging request, and sends a charging response to the session management function device 102.

[0204] The above steps 351 to 353 are optional steps. In some scenarios, the above steps may not be executed, and the process may directly start from step 354. For example: the user service has not started, or other user services of the user or the user account management process may cause a change in the first quota management mode (here is the first initial quota application mode) corresponding to the user service.

[0205] Step 354: The charging processing device 101 determines the relevant information for changing the first IQRM of user service A.

[0206] Specifically, the charging processing device 101 may determine that it is necessary to change the first quota management mode of the user service when processing the charging request of the user service sent in step 352, or when processing the charging request of other services of the user, or when performing the charging management process on the user account.

[0207] For example, the charging processing device 101 determines that it is necessary to change the quota management mode of the user service as follows: the charging processing device 101 determines that the user service currently uses the first quota management mode, and determines that it is necessary to change the first quota management mode of the user service to the second quota management mode.

[0208] Among them, the method by which the charging processing device 101 determines that the user service currently uses the first quota management mode can be: The charging processing device 101 receives a charging request for the user service, and the charging request includes indication information indicating that the user service currently uses the first quota management mode. The charging processing device 101 determines that the user service currently uses the first quota management mode according to the first quota management mode indication information of the user service included in the charging request; or, the charging processing device 101 determines that it has sent relevant information about the first quota management mode of the user service to the policy control device 104, and determines that the user service currently uses the first quota management mode based on the relevant information about the first quota management mode of the user service sent to the policy control device 104.

[0209] Among them, the situation where the charging processing device 101 determines that it is necessary to change the first quota management mode of the user service to the second quota management mode of the user service can be: When processing the charging request of the user service sent in processing step 352, or when processing the charging request of other services of the user or when performing a charging management process on the user account, the charging processing device 101 determines that the conditions for the user service to use the first quota management mode are not met. For example: If the balance of the user account does not meet the conditions for service A to adopt the non-blocking mode, the charging processing device 101 determines to change the IQRM of service A to the blocking mode, or prohibits service A from using the non-blocking mode. The conditions for the user service to adopt the non-blocking mode can be: The remaining amount of the user account package is greater than the first threshold, or the balance decline rate of the user account is lower than the second threshold, or others.

[0210] Furthermore, when the charging processing device 101 determines to change the non-blocking mode of user service A to the blocking mode, it can also determine to change the non-blocking mode of other services of the user to the blocking mode, or determine to prohibit other services of the user from using the non-blocking mode.

[0211] As an option, after the charging processing device 101 determines the relevant information for changing the IQRM of the user service, it saves the determined result, that is: saves the determined second quota management mode of the user service, so as to provide it to the requesting device when other devices subsequently obtain the IQRM information of the user service.

[0212] Step 355, the charging processing device 101 sends relevant information about the second IQRM of the user service for changing the first IQRM to the policy control device 104.

[0213] Specifically, the charging processing device 101 sends a notification message (also called a change notification) to the policy control device 104, and the notification message carries relevant information about the second quota management mode of the user service, that is, relevant information about the second IQRM of the user service.

[0214] The charging processing device 101 determines that there is a resource created by the policy control device 104 for the user, and sends a notification message to the policy control device 104 through the notification address corresponding to the resource. The resource created for the user is: the resource that the policy control device 104 requests the charging processing device 101 to create for the user. The resource created for the user is used for the policy control device to obtain (subscribe to) the cumulative status information of the user. The resource created for the user is created by the charging processing device according to the resource creation request after the policy control device sends a resource creation request to the charging processing device. The resource creation request carries the notification address corresponding to the resource and the user identifier. This notification address is used for the charging processing device 101 to notify the policy control device 104 of the cumulative status information of the user. Based on the determined existence of the resource requested to be created for the user, the charging processing device 101 determines that it needs to send a notification message of the second IQRM-related information of the user service to the policy control device 104. Or, based on the determined existence of the resource (or subscription information) requested to be created for the user, if the charging processing device 101 determines that the policy control device 104 has subscribed to or requested the first IQRM-related information of the user, it determines that it needs to send a notification message of the second IQRM-related information of the user service to the policy control device 104.

[0215] The relevant information of the second IQRM of the user service carried in the notification message can be as follows in the reference table:

[0216] First Notice List of Services Allowed for the User to Use the Non - blocking Second IQRM Second Notice Indication Information on Whether to Allow the User to Use the Non - blocking Second IQRM Third Notice Indication Information on Whether to Allow the User's Services to Use the Non - blocking Second IQRM Fourth Notice Indication Information on Whether the Second IQRM of the User's Services is Blocking or Non - blocking Fifth Notice Indication Information on Whether the Second IQRM of Each Service of the User is Blocking or Non - blocking

[0217] The notification message containing the first notification can be called the first notification message, and so on. The following is a reference example of the second notification message:

[0218]

[0219] Among them, the userID field represents the user identifier. The value of "NBModeAuthResult" being "no" means that the charging processing device 101 confirms that the user cannot use the non-blocking mode, that is, all services of this user cannot use the non-blocking mode.

[0220] For other notification messages, such as reference examples of the second notification message, the third notification message, the fourth notification message, or the fifth notification message, the embodiments of the present application will not give examples here.

[0221] Step 356: After receiving the relevant information of the second quota management mode of the user service sent by the charging processing device 101, the policy control device 104 determines the second quota management mode of the user service according to the relevant information of the second quota management mode, and generates the second policy of the user service.

[0222] The second policy is used to update or replace the first policy and to indicate the execution of the second quota management mode for the user service.

[0223] Among them, the second policy updates the first policy specifically as follows: The generated second policy includes a policy identifier that is the same as the identifier of the first policy, and it is determined by the identifier that it is used to update the first policy.

[0224] Among them, the second policy replaces the first policy specifically as follows: The second policy identifier assigned to the second policy. The second policy is a new policy for a user service different from the first policy. The policy control device 104 needs to first deactivate the first policy and then activate the second policy.

[0225] Step 357: The policy control device 104 sends the second policy to the session management function device 102, and the second policy carries the second IQRM information.

[0226] Specifically, if the second policy includes a policy identifier that is the same as the identifier of the first policy, then the policy update message sent by the policy control device 104 to the session management function carries the second policy to update the first policy of the user service.

[0227] If the second policy is a new policy for the user service, then the policy update message sent by the policy control device 104 to the session management function carries a deactivation instruction for the first policy and an activation instruction for the second policy, so as to update the first policy of the user service with the second policy.

[0228] According to the embodiments of the present application, the charging processing device 101 can determine or change the first IQRM of the user service according to information such as the user's account information. Thus, the IQRM of the user service can be made more accurate, and the risks and losses caused by blindly using the non-blocking mode in the user service can be avoided.

[0229] It should be noted that in the actual business use process, Figure 3B can be used in combination with Figure 3A or separately. The embodiments of the present application do not make any limitations here.

[0230] Figure 4 This is a flowchart of the method for determining the first quota management mode and the second quota management mode of the user service provided by the embodiments of the present application. In this embodiment, the quota management mode is the initial quota request mode (IQRM). And Figure 3A and Figure 3BDifferent from the corresponding embodiments, in this embodiment, the policy control device 104 determines the first quota management mode of the user service according to the obtained user configuration information, that is, determines whether the user service uses the non-blocking mode. The charging processing device 101 makes a real-time decision on whether to change the first quota management mode of the user service to the second quota management mode of the charging processing device 101. The method flow mainly includes the following steps:

[0231] Steps 401-402: The policy control device 104 sends a resource creation request to the charging processing device 101 and receives a resource creation response from the charging processing device 101.

[0232] After receiving the policy acquisition indication of the user service or the policy update request of the user service sent by the session management function device 102, the policy control device 104, in response to the policy acquisition indication or the policy update request, sends a resource creation request to the charging processing device 101. So as to obtain the user service or the relevant information of the user from the charging processing device 101 through the created resource. For example, the usage information of the user service. The resource creation request can also be a session establishment request to establish a session between the policy control device 104 and the charging processing device 101.

[0233] Step 403: The policy control device 104 determines the first quota management mode of the user service (the first IQRM in this application) according to the obtained information, and generates the first policy of the user service according to the determined first IQRM of the user service. The generated first policy of the user service contains the first IQRM information of the user service.

[0234] For example, the policy control device 104 can obtain the user's configuration information from the charging processing device 101 or other network devices such as (UDR), and determine the IQRM of the user service based on the obtained user's configuration information. For example, the policy control device 104 can determine the first IQRM of the user service according to the information of the user account obtained from the charging processing device 101 and / or the usage information of the user service. The policy control device 104 can also determine the first IQRM according to the information of the user obtained from the UDR, such as whether the user subscribes to the non-blocking mode of IQRM.

[0235] Step 404: The policy control device 104 sends the generated first policy of the user service to the session management function device 102.

[0236] For the specific description of step 404, reference can be made to the description of step 310, which will not be elaborated in this application embodiment.

[0237] Step 405: The session management function device 102 receives the start request of the user service and processes it according to the first IQRM. The business identifier and the user identifier are carried in the start request of the user service.

[0238] Specifically, for the description of step 405, reference may be made to the description of step 351, which will not be elaborated in the embodiments of the present application.

[0239] Step 406, the session management function device 102 sends a charging request to the charging processing device 101. The charging request may be a charging request for the user service or a charging request for other services used by the user. In addition, the charging request may be an initial charging request (i.e., the first charging request for a certain service used by the user) or an updated charging request after the initial charging request. The embodiments of the present invention do not make limitations here.

[0240] Furthermore, the first IQRM information of the user service is carried in the charging request to indicate the current IQRM used by the user service (such as service B). In the embodiments of the present application, the first IQRM of the user service is taken as an example of the non-blocking mode for illustration. That is, the IQRM information of user service B carried in the charging request is in the non-blocking mode, indicating that the session management function device 102 will release the data stream related to user service B before receiving the quota allocated by the charging processing device 101.

[0241] Step 407, the charging processing device 101 performs corresponding charging processing according to the charging request, and then sends a charging response to the session management function device 102.

[0242] Step 408, the charging processing device 101 determines that it is necessary to change the first IQRM of the user service, generates a second IQRM for changing the first IQRM, and saves the information of the changed second IQRM.

[0243] Specifically, in the process of the charging processing device 101 executing step 407, it determines that the user service uses the non-blocking mode according to the first IQRM information of the user service carried in the charging request. When the charging processing device 101 determines that the user account does not meet the conditions for the user service to adopt the non-blocking mode, it determines that the second quota management mode (the second IQRM in this embodiment) of the user service is the blocking mode, or prohibits the user service from using the non-blocking mode. The conditions for the user service to adopt the non-blocking mode may be: the remaining amount of the user account package is greater than the first threshold, or the balance reduction speed of the user account is lower than the second threshold, or others.

[0244] Furthermore, when the charging processing device 101 determines to change the non-blocking mode of the user service to the blocking mode, it may also determine to change the non-blocking mode of other services of the user to the blocking mode, or determine to prohibit other services of the user from using the non-blocking mode, or prohibit all services of the user from using the non-blocking mode.

[0245] It should be noted that there is no time sequence between step 407 and step 408.

[0246] Step 409: The charging processing device 101 sends a notification message (also referred to as a change notification) regarding the relevant information of the first IQRM for changing the user service to the policy control device 104, so that the policy control device 104 can generate or update the control policy for the user service according to the change notification.

[0247] Specifically, the description of step 409 is the same as that of step 355, and the embodiments of the present invention will not elaborate herein.

[0248] Steps 410 - 411 are the same as the descriptions of steps 356 - 357, and the embodiments of the present invention will not elaborate herein.

[0249] According to the embodiments of the present application, the policy control device 104 determines whether the user service can use the non - blocking mode according to the obtained relevant information of the user. In addition, during the use of the user service, the IQRM of the user service is determined or changed according to the account information of the user. Thereby, the IQRM of the user service is more accurate, and the risks and losses caused by using the non - blocking mode during the use of the user service can be avoided.

[0250] Figure 5A It is a flowchart of the method for the policy control device 104 to determine the policy provided by the embodiments of the present application. Figure 5A In the corresponding method flow, the quota management mode is to suspend or enable quota management (SRQM). The policy control device 104 receives the relevant information of the quota management mode of the user or the user service from the charging processing device 101, and then determines whether to suspend or enable the quota management of the user service, and generates a policy accordingly. The method flow mainly includes the following steps:

[0251] Step 500: The policy control device 104 determines that a request message needs to be sent to the charging processing device 101.

[0252] Specifically, after receiving the policy acquisition request or the policy update request for the user service sent by the session management function device 102, in response to the policy acquisition request or the policy update request, the policy control device 104 determines that it needs to obtain information from the charging processing device 101, and then determines to send a request message to the charging processing device 101. Generally, when receiving a request to establish a PDU session for a user, the session management function device 102 can send a policy acquisition request to the policy control device 104. The session management function device 102 can also send a policy acquisition request to the policy control device 104 after receiving a service start request. The session management function device 102 can carry user identification, information of the PDU session (such as the type of the PDU session), etc. in the policy acquisition request sent to the policy control device 104.

[0253] Optionally, the policy control device 104 also determines whether it is necessary to obtain information on the SRQM of the user's service from the charging processing device 101. If necessary, an indication to obtain the SRQM-related information of the user's service is carried in the request message sent to the charging processing device 101.

[0254] Optionally, the policy control device 104 determines, according to the configuration information, that it is necessary to send a request message to the charging processing device 101 and to obtain the SRQM-related information of the user service. The configuration information may be the local configuration information of the policy control device 104 or the configuration information of this user obtained from the UDR.

[0255] Step 502: The policy control device 104 sends a request message to the charging processing device 101.

[0256] Specifically, the request message may be used to obtain and subscribe to the current status and status change of the counter Counter from the charging processing device 101, and this request may not carry an indication to obtain the SRQM.

[0257] Furthermore, the request message may also be used to obtain the SRQM-related information of this user or this user service from the charging processing device 101. For example, in step 500, the policy control device 104 determines that it is necessary to obtain the SRQM information of the user service from the charging processing device 101, and the request message may also carry an indication to obtain the SRQM of the user service. The SRQM acquisition indication may be any of the indications in the following table:

[0258]

[0259] Specifically, the method for the policy control device 104 to carry any of the above first to fourth acquisition indications in the request message sent to the charging processing device 101 is similar to the method for carrying the corresponding first to fourth acquisition indications in step 302 of Embodiment 3A, and details are not described in this embodiment of the present invention.

[0260] Step 504: After receiving the request message, the charging processing device 101 performs corresponding processing according to the request message. For example, it determines the first SRQM-related information of the user service.

[0261] Specifically, if the request message does not carry an indication for obtaining information related to the quota management mode (the first SRQM in this embodiment), the charging processing device 101 can actively determine and return whether to suspend the user's quota management. If the charging processing device 101 stores the SRQM information for each service, the charging processing device 101 determines whether the user or the user's service can suspend quota management according to the stored SRQM information for each service. If the charging processing device 101 does not store the SRQM information for the service, the charging processing device 101 determines whether the user or the user's service can use the non-blocking mode according to the user's account information and / or service type.

[0262] Further, if the request message carries an indication for obtaining the quota management mode, the relevant information of the SRQM of the user or the user's service is determined and returned according to the obtaining indication. For specific processing, see the following table:

[0263]

[0264]

[0265] The specific method is similar to step 304 of Embodiment 3A and will not be elaborated here.

[0266] Step 506, the charging processing device 101 sends a response message to the request message to the policy control device 104.

[0267] Specifically, the response message carries the relevant information of the first SRQM of the user or the user's service obtained in step 504.

[0268] - If the request message does not carry an indication for obtaining the quota management mode, the response message carries an indication information of the first quota management mode for whether to allow suspending the user's service.

[0269] - If the request message carries an indication for obtaining the quota management mode (such as any one of the first obtaining indication to the fourth obtaining indication,

[0270] then the response message carries the relevant information of the first SRQM corresponding to the obtaining indication.

[0271] The specific method and message example are similar to step 306 of Embodiment 3A and will not be elaborated here.

[0272] Step 508, the policy control device 104 determines the first quota management mode of the user service and generates a first policy for the user service. The first policy is used to indicate to execute the first quota management mode for the user service

[0273] Specifically, if the response message returned by the charging processing device 101 carries the relevant information of the first SRQM of the user or the user service, the policy control device 104 determines the first quota management mode of the user service according to the relevant information of the first SRQM of the user or the user service. Here, the quota management mode is to suspend or start quota management.

[0274] Specifically, the policy control device 104 generates a first policy. If the determined first quota management mode of the user service is to suspend quota management, the charging method of the user service included in the first policy is offline charging or temporary offline charging. If the determined first quota management mode of the user service is to enable quota management, the charging method of the user service included in the first policy is online charging.

[0275] Step 510, the policy control device 104 sends the first policy to the session management function device 102.

[0276] Specifically, the policy control device 104 sends the first policy to the session management function to instruct the session management function device 102 to execute the first quota management mode for the user service;

[0277] Specifically, the control policy sent to the session management function device 102 can refer to the following form:

[0278]

[0279] Among them, the value of "ChargingMethod" is TempOffline, indicating the suspension of quota management for the user service.

[0280] Through the embodiments of the present application, the policy control device 104 obtains the relevant information of the first SRQM of the user service from the charging processing device 101 before issuing the policy, and generates the first policy of the user service according to the relevant information of the first SRQM to send to the session management function device 102. Through the embodiments of the present application, the first policy sent by the policy control device 104 to the session management function device 102 determines the charging method based on the decision of the charging processing device 101, which can not only reduce the burden of charging processing, improve the efficiency of the entire system, but also avoid the credit control risk during the business use process.

[0281] Figure 5B This is the flowchart of the method for the charging processing device 101 provided by the embodiments of the present application to determine to change the quota management mode of the user service. Combined with Figure 5A Combined with Figure 5BIn the corresponding method flow, the quota management mode is to suspend or enable quota management (SRQM). The policy control device 104 receives information related to the second SRQM for changing the first SRQM from the charging processing device 101, and determines whether to suspend or enable the quota management of the user service according to the relevant information of the second SRQM, and determines whether to update / replace the previous first policy of the user service. The method flow mainly includes the following steps:

[0282] Step 552, during the use of the user service, the session management function device 102 sends a charging request for the user service to the charging processing device 101.

[0283] This charging request can be an initial charging request (i.e., the first charging request for a user to use a certain service), or an updated charging request after the initial charging request. This is not limited in the embodiments of the present invention.

[0284] As an alternative, the charging request also carries SRQM information corresponding to the service (taking temporary suspension as an example) to indicate that the service (such as service A) currently has suspended quota management.

[0285] Before executing this step, the session management function device 102 receives a start request for the user service and determines that it has obtained information on the first quota management mode (the first SRQM in this embodiment) of the user service (such as service A). For example, in Figure 5A the first SRQM information of the user service included in step 510. The session management function device 102 performs corresponding processing according to the information of the first SRQM of the user service. If the session management function device 102 determines that it has not obtained the first IQRM information of the service, it can execute the process in Figure 5A to obtain the first SRQM information of the user's service.

[0286] If the session management function device 102 determines that the first SRQM information of the obtained service indicates that the SRQM of the user service is pending quota management, the session management function device 102 starts the user service and does not obtain a quota from the charging processing device 101. If the session management function device 102 determines that the information of the first SRQM of the obtained user service indicates that the SRQM of the user service is start quota management, the session management function device 102 first sends a quota application request to the charging processing device 101 to apply for a quota for the user service, and starts the user service after receiving the quota allocated by the charging processing device 101. Or if the session management function device 102 determines that the information of the first SRQM of the obtained user service indicates that the SRQM of the user service is start quota management, the session management function device 102 first starts the service, and then sends a quota application request to the charging processing device 101 to apply for a quota for the user service or sends a quota request to the charging processing device 101 to apply for a quota for the user service while starting the service. If the session management function device 102 determines that the information of the first SRQM of the obtained user service indicates that the SRQM of the user service is start quota management, the session management function device 102 can further adopt the first initial quota mode of the blocking mode or the non-blocking mode, for details, see the foregoing embodiments.

[0287] Step 553: The charging processing device 101 performs corresponding charging processing according to the charging request, and sends a charging response to the session management function device 102.

[0288] The above steps 552 to 553 are optional steps. In some scenarios, the above steps are not executed, and directly start from step 554. For example: the user service has not started, and other user services of the user or the user account management process may cause a change in the quota management mode corresponding to the user service (here it is pending or enabling quota management).

[0289] Step 554: The charging processing device 101 determines that it is necessary to change the first SRQM-related information of user service A.

[0290] The charging processing device 101 can determine whether it is necessary to change the first quota management mode of the user service when processing the charging request of the user service sent in step 552, or when processing the charging request of other services of the user, or when performing the charging management process on the user account.

[0291] For example, the charging processing device 101 determines that it is necessary to change the quota management mode of the user service as follows: The charging processing device 101 determines the first quota management mode of the user service, and determines that it is necessary to change the first quota management mode of the user service to the second quota management mode.

[0292] Among them, the method for the charging processing device 101 to determine that the user service currently uses the first quota management mode may be as follows: The charging processing device 101 receives a charging request for the user service, and the charging request includes indication information indicating that the user service currently uses the first quota management mode. The charging processing device 101 determines that the user service currently uses the first quota management mode according to the first quota management mode indication information of the user service included in the charging request; or, the charging processing device 101 determines that it has sent relevant information about the first quota management mode of the user service to the policy control device 104, and determines that the user service currently uses the first quota management mode based on the relevant information about the first quota management mode of the user service sent to the policy control device 104.

[0293] Among them, the charging processing device 101 determines that it is necessary to change the first quota management mode of the user service to the second quota management mode of the user service. This can be done as follows: When processing the charging request for the user service sent in step 552, or when processing the charging request for other services of the user, or when performing a charging management process on the user account, the conditions for the user service to use the first quota management mode are not met. For example, the balance of the user account does not meet the conditions for service A to adopt the suspended quota management, then it is determined to change the SRQM of service A to the enabled quota management.

[0294] Furthermore, when the charging processing device 101 determines to change the suspended quota management of user service A to the enabled quota management, it can also determine to change the suspended quota management of other services of the user to the enabled quota management, or determine to prohibit other services of the user from using the suspended quota management.

[0295] As an option, after the charging processing device 101 determines the relevant information for changing the first SRQM of the user service, it saves the determined result, that is, saves the determined use of the second quota management mode for the user service, so as to provide it to the requesting device when other devices subsequently obtain the SRQM information of the user service.

[0296] Step 555: The charging processing device 101 sends relevant information about the second SRQM of the user service for changing the first SRQM to the policy control device 104.

[0297] Specifically, the charging processing device 101 sends a notification message (also called a change notification) to the policy control device 104, and the notification message carries relevant information about the second quota management mode of the user service, that is, relevant information about the second SRQM of the user service.

[0298] The charging processing device 101 determines that there is a resource created by the policy control device 104 for the user, and sends a notification message to the policy control device 104 through the notification address corresponding to the resource. The resource created for the user is: the resource that the policy control device 104 requests the charging processing device 101 to create for the user. The resource created for the user is used for the policy control device to obtain (subscribe to) the cumulative status information of the user. The resource created for the user is created by the charging processing device according to the resource creation request after the policy control device sends a resource creation request to the charging processing device. The resource creation request carries the notification address corresponding to the resource and the user identification. This notification address is used for the charging processing device 101 to notify the policy control device 104 of the cumulative status information of the user. Based on the determined existence of the resource requested to be created for the user, the charging processing device 101 determines that it is necessary to send a notification message of the second SRQM-related information of the user service to the policy control device 104. Or, based on the determined existence of the resource (or subscription information) requested to be created for the user, if the charging processing device 101 determines that the policy control device 104 has subscribed to or requested the first SRQM-related information of the user, it determines that it is necessary to send a notification message of the second SRQM-related information of the user service to the policy control device 104.

[0299] The relevant information of the second SRQM of the user service carried in the notification message can be as shown in the following table:

[0300] First Notice List of Services Allowed for the User to Suspend Quota Management Second Notice Indication Information on Whether to Allow Suspension of the User's Service Quota Management Third Notice Second SRQM Indication Information on Whether to Allow Suspension of the User's Service Quota Management Fourth Notice Indication Information on Whether the Second SRQM of the User's Services is Suspending Quota Management or Starting Quota Management Fifth Notice Indication Information on Whether the Second SRQM of Each Service of the User is Suspending Quota Management or Starting Quota Management

[0301] The notification message containing the first notification can be called the first notification message, and so on. The following is a reference example of the third notification message:

[0302]

[0303] Among them, the userID field represents the user identification. The value of "SRQMode" being "RESUME" means that the charging processing device 101 confirms that the services of this user are not allowed to suspend quota management, that is, all services of this user are not allowed to suspend quota management. If the notification message also carries the user identification, such as service id or Rating group, the notification message is the second notification message. It indicates that the user services indicated by the service id or Rating group are not allowed to suspend quota management. Further, if the relevant information of the second SRQM in the notification message is to start quota management, the notification message can also carry the information of IQRM to indicate that the user service can adopt the blocking mode or the non-blocking mode.

[0304] For other notification messages, such as reference examples of the first notification message, the fourth notification message or the fifth notification message, the embodiments of the present application will not give examples here.

[0305] Step 556: After receiving the relevant information on the second quota management mode of the user service sent by the charging processing device 101, the policy control device 104 determines the second quota management mode of the user service according to the relevant information on the second quota management mode, and generates a second policy for the user service.

[0306] The second policy is used to update or replace the first policy, and to indicate the execution of the second quota management mode for the user service.

[0307] Specifically, the second policy updates the first policy as follows: The generated second policy includes a policy identifier that is the same as the identifier of the first policy, and it is determined through the identifier that it is used to update the first policy.

[0308] Specifically, the second policy replaces the first policy as follows: A unique policy identifier is assigned to the second policy. The second policy is a new policy for the user service that is different from the first policy. The policy control device 104 needs to first deactivate the first policy and then install and activate the second policy.

[0309] Before generating the second policy, the policy control device 104 needs to first determine that the change of the user service's SRQM to the second quota management mode affects the first policy.

[0310] Step 557: The policy control device 104 sends the second policy to the session management function device 102.

[0311] Specifically, if the second policy includes a policy identifier that is the same as the identifier of the first policy, the policy control device 104 carries the second policy in the policy update message sent to the session management function to update the first policy of the user service.

[0312] If the second policy is a new policy for the user service, the policy control device 104 carries a deactivation instruction for the first policy and an activation instruction for the second policy in the policy update message sent to the session management function, so as to use the second policy to update the first policy of the user service.

[0313] According to the embodiments of the present application, the charging processing device 101 can determine or change the SRQM of the user service according to information such as the user's account information. Thus, the control of the user service's SRQM is more accurate, and the risks and losses caused by blindly suspending quota management during the use of the user service can be avoided.

[0314] It should be noted that during the actual business use process, Figure 5A can be used in combination with Figure 5B or separately. The embodiments of the present application do not make any limitations in this regard.

[0315] Figure 6Another flowchart of the method for determining the quota management mode of user services provided by the embodiments of the present application. In this embodiment, the quota management mode is Suspend / Resume Quota Management (SRQM). Different from the corresponding embodiments of Figure 5A and Figure 5B , in this embodiment, the policy control device 104 determines the first quota management mode of the user service according to the obtained configuration information of the user, that is, determines whether the user service allows suspension of quota management. The charging processing device 101 makes a real-time decision on whether to change the first quota management mode of the user service to the second quota management mode. The method process mainly includes the following steps:

[0316] Steps 601-602: The policy control device 104 sends a resource creation request to the charging processing device 101 and receives a resource creation response from the charging processing device 101.

[0317] In this embodiment, the descriptions of steps 601-602 are the same as those of steps 401-402, so they will not be elaborated here.

[0318] Step 603: The policy control device 104 determines the first quota management mode of the user service (the first SRQM in the present application) according to the obtained information and generates the first policy of the user service. The first policy is used to indicate the execution of the first quota management mode for the user service. For example, the policy control device 104 can obtain the configuration information of the user from the charging processing device 101 or other network devices such as (UDR), and determine the first SRQM of the user service based on the obtained configuration information of the user. For example, the policy control device 104 can determine the first SRQM of the user service according to the information of the user account and / or the usage information of the user service obtained from the charging processing device 101. The policy control device 104 can also determine the information of the user according to the information obtained from the UDR, such as whether the user subscribes to the SRQM as suspension of quota management.

[0319] The first policy generated by the policy control device 104 in step 603 is the same as the first policy generated in step 508, and will not be elaborated in the embodiments of the present application.

[0320] Step 604: The policy control device 104 sends the generated first policy of the user service to the session management function device 102.

[0321] For the specific description of step 604, reference can be made to the description of step 510, and it will not be elaborated in the embodiments of the present application.

[0322] Step 605: The session management function device 102 receives a start request for the user service, and the start request for the user service carries a service identifier and a user identifier.

[0323] Specifically, for the description of step 605, reference can be made to the description of step 351, which will not be elaborated in the embodiments of the present application. As an option, the embodiments of the present application may also not execute step 605 but execute step 606. Alternatively, step 605 is executed before step 601. The embodiments of the present application do not make any limitations in this regard.

[0324] Step 606, the session management function device 102 sends a charging request to the charging processing device 101. The charging request may be a charging request for the user service or a charging request for other services used by the user. In addition, the charging request may be an initial charging request (i.e., the first charging request for a certain service used by the user) or an updated charging request after the initial charging request. The embodiments of the present invention do not make any limitations in this regard.

[0325] Furthermore, the first SRQM information of the user service is carried in the charging request to indicate the SRQM currently used by the user service (such as service B). The embodiments of the present application take the first SRQM of the user service as the suspended quota management as an example for illustration. That is, the first SRQM information of user service B carried in the charging request is the suspended quota management. It indicates that the session management function device 102 will not apply for a quota from the charging processing device 101 during the execution of the service and release the data stream related to user service B.

[0326] Step 607, the charging processing device 101 performs corresponding charging processing according to the charging request, and then sends a charging response to the session management function device 102.

[0327] Step 608, the charging processing device 101 determines to change the first SRQM of the user service or disable the suspended quota management of the user service, and saves the information of the changed second SRQM.

[0328] Specifically, during the execution of step 607, the charging processing device 101 determines that the user service uses the suspended quota management (Suspending) according to the first SRQM information of the user service carried in the charging request. When the charging processing device 101 determines that the user account does not meet the conditions for the user service to adopt the suspended quota management, it determines that the second quota management mode (the second SRQM in this embodiment) of the user service is to start the quota management or prohibits the user service from using the suspended quota management. The conditions for the user service to adopt the suspended quota management may be: the remaining amount of the user account package is greater than the first threshold, or the balance decline rate of the user account is lower than the second threshold, or others.

[0329] Further, when the charging processing device 101 determines to change the suspended quota management of the user service to the startup quota management, it may also determine to change the suspended quota management of other services of the user to the startup quota management, or determine to prohibit other services of the user from using the suspended quota management, or prohibit all services of the user from using the suspended quota management.

[0330] It should be noted that there is no time sequence between step 607 and step 608.

[0331] Step 609: The charging processing device 101 sends a notification message (also called a change notification) of the relevant information of the first SRQM of the changed user service to the policy control device 104, so that the policy control device 104 can generate or update the control policy of the user service according to the change notification.

[0332] Specifically, the description of step 609 is the same as that of step 555, and the embodiments of the present invention will not be described in detail here.

[0333] Steps 610-611 are the same as the descriptions of steps 556-557, and the embodiments of the present invention will not be described in detail here.

[0334] According to the embodiments of the present application, the policy control device 104 determines whether the user service can use the non-blocking mode according to the obtained relevant information of the user. In addition, during the use of the user service, the SRQM of the user service is determined or changed according to the account information of the user. Thus, the SRQM of the user service is more accurate, and the risks and losses caused by using the non-blocking mode during the use of the user service can be avoided.

[0335] Figure 7 This is the hardware structure diagram of the session management function device, the charging processing device 101 or the policy control device 104 provided by the embodiments of the present application. The session management function device 102 (for example, 102 in FIG. 1), the charging processing device 101 (for example, 101 in FIG. 1), and the policy control device 104 (for example, the policy control device 104 in FIG. 1) in the embodiments of the present application can all adopt Figure 7 the shown general computer hardware structure, which includes a processor 701, a memory 702, a bus 703, an input device 704, an output device 705, and a network interface 706, where the input device 704 and the output device 705 are optional.

[0336] Specifically, the memory 702 may include computer storage media in the form of volatile and / or non-volatile memories, such as read-only memories and / or random access memories. The memory 702 may store an operating system, application programs, other program modules, executable code, and program data.

[0337] The input device 704 can be used to input information to facilitate the system administrator to operate and manage the session management function device, the charging processing device 101, or the policy control device 104, etc. For example, configure the user account risk threshold on the charging processing device 101, manage the storage space of the quota management mode indication information on the session management function device, manage the storage space of the quota management mode indication information on the policy control device 104, etc.; the input device 704 can be a keyboard or a pointing device, such as a mouse, a trackball, a touchpad, a scanner, or similar devices, all of which can be connected to the processor 701 through the bus 703.

[0338] The output device 705 can be used to output information to facilitate the system administrator to operate and manage the session management function device, the charging processing device 101, or the policy control device 104, etc.; for example, display the user account risk threshold on the charging processing device 101, display the remaining storage space on the session management function device, display the remaining storage space on the policy control device 104, etc.; in addition to the monitor, the output device 705 can also be other peripheral output devices, all of which can also be connected to the processor 701 through the bus 703.

[0339] The session management function device 102, the charging processing device 101, or the policy control device 104 can all be connected to the network through the network interface 706, for example, connected to a Local Area Network (LAN). In a networked environment, the computer-executable instructions stored in the session management function device, the charging processing device 101, or the policy control device 104 can be stored in a remote storage device, rather than being limited to local storage.

[0340] When the processor 701 in the session management function device 102 executes the executable code or application program stored in the memory 702, the session management function device 102 can execute the method steps corresponding to the session management function device 102 in all the above embodiments, such as steps 206, 310, 351, 332 - 353, 357, 404, 405, 406 - 407, 411, 310, 351, 332 - 353, 357, 604, 605, 606 - 607, and 611, etc.; the specific execution process can be referred to the above embodiments and will not be elaborated here.

[0341] When the processor 701 in the charging processing device 101 executes the executable code or application program stored in the memory 702, the charging processing device 101 may execute the method steps corresponding to the charging processing device 101 in all the above embodiments, such as steps 208, 302, 304, 306, 352 - 355, 401 - 402, 406 - 409, 502, 504, 506, 552 - 555, 601 - 602, and 606 - 609; for the specific execution processes, please refer to the above embodiments and will not be elaborated here.

[0342] When the processor 701 in the policy control device 104 executes the executable code or application program stored in the memory 702, the policy control may execute the method steps corresponding to the policy control device 104 in all the above embodiments, such as steps 202 - 212, 300 - 302, 306 - 310, 355 - 357, 401 - 404, 409 - 411, 500 - 502, 506 - 510, 555 - 557, 5501 - 504, and 509 - 511; for the specific execution processes, please refer to the above embodiments and will not be elaborated here.

[0343] It should be noted that some of the above steps are executed by two devices because one device sends and the other device receives. For example, in step 206, the policy control device 104 sends the first policy, and the session management function device 102 receives the first policy.

[0344] Figure 8 The figure is a schematic logical structure diagram of the charging processing device 101 provided by the embodiments of the present application. The charging processing device 101 is used to determine a first quota management mode for changing a user service and send a notification message to the policy control device 104. The notification message carries information related to a second quota management mode of the user service, and the second quota management mode is used to change the first quota management mode. The charging processing device 101 includes:

[0345] - A processing module 802, configured to determine a first quota management mode for changing a user service. The processing module 802 is mainly used to execute steps such as processing and determining in the charging processing device 101 in the above embodiments, such as steps 208, 304, 354, 408, 504, 554, and 608.

[0346] A sending module 803, configured to send a notification message to a policy control device 104, where the notification message carries information related to a second quota management mode of a user service, and the second quota management mode is used to change a first quota management mode. The sending module 803 is mainly configured to execute the sending steps on the side of the charging processing device 101 in the foregoing embodiments, such as steps 208, 306, 353, 355, 402, 407, 409, 506, 553, 555, 602, 607, and 609, etc.

[0347] In addition, the charging processing device 101 further includes a receiving module 801, configured to receive a request message sent by the policy control device 104. The receiving module 801 is mainly configured to execute the receiving steps on the side of the charging processing device 101 in the foregoing embodiments, such as steps 302, 352, 401, 406, 502, 552, 601, and 606, etc.

[0348] Figure 9 The figure is a schematic logical structure diagram of a policy control device 104 (104) provided in an embodiment of the present application. The policy control device 104 (104) is configured to determine a policy for a user service. The policy control device 104 (104) includes:

[0349] A receiving module 901, configured to receive information related to a second quota management mode of a user service for changing a first quota management mode, sent by the charging processing device 101. The receiving module 901 is mainly configured to execute the receiving steps of the policy control device 104 in the foregoing embodiments, such as steps 208, 306, 355, 402, 409, 506, 555, 602, and 609, etc.

[0350] A processing module 902, configured to determine a first quota management mode of a user service, generate a first policy for the user service according to the first quota management mode, and determine a second quota management mode according to the information related to the second quota management mode of the user service, and generate a second policy for the user service according to the second quota management mode, where the second policy is used to update or replace the first policy. The processing module 902 is mainly configured to execute the steps of determining, processing, and generating a policy of the policy control device 104 in the foregoing examples, such as steps 202-204, 210-212, 304, 354, 403, 410, 504, 554, 603, and 610, etc.

[0351] A sending module 903, configured to send a first policy to a session management function device 102 to instruct the session management function device 102 to perform a first quota management mode on user services. The sending module 903 is mainly used to execute steps such as sending by the policy control device 104 in the above-mentioned examples, such as steps 206, 302, 310, 357, 401, 404, 411, 502, 510, 557, 601, 604, and 611, etc.

[0352] Figure 8 The shown charging processing device 101 and Figure 9 The shown policy control device 104 is presented in the form of functional modules. Here, "module" may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and a memory that execute one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can think that these devices can also be in Figure 6 the form shown. For example, the receiving module 801, the processing module 802, the sending module 803, the receiving module 901, the processing module 802, and the sending module 903 can all be implemented by Figure 6 the processor 701 and the memory 702 in. For example, it is implemented by the processor 701 executing the code stored in the memory 702.

[0353] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the components and steps of the examples have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0354] Those of ordinary skill in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0355] In several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the division of units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Additionally, the displayed or discussed couplings or direct couplings or communication connections to each other can be indirect couplings or communication connections through some interfaces, devices, or units, and can also be electrical, mechanical, or other forms of connections.

[0356] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the objectives of the embodiments of the present application.

[0357] Furthermore, in each embodiment of the present application, the functional units can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0358] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, 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. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in each embodiment of the present application. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read-only memories, random access memories, magnetic disks, or optical discs, etc., which can store program codes.

[0359] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present application can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A user service processing method, characterized in that, Including: The policy control device generates a first policy for the user's service and sends the first policy to the session management function device, and the first policy indicates to execute a first quota management mode for the user service; The policy control device receives the relevant information of the second quota management mode of the user or the user service for changing the first quota management mode sent by the charging processing device, and determines to execute the second quota management mode for the user service according to the relevant information of the second quota management mode of the user or the user service; The policy control device generates a second policy for the user service and sends the second policy to the session management function device to update or replace the first policy, and the second policy indicates to execute the second quota management mode for the user service; The first quota management mode is a first initial quota application mode, the second quota management mode is a second initial quota application mode, the first initial quota application mode is a blocking mode and the second initial quota application mode is a non-blocking mode, or, the first initial quota application mode is a non-blocking mode and the second initial quota application mode is a blocking mode; or, The first quota management mode is suspended quota management and the second quota management mode is enabled quota management, or, the first quota management mode is enabled quota management and the second quota management mode is suspended quota management.

2. The method according to claim 1, wherein The method further includes: The policy control device receives the relevant information of the first quota management mode of the user or the user service sent by the charging processing device; The policy control device determines the first quota management mode of the user service according to the relevant information of the first quota management mode of the user or the user service.

3. The method according to claim 1, characterized in that The method further includes: The policy control device sends a request message to the charging processing device; The policy control device receives a response message sent by the charging processing device, and the response message carries the relevant information of the first quota management mode of the user or the user service; The policy control device determines the first quota management mode of the user service according to the relevant information of the first quota management mode of the user or the user service.

4. According to the method described in claim 3, the first quota management mode is a first initial quota application mode, and the request message further carries an indication for obtaining the first quota management mode, characterized in that: The indication is the identification of the user and the indication information for obtaining the service list of the non-blocking mode of the user, and the relevant information of the first quota management mode carried by the response message is the service list of the first initial quota application mode that allows the user to use the non-blocking mode; or The indication is the identification of the user service and the indication information for obtaining whether the user service is allowed to use the first initial quota application mode of the non-blocking mode, and the relevant information of the first quota management mode carried by the response message is the indication information for whether the user service is allowed to use the first initial quota application mode of the non-blocking mode; or The obtaining instruction is the identification of the user and the instruction information for obtaining whether to allow the services of the user to use the non-blocking first initial quota application mode, and the related information of the first quota management mode carried in the response message is the instruction information for whether to allow the services of the user to use the non-blocking first initial quota application mode; or The obtaining instruction is the identification of the user service and the instruction information for obtaining the first initial quota application mode of the user service, and the related information of the first quota management mode carried in the response message is the first initial quota application mode of the user service, and the first initial quota application mode is a blocking mode or a non-blocking mode; or The obtaining instruction is the identification of the user and the instruction information for obtaining the first initial quota application modes of the services of the user, and the related information of the first quota management mode carried in the response message is the first initial quota application modes of the services of the user, and the first initial quota application mode is a blocking mode or a non-blocking mode.

5. The method according to claim 3 or 4, wherein the first quota management mode is to suspend or enable quota management, and the request message further carries an obtaining instruction for the first quota management mode, and is characterized in that: The obtaining instruction is the identification of the user and the instruction information for obtaining the service list of the user allowed to suspend quota management, and the related information of the first quota management mode carried in the response message is the service list of the user allowed to suspend quota management; or The obtaining instruction is the identification of the user service and the instruction information for obtaining whether to allow the user service to suspend quota management, and the related information of the first quota management mode carried in the response message is the instruction information for whether to allow the quota management of the user service to be suspended; or The obtaining instruction is the identification of the user and the instruction information for obtaining whether to allow the quota management of the services of the user to be suspended, and the related information of the first quota management mode carried in the response message is the instruction information for whether to allow the quota management of the services of the user to be suspended; or The obtaining instruction is the identification of the user service and the instruction information for obtaining the first quota management mode of the user service, and the related information of the first quota management mode carried in the response message is the first quota management mode of the user service, and the first quota management mode is to suspend quota management or enable quota management; or The obtaining instruction is the identification of the user and the instruction information for obtaining the quota management modes of the services of the user, and the related information of the first quota management mode carried in the response message is the information of the first quota management modes of the services of the user, and the first quota management mode is to suspend quota management or start quota management.

6. The method according to claim 3, and is characterized in that: The related information of the first quota management mode of the user or the user service is: the instruction information for whether to allow the services of the user to use the non-blocking mode, or the instruction information for whether to allow the quota management of the services of the user to be suspended.

7. The method according to any one of claims 1-4, 6, and is characterized in that If the first quota management mode is the first initial quota application mode, the first policy includes an indication of the first initial quota application mode, and the first initial quota application mode is a non-blocking mode or a blocking mode; or, If the first quota management mode of the user service is suspended quota management, the first policy includes that the charging method of the user service is offline charging or temporary offline charging; Or If the first quota management mode of the user service is enabled quota management, the first policy includes that the charging method of the user service is online charging.

8. The method according to any one of claims 1-4 and 6, characterized in that The relevant information of the second quota management mode for changing the first quota management mode sent by the charging processing device received by the policy control device includes: The policy control device receives a notification message sent by the charging processing device for the user or the user service, and the notification message carries the relevant information of the second quota management mode of the user service.

9. The method according to claim 8, wherein The first quota management mode is the first initial quota application mode of the blocking mode or the non-blocking mode, and the relevant information of the second quota management mode of the user service includes: The service list of the user allowed to use the non-blocking second initial quota application mode; or The indication information of whether to allow the user's service to use the non-blocking second initial quota application mode; or The indication information of whether to allow the user service to use the non-blocking second initial quota application mode; or The second initial quota application mode of the user service.

10. The method according to claim 8, wherein The first quota management mode is suspended or enabled quota management, and the relevant information of the second quota management mode of the user service includes: The service list of the user allowed to suspend quota management; or The indication information of whether to allow the quota management of the user service to be suspended; or The indication information of whether to allow the quota management of the user's service to be suspended; or The quota management mode of the user service for suspension or enabled quota management.

11. The method according to claim 8, characterized in that, The policy control device saves the second quota management mode of the user service.

12. The method according to claim 8, wherein If the second quota management mode is the second initial quota application mode, the second policy includes the second initial quota application mode of the user service, and the second initial quota application mode is a blocking mode or a non-blocking mode; or, If the second quota management mode of the user service is suspended quota management, the second policy includes that the charging method of the user service is offline charging or temporary offline charging; Or, If the second quota management mode of the user service is enabled quota management, the charging method of the user service included in the second policy is online charging.

13. A user service processing method, applied to a charging processing device, characterized in that Including: Determine that it is necessary to change the first quota management mode of the user service of the user to the second quota management mode; Send a notification message to the policy control device, and the notification message carries the relevant information of the second quota management mode of the user or the user service; The first quota management mode is the first initial quota application mode, the second quota management mode is the second initial quota application mode, the first initial quota application mode is a blocking mode and the second initial quota application mode is a non-blocking mode, or the first initial quota application mode is a non-blocking mode and the second initial quota application mode is a blocking mode; or, The first quota management mode is suspended quota management and the second quota management mode is enabled quota management, or the first quota management mode is enabled quota management and the second quota management mode is suspended quota management.

14. The method according to claim 13, wherein It further includes: When processing the charging request of the user service, or processing the charging request of other services of the user, or performing a charging management process on the user account, it is determined that the first quota management mode of the user service needs to be changed.

15. The method according to claim 13 or 14, characterized in that, The charging processing device determines that the first quota management mode of the user service needs to be changed to the second quota management mode, including: Receiving the charging request of the user service, where the charging request includes indication information of the user service using the first quota management mode; Based on the indication information of the first quota management mode, it is determined that the first quota management mode of the user service needs to be changed to the second quota management mode; Or, The charging processing device determines that relevant information of the first quota management mode of the user service has been sent to the policy control device; Based on the first quota management mode, the charging processing device determines to change the first quota management mode of the user service to the second quota management mode.

16. The method according to claim 13 or 14, characterized in that The first quota management mode is the first initial quota application mode of a blocking mode or a non-blocking mode, and the relevant information of the second quota management mode for changing the first quota management mode includes: An updated service list of the user allowing the use of the second initial quota application mode of the non-blocking mode; or An updated indication information on whether to allow the user's service to use the second initial quota application mode of the non-blocking mode; or An updated indication information on whether to allow the user service to use the second initial quota application mode of the non-blocking mode; or An updated second initial quota application mode of the user service.

17. The method according to claim 13 or 14, characterized in that The first quota management mode is suspended or enabled quota management, and the relevant information of the second quota management mode for changing the first quota management mode includes: An updated service list of the user allowing suspended quota management; or An updated indication information on whether to allow the quota management of the user service to be suspended; or An updated indication information on whether to allow the quota management of the user's service to be suspended; or An updated quota management mode of the user service for suspended or enabled quota management.

18. The method according to claim 13 or 14, characterized in that The charging processing device saves the second quota management mode of the user service.

19. The method according to claim 13 or 14, characterized in that, The method further includes: The charging processing device determines that there are resources created for the user; Sending the notification message to the policy control device includes: sending the notification message to the policy control device through the notification address corresponding to the resource.

20. The method according to claim 13 or 14, characterized in that, Before the method, it further includes: Receive the request message sent by the policy control device; Send a response message to the policy control device, where the response message carries information related to the first quota management mode of the user or the user service.

21. The method according to claim 20, wherein the first quota management mode is a blocking mode or a first initial quota application mode of a non-blocking mode, and the request message further carries an indication for obtaining the first quota management mode. The method is characterized in that: The indication for obtaining is the identification of the user and the indication information for obtaining the service list of the non-blocking mode of the user, and the information related to the first quota management mode carried in the response message is the service list of the first initial quota application mode of the non-blocking mode allowed for the user; or The indication for obtaining is the identification of the user service and the indication information for obtaining whether the user service is allowed to use the first initial quota application mode of the non-blocking mode, and the information related to the first quota management mode carried in the response message is the indication information for whether the user service is allowed to use the first initial quota application mode of the non-blocking mode; or The indication for obtaining is the identification of the user and the indication information for obtaining whether the service of the user is allowed to use the first initial quota application mode of the non-blocking mode, and the information related to the first quota management mode carried in the response message is the indication information for whether the service of the user is allowed to use the first initial quota application mode of the non-blocking mode; or The indication for obtaining is the identification of the user service and the indication information for obtaining the first initial quota application mode of the user service, and the information related to the first quota management mode carried in the response message is the first initial quota application mode of the user service, and the first initial quota application mode is a blocking mode or a non-blocking mode; or The indication for obtaining is the identification of the user and the indication information for obtaining the first initial quota application mode of each service of the user, and the information related to the first quota management mode carried in the response message is the first initial quota application mode of each service of the user, and the first initial quota application mode is a blocking mode or a non-blocking mode.

22. The method according to claim 20, wherein the first quota management mode is to suspend or enable quota management, and the request message further carries an indication for obtaining the first quota management mode. The method is characterized in that: The indication for obtaining is the identification of the user and the indication information for obtaining the service list of the user allowed to suspend quota management, and the information related to the first quota management mode carried in the response message is the service list of the user allowed to suspend quota management; or The indication for obtaining is the identification of the user service and the indication information for obtaining whether the user service is allowed to suspend quota management, and the information related to the first quota management mode carried in the response message is the indication information for whether the quota management of the user service is allowed to be suspended; or The obtaining instruction is the identification of the user and the instruction information for obtaining quota management for suspending the user's service. The relevant information of the first quota management mode carried in the response message is the instruction information for quota management for suspending the user's service; or The obtaining instruction is the identification of the user service and the instruction information for obtaining the first quota management mode of the user service. The relevant information of the first quota management mode carried in the response message is the first quota management mode of the user service, and the first quota management mode is suspension quota management or enabling quota management; or The obtaining instruction is the identification of the user and the quota management modes of the user's respective services. The relevant information of the first quota management mode carried in the response message is the information of the first quota management modes of the user's respective services, and the first quota management mode is suspension quota management or activation quota management.

23. The method according to claim 20, wherein: The relevant information of the first quota management mode of the user or the user service is: the instruction information on whether to allow the user's service to use the non-blocking mode, or the instruction information on whether to allow quota management for suspending the user's service.

24. A policy control device, characterized in that It includes: A processing module is used to generate a first policy for the user service of the user; A sending module is used to send the first policy to a session management function device, and the first policy indicates to execute a first quota management mode for the user service; A receiving module is used to receive the relevant information of the second quota management mode of the user or the user service sent by a charging processing device for changing the first quota management mode; The processing module is further used to determine to execute a second quota management mode for the user service according to the relevant information of the second quota management mode of the user or the user service, and generate a second policy for the user service; The sending module is further used to send the second policy to the session management function device to update or replace the first policy, and the second policy also indicates to execute the second quota management mode for the user service; The first quota management mode is a first initial quota application mode, the second quota management mode is a second initial quota application mode, the first initial quota application mode is a blocking mode and the second initial quota application mode is a non-blocking mode, or the first initial quota application mode is a non-blocking mode and the second initial quota application mode is a blocking mode; or The first quota management mode is suspension quota management and the second quota management mode is enabling quota management, or the first quota management mode is enabling quota management and the second quota management mode is suspension quota management.

25. The policy control device according to claim 24, wherein The receiving module is further used to receive the relevant information of the first quota management mode of the user or the user service sent by the charging processing device; The processing module determines that the first quota management mode of the user service is: the processing module determines the first quota management mode of the user service according to the relevant information of the first quota management mode of the user or the user service.

26. The policy control device according to claim 24 or 25, characterized in that The sending module is further configured to send a request message to the charging processing device; The receiving module receives a response message sent by the charging processing device, and the response message carries the relevant information of the first quota management mode of the user or the user service.

27. The policy control device according to claim 24 or 25, characterized in that The relevant information of the second quota management mode for changing the first quota management mode received by the receiving module from the charging processing device includes: the receiving module receives a notification message sent by the charging processing device for the user or the user service, and the notification message carries the relevant information of the second quota management mode of the user service.

28. A billing processing device, characterized in that, Including: A processing module, configured to determine that it is necessary to change the first quota management mode of the user service of the user to a second quota management mode; A sending module, which sends a notification message to the policy control device, and the notification message carries the relevant information of the second quota management mode of the user or the user service; The first quota management mode is a first initial quota application mode, the second quota management mode is a second initial quota application mode, the first initial quota application mode is a blocking mode and the second initial quota application mode is a non-blocking mode, or, the first initial quota application mode is a non-blocking mode and the second initial quota application mode is a blocking mode; or The first quota management mode is suspended quota management and the second quota management mode is enabled quota management, or the first quota management mode is enabled quota management and the second quota management mode is suspended quota management.

29. The charging processing device according to claim 28, characterized in that The charging processing device further includes a receiving module, configured to receive a charging request for a user service, where the charging request includes indication information of using the first quota management mode for the user service; the processing module is further configured to determine, based on the indication information of the first quota management mode, that it is necessary to change the first quota management mode of the user service to a second quota management mode; or The processing module is further configured to determine that the relevant information of the first quota management mode of the user service has been sent to the policy control device, and based on the first quota management mode, determine that it is necessary to change the first quota management mode of the user service to a second quota management mode.

30. The charging processing device according to claim 28 or 29, characterized in that The processing module further determines that there are resources created for the user; The sending module sending the notification message to the policy control device includes: sending the notification message to the policy control device through a notification address corresponding to the resource.

31. The charging processing device according to claim 28 or 29, characterized in that the charging processing device further comprises a receiving module, configured to receive a request message sent by the policy control device; the sending module is further configured to send a response message to the policy control device, and the response message carries information related to the first quota management mode of the user or the user service.

32. A charging processing device (101), characterized in that, comprising a processor and a memory, wherein: the memory is configured to store program instructions; the processor is configured to call and execute the program instructions stored in the memory, so that the charging processing device (101) executes the user service processing method according to any one of claims 13 to 23.

33. A session management function device (102), characterized in that, comprising a processor and a memory, wherein: the memory is configured to store program instructions; the processor is configured to call and execute the program instructions stored in the memory, so that the session management function device (102) executes the user service processing method according to any one of claims 1 to 12.

34. A system, characterized in that, comprising a policy control device for executing any one of claims 24-27, and a charging processing device for executing any one of claims 28-32.

35. A user service processing method, characterized in that, comprising: The policy control device determines the first quota management mode of the user service; The policy control device generates a first policy for the user service according to the first quota management mode, and sends the first policy to the session management function device, and the first policy indicates to execute the first quota management mode for the user service; The charging processing device sends information related to the second quota management mode of the user service for changing the first quota management mode to the policy control device; The policy control device determines to execute the second quota management mode for the user service according to the information related to the second quota management mode of the user service; The policy control device generates a second policy for the user service according to the second quota management mode, and sends the second policy to the session management function device to update or replace the first policy, and the second policy indicates to execute the second quota management mode for the user service; The first quota management mode is a first initial quota application mode, the second quota management mode is a second initial quota application mode, the first initial quota application mode is a blocking mode and the second initial quota application mode is a non-blocking mode, or, the first initial quota application mode is a non-blocking mode and the second initial quota application mode is a blocking mode; or, The first quota management mode is suspended quota management and the second quota management mode is enabled quota management, or, the first quota management mode is enabled quota management and the second quota management mode is suspended quota management.

Images