1. Patent Search
  2. Details

USER SERVICE PROCESSING METHOD, SYSTEM, AND RELATED DEVICE

20230109543 · 2023-04-06

    Inventors

    Cpc classification

    International classification

    Abstract

    A service processing method and a related product is applied to the charging field. A policy control device generates a first policy of a user service, and sends the first policy to a session management function device to indicate the session management function device to perform a first quota management mode on the user service. The policy control device receives related information of a second quota management mode of a user or the user service, and determines the second quota management mode. The policy control device generates a second policy of the user service based on the second quota management mode, where the second policy is for updating or replacing the first policy. According to this method, the quota management mode of the user service is time-effective, ensuring a balance between a latency condition and credit control risks.

    Claims

    1. A user service processing method, comprising: generating, by a policy control device, a first policy of a user service of a user, and sending the first policy to a session management function device, wherein the first policy indicates whether to perform a first quota management mode on the user service; receiving, by the policy control device, related information, from a charging processing device and that is usable for changing the first quota management mode, of a second quota management mode of the user or the user service determining, by the policy control device, the second quota management mode of the user service based on the related information of the second quota management mode of the user or the user service; and generating, by the policy control device, a second policy of the user service, wherein the second policy is usable for updating or replacing the first policy and for indicating whether to perform the second quota management mode on the user service.

    2. The method according to claim 1, wherein the first quota management mode includes a first initial quota request mode, the second quota management mode includes a second initial quota request mode, the first initial quota request mode includes a blocking mode, and the second initial quota request mode includes a non-blocking mode; or the first initial quota request mode includes a non-blocking mode, and the second initial quota request mode includes a blocking mode; or the first quota management mode includes suspend quota management and the second quota management mode includes resume quota management; or the first quota management mode includes resume quota management and the second quota management mode includes suspend quota management.

    3. The method according to claim 1, wherein the method further comprises: receiving, by the policy control device, related information of the first quota management mode of the user or the user service, wherein the related information of the first quota management mode is received from the charging processing device; and determining, by the policy control device, the first quota management mode of the user service based on the related information of the first quota management mode of the user or the user service.

    4. The method according to claim 1, wherein the method further comprises: sending, by the policy control device, a request message to the charging processing device; receiving, by the policy control device, a response message from the charging processing device, wherein the response message carries related information of the first quota management mode of the user or the user service; and determining, by the policy control device, the first quota management mode of the user service based on the related information of the first quota management mode of the user or the user service.

    5. The method according to claim 4, wherein the first quota management mode is-includes the first initial quota request mode, and the request message further carries an obtaining indication for the first quota management mode, wherein the obtaining indication includes an identifier of the user and indication information for obtaining a service list in the non-blocking mode of the user, and the related information of the first quota management mode carried in the response message includes a list of services of the user that are allowed to use the first initial quota request mode in the non-blocking mode; or the obtaining indication includes an identifier of the user service and indication information for obtaining whether a user service is allowed to use the first initial quota request mode in the non-blocking mode, and the related information of the first quota management mode carried in the response message includes indication information of whether the user service is allowed to use the first initial quota request mode in the non-blocking mode; or the obtaining indication includes an identifier of the user and indication information for obtaining whether a service of the user is allowed to use the first initial quota request mode in the non-blocking mode, and the related information of the first quota management mode carried in the response message includes indication information of whether the service of the user is allowed to use the first initial quota request mode in the non-blocking mode; or the obtaining indication includes an identifier of the user service and indication information for obtaining the first initial quota request mode of the user service, the related information of the first quota management mode carried in the response message includes the first initial quota request mode of the user service, and the first initial quota request mode includes the blocking mode or the non-blocking mode; or the obtaining indication includes an identifier of the user and indication information for obtaining a first initial quota request mode of services of the user, the related information of the first quota management mode carried in the response message includes the first initial quota request mode of the services of the user, and the first initial quota request mode includes the blocking mode or the non-blocking mode.

    6. The method according to claim 4, wherein the first quota management mode includes suspend or resume quota management, and the request message further carries an obtaining indication for the first quota management mode, wherein the obtaining indication includes an identifier of the user and indication information for obtaining a service list that allows suspend quota management and that is of the user, and the related information of the first quota management mode carried in the response message is includes a service list that allows suspend quota management and that is of the user; or the obtaining indication includes an identifier of the user service and indication information for obtaining whether a user service allows suspend quota management, and the related information of the first quota management mode carried in the response message is includes indication information of whether quota management of the user service is allowed to be suspended; or the obtaining indication includes an identifier of the user and indication information for obtaining whether quota management of a service of the user is allowed to be suspended, and the related information of first quota management mode carried in the response message includes indication information of whether quota management of the service of the user is allowed to be suspended;or the obtaining indication includes an identifier of the user service and indication information for obtaining the first quota management mode of the user service, the related information of the first quota management mode carried in the response message includes the first quota management mode of the user service, and the first quota management mode includes suspend quota management or resume quota management; or the obtaining indication includes an identifier of the user and indication information for obtaining quota management modes of services of the user, the related information of the first quota management mode carried in the response message includes information about the first quota management mode of the services of the user, and the first quota management mode includes suspend quota management or resume quota management.

    7. The method according to claim 4, wherein the related information of the first quota management mode of the user or the user service is: indication information indicating whether the service of the user is allowed to use the non-blocking mode, or indication information indicating whether quota management of a service of the user is allowed to be suspended.

    8. The method according to claim 1, wherein the receiving, by the policy control device, related information of a second quota management mode from a charging processing device and that is for changing the first quota management mode includes: receiving, by the policy control device, a notification message for the user or the user service, wherein the notification message is received from the charging processing device, and carries related information of the second quota management mode of the user service.

    9. A user service processing method, comprising: determining, by a charging processing device, that a first quota management mode of a user service of a user is to be changed to a second quota management mode; and sending, by the charging processing device, a notification message to a policy control device, wherein the notification message carries related information of the second quota management mode of the user or the user service.

    10. The method according to claim 9, wherein the first quota management mode includes a first initial quota request mode, the second quota management mode includes a second initial quota request mode, the first initial quota request mode includes a blocking mode, and the second initial quota request mode includes a non-blocking mode; or the first initial quota request mode includes a non-blocking mode, and the second initial quota request mode includes a blocking mode; or the first quota management mode includes suspend quota management and the second quota management mode includes resume quota management; or the first quota management mode includes resume quota management and the second quota management mode includes suspend quota management.

    11. The method according to claim 9, further comprising: in response to processing a charging request of the user service, or processing a charging request of another service of the user, or performing a charging management process on an account of the user, determining that the first quota management mode of the user service is to be changed.

    12. The method according to claim 9, wherein that the charging processing device determines that the first quota management mode of the user service is to be changed to the second quota management mode includes: receiving the charging request of the user service, wherein the charging request includes indication information indicating that the user service uses the first quota management mode; and determining, based on the indication information of the first quota management mode, that the first quota management mode of the user service is to be changed to the second quota management mode; or determining, by the charging processing device, that related information of the first quota management mode of the user service has been sent to the policy control device; and determining, by the charging processing device based on the first quota management mode, to change the first quota management mode of the user service to the second quota management mode.

    13. The method according to claim 9, wherein the first quota management mode includes the first initial quota request mode in the blocking mode or the non-blocking mode, and the related information of the second quota management mode for changing the first quota management mode includes: an updated list of services of the user that are allowed to use the second initial quota request mode in the non-blocking mode; updated indication information indicating whether the service of the user is allowed to use the second initial quota request mode in the non-blocking mode; updated indication information indicating whether the user service is allowed to use the second initial quota request mode in the non-blocking mode; or an updated second initial quota request mode of the user service.

    14. The method according to claim 9, wherein the first quota management mode includes suspend or resume quota management, and the related information of the second quota management mode for changing the first quota management mode includes: an updated service list that allows suspend quota management and that is of the user; updated indication information indicating whether quota management of the user service is allowed to be suspended; updated indication information indicating whether quota management of the service of the user is allowed to be suspended; or an updated quota management mode that is of the user service and that suspends or resumes quota management.

    15. The method according to claim 9, wherein the method further comprises: determining, by the charging processing device, that there is a resource created for the user; and the sending a notification message to a policy control device includes: sending the notification message to the policy control device based on a notification address corresponding to the resource.

    16. The method according to claim 9, wherein the method further comprises: receiving the request message from the policy control device; and sending a response message to the policy control device, wherein the response message carries related information of the first quota management mode of the user or the user service.

    17. The method according to claim 16, wherein the related information of the first quota management mode of the user or the user service is: indication information indicating whether the service of the user is allowed to use the non-blocking mode, or indication information indicating whether quota management of the service of the user is allowed to be suspended.

    18. A user service processing method, comprising: determining, by a policy control device, a first quota management mode of a user service; generating, by the policy control device, a first policy of the user service based on the first quota management mode, and sending the first policy to a session management function device, wherein the first policy indicates whether to perform the first quota management mode on the user service; receiving, by the policy control device from the charging processing device, related information of a second quota management mode of the user service that is for changing the first quota management mode; determining, by the policy control device, the second quota management mode based on the related information of the second quota management mode of the user service; and generating, by the policy control device, a second policy of the user service based on the second quota management mode, wherein the second policy is for updating or replacing the first policy, and indicates whether to perform the second quota management mode on the user service.

    19. The method according to claim 18, wherein the method further comprises: receiving, by the policy control device, related information of the first quota management mode of the user or the user service, wherein the related information of the first quota management mode is received from the charging processing device; and determining, by the policy control device, the first quota management mode of the user service based on the related information of the first quota management mode of the user or the user service.

    20. The method according to claim 18, wherein the method further comprises: sending, by the policy control device, a request message to the charging processing device; receiving, by the policy control device, a response message from the charging processing device, wherein the response message carries related information of the first quota management mode of the user or the user service; and determining, by the policy control device, the first quota management mode of the user service based on the related information of the first quota management mode of the user or the user service.

    Description

    BRIEF DESCRIPTION OF DRAWINGS

    [0049] FIG. 1A is a schematic diagram of a system architecture to which an embodiment of this application is applied;

    [0050] FIG. 1B is a schematic diagram of an architecture of a 5G system to which this application is applied;

    [0051] FIG. 2 is a flowchart of a user service processing method according to an embodiment of this application;

    [0052] FIG. 3A is a flowchart of a method for determining a first quota management mode of a user service by a policy control device according to an embodiment of this application;

    [0053] FIG. 3B is a flowchart of a method for determining, by a charging processing device, to change a first quota management mode of a user service according to an embodiment of this application;

    [0054] FIG. 4 is a flowchart of a method for determining a first quota management mode and a second quota management mode of a user service according to an embodiment of this application;

    [0055] FIG. 5A is a flowchart of another method for determining a first quota management mode of a user service by a policy control device according to an embodiment of this application;

    [0056] FIG. 5B is a flowchart of another method for determining, by a charging processing device, to change a first quota management mode of a user service according to an embodiment of this application;

    [0057] FIG. 6 is a flowchart of another method for determining a first quota management mode and a second quota management mode of a user service according to an embodiment of this application;

    [0058] FIG. 7 is a schematic diagram of a hardware structure of a session management function device, a charging processing device, or a policy control device according to an embodiment of this application;

    [0059] FIG. 8 is a schematic diagram of a logical structure of a charging processing device according to an embodiment of this application; and

    [0060] FIG. 9 is a schematic diagram of a logical structure of a policy control device according to an embodiment of this application.

    DESCRIPTION OF EMBODIMENTS

    [0061] The following describes the technical solutions in embodiments of this application with reference to the accompanying drawings in embodiments of this application. In the descriptions of this application, “/” represents an “or” relationship between associated objects unless otherwise specified. For example, A/B may represent A or B. The term “and/or” in this application indicates an association relationship for describing associated objects and indicates that three relationships may exist. For example, A and/or B may indicate the following three cases: Only A exists, both A and B exist, and only B exists, where A and B may be singular or plural. In addition, in the descriptions of this application, “a plurality of” means two or more than two unless otherwise specified. In addition, to clearly describe the technical solutions in embodiments of this application, words such as “first” and “second” are used in embodiments of this application to distinguish between same items or similar items that have basically the same functions or purposes. A person skilled in the art may understand that the terms such as “first” and “second” do not limit a quantity or an execution sequence, and that the terms such as “first” and “second” do not indicate a definite difference.

    [0062] FIG. 1A is a diagram of an architecture of a charging system according to an embodiment of this application. The charging system is configured to control a session management function device to process a user service, and includes a charging processing device 101, a session management function device 102, a user equipment 103, and a policy control device 104. Main functions of these devices are separately described as follows.

    [0063] The charging processing device 101 is communicatively connected to the session management function device 102 and the policy control device 104. The charging processing device 101 is configured to: receive quota request information, usage information, and the like reported by the session management function device, and perform charging processing on the user service. In addition, the charging processing device 101 determines or changes a quota management mode of a user service based on account information of a user, and sends the quota management mode of the user service to the policy control device 104, or sends the account information of the user to the policy control device 104, so that the policy control device 104 determines the quota management mode of the user service.

    [0064] The charging processing device 101 may be a CHF (Charging Function, charging function) device defined in 3GPP standard specifications, or may be a CCS (Converged Charging System, converged charging system) device defined in the 3GPP standard specifications, and includes functions of a CHF device.

    [0065] It should be understood that, during actual application, the charging system shown in FIG. 1A may have more charging processing devices 101. For example, a cluster may be constructed, including a plurality of charging processing devices 101 which are mutually backed up. This can improve a redundancy capability, and achieve high availability.

    [0066] For ease of description, in embodiments of this application, the charging processing device 101 is sometimes directly referred to as a CHF device.

    [0067] The session management function device 102 is communicatively connected to the charging processing device 101, the policy control device 104, and the user equipment 103. The device may be configured to: [0068] (1) receive a user service start request (a request message for requesting the session management function device to start a user service) from the user equipment 103, start the user service based on the start request, and perform charging operations such as quota management and usage reporting on the user service; [0069] (2) carry, in a charging request to the charging processing device 101, the quota management mode adopted for the user service, so that the charging processing device 101 changes the quota management mode of the user service based on the account information of the user and/or the usage information of the user service; and [0070] (3) request a policy of the user service from the policy control device 104, and perform quota management on the user service based on the policy sent by the policy device 104 or an updated policy and the quota management mode carried in the policy or the updated policy.

    [0071] It should be understood that, during actual application, the charging system shown in FIG. 1A may have more session management function devices. The session management function devices may be communicatively connected to a same charging processing device 101 (for example, the charging processing device 101), or may be communicatively connected to different charging processing devices 101. A plurality of service start requests initiated by a same user equipment for a same user service may be processed by a same session management function device or different session management function devices.

    [0072] The user equipment 103, connected to the session management function device, is configured to: send a user service start request to the session management function device, and access or use the user service via the session management function device.

    [0073] The user equipment 103 may be a user equipment (user equipment, UE) defined in the 3GPP standard specifications, or may be a wireless access device having a wireless communication function or a wired access device having no wireless communication function, including a handheld device, a vehicle-mounted device, a wearable device, or a computing device. For example, the user equipment 103 may be a mobile phone (mobile phone), a tablet computer, or a computer having a wireless transceiver function. Alternatively, the user equipment 103 may be a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), and the like.

    [0074] It should be understood that, during actual application, the charging system shown in FIG. 1A may include more user equipments.

    [0075] The policy control device 104 is communicatively connected to the session management function device 102 and the charging processing device 101, is configured to provide a charging policy of the user service for the session management function device 102, and is further configured to provide the session management function device 102 with related information of a quota management mode corresponding to the user service or a service of the user.

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

    [0077] It should be noted that the foregoing “connected” or “connection” includes a direct connection or a communication connection by using one or more intermediate network devices.

    [0078] FIG. 1B is a schematic diagram of an architecture of a basic 5G system. As shown in FIG. 1B, the system includes: an access and mobility management function (access and mobility management function, AMF), a session management function (session management function, SMF), a radio access network (radio access network, RAN), unified data management (unified data management, UDM), a policy control function (policy control function, PCF), a data network (data network, DN), a user plane function (user plane function, UPF), UE, an application function (application function, AF), a unified data repository (unified data repository, UDR), and a charging function (charging function, CHF). Optionally, the following functions (not shown in FIG. 1B) may further be included in FIG. 1B: a network slice selection function (network slice selection function, NSSF), an authentication server function (authentication server function, AUSF), a network exposure function (network exposure function, NEF), a network repository function (NF repository function, NRF).

    [0079] Main functions of the network elements are described as follows:

    [0080] The AF may be understood as the name of an application function network element in a 5G architecture. The application function network element mainly transfers a requirement of an application side on a network side, for example, a quality of service (quality of service, QoS) requirement. The AF may be a third-party functional entity, or may be an operator-deployed application service, for example, an IP multimedia subsystem (IP Multimedia Subsystem, IMS) voice call service.

    [0081] The UDM may be understood as the name of a unified data management network element in the 5G architecture. The unified data management network element mainly includes the following functions: unified data management, authentication credential processing in a 3GPP authentication and key agreement mechanism, user identity processing, access authorization, registration and mobility management, subscription management, short message service management, and the like.

    [0082] The UDR may be understood as the name of a unified data repository network element in the 5G architecture. The unified data repository network element mainly includes the following functions: storage and retrieval of subscription data, storage and retrieval of policy data, storage and retrieval of application data, and storage and retrieval of other types of data.

    [0083] The PCF may be understood as the name of a policy control function network element in the 5G architecture. The policy control function network element mainly includes policy control functions such as performing session-level or service flow-level charging, QoS bandwidth guarantee and mobility management, and UE policy decision. In this system, a PCF connected to the AMF is a PCF for access and mobility control (PCF for access and mobility control, AM PCF), and a PCF connected to the SMF is a PCF for session management (PCF for session management, SM PCF). In actual deployment, the AM PCF and the SM PCF may be different PCF entities.

    [0084] The SMF may be understood as the name of a session management network element in the 5G architecture. The session management network element mainly performs functions such as session management, execution of a control policy delivered by the PCF, UPF selection, and UE IP address allocation.

    [0085] The AMF may be understood as the name of a mobility management network element in the 5G architecture. The mobility management network element mainly includes the following functions related to access and mobility, for example, connection management, mobility management, registration management, access authentication and authorization, reachability management, and security context management.

    [0086] The UPF may be understood as the name of a user plane function network element in the 5G architecture. The user plane function network element mainly includes the following functions related to a user plane, for example, data packet routing and transmission, packet detection, service usage reporting, QoS processing, lawful interception, uplink packet detection, and downlink data packet storage.

    [0087] A (R)AN is a (radio) access network, and corresponds to different access networks in 5G, for example, a wired access network and a wireless base station access network.

    [0088] DN is a data network, and is used to identify a name of a carrier network access point. In this application, the DN may further include an authentication, authorization, and accounting (authentication, authorization, accounting, AAA) server function, and is responsible for performing secondary authentication on the user.

    [0089] CHF is a charging function. The CHF is responsible for reporting charging status information to the PCF and interacting with the SMF to implement quota management and charging control.

    [0090] Functions of interfaces are described as follows:

    [0091] N7 represents an interface between the PCF and SMF, and is configured to deliver a PDU session granularity and a service data flow granularity control policy.

    [0092] N15 represents an interface between the PCF and the AMF, and is configured to deliver a UE policy and an access control related policy.

    [0093] N5 represents an interface between the AF and the PCF, and is configured to deliver an application service request and report a network event.

    [0094] N4 represents an interface between the SMF and UPF, and is configured to transmit information between a control plane and a user plane, including delivery of forwarding rules, QoS control rules, traffic statistics rules, and the like from the control plane to the user plane, and reporting of user-plane information.

    [0095] N11 represents an interface between the SMF and the AMF, and is configured to: transmit PDU session tunnel information between the RAN and the UPF, transmit a control message to be sent to the UE, transmit radio resource control information to be sent to the RAN, and the like.

    [0096] N2 represents an interface between the AMF and the RAN, and is configured to transmit radio bearer control information from the core network to the RAN and perform another operation.

    [0097] N1 represents an interface between the AMF and the UE, is access-irrelevant, and is configured to transmit the QoS control rule to the UE and perform another operation.

    [0098] N8 represents an interface between the AMF and the UDM, and is used by the AMF to obtain, from the UDM, subscription data related to access and mobility management and authentication data, and used by the AMF to register current mobility management related information of the UE with the UDM.

    [0099] N10 represents an interface between the SMF and the UDM, and is used by the SMF to obtain, from the UDM, subscription data related to session management, and used by the SMF to register current session related information of the UE with the UDM.

    [0100] N35 represents an interface between the UDM and the UDR, and is used by the UDM to obtain user subscription data information from the UDR.

    [0101] N36 represents an interface between the PCF and the UDR, and is used by the PCF to obtain policy-related subscription data and application data related information from the UDR.

    [0102] N3 represents an interface between the RAN and the UPF, and is configured to transmit user plane data between the RAN and the UPF.

    [0103] N6 represents an interface between the UPF and the DN, and is configured to transmit the user plane data between the UPF and the DN.

    [0104] N9 represents an interface between UPFs, for example, an interface between a visited-policy control function (visited-policy control function, V-PCF) and a home-policy control function (home-policy control function, H-PCF), or an interface between a UPF connected to the DN and a UPF connected to the RAN, and is configured to transmit the user plane data between the UPFs.

    [0105] N28 represents an interface between the PCF and the CHF, and is used by the PCF to subscribe to charging status (Policy Counter) information, such as a user balance status and a remaining traffic status, from the UDR.

    [0106] N40 represents an interface between the SMF and the CHF, and is used by the SMF to report charging information (Charging data) to the CHF and obtain a quota (Credit) threshold from the CHF.

    [0107] The architecture of the charging system shown in FIG. 1A or FIG. 1B enables the charging processing device 101 and/or the policy device to determine the quota management mode of the user service in a timely and dynamic manner, for example, determine or change the quota management mode of the user service based on the account information of the user and/or the usage information of the user service in the process of using the service. In this way, an initial quota request in a non-blocking mode or suspend quota management is used in the case of low credit control risks of the user service, and a quota request in a blocking mode or resume quota management is used in the case of high credit control risks of the user service. Therefore, this incorporates an access latency requirement of the user service, carriers’ requirements for system performance, and control of credit risks.

    [0108] For ease of understanding embodiments of this application, the following explains some concepts.

    [0109] A user service is a service accessed or used by the user equipment 103 via a network device (for example, the session management function device 102 or a user plane device not shown in FIG. 1A). The user service may be a service in a protocol data unit (Protocol Data Unit, PDU) session. For example, one or more data flows corresponding to a rating group (Rating Group, RG) in a PDU session, or a data flow corresponding to an RG and a service identifier in a PDU session may be understood as the user service in embodiments of this application. In embodiments of this application, “a user service in a PDU session” or “a service in a PDU session” means a plurality of data flows corresponding to the RG in the PDU session, or may be a data flow corresponding to a service identifier in the plurality of data flows corresponding to the RG.

    [0110] For of ease of description, in embodiments of this application, the user service is sometimes directly referred to as a “service”.

    [0111] The user service accessed or used by the user equipment 103 is mainly described in embodiments of this application by using a data connection service in a 5G network as an example. Correspondingly, charging data in embodiments of this application is mainly described by using information related to data traffic as an example. The information related to the data traffic includes but is not limited to: information that is about the PDU session and that is collected by the session management function device, usage of a service unit allowed to pass in the PDU session, a charging trigger condition, a timestamp, and the like.

    [0112] A service of a user is one or more services subscribed to by the user. The service of the user may be a user service in a PDU session in use, or may be a service not in use that is subscribed to by the user.

    [0113] Starting a user service means that, after receiving a start request of the user service, the session management function device allows the user service to pass. Allowing the user service to pass includes allowing signaling or data of the user service to pass. For example, when a user service is the foregoing data connection service, “starting a user service” includes continuing to establish or perform an update operation on a PDU session for the data connection service (if the PDU session is unavailable) or allowing a service data flow to pass (if the PDU session is available).

    [0114] A quota management mode (Quota Management Mode, QMM) is a method for processing an online charging user service by the session management function device 102 (which may alternatively be a charging trigger device). Specifically, in this application, the quota management mode may be an initial quota request mode (Initial Quota Request Mode, IQRM) (or an initial quota request mode) of an online charging user service, or the quota management mode may be suspend/resume quota management (Suspend/Resume Quota Management, SRQM) of the online charging user service. The initial quota request mode is a mode in which a quota is requested for the user service for the first time after the start request of the user service is received. The initial quota request mode may be blocking mode quota request or non-blocking mode quota request, which are described as follows.

    [0115] The blocking mode initial quota request (Blocking Mode Initial Quota Request, BLIQR) means that the session management function device 102 first requests a quota from the charging processing device 101 for the user service in response to the start request of the user service received from the user equipment 103, and starts the user service only after receiving a quota granted by the charging processing device 101 for the user service.

    [0116] The non-blocking mode initial quota request (Non-Blocking Mode Initial Quota Request, NBIQR) means that, in response to the start request of the user service received from the user equipment 103, the session management function device 102 preferentially starts the user service before requesting a quota from the charging processing device 101 for the user service, or requests the quota from the charging processing device 101 for the user service while starting the user service.

    [0117] Suspend/resume quota management (Suspend/Resume Quota Management, SRQM) means that suspend or resume quota management may be used for an online charging service in the case of sufficient balance or no credit control risks. When suspend quota management is used for a user service, the user service may be considered as a temporary offline charging service or an unlimited quota service, and the session management function device 102 does not request a quota from the charging processing device 101 for the user service. However, quota management is resumed or enabled for normal quota management for a user in the case of insufficient balance in the user’s account or in the case of existence of credit control risks for the user.

    [0118] Quota management mode indication information (Quota Management Mode Indication, QMMInd) is information indicating which quota management mode (such as IQRM or SRQM) has been used for the user service when the session management function device 102 receives the start request of the user service. The quota management mode indication information may include only a value of IQRM or SRQM, or may include an IQRMod field and a value thereof, or may include an SID (identifier of the user service) field and a value thereof. A data structure of the quota management mode indication information is not limited in embodiments of this application.

    [0119] It should be noted that, for ease of description, in embodiments of this application, “using a quota management mode for a user service” is sometimes described as “using a mode of initial quota request for a user service”.

    [0120] The following further describes an example of method procedures that can be implemented based on the charging system architecture shown in FIG. 1A. As shown in FIG. 2, FIG. 3A, FIG. 3B, FIG. 4, FIG. 5A, and FIG. 5B, in a method procedure corresponding to each figure, a session management function entity corresponds to the session management function device 102 in FIG. 1A, a charging processing device 101 corresponds to the charging processing device 101 in FIG. 1A, a user equipment corresponds to the user equipment 103 in FIG. 1A, and a policy control device 104 corresponds to the policy control device 104 in FIG. 1A. Details are not described in subsequent descriptions of these method procedures.

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

    [0122] Step 202: The policy control device 104 determines a first quota management mode of a user service. The first quota management mode of the user service is a quota management mode determined by the policy control device 104 for the user service before the user service starts.

    [0123] The first quota management mode may be a first initial quota request mode. The first initial quota request mode may be a non-blocking mode or a blocking mode. A first initial quota request mode in a blocking mode indicates that a quota granted by the charging processing device 101 needs to be obtained before the user service starts. A first initial quota request mode in a non-blocking mode means that a quota granted by the charging processing device 101 does not need to be obtained before the user service starts.

    [0124] The first quota management mode may alternatively be suspend/resume quota management. Suspend quota management means that the user service may be considered as a temporary offline charging service or an unlimited quota service, and the session management function device 102 does not request a quota from the charging processing device 101 for the user service. Resume quota management means performing normal quota management for the user.

    [0125] In an example, before performing step 202, the policy control device 104 receives related information that is of the first quota management mode of a user or the user service and that is sent by the charging processing device 101. Then, the policy control device 104 determines the first quota management mode of the user service based on the related information of the first quota management mode of the user or the user service.

    [0126] In another example, before performing step 202, the policy control device 104 obtains account information of the user or configuration information of the user from the charging processing device 101 or another network device. Then, the policy control device 104 determines the first quota management mode of the user service based on the obtained account information or configuration information of the user.

    [0127] In an optional step, before performing step 202, the policy control device 104 sends a request message to the charging processing device 101. The policy control device 104 receives a response message sent by the charging processing device 101, where the response message carries the related information of the first quota management mode of the user or the user service.

    [0128] Step 204: The policy control device 104 generates the first policy, where the first policy indicates to perform the first quota management mode for the user service.

    [0129] If the first quota management mode is the first initial quota request mode, the first policy includes indication of the first initial quota request mode, and the first initial quota request mode is the non-blocking mode or the blocking mode. If the first quota management mode of the user service is suspend quota management, a charging method of the user service included in the first policy is offline charging or temporary offline charging. If the first quota management mode of the user service is resume quota management, a charging method of the user service included in the first policy is online charging.

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

    [0131] Step 208: The policy control device 104 receives the related information of the second quota management mode that is sent by the charging processing device 101 and that is for changing the first quota management mode. The second quota management mode means that, the first quota management mode determined before is changed or replaced after the service starts.

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

    [0133] In an optional manner, the first quota management mode is a first initial quota request mode, and the second quota management mode is a second initial quota request mode. The first initial quota request mode is a blocking mode, and the second initial quota request mode is a non-blocking mode; or the first initial quota request mode is a non-blocking mode, and the second initial quota request mode is a blocking mode.

    [0134] In another optional manner, the first quota management mode is suspend quota management, and the second quota management mode is resume quota management; or the first quota management mode is resume quota management, and the second quota management mode is suspend quota management.

    [0135] Step 210: The policy control device 104 determines the second quota management mode based on the related information of the second quota management mode of the user service.

    [0136] Step 212: The policy control device 104 generates a second policy of the user service, where the second policy is for updating or replacing the first policy, and the second policy further indicates to perform the second quota management mode on the user service.

    [0137] If the second quota management mode is the second initial quota request mode, the second policy includes the second initial quota request mode of the user service, and the second initial quota request mode is the blocking mode or the non-blocking mode. If the second quota management mode of the user service is suspend quota management, a charging method of the user service included in the second policy is offline charging or temporary offline charging. If the second quota management mode of the user service is resume quota management, a charging method of the user service included in the second policy is online charging.

    [0138] If the second policy includes a policy identifier that is the same as an identifier of the first policy, the policy control device 104 sends the second policy to the session management function device 102. The identifier related to the first policy indicates that the second policy is for updating the first policy of the user service. In another example, the policy control device 104 allocates 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, where the second policy identifier indicates that the second policy is for replacing the executed first policy. For example, the session management function device 102 may indicate, based on the second policy identifier, to deactivate the first policy and activate the second policy.

    [0139] According to the method procedure corresponding to FIG. 2, the policy control device 104 determines the second quota management mode based on the related information of the second quota management mode that is sent by the charging processing device 101 and that is for changing the first quota management mode of the user service, and generates the second policy for replacing or updating the first policy, so that the quota management mode can be changed dynamically. This helps balance, dynamically and in real time, a relationship between an access latency requirement of an end user, carriers’ requirements for system performance, and control of credit risks.

    [0140] For the method procedure corresponding to FIG. 2, further refer to method procedures corresponding to FIG. 3A, FIG. 3B, FIG. 4, FIG. 5A, FIG. 5B, and FIG. 6 provided in embodiments of this application.

    [0141] FIG. 3A is a flowchart of a method for determining, by a policy control device 104, a quota management mode of a user service according to an embodiment of this application. In the method procedure corresponding to FIG. 3A, the quota management mode is an initial quota request mode (IQRM). The policy control device 104 receives quota management mode IQRM information of a user or a user service from a charging processing device 101, further determines an initial quota request mode of the user service, and generates a policy based on the determined initial quota request mode of the user service. The method procedure mainly includes the following steps.

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

    [0143] Specifically, after receiving a policy obtaining request of the user service or a policy update request of the user service that is sent by a session management function device 102, the policy control device 104 may determine, in response to the policy obtaining request or the policy update request, that information needs to be obtained from the charging processing device 101. Generally, when receiving a request for establishing a PDU session for a user, the session management function device 102 may send a policy obtaining request to the policy control device 104. The session management function device 102 may further send the policy obtaining request to the policy control device 104 after receiving a service start request. The policy obtaining request sent by the session management function device 102 to the policy control device 104 may carry a user identifier, PDU session information (for example, a type of the PDU session), and the like.

    [0144] Optionally, the policy control device 104 further determines that information about the IQRM of the user service needs to be obtained from the charging processing device 101, and carries an obtaining indication of the IQRM related information of the user service in the request message sent to the charging processing device 101.

    [0145] Optionally, the policy control device 104 determines, based on configuration information, that the request message needs to be sent to the charging processing device 101 and that the IQRM related information needs to be obtained. The configuration information may be local configuration information of the policy control device 104 or configuration information of the user obtained from a UDR. Alternatively, if the policy control device 104 determines that no information related to the IQRM of the user service or the user is stored, the policy control device 104 determines that the information about the IQRM of the user service needs to be obtained from the charging processing device 101.

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

    [0147] Specifically, the request message may be used to obtain and subscribe to a current status and a status change of a counter from the charging processing device 101. The request may not carry an obtaining indication of the IQRM.

    [0148] Further, the request message may be further used to obtain the information related to the IQRM of the user or the user service from the charging processing device 101. For example, in step 300, the policy control device 104 determines that information about first IQRM of the user service needs to be obtained from the charging processing device 101, and the request message may further carry an obtaining indication for the IQRM of the user service. The IQRM obtaining indication may be any indication in the following table.

    TABLE-US-00001 Indication name Indication content First obtaining indication of the IQRM related information An identifier of a user and indication information for obtaining a service list of the user in a non-blocking mode Second obtaining indication of the IQRM related information An identifier of a user service and indication information for obtaining whether the user service is allowed to use the first initial quota request mode in a non-blocking mode; or an identifier of a user and indication information for obtaining whether a service of the user is allowed to use the first initial quota request mode in a non-blocking mode Third obtaining indication of the IQRM related information An identifier of a user service and indication information for obtaining a first initial quota request mode of the user service, where the first initial quota request mode is a blocking mode or a non-blocking mode Fourth obtaining indication of the IQRM related information An identifier of a user and indication information for obtaining a first initial quota request mode of each service of the user, where the first initial quota request mode is a blocking mode or a non-blocking mode

    [0149] In an example, after receiving the policy obtaining request or the policy update request of the user sent by the session management function device 102, the policy control device 104 determines that a service list of services of an NB type of the current user needs to be obtained from the charging processing device 101, and sends the first obtaining indication of IQRM related information to the charging processing device 101. The first obtaining indication of the IQRM related information carries the identifier of the user and the indication information for obtaining the service list in the NB mode of the user. The following is an example:

    TABLE-US-00002            Request:              {              “UserID”: “SUPI”,              “RequestedNBM”: true              }

    [0150] The userID field indicates the user identifier. RequestedNBM is set to true, indicating to obtain a service list of the user whose IQRM is NB.

    [0151] In another example, after receiving the policy obtaining request or policy update request of the 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 obtaining indication of the IQRM related information to the charging processing device 101. The second obtaining indication of the IQRM related information carries the identifier of the user service and/or the user identifier, and indication information for obtaining whether the user service or the user is allowed to use the first initial quota request in the non-blocking mode. For example, the request message carries the user identifier and the identifier of the user service, indicating that it needs to be determined 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 indicates that it needs to be determined whether the current user can use the non-blocking mode.

    [0152] The following is an example:

    TABLE-US-00003            Request:            {                 “UserID”: “SUPI”,                 “NBModeAuth”:,                 “Service ID” or “RatingGroup”: “1”,                 “Service ID” or “RatingGroup”: “2”            }

    [0153] The userID field indicates the user identifier. “InitialQRMMode” indicates that the charging processing device 101 needs to determine whether the user service or user indicated in the request message can use the non-blocking mode. “RatingGroup” indicates a user service corresponding to a rating group. “Service ID” indicates a user service corresponding to an 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 rating group 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 a service indicated by “Service ID” can use the non-blocking mode. When the request message does not carry the “Service ID” and the “RatingGroup”, it indicates that the charging processing device 101 needs to confirm whether a user indicated by “userID” can use the non-blocking mode.

    [0154] Optionally, after receiving the policy obtaining request or the policy update request of the user sent by the session management function device 102, the policy control device 104 determines that first IQRM related information of the user service needs to be obtained, and sends a third obtaining indication of the IQRM related information to the charging processing device 101, to obtain first IQRM information of the user service. The third obtaining indication carries an identifier of the user service and indication information for obtaining a first initial quota request mode of the user service. The first IQRM of the user service may be the blocking mode or the non-blocking mode. The identifier of the user service may be a service identifier, a corresponding rating group, or another identifier that can identify the user service. The following is an example:

    TABLE-US-00004            Request:            {                 “UserID”: “SUPI”,                 “IntialQRMMAuthorization”,                 “Service ID”: “XXX”; //“RatingGroup” or “Service ID” can be used            }

    [0155] “IntialQRMMAuthorization” indicates that the charging processing device 101 needs to determine whether the user service indicated in the request message uses the non-blocking mode or the blocking mode. The user service indicated in the request message may be the user service corresponding to the rating group in “RatingGroup” or the user service corresponding to the user identifier in “Service ID”. For example, when the request carries “IntialQRMMAuthorization” and “RatingGroup”, it indicates that the charging processing device 101 determines and returns that IQRM of the user service corresponding to the rating group is the blocking mode or the non-blocking mode. When the request carries “IntialQRMMAuthorization” and “Service ID”, it indicates that the charging processing device 101 needs to confirm and return that IQRM of the service indicated by the “Service ID” is the blocking mode or the non-blocking mode.

    [0156] In another example, after receiving the policy obtaining request or the policy update request of the user sent by the session management function device 102, the policy control device 104 determines that first IQRM of each service of the user needs to be obtained from the charging processing device 101, and sends a fourth obtaining indication of the IQRM related information to the CHF, to obtain the first IQRM related information of each service of the user. The fourth obtaining indication of the IQRM related information carries the user identifier and indication information for obtaining the IQRM of each service of the user. The fourth IQRM obtaining indication may be in the following form:

    TABLE-US-00005            Request:            {               “UserID”: “SUPI”,               “InitialQRMMode”: true            }

    [0157] The userID field indicates the user identifier. “InitialQRMMode” being true indicates that the charging processing device 101 needs to determine a value of an initial quota request mode of each service of the user. The request message indicates that the charging processing device 101 needs to determine whether the first IQRM of each service of the user is the non-blocking mode or the blocking mode.

    [0158] Step 304: After receiving the request message, the charging processing device 101 performs corresponding processing based on the request message, and determines the first IQRM related information of the user service.

    [0159] Specifically, if the request message does not carry obtaining indication of information related to the quota management mode (the first IQRM in this embodiment), the charging processing device 101 may not return or may actively determine and return whether the service of the user is allowed 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, based on the stored IQRM of each service, whether the user or the user service can use the non-blocking mode. If the charging processing device 101 does not store the IQRM information of the service, the charging processing device 101 determines, based on account information and/or a service type of the user, whether the user or the user service can use the non-blocking mode.

    [0160] Further, if the request message carries obtaining indication of the quota management mode, the charging processing device 101 determines and returns the IQRM related information of the user or the service of the user based on the obtaining indication. The following table shows specific processing.

    TABLE-US-00006 Obtaining indication in step 302 Related processing in step 304 First obtaining indication The charging processing device 101 obtains, based on the first obtaining indication, a service list of services of the user whose IQRMs are the non-blocking mode and that are indicated by the user identifier. The service list includes identifiers of one or more user services in the non-blocking mode. If the charging processing device 101 stores IQRM related information of each service of the user, the charging processing device 101 obtains, based on the stored IQRM related information of each service of the user, the user service whose IQRM is the non-blocking mode. If the charging processing device 101 does not store the IQRM related information of the user service, the charging processing device 101 determines, based on the account information and/or the service type of the user, the user service that can use the non-blocking mode. Second obtaining indication, carrying a user service identifier The charging processing device 101 determines, based on the identifier of the user service in the second obtaining indication and the indication information indicating whether the user service is allowed to use the first initial quota request mode of the non-blocking mode, whether the user service can use the non-blocking mode. Second obtaining indication, not carrying a user service identifier The charging processing device 101 determines, based on the identifier of the user in the second obtaining indication and the indication information indicating whether the user is allowed to use the first initial quota request mode of the non-blocking mode, whether a service of the user can use the non-blocking mode. Third obtaining indication The charging processing device 101 determines, based on the identifier of the user service in the third obtaining indication and the indication information for obtaining the first IQRM of the user service, that the IQRM of the user service is the non-blocking mode or the blocking mode. Fourth obtaining indication The charging processing device 101 obtains a first IQRM of each service of the user based on the fourth obtaining indication, where the first IQRM is the non-blocking mode or the blocking mode.

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

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

    [0163] If the request message does not carry an obtaining indication of the first quota management mode, the response message carries indication information indicating whether the service of the user is allowed to use the non-blocking mode. If the request message carries the obtaining indication of the first quota management mode, the response message carries IQRM related information corresponding to the obtaining indication.

    [0164] If the charging processing device 101 receives the obtaining indication of the IQRM related information in step 302, refer to the following table for content carried in the response message.

    TABLE-US-00007 Name of the obtaining indication of the IQRM related information Name and content of the response message of the IQRM related information First obtaining indication A first response message carries the related information of the first quota management mode that is a list of services of the user that are allowed to use the first initial quota request mode in the non-blocking mode. The service list that uses the first initial quota request mode in the non-blocking mode includes a service identifier of one or more services that use the non-blocking mode, or a rating group of one or more services that use the non-blocking mode. Second obtaining indication A second response message includes information about whether the user service can use the non-blocking mode. Alternatively, the second IQRM response message includes information about whether a service of the user can use the non-blocking mode, to be specific, whether any online charging service of the user can use the non-blocking mode. Third obtaining indication A third response message carries the first IQRM of the user service is the non-blocking mode or the blocking mode. Fourth obtaining indication A fourth response message carries whether each service of the user is in the non-blocking mode or the blocking mode.

    [0165] For the first IQRM response message, refer to the following form:

    TABLE-US-00008            Response:            {                  “NBMserviceList”                        “RatingGroup” or “ServiceID”: 1,                        “RatingGroup” or “ServiceID”: 2                  }:            }

    [0166] The “NBMserviceList” indication carries a list of user services that can use the non-blocking mode.

    [0167] For the second response message, refer to the following form:

    TABLE-US-00009            Response:            {                 “UserID”: “SUPI”,                 “NBModeAuthResult”: yes;            }

    [0168] A value of NBModeAuthResult is yes, indicating that any online charging service of the user can use the non-blocking mode.

    [0169] If the second IQRM obtaining indication carries the rate group or the service identifier, refer to the following form for the second IQRM response message:

    TABLE-US-00010            Response:            {               “NBModeAuthResult”: {                 “RatingGroup” or “Service ID” “1”                 “ServiceResult”: yes;                  }               “NBModeAuthResult”: {                 “RatingGroup” or “Service ID”: “2”,                 “ServiceResult”: no               }            }

    [0170] If a value of the RatingGroup or the ServiceID is 1 and a value of the ServiceResult is yes, it indicates that the non-blocking mode can be used for a user service whose service ID is 1 or rating group is 1. If a value of the RatingGroup or the ServiceID is 2 and a value of the ServiceResult is no, it indicates that the non-blocking mode can be used for a user service whose service ID is 2 or rating group is 2.

    [0171] For the third response message, refer to the following form:

    TABLE-US-00011            Response:            {                “InitialQMMode” {                     “RatingGroup” or “ServiceID”: 1,                     “IQRMValue”: “NB”                }            }

    [0172] A value of “IQRMValue” is “NB”, indicating that a first initial quota request mode of the service corresponding to the rating group “RatingGroup” or the service indicated by the service identifier “ServiceID” is the non-blocking mode.

    [0173] For the fourth IQRM response message, refer to the following form:

    TABLE-US-00012            Response:            {                “InitialQRMMode”{                    “RatingGroup” or “ServiceID”: 1,                    “IQRMValue”: “NB”                  }                “InitialQRMMode” {                    “RatingGroup” or “ServiceID”: 2,                    “IQRMValue”: “B”                  }            }

    [0174] A value of “IQRMValue” is “NB”, indicating that a service corresponding to a rating group “RatingGroup” whose value is 1 or a service indicated by a service identifier whose value is 1 uses the non-blocking mode. A value of “IQRMValue” is “B”, indicating that a service corresponding to a rating group “RatingGroup” whose value is 2 or a service indicated by a service identifier whose value is 2 uses the blocking mode.

    [0175] Step 308: The policy control device 104 determines a first quota management mode of a user service, and generates a first policy of the user service. The first policy indicates to perform the first quota management mode on the user service.

    [0176] Specifically, if the charging processing device 101 returns a response message carrying related 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 based on the related information of the first IQRM of the user or the user service.

    [0177] Specifically, the policy control device 104 generates the first policy, and the first policy includes the first quota management mode of the user service. The quota management mode herein is the first initial quota request mode, and the first initial quota request mode is the blocking mode or the non-blocking mode.

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

    [0179] Specifically, the policy control device 104 sends the first policy to the session management function device 102, to indicate the session management function device 102 to perform the first quota management mode on the user service.

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

    TABLE-US-00013            {                 “ChargingRule”{                      “ChargingRuleID”: 1,                      “ChargingMethod”: “online”,                      “RatingGroup”: 1; or “ServiceID”: 1,                      “sdfHandl”: “true”                 }            }

    [0181] A value of the “sdfHandl” is true, indicating that the IQRM of a service indicated by the service identifier or a service indicated by the rating group is the blocking mode.

    [0182] According to this embodiment of this application, before delivering the policy, the policy control device 104 obtains the IQRM information of the user service from the charging processing device 101, and sends the IQRM information of the user service in the policy to the session management function device 102. According to this embodiment of this application, the IQRM information carried by the policy control device 104 in the policy sent to the session management function device 102 is more accurate, so that a risk in a service use process can be avoided.

    [0183] FIG. 3B is a flowchart of a method for determining, by a charging processing device 101, to change a first quota management mode of a user service according to an embodiment of this application. In combination with FIG. 3A, in the method procedure corresponding to FIG. 3B, the first quota management mode is an initial quota request mode (IQRM). For example, the charging processing device 101 makes a real-time decision to change a first IQRM of the user service to the blocking mode, or the charging processing device 101 makes a real-time decision on whether to forbid the user service to use the non-blocking mode. When the charging processing device 101 determines to change the first IQRM of the user service to the blocking mode or prohibit the first IQRM of the service quota management mode of the user service to the non-blocking mode, the charging processing device 101 notifies the policy control device 104, so that the policy control device 104 determines a second quota management mode (a second IQRM in this embodiment) of the user service based on second IQRM related information of the user service, and further determines whether to generate a second policy. The method procedure mainly includes the following steps.

    [0184] Step 351: The session management function device 102 receives a start request of the user service.

    [0185] After receiving the service start request, the session management function device 102 determines that information about the first quota management mode (the first IQRM in this embodiment) of the user service (for example, a service A), for example, the first IQRM information of the user service included in step 310 in FIG. 3A, has been obtained. The session management function device 102 performs corresponding processing based on the first IQRM information of the user service. If the session management function device 102 determines that the first IQRM information of the service is not obtained, the procedure in FIG. 3A may be performed to obtain the IQRM information of the service of the user.

    [0186] If the session management function device 102 determines that the obtained first IQRM information of the 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 request to the charging processing device 101 to request a quota for the user service, or sends a quota request to the charging processing device 101 to request a quota for the user service when starting the service. If the session management function device 102 determines that the obtained first IQRM information of the user service indicates that the IQRM of the user service is the blocking mode, the session management function device 102 first sends a quota request to the charging processing device 101 to request a quota for the user service, and starts the user service after receiving a quota allocated by the charging processing device 101.

    [0187] Step 352: The session management function device 102 sends a charging request of the user service to the charging processing device 101.

    [0188] The charging request may be an initial charging request (that is, the first charging request for a user to use a service), or may be an update charging request after the initial charging request. This is not limited in this embodiment of the present invention.

    [0189] In an optional manner, the charging request further carries the first IQRM information of the user service, to indicate an IQRM currently used by the user service (for example, the user service A). In this embodiment of this application, an example in which the IQRM of the service A is the non-blocking mode is used for description. To be specific, the IQRM information of the service A carried in the charging request is the non-blocking mode.

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

    [0191] The foregoing step 351 to step 353 are optional steps. In some scenarios, the foregoing steps may not be performed, and step 354 is directly started. For example, if the user service does not start, another user service of the user or a user account management process may cause a change of the first quota management mode (herein, the first initial quota request mode) corresponding to the user service.

    [0192] Step 354: The charging processing device 101 determines that first IQRM related information of the user service A needs to be changed.

    [0193] Specifically, when processing the charging request of the user service sent in step 352, or processing a charging request of another service of the user, or performing a charging management process on an account of the user, the charging processing device 101 may determine that the first quota management mode of the user service needs to be changed.

    [0194] For example, that the charging processing device 101 determines that the quota management mode of the user service needs to be changed may be as follows: The charging processing device 101 determines the first quota management mode currently used by the user service, and determines that the first quota management mode of the user service needs to be changed to a second quota management mode.

    [0195] A method for determining, by the charging processing device 101, that the user service currently uses the first quota management mode may be as follows: The charging processing device 101 receives a charging request of the user service, where the charging request includes indication information indicating that the user service currently uses the first quota management mode; and the charging processing device 101 determines, based on the indication information of the first quota management mode of the user service included in the charging request, that the user service currently uses the first quota management mode. Alternatively, the charging processing device 101 determines that related information of the first quota management mode of the user service has been sent to the policy control device 104, and determines, based on the related information of the first quota management mode of the user service that has been sent to the policy control device 104, that the user service currently uses the first quota management mode.

    [0196] That the charging processing device 101 determines that the first quota management mode of the user service needs to be changed to the second quota management mode of the user service may be as follows: When processing the charging request of the user service sent in step 352, or when processing a charging request of another service of the user, or when performing a charging management procedure on a user account, the charging processing device 101 determines that a condition for using the first quota management mode by the user service is not met. For example, when a balance of the user account does not meet a condition for the service A to use the non-blocking mode, the charging processing device 101 determines to change the IQRM of the service A to the blocking mode, or forbids the service A to use the non-blocking mode. The condition for the user service to use the non-blocking mode may be as follows: A package balance of the user account is greater than a first threshold, or a decrease speed of the balance of the user account is lower than a second threshold, or the like.

    [0197] Further, when determining to change the non-blocking mode of the user service A to the blocking mode, the charging processing device 101 may further determine to change the non-blocking mode of another service of the user to the blocking mode, or determine to forbid another service of the user to use the non-blocking mode.

    [0198] Optionally, after determining to change the IQRM related information of the user service, the charging processing device 101 saves a determining result, that is, saves the determined second quota management mode of the user service, to provide the IQRM information to a requesting device when another device subsequently obtains the IQRM information of the user service.

    [0199] Step 355: The charging processing device 101 sends, to the policy control device 104, related information of a second IQRM of the user service that is for changing the first IQRM.

    [0200] Specifically, the charging processing device 101 sends a notification message (also referred to as a change notification) to the policy control device 104, where the notification message carries related information of the second quota management mode of the user service, namely, related information of the second IQRM of the user service.

    [0201] The charging processing device 101 determines that a resource created by the policy control device 104 for the user exists, and sends the notification message to the policy control device 104 based on a notification address corresponding to the resource. The resource created for the user is a 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 by the policy control device to obtain (subscribe to) accumulative status information of the user. The resource created for the user is created by the charging processing device based on a resource creation request after the policy control device sends the resource creation request to the charging processing device. The resource creation request carries a notification address and a user identifier that correspond to the resource. The notification address is used by the charging processing device 101 to notify the policy control device 104 of the accumulative status information of the user. Based on the determined existing resource requested to be created for the user, the charging processing device 101 determines that a notification message of the second IQRM related information of the user service needs to be sent to the policy control device 104. Alternatively, if the charging processing device 101 determines, based on the determined existing resource (or subscription information) requested to be created for the user, that the policy control device 104 has subscribed to or requested the first IQRM related information of the user, the charging processing device 101 determines that a notification message of the second IQRM related information of the user service needs to be sent to the policy control device 104.

    [0202] For the second IQRM related information of the user service carried in the notification message, refer to the following table.

    TABLE-US-00014 First notification A list of services of the user that are allowed to use the second IQRM in the non-blocking mode Second notification Indication information indicating whether the user is allowed to use the second IQRM in the non-blocking mode Third notification Indication information indicating whether the user service is allowed to use the second IQRM in the non-blocking mode Fourth notification Indication information indicating that the second IQRM of the user service is the blocking mode or the non-blocking mode Fifth notification Indication information indicating that a second IQRM of each service of the user is the blocking mode or the non-blocking mode

    [0203] A notification message including the first notification may be referred to as a first notification message, and the rest may be deduced by analogy. The following is a reference example of the second notification message:

    TABLE-US-00015            Notify:            {                “UserID”: “SUPI”,                “NBModeAuthResult”: No;            }

    [0204] The userID field indicates the user identifier. If the value of “NBModeAuthResult” is no, it indicates that the charging processing device 101 confirms that the user cannot use the non-blocking mode, to be specific, all services of the user cannot use the non-blocking mode.

    [0205] A reference example of another notification message, for example, the second notification message, the third notification message, the fourth notification message, or the fifth notification message, is not provided herein in this embodiment of this application.

    [0206] Step 356: After receiving the related 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 based on the related information of the second quota management mode, and generates a second policy of the user service.

    [0207] The second policy is for updating or replacing the first policy, and indicates to perform the second quota management mode on the user service.

    [0208] That the second policy updates the first policy is specifically as follows: The generated second policy includes a policy identifier that is the same as an identifier of the first policy, and it is determined, based on the identifier, that the second policy is for updating the first policy.

    [0209] That the second policy replaces the first policy is specifically as follows: A second policy identifier is allocated to the second policy, where the second policy is a new policy of a user service different from the first policy, and the policy control device 104 needs to first deactivate the first policy, and then activate the second policy.

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

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

    [0212] If the second policy is the new policy of the user service, the policy update message delivered by the policy control device 104 to the session management function carries a deactivation instruction of the first policy and an activation instruction of the second policy, to update the first policy of the user service using the second policy.

    [0213] According to this embodiment of this application, the charging processing device 101 may determine or change the first IQRM of the user service based on information such as user account information. Therefore, the IQRM of the user service is more accurate, and risks and losses caused by the use of the non-blocking mode in the user service can be avoided.

    [0214] It should be noted that, in an actual service use process, FIG. 3B may be used in combination with FIG. 3A, or may be used separately. This is not limited in this embodiment of this application.

    [0215] FIG. 4 is a flowchart of a method for determining a first quota management mode and a second quota management mode of a user service according to an embodiment of this application. In this embodiment, the quota management mode is an initial quota request mode (IQRM). Different from the embodiments corresponding to FIG. 3A and FIG. 3B, in this embodiment, the policy control device 104 determines the first quota management mode of the user service based on the obtained configuration information of the user, that is, determines whether the user service uses the non-blocking mode. The charging processing device 101 decides in real time whether to change the first quota management mode of the user service to the second quota management mode. The method procedure mainly includes the following steps.

    [0216] Step 401 and 402: The policy control device 104 sends a resource creation request to the charging processing device 101, and receives a resource creation response of the charging processing device 101.

    [0217] After receiving a policy obtaining indication of the user service or a policy update request of the user service that is sent by a session management function device 102, the policy control device 104 sends the resource creation request to the charging processing device 101 in response to the policy obtaining indication or the policy update request, to obtain related information of the user service or the user, such as usage information of the user service, from the charging processing device 101 by using the created resource. The resource creation request may alternatively be a session establishment request, to establish a session between the policy control device 104 and the charging processing device 101.

    [0218] Step 403: The policy control device 104 determines a first quota management mode (first IQRM in this application) of the user service based on the obtained information, and generates a first policy of the user service based on the determined first IQRM of the user service. The generated first policy of the user service includes first IQRM information of the user service.

    [0219] For example, the policy control device 104 may obtain the configuration information of the user from the charging processing device 101 or another network device such as a (UDR), and determine the IQRM of the user service based on the obtained configuration information of the user. For example, the policy control device 104 may determine the first IQRM of the user service based on the user account information and/or the usage information of the user service obtained from the charging processing device 101, and the policy control device 104 may further determine the first IQRM based on user information obtained from the UDR, such as whether the IQRM subscribed to by the user is the non-blocking mode.

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

    [0221] For specific descriptions of step 404, refer to the descriptions of step 310. Details are not described again in this embodiment of this application.

    [0222] Step 405: The session management function device 102 receives a start request of the user service, and performs processing based on the first IQRM. The start request of the user service carries a service identifier and a user identifier.

    [0223] Specifically, for descriptions of step 405, refer to the descriptions of step 351. Details are not described again in this embodiment of this application.

    [0224] Step 406: The session management function device 102 sends a charging request to the charging processing device 101, where the charging request may be a charging request for the user service, or may be a charging request for another service used by the user. In addition, the charging request may be an initial charging request (that is, the first charging request for a user to use a service), or may be an update charging request after the initial charging request. This is not limited in this embodiment of the present invention.

    [0225] Further, the charging request carries the first IQRM information of the user service, to indicate an IQRM currently used by the user service (for example, a service B). In this embodiment of this application, an example in which the first IQRM of the user service is the non-blocking mode is used for description. To be specific, the IQRM information of the user service B carried in the charging request is the non-blocking mode. It indicates that before receiving a quota allocated by the charging processing device 101, the session management function device 102 allows a data flow related to the user service B to pass.

    [0226] Step 407: The charging processing device 101 performs corresponding charging processing based on the charging request, and then sends a charging response to the session management function device 102.

    [0227] Step 408: The charging processing device 101 determines that the first IQRM of the user service needs to be changed, generates a second IQRM for changing the first IQRM, and saves information of the changed second IQRM.

    [0228] Specifically, in a process of performing step 407, the charging processing device 101 determines, based on the first IQRM information of the user service carried in the charging request, that the user service uses the non-blocking mode. When determining that the user account does not meet a condition for the user service to use the non-blocking mode, the charging processing device 101 determines that the second quota management mode (the second IQRM in this embodiment) of the user service is the blocking mode, or forbids the user service to use the non-blocking mode. The condition for the user service to use the non-blocking mode may be as follows: A package balance of the user account is greater than a first threshold, or a decrease speed of the balance of the user account is lower than a second threshold, or the like.

    [0229] Further, when determining to change the non-blocking mode of the user service to the blocking mode, the charging processing device 101 may further determine to change the non-blocking mode of another service of the user to the blocking mode, or determine to forbid another service of the user to use the non-blocking mode, or forbid all services of the user to use the non-blocking mode.

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

    [0231] Step 409: The charging processing device 101 sends a notification message (also referred to as a change notification) of changing the first IQRM related information of the user service to the policy control device 104, so that the policy control device 104 generates or updates the control policy of the user service based on the change notification.

    [0232] Specifically, descriptions of step 409 are consistent with the descriptions of step 355. Details are not described herein again in this embodiment of the present invention.

    [0233] Descriptions of steps 410 and 411 are consistent with descriptions of steps 356 and 357. Details are not described again in this embodiment of the present invention.

    [0234] According to this embodiment of this application, the policy control device 104 determines, based on the obtained related information of the user, whether the user service can use the non-blocking mode. In addition, in the process of using the user service, the IQRM of the user service is determined or changed based on the account information of the user. Therefore, the IQRM of the user service is more accurate, and risks and losses caused by the use of the non-blocking mode in the process of using the user service can be avoided.

    [0235] FIG. 5A is a flowchart of a method for determining a policy by the policy control device 104 according to an embodiment of this application. In the method procedure corresponding to FIG. 5A, the quota management mode is suspend or resume quota management (SRQM). The policy control device 104 receives related information of a quota management mode of a user or a user service from the charging processing device 101, further determines whether to suspend or resume quota management of the user service, and generates a policy accordingly. The method procedure mainly includes the following steps.

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

    [0237] Specifically, after receiving a policy obtaining request of the user service or a policy update request of the user service that is sent by a session management function device 102, the policy control device 104 may determine, in response to the policy obtaining request or the policy update request, that information needs to be obtained from the charging processing device 101, and determine to send a request message to the charging processing device 101. Generally, when receiving a request for establishing a PDU session for a user, the session management function device 102 may send a policy obtaining request to the policy control device 104. The session management function device 102 may further send the policy obtaining request to the policy control device 104 after receiving a service start request. The policy obtaining request sent by the session management function device 102 to the policy control device 104 may carry a user identifier, PDU session information (for example, a type of the PDU session), and the like.

    [0238] Optionally, the policy control device 104 further determines whether information about the SRQM of the service of the user needs to be obtained from the charging processing device 101. If the information about the SRQM of the service of the user needs to be obtained from the charging processing device 101, the policy control device 104 carries an obtaining indication of the SRQM related information of the service of the user in the request message sent to the charging processing device 101.

    [0239] Optionally, the policy control device 104 determines, based on configuration information, that the request message needs to be sent to the charging processing device 101 and that the SRQM related information of the user service needs to be obtained. The configuration information may be local configuration information of the policy control device 104 or configuration information of the user obtained from a UDR.

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

    [0241] Specifically, the request message may be used to obtain and subscribe to a current status and a status change of a counter Counter from the charging processing device 101, and the request may not carry an instruction for obtaining the SRQM.

    [0242] Further, the request message may be further used to obtain the information related to the SRQM of the user or the user service from the charging processing device 101. For example, in step 500, the policy control device 104 determines that information about the SRQM of the user service needs to be obtained from the charging processing device 101, and the request message may further carry an obtaining indication for the SRQM of the user service. The SRQM obtaining indication may be any indication in the following table.

    TABLE-US-00016 Indication name Indication content First obtaining indication of the SRQM related information Indication information for obtaining a list of services of a user whose quota management can be suspended Second obtaining indication of the SRQM related information Indication information for obtaining whether quota management of the user or the user service is allowed to be suspended Third obtaining indication of the SRQM related information Indication information for obtaining SRQM information of a specified user service, where the SRQM may be Suspend, indicating that the user service uses a temporarily suspend quota management mode; or the SRQM is Resume, indicating that quota management is resumed for the user service, to be specific, the session management function device 102 needs to request a quota for the user service. Fourth obtaining indication of the SRQM related information Indication information for obtaining SRQM information of services of the user, where the SRQM may be Suspend, indicating that the user service uses a temporarily suspend quota management mode; or the SRQM is Resume, indicating that quota management is resumed for the user service, to be specific, the session management function device 102 needs to request a quota for the user service.

    [0243] Specifically, a method for carrying any one of the first to the fourth obtaining indications in the request message sent by the policy control device 104 to the charging processing device 101 is similar to the method for carrying the first to the fourth corresponding obtaining indications in step 302 of the embodiment shown in FIG. 3A. Details are not described again in this embodiment of the present invention.

    [0244] Step 504: After receiving the request message, the charging processing device 101 performs corresponding processing based on the request message. For example, the charging processing device 101 determines the first SRQM related information of the user service.

    [0245] Specifically, if the request message does not carry obtaining indication of information related to the quota management mode (the first SRQM in this embodiment), the charging processing device 101 may actively determine and return whether the quota management of the user is suspended. If the charging processing device 101 stores the SRQM information of each service, the charging processing device 101 determines, based on the stored SRQM information of each service, whether the user or the user service can suspend quota management. If the charging processing device 101 does not store the SRQM information of the service, the charging processing device 101 determines, based on account information and/or a service type of the user, whether the user or the user service can use the non-blocking mode.

    [0246] Further, if the request message carries obtaining indication of the quota management mode, the charging processing device 101 determines and returns the SRQM related information of the user or the user service based on the obtaining indication. The following table shows specific processing.

    TABLE-US-00017 Obtaining indication in step 502 Related processing in step 504 First obtaining indication Determine, based on the first obtaining indication, a list of services of the user that allow suspend quota management Second obtaining indication, carrying a user service identifier Determine, based on the identifier of the user service and the indication information indicating whether the quota management of the user service can be suspended, whether the user service allows suspend quota management Second obtaining indication, not carrying a user service identifier Determine, based on the identifier of the user and the indication information indicating whether the quota management of the service of the user can be suspended, whether the service of the user allows suspend quota management Third obtaining indication Determine, based on the user service identifier in the third obtaining indication and the indication information for obtaining the first SRQM of the user service, whether the first SRQM of the user service is suspend (suspend) or resume (resume) quota management Fourth obtaining indication Determine first SRQM of each service of the user based on the user identifier in the fourth obtaining indication, where the first SRQM is suspend quota management or resume quota management

    [0247] A specific method is similar to step 304 in the embodiment shown in FIG. 3A, and details are not described herein again.

    [0248] Step 506: The charging processing device 104 sends a response message of the request message to the policy control device 101.

    [0249] Specifically, the response message carries the first SRQM related information of the user or the user service obtained in step 504. [0250] If the request message does not carry an obtaining indication of the quota management mode, the response message carries indication information indicating whether the first quota management mode of the service of the user is allowed to be suspended. [0251] If the request message carries the obtaining indication (such as any obtaining indication in the first obtaining indication to the fourth obtaining indication) of the quota management mode, the response message carries first SRQM related information corresponding to the obtaining indication.

    [0252] Specific examples of the method and the message are similar to those in step 306 in the embodiment shown in FIG. 3A, and details are not described herein again.

    [0253] Step 508: The policy control device 104 determines a first quota management mode of a user service, and generates a first policy of the user service. The first policy indicates to perform the first quota management mode on the user service.

    [0254] Specifically, if the charging processing device 101 returns a response message carrying related 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 based on the related information of the first SRQM of the user or the user service. The quota management mode herein is suspend or resume quota management.

    [0255] Specifically, the policy control device 104 generates the first policy. If the determined first quota management mode of the user service is suspend quota management, a 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 resume quota management, the charging method of the user service included in the first policy is online charging.

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

    [0257] Specifically, the policy control device 104 sends the first policy to the session management function device 102, to indicate the session management function device 102 to perform the first quota management mode on the user service.

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

    TABLE-US-00018            {                “ChargingRule” {                      “ChargingRuleID”: 1,                      “ChargingMethod”: “TempOffline”,                      “RatingGroup”: 1; or “ServiceID”: 1                  }            }

    [0259] A value of “ChargingMethod” is TempOffline, indicating that the quota management of the user service is suspended.

    [0260] According to this embodiment of this application, before delivering the policy, the policy control device 104 obtains the first SRQM related information of the user service from the charging processing device 101, generates the first policy of the user service based on the first SRQM related information, and sends the first policy to the session management function device 102. According to this embodiment of this application, the policy control device 104 determines, before sending the first policy to the session management function device 102, the charging method based on the decision of the charging processing device 101. This can reduce charging processing load, improve efficiency of an entire system, and avoid credit control risks in a service use process.

    [0261] FIG. 5B is a flowchart of a method for determining, by the charging processing device 101, to change a quota management mode of a user service according to an embodiment of this application. In combination with FIG. 5A, in the method procedure corresponding to FIG. 5B, the quota management mode is suspend or resume quota management (SRQM). The policy control device 104 receives, from the charging processing device 101, related information of second SRQM for changing the first SRQM, determines, based on the related information of the second SRQM, whether to suspend or enable quota management of the user service, and determines whether to update/replace the previously generated first policy of the user service. The method procedure mainly includes the following steps.

    [0262] Step 552: The session management function device 102 sends a charging request of the user service to the charging processing device 101 in a process of using the user service.

    [0263] The charging request may be an initial charging request (that is, the first charging request for a user to use a service), or may be an update charging request after the initial charging request. This is not limited in this embodiment of the present invention.

    [0264] In an optional manner, the charging request further carries SRQM information (temporary suspension is used as an example) corresponding to the service, to indicate that quota management is currently suspended for the service (for example, the service A).

    [0265] Before performing this step, the session management function device 102 receives a start request of the user service, and determines that information about the first quota management mode (the first SRQM in this embodiment) of the user service (for example, the service A), for example, the first SRQM information of the user service included in step 510 in FIG. 5A, has been obtained. The session management function device 102 performs corresponding processing based on the first SRQM information of the user service. If the session management function device 102 determines that the first IQRM information of the service is not obtained, the procedure in FIG. 5A may be performed to obtain the first SRQM information of the service of the user.

    [0266] If the session management function device 102 determines that the obtained first SRQM information of the service indicates that the SRQM of the user service is suspend 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 obtained first SRQM information of the user service indicates that the SRQM of the user service is resume quota management, the session management function device 102 first sends a quota request to the charging processing device 101 to request a quota for the user service, and starts the user service after receiving a quota allocated by the charging processing device 101. Alternatively, if the session management function device 102 determines that the obtained first SRQM information of the user service indicates that the SRQM of the user service is resume quota management, the session management function device 102 first starts the service, and then sends a quota request to the charging processing device 101 to request a quota for the user service, or sends a quota request to the charging processing device 101 to request a quota for the user service when starting the service. If the session management function device 102 determines that the obtained first SRQM information of the user service indicates that the SRQM of the user service is resume quota management, the session management function device 102 may further use a first initial quota request mode in the blocking mode or the non-blocking mode. For details, refer to the foregoing embodiment.

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

    [0268] The foregoing step 552 and step 553 are optional steps. In some scenarios, the foregoing steps are not performed, and step 554 is directly started. For example, if the user service does not start, another user service of the user or a user account management process may cause a change of the quota management mode (herein, suspend or resume quota management) corresponding to the user service.

    [0269] Step 554: The charging processing device 101 determines that first SRQM related information of the user service A needs to be changed.

    [0270] When processing the charging request of the user service sent in step 552, or processing a charging request of another service of the user, or performing a charging management process on an account of the user, the charging processing device 101 may determine whether the first quota management mode of the user service needs to be changed.

    [0271] For example, that the charging processing device 101 determines that the quota management mode of the user service needs to be changed may be as follows: The charging processing device 101 determines the first quota management mode of the user service, and determines that the first quota management mode of the user service needs to be changed to a second quota management mode.

    [0272] A method for determining, by the charging processing device 101, that the user service currently uses the first quota management mode may be as follows: The charging processing device 101 receives a charging request of the user service, where the charging request includes indication information indicating that the user service currently uses the first quota management mode; and the charging processing device 101 determines, based on the indication information of the first quota management mode of the user service included in the charging request, that the user service currently uses the first quota management mode. Alternatively, the charging processing device 101 determines that related information of the first quota management mode of the user service has been sent to the policy control device 104, and determines, based on the related information of the first quota management mode of the user service that has been sent to the policy control device 104, that the user service currently uses the first quota management mode.

    [0273] That the charging processing device 101 determines that the first quota management mode of the user service needs to be changed to the second quota management mode of the user service may be as follows: When processing the charging request of the user service sent in step 552, or when processing a charging request of another service of the user, or when performing a charging management procedure on a user account, a condition for the user service to use the first quota management mode is not met. For example: if an account balance of the user does not meet the condition for the service A to use suspend quota management, the charging processing device 101 determines to change the SRQM of the service A to resume quota management.

    [0274] Further, when determining to change suspend quota management of the user service A to resume quota management, the charging processing device 101 may further determine to change suspend quota management of another service of the user to resume quota management, or determine to forbid another service of the user to use suspend quota management.

    [0275] Optionally, after determining to change the first SRQM related information of the user service, the charging processing device 101 saves a determining result, that is, saves the determined second quota management mode used by the user service, to provide the SRQM information to a requesting device when another device subsequently obtains the SRQM information of the user service.

    [0276] Step 555: The charging processing device 101 sends, to the policy control device 104, related information of second SRQM of the user service that is for changing the first SRQM.

    [0277] Specifically, the charging processing device 101 sends a notification message (also referred to as a change notification) to the policy control device 104, where the notification message carries related information of the second quota management mode of the user service, namely, related information of the second SRQM of the user service.

    [0278] The charging processing device 101 determines that a resource created by the policy control device 104 for the user exists, and sends the notification message to the policy control device 104 based on a notification address corresponding to the resource. The resource created for the user is a 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 by the policy control device to obtain (subscribe to) accumulative status information of the user. The resource created for the user is created by the charging processing device based on a resource creation request after the policy control device sends the resource creation request to the charging processing device. The resource creation request carries a notification address and a user identifier that correspond to the resource. The notification address is used by the charging processing device 101 to notify the policy control device 104 of the accumulative status information of the user. Based on the determined existing resource requested to be created for the user, the charging processing device 101 determines that a notification message of the second SRQM related information of the user service needs to be sent to the policy control device 104. Alternatively, if the charging processing device 101 determines, based on the determined existing resource (or subscription information) requested to be created for the user, that the policy control device 104 has subscribed to or requested the first SRQM related information of the user, the charging processing device 101 determines that a notification message of the second SRQM related information of the user service needs to be sent to the policy control device 104.

    [0279] For the second SRQM related information of the user service carried in the notification message, refer to the following table.

    TABLE-US-00019 First notification A service list that allows suspend quota management and that is of the user Second notification Indication information indicating whether quota management of the user service is allowed to be suspended Third notification Second SRQM indication information indicating whether quota management of the service of the user is allowed to be suspended Fourth notification Indication information indicating whether the second SRQM of the user service is suspend quota management or resume quota management Fifth notification Indication information indicating whether second SRQM of each service of the user is suspend quota management or resume quota management

    [0280] A notification message including the first notification may be referred to as a first notification message, and the rest may be deduced by analogy. The following is a reference example of the third notification message:

    TABLE-US-00020            Notify:            {                “UserID”: “SUPI”;                “SRQMode”: “RESUME”;            }

    [0281] The userID field indicates the user identifier. A value of “SRQMode” is “RESUME”, indicating that the charging processing device 101 confirms that the service of the user does not allow suspend quota management, to be specific, all services of the user do not allow suspend quota management. If the notification message further carries a user identifier, for example, service id or Rating group, the notification message is a second notification message. It indicates that the user service indicated by the service id or Rating group does not allow suspend quota management. Further, if the second SRQM related information in the notification message is resume quota management, the notification message may further carry IQRM information, to indicate that the user service can use the blocking mode or the non-blocking mode.

    [0282] A reference example of another notification message, for example, the first notification message, the fourth notification message, or the fifth notification message, is not provided herein in this embodiment of this application.

    [0283] Step 556: After receiving the related 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 based on the related information of the second quota management mode, and generates a second policy of the user service.

    [0284] The second policy is for updating or replacing the first policy, and indicates to perform the second quota management mode on the user service.

    [0285] That the second policy updates the first policy is specifically as follows: The generated second policy includes a policy identifier that is the same as an identifier of the first policy, and it is determined, based on the identifier, that the second policy is for updating the first policy.

    [0286] That the second policy replaces the first policy is specifically as follows: A unique policy identifier is allocated to the second policy, where the second policy is a new policy of a user service different from the first policy, and the policy control device 104 needs to first deactivate the first policy, and then install and activate the second policy.

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

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

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

    [0290] If the second policy is the new policy of the user service, the policy update message delivered by the policy control device 104 to the session management function carries a deactivation instruction of the first policy and an activation instruction of the second policy, to update the first policy of the user service using the second policy.

    [0291] According to this embodiment of this application, the charging processing device 101 may determine or change the SRQM of the user service based on information such as user account information. In this way, SRQM control of the user service is more accurate, and risks and losses caused by suspend quota management in a process of using the user service can be avoided.

    [0292] It should be noted that, in an actual service use process, FIG. 5A may be used in combination with FIG. 5B, or may be used separately. This is not limited in this embodiment of this application.

    [0293] FIG. 6 is a flowchart of another method for determining a quota management mode of a user service according to an embodiment of this application. In this embodiment, the quota management mode is suspend/resume quota management (SRQM). Different from the embodiments corresponding to FIG. 5A and FIG. 5B, in this embodiment, the policy control device 104 determines the first quota management mode of the user service based on the obtained configuration information of the user, that is, determines whether the user service allows suspend quota management. The charging processing device 101 decides in real time whether to change the first quota management mode of the user service to the second quota management mode. The method procedure mainly includes the following steps.

    [0294] Step 601 and 602: The policy control device 104 sends a resource creation request to the charging processing device 101, and receives a resource creation response of the charging processing device 101.

    [0295] In this embodiment, descriptions of steps 601 and 602 are the same as descriptions of steps 401 and 402, and therefore details are not described again.

    [0296] Step 603: The policy control device 104 determines a first quota management mode (first SRQM in this application) of the user service based on the obtained information, and generates a first policy of the user service. The first policy indicates to perform the first quota management mode on the user service. For example, the policy control device 104 may obtain the configuration information of the user from the charging processing device 101 or another network device such as a (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 may determine the first SRQM of the user service based on the user account information and/or the usage information of the user service obtained from the charging processing device 101, and the policy control device 104 may further determine the first SRQM of the user service based on user information obtained from the UDR, such as the SRQM subscribed to by the user.

    [0297] The first policy generated by the policy control device 104 in step 603 is the same as the first policy generated in step 508. Details are not described herein again in this embodiment of this application.

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

    [0299] For specific descriptions of step 604, refer to the descriptions of step 510. Details are not described again in this embodiment of this application.

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

    [0301] Specifically, for descriptions of step 605, refer to the descriptions of step 351. Details are not described again in this embodiment of this application. Optionally, in this embodiment of this application, step 606 may be performed without performing step 605. Alternatively, step 605 is performed before step 601. This is not limited in this embodiment of this application.

    [0302] Step 606: The session management function device 102 sends a charging request to the charging processing device 101, where the charging request may be a charging request for the user service, or may be a charging request for another service used by the user. In addition, the charging request may be an initial charging request (that is, the first charging request for a user to use a service), or may be an update charging request after the initial charging request. This is not limited in this embodiment of the present invention.

    [0303] Further, the charging request carries the first SRQM information of the user service, to indicate an SRQM currently used by the user service (for example, a service B). In this embodiment of this application, an example in which the first SRQM of the user service is suspend quota management is used for description. To be specific, the first SRQM information of the user service B carried in the charging request is suspend quota management. It indicates that the session management function device 102 does not request the charging processing device 101 for a quota in a service execution process, and allows a data flow related to the user service B to pass.

    [0304] Step 607: The charging processing device 101 performs corresponding charging processing based on the charging request, and then sends a charging response to the session management function device 102.

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

    [0306] Specifically, in a process of performing step 607, the charging processing device 101 determines, based on the first SRQM information of the user service carried in the charging request, that the user service uses suspend quota management (Suspending). When determining that the user account does not meet a condition for the user service to use suspend quota management, the charging processing device 101 determines that the second quota management mode (the second SRQM in this embodiment) of the user service is resume quota management, or forbids the user service to use suspend quota management. The condition for the user service to use suspend quota management may be as follows: A package balance of the user account is greater than a first threshold, or a decrease speed of the balance of the user account is lower than a second threshold, or the like.

    [0307] Further, when determining to change suspend quota management of the user service to resume quota management, the charging processing device 101 may further determine to change suspend quota management of another service of the user to resume quota management, or determine to forbid another service of the user to use suspend quota management, or forbid all services of the user to use suspend quota management.

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

    [0309] Step 609: The charging processing device 101 sends a notification message (also referred to as a change notification) of changing the first SRQM related information of the user service to the policy control device 104, so that the policy control device 104 generates or updates the control policy of the user service based on the change notification.

    [0310] Specifically, descriptions of step 609 are consistent with the descriptions of step 555. Details are not described herein again in this embodiment of the present invention.

    [0311] Descriptions of steps 610 and 611 are consistent with descriptions of steps 556 and 557. Details are not described again in this embodiment of the present invention.

    [0312] According to this embodiment of this application, the policy control device 104 determines, based on the obtained related information of the user, whether the user service can use the non-blocking mode. In addition, in the process of using the user service, the SRQM of the user service is determined or changed based on the account information of the user. Therefore, the SRQM of the user service is more accurate, and risks and losses caused by the use of the non-blocking mode in the process of using the user service can be avoided.

    [0313] FIG. 7 is a diagram of a hardware structure of a session management function device 102, a charging processing device 101, or a policy control device 104 according to an embodiment of this application. The session management function device 102 (for example, 102 in FIG. 1A), the charging processing device 101 (for example, 101 in FIG. 1A), and the policy control device 104 (for example, the policy control device 104 in FIG. 1A) in this embodiment of this application may all be implemented by using a general-purpose computer hardware structure shown in FIG. 7, including 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.

    [0314] Specifically, the memory 702 may include a computer storage medium in a form of a volatile memory and/or a non-volatile memory, for example, a read-only memory and/or a random access memory. The memory 702 may store an operating system, an application program, another program module, executable code, and program data.

    [0315] The input device 704 may be configured to enter information, so that a system administrator operates and manages the session management function device, the charging processing device 101, or the policy control device 104. For example, a user account risk threshold is configured on the charging processing device 101, storage space of quota management mode indication information is managed on the session management function device, and storage space of quota management mode indication information is managed on the policy control device 104. The input device 704 may be a keyboard or a pointing device, such as a mouse, a trackball, a touchpad, a scanner, or a similar device, and may be connected to the processor 701 by using the bus 703.

    [0316] The output device 705 may be configured to output information, so that the system administrator operates and manages the session management function device, the charging processing device 101, or the policy control device 104. For example, the user account risk threshold is displayed on the charging processing device 101, remaining storage space is displayed on the session management function device, or remaining storage space is displayed on the policy control device 104. In addition to a monitor, the output device 705 may be another peripheral output device, or may be connected to the processor 701 by using the bus 703.

    [0317] The session management function device 102, the charging processing device 101, or the policy control device 104 may all be connected to a network by using the network interface 706, for example, connected to a local area network (Local Area Network, LAN). In a network connection environment, a computer-executable instruction stored in the session management function device, the charging processing device 101, or the policy control device 104 may be stored in a remote storage device, but is not limited to being stored locally.

    [0318] When the processor 701 in the session management function device 102 executes the executable code or the application program stored in the memory 702, the session management function device 102 may perform method steps corresponding to the session management function device 102 in all the foregoing embodiments, for example, steps 206, 310, 351, 332, 353, 357, 404, 405, 406, 407, 411, 310, 351, 332, 353, 357, 604, 605, 606, 607, and 611. For a specific execution process, refer to the foregoing embodiments. Details are not described herein again.

    [0319] When the processor 701 in the charging processing device 101 executes the executable code or the application program stored in the memory 702, the charging processing device 101 may perform method steps corresponding to the charging processing device 101 in all the foregoing embodiments, for example, steps 208, 302, 304, 306, 352 to 355, 401, 402, 406 to 409, 502, 504, 506, 552 to 555, 601, 602, and 606 to 609. For a specific execution process, refer to the foregoing embodiments. Details are not described herein again.

    [0320] When the processor 701 in the policy control device 104 executes the executable code or the application program stored in the memory 702, the policy control device 104 may perform method steps corresponding to the policy control device 104 in all the foregoing embodiments, for example, steps 202 to 212, 300 to 302, 306 to 310, 355 to 357, 401 to 404, 409 to 411, 500 to 502, 506 to 510, 555 to 557, 5501 to 504, and 509 to 511. For a specific execution process, refer to the foregoing embodiments. Details are not described herein again.

    [0321] It should be noted that some of the foregoing steps are performed by two devices because one device performs sending and the other device performs receiving. 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.

    [0322] FIG. 8 is a schematic diagram of a logical structure of a charging processing device 101 according to an embodiment of this application. The charging processing device 101 (101) is configured to: determine that a first quota management mode of a user service needs to be changed, and send a notification message to a policy control device 104, where the notification message carries related information of a second quota management mode of the user service, and the second quota management mode is for changing the first quota management mode. The charging processing device 101 includes: [0323] a processing module 802, configured to determine that the first quota management mode of the user service needs to be changed to the second quota management mode, where the processing module 802 is mainly configured to perform steps such as processing and determining performed by the charging processing device 101 in the foregoing embodiment, for example, steps 208, 304, 354, 408, 504, 554, and 608; and [0324] a sending module 803, configured to send a notification message to the policy control device 104, where the notification message carries related information of the second quota management mode of the user service, and the second quota management mode is for changing the first quota management mode. The sending module 803 is mainly configured to perform sending steps on the charging processing device 101 side in the foregoing embodiments, for example, steps 208, 306, 353, 355, 402, 407, 409, 506, 553, 555, 602, 607, and 609.

    [0325] 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 perform receiving steps on the charging processing device 101 side in the foregoing embodiments, for example, steps 302, 352, 401, 406, 502, 552, 601, and 606.

    [0326] FIG. 9 is a schematic diagram of a logical structure of a policy control device 104 (104) according to an embodiment of this application. The policy control device 104 (104) is configured to determine a policy for a user service. The policy control device 104 (104) includes: [0327] a receiving module 901, configured to receive the related information of a second quota management mode that is sent by a charging processing device 101 and that is for changing a first quota management mode, where the receiving module 901 is mainly configured to perform receiving steps performed by the policy control device 104 in the foregoing embodiments, for example, steps 208, 306, 355, 402, 409, 506, 555, 602, and 609; [0328] a processing module 902, configured to: determine the first quota management mode of the user service, generate a first policy of the user service based on the first quota management mode, determine the second quota management mode based on the related information of the second quota management mode of the user service, and generate a second policy of the user service based on the second quota management mode, where the second policy is for updating or replacing the first policy, where the processing module 902 is mainly configured to perform steps of determining, processing, and generating policies performed by the policy control device 104 in the foregoing embodiments, for example, steps 202 to 204, 210 to 212, 304, 354, 403, 410, 504, 554, 603, and 610; and [0329] a sending module 903, configured to send the first policy to a session management function device 102, to indicate the session management function device 102 to perform the first quota management mode on the user service, where the sending module 903 is mainly configured to perform sending steps performed by the policy control device 104 in the foregoing embodiments, for example, steps 206, 302, 310, 357, 401, 404, 411, 502, 510, 557, 601, 604, and 611.

    [0330] The charging processing device 101 shown in FIG. 8 and the policy control device 104 shown in FIG. 9 are presented in a form of functional modules. The “module” herein may be an application-specific integrated circuit (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 another device that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that these devices may alternatively be in the form shown in FIG. 6. 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 may all be implemented by using the processor 701 and the memory 702 in FIG. 6. For example, the embodiments are implemented by executing code stored in the memory 702 by the processor 701.

    [0331] A person of ordinary skill in the art may be aware that, in combination with the examples described in embodiments disclosed in this specification, units and algorithm steps can be implemented by electronic hardware, computer software, or a combination thereof. To clearly describe the interchangeability between the hardware and the software, the foregoing has generally described compositions and steps of each example according to functions. Whether the functions are executed by hardware or software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application.

    [0332] It may be clearly understood by a person of ordinary skill in the art that, for ease and brief description, for a detailed working process of the foregoing system, apparatus and units, refer to a corresponding process in the foregoing method embodiments, and details are not described herein again.

    [0333] In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the unit division is merely logical function division and may be other division in actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or may not be performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.

    [0334] The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, in other words, may be located in one position, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual requirements to achieve the objectives of the solutions of embodiments in this application.

    [0335] In addition, functional units in embodiments of this application may be integrated into one processing unit, each of the units may exist alone physically, or two or more units may be integrated into one unit. The integrated unit may be implemented in a form of hardware, or may be implemented in a form of a software functional unit.

    [0336] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such an understanding, technical solutions of this application essentially, or a part contributing to the current technology, or all or some of the technical solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the method in embodiments of this application. The foregoing storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disc.

    [0337] The foregoing descriptions are merely specific implementations of this application, but are not intended to limit the protection scope of this application. Any modification or replacement readily figured out by a person skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.