WO2021197278A1 - 处理用户业务的方法、系统及相关设备 - Google Patents

处理用户业务的方法、系统及相关设备 Download PDF

Info

Publication number
WO2021197278A1
WO2021197278A1 PCT/CN2021/083671 CN2021083671W WO2021197278A1 WO 2021197278 A1 WO2021197278 A1 WO 2021197278A1 CN 2021083671 W CN2021083671 W CN 2021083671W WO 2021197278 A1 WO2021197278 A1 WO 2021197278A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
user service
initial
application mode
quota application
Prior art date
Application number
PCT/CN2021/083671
Other languages
English (en)
French (fr)
Inventor
柴晓前
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21781325.2A priority Critical patent/EP4120705A4/en
Publication of WO2021197278A1 publication Critical patent/WO2021197278A1/zh
Priority to US17/959,045 priority patent/US20230045030A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/785—Reserving amount on the account
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/852—Low balance or limit reached
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/853—Calculate maximum communication time or volume
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/854—Available credit
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/88—Provision for limiting connection, or expenditure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • This application relates to the field of communications, and in particular to a method, system and related equipment for processing user services in a charging system.
  • charging trigger function (Charging Trigger Functiong, CTF) devices usually use blocking mode initial quota application for user services.
  • CTF devices need to be Before the user’s business starts, apply for a quota. This will help reduce credit control risks and reduce the possibility of operators suffering losses, but it will not only increase the amount of equipment including CTF equipment and billing processing function (CHF) equipment.
  • CHF billing processing function
  • the performance burden of the operator's billing system will also increase the access delay of user services, affect the provision of delay-sensitive services, and thereby affect user experience.
  • the delay-sensitive services supported by 5G (5th Generation) networks such as uRLLC (ultra High-Reliability and Low-Latency Communication, ultra-high reliability and low-latency communication) services, have a greater impact on access latency. High demands.
  • the 3GPP standard specification defines the initial quota application in the non-blocking mode, which is characterized in that the CTF device starts the user service at the same time or after applying for the quota, which is beneficial to reduce the access delay of the user service.
  • 5G networks can support more and more user services.
  • some services have extremely high requirements on the network. If the service is interrupted due to the network, it may cause serious consequences, such as: driverless business, telemedicine business, industrial control business, etc.
  • This application refers to this type of business as uninterruptible business; some businesses will not have serious consequences even if the business is interrupted due to network reasons, such as VR (Virtual Reality) business, AR (Augment Reality, augmented reality) Services, etc., this application refers to such services as interruptible services.
  • the initial quota application that blindly adopts non-blocking mode has the following problems:
  • the CTF device may find that the quota application fails after starting user services, and at this time, the CTF device cannot arbitrarily interrupt it.
  • the CTF device can only continue to allow the user service, and if it consumes the operator's network resources, it may cause losses to the operator;
  • the CTF device may also find that the quota is obtained after the user's service starts. Failure, although the service can be interrupted at this time, on the one hand, this will affect the user experience. On the other hand, malicious users may use this mechanism to perform DoS (Denial of Service) attacks on the network.
  • DoS Delivery of Service
  • an embodiment of the present application provides a charging system.
  • the charging system includes a charging processing device (101) and a charging triggering device (102), wherein:
  • the charging trigger device (102) is configured to send initial quota application mode indication information to the charging processing device (101), where the initial quota application mode indication information indicates that the charging trigger device (102) is receiving The first initial quota application mode is adopted for the user service when the first request for the user service is started;
  • the charging processing device (101) is configured to obtain the indication information of the initial quota application mode, and send the charging processing result to the charging trigger device (102), and the charging processing result is based on the initial quota application mode.
  • Quota application mode indication information is the result of charging the user service;
  • the charging trigger device (102) is further configured to process the user service based on the charging processing result.
  • the charging system changes the coordination relationship between the charging triggering device and the charging processing device.
  • the charging processing device can combine the charging triggering device to perform charging processing on the initial quota application mode adopted by the user service, so that The billing process is more context-sensitive so that you can get more practical billing processing results.
  • the billing trigger device can process user services based on the more context-sensitive billing processing results. In this way, billing The processing device and the charging trigger device can be combined to solve the current problems caused by the unilateral use of the initial quota application mode by the CTF device.
  • the charging trigger device (102) is further configured to: when the first start request is received, the first initial quota application mode is adopted for the user service, and the accounting
  • the charging processing device (101) sends an initial charging request message for the user service, where the initial charging request message contains the indication information of the initial quota application mode; the charging processing device (101) is also used to: Obtain the indication information of the initial quota application mode in the initial charging request message.
  • the charging processing device (101) is further configured to send a charging processing result including any one of the following to the charging triggering device (102): used to indicate the charging An indication parameter for the triggering device (102) to suspend quota management of the user service, or an indication parameter for instructing the charging triggering device (102) to interrupt the user service.
  • the charging processing device (101) is also used to determine that the charging trigger device (102) needs to be suspended when the first initial quota application mode is a non-blocking mode.
  • the charging processing result including the indication parameter for instructing the charging triggering device (102) to suspend the quota management of the user service is sent to the charging triggering device (102), so The charging trigger device (102) is also used to suspend quota management of the user service.
  • the charging processing device (101) is further configured to send to the charging triggering device (102) a second start request that is used to instruct the charging triggering device to receive the user service.
  • the second start request occurs later than the first start request.
  • an embodiment of the present application provides a method for processing user services.
  • the method is applied to a charging processing device (101), and the method includes:
  • the indication information of the initial quota application mode indicates that the charging trigger device (102) adopted the first initial request for the user service when receiving the first start request of the user service.
  • the charging processing result is a result of performing charging processing on the user service based on the initial quota application mode indication information.
  • the charging processing device (101) obtains the initial quota application mode indication information through an initial charging request message.
  • the charging processing device (101) obtains the indication information of the initial quota application mode through a mid-term charging request message.
  • the charging processing device (101) obtains the initial quota application mode indication information based on the charging policy sent by the policy control device, and the charging policy includes the initial quota application mode of the user service .
  • the charging processing device (101) sends a charging processing result including any one of the following through an initial charging response message of the user service:
  • An indication parameter used to instruct the charging trigger device (102) to suspend quota management of the user service or
  • the charging processing device (101) sends a charging processing result including any one of the following through a mid-term charging response message of the user service or through a notification message:
  • An indication parameter used to instruct the charging trigger device (102) to suspend quota management of the user service or
  • the charging processing result includes quota management for instructing the charging triggering device (102) to suspend the user service
  • the indication parameter of the user service based on the indication information of the initial quota application mode includes: authorization of the user service fails, and based on the indication information of the initial quota application mode, it is determined that the accounting is required
  • the fee triggering device (102) suspends the quota management of the user service.
  • the first initial quota application mode is a non-blocking mode, and it is determined that the charging trigger device (102) needs to be converted to offline charging from the user service (from online charging) At this time, sending to the charging triggering device (102) a charging processing result including an indication parameter for instructing the charging triggering device (102) to convert the user service to offline charging.
  • the The charging triggering device (102) sends a charging processing result including an indication parameter for instructing the charging triggering device (102) to use unlimited quota management for the user service.
  • the charging trigger device (102) when the first initial quota application mode is a non-blocking mode, and it is determined that the charging trigger device (102) needs to be changed to the initial quota application in the blocking mode for the user service Next, send to the charging triggering device (102) a charging processing result including an indication parameter for instructing the charging triggering device (102) to adopt a blocking mode for the initial quota application for the user service.
  • the first initial quota application mode is a non-blocking mode, and it is determined that the charging trigger device (102) needs to be changed to the blocking mode initial quota application for the user service and the determination
  • the charging processing result including the following is sent to the charging triggering device (102):
  • the charging processing device (101) instructs the charging trigger device to include the granted quota in the mid-term charging response message corresponding to the mid-term charging request message that does not contain quota application information. (102) Restore quota management for the user service.
  • the charging processing result includes an indication parameter for instructing the charging triggering device (102) to interrupt the user service
  • the performing charging processing on the user service based on the initial quota application mode indication information includes: failing to authorize the user service, and determining, based on the initial quota application mode indication information, that the charging processing device ( 101) Interrupt the user service.
  • the method further includes:
  • the quota-free usage of the user service is received from the charging trigger device (102).
  • the charging trigger device (102) needs to be changed to the non-blocking mode initial quota application for the user service
  • the first initial quota application mode is the blocking mode, and it is determined that the charging trigger device (102) needs to be changed to the non-blocking mode initial quota application for the user service and the determination
  • the charging triggering device (102) has not suspended or is performing the quota management of the user service, it sends the charging processing result including the following to the charging triggering device (102):
  • the charging processing result further includes an indication parameter for instructing the charging trigger device to adopt the second initial quota application mode for the user service when receiving the second start request of the user service ,
  • the second start request occurs later than the first start request.
  • the first initial quota application mode is a non-blocking mode
  • the second initial quota application mode is a blocking mode
  • the first initial quota application mode is a blocking mode
  • the second initial quota application mode is a blocking mode.
  • the initial quota application mode is non-blocking mode.
  • the charging processing of the user service based on the indication information of the initial quota application mode is triggered by an initial charging request message of the user service, and a corresponding initial charging response message is sent to all users.
  • the charging trigger device (102) sends the charging processing result.
  • the charging processing of the user service based on the indication information of the initial quota application mode is triggered by a mid-term charging request message of the user service, and a corresponding mid-term charging response message is sent to all users.
  • the charging trigger device (102) sends the charging processing result.
  • the charging processing of the user service based on the indication information of the initial quota application mode is triggered by other charging request messages or account management messages, and the other charging request messages are other user services
  • the charging request message of the other user service corresponds to the same account as the user service
  • the account management message is a management message of the account corresponding to the user service
  • the charging trigger device (101 ) Send the charging processing result.
  • the charging processing device (101) also records or saves the initial quota application mode of the user service based on the initial quota application mode indication information.
  • an embodiment of the present application provides a method for processing user services, which is applied to a charging trigger device (102), and the method includes:
  • the charging processing device (101) Send the initial quota application mode indication information of the user service to the charging processing device (101), where the initial quota application mode indication information indicates that when the charging trigger device (102) receives the first start request of the user service Adopting the first initial quota application mode for the user service;
  • the sending of indication information of the initial quota application mode of the user service to the charging processing device (101) is specifically as follows:
  • the charging triggering device (102) also sends the initial quota application mode indication information to the charging processing device (101) in the mid-term charging request message.
  • the charging processing result includes any one of the following:
  • An indication parameter used to instruct the charging trigger device (102) to suspend quota management of the user service or
  • the user instructs the charging trigger device (102) to resume the indication parameter of the quota management of the user service, or
  • the charging processing result includes an indication parameter for instructing the charging trigger device (102) to suspend quota management of the user service, and the charging processing result is based on the charging processing result.
  • Describes user services including:
  • the charging processing result includes an indication parameter for instructing the charging trigger device (102) to resume quota management of the user service, and the processing of the charging processing result is based on the charging processing result.
  • User services including:
  • the charging processing device (102) sends a response message corresponding to the mid-term charging request message from the charging processing device ( 101)
  • the charging processing result is received, the charging processing result includes the quota granted by the charging processing device (101) for the user service, and the mid-term charging response message is based on the charging
  • the processing result processing the user service includes:
  • the charging processing result includes an indication parameter for instructing the charging trigger device (102) to interrupt the user service, and the processing the user service based on the charging processing result, include:
  • the user service is interrupted, and the quota-free usage of the user service is sent to the charging processing device (101).
  • the charging processing result further includes an indication parameter for instructing the charging trigger device to adopt the second initial quota application mode for the user service when receiving the second start request of the user service ,
  • the second start request occurs later than the first start request
  • the processing of the user service based on the charging processing result further includes:
  • the initial quota application mode of the user service is updated to the second initial quota application mode.
  • the charging trigger device (102) receives the charging processing result through the initial charging response message of the user service; or receives the charging processing result through the mid-term charging response message of the user service. Charging processing result; or receiving the charging processing result through a notification message.
  • the processing the user service based on the charging processing result includes:
  • the initial quota application mode of the user service is updated to the second initial quota application mode.
  • the charging triggering device (102) is used to instruct the charging triggering device (102) to change the initial quota application mode of the user service to all according to the charging processing result.
  • the indication parameter of the second initial quota application mode updates the initial quota application mode of the user service to the second initial quota application mode.
  • the charging trigger device (102) updates the initial quota application mode of the user service to the second initial quota application according to the information related to the quota granted in the charging processing result model.
  • the updating the initial quota application mode of the user service to the second initial quota application mode includes:
  • the first initial quota application mode is a non-blocking mode
  • the second initial quota application mode is a blocking mode
  • the first initial quota application mode is a blocking mode
  • the second initial quota application mode is a blocking mode.
  • the initial quota application mode is non-blocking mode.
  • an embodiment of the present application provides a charging processing device (101), including an obtaining module (701) and a sending module (702), wherein:
  • the obtaining module (701) is configured to obtain indication information of the initial quota application mode of the user service, where the indication information of the initial quota application mode indicates that the charging trigger device (102) receives the first start request of the user service Adopting the first initial quota application mode for the user service;
  • the sending module (702) is configured to send a charging processing result to the charging trigger device (102), where the charging processing result is charging the user service based on the initial quota application mode indication information The result of processing.
  • the acquisition module (701) is also used to:
  • the sending module is also used to:
  • An indication parameter used to instruct the charging trigger device (102) to suspend quota management of the user service or
  • the sending module is also used to:
  • an indication parameter for instructing the charging trigger device to adopt the second initial quota application mode for the user service upon receiving the second start request of the user service is generated, and the indication parameter is The parameter is included in the charging processing result, and the second start request occurs later than the first start request.
  • an embodiment of the present application provides a charging trigger device (102), including a sending module (801), a receiving module (802), and a processing module (803), wherein:
  • the sending module (801) is configured to send initial quota application mode indication information of the user service to the charging processing device (101), where the initial quota application mode indication information indicates that the charging trigger device (102) is receiving The first initial quota application mode is adopted for the user service when the user service is first requested;
  • the receiving module (802) is configured to: receive the charging processing result of the user service from the charging processing device (101);
  • the processing module (803) is configured to process the user service based on the charging processing result.
  • the sending module is also used to:
  • the receiving module (802) is further configured to receive from the charging processing device (101) including quota management for instructing the charging trigger device (102) to suspend the user service
  • the processing module (803) is also used to suspend the quota management of the user service; or the receiving module (802) is also used to receive the charging processing result from the charging processing device (101).
  • Receiving a charging processing result including an indication parameter used to instruct the charging trigger device (102) to interrupt the user service and the processing module (803) is further configured to interrupt the user service.
  • the receiving module (802) is further configured to receive information from the charging processing device (101) that is used to instruct the charging triggering device to respond to the second start request of the user service.
  • the user service adopts the charging processing result of the indication parameter of the second initial quota application mode, the second start request occurs later than the first start request, and the processing module (803) is further configured to transfer the user
  • the initial quota application mode of the service is updated to the second initial quota application mode.
  • an embodiment of the present application provides a charging processing device (101), including a processor and a memory, wherein:
  • the memory is used to store program instructions
  • the processor is configured to call and execute program instructions stored in the memory, so that the billing processing device (101) executes the user service processing in the second aspect or any possible solution in the second aspect method.
  • an embodiment of the present application provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to perform the processing in the second aspect or any possible solution in the second aspect The method of user business.
  • an embodiment of the present application provides a charging trigger device (102), including a processor and a memory, wherein:
  • the memory is used to store program instructions
  • the processor is configured to call and execute the program instructions stored in the memory, so that the charging trigger device (102) executes the user service processing in the third aspect or any possible solution in the third aspect method.
  • an embodiment of the present application provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to perform the processing in the third aspect or any possible solution in the third aspect The method of user business.
  • an embodiment of the present application provides a method for processing user services, which is applied to a policy control device (104), and the method includes:
  • the initial quota application mode indication information of the user service is received from the charging triggering device (102), where the indication information is indication information that prohibits the use of the first initial quota application mode for the user service, or an indication Instruction information for changing the initial quota application mode corresponding to the user service to the second initial quota application mode;
  • an embodiment of the present application provides a chip that is used to implement any possible implementation solutions of the second aspect, the third aspect, and the second aspect or any possible implementation of the third aspect when the chip is running. The way to implement the program.
  • Fig. 1 is an architecture diagram of a charging system provided by an embodiment of the application
  • Figure 2 is a flowchart of a method for processing user services provided by an embodiment of the application
  • 3A is a flowchart of a first method for a charging processing device to process user services through an initial charging response message according to an embodiment of the application;
  • 3B is a flowchart of the first method for the charging processing device to process user services through mid-term charging response messages according to an embodiment of the application;
  • 3C is a flowchart of a second method for the charging processing device to process user services through initial charging response messages according to an embodiment of the application;
  • 3D is a flowchart of a second method for the charging processing device to process user services through mid-term charging response messages according to an embodiment of the application;
  • 4A is a flowchart of the first method for the charging processing device to process user services through notification messages according to an embodiment of the application;
  • 4B is a flowchart of a second method for the charging processing device to process user services through notification messages according to an embodiment of the application;
  • 5A is a flowchart of a first method for a charging trigger device to process user services based on a charging processing result according to an embodiment of this application;
  • FIG. 5B is a flowchart of a second method for the charging trigger device to process user services based on the quota grant result according to an embodiment of the application;
  • FIG. 6 is a schematic diagram of the hardware structure of a charging trigger device, a charging processing device, or a policy control device provided by an embodiment of the application;
  • FIG. 7 is a schematic diagram of a logical structure of a charging processing device provided by an embodiment of the application.
  • FIG. 8 is a schematic diagram of a logical structure of a charging trigger device provided by an embodiment of the application.
  • FIG. 9 is a schematic diagram of the logical structure of a policy control device provided by an embodiment of the application.
  • At least one item (a) refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • words such as “first” and “second” are used to distinguish the same or similar items with substantially the same function and effect. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and order of execution, and words such as “first” and “second” do not limit the difference.
  • FIG. 1 is an architecture diagram of a charging system provided by an embodiment of the application, which is used to control a charging triggering device to process user services, including a charging processing device 101, a charging triggering device 102, and a user equipment 103.
  • a charging processing device 101 a charging processing device 101
  • a charging triggering device 102 a charging triggering device 102
  • a user equipment 103 a user equipment 103
  • policy control device 104 the main functions of these devices are described as follows.
  • Charging processing device 101 connected to charging triggering devices (including charging triggering device 102 and other charging triggering devices not shown in Figure 1), except for receiving quota application information and usage information reported by the charging triggering device , According to this, the user service is charged, and the initial quota application mode of the user service reported by the device is triggered according to the charging, and according to the relevant information of the user service, such as user type, customer information, account balance, The business whitelist, business blacklist, account balance change trend, remaining validity period of the package, etc. are charged, and the charging processing result is sent to the charging triggering device, so that the charging triggering device adjusts the performance of the user service Billing operation.
  • charging triggering devices including charging triggering device 102 and other charging triggering devices not shown in Figure 1
  • the user service is charged, and the initial quota application mode of the user service reported by the device is triggered according to the charging, and according to the relevant information of the user service, such as user type, customer information, account balance, The business whitelist, business blacklist, account
  • the charging processing device 101 may be a CHF (Charging Function) device defined by the 3GPP standard specification, or may be a CCS (Converged Charging System) device defined by the 3GPP standard specification, which includes the CHF device Function.
  • CHF Charging Function
  • CCS Converged Charging System
  • the charging system shown in Figure 1 can have more charging processing equipment, for example, a cluster can be constructed that contains multiple charging processing equipment, which are mutually backed up, thereby improving disaster tolerance. , To achieve high availability.
  • the charging processing device is directly referred to as the CHF device.
  • Charging trigger device 102 connected to the charging processing device 101, the policy control device 104 (if any), and the user equipment 103, the device can be used for:
  • a user service start request (that is, a request message for requesting the charging trigger device to start the user service) from the user equipment 103, and start the user service according to the start request, and perform the user service Billing operations such as quota management and usage reporting;
  • the initial quota application mode of the user service can be shared among multiple charging triggering devices, which can reduce synchronization and interaction between different charging triggering devices, and can also reduce its own storage burden.
  • the charging trigger device 102 may be a CTF device defined by the 3GPP standard specification.
  • the function of the charging trigger device 102 can be deployed in the SMF (Session Management Function) device defined in the 3GPP specification; when the user service is a voice service, the charging trigger device
  • the function of 102 can be deployed in AS (Application Server) or CSCF (call session control function, call session control function) equipment in IMS (IP Multimedia Sub-system).
  • AS Application Server
  • CSCF call session control function, call session control function
  • IMS IP Multimedia Sub-system
  • the charging system shown in FIG. 1 can have more charging trigger devices, which can be connected to the same charging processing device (such as the charging processing device 101), or they can be connected to different Charging processing equipment, multiple service start requests initiated by the same user equipment for the same user service may be processed by the same or different charging triggering equipment.
  • the charging trigger device is sometimes referred to as a CTF device in the embodiments of the present application.
  • User equipment 103 connected to a charging triggering device (charging triggering device 102 or other charging triggering devices not shown in Figure 1), and used to send a user service start request to the charging triggering device and trigger the device through charging Access or use user services.
  • a charging triggering device charging triggering device 102 or other charging triggering devices not shown in Figure 1
  • the user equipment 103 may be a user equipment (UE) defined by the 3GPP standard specifications, and may be a wireless access device with wireless communication function or a wired access device without wireless communication function, including handheld devices, vehicle-mounted devices, A wearable device or a computing device; for example, it may be a mobile phone, a tablet computer, or a computer with wireless transceiver function; the user equipment 103 may also be a virtual reality (VR) terminal device, augmented reality (augmented reality) Reality, AR) terminal equipment, wireless terminals in industrial control, wireless terminals in unmanned driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in smart cities, smart homes ( Wireless terminals in smart home), etc.
  • UE user equipment
  • Policy control device 104 connected to a charging triggering device (charging triggering device 102 or other charging triggering devices not shown in FIG. 1), and used to provide a charging strategy for user services to the charging triggering device, and also to provide The charging trigger device provides an initial quota application mode corresponding to a certain user service.
  • a charging triggering device charging triggering device 102 or other charging triggering devices not shown in FIG. 1
  • the charging trigger device provides an initial quota application mode corresponding to a certain user service.
  • the policy control device 104 may be a policy control function (Policy Control Function, PCF) device defined in the 3GPP standard specifications, or a policy and charging rules function (Policy and Charging rules Function, PCRF) device.
  • Policy Control Function Policy Control Function
  • PCRF Policy and Charging rules Function
  • the charging trigger device is sometimes directly referred to as the CTF device in the embodiments of the present application.
  • connection includes direct connection or connection through one or more intermediate network devices.
  • the charging system architecture shown in Figure 1 can change the coordination relationship between the charging processing equipment and the charging triggering device, so that the charging operation of the charging triggering device for user services can be adjusted dynamically and on-demand, so as to achieve
  • the initial quota application in non-blocking mode is adopted when the credit control risk of the user business is low
  • the initial quota application in the blocking mode is adopted when the credit control risk of the user business is high
  • the use of the user business in the non-blocking mode Proper handling, such as suspension of quota management for user services or interruption of user services, can take into account the needs of user services for access delay, and the requirements of operators for system performance and credit risk control.
  • User services refer to services that the user equipment 103 accesses or uses through a charging triggering device (charging triggering device 102 or a charging triggering device not shown in Figure 1), including but not limited to:
  • Data connection services for example, one or more data streams corresponding to a certain rating group (RG) in a Protocol Data Unit (PDU) session, or a certain PDU session
  • the data stream corresponding to the RG and the service identifier can be understood as the user service in the embodiment of this application; in the embodiment of this application, "user service in a PDU session” and “service in a PDU session” refer to a certain number in the PDU session.
  • Multiple data streams corresponding to an RG may also be data streams corresponding to a certain service identifier among multiple data streams corresponding to a certain RG;
  • the user service is sometimes referred to as "service" for short.
  • the embodiment of the present application will mainly take the data connection service of the 5G network as an example; accordingly, regarding the charging data, the embodiment of the present application will mainly focus on the data flow-related
  • Information related to data traffic includes but is not limited to: information about PDU sessions collected by the charging trigger device, usage of released service units in the PDU session, charging trigger conditions, time stamps, etc. .
  • Starting a user service means that the charging trigger device releases the user service after receiving the start request of the user service, including the signaling or data to release the user service.
  • the user service is the above-mentioned data connection service
  • "Starting a user service” includes enabling the establishment or update operation of the PDU session for the data connection service to continue (if the PDU session is not available) or to let the service data flow (if the PDU session is already available).
  • Interrupting user services means that the charging triggering device (the charging triggering device 102 or the charging triggering device not shown in FIG. 1) stops allowing the user service.
  • the charging triggering device the charging triggering device 102 or the charging triggering device not shown in FIG. 1
  • interrupt "User service” includes the operation of disconnecting the data stream corresponding to the user service.
  • the initial quota request mode refers to the charging trigger device (the charging trigger device 102 or the charging trigger device not shown in Figure 1) for the first time after receiving the user's service start request
  • the business application quota mode mainly reflects the chronological relationship between the initial application of quota for the user’s business and the start of the user’s business after receiving the user’s business start request; according to whether the process of applying for the quota for the first time blocks the start of the user’s business, the initial Quota application modes can be divided into blocking mode and non-blocking mode; therefore, the initial quota application is divided into "blocking mode initial quota application" and "non-blocking initial quota application", which are described as follows:
  • Blocking Mode Initial Quota Request means that the charging triggering device (the charging triggering device 102 or the charging triggering device not shown in Figure 1) responds to the user service received from the user equipment 103
  • the charging triggering device the charging triggering device 102 or the charging triggering device not shown in Figure 1
  • For the start request of the user service first apply for a quota to the charging processing device 101 for the user service, and start the user service only after receiving the quota granted by the charging processing device for the user service.
  • the initial quota request in non-blocking mode means that the charging triggering device (the charging triggering device 102 or the charging triggering device not shown in Figure 1) responds to the receipt from the user equipment 103
  • the user service start request does not give priority to the application of quota for the user service from the charging processing device 101, but the priority is to start the user service, or to charge the user service at the same time as the user service is started
  • the processing device 101 applies for a quota, that is, the operation of starting the user service does not depend on the quota granted by the charging processing device 101 for the user service.
  • the charging trigger device has released the user service when receiving the quota granted by the charging processing device 101 for the user service, in most scenarios, especially in the user account corresponding to the user service
  • the charging trigger device can receive the quota granted by the charging processing device 101, so it can deduct the granted service usage from the granted quota and pass it through the service in the subsequent charging request message
  • the used service unit (USU) is reported to the billing processing device 101.
  • the reliability of this mechanism is limited, because the account information corresponding to the user's business changes dynamically. When the balance in the account is lower than a certain threshold, or the tariff package corresponding to the account changes, it will still be used blindly. The initial quota application in non-blocking mode may cause serious credit control risks.
  • the charging triggering device After the charging triggering device receives the indication information of the initial quota application of a certain mode that it decides to adopt from the charging processing device 101, if the corresponding user service has already started, the charging triggering device will receive the The initial quota application of this mode is only applied to the user service when the user service starts to request next time, instead of being applied immediately.
  • the initial quota request mode indication information indicates that the charging trigger device (the charging trigger device 102 or the charging trigger device not shown in Figure 1) responds to all users when receiving a user service start request.
  • the requirements of the initial quota application mode refer to the conditions that should be met in order for the charging trigger device to adopt the initial quota application mode for the user service, the attribute information of the user service, the account corresponding to the user service, and the like.
  • the requirement of non-blocking mode can be "user service is delay-sensitive business, has been continuously ordered for more than 12 months, and the account balance exceeds 1,000 yuan", while the requirement of blocking mode can be "user service is non-delay sensitive Business, the account balance is less than 100 yuan”.
  • the requirements of the initial quota application mode are not limited to the requirements for the attribute information of the user's business and the account corresponding to the user's business, and can be pre-configured by the operator, or jointly determined by the operator and the user.
  • this application implements The examples are not limited.
  • a certain initial quota application mode for a certain user service is sometimes described as "a certain mode of initial quota application for a certain user service”.
  • the charging trigger device in the method flow corresponds to the charging trigger device 102 in FIG. 1
  • the charging processing device corresponds to the charging processing device 101 in FIG. 1
  • the user equipment corresponds to the user equipment 103 in FIG.
  • the control device (if present) corresponds to the policy control device 104 in FIG. 1, and will not be repeated in the description of the flow of these methods.
  • the charging trigger device changes the charging operation for the user service based on the charging processing result sent by the charging processing device.
  • the method flow mainly includes the following steps:
  • Step 210 The charging trigger device sends the initial quota application mode indication information of the user service to the charging processing device, or the charging processing device obtains the initial quota application mode indication information.
  • this step can be said to be that the charging triggering device sends the initial quota application mode indication information to the charging processing device, or it can be said that the charging processing device obtains the initial quota application mode indication information, the latter including:
  • the billing processing device directly reads the initial quota application mode indication information from the local storage facility, or reads the initial quota application mode of the user service from the local storage facility, and indirectly obtains the initial quota application mode indication information; or
  • the charging trigger device may send the initial quota application mode indication information to the charging processing device through an initial charging request message or a mid-term charging request message.
  • the initial charging request message refers to the first charging request message of the user service sent to the charging processing device by the charging triggering device after receiving the start request of the user service, which is mainly used for application Quota;
  • the initial charging request message of the user service is sometimes referred to as the initial charging request for short.
  • the mid-term charging request message refers to the subsequent charging request message of the user service sent after the charging triggering device sends the initial charging request message of the user service to the charging processing device, which can be used to apply for quota , Can also be used to report usage, and it can also be used to apply for quota and report usage; for the convenience of description, in the embodiments of this application, sometimes the mid-term charging request message for user services is sometimes referred to as mid-term charging. ask.
  • Step 220 The charging processing device sends the charging processing result obtained by performing charging and charging processing on the user service based on the initial quota application mode indication information to the charging triggering device.
  • the charging processing device performs charging processing on the user service based on the indication information of the initial quota application mode, and sends the charging processing result obtained by the charging processing to the charging triggering device.
  • the charging processing device can learn whether the current user service has started, and what mode of initial quota application mode the charging triggering device uses for the user service, so that the In the charging process, some attribute information of the user service can be further combined, for example, the type of user service (such as interruptibility), the charging process is performed, and the corresponding charging process result is generated.
  • the charging process result includes authorization As a result, indication parameters related to the initial quota application mode of the user service, etc., so that the charging trigger device can adjust the charging operation for the user service accordingly.
  • the authorization result may be information about the quota granted, such as the number of quotas granted, the reason for the failure of granting quotas, and so on.
  • the charging processing result includes “instruct the charging trigger device to start the next time it receives the user service
  • the indication parameter of the second initial quota application mode (here, the blocking mode" is used for the user service when requested.
  • the indication parameter may be an indication parameter indicating that the initial quota application in the non-blocking mode is disabled, or it may indicate a change
  • the initial quota application mode is the indication parameter of the blocking mode, so that the charging trigger device adopts the initial quota application in the blocking mode when receiving the next start request of the user service, thereby avoiding long-term credit control risks and network security risks (prevention DoS attack); on the other hand, when it is determined that the authorization fails, the billing processing device can further determine that the user service needs to be interrupted (for example, when the user service is judged to be interruptible, and it is judged to be an interruptible service), then The charging processing result includes the charging operation control instruction of "interrupting service", and if it is determined that the quota management of the user service needs to be suspended (for example, the user service is an uninterruptible service), then the charging operation The result further contains the charging operation control instruction of "suspended quota management".
  • the suspended quota management can be to convert the user's business to offline charging or to use an unlimited quota (that is, the charging trigger device will not be affected by the quota.
  • Quota application is triggered after the quota management is suspended.
  • real-time credit control of the user service cannot be performed after the quota management is suspended, the charging information of the user service can still be collected as the basis for subsequent charging processing, by indicating the mode based on the initial quota application
  • Information charging processing for authorization failures can take appropriate processing measures for user services, avoiding credit control risks and network security risks.
  • the charging processing result may include “instruct the charging trigger device to adopt the second initial quota application mode for the user service when receiving the next start request of the user service (here, non-blocking Mode)”.
  • the indication parameter may be an indication parameter for changing the initial quota application mode to non-blocking mode, or if the initial quota application mode of the user service is configured as non-blocking mode by default, and it has been previously
  • the indication parameter may be an indication parameter for restoring the non-blocking initial quota application mode configured by the user service default configuration, so that the charging trigger device starts the next time the user service is received.
  • a non-blocking mode initial quota application may be used for the user service to reduce the access delay of the user service.
  • the billing processing device may also include "suspended quota management" in the billing processing result (meaning that no quota management or restriction is performed on the user service before the end of the user service, unless it is received again.
  • the “recovery quota management” indication parameter sent by the charging processing device) is used to reduce the complicated credit control during the service use process and improve the system efficiency.
  • the billing processing equipment may also not include explicit indication parameters in the billing processing results. Instead, for example, by changing the number of granted quotas, the quotas granted multiple times will show an upward trend or a downward trend, so as to pass " The "implied" approach prompts the charging trigger device to adjust the initial quota application mode adopted for the user service.
  • Step 230 The charging trigger device processes the user service based on the charging processing result.
  • the charging trigger device receives the charging processing result from the charging processing device, and then processes the user service according to the charging processing result.
  • the charging processing result contains the indication parameter of "interrupting user service”
  • the user service is interrupted, and optionally, the previously recorded quota-free usage is reported to the charging processing device; if the charging processing result is If the indication parameter of "suspend quota management" is included, the quota management of the user service is suspended.
  • the user service may be converted to offline charging or to use unlimited quota management (ie: charging trigger The device will not trigger a quota application because the quota is exhausted); if the billing processing result contains "instruct the billing trigger device to use the second initial quota application for the user service when it receives the next start request of the user service Mode", then change the initial quota application mode of the user service; if the charging processing result does not include “instruct the charging trigger device to respond to the user service when it receives the next start request of the user service Using the indication parameters of the “second initial quota application mode”, the charging trigger device can be based on the authorization result contained in the charging processing result (such as the reason for the failure to grant quota, or the amount of quota granted which is much lower than the requested amount), It is further determined whether to change the initial quota application mode of the user service.
  • charging trigger device can be based on the authorization result contained in the charging processing result (such as the reason for the failure to grant quota, or the amount of quot
  • the charging trigger device may further determine whether to change the initial quota application mode of the user service according to the quota grant information included in the multiple charging processing results. For example, when it is known that the quota has been successfully granted many times before, and the current initial quota application mode is the blocking mode, the charging triggering device can determine that when receiving the next start request of the user service, the user service is changed to non- Initial quota application in blocking mode; for another example, if the number of quotas granted multiple times before shows a downward trend, and the current initial quota application mode is non-blocking mode, it can be determined that the next time the user service starts request is received The user service is changed to the initial quota application in the blocking mode.
  • the above-mentioned method flow corresponding to FIG. 2 enables the charging processing device to perform charging processing on the user service based on the initial quota application mode adopted by the charging trigger device for the user service, and to issue the corresponding charging processing result, so that
  • the charging trigger device processes the user service (mainly changing the charging operation for the user service), which helps to balance the terminal user's demand for access delay in real time and dynamically, and the operator's system performance and credit risk The relationship between the needs of control.
  • 3A to 3D are flowcharts of a method for a charging processing device to process user services through a charging response message according to an embodiment of the application, and the flow of these methods will be described below.
  • charging triggers the device to apply for the initial quota in the non-blocking mode (first mode) for user services, and then the charging processing device sends the charging control instruction through the initial charging response message to make the charging Trigger the device to adjust the charging operation, such as: suspending quota management of the user service, interrupting the user service, changing the user service to the initial quota application of the blocking mode (the second mode), etc.
  • the method flow mainly includes the following steps:
  • Step 301 The charging trigger device receives the start request StartReq31 of the user service.
  • the charging trigger device receives StartReq31 from the user equipment.
  • StartReq31 may be a request message for establishing a PDU session for the data service, or, if the PDU session has been established, it may be the initial data packet in the data stream of the data service .
  • the charging trigger device may obtain the initial quota application mode of the user service according to the configuration information of the user service stored in a local or external storage facility, and may also obtain the user service from the policy issued by the policy control device.
  • the initial quota application mode (for example, the initial quota application mode of the user service is obtained from the charging policy of the user service activated by the policy control device; or the user service does not currently have an activated charging policy, then the policy control The device requests the charging policy of the user service, and the policy control device returns the initial quota application mode of the user service as the charging policy of the user service to the charging trigger device, and the charging trigger device obtains the user service therefrom The initial quota application mode).
  • the flow of this method assumes that the initial quota application mode IqrMod adopted for the user service is non-blocking mode (NB).
  • Step 303 The charging trigger device starts the user service and records the quota-free usage NQUSU.
  • the charging trigger device can immediately start the user service without waiting for the result of the quota application in the subsequent steps; in addition, the charging trigger device starts recording the quota-free usage ⁇ NQUSU.
  • the quota-free usage volume refers to the service usage volume formed by allowing the user service to be released by the charging trigger device without the effective quota granted by the charging processing device for the user service. Taking 5G data service as an example, The quota-free usage is that the charging trigger device allows the data traffic formed by the 5G data service without the effective quota granted by the charging processing device for the 5G data service.
  • Step 304 The charging trigger device sends the initial charging request of the user service to the charging processing device, which includes quota application information RSU31 and initial quota application mode indication information IqrModInd31.
  • the charging trigger device sends the initial charging request message to the charging processing device, which includes quota application information RSU31 and an initial quota application mode indication
  • Quotas can be shared between different user services (for example, if a user service is a data stream corresponding to a certain service identifier among multiple data streams corresponding to a certain RG, multiple user services corresponding to the same rate group share the rate group’s Quotas), or exclusive quotas for user services (for example, if the user service is multiple data streams corresponding to a certain rate group, then the user service exclusively enjoys the quota of the rate group), corresponding to the charging requests in these two cases
  • Examples of the data structure of the message and the indication information of the initial quota application mode in the message are as follows.
  • the charging trigger device can report the initial quota application mode in the unit of the rate group (subsequent charging processing equipment also The initial quota application mode will be managed in units of rate groups), then an exemplary charging request message is:
  • MUU is the abbreviation of Multiple Unit Usage
  • RG is the abbreviation of Rating Group (rate group)
  • RSU is the abbreviation of Requested Service Unit (requested service usage), the same below.
  • Quotas are shared between different user services (for example, if the user service is a data stream corresponding to a certain service identifier among multiple data streams corresponding to a certain rate group, then multiple user services corresponding to the same rate group share the Rate group quota), as follows:
  • charging The trigger device determines that the IqrMod of Service1 is in blocking mode, and the IqrMod of Service2 is in non-blocking mode.
  • the charging trigger device When the charging trigger device receives the start request of Service2, if the charging trigger device already has the quota corresponding to the rate group (assuming that Service1 has started, the quota corresponding to the rate group is granted for Service1), then the charging is triggered The device directly uses the quota corresponding to the rate group for Service2. In this case, the billing trigger device does not use the non-blocking mode for Service2, and it does not report the initial quota application mode indication information adopted by Service2 or the reported Service2 to the billing processing device.
  • the initial quota application mode adopted is the blocking mode.
  • the charging triggering device When the charging triggering device receives the start request of Service2, if there is no quota corresponding to the rate group on the charging triggering device, the charging triggering device is the initial quota application of Service2 in the non-blocking mode, and then it applies to the charging processing device
  • the sent initial charging request message carries the indication information of "Service2 uses the initial quota application in non-blocking mode". Specifically, there are two methods for reporting the initial quota application mode:
  • the charging trigger device reports the initial quota application mode in the unit of user service (the subsequent charging processing device can also manage the initial quota application mode in the unit of user service), then an exemplary charging request message is:
  • the billing trigger device can report the initial quota application mode in units of rate groups (the subsequent billing processing device can also manage the initial quota application mode in units of rate groups), then an exemplary billing request The message is:
  • step 303 does not depend on step 304, that is, step 304 can be performed after, before, or at the same time as step 303.
  • the charging processing device receives and parses the above-mentioned initial charging request, obtains RSU31 and IqrModInd31 from them, and based on the situation specified by IqrModInd31 (that is, the charging trigger device uses the non-blocking mode initial quota application for the user service),
  • the user service performs charging processing, generates the current stage charging control command (Current Stage Charging Control Command, CurCmd) and/or the next stage charging control command (Next Stage Charging Control Command, NxtCmd), and sends it to the charging trigger device implement.
  • the description is as follows:
  • the current charging control instruction refers to the instruction parameter or instruction provided to the charging trigger device for the user service of the current period
  • the next charging control instruction refers to the charging trigger device for the next user service.
  • Indicating parameters or instructions; among them, the current user service refers to the user service for which quota is currently applied for or is consuming quota. For example, if a user service corresponds to a service data stream of a rate group in a 5G data service, then Before the termination event of service data flow (Termination of service data flow) appears, the user service is called "current user service"; while the next user service is relative to the current user service, which refers to the start after the current time point.
  • a user service corresponds to a service data stream of a rate group in the data service, and it is currently being released. After the current time point, the start event of the service data stream of the user service (Start of service) data flow) appears, the starting service data flow is called the "next period user service".
  • Start of service the start event of the service data stream of the user service
  • the starting service data flow is called the "next period user service”.
  • user services in the current period and user services in the next period may coexist in a certain period of time.
  • the charging processing device grants quota GSU31 for the user service based on RSU31; the charging processing device determines whether the initial quota application mode of the user service needs to be changed based on IqrModInd31, and when determining that the charging trigger device needs to be changed to the blocking mode NxtCmd31 is generated when the initial quota is applied for; the exemplary value of NxtCmd31 is "ToB" (To Blocking Mode) to indicate that the charging triggering device (the charging triggering device 102 or the charging triggering device not shown in Figure 1) is receiving At the next start request of the user service (such as the start request StartReq32), the initial quota application in the blocking mode is adopted for the user service; optionally, the charging processing device may also record or save the said user service based on IqrModInd31 or NxtCmd31
  • the current initial quota application mode of the user service is used as an input for determining whether to modify the initial quota application mode of the user service next time.
  • the billing processing device learns based on IqrModInd31 that the current billing triggering device uses the initial quota application in the non-blocking mode for the user service, and when it is determined that the user account no longer meets the requirements of the initial quota application in the non-blocking mode (For example, the condition that "the remaining validity period of the package in the account is greater than a certain threshold" is no longer met, or the "account balance decline rate exceeds a certain threshold", etc.), which will result in a credit control risk, determine the need to use
  • the charging trigger device changes the initial quota application mode of the blocking mode to the user service, and then generates NxtCmd31.
  • the charging processing device may also determine that the user account no longer meets the requirements of the initial quota application in the non-blocking mode, regardless of the mode of the initial quota application used by the current charging trigger device for the user service Next, directly generate NxtCmd31.
  • NxtCmd instruction in the embodiments of this application is exemplary and not limiting.
  • other representations can also be used.
  • Enable NB can be used to indicate that non-blocking is to be used.
  • the initial quota application of the mode, and “disable NB” means that the initial quota application of the blocking mode is to be adopted.
  • the charging processing device may further Record or save the current initial quota application mode in this charging context: if NxtCmd31 has not been issued before, record or save the initial quota application mode IqrMod of the user service based on IqrModInd31, if the charging processing equipment is updated
  • Step 306-1 The charging processing device sends an initial charging response message to the charging triggering device, which includes GSU31 and NxtCmd31.
  • the initial charging response message is a response message corresponding to the foregoing initial charging request message.
  • the initial charging response message is sometimes referred to as the initial charging response for short, which will not be repeated in the following.
  • NxtCmd31 is optional. There is a corresponding "?” mark in the method flow chart; conversely, if a message field in the method flow chart is suffixed with a "?” mark, it means that the message field is optional; this representation The method is also applicable to all the embodiments of this application, and will not be repeated.
  • step 305-1 the recording or saving of the initial quota application mode of the user service in step 305-1 can also be executed after the initial charging response message is successfully sent in this step.
  • the charging response message and the data structure of the NxtCmd in the charging response message are as follows (for example in step 304).
  • the user service has exclusive quota, and the charging processing device can manage the initial quota application mode in units of rate groups.
  • An exemplary charging response message is:
  • MUI is the abbreviation of Multiple Unit Information
  • GSU is the abbreviation of Granted Service Unit.
  • the billing processing device can manage the initial quota application mode in units of user services, and the exemplary billing response message is:
  • the billing processing equipment can also manage the initial quota application mode in units of rate groups:
  • Example 1 Make the charging trigger device use the blocking mode (or prohibit the use of non-blocking mode) for all user services in the entire rate group.
  • An exemplary charging response message is:
  • the response message (NxtCmd31 in) is equivalent to only the user service in the non-blocking mode before this (For example, the user service of Service2 in step 304) works.
  • Example 2 If the non-blocking mode of Service2 has been disabled by the charging processing device, the charging triggering device determines to restore the original initial quota application mode of the Service2 user service (ie: the non-blocking mode is used during the recovery period), an exemplary charging response The message is:
  • the response message (NxtCmd31 in) is equivalent to the user service that only uses the non-blocking mode before. (For example, the user service whose ServiceID is 2 in the example of step 304) works.
  • Step 307-1 The charging trigger device monitors the use of GSU31 (taking NQUSU as the used amount), and updates the initial quota application mode of the user service based on NxtCmd31.
  • the charging triggering device receives and parses the initial charging response message in step 306-1, obtains GSU31 and NxtCmd31 (if any) from them, and monitors the use of GSU31. At this time, it will record the absence of the user service.
  • the quota usage NQUSU is used as the quota GSU31's used amount.
  • the charging trigger device updates the initial quota application mode of the user service based on NxtCmd31: obtains the new initial quota application mode of the user service based on the NxtCmd31 parameter, and corresponds to step 302, changes the initial quota application mode It is stored in the user service configuration information stored in a local or external storage facility, where the initial quota application mode stored in the external storage facility can be shared by multiple charging trigger devices.
  • the policy control device After updating the initial quota application mode in the locally effective charging policy of the user service, further sending a policy update request to the policy control device, the policy update request including the initial quota application for updating the user service Mode indication information; or, instead of updating the initial quota application mode in the locally effective charging policy of the user service, it directly sends a policy update request to the policy control device, and the update request includes updating the user service
  • the policy control device issues the new charging policy of the user service in the response message of the policy update request, and the new charging policy includes the updated all
  • the indication information may be that the non-blocking mode is prohibited for the user service, or the blocking mode is indicated for the user service.
  • the embodiment of this application does not limit the data structure and storage location of the initial quota application mode saved by the charging trigger device. For example, it can be placed in the data structure of the configuration data of the user service:
  • the charging processing device when the charging processing device fails to authorize the user service, it determines that the charging triggering device should suspend the quota management of the user service, and then generates the current charging control instruction CurCmd32 for suspending quota management ,
  • the example value is "HngQm" (Hang up quota management); optionally, the charging processing device can also determine that the charging triggering device should be changed to the initial blocking mode for the user service.
  • the next charging control instruction NxtCmd32 is generated, and the example value is "ToB".
  • the charging processing device may also update the initial quota application mode of the user service based on NxtCmd32.
  • the authorization failure includes: insufficient balance, failure to approve price, and permission to access the user service, etc., resulting in authorization failure.
  • the authorization failure is mainly based on the failure of granting quota as an example, which will not be described in detail later.
  • the charging processing device further determines the need to use the accounting according to the configuration information of the user service (for example, the type of the user service is an uninterruptible service, or the user contract agreement indicates that the user service is uninterruptible).
  • the charge triggering device suspends the quota management of the user service, and generates the current charging control instruction CurCmd32 with a value of "HngQm".
  • the optional CurCmd32 may also include indication information of quota grant failure, such as "Fail".
  • the above-mentioned suspended quota management can be realized as switching from online charging to offline charging for the user service, which is equivalent to quota-free management.
  • the charging trigger device can switch the user service offline based on the instructions of CurCmd32.
  • Charging; the above-mentioned suspended quota management can also be realized as the user service is changed from conventional quota management to unlimited quota management, and the charging trigger device can limit the quota or use of the user service based on the instruction of CurCmd32 A large enough quota, and record the usage of the large enough quota.
  • the above-mentioned conventional quota management means that the billing processing device allocates quotas for user services based on the user account balance, and the billing triggering device releases the user services according to the quota granted by the billing processing device, and triggers the accounting when the quota is exhausted.
  • the fee processing device sends a charging request for applying for a quota.
  • the so-called unlimited quota management refers to the pending quota instruction issued by the billing processing device (such as "HngQm" above).
  • the billing trigger device will not limit the quota usage for the user's business based on the instruction (not because the quota is used up) And trigger the quota application), and record the usage of the quota.
  • the above-mentioned "HngQm” indication parameter can be replaced with "ToOff” (To Offline Charging, converted to offline charging) or "ToNLQM” (To No Litmited Quota Management, converted to unlimited quota management). To show the difference.
  • step 305-1 For generating the next charging control command NxtCmd32, reference may be made to the related description in step 305-1.
  • step 305-1 For recording or saving the initial quota application mode of the user service, reference may be made to the relevant description in step 305-1.
  • Step 306-2 The charging processing device sends an initial charging response message to the charging triggering device, which includes CurCmd32 and NxtCmd32.
  • NxtCmd32 is optional, and the charging processing device can issue an indication parameter to change the initial quota application mode of the user service to the blocking mode through a subsequent mid-term charging response message.
  • the charging processing device can issue an indication parameter to change the initial quota application mode of the user service to the blocking mode through a subsequent mid-term charging response message.
  • Step 307-2 Charging triggers the device to suspend quota management, and updates the initial quota application mode of the user service based on NxtCmd32.
  • the charging trigger device receives and parses the initial charging response message in step 306-2, obtains CurCmd32 and NxtCmd32 (if any) therefrom, and suspends the quota management of the user service according to CurCmd32.
  • the user service is converted to offline charging (equivalent to quota-free management) or an unlimited number of quota management is performed on the user service.
  • the previously recorded quota-free usage of the user service will be reported to the charging processing device as a USU for charging processing.
  • the charging trigger device also updates the initial quota application mode of the user service based on NxtCmd32. For details, refer to the relevant description in step 307-1.
  • step 305-2 This step is similar to step 305-2.
  • the charging processing device further determines that the charging triggering device should interrupt the user service (for example, the type of the user service is an interruptible service, Or the user contract agreement indicates that the user service is an interruptible service).
  • CurCmd instruction for interrupting user services in the embodiments of the present application is exemplary rather than limiting.
  • other expressions may also be used, for example, a specific result code may also be used to indicate The charging trigger device interrupts the user service.
  • Step 306-3 The charging processing device sends an initial charging response message to the charging triggering device, which contains CurCmd33 and NxtCmd33.
  • This step is similar to step 306-2 and will not be repeated here.
  • Step 307-3 The charging trigger device interrupts the user service, reports NQUSU, and updates the initial quota application mode of the user service based on NxtCmd33.
  • the initial quota application mode for updating the user service based on NxtCmd33 is similar to step 307-1.
  • the charging trigger device interrupts the user service according to the "Fail” indication information in CurCmd33, and optionally, further reports the non-quota usage amount NQUSU recorded so far.
  • step 308 Since the charging processing device instructs to interrupt the user service, after this step, step 308 will be directly transferred to end the user service.
  • Step 308 The user service ends.
  • the end of the user service may be triggered by the user, or authorization failure, etc.
  • Step 309 The charging trigger device receives the start request StartReq32 of the user service.
  • the charging trigger device receives StartReq32 from the user equipment.
  • the next start request of the user service may be the charging trigger device in steps 301-308, or other charging trigger devices, so the charging trigger device in step 309 may be the same as steps 301-308.
  • the same charging trigger device may also be different charging trigger devices.
  • step 302 is similar to step 302 and will not be described in detail.
  • the charging trigger device knows the initial quota application that should adopt the blocking mode for the user service, and therefore determines that the quota should be applied first, and then the user service is started.
  • Step 311 The charging trigger device sends the initial charging request message of the user service to the charging processing device, which includes quota application information RSU32 and initial quota application mode indication information IqrModInd32.
  • the initial calculation is sent first. Fee request message to apply for quota.
  • the initial quota application includes quota application information RSU32 and initial quota application mode indication information IqrModInd32, where IqrModInd32 is similar to IqrModInd31 in step 304.
  • Step 312 The charging processing device grants the quota GSU32.
  • the charging processing device receives and parses the initial charging request message in step 311, obtains quota application information RSU32 and initial quota application mode indication information IqrModInd32, and grants quota GSU32 for the user service, based on IqrModInd32 recording or saving
  • the current initial quota application mode of the user service is used as the input for determining whether the initial quota application mode of the user service needs to be modified next time; regarding granting quota GSU32 and recording or saving the current initial quota application mode of the user service based on IqrModInd32
  • IqrModInd32 For the process, please refer to the related description in step 305-1.
  • Step 313 The charging processing device sends an initial charging response to the charging triggering device, which includes the granted quota GSU32.
  • Step 314 The charging trigger device starts the user service based on the GSU32.
  • steps 309-314 may also change the initial quota application mode of the user service. For details, refer to steps 341-346 in Figure 3C. After step 314, the initial quota application mode of the user service may also be changed. For details, see Steps 367-370 of Figure 3D.
  • step 301-step 303 the user service is started before the quota is applied, so this is the initial quota application process in non-blocking mode; in the process of step 309-step 314, the user service is started after the quota is applied for, so this is The initial quota application process in the blocking mode; the changes before and after are caused by the charging control instructions issued by the charging processing equipment.
  • the above method flow corresponding to Figure 3A enables the charging processing device to determine whether the current user service has started according to the initial quota application mode used when the authorization fails, and then determine appropriate processing measures (such as triggering device suspension by instructing charging Quota management or interruption of user services, etc.) to process user services in the current period, thereby preventing user business risks in the current period caused by the operation of the billing system.
  • the process of this method also enables the charging processing device to promptly change the initial quota application mode used by the charging trigger device for user services from non-blocking mode to blocking mode, which can prevent user services from changing in the next period.
  • the poor user experience from the beginning to the immediate interruption can also prevent the billing system from being DOS attacked.
  • the billing processing equipment may not always be able to evaluate the credit control risk when processing the initial billing request message, and it is more likely to be when the user’s business starts. Later, it can be evaluated as the user's service-related information changes to a certain extent. For this reason, the embodiment of the present application provides the method flow corresponding to FIG. 3B.
  • charging triggers the device to apply for the initial quota in the non-blocking mode (first mode) for user services at first, and then the charging processing device sends a charging control instruction through a mid-term charging response message to make charging Trigger the device to adjust the charging operation, such as: suspending/resuming quota management, interrupting the user service, changing the user service to the initial quota application in the blocking mode (the second mode), etc.
  • the method flow mainly includes the following steps:
  • Step 321 The charging trigger device receives the start request StartReq33 of the user service.
  • step 301 For the content of this step, please refer to step 301.
  • Step 323 The charging trigger device starts the user service, and records the quota-free usage NQUSU.
  • step 303 For the content of this step, refer to step 303.
  • Step 324 The charging trigger device sends an initial charging request to the charging processing device, which includes quota application information RSU33 and initial quota application mode indication information IqrModInd33.
  • step 304 For the content of this step, refer to step 304.
  • Step 325 The charging processing device grants quota GSU33, and saves the current initial quota application mode of the user service based on IqrModInd33.
  • step 305-1 For the content of this step, refer to step 305-1. The difference is that step 305-1 determines that the initial quota application mode of the user service needs to be changed, while this step determines that the initial quota application mode of the user service does not need to be changed (for example: No credit control risk was found).
  • Step 326 The charging processing device sends an initial charging response to the charging triggering device, which includes GSU33.
  • Step 327 The charging trigger device monitors the use of GSU33 (NQUSU is used as the used amount).
  • the charging trigger device receives and parses the initial charging response message in step 326, obtains GSU33 from it, and manages the use of GSU33. At this time, the recorded user service quota-free usage NQUSU is used as the quota GSU31. Usage amount.
  • the charging triggering device requests the charging processing device for charging processing through a mid-term charging request.
  • the mid-term charging request may include quota application information RSU, or may include usage amount USU, as shown in step 328-1 and step 328-4, respectively.
  • Step 328-1 The charging trigger device sends a mid-term charging request to the charging processing device, which includes quota application information RSU34 and initial quota application mode indication information IqrModInd33.
  • the charging trigger device sends the mid-term charging request message to the charging processing device, which includes quota application information RSU34 and an initial quota application mode indication
  • the information IqrModInd33, and IqrModInd33 is optional.
  • the charging processing device determines that the previous charging trigger device uses the non-blocking mode for the user service according to the current initial quota application mode of the user service stored in step 325 Initial quota application mode.
  • step 328-1 After receiving the mid-term charging request of step 328-1, there are different charging processes according to the account information of the user service and the information of the user service, for example, as follows.
  • NxtCmd34 is optional; for the content of this step, please refer to step 305-1.
  • Step 330-1 The charging processing device sends a mid-term charging response to the charging triggering device, which includes GSU34 and NxtCmd34.
  • step 306-1 is similar to step 306-1, except that the interim charging response message is used to replace the initial charging response message, other steps can be referred to step 306-1.
  • Step 331-1 The charging trigger device monitors the use of GSU34, and updates the initial quota application mode of the user service based on NxtCmd34.
  • This step is similar to step 307-1. The difference is that since there is no quota-free usage before, there is no need to deduct the quota-free usage in GSU34 in this step.
  • step 305-2 For the content of this step, please refer to step 305-2.
  • Step 330-2 The charging processing device sends a mid-term charging response to the charging triggering device, which includes CurCmd35 and NxtCmd35.
  • step 306-2 is similar to step 306-2, except that the interim charging response message is used to replace the initial charging response message, other steps can be referred to step 306-2.
  • Step 331-2 Charging triggers the device to suspend quota management, and updates the initial quota application mode of the user service based on NxtCmd35.
  • step 307-2 For the content of this step, please refer to step 307-2.
  • step 305-3 For the content of this step, please refer to step 305-3.
  • Step 330-3 The charging processing device sends a mid-term charging response to the charging triggering device, which includes CurCmd36 and NxtCmd36.
  • step 306-3 is similar to step 306-3, except that the interim charging response message is used to replace the initial charging response message, other steps can be referred to step 306-3.
  • Step 331-3 The charging trigger device interrupts the user service, and updates the initial quota application mode of the user service based on NxtCmd36.
  • step 307-3 For the content of this step, please refer to step 307-3.
  • Step 328-4 The charging trigger device sends a mid-term charging request to the charging processing device, which includes usage information USU34 and initial quota application mode indication information IqrModInd33.
  • the charging triggering device sends a mid-term charging request message to the charging processing device, which includes usage information USU34; in order for the charging processing device to know
  • the mid-term charging request may also include initial quota application mode indication information IqrModInd33, that is, IqrModInd33 is optional.
  • IqrModInd33 For the content of IqrModInd33, refer to IqrModInd31 in step 304.
  • the charging processing device determines that the previous charging trigger device uses the non-blocking mode for the user service according to the current initial quota application mode of the user service stored in step 325 Initial quota application.
  • an example of the charging process is as follows.
  • the charging processing device receives and parses the mid-term charging request described in step 328-4, and obtains usage information USU34 and initial quota application mode indication information IqrModInd33 (if there is this field) from it, and the charging processing device performs processing based on USU34 Account balance is deducted or USU34 is written into the bill, and based on IqrModInd33, it is judged whether it is necessary to change the initial quota application mode of the user service.
  • IqrModInd33 initial quota application mode indication information
  • the charging processing device may further determine that the quota management of the user service has been suspended (for example, when the user service is transferred to offline charging, the user service Whether the quota management is currently suspended is recorded in the charging processing device), then it can be further determined that the quota management needs to be resumed.
  • quotas can be granted for the user service: Although there is USU in the mid-term charging request message but no RSU, that is, no quota request information, the charging processing device determines the granted quota according to the configuration information or the charging policy.
  • the billing processing device can send either or both of CurCmd37 and GSU34X: if only CurCmd37 is sent, the billing trigger device can send the billing device accordingly after receiving the indication parameter.
  • the charge processing device sends a charging request message to apply for quota for the user service.
  • the factor that the charging processing device determines that the quota management of the user service needs to be restored may include: determining that the initial quota application mode of the user service needs to be changed to the blocking mode, and further determining that there is a credit control risk currently.
  • the credit control risk of user services in the current period can be reduced by restoring quota management, and the credit control risk of user services in the next period can be reduced by changing the initial quota application mode of the user service to the blocking mode.
  • the expression mode of the CurCmd command for restoring quota management in the embodiments of this application is exemplary and not limited. In addition to the above mode, other modes can also be used.
  • the "enable QM” indicator can also be used to calculate Charge triggers the device to resume quota management, and use “disable QM” to indicate that charging triggers the device to suspend quota management.
  • Step 330-4 The charging processing device sends a mid-term charging response to the charging triggering device, which includes CurCmd37, GSU34X, and NxtCmd37.
  • step 330-3 For details about whether the optional parameters are carried, refer to the description of the generated parameters in step 329-4.
  • Step 331-4 Charging triggers the device to resume quota management, and updates the initial quota application mode of the user service based on NxtCmd37.
  • the charging trigger device receives and parses the mid-term charging response described in step 330-4, and performs the following operations:
  • CurCmd37 RsmQm (but no GSU34X) in the charging response, resume quota management of the user service, and send a charging request message for applying for quota to the charging processing device;
  • step 307-1 For the process of updating the initial quota application mode of the user service based on NxtCmd37, reference may be made to the description of step 307-1.
  • Step 332 The user service ends.
  • Step 333 The charging trigger device receives the start request StartReq34 of the user service.
  • step 310 For the content of this step, refer to step 310.
  • Step 335 The charging trigger device sends an initial charging request to the charging processing device, which includes quota application information RSU35 and initial quota application mode indication information IqrModInd34.
  • step 311 For the content of this step, refer to step 311.
  • Step 336 The charging processing device grants quota GSU35 and saves IqrMod.
  • Step 337 The charging processing device sends an initial charging response to the charging triggering device, which includes the granted quota GSU35.
  • Step 338 The charging trigger device starts the user service based on the GSU35.
  • steps 333-338 may also change the initial quota application mode of the user service. For details, refer to steps 341-346 in Figure 3C. After step 338, the initial quota application mode of the user service may also be changed. For details, see Steps 367-370 of Figure 3D.
  • the method flow corresponding to Figure 3B above allows the billing processing equipment to have more decision-making opportunities, and more timely balance the demand for credit risk control and the demand for access delay (without having to wait until the user Business starts again).
  • the charging trigger device uses the initial quota application in the blocking mode (first mode) for user services, and then the charging processing device sends the charging control instruction through the initial charging response message to trigger the charging
  • the device adjusts charging operations, such as suspending quota management, and changing the initial quota application to the non-blocking mode (second mode) for the user service.
  • the method flow mainly includes the following steps:
  • Step 341 The charging trigger device receives the start request StartReq35 of the user service.
  • step 301 For the content of this step, please refer to step 301.
  • step 302. For the content of this step, refer to step 302. The difference is that the initial quota application mode of the user service obtained in this step is the blocking mode.
  • Step 343 The charging trigger device sends an initial charging request to the charging processing device, which includes quota application information RSU36 and initial quota application mode indication information IqrModInd35.
  • the charging trigger device first applies for a quota from the charging processing device, specifically, sending the initial charging request to the charging processing device, including the quota application Information RSU36 and initial quota application mode indication information IqrModInd35.
  • a quota from the charging processing device, specifically, sending the initial charging request to the charging processing device, including the quota application Information RSU36 and initial quota application mode indication information IqrModInd35.
  • IqrModInd35 For the content of IqrModInd35, refer to IqrModInd31 in step 304.
  • the charging processing device receives and parses the foregoing initial charging request, and charges the user service based on the situation indicated by IqrModInd35 (that is, the charging trigger device uses the initial quota application in the blocking mode for the user service) Process, generate the current charging control command CurCmd and/or the next charging control command NxtCmd, and issue them to the charging trigger device for execution.
  • the charging processing device determines that the user service should be changed to the initial quota application in the non-blocking mode, and then generates NxtCmd38.
  • the charging processing device determines that the user service should be changed to the initial quota application in the non-blocking mode, and then generates NxtCmd38.
  • it may not be based on the situation indicated by IqrModInd35, but when it is determined that the required conditions of the non-blocking mode are satisfied, it is determined that the initial quota application of the non-blocking mode should be adopted for the user service, and then NxtCmd38 is generated.
  • the charging processing device may also suspend the current quota management of the user service (because the requirements of the non-blocking mode are met, it means that the current credit control risk is low), Then, CurCmd38 is generated, and if it is determined that quota management is suspended, no quota is granted for the user service.
  • the billing processing device learns that the current billing triggering device has adopted the initial quota application in the blocking mode for the user service, and when it is determined that the user account meets the requirements of the initial quota application in the non-blocking mode (for example, it satisfies " If the remaining validity period of the package in the account is greater than a certain threshold, or meet the “account balance decline rate is lower than a certain threshold”, etc.), to confirm that the credit control risk is low, it is determined that billing triggers the device to check The user service is changed to the initial quota application mode of non-blocking mode, and then NxtCmd38 is generated.
  • the charging processing device may also directly generate NxtCmd38 after determining that the user account meets the requirements of the non-blocking mode, regardless of which mode the current charging trigger device uses for the initial quota application for the user service.
  • NxtCmd38 The value of NxtCmd38 is "ToNB" (To Non-Blocking Mode, converted to non-blocking mode) to instruct the charging triggering device to use the non-blocking mode for the user service when it receives the start request of the user service again.
  • ToNB To Non-Blocking Mode, converted to non-blocking mode
  • the billing processing device may perform billing processing on the user service based on the situation indicated by IqrModInd35, including granting quota to RSU36 to GSU36, and determining that the credit control risk of the user service is low during the quota granting process.
  • IqrModInd35 including granting quota to RSU36 to GSU36, and determining that the credit control risk of the user service is low during the quota granting process.
  • the performance burden of the charging processing device and the charging trigger device can reduce the number of information exchanges between the two after all.
  • step 305-1 For the process of recording or saving the currently effective initial quota application mode of the user service, reference may be made to the relevant description in step 305-1.
  • Step 345 The charging processing device sends an initial charging response message to the charging triggering device, which includes GSU36, CurCmd38, and NxtCmd38.
  • GSU36 and CurCmd38 are optional.
  • Step 346 The charging trigger device starts the user service based on GSU36, suspends quota management, and updates the initial quota application mode of the user service based on NxtCmd38.
  • the charging trigger device receives and parses the initial charging response message described in step 345-1, and obtains GSU36 (if any), CurCmd38 (if any), and NxtCmd38 from it. If the response message carries GSU36, the user service is started based on GSU36 and quota management is performed. If the response message carries CurCmd38 but not GSU36, the quota management of the user service is suspended according to CurCmd38; regarding charging The triggering device updates the initial quota application mode of the user service based on NxtCmd38. You can refer to the related description in step 307-1.
  • Step 347 The user service ends.
  • Step 348 The charging trigger device receives the start request StartReq36 of the user service.
  • Step 350 The charging trigger device starts the user service, and records the quota-free usage NQUSU.
  • Step 351 The charging trigger device sends an initial charging request to the charging processing device, which includes quota application information RSU37 and initial quota application mode indication information IqrModInd36.
  • step 324 For the content of this step, refer to step 324.
  • Step 352 The charging processing device grants quota GSU37, and saves IqrMod.
  • step 325 For the content of this step, refer to step 325.
  • Step 353 The charging processing device sends an initial charging response message to the charging triggering device, which contains the granted quota GSU37.
  • step 326 For the content of this step, refer to step 326.
  • Step 354 The charging trigger device monitors the use of GSU37 (NQUSU is deducted first).
  • step 327 For the content of this step, refer to step 327.
  • steps 348-354 may also change the initial quota application mode of the user service. For details, refer to steps 301-307 of FIG. 3A. After step 354, the initial quota application mode of the user service may also be changed. For details, see Steps 328-332 of Figure 3B.
  • the initial quota application in the blocking mode is the initial quota application after starting the user service after applying for the quota.
  • Step 348-step 354 before starting the user service before applying for the quota.
  • the change before and after the initial quota application in non-blocking mode is caused by the charging control instruction issued by the charging processing device.
  • the above-mentioned method flow corresponding to Figure 3C enables the billing processing equipment to timely adjust the initial quota application mode of the user service from the blocking mode to the non-blocking mode, which is beneficial to timely meet the access delay requirements of delay-sensitive services; On this basis, the method flow also enables the charging processing equipment to suspend quota management in time to reduce the communication interaction and data processing between the charging triggering equipment and the charging processing equipment, thereby further reducing the charging triggering equipment and the charging The performance burden of processing equipment.
  • the charging trigger device uses the blocking mode (first mode) for the initial quota application for the user service, and then the charging processing device sends the charging control instruction through the mid-term charging response message to trigger the charging
  • the device adjusts the charging operation, such as: suspending quota management, changing the initial quota application to the non-blocking mode (second mode) for the user service, and so on.
  • the method flow mainly includes the following steps:
  • Step 361 The charging trigger device receives the start request StartReq37 of the user service.
  • step 310 For the content of this step, refer to step 310.
  • Step 363 The charging trigger device sends an initial charging request message to the charging processing device, which includes quota application information RSU38 and initial quota application mode indication information IqrModInd37.
  • step 311 For the content of this step, refer to step 311.
  • Step 364 The charging processing device grants quota GSU38, and saves the initial quota application mode of the user service.
  • the charging processing device grants the corresponding quota GSU38 according to the RSU38, and records or saves the initial quota application mode of the user service based on IqrModInd37.
  • the charging processing device grants the corresponding quota GSU38 according to the RSU38, and records or saves the initial quota application mode of the user service based on IqrModInd37.
  • IqrModInd37 For details, please refer to the relevant descriptions in steps 305-1 and 305-2.
  • Step 365 The charging processing device sends an initial charging response message to the charging triggering device, which includes GSU38.
  • Step 366 The charging trigger device starts the user service based on the GSU38.
  • the charging trigger device can continue to apply for a quota from the charging processing device to maintain the user service, specifically as shown in the following steps.
  • Step 367 The charging trigger device sends a mid-term charging request to the charging processing device, which includes quota application information RSU39 and initial quota application mode indication information IqrModInd37, where IqrModInd37 is optional.
  • the charging processing device may determine, according to the initial quota application mode recorded or saved in step 364, that the charging trigger device uses the blocking mode initial quota application for the user service.
  • the charging processing device receives and parses the mid-term charging request, obtains quota application information RSU39 and initial quota application mode indication information IqrModInd37 therefrom, and then performs charging processing.
  • step 344 For the content of this step, refer to step 344.
  • Step 369 The charging processing device sends a mid-term charging response to the charging triggering device, which includes GSU39, CurCmd3a, and NxtCmd3a.
  • step 345 This step is similar to step 345. In this step, except for replacing the initial charging response of step 345 with an interim charging response, the rest can refer to step 345.
  • Step 370 The charging trigger device continues the user service, suspends the quota management of the user service, and updates the initial quota application mode of the user service based on NxtCmd3a.
  • Step 371 The user service ends.
  • Step 372 The charging trigger device receives the start request StartReq38 of the user service.
  • Step 374 The charging trigger device starts the user service, and records the quota-free usage NQUSU.
  • Step 375 The charging trigger device sends an initial charging request to the charging processing device, which includes quota application information RSU3a and initial quota application mode indication information IqrModInd38.
  • step 324 For the content of this step, refer to step 324.
  • Step 376 The charging processing device grants quota GSU3a and saves IqrMod.
  • step 325 For the content of this step, refer to step 325.
  • Step 377 The charging processing device sends an initial charging response message to the charging triggering device, which contains the granted quota GSU3a.
  • step 326 For the content of this step, refer to step 326.
  • Step 378 The charging trigger device monitors the use of GSU3a (NQUSU is deducted first).
  • step 327 For the content of this step, refer to step 327.
  • steps 372-378 may also change the initial quota application mode of the user service. For details, refer to steps 301-307 of FIG. 3A. After step 378, the initial quota application mode of the user service may also be changed. For details, see Steps 328-S332 of FIG. 3B.
  • the method flow corresponding to Figure 3D above allows the billing processing device to have more decision-making opportunities and more timely balance the demand for credit control, the demand for resource utilization, and the demand for access delay. .
  • the above-mentioned method flow corresponding to FIG. 3A-FIG. 3D is to obtain the account balance, account status, account usage trend and other information of the user service through the charging processing of the user service itself, and send charging control instructions accordingly.
  • the “brother service” or “other services” can also be used.
  • This information can be obtained through the charging process of the service of the same account corresponding to the user service), and it can even be obtained through the management message of the corresponding account of the user service (such as the account management message from the BSS system), and then Send a charging control instruction to the charging trigger device based on this information.
  • the embodiment of the present application further provides the method flow corresponding to FIG. 4A to FIG. 4B, which will be described separately below.
  • the charging trigger device uses the initial quota application in the non-blocking mode (first mode) for user services at first, and then the charging processing device sends the charging control instruction through the charging notification message to trigger the charging
  • the device adjusts charging operations, such as restoring quota management of the user service, changing the initial quota application to the blocking mode (the second mode) for the user service, and so on.
  • the method flow mainly includes the following steps:
  • Step 401 The charging trigger device receives the start request StartReq41 of the user service.
  • Step 403 The charging trigger device starts the user service, and records the quota-free usage NQUSU.
  • Step 404 The charging trigger device sends an initial charging request to the charging processing device, which includes quota application information RSU41 and initial quota application mode indication information IqrModInd41.
  • step 324 For the content of this step, refer to step 324.
  • Step 405 The charging processing device grants the quota GSU41 and saves the IqrMod.
  • step 325 For the content of this step, refer to step 325.
  • Step 406 The charging processing device sends an initial charging response message to the charging triggering device, which contains the granted quota GSU41.
  • step 326 For the content of this step, refer to step 326.
  • Step 407 The charging trigger device monitors the usage of GSU41 (NQUSU is used as quota).
  • step 327 For the content of this step, refer to step 327.
  • the charging processing device continues to grant quotas for the user's services (based on the charging request sent by the charging trigger device), so that the user is continuously released; at the same time, the charging processing device may also perform services for other users.
  • the other user services correspond to the same accounts as the user services, and it is also possible to receive change events related to the attribute information of the user services (such as insufficient package changes for the user services, lower user levels, etc.) Etc.), the charging processing device may also send a charging control instruction to the charging trigger device to adjust the charging trigger based on the charging processing result of the other user services, the change event of the attribute information of the user service, etc.
  • the charging operation of the device for the user service for example, restoring the quota management for the user service, and changing to the initial quota application in the blocking mode.
  • the charging processing device determines that the charging triggering device should change the quota management in the blocking mode to the user service, and then generates the next charging control command NxtCmd41 with the value "ToB"; on this basis,
  • the charging processing device may also generate the current charging control instruction CurCmd41 with a value of "RsmQm”; optionally, the charging processing device may also save/update the initial quota application mode indication information based on the generation of NxtCmd41 .
  • the charging processing device determines that the previous charging trigger device uses the non-blocking mode initial quota application for the user service according to the initial quota application mode previously saved for the user service, and according to the initial quota application for the “brother service” or The result of the charging processing of the charging request message of the "other user service", or the processing of the management message of the account of the user service (for example, the account management message from the Business Support System, BSS)
  • BSS Business Support System
  • the charging processing result of the other user service indicates that the account of the user service (also the account corresponding to the other user service) ) No longer meets the requirements of the initial quota application in the non-blocking mode, and another example is that the event received by the charging processing device indicates that the user level corresponding to the user service has decreased, and so on.
  • the charging processing device finds that the quota management of the user service has been suspended (meaning that offline charging may have been adopted, or unlimited quota management)
  • the user service account also The account corresponding to other user services mentioned above
  • the credit control risk becomes higher.
  • a CurCmd41 with a value of "RsmQm” can also be generated to indicate The charging trigger device restores the quota management of the user service in a timely manner.
  • step 305-1 For the process of saving/updating the initial quota application mode of the user service, reference may be made to the relevant description in step 305-1.
  • Step 409 The charging processing device sends a notification request to the charging triggering device, which includes CurCmd41 and NxtCmd41.
  • the charging processing device in order to send the charging control instruction generated in step 408-1 to the charging triggering device more timely, the charging processing device generates a notification request message, which contains the CurCmd41 and NxtCmd41, and sends the notification request message Send to the charging trigger device; among them, CurCmd41 is optional; the notification address (NotifyURL) of the notification request message can identify the charging trigger device and the user service; if the user service is a data service, the notification request The message may further carry the identifier RG of the tariff group in which the user service belongs.
  • Step 410 Charging triggers the device to resume quota management, and updates the initial quota application mode of the user service based on NxtCmd41.
  • the charging trigger device receives and parses the notification request message, obtains CurCmd41 and NxtCmd41 from it, and on this basis, executes CurCmd41 and NxtCmd41 on the user service, specifically, restoring the quota management of the user service (meaning As a result, the charging triggering device restarts requesting quotas from the charging processing device for the user service), and changes the initial quota application mode of the user service based on NxtCmd41 (for example, it can be saved locally in the charging triggering device, or it can be saved to External storage facility, or sent to the policy control device, for details, please refer to step 307-1), so that when the charging trigger device receives the next start request of the user service, the initial quota of the blocking mode is used for the user service Application.
  • Step 411 The charging trigger device returns a notification response message to the charging processing device.
  • the charging trigger device returns a notification response message to the charging processing device according to the processing result of step 410, which contains information indicating that the notification request of step 409 has been successfully processed.
  • Step 412 The user service ends.
  • Step 413 The charging trigger device receives the start request StartReq42 of the user service.
  • step 333 For the content of this step, refer to step 333.
  • step 334 For the content of this step, refer to step 334.
  • Step 415 The charging trigger device sends an initial charging request to the charging processing device, which includes quota application information RSU32 and initial quota application mode indication information IqrModInd42.
  • step 335 For the content of this step, refer to step 335.
  • Step 416 The charging processing device grants the quota GSU42, and saves the IqrMod.
  • step 336 For the content of this step, refer to step 336.
  • Step 417 The charging processing device sends an initial charging response message to the charging triggering device, which includes GSU42.
  • step 337 For the content of this step, please refer to step 337.
  • Step 418 The charging trigger device starts the user service based on the GSU42.
  • step 338 For the content of this step, refer to step 338.
  • steps 413-418 may also change the initial quota application mode of the user service. For details, refer to steps 341-346 in Figure 3C. After step 418, the initial quota application mode of the user service may also be changed. For details, see Steps 367-370 of Figure 3D.
  • the above-mentioned method flow corresponding to Figure 4A further expands the opportunity for the billing processing equipment to discover risks and make decisions.
  • the charging trigger device uses the initial quota application in the blocking mode (first mode) for user services, and then the charging processing device sends a charging control instruction through a charging notification message to make the charging trigger device Adjust the charging operation, for example: suspend the quota management of the user service, change the initial quota application for the user service to the non-blocking mode (the second mode), etc.
  • the method flow mainly includes the following steps:
  • Step 441 The charging trigger device receives the start request StartReq43 of the user service.
  • step 310 For the content of this step, refer to step 310.
  • Step 443 The charging trigger device sends an initial charging request message to the charging processing device, which includes quota application information RSU46 and initial quota application mode indication information IqrModInd43.
  • step 311 For the content of this step, refer to step 311.
  • Step 444 The charging processing device grants quota GSU46, and saves IqrMod.
  • the charging processing device grants the corresponding quota GSU46 according to the quota application information RSU46, and records or saves the initial quota application mode IqrMod of the user service based on IqrModInd43.
  • the charging processing device grants the corresponding quota GSU46 according to the quota application information RSU46, and records or saves the initial quota application mode IqrMod of the user service based on IqrModInd43.
  • IqrModInd43 For details, please refer to the relevant description in step 305-1. .
  • Step 445 The charging processing device sends an initial charging response message to the charging triggering device, which includes GSU46.
  • Step 446 The charging trigger device starts the user service based on the GSU46.
  • the charging processing device continues to grant quotas for the user's services (based on the charging request sent by the charging trigger device), so that the user is continuously released; at the same time, the charging processing device may also perform services for other users.
  • the other user services correspond to the same accounts as the user services, and it is also possible to receive change events regarding the attribute information of the user services (such as package changes for the user services: postponement, user level upgrade, Account recharge, etc.), the charging processing device may also send a charging control instruction to the charging triggering device based on the charging processing result of the other user services, the change event of the attribute information of the user service, etc., to adjust
  • the charging triggers the charging operation of the device for the user service for example, suspending the quota management of the user service and changing to the initial quota application in the non-blocking mode.
  • the charging processing device determines that the charging trigger device should be changed to adopt non-blocking mode quota management for the user service, and then generates the next charging control command NxtCmd43 with a value of "ToNB"; on this basis,
  • the charging processing device may also generate the current charging control instruction CurCmd43 with the value "HngQm”; optionally, the charging processing device may also save/update the initial quota application mode indication based on the generation of NxtCmd43 information.
  • the charging processing device determines that the previous charging triggering device uses the blocking mode initial quota application for the user service according to the initial quota application mode previously saved for the user service; at this time, the charging processing device finds that it is not The requirements of the blocking mode are met, so NxtCmd43 with a value of "ToNB" is generated.
  • the embodiment of this application does not limit it.
  • the charging processing result of the other user service indicates that the account of the user service (also the account corresponding to the other user service) Satisfying the requirements of the initial quota application in the blocking mode
  • the event received by the charging processing device indicates that the level of the user corresponding to the user service has increased.
  • the user service account (also the account corresponding to the other user service) meets the requirements of the initial quota application in the non-blocking mode at this time, it means that the credit control risk becomes lower.
  • it can also generate CurCmd43 with a value of "HngQm" is used to instruct the charging trigger device to suspend the quota management of the user service in time.
  • step 305-1 For saving/update of the initial quota application mode, please refer to the relevant description in step 305-1.
  • Step 448 The charging processing device sends a notification request to the charging triggering device, which includes CurCmd43 and NxtCmd43.
  • step 409-1 For the content of this step, please refer to step 409-1.
  • Step 449 Charging triggers the device to suspend quota management, and changes the initial quota application mode of the user service based on NxtCmd43.
  • the charging trigger device receives and parses the notification request message, obtains CurCmd43 and NxtCmd43 from it, and on this basis, executes CurCmd43 and NxtCmd43 on the user service, specifically, suspends the quota management of the user service ( If it is to switch to offline charging, it means that the charging triggering device no longer requests quotas from the charging processing device for the user service.
  • the charging triggering device is The billing processing device applies for an equal amount of quota), and changes the initial quota application mode of the user service based on NxtCmd43 (for example, it can be stored locally in the billing trigger device, or stored in an external storage facility, or sent to the policy control device, For details, refer to step 307-1), so that when the charging trigger device receives the next start request of the user service, the initial quota application in the non-blocking mode is used for the user service.
  • Step 450 The charging trigger device returns a notification response message to the charging processing device.
  • the charging trigger device returns a notification response message to the charging processing device according to the processing result of step 449, which contains information indicating that the notification request of step 448 has been successfully processed.
  • Step 451 The user service ends.
  • Step 452 The charging trigger device receives the start request StartReq44 of the user service.
  • Step 454 The charging trigger device starts the user service, and records the quota-free usage NQUSU.
  • Step 455 The charging triggering device sends an initial charging request to the charging processing device, which includes quota application information RSU47 and initial quota application mode indication information IqrModInd44.
  • IqrModInd44 indicates the initial charging trigger device to use non-blocking mode for the user service. Quota application.
  • step 324 For the content of this step, refer to step 324.
  • Step 456 The charging processing device grants quota GSU47, and saves IqrMod.
  • step 325 For the content of this step, refer to step 325.
  • Step 457 The charging processing device sends an initial charging response message to the charging triggering device, which contains the granted quota GSU47.
  • step 326 For the content of this step, refer to step 326.
  • Step 458 The charging trigger device monitors the use of GSU47 (first deduct NQUSU).
  • step 327 For the content of this step, refer to step 327.
  • steps 452-458 may also change the initial quota application mode of the user service. For details, refer to steps 341-346 in Figure 3C. After step 458, the initial quota application mode of the user service may also be changed. For details, see Steps 367-370 of Figure 3D.
  • the above-mentioned method flow corresponding to Figure 4B further expands the opportunity for charging processing equipment to discover low risks and reduce user service access delays, from charging user services
  • the context is expanded to the context of charging processing of other user services, and even the context of processing management messages of the operation support system.
  • the initial charging trigger device uses the initial quota application in the non-blocking mode (first mode) for the user service, and the charging processing device controls the charging operation of the charging trigger device for the current user service accordingly.
  • the charging trigger device changes the initial quota application to the blocking mode (the second mode) for the user service.
  • the method flow mainly includes the following steps:
  • Step 501 The charging trigger device receives the start request StartReq51 of the user service.
  • step 301 For the content of this step, please refer to step 301.
  • the charging trigger device In order to determine the time sequence of starting the user service and applying for quota for the user service, the charging trigger device first obtains the initial quota application mode of the user service, as shown in step 502-1 or step 502-2.
  • the charging trigger device may obtain the initial quota application mode of the user service according to the configuration information of the user service stored in a local or external storage facility, or from the charging policy of the user service activated by the policy control device Obtain the initial quota application mode of the user service, which is a non-blocking mode, and then determine the initial quota application that should adopt the non-blocking mode for the user service.
  • the charging policy for the user service may be requested from the policy control device.
  • Step 502-2-1 The charging trigger device sends a policy request message to the policy control device.
  • the policy request message includes user identification, PDU session information, and other information that can be used to identify the user service.
  • Step 502-2-2 The policy control device returns a policy response message to the charging trigger device, which contains the initial quota application mode of the user service.
  • the policy control device returns the charging policy, which includes the initial quota application mode of the user service.
  • the charging trigger device can receive and parse the policy response message, obtain the initial quota application mode of the user service therefrom, and then determine that the initial quota application of the non-blocking mode should be adopted for the user service.
  • Step 503 The charging trigger device starts the user service, and records the quota-free usage NQUSU.
  • the charging trigger device since the charging trigger device previously determined that the user service should adopt the initial quota application in the non-blocking mode, it immediately starts the user service (without waiting for the quota granted by the charging processing device), and starts recording the quota-free situation Usage under NQUSU.
  • Step 504 The charging trigger device sends a charging request message to the charging processing device, which includes quota application information RSU51 and initial quota application mode indication information IqrModInd51.
  • the charging trigger device sends a charging request message to the charging processing device;
  • the charging request message may be an initial charging request message or It is a mid-term charging request message; when the charging request message is an initial charging request message, it contains quota application information RSU51 and initial quota application mode indication information IqrModInd51; when the charging request message is a mid-term charging request message, It contains quota application information RSU51, and optionally, IqrModInd51.
  • IqrModInd51 indicates that the charging trigger device uses the initial quota application mode for the user service to be the non-blocking mode.
  • the charging processing device After the charging processing device receives and parses the charging request message, it obtains quota application information RSU51 and initial quota application mode indication information IqrModInd51 (if present), and its subsequent processing is as shown in example 5A-1 or 5A-2 Show.
  • Step 505-1 The charging processing device grants the quota GSU51.
  • the charging processing device grants the quota GSU51 for the user service based on the quota application information RSU51.
  • Step 506-1 The charging processing device sends a charging response message to the charging triggering device, which includes GSU51.
  • the charging response message may be an initial charging response message or an intermediate charging response message.
  • Step 507-1 The charging trigger device monitors the use of GSU51 (NQUSU is used as the quota).
  • Step 505-1-Step 507-1 is a process of successful authorization, and the granted quota can be used as one of the basis for the charging trigger device to determine to change the initial quota application mode. See step 508 for details.
  • the charging processing device fails to authorize the user service. For example, based on the quota application information RSU51, it is determined that the conditions for granting the quota are not met (for example, the balance is less than the quota request amount in the quota application information RSU51), and the quota granting fails, then It is further determined that the user service needs to be interrupted or the quota management of the user service needs to be suspended, and the current service control instruction CurCmd51 with a value of "Fail" or "HngQm" is generated.
  • the billing processing device generates CurCmd51 according to the attribute information of the user service, such as the interruptibility of the service: if it knows that the user service is an interruptible service, it generates CurCmd51 with the value "HngQm"; If the user service is an interruptible service, a CurCmd51 with a value of "Fail" is generated.
  • the attribute information of the user service such as the interruptibility of the service: if it knows that the user service is an interruptible service, it generates CurCmd51 with the value "HngQm"; If the user service is an interruptible service, a CurCmd51 with a value of "Fail" is generated.
  • Step 506-2 The charging processing device sends a charging response message to the charging triggering device, which contains CurCmd51.
  • the charging response message may be an initial charging response message or an intermediate charging response message.
  • Step 507-2 The charging trigger device executes CurCmd51.
  • CurCmd51 is "Fail”
  • the user service is interrupted; if the value of CurCmd is "HngQm”, the quota management of the user service is suspended, for example, it is switched to offline charging, but the service is maintained. Through the user service.
  • Step 505-2-Step 507-2 is a process of authorization failure.
  • the issued control instruction can be used as one of the basis for the charging trigger device to determine to change the initial quota application mode. See step 508 for details.
  • Step 508 The charging trigger device determines based on the charging processing result that the initial quota application mode of the user service should be changed to the blocking mode.
  • the charging trigger device determines that the initial quota application mode of the user service should be changed, that is: changing from the previous non-blocking mode (NB) to blocking Mode (B).
  • the billing trigger device may determine that the amount of quota granted in the result of multiple consecutive billing processing shows a downward trend, and then determine that the billing processing device tightens credit control, and then determines that the initial quota application mode of the user service should be changed to Blocking mode; for another example, according to the reason and/or number of authorization failures, it is determined that the credit control risk of the user service is increased, and the initial quota application in blocking mode should be adopted in the follow-up.
  • the charging trigger device may save the new initial quota application mode for the user service, as shown in step 509-1 or step 509-2.
  • Step 509-1 The charging trigger device updates the initial quota application mode of the user service.
  • the charging trigger device saves the initial quota application mode to the user service configuration information stored in a local or external storage facility, where the initial quota application mode stored in the external storage facility can be used in multiple charging Shared between trigger devices.
  • Step 509-2-1 The charging trigger device sends a policy update request message to the policy control device, which contains the indication information for updating the initial quota application mode of the user service.
  • the charging trigger device updates the initial quota application mode in the locally effective charging policy of the user service, it further sends a policy update request to the policy control device, and the policy update request includes the update request for the user service.
  • Indication information of the initial quota application mode so that the policy control device subsequently generates the charging policy of the user service based on the initial quota application mode; or, does not update the initial quota in the locally effective charging policy of the user service
  • the policy control device sends a policy update request directly to the policy control device.
  • the update request includes the indication information for updating the initial quota application mode of the user service.
  • the policy control device includes the policy update request in the response message of the policy update request.
  • a new charging policy for the user service is issued, the new charging policy includes an updated initial quota application mode for the user service, and the indication information may indicate that non-blocking is prohibited for the user service Mode, or instruct to adopt a blocking mode for the user service.
  • an example of sending a policy update request message to a policy control device is as follows:
  • Step 509-2-2 The policy control device returns a policy update response message (OK) to the charging trigger device.
  • the method flow corresponding to FIG. 5A can further reduce the performance burden of the charging processing device on this basis.
  • the charging trigger device uses the initial quota application in the blocking mode (the first mode) for user services, and the charging processing device performs charging processing based on this and issues the charging processing result to control the charging trigger device
  • the charging trigger device applies the initial quota application for the user service to the non-blocking mode (the second mode) according to the charging processing result returned by the charging processing device.
  • the flow of the method It mainly includes the following steps:
  • Step 551 The charging trigger device receives the start request StartReq52 of the user service.
  • step 301 For the content of this step, please refer to step 301.
  • the charging trigger device In order to determine the time sequence of starting the user service and applying for quota for the user service, the charging trigger device first obtains the initial quota application mode of the user service, as shown in step 552-1 or step 552-2.
  • step 502-1 The content of this step can refer to step 502-1, the difference is that the initial quota application mode of the user service is the blocking mode.
  • Step 552-2-1 The charging trigger device sends a policy request message to the policy control device.
  • step 502-2-1 For the content of this step, please refer to step 502-2-1.
  • Step 552-2-2 The policy control device returns a policy response message to the charging trigger device, which contains the initial quota application mode of the user service.
  • step 502-2-2 For the content of this step, please refer to step 502-2-2.
  • Step 553 The charging trigger device sends a charging request message to the charging processing device, which includes quota application information RSU52 and initial quota application mode indication information IqrModInd53.
  • the charging request message may be an initial charging request message or a mid-term charging request message; specifically, in order to start the user service, the charging trigger device sends an initial charging request message to the charging processing device, which includes Quota application information RSU52 and initial quota application mode indication information IqrModInd53; after the user service starts, in order to keep the user service open, the charging trigger device sends a mid-term charging request message to the charging processing device, which contains quota application information RSU52, optionally, may also include IqrModInd53.
  • IqrModInd53 indicates that the initial quota application mode adopted by the charging trigger device for the user service is the blocking mode.
  • the charging processing device After the charging processing device receives and parses the charging request message, it obtains quota application information RSU52 and initial quota application mode indication information IqrModInd53 (if any), and its subsequent processing is shown in example 5B-1 or 5B-2 .
  • Step 554-1 The charging processing device grants the quota GSU52.
  • the charging processing device grants the quota GSU52 for the user service based on the quota application information RSU52.
  • Step 555-1 The charging processing device sends a charging response message to the charging triggering device, which includes GSU52.
  • Step 556-1 The charging trigger device starts the user service based on the GSU52, or monitors the use of the GSU52.
  • the charging triggering device starts the user based on GSU52, and if the charging response message is a mid-term charging response message, the charging triggering device monitors the use of GSU52 .
  • Step 554-1-Step 556-1 is the process of granting quota normally.
  • the granted quota can be used as one of the basis for the charging trigger device to determine to change the initial quota application mode. See step 557 for details.
  • Step 555-2 The charging processing device sends a charging response message to the charging triggering device, which includes GSU52 and CurCmd52.
  • the charging response message also contains CurCmd52.
  • Step 556-2 The charging trigger device executes CurCmd52.
  • Step 554-1-Step 556-1 is the process of granting quota normally.
  • the granted quota and the issued charging control command (CurCmd52) can be used as one of the basis for the charging trigger device to determine to change the initial quota application mode, see details Step 557.
  • Step 557 The charging trigger device determines based on the charging processing result that the initial quota application mode of the user service should be changed to the non-blocking mode.
  • the charging triggering device determines that the initial quota application mode of the user service should be changed based on the charging process of Example 5B-1 or Example 5B-2, that is, changing from the previous blocking mode (B) to the non-blocking mode (NB). For example, the charging triggering device can determine that the charging processing device relaxes credit control based on the increasing trend of the quota granted in the result of multiple consecutive charging processing, and then determines that the initial quota application mode of the user service should be changed to non- Blocking mode.
  • the charging trigger device may save the new initial quota application mode for the user service, as shown in step 558-1 or step 558-2.
  • Step 558-1 The charging trigger device updates the initial quota application mode of the user service.
  • step 509-1 For the content of this step, please refer to step 509-1.
  • Step 558-2-1 The charging trigger device sends a policy update request message to the policy control device, which contains instruction information for updating the initial quota application mode of the user service.
  • step 509-2-1 For the content of this step, please refer to step 509-2-1.
  • Step 558-2-2 The policy control device returns a policy update response message (OK) to the charging trigger device.
  • step 509-2-2 For the content of this step, please refer to step 509-2-2.
  • the method flow corresponding to FIG. 5B can further reduce the performance burden of the charging processing device on this basis.
  • Fig. 6 is a hardware structure diagram of a charging trigger device, a charging processing device, or a policy control device provided by an embodiment of the application. All charging trigger devices (for example, 102 in FIG. 1), charging processing devices (for example, 101 in FIG. 1), and policy control devices (for example, the policy control device 104 in FIG. 1) in the embodiments of the present application may all be It is realized by adopting the general computer hardware structure shown in FIG. 6, which includes a processor 601, a memory 602, a bus 603, an input device 604, an output device 605, and a network interface 606. The input device 604 and the output device 605 are optional.
  • the memory 602 may include a computer storage medium in the form of a volatile and/or nonvolatile memory, such as a read-only memory and/or a random access memory.
  • the memory 602 can store an operating system, application programs, other program modules, executable codes, and program data.
  • the input device 604 can be used to input information, so that the system administrator can operate and manage the charging trigger device, the charging processing device, or the policy control device.
  • the user account risk threshold is configured on the charging processing device and the billing
  • the storage space of the initial quota application mode indication information is managed on the trigger device, and the storage space of the initial quota application mode indication information is managed on the policy control device;
  • the input device 604 can be a keyboard or pointing device, such as a mouse, trackball, touchpad, Microphones, joysticks, game pads, satellite TV antennas, scanners or similar devices can all be connected to the processor 601 via the bus 603.
  • the output device 605 can be used to output information, so that the system administrator can operate and manage the charging trigger device, the charging processing device, or the policy control device; for example, the user account risk threshold is displayed on the charging processing device, and the Trigger the display of the remaining storage space on the device, display the remaining storage space on the policy control device, etc.; in addition to the monitor, the output device 605 can also be other peripheral output devices, such as speakers and/or printing devices, and can also pass through the bus 603 Connect to the processor 601.
  • the charging trigger device, the charging processing device, or the policy control device may all be connected to the network through the network interface 606, for example, connected to a local area network (LAN).
  • LAN local area network
  • the computer execution instructions stored in the charging trigger device, the charging processing device, or the policy control device can be stored in a remote storage device, not limited to local storage.
  • the charging trigger device can execute the method steps corresponding to the charging trigger device in all the above embodiments, such as step 230, 303, 307-2, 331-2, 346, 370, 410, 449, 507-2, and 556-2, etc.; for the specific execution process, please refer to the above-mentioned embodiment, which will not be repeated here.
  • the billing processing device can execute the method steps corresponding to the billing processing device in all the above embodiments, such as step 220, 305-1, 329-1, 344, 368, 408, 447, 505-2, and 554-2; refer to the above-mentioned embodiments for the specific execution process, and will not be repeated here.
  • the policy control device executes the executable code or application program stored in the memory 602, the policy control can execute the method steps corresponding to the policy control device in all the above embodiments, such as steps 502-2, 509- 2. 552-2 and 558-2; refer to the above-mentioned embodiment for the specific execution process, which will not be repeated here.
  • FIG. 7 is a schematic diagram of the logical structure of a charging processing device (101) provided by an embodiment of the application.
  • the charging processing device (101) is used to control the initial quota application mode adopted by the charging trigger device (102) for user services.
  • the charging operation of the charging trigger device (102) for the user service includes:
  • the -Obtaining module 701 configured to obtain indication information of the initial quota application mode of the user service, etc., where the initial quota application mode indication information indicates that the charging trigger device (102) responds to all users when receiving the first start request of the user service.
  • the user service uses the first initial quota application mode.
  • the specific execution process refer to the step description on the charging processing device side in the foregoing embodiment, such as steps 201, 304, 324, and 328-1.
  • -A sending module 702 configured to send a charging processing result, etc., to the charging trigger device (102), where the charging processing result is based on the initial quota application mode indication information for performing charging processing on the user service
  • steps 330-1, 330-2, and 345 refer to the step description on the charging processing device side in the foregoing embodiment, such as steps 330-1, 330-2, and 345.
  • FIG. 8 is a schematic diagram of the logical structure of a charging trigger device (102) provided by an embodiment of the application.
  • the charging trigger device (102) is used to send the initial quota application mode indication information of the user service to the charging processing device (101) , And adjusting the charging operation for the user service according to the charging processing result sent by the charging processing device (101), including:
  • the sending module 801 is used to send the initial quota application mode indication information of the user service to the charging processing device (101).
  • the initial quota application mode indication information indicates that the charging trigger device (102) is receiving the
  • the first initial quota application mode is adopted for the user service at the first start request of the user service.
  • steps 201, 304, 324 and 328-1 For the specific execution process, refer to the step description on the charging trigger device side in the above embodiment, such as steps 201, 304, 324 and 328-1. Wait.
  • the receiving module 802 is used to receive the charging processing result of the user service, etc. from the charging processing device (101).
  • the specific execution process refer to the step description on the charging trigger device side in the above embodiment, such as step 330- 1, 330-2 and 345, etc.
  • -Processing module 803 used to process the user services, etc. based on the charging processing result.
  • FIG. 9 is a schematic diagram of the logical structure of a policy control device (104) provided by an embodiment of the application.
  • the policy control device (104) is used to save the initial quota application mode of user services for the charging trigger device (102), including:
  • the transceiver module 901 is used to receive the initial quota application mode of the user service from the charging trigger device (102), or receive the query request of the initial quota application mode from the charging trigger device (102), etc., see the above for the specific execution process In the embodiment, the steps of the charging trigger device side are described, such as steps 502-2-1 and 509-2-1.
  • -A storage module 902 configured to save the initial quota application mode for receiving user services from the charging triggering device (102) to a local storage facility, optionally, to the charging triggering device (102) through the transceiver module 901 Return a successful response, or according to the query request for the initial quota application mode received from the charging trigger device (102), find the initial quota application mode of the user service from the local storage settings, and send it to the said user service through the transceiver module 901
  • the charging trigger device (102) such as steps 502-2-2 and 509-2-2, etc.
  • the charging processing device shown in FIG. 7, the charging triggering device shown in FIG. 8, and the policy control device shown in FIG. 9 are presented in the form of functional modules.
  • the “module” here can refer to application-specific integrated circuits (ASIC), circuits, processors and memories that execute one or more software or firmware programs, integrated logic circuits, and/or other functions that can provide the above-mentioned functions Of the device.
  • ASIC application-specific integrated circuits
  • these devices may also adopt the form shown in FIG. 6.
  • the acquiring module 701, the sending module 702, the sending module 801, the receiving module 802, the processing module 803, the transceiver module 901, and the storage module 902 can all be implemented by the processor 601 and the memory 602 in FIG. 6.
  • the function of the obtaining module 701 to obtain the indication information of the initial quota application mode of the user service, the function of the sending module 801 to send the indication information of the initial quota application mode, and the function of the storage module 901 to store the initial quota application mode of the user service can all be processed by The device 601 executes the code stored in the memory 602 to achieve this.
  • the disclosed system, device, and method can be implemented in other ways.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation.
  • multiple units or components can be combined or integrated into another system, or some features can be ignored or not. implement.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present application.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application is essentially or the part that contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium. It includes several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Databases & Information Systems (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)

Abstract

在计费系统中处理用户业务的方法:计费触发设备(102)向计费处理设备(101)提供初始配额申请模式指示信息，以指明此前自身对用户业务采用何种模式的初始配额申请，计费处理设备(101)基于该指示信息对所述用户业务进行计费处理，并向计费触发设备(102)下发计费处理结果，使计费触发设备(102)改变对所述用户业务的计费操作，如此通过改变计费处理设备(101)和计费触发设备(102)之间的配合关系，实现了在计费系统的性能和信用控制风险之间、或者接入时延和信用控制风险之间的平衡。

Description

处理用户业务的方法、系统及相关设备
本申请要求于2020年4月1日提交中国国家知识产权局、申请号为202010251898.5、发明名称为“处理用户业务的方法、系统及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及在计费系统中处理用户业务的的方法、系统及相关设备。
背景技术
根据3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)标准规范，计费触发功能(Charging Trigger Functiong，CTF)设备对用户业务通常采用阻塞模式的初始配额申请，其特点在于，CTF设备需在用户业务开始之前先申请到配额，这样虽然有助于降低信用控制风险，降低运营商遭受损失的可能，但不仅会加大包括CTF设备、计费处理功能(CHarging Function,CHF)设备在内的运营商计费系统的性能负担，还会加大用户业务的接入时延，影响时延敏感业务的提供，进而影响用户体验。
5G(5th Generation，第五代)网络所支撑的时延敏感性业务，如uRLLC(ultra High-Reliability and Low-Latency Communication，超高可靠性低时延通信)业务，对接入时延有较高的要求。为此，3GPP标准规范定义了非阻塞模式的初始配额申请，其特点在于，CTF设备开始用户业务的同时或者之后申请配额，有利于减小该用户业务的接入时延。
5G网络可以支撑的用户业务越来越多，其中，有些业务对网络要求极高，如果因为网络造成业务中断可能会造成严重后果，例如：无人驾驶业务、远程医疗业务、工业控制业务等，本申请将这类业务称之为不可中断业务；有些业务即使因为网络原因造成业务中断，也不会有严重后果，例如：VR(Virtual Reality，虚拟现实)业务、AR(Augment Reality，增强现实)业务等，本申请将这类业务称之为可中断业务。对于这两类业务，一味地采用非阻塞模式的初始配额申请分别存在如下问题：对于不可中断业务，CTF设备可能在开始用户业务之后才发现配额申请失败，而此时又不能由CTF设备随意中断该用户业务，CTF设备只能继续放通该用户业务，任其消耗运营商的网络资源，则可能给运营商造成损失；对于可中断业务，CTF设备也可能在用户业务开始之后才发现配额获取失败，虽然此时可以中断业务，但是，这样一方面会影响用户的体验，另一方面，恶意用户可能借此机制对网络进行DoS(Denial of Service，拒绝服务)攻击。
当前CTF设备单侧确定阻塞模式/非阻塞模式的做法，因为缺少配额授予所需的大量支撑信息，会造成一味使用阻塞模式或者一味使用非阻塞模式的结果，而一味地采用阻塞模式的初始配额申请会加大计费系统的性能负担或者加大用户业务的接入时延，而一味地采用非阻塞模式的初始配额申请会影响用户体验甚至造成网络安全风险。
如何在计费系统的性能负担、用户业务的接入时延需求、信用控制风险和网络安全之间取得平衡，是亟需解决的技术问题。
发明内容
鉴于此，有必要提供一种在计费系统中处理用户业务的方法，以在不同场合下对用户业务进行不同的处理，包括调整对其进行计费操作、控制用户业务的通断等，实现计费系统的性能负担、用户业务的接入时延需求、信用控制风险和网络安全之间的平衡。
第一方面，本申请实施例提供了一种计费系统，该计费系统包括计费处理设备(101)和计费触发设备(102)，其中：
所述计费触发设备(102)用于：向所述计费处理设备(101)发送初始配额申请模式指示信息，所述初始配额申请模式指示信息指明所述计费触发设备(102)在收到用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
所述计费处理设备(101)用于：获取所述初始配额申请模式指示信息，且向所述计费触发设备(102)发送计费处理结果，所述计费处理结果为基于所述初始配额申请模式指示信息对所述用户业务进行计费处理的结果；
所述计费触发设备(102)还用于：基于所述计费处理结果处理所述用户业务。
该计费系统改变计费触发设备和计费处理设备之间的配合关系，一方面使得计费处理设备可以结合计费触发设备对用户业务采用的初始配额申请模式的情况进行计费处理，使得计费处理过程更贴合上下文从而可以得到更贴合实际的计费处理结果，另一方面，使得计费触发设备可以根据更贴合上下文的计费处理结果处理用户业务，如此，使得计费处理设备和计费触发设备可以联合起来解决当前由CTF设备单方面采用初始配额申请模式所引起的问题。
在一个可能的方案中，所述计费触发设备(102)还用于：在收到所述第一开始请求时对所述用户业务采用所述第一初始配额申请模式，且向所述计费处理设备(101)发送所述用户业务的初始计费请求消息，所述初始计费请求消息包含所述初始配额申请模式指示信息；所述计费处理设备(101)还用于：从所述初始计费请求消息中获取所述初始配额申请模式指示信息。
在一个可能的方案中，所述计费处理设备(101)还用于向所述所述计费触发设备(102)发送包含以下任意一项的计费处理结果：用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，或者用于指示所述计费触发设备(102)中断所述用户业务的指示参数。
在一个可能的方案中，所述计费处理设备(101)还用于在所述第一初始配额申请模式为非阻塞模式，且确定需使所述计费触发设备(102)挂起所述用户业务的配额管理时，向所述计费触发设备(102)发送包含用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数的计费处理结果，所述计费触发设备(102)还用于挂起所述用户业务的配额管理。
在一个可能的方案中，所述计费处理设备(101)还用于向所述计费触发设备(102)发送包含用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数的计费处理结果，所述第二开始请求晚于所述第一开始请求发生。
第二方面，本申请实施例提供了一种处理用户业务的方法，该方法应用于计费处理设备(101)，该方法包括：
获取用户业务的初始配额申请模式指示信息，所述初始配额申请模式指示信息指明计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
向所述计费触发设备(102)发送计费处理结果，所述计费处理结果为基于所述初始配额申请模式指示信息对所述用户业务进行计费处理的结果。
在一个可能的方案中，所述计费处理设备(101)通过初始计费请求消息获取所述初始配额申请模式指示信息。
在一个可能的方案中，所述计费处理设备(101)通过中期计费请求消息获取所述初始配额申请模式指示信息。
在一个可能的方案中，所述计费处理设备(101)基于策略控制设备发送的计费策略得到所述初始配额申请模式指示信息，所述计费策略包含所述用户业务的初始配额申请模式。
在一个可能的方案中，所述计费处理设备(101)通过所述用户业务的初始计费响应消息发送包含以下任意一项的计费处理结果：
用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，或者
用于指示所述计费触发设备(102)中断所述用户业务的指示参数。
在一个可能的方案中，所述计费处理设备(101)通过所述用户业务的中期计费响应消息、或者通过通知消息发送包含以下任意一项的计费处理结果：
用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，或者
用于指示所述计费触发设备(102)恢复所述用户业务的配额管理的指示参数；
用于指示所述计费触发设备(102)中断所述用户业务的指示参数。
在一个可能的方案中，当所述第一初始配额申请模式为非阻塞模式时，所述计费处理结果包含用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理包括：为所述用户业务授权失败，且基于所述初始配额申请模式指示信息确定需使所述计费触发设备(102)挂起所述用户业务的配额管理。
在一个可能的方案中，在所述第一初始配额申请模式为非阻塞模式，且确定需使所述计费触发设备(102)将所述用户业务(由在线计费)转为离线计费时，向所述计费触发设备(102)发送包含用于指示所述计费触发设备(102)将所述用户业务转为离线计费的指示参数的计费处理结果。
在一个可能的方案中，在所述第一初始配额申请模式为非阻塞模式，且确定需使所述计费触发设备(102)对所述用户业务采用不限量的配额管理的情况下，向所述计费触发设备(102)发送包含用于指示所述计费触发设备(102)对所述用户业务采用不限量的配额管理的指示参数的计费处理结果。
在一个可能的方案中，在所述第一初始配额申请模式为非阻塞模式，且确定需使所述计费触发设备(102)对所述用户业务改为采用阻塞模式的初始配额申请的情况下，向所述计费触发设备(102)发送包含用于指示所述计费触发设备(102)对所述用户业务采用阻塞模式的初始配额申请的指示参数的计费处理结果。
在一个可能的方案中，在所述第一初始配额申请模式为非阻塞模式，且确定需使所述计费触发设备(102)对所述用户业务改为采用阻塞模式的初始配额申请以及确定所述计费触 发设备(102)对所述用户业务的配额管理已挂起的情况下，向所述计费触发设备(102)发送包含以下内容的计费处理结果：
用于指示所述计费触发设备(102)对所述用户业务采用阻塞模式的初始配额申请的指示参数；
用于指示所述计费触发设备(102)恢复对所述用户业务的配额管理的指示参数。
在一个可能的方案中，所述计费处理设备(101)通过在不包含配额申请信息的中期计费请求消息对应的中期计费响应消息中包含授予的配额，以指示所述计费触发设备(102)恢复对所述用户业务的配额管理。
在一个可能的方案中，当所述第一初始配额申请模式为非阻塞模式时，所述计费处理结果包含用于指示所述计费触发设备(102)中断所述用户业务的指示参数，所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理包括：为所述用户业务授权失败，且基于所述初始配额申请模式指示信息确定需使所述计费处理设备(101)中断所述用户业务。
在一个可能的方案中，所述方法还包括：
从所述计费触发设备(102)接收所述用户业务的无配额使用量。
在一个可能的方案中，在所述第一初始配额申请模式为阻塞模式，且确定需使所述计费触发设备(102)对所述用户业务改为采用非阻塞模式的初始配额申请的情况下，向所述计费触发设备(102)发送包含用于指示所述计费触发设备(102)对所述用户业务采用非阻塞模式的初始配额申请的指示参数的计费处理结果。
在一个可能的方案中，在所述第一初始配额申请模式为阻塞模式，且确定需使所述计费触发设备(102)对所述用户业务改为采用非阻塞模式的初始配额申请以及确定所述计费触发设备(102)对所述用户业务的配额管理未挂起或正常进行的情况下，向所述计费触发设备(102)发送包含以下内容的计费处理结果：
用于指示所述计费触发设备(102)对所述用户业务采用非阻塞模式的初始配额申请的指示参数；
用于指示所述计费触发设备(102)挂起对所述用户业务的配额管理的指示参数。
在一个可能的方案中，所述计费处理结果还包含用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数，所述第二开始请求晚于所述第一开始请求发生。
在一个可能的方案中，所述第一初始配额申请模式为非阻塞模式，所述第二初始配额申请模式为阻塞模式；或者，所述第一初始配额申请模式为阻塞模式，所述第二初始配额申请模式为非阻塞模式。
在一个可能的方案中，所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理由所述用户业务的初始计费请求消息触发，通过相应的初始计费响应消息向所述计费触发设备(102)发送所述计费处理结果。
在一个可能的方案中，所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理由所述用户业务的中期计费请求消息触发，通过相应的中期计费响应消息向所述计费触发设备(102)发送所述计费处理结果。
在一个可能的方案中，所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理由其他计费请求消息或者账户管理消息触发，所述其他计费请求消息为其他用户业务 的计费请求消息，所述其他用户业务与所述用户业务对应相同的账户，所述账户管理消息为所述用户业务对应的账户的管理消息，通过通知消息向所述计费触发设备(101)发送所述计费处理结果。
在一个可能的方案中，所述计费处理设备(101)还基于所述初始配额申请模式指示信息记录或保存所述用户业务的初始配额申请模式。
第三方面，本申请实施例提供了一种处理用户业务的方法，应用于计费触发设备(102)，该方法包括：
向计费处理设备(101)发送用户业务的初始配额申请模式指示信息，所述初始配额申请模式指示信息指明所述计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
从所述计费处理设备(101)接收所述用户业务的计费处理结果；
基于所述计费处理结果处理所述用户业务。
在一个可能的方案中，所述向计费处理设备(101)发送用户业务的初始配额申请模式指示信息，具体为：
在收到所述第一开始请求时对所述用户业务采用所述第一初始配额申请模式；
通过初始计费请求消息向所述计费处理设备(101)发送所述初始配额申请模式指示信息。
在一个可能的方案中，所述计费触发设备(102)还通过中期计费请求消息向所属计费处理设备(101)发送所述初始配额申请模式指示信息。
在一个可能的方案中，所述计费处理结果包含以下任意一项：
用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，或者
用户指示所述计费触发设备(102)恢复所述用户业务的配额管理的指示参数，或者
用于指示所述计费触发设备(102)中断所述用户业务的指示参数。
在一个可能的方案中，所述计费处理结果包含用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，所述基于所述计费处理结果处理所述用户业务，包括：
挂起所述用户业务的配额管理。
在一个可能的方案中，所述计费处理结果包含用于指示所述计费触发设备(102)恢复所述用户业务的配额管理的指示参数，所述基于所述计费处理结果处理所述用户业务，包括：
恢复所述用户业务的配额管理。
在一个可能的方案中，所述计费触发设备(102)发送不包含配额申请信息的中期计费请求消息后，通过所述中期计费请求消息对应的响应消息从所述计费处理设备(101)接收到所述计费处理结果，所述计费处理结果包含所述计费处理设备(101)为所述用户业务授予的配额，所述中期计费响应消息所述基于所述计费处理结果处理所述用户业务，包括：
恢复所述用户业务的配额管理。
在一个可能的方案中，所述计费处理结果包含用于指示所述计费触发设备(102)中断所述用户业务的指示参数，所述基于所述计费处理结果处理所述用户业务，包括：
中断所述用户业务，且向所述计费处理设备(101)发送所述用户业务的无配额使用量。
在一个可能的方案中，所述计费处理结果还包含用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数，所述第二开 始请求晚于所述第一开始请求发生，所述基于所述计费处理结果处理所述用户业务，还包括：
将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式。
在一个可能的方案中，所述计费触发设备(102)通过所述用户业务的初始计费响应消息接收所述计费处理结果；或者通过所述用户业务的中期计费响应消息接收所述计费处理结果；或者通过通知消息接收所述计费处理结果。
在一个可能的方案中，所述基于所述计费处理结果处理所述用户业务，包括：
根据所述计费处理结果，将所述用户业务的初始配额申请模式更新为第二初始配额申请模式。
在一个可能的方案中，所述计费触发设备(102)根据所述计费处理结果中的用于指示所述计费触发设备(102)将所述用户业务的初始配额申请模式变更为所述第二初始配额申请模式的指示参数，将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式。
在一个可能的方案中，所述计费触发设备(102)根据所述计费处理结果中的授予配额相关的信息，将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式。
在一个可能的方案中，所述将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式，包括：
向所述策略控制设备(104)发送对所述用户业务禁止采用所述第一初始配额申请模式的指示信息；或者，
向所述策略控制设备(104)发送指示将所述用户业务对应的初始配额申请模式更改为所述第二初始配额申请模式的指示信息。
在一个可能的方案中，所述第一初始配额申请模式为非阻塞模式，所述第二初始配额申请模式为阻塞模式；或者，所述第一初始配额申请模式为阻塞模式，所述第二初始配额申请模式为非阻塞模式。
第四方面，本申请实施例提供了一种计费处理设备(101)，包括获取模块(701)和发送模块(702)，其中：
所述获取模块(701)用于：获取用户业务的初始配额申请模式指示信息，所述初始配额申请模式指示信息指明计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
所述发送模块(702)用于：向所述计费触发设备(102)发送计费处理结果，所述计费处理结果为基于所述初始配额申请模式指示信息对所述用户业务进行计费处理的结果。
在一个可能的方案中，所述获取模块(701)还用于：
从所述计费触发设备(102)接收所述用户业务的初始计费请求消息，所述初始计费请求消息包含所述初始配额申请模式指示信息；
从所述初始计费请求消息中获取所述初始配额申请模式指示信息。
在一个可能的方案中，所述发送模块还用于：
基于所述初始配额申请模式指示信息生成以下任意一项并将以下任意一项包含在所述计费处理结果中：
用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，或者
用于指示所述计费触发设备(102)中断所述用户业务的指示参数。
在一个可能的方案中，所述发送模块还用于：
基于所述初始配额申请模式指示信息生成用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数，并将该指示参数包含在所述计费处理结果中，所述第二开始请求晚于所述第一开始请求发生。
第五方面，本申请实施例提供了一种计费触发设备(102)，包括发送模块(801)、接收模块(802)和处理模块(803)，其中：
所述发送模块(801)用于：向计费处理设备(101)发送用户业务的初始配额申请模式指示信息，所述初始配额申请模式指示信息指明所述计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
所述接收模块(802)用于：从所述计费处理设备(101)接收所述用户业务的计费处理结果；
所述处理模块(803)用于：基于所述计费处理结果处理所述用户业务。
在一个可能的方案中，所述发送模块还用于：
在收到所述第一开始请求时对所述用户业务采用所述第一初始配额申请模式；
向所述计费处理设备(101)发送所述用户业务的初始计费请求消息，所述初始计费请求消息包含所述初始配额申请模式指示信息。
在一个可能的方案中，所述接收模块(802)还用于从所述计费处理设备(101)接收包含用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数的计费处理结果，所述处理模块(803)还用于挂起所述用户业务的配额管理；或者所述接收模块(802)还用于从所述计费处理设备(101)接收包含用于指示所述计费触发设备(102)中断所述用户业务的指示参数的计费处理结果，所述处理模块(803)还用于中断所述用户业务。
在一个可能的方案中，所述接收模块(802)还用于从所述计费处理设备(101)接收包含用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数的计费处理结果，所述第二开始请求晚于所述第一开始请求发生，所述处理模块(803)还用于将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式。
第六方面，本申请实施例提供了一种计费处理设备(101)，包括处理器和存储器，其中：
所述存储器，用于存储程序指令；
所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费处理设备(101)执行第二方面或第二方面中任一可能的方案中的处理用户业务的方法。
第七方面，本申请实施例提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得所述计算机执行第二方面或第二方面中任一可能的方案中的处理用户业务的方法。
第八方面，本申请实施例提供了一种计费触发设备(102)，包括处理器和存储器，其中：
所述存储器，用于存储程序指令；
所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费触发设备(102)执行第三方面或第三方面中任一可能的方案中的处理用户业务的方法。
第九方面，本申请实施例提供了一种计算机可读存储介质，包括指令，当其在计算机上 运行时，使得所述计算机执行第三方面或第三方面中任一可能的方案中的处理用户业务的方法。
第十方面，本申请实施例提供了一种处理用户业务的方法，应用于策略控制设备(104)，该方法包括：
向计费触发设备(102)发送用户业务的初始配额申请模式指示信息，所述初始配额申请模式指示信息指明所述计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
从所述计费触发设备(102)接收所述用户业务的初始配额申请模式指示信息，所述指示信息为对所述用户业务禁止采用所述第一初始配额申请模式的指示信息，或者，指示将所述用户业务对应的初始配额申请模式更改为第二初始配额申请模式的指示信息；
基于所述初始配额申请模式指示信息将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式。
第十一方面，本申请提实施例供了一种芯片，当所述芯片运行时用于实现上述第二方面、第三方面、第二方面的任意可能的实现方案或第三方面的任意可能的实现方案的方法。
附图说明
图1为本申请实施例提供的计费系统架构图；
图2为本申请实施例提供的处理用户业务的方法流程图；
图3A为本申请实施例提供的计费处理设备通过初始计费响应消息处理用户业务的第一方法流程图；
图3B为本申请实施例提供的计费处理设备通过中期计费响应消息处理用户业务的第一方法流程图；
图3C为本申请实施例提供的计费处理设备通过初始计费响应消息处理用户业务的第二方法流程图；
图3D为本申请实施例提供的计费处理设备通过中期计费响应消息处理用户业务的第二方法流程图；
图4A为本申请实施例提供的计费处理设备通过通知消息处理用户业务的第一方法流程图；
图4B为本申请实施例提供的计费处理设备通过通知消息处理用户业务的第二方法流程图；
图5A为本申请实施例提供的计费触发设备基于计费处理结果处理用户业务的第一方法流程图；
图5B为本申请实施例提供的计费触发设备基于配额授予结果处理用户业务的第二方法流程图；
图6为本申请实施例提供的计费触发设备、计费处理设备或策略控制设备的硬件结构示意图；
图7为本申请实施例提供的计费处理设备的逻辑结构示意图；
图8为本申请实施例提供的计费触发设备的逻辑结构示意图；
图9为本申请实施例提供的策略控制设备的逻辑结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A、同时存在A和B、单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
图1为本申请实施例提供的计费系统架构图，用于控制计费触发设备处理用户业务，其中包括计费处理设备101、计费触发设备102和用户设备103，可选地，还可以包括策略控制设备104，这些设备的主要功能分别描述如下。
计费处理设备101：与计费触发设备(包括计费触发设备102及图1未显示的其他计费触发设备)连接，除了用于接收计费触发设备上报的配额申请信息、使用量信息等、据此对用户业务进行计费处理外，还根据计费触发设备上报的所述用户业务的初始配额申请模式，以及根据所述用户业务的相关信息，如用户类型、客户信息、账户余额、业务白名单、业务黑名单、账户余额变化趋势、套餐剩余有效期等，进行计费处理，并向计费触发设备发送计费处理结果，以使该计费触发设备调整对所述用户业务进行的计费操作。
计费处理设备101可以为3GPP标准规范定义的CHF(Charging Function，计费功能)设备，也可以为3GPP标准规范定义的CCS(Converged Charging System，融合计费系统)设备，其中包含了CHF设备的功能。
应理解，实际应用中，图1所示计费系统可以有更多的计费处理设备，例如，可以构建一个集群，其中包含多个计费处理设备，互为备份，从而可以提高容灾能力，实现高可用性。
为叙述方便，本申请实施例中，有时候也将计费处理设备直接称为CHF设备。
计费触发设备102：与计费处理设备101、策略控制设备104(如果有)以及用户设备103相连，该设备可以用于：
(1)从用户设备103接收用户业务的开始请求(即用于请求计费触发设备开始所述用户业务的请求消息)，并根据该开始请求开始所述用户业务，且对所述用户业务进行配额管理、使用量上报等计费操作；
(2)向计费处理设备101上报自身对用户业务采用的初始配额申请模式，从计费处理设备101接收计费处理结果，据此调整对所述用户业务的计费操作，包括调整对所述用户业务采用的初始配额申请模式和/或调整对所述用户业务的中期计费操作(如挂起所述用户业务的配额管理、中断所述用户业务等)；
(3)根据计费处理设备101返回的关于所述用户业务的计费处理结果(例如，配额授 予结果)，决策自身对所述用户业务采用的初始配额申请模式；
(4)在本地或外部存储实体存储所述用户业务的初始配额申请模式，或者，若有策略控制设备104，将自身或计费处理设备101确定的初始配额申请模式的相关信息上报给策略控制设备104，这样可以在多个计费触发设备之间共享所述用户业务的初始配额申请模式，既可以减少不同计费触发设备之间的同步和交互，也可以减轻自身的存储负担。
计费触发设备102可以为3GPP标准规范定义的CTF设备。当用户业务为5G数据连接业务时，计费触发设备102的功能可以部署在3GPP规范中定义的SMF(Session Management Function，会话管理功能)设备中；当用户业务为语音业务时，计费触发设备102的功能可以部署在IMS(IP Multimedia Sub-system，IP多媒体子系统)中的AS(Application Server，应用服务器)或CSCF(call session control function，呼叫会话控制功能)设备中。本申请实施例对计费触发设备102的功能所部署的物理设备不做限定。
应理解，实际应用中，图1所示的计费系统可以有更多的计费触发设备，它们可以连接到相同的计费处理设备(如计费处理设备101)，也可以连接到不同的计费处理设备，同一用户设备为同一用户业务发起的多次业务开始请求，可能是由相同的或不同的计费触发设备处理。
为叙述方便，本申请实施例中有时候也将计费触发设备称为CTF设备。
用户设备103：与计费触发设备(计费触发设备102或图1中未显示的其他计费触发设备)相连，用于向计费触发设备发送用户业务的开始请求，并通过计费触发设备接入或使用用户业务。
用户设备103可以是3GPP标准规范定义的用户设备(user equipment，UE)，可以是具有无线通信功能的无线接入设备或者不具有无线通信功能的有线接入设备，包括手持式设备、车载设备、可穿戴设备或计算设备；示例性地，可以是手机(mobile phone)、平板电脑或带无线收发功能的电脑；用户设备103还可以是虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
应理解，实际应用中，图1所示计费系统可以有更多的用户设备。
策略控制设备104：与计费触发设备(计费触发设备102或图1中未显示的其他计费触发设备)相连，用于为计费触发设备提供用户业务的计费策略，还用于为计费触发设备提供某个用户业务对应的初始配额申请模式。
策略控制设备104可以是3GPP标准规范定义的策略控制功能(Policy Control Function，PCF)设备，或者策略和计费规则功能(Policy and Charging rules Function,PCRF)设备。
为叙述方便，本申请实施例中有时候也将计费触发设备直接称为CTF设备。
需要说明，上文所述的“相连”或者“连接”包括直接连接或者通过一个或多个中间网络设备连接。
图1所示的计费系统架构可以改变计费处理设备和计费触发设备之间的配合关系，使得计费触发设备对用户业务的计费操作可以动态、按需地进行调整，从而可以实现在用户业务的信用控制风险较低时采用非阻塞模式的初始配额申请，而在用户业务的信用控制风险较高 时采用阻塞模式的初始配额申请，并对非阻塞模式情况下的用户业务的使用进行适当的处理，如：挂起用户业务的配额管理或者中断用户业务，可以兼顾用户业务对接入时延的需求、运营商对系统性能和信用风险控制的需求。
为便于理解本申请实施例，下面对一些概念进行解释。
用户业务是指用户设备103通过计费触发设备(计费触发设备102或图1中未显示的计费触发设备)接入或使用的业务，包括但不限于：
(1)数据连接业务，例如，一个协议数据单元(Protocol Data Unit，PDU)会话中的某个费率组(Rating Group，RG)对应的一到多个数据流，或者PDU会话中的某个RG与业务标识对应的数据流，都可以理解为本申请实施例的用户业务；本申请实施例中，“PDU会话中用户业务”、“PDU会话中的业务”，是指PDU会话中某个RG对应的多个数据流，也可以是某个RG对应的多个数据流中某个业务标识对应的数据流；
(2)IMS业务；
(3)能力开放业务等。
为叙述的方便，本申请实施例中，有时候也将用户业务简称为“业务”。
关于用户设备103所接入或使用的用户业务，本申请实施例将主要以5G网络的数据连接业务为例进行说明；相应地，关于计费数据，本申请实施例将主要以数据流量有关的信息为例进行说明，数据流量有关的信息包括但不限于：计费触发设备所采集的PDU会话的信息、所述PDU会话中的被放行的业务单元使用量、计费触发条件、时间戳等。
开始用户业务，是指计费触发设备收到用户业务的开始请求后放通所述用户业务，包括放通所述用户业务的信令或者数据，例如：当用户业务为上述数据连接业务时，“开始用户业务”包括使针对该数据连接业务的PDU会话的建立或更新操作得以继续(如果PDU会话不可用)或者放通业务数据流(如果PDU会话已可用)。
中断用户业务，是指计费触发设备(计费触发设备102或图1中未显示的计费触发设备)停止放通用户业务，例如：当所述用户业务为上述数据连接业务时，“中断用户业务”包括断开所述用户业务对应的数据流的操作。
初始配额申请模式(Initial Quota Request Mode，IqrMod)是指计费触发设备(计费触发设备102或图1中未显示的计费触发设备)在收到用户业务的开始请求后首次为所述用户业务申请配额的模式，主要体现了收到用户业务的开始请求后，为用户业务首次申请配额与开始用户业务之间的时间顺序关系；根据首次申请配额的过程是否阻塞用户业务的开始操作，初始配额申请模式可以分为阻塞模式和非阻塞模式；因此，初始配额申请有“阻塞模式的初始配额申请”和“非阻塞式的初始配额申请”之分，分别描述如下：
阻塞模式的初始配额申请(Blocking Mode Initial Quota Request,BIqr)，是指计费触发设备(计费触发设备102或图1中未显示的计费触发设备)响应于从用户设备103接收的用户业务的开始请求，先为所述用户业务向计费处理设备101申请配额，并在接收到计费处理设备为所述用户业务授予的配额后，才开始所述用户业务。
非阻塞模式的初始配额申请(Non-Blocking Mode Initial Quota Request,NBIqr)，是指计费触发设备(计费触发设备102或图1中未显示的计费触发设备)响应于从用户设备103接收的用户业务的开始请求，并不优先为所述用户业务向计费处理设备101申请配额，而是优先开始所述用户业务，或者在开始所述用户业务的同时为所述用户业务向计费处理设 备101申请配额，也就是说，开始所述用户业务的操作并不依赖于计费处理设备101为所述用户业务授予的配额。虽然计费触发设备在收到计费处理设备101为所述用户业务授予的配额时，已经放通了所述用户业务，但在大多数场景下，尤其是在用户业务对应的用户账户中的余额充足时，计费触发设备可以收到计费处理设备101授予的配额，因此可以在授予的配额中扣减已放通的业务使用量，并将其通过后续的计费请求消息中的业务使用量(Used Service Unit，USU)上报给计费处理设备101。但这种机制的可靠性是有限的，因为用户业务对应的账户信息是动态变化的，当账户中的余额低于某个阈值，或者账户对应的资费套餐发生变化后，仍一味地对其采用非阻塞模式的初始配额申请，将可能出现严重的信用控制风险。
由此可知，当计费触发设备从计费处理设备101接收到其决策采用的某个模式的初始配额申请的指示信息后，如果相应用户业务已经开始，则计费触发设备在收到所述用户业务的下次开始请求时才对所述用户业务应用该模式的初始配额申请，而不是立即应用。
初始配额申请模式指示信息(Initial Quota Request Mode Indication，IqrModInd)是指明计费触发设备(计费触发设备102或图1中未显示的计费触发设备)在收到用户业务的开始请求时对所述用户业务已采用哪一种初始配额申请模式(即上面两种模式中的哪一种模式)的指示信息；初始配额申请模式指示信息可以仅包含IqrMod的取值,也可以包含IqrMod字段及其取值，还可以包含SID(用户业务的标识)字段及其取值。本申请实施例不限定初始配额申请模式指示信息的数据结构。
初始配额申请模式的要求条件是指为使计费触发设备对用户业务采用初始配额申请模式，所述用户业务的属性信息、所述用户业务对应的账户等应满足的条件。例如，非阻塞模式的要求条件可以是“用户业务为时延敏感业务，已连续订购超过12个月，账户余额超过1000元”，而阻塞模式的要求条件可以是“用户业务为非时延敏感业务，账户余额小于100元”。应理解，初始配额申请模式的要求条件不限于对用户业务的属性信息和用户业务对应的账户的要求，且可以由运营商事先配置，或者由运营商与用户共同确定，对此，本申请实施例不作限定。
注意，为了叙述方便，本申请实施例中有时候将“对某个用户业务采用某种初始配额申请模式”描述成“对某个用户业务采用某种模式的初始配额申请”。
下面进一步描述基于图1所示的计费系统架构可以实现的方法流程示例，如图2、图3A-图3D、图4A-图4B和图5A-图5B所示，其中，每一个图对应的方法流程中的计费触发设备都对应图1中的计费触发设备102、计费处理设备都对应图1中的计费处理设备101、用户设备都对应图1中的用户设备103，策略控制设备(如果出现的话)，都对应图1中的策略控制设备104，后续在关于这些方法流程的描述中将不再赘述。
图2对应的方法流程中，计费触发设备基于计费处理设备发送的计费处理结果改变对用户业务的计费操作，该方法流程主要包括如下步骤：
步骤210：计费触发设备向计费处理设备发送用户业务的初始配额申请模式指示信息，或者计费处理设备获取所述初始配额申请模式指示信息。
具体地，该步骤可以说是计费触发设备向计费处理设备发送所述初始配额申请模式指示信息，也可以说是计费处理设备获取所述初始配额申请模式指示信息，后者包括：
-计费处理设备从本地存储设施中直接读取所述初始配额申请模式指示信息、或者从本 地存储设施读取所述用户业务的初始配额申请模式，间接得到所述初始配额申请模式指示信息；或者
-根据所述用户业务的配置信息确定所述初始配额申请模式指示信息；或者
-从计费触发设备接收所述初始配额申请模式指示信息。
计费触发设备可以通过初始计费请求消息，也可以通过中期计费请求消息，发送所述初始配额申请模式指示信息给计费处理设备。
本申请实施例中，初始计费请求消息是指计费触发设备收到所述用户业务的开始请求后向计费处理设备发送的所述用户业务第一个计费请求消息，主要用来申请配额；为叙述方便，本申请实施例中，有时候也将用户业务的初始计费请求消息简称为初始计费请求。
本申请实施例中，中期计费请求消息是指计费触发设备向计费处理设备发送用户业务的初始计费请求消息之后发送的所述用户业务的后续计费请求消息，可以用来申请配额，也可以用来上报使用量，还可以既用来申请配额又用来上报使用量；为叙述方便，本申请实施例中，有时候也将用户业务的中期计费请求消息简称为中期计费请求。
步骤220：计费处理设备向计费触发设备发送基于所述初始配额申请模式指示信息对所述用户业务进行计费计费处理得到的计费处理结果。
具体地，计费处理设备基于所述初始配额申请模式指示信息对所述用户业务进行计费处理，并将该计费处理得到的计费处理结果发送给计费触发设备。基于所述初始配额申请模式指示信息，计费处理设备可以获知当前所述用户业务是否已经开始，以及计费触发设备对所述用户业务采用了何种模式的初始配额申请模式，从而在所述计费处理过程中，可以进一步结合用户业务的一些属性信息，例如，用户业务的类型(如可中断性)，进行计费处理、生成相应的计费处理结果，所述计费处理结果包括授权结果、用户业务的初始配额申请模式相关的指示参数等，以便计费触发设备据此调整对所述用户业务的计费操作。其中，授权结果可以是授予配额的信息，如授予配额的数量、授予配额失败的原因等。
例如，当所述初始配额申请模式指示信息指明计费触发设备此前对所述用户业务采用非阻塞模式(第一初始配额申请模式)的初始配额申请，一方面，若确定需要将所述用户业务的初始配额申请模式更改为阻塞模式或者需要禁用所述用户业务的非阻塞模式的初始配额申请，则在计费处理结果中包含“指示计费触发设备在收到所述用户业务的下次开始请求时对所述用户业务采用第二初始配额申请模式(此处为阻塞模式”的指示参数，具体的，该指示参数可以是指示禁用非阻塞模式初始配额申请的指示参数，也可以是指示更改初始配额申请模式为阻塞模式的指示参数，以便计费触发设备在收到所述用户业务的下次开始请求时采用阻塞模式的初始配额申请，进而避免远期信用控制风险和网络安全风险(防DoS攻击)；另一方面，在确定授权失败时，计费处理设备可以进一步确定需要中断用户业务(如判断所述用户业务的可中断性，且判断其为可中断业务时)，则在所述计费处理结果中包含“中断业务”的计费操作控制指令，而如果确定需要挂起所述用户业务的配额管理(如所述用户业务为不可中断业务)，则在所述计费处理结果中进一步包含“挂起配额管理”的计费操作控制指令，挂起配额管理可以是将该用户业务转为离线计费或者转为使用一个无限配额(即：计费触发设备不会因为配额用完而触发配额申请)，挂起配额管理后虽然不能对所述用户业务进行实时信用控制，但依然可以采集用户业务的计费信息作为后续计费处理的基础，通过基于初始配额申请模式指示信息对授权失败的计费处理，可以对用户业务采取合适的处理措 施，避免了信用控制风险和网络安全风险。
再如，当所述初始配额申请模式指示信息指明计费触发设备此前对所述用户业务采用阻塞模式的初始配额申请(第一初始配额申请模式)，若确定需要将该用户业务的初始配额申请模式更改为非阻塞模式或者需要恢复该用户业务的非阻塞模式配额管理(例如当授予配额成功时，计费处理设备可以进一步分析所述用户业务的账户信息，如果所述用户业务的账户余额充足)，则可在所述计费处理结果中包含“指示计费触发设备在收到所述用户业务的下次开始请求时对所述用户业务采用第二初始配额申请模式(此处为非阻塞模式)”的指示参数，具体的，该指示参数可以是指示更改初始配额申请模式为非阻塞模式的指示参数，或者，若该用户业务的初始配额申请模式默认配置为非阻塞模式，且之前被计费处理设备禁用了该非阻塞模式，则该指示参数可以是恢复该用户业务默认配置的非阻塞初始配额申请模式的指示参数，以便计费触发设备在收到所述用户业务的下次开始请求时，可以对所述用户业务采用非阻塞模式的初始配额申请，以降低所述用户业务的接入时延。这种情况下，计费处理设备还可以在计费处理结果中包含“挂起配额管理”(意思是在所述用户业务结束前对所述用户业务不做配额管理或限制，除非再次收到计费处理设备发送的“恢复配额管理”指示参数)的指示参数，以便在本次业务使用过程中减少复杂的信用控制，提高系统效率。
计费处理设备也可以不在计费处理结果中包含显式的指示参数，而是，例如，通过改变授予配额的数量，使多次授予的配额呈上升趋势，或者呈下降趋势，以此通过“暗示”的方式促使计费触发设备调整对所述用户业务采用的初始配额申请模式。
更多例子，参见本申请后续实施例。
步骤230：计费触发设备基于所述计费处理结果处理所述用户业务。
具体地，计费触发设备从计费处理设备接收所述计费处理结果，然后根据计费处理结果处理所述用户业务。
具体地，如果计费处理结果中包含“中断用户业务”的指示参数，则中断所述用户业务，可选的，向计费处理设备上报此前记录的无配额使用量；如果计费处理结果中包含“挂起配额管理”的指示参数，则挂起所述用户业务的配额管理，例如：可以是将所述用户业务转为离线计费或者转为使用不限量配额管理(即：计费触发设备不会因为配额用完而触发配额申请)；如果计费处理结果中包含“指示计费触发设备在收到所述用户业务的下次开始请求时对所述用户业务采用第二初始配额申请模式”的指示参数，则更改所述用户业务的初始配额申请模式；如果计费处理结果中未包含“指示计费触发设备在收到所述用户业务的下次开始请求时对所述用户业务采用第二初始配额申请模式”的指示参数，计费触发设备可以根据计费处理结果中包含的授权结果(如授予配额失败的原因，或者相比请求量低很多的授予配额的数量等)，进一步确定是否更改所述用户业务的初始配额申请模式。
具体地，计费触发设备还可以根据多个计费处理结果中包含的配额授予信息，进一步确定是否更改所述用户业务的初始配额申请模式。例如，当获知此前多次授予配额均成功，且当前初始配额申请模式为阻塞模式，则计费触发设备可以确定收到所述用户业务的下次开始请求时对所述用户业务改为采用非阻塞模式的初始配额申请；再如，如果此前多次授予配额的数量呈现下降趋势，且当前初始配额申请模式为非阻塞模式，则可以确定收到所述用户业务的下次开始请求时对所述用户业务改为采用阻塞模式的初始配额申请。
更多例子，参见本申请后续实施例。
上述图2对应的方法流程使得计费处理设备可以基于计费触发设备对用户业务所采用的初始配额申请模式对所述用户业务进行计费处理，并下发相应的计费处理结果，以使计费触发设备处理所述用户业务(主要是改变对所述用户业务的计费操作)，有助于实时、动态地平衡终端用户对接入时延的需求、运营商对系统性能和信用风险控制的需求之间的关系。
关于上述图2对应的方法流程，可进一步参考本申请实施例提供的图3A-图3D、图4A-图4B和图5A-图5B对应的方法流程。
图3A-图3D为本申请实施例提供的计费处理设备通过计费响应消息处理用户业务的方法流程图，下面对这些方法流程分别进行描述。
图3A对应的方法流程中，起先计费触发设备对用户业务采用非阻塞模式(第一模式)的初始配额申请，后来计费处理设备通过初始计费响应消息发送计费控制指令，使计费触发设备调整计费操作，例如：挂起所述用户业务的配额管理、中断所述用户业务、对所述用户业务改为采用阻塞模式(第二模式)的初始配额申请等。该方法流程主要包括如下步骤：
步骤301：计费触发设备收到所述用户业务的开始请求StartReq31。
具体地，计费触发设备从用户设备接收到StartReq31。
以所述用户业务为5G数据业务为例，StartReq31可以是为该数据业务建立PDU会话的请求消息，或者，在PDU会话已建立的情况下，可以是该数据业务的数据流中的初始数据包。
步骤302：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝NB)。
具体地，计费触发设备可以根据本地或外部存储设施保存的所述用户业务的配置信息得到所述用户业务的初始配额申请模式，还可以从策略控制设备下发的策略中获取所述用户业务的初始配额申请模式(例如，策略控制设备激活的所述用户业务的计费策略中获取所述用户业务的初始配额申请模式；或者所述用户业务当前没有激活的计费策略，则向策略控制设备请求所述用户业务的计费策略，策略控制设备将所述用户业务的初始配额申请模式作为所述用户业务的计费策略返回给计费触发设备，计费触发设备从中获取所述用户业务的初始配额申请模式)。
本方法流程假设对所述用户业务采用的初始配额申请模式IqrMod为非阻塞模式(NB)。
步骤303：计费触发设备开始所述用户业务，记录无配额使用量NQUSU。
由于所述用户业务的初始配额申请模式为非阻塞模式，计费触发设备可以立即开始所述用户业务，而不必等待后续步骤中的配额申请的结果；此外，计费触发设备开始记录无配额使用量NQUSU。所述无配额使用量是指计费触发设备在没有计费处理设备为所述用户业务授予的有效配额的情况下放通所述用户业务所形成的的业务使用量，以5G数据业务为例，其无配额使用量为计费触发设备在没有计费处理设备为该5G数据业务授予的有效配额的情况下，放通该5G数据业务所形成的的数据流量。
步骤304：计费触发设备向计费处理设备发送所述用户业务的初始计费请求，其中包括配额申请信息RSU31和初始配额申请模式指示信息IqrModInd31。
具体地，为了从计费处理设备申请配额以维持放通所述用户业务，计费触发设备向计费处理设备发送所述初始计费请求消息，其中包括配额申请信息RSU31和初始配额申请模式指示信息IqrModInd31，IqrModInd31包括所述用户业务的初始配额申请模式IqrMod(＝NB)。
不同用户业务之间可以共享配额(如：用户业务为某个RG对应的多个数据流中某个业 务标识对应的数据流，则对应相同费率组的多个用户业务共享该费率组的配额)，或者用户业务独享配额(例如：用户业务为某个费率组对应的多个数据流，则该用户业务独享该费率组的配额)，对应这两种情况的计费请求消息及其中的初始配额申请模式指示信息的数据结构，分别举例如下。
(1)用户业务独享配额(例如：用户业务为某个费率组对应的多个数据流)，计费触发设备可以以费率组为单位上报初始配额申请模式(后续计费处理设备也将以费率组为单位管理初始配额申请模式)，则示例性的计费请求消息为：
Figure PCTCN2021083671-appb-000001
注：MUU是Multiple Unit Usage(多单元使用量)的缩写，RG是Rating Group(费率组)的缩写，RSU是Requested Service Unit(请求的业务使用量)的缩写，下同。
(2)不同用户业务之间共享配额(如：用户业务为某个费率组对应的多个数据流中某个业务标识对应的数据流，则对应相同费率组的多个用户业务共享该费率组的配额)，具体如下：
假定有两个用户业务：用户业务Service1和用户业务Service2共享配额，即：Service1为费率组RG1中Service ID＝1对应的数据流，Service2为RG1中Service ID＝2对应的数据流，计费触发设备确定Service1的IqrMod为阻塞模式，Service2的IqrMod为非阻塞模式。
计费触发设备在收到Service2的开始请求时，若计费触发设备上已经有该费率组对应配额(假设Service1已经开始，该费率组对应配额是为Service1授予的)，则计费触发设备为Service2直接使用该费率组对应配额，这种情况下，计费触发设备未对Service2采用非阻塞模式，则不向计费处理设备上报Service2采用的初始配额申请模式指示信息或者上报的Service2采用的初始配额申请模式为阻塞模式。
计费触发设备在收到Service2的开始请求时，若计费触发设备上无该费率组对应配额，则计费触发设备为Service2采用非阻塞模式的初始配额申请，此时向计费处理设备发送的初始计费请求消息中携带“Service2采用了非阻塞模式的初始配额申请”的指示信息。具体的，有两种上报初始配额申请模式的方法：
(2-1)：计费触发设备以用户业务为单位上报初始配额申请模式(后续计费处理设备也可以以用户业务为单位管理初始配额申请模式)，则示例性的计费请求消息为：
Figure PCTCN2021083671-appb-000002
Figure PCTCN2021083671-appb-000003
(2-2)：计费触发设备可以以费率组为单位上报初始配额申请模式(后续计费处理设备也可以以费率组为单位管理初始配额申请模式)，则示例性的计费请求消息为：
Figure PCTCN2021083671-appb-000004
应理解，步骤303并不依赖步骤304，也就是说步骤304可以在步骤303之后、之前或同时执行。
计费处理设备接收并解析上述初始计费请求，从中获取RSU31和IqrModInd31，并基于IqrModInd31所指明的情况(即所述计费触发设备对所述用户业务采用非阻塞模式的初始配额申请)，对所述用户业务进行计费处理，生成本期计费控制指令(Current Stage Charging Control Command，CurCmd)和/或下期计费控制指令(Next Stage Charging Control Command，NxtCmd)，下发给计费触发设备执行。关于本期计费控制指令和下期计费控制指令，说明如下：
本申请实施例中，本期计费控制指令是指提供给计费触发设备针对本期用户业务执行的指示参数或指令，而下期计费控制指令是指提供给计费触发设备针对下期用户业务的指示参数或指令；其中，本期用户业务是指当前为其申请配额或正在消费配额的用户业务，例如：假设一个用户业务对应5G数据业务中一个费率组的业务数据流，则在该业务数据流的结束事件(Termination of service data flow)出现之前，该用户业务都称为“本期用户业务”；而下期用户业务是相对于本期用户业务而言的，指当前时间点之后开始的相同用户业务，例如：假设一个用户业务对应数据业务中一个费率组的业务数据流，当前正在放通中，在当前时间点之后的该用户业务的业务数据流的开始事件(Start of service data flow)出现，则该开始的业务数据流称为“下期用户业务”。考虑用户业务可以并发执行，本期用户业务和下期用户业务在某个时间段上可能并存。
上述生成本期计费控制指令和下期计费控制指令的过程举例如下。
示例3A-1
步骤305-1：计费处理设备授予配额GSU31，确定改用阻塞模式的初始配额申请，生成所述用户业务的下期计费控制指令NxtCmd31＝ToB，保存所述用户业务的初始配额申请模式。
具体地，计费处理设备基于RSU31为所述用户业务授予配额GSU31；计费处理设备基于IqrModInd31判断是否需要更改所述用户业务的初始配额申请模式，在确定需使计费触发设备改用阻塞模式的初始配额申请时，生成NxtCmd31；NxtCmd31示例性取值为“ToB”(To Blocking Mode)，以指示计费触发设备(计费触发设备102或者图1中未显示的计费触发设备)在收到所述用户业务的下一次开始请求(如开始请求StartReq32)时，对所述用户业务采用阻塞模式的初始配额申请；可选地，计费处理设备还可以基于IqrModInd31或NxtCmd31记录或保存所述用户业务当前的初始配额申请模式，以作为下次判断是否需要修改所述用户业务的初始配额申请模式的输入。可选地，计费处理设备也可以不基于IqrModInd31确定需使计费触发设备改用阻塞模式的初始配额申请，进而生成NxtCmd31。
例如，计费处理设备基于IqrModInd31获知当前计费触发设备为所述用户业务采用了非阻塞模式的初始配额申请，且在确定所述用户账户不再满足非阻塞模式的初始配额申请的要求条件时(例如，不再满足“账户中的套餐剩余有效期大于某个阈值”的条件，或者，满足“账户余额下降速度超过某个阈值”等)，从而将形成信用控制风险的情况下，确定需使计费触发设备对所述用户业务改为采用阻塞模式的初始配额申请模式，进而生成NxtCmd31。
再如，计费处理设备也可以在确定用户账户不再满足非阻塞模式的初始配额申请的要求条件时，不管当前计费触发设备为所述用户业务采用了何种模式的初始配额申请的情况下，直接生成NxtCmd31。
应理解，本申请实施例中关于NxtCmd指令的表示方式是示例性的，而非限定，除了上面的表示方式，还可以采用其他的表示方式，例如，可以用“enable NB”表示要采用非阻塞模式的初始配额申请，而用“disable NB”表示要采用阻塞模式的初始配额申请。
具体地，为使计费处理设备在中间计费请求中不上报初始配额申请模式的情况下，也能知道计费触发设备对所述用户采用的初始配额申请模式，计费处理设备还可以进一步在本次计费上下文中记录或者保存当前生效的初始配额申请模式：如果此前未下发过NxtCmd31，则基于IqrModInd31记录或保存所述用户业务的初始配额申请模式IqrMod，如果计费处理设备更新了初始配额申请模式，则记录或保存更新后的初始配额申请模式(例如，NxtCmd31＝ToB，则应该记录或保存所述用户业务的配额申请模式为阻塞模式)。应理解，上述生成NxtCmd31的步骤是可选的，在方法流程图中有相应的“？”标记，反过来说，如果流程图中一个动作后缀一个“？”标记，则表示该动作是可选动作；这种表示方式适用于本申请所有实施例，将不再赘述。
步骤306-1：计费处理设备向计费触发设备发送初始计费响应消息，其中包含GSU31和NxtCmd31。
其中，初始计费响应消息是上述初始计费请求消息对应的响应消息。为叙述方便，本申请实施例中，有时候也将初始计费响应消息简称为初始计费响应，后续将不再赘述。
NxtCmd31是可选的在方法流程图中有相应的“？”标记；反过来说，如果方法流程图中一个消息字段后缀一个“？”标记，则表示该消息字段是可选的；这种表示方式也适用于本申请所有实施例，将不再赘述。
应理解，步骤305-1记录或保存所述用户业务的初始配额申请模式也可以在本步骤中发送初始计费响应消息成功之后再执行。
根据不同用户业务之间是否共享配额，对计费响应消息及其中的NxtCmd的数据结构，分别举例如下(接步骤304举例)。
(1)用户业务独享配额，计费处理设备可以以费率组为单位管理初始配额申请模式，则示例性的计费响应消息为：
Figure PCTCN2021083671-appb-000005
注：MUI是Multiple Unit Information(多单元信息)的缩写；GSU是Granted Service Unit(授予业务单元)的缩写。
(2)不同用户业务之间共享配额，对应步骤304有两种上报初始配额申请模式的方法(基于步骤304的Service1和Service2)：
(2-1)：计费处理设备可以以用户业务为单位管理初始配额申请模式，则示例性的计费响应消息为：
Figure PCTCN2021083671-appb-000006
(2-2)计费处理设备也可以以费率组为单位管理初始配额申请模式：
示例1：使计费触发设备对整个费率组中的所有用户业务都采用阻塞模式(或者说禁止使用非阻塞模式)，示例性的计费响应消息为：
ChargingDataResponse{
"MUI"{
"RG":1；
"NBMode":"disabed"；//NxtCmd31，禁用该费率组的所有用户业务的非阻塞模式，即：Service2的非阻塞模式被禁用(改为阻塞模式)，因Service1原本就是阻塞模式，所以禁用对其没有影响(依然是阻塞模式)
Figure PCTCN2021083671-appb-000007
假设此前该费率组中有的用户业务(如步骤304示例中的Service1的用户业务)已经被采用阻塞模式，则该响应消息(中的NxtCmd31)相当于仅对此前采用非阻塞模式的用户业务(如步骤304示例中的Service2的用户业务)起作用。
示例2：若Service2的非阻塞模式已经被计费处理设备禁用，计费触发设备确定恢复该Service2用户业务的原来初始配额申请模式(即：恢复期采用非阻塞模式)，示例性的计费响应消息为：
ChargingDataResponse{
"MUI"{
"RG":1；
"NBMode":"enabled"；//NxtCmd31,恢复被禁用的初始配额申请模式，即：Service2的初始配额申请模式恢复为原始的非阻塞模式，因Service1原本就是阻塞模式，所以恢复后依然是阻塞模式
Figure PCTCN2021083671-appb-000008
假设此前该费率组中有的用户业务(如步骤304示例中ServiceID为1的用户业务)已经采用阻塞模式，则该响应消息(中的NxtCmd31)相当于仅对此前采用非阻塞模式的用户业务(如步骤304示例中ServiceID为2的用户业务)起作用。
步骤307-1：计费触发设备监控GSU31的使用(将NQUSU作为已使用量)，基于NxtCmd31更新所述用户业务的初始配额申请模式。
具体地，计费触发设备接收并解析步骤306-1的初始计费响应消息，从中获取GSU31和NxtCmd31(如果有)，并且，监控GSU31的使用，此时，将记录的所述用户业务的无配额使用量NQUSU作为配额GSU31的已使用量。
具体地，计费触发设备基于NxtCmd31更新所述用户业务的初始配额申请模式：基于NxtCmd31参数得到所述用户业务的新的初始配额申请模式，并与步骤302对应地，将所述初始配额申请模式保存到本地或外部存储设施保存的所述用户业务的配置信息中，其中在外部存储设施保存的初始配额申请模式可以供多个计费触发设备共用。对于数据业务，更新本地生效的所述用户业务的计费策略中的初始配额申请模式后，进一步向策略控制设备发送策略更新请求，所述策略更新请求中包含更新所述用户业务的初始配额申请模式的指示信息；或 者，不更新本地生效的所述用户业务的计费策略中的初始配额申请模式，而是直接向策略控制设备发送策略更新请求，所述更新请求中包括更新所述用户业务的初始配额申请模式的指示信息，之后，策略控制设备在所述策略更新请求的响应消息中下发所述用户业务的新的计费策略，所述新的计费策略中包含更新后的所述用户业务的初始配额申请模式，所述指示信息可以为禁止对所述用户业务采用非阻塞模式，或者指示对所述用户业务采用阻塞模式。本申请实施例对计费触发设备保存初始配额申请模式的数据结构和存储位置不作限定，例如，可以置于用户业务的配置数据的数据结构中：
Figure PCTCN2021083671-appb-000009
转步骤308。
示例3A-2
步骤305-2：计费处理设备授权失败，且确定需使计费触发设备挂起配额管理/改用阻塞模式的初始配额申请，生成CurCmd32＝HngQm/NxtCmd32＝ToB，保存所述用户业务的初始配额申请模式。
具体地，计费处理设备在为所述用户业务授权失败的情况下，确定应使计费触发设备挂起所述用户业务的配额管理，则生成挂起配额管理的本期计费控制指令CurCmd32，示例的取值为“HngQm”(Hang up quota management，挂起配额管理)；可选地，计费处理设备还可以确定应使计费触发设备对所述用户业务改为采用阻塞模式的初始配额申请，则生成下期计费控制指令NxtCmd32，示例取值为“ToB”。可选地，计费处理设备还可以基于NxtCmd32更新所述用户业务的初始配额申请模式。其中，所述授权失败，包括：余额不足、批价失败、不允许接入所述用户业务等导致授权失败。本申请实施例中，授权失败主要以授予配额失败为例，后续不再赘述。
关于生成CurCmd32，举例如下。
例如，在授予配额失败后，计费处理设备进一步根据所述用户业务的配置信息(如所述用户业务的类型为不可中断业务，或者用户签约协议表明所述用户业务不可中断)确定需使计费触发设备挂起所述用户业务的配额管理，则生成取值为“HngQm”的本期计费控制指令CurCmd32。可选的CurCmd32中还可以包含配额授予失败的指示信息，如“Fail”。
实际部署中，上述挂起配额管理可以实现为对所述用户业务由在线计费转为离线计费，相当于无配额管理，计费触发设备可基于CurCmd32的指示对所述用户业务转为离线计费；上述挂起配额管理也可以实现为对所述用户业务由常规的配额管理转为不限量的配额管理，则计费触发设备可基于CurCmd32的指示对所述用户业务不限配额或者使用一个足够大的配额，并记录该足够大的配额的使用量。
上述常规的配额管理是指计费处理设备基于用户账户余额为用户业务分配配额，而计费 触发设备按计费处理设备授予的配额放通用户业务，并且会因配额的用完而触发向计费处理设备发送用于申请配额的计费请求。
所谓不限量的配额管理，指计费处理设备下发的挂起配额指示(如上文“HngQm”)，计费触发设备将基于该指示对用户业务不限制配额使用量(不会因为配额用完而触发申请配额)，并记录配额的使用量。
针对上述挂起配额管理，如果计费触发设备和计费处理设备既实现了转为离线计费(无配额管理)又实现了不限量的配额管理，这样计费处理设备和计费触发设备都面临两个选择，则上述“HngQm”的指示参数可以用“ToOff”(To Offline Charging，转为离线计费)或“ToNLQM”(To No Litmited Quota Management，转为不限量的配额管理)代替，以示区别。
关于生成下期计费控制指令NxtCmd32，可以参考步骤305-1中的相关描述。
关于记录或保存所述用户业务的初始配额申请模式，可以参考步骤305-1中的相关描述。
步骤306-2：计费处理设备向计费触发设备发送初始计费响应消息，其中包含CurCmd32和NxtCmd32。
其中，NxtCmd32是可选的，计费处理设备可以通过后续的中期计费响应消息中下发将所述用户业务的初始配额申请模式更改为阻塞模式的指示参数。具体参考步骤306-1中的相关描述
步骤307-2：计费触发设备挂起配额管理，基于NxtCmd32更新所述用户业务的初始配额申请模式。
具体地，计费触发设备接收并解析步骤306-2中的初始计费响应消息，从中获取CurCmd32和NxtCmd32(如果有)，并根据CurCmd32挂起所述用户业务的配额管理，具体的，将所述用户业务转为离线计费(相当于无配额管理)或者对所述用户业务进行不限数量的配额管理。此前记录的所述用户业务的无配额使用量，将作为USU上报给计费处理设备进行计费处理。
类似地，计费触发设备还基于NxtCmd32更新所述用户业务的初始配额申请模式，具体参考步骤307-1中的相关描述。
此后转步骤308。
示例3A-3
步骤305-3：计费处理设备授权失败，且确定需中断所述用户业务/改用阻塞模式的初始配额申请，生成CurCmd33＝Fail/NxtCmd33＝ToB，保存所述用户业务的初始配额申请模式。
该步骤与步骤305-2类似，所不同的是，计费处理设备在授权失败后，进一步确定应使计费触发设备中断所述用户业务(如：所述用户业务的类型为可中断业务，或者用户签约协议表明所述用户业务为可中断业务)，如VR业务等娱乐性质业务，则生成本期计费控制指令CurCmd33＝Fail。
应理解，本申请实施例中关于中断用户业务的CurCmd指令的表示方式是示例性的，而非限定，除了上面的表示方式，还可以采用其他的表示方式，例如，还可以用特定结果码指示计费触发设备中断所述用户业务。
关于保存所述用户业务的初始配额申请模式，可以参考步骤305-1中的相关描述。步骤306-3：计费处理设备向计费触发设备发送初始计费响应消息，其中包含CurCmd33和 NxtCmd33。
该步骤与步骤306-2类似，不再赘述。
步骤307-3：计费触发设备中断所述用户业务，上报NQUSU，基于NxtCmd33更新所述用户业务的初始配额申请模式。
其中，基于NxtCmd33更新所述用户业务的初始配额申请模式与步骤307-1类似。
具体地，计费触发设备根据CurCmd33中的“Fail”指示信息，中断所述用户业务，可选地，进一步上报目前为止记录的无配额使用量NQUSU。
由于计费处理设备指示中断所述用户业务，所以该步骤之后将直接转步骤308结束所述用户业务。
应理解，本步骤中，中断所述用户业务和更新所述用户业务的初始配额申请模式之间的顺序不固定。
步骤308：用户业务结束。
具体地，所述用户业务结束可以是用户触发，或者授权失败等。
步骤309：计费触发设备接收所述用户业务的开始请求StartReq32。
具体地，计费触发设备从用户设备接收到StartReq32。
接收所述用户业务的下次开始请求的可能是步骤301-308中的计费触发设备，也可能是其他的计费触发设备，所以步骤309中的计费触发设备与步骤301-308可能是同一个计费触发设备，也可能是不同的计费触发设备。
步骤310：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝B)。
该步骤与步骤302类似，不赘述。该步骤使计费触发设备获知应对所述用户业务采用阻塞模式的初始配额申请，因而确定应先申请配额，后开始用户业务。
步骤311：计费触发设备向计费处理设备发送所述用户业务的初始计费请求消息，其中包括配额申请信息RSU32和初始配额申请模式指示信息IqrModInd32。
具体地，根据所述用户业务的初始配额申请模式为阻塞模式(IqrMod＝B)，确定应先获取配额，假定计费触发设备并没有所述用户业务可用的配额，则先发送所述初始计费请求消息，以申请配额。所述初始配额申请中包含配额申请信息RSU32和初始配额申请模式指示信息IqrModInd32，其中，IqrModInd32与步骤304中的IqrModInd31类似。
步骤312：计费处理设备授予配额GSU32。
具体地，计费处理设备接收并解析步骤311所述初始计费请求消息，从中获取配额申请信息RSU32和初始配额申请模式指示信息IqrModInd32，为所述用户业务授予配额GSU32，基于IqrModInd32记录或保存所述用户业务当前的初始配额申请模式，以作为下次判断是否需要修改所述用户业务的初始配额申请模式的输入；关于授予配额GSU32和基于IqrModInd32记录或保存所述用户业务当前的初始配额申请模式的过程，可以参考步骤305-1中的相关描述。
步骤313：计费处理设备向计费触发设备发送初始计费响应，其中包含授予的配额GSU32。
步骤314：计费触发设备基于GSU32开始用户业务。
上述步骤309-314中还可能会更改所述用户业务的初始配额申请模式，具体参见图3C的步骤341-346，在步骤314之后也可能会更改所述用户业务的初始配额申请模式，具体参见图3D的步骤367-370。
上述步骤301-步骤303的过程中，开始用户业务在申请配额之前，因此这是非阻塞模式的初始配额申请过程；步骤309-步骤314的过程中，开始用户业务在申请到配额之后，因此这是阻塞模式的初始配额申请过程；前后的变化由计费处理设备下发计费控制指令所致。
上述图3A对应的方法流程使得计费处理设备可以在授权失败时，根据所采用的初始配额申请模式判断当前用户业务是否已经开始，进而确定合适的处理措施(如通过指示计费触发设备挂起配额管理或中断用户业务等)处理本期用户业务，进而防止因为计费系统操作造成本期用户业务风险。同时，在发现有信用控制风险时，该方法流程还使得计费处理设备可以及时将计费触发设备对用户业务采用的初始配额申请模式从非阻塞模式改为阻塞模式，可以防止下期用户业务从开始到立即中断的不良用户体验，又可以避免计费系统遭受DOS攻击。
考虑用户业务相关信息(如账户余额等)是动态变化的，所以计费处理设备并不总能在对初始计费请求消息进行处理时就能评估出信用控制风险，而更可能在用户业务开始之后随着用户业务相关信息的变化到一定程度才能评估出，为此，本申请实施例提供了图3B对应的方法流程。
图3B对应的方法流程中，起先计费触发设备对用户业务采用非阻塞模式(第一模式)的初始配额申请，后来计费处理设备通过中期计费响应消息发送计费控制指令，使计费触发设备调整计费操作，例如：挂起/恢复配额管理、中断所述用户业务、对所述用户业务改为采用阻塞模式(第二模式)的初始配额申请等。该方法流程主要包括如下步骤：
步骤321：计费触发设备收到所述用户业务的开始请求StartReq33。
该步骤的内容可参考步骤301。
步骤322：获取所述用户业务的初始配额申请模式IqrMod(＝NB)。
该步骤的内容可参考步骤302。
步骤323：计费触发设备开始所述用户业务，记录无配额使用量NQUSU。
该步骤的内容可参考步骤303。
步骤324：计费触发设备向计费处理设备发送初始计费请求，其中包括配额申请信息RSU33和初始配额申请模式指示信息IqrModInd33。
该步骤的内容可参考步骤304。
步骤325：计费处理设备授予配额GSU33，基于IqrModInd33保存所述用户业务当前的初始配额申请模式。
该步骤的内容可参考步骤305-1，区别为步骤305-1确定需要更改所述用户业务的初始配额申请模式，而本步骤确定不需要更改所述用户业务的初始配额申请模式(原因例如：未发现信用控制风险)。步骤326：计费处理设备向计费触发设备发送初始计费响应，其中包括GSU33。
步骤327：计费触发设备监控GSU33的使用(NQUSU作为已使用量)。
具体地，计费触发设备接收并解析步骤326所述初始计费响应消息，从中获取GSU33，管理GSU33的使用，此时，将记录的所述用户业务的无配额使用量NQUSU作为配额GSU31的已使用量。
此后，计费触发设备通过中期计费请求向计费处理设备请求计费处理。中期计费请求可能包含配额申请信息RSU，也可能包含使用量USU，分别如步骤328-1和步骤328-4所示。
步骤328-1：计费触发设备向计费处理设备发送中期计费请求，其中包含配额申请信息RSU34和初始配额申请模式指示信息IqrModInd33。
具体地，为了从计费处理设备申请配额以维持放通所述用户业务，计费触发设备向计费处理设备发送所述中期计费请求消息，其中包括配额申请信息RSU34和初始配额申请模式指示信息IqrModInd33，且IqrModInd33为可选的。当所述中期计费请求中不包含IqrModInd33时，计费处理设备根据步骤325中保存的所述用户业务当前的初始配额申请模式，确定此前计费触发设备对所述用户业务采用非阻塞模式的初始配额申请模式。
在接收到步骤328-1的中期计费请求后，根据所述用户业务的账户信息的情况、所述用户业务的信息的不同，有不同的计费处理，举例如下。
示例3B-1
步骤329-1：计费处理设备授予配额GSU34，确定改用阻塞模式，生成NxtCmd34＝ToB，保存IqrMod。
其中，生成NxtCmd34是可选的；该步骤的内容可参考步骤305-1。
步骤330-1：计费处理设备向计费触发设备发送中期计费响应，其中包含GSU34和NxtCmd34。
该步骤与步骤306-1类似，除了用中期计费响应消息替代初始计费响应消息外，其他可参考步骤306-1。
步骤331-1：计费触发设备监控GSU34的使用，基于NxtCmd34更新所述用户业务的初始配额申请模式。
该步骤与步骤307-1类似，所不同的是，由于此前不存在无配额使用量，本步骤无需在GSU34中扣减无配额使用量。
转步骤332。
示例3B-2
步骤329-2：计费处理设备为所述用户业务授权失败，确定需挂起所述用户业务的配额管理/改用阻塞模式的初始配额申请，生成CurCmd35＝HngQm/NxtCmd35＝ToB，保存IqrMod。
该步骤的内容可参考步骤305-2。
步骤330-2：计费处理设备向计费触发设备发送中期计费响应，其中包含CurCmd35和NxtCmd35。
该步骤与步骤306-2类似，除了用中期计费响应消息替代初始计费响应消息外，其他可参考步骤306-2。
步骤331-2：计费触发设备挂起配额管理，基于NxtCmd35更新所述用户业务的初始配额申请模式。
该步骤的内容可参考步骤307-2。
转步骤332。
示例3B-3
步骤329-3：计费处理设备为所述用户业务授权失败，且确定需中断所述用户业务/改用阻塞模式的初始配额申请，生成CurCmd36＝Fail/NxtCmd36＝ToB，保存IqrMod。
该步骤的内容可参考步骤305-3。
步骤330-3：计费处理设备向计费触发设备发送中期计费响应，其中包含CurCmd36和NxtCmd36。
该步骤与步骤306-3类似，除了用中期计费响应消息替代初始计费响应消息外，其他可参考步骤306-3。
步骤331-3：计费触发设备中断所述用户业务，基于NxtCmd36更新所述用户业务的初始配额申请模式。
该步骤的内容可参考步骤307-3。
转步骤333。
示例3B-4
步骤328-4：计费触发设备向计费处理设备发送中期计费请求，其中包含使用量信息USU34和初始配额申请模式指示信息IqrModInd33。
具体地，为了上报使用量信息给计费计费处理设备进行计费处理，计费触发设备向计费处理设备发送中期计费请求消息，其中包括使用量信息USU34；为了使计费处理设备获知所述用户业务的初始配额申请模式，所述中期计费请求还可以包含初始配额申请模式指示信息IqrModInd33，也就是说IqrModInd33为可选。IqrModInd33的内容可以参考步骤304中的IqrModInd31。当所述中期计费请求中不包含IqrModInd33时，计费处理设备根据步骤325中保存的所述用户业务当前的初始配额申请模式，确定此前计费触发设备对所述用户业务采用非阻塞模式的初始配额申请。
在接收到步骤328-2的中期计费请求后，根据所述用户业务的账户信息的情况、所述用户业务的信息，计费处理过程举例如下。
步骤329-4：计费处理设备确定需改用阻塞模式的初始配额申请/恢复所述用户业务的配额管理，生成NxtCmd37＝ToB/CurCmd37＝RsmQm；保存IqrMod。
具体地，计费处理设备接收并解析步骤328-4所述的中期计费请求，从中获取使用量信息USU34和初始配额申请模式指示信息IqrModInd33(如果有该字段)，计费处理设备基于USU34进行账户余额扣减或者将USU34写入话单，并基于IqrModInd33判断是否需要更改所述用户业务的初始配额申请模式，具体判断方法可参考步骤305-1。在确定需要更改所述用户业务的初始配额申请模式为阻塞模式的情况下，计费处理设备可以进一步确定对所述用户业务的配额管理已经挂起(如转离线计费，所述用户业务的配额管理当前是否挂起在计费处理设备内部有记录)，则可以进一步确定需要恢复配额管理。此时，可为所述用户业务授予配额：虽然此时中期计费请求消息中有USU但没有RSU，也就是无配额请求信息，但计费处理设备根据配置信息或者计费策略确定授予的配额量GSU34X，和/或，生成取值为“RsmQm”(Resume Quota Management,恢复配额管理)的本期计费控制指令CurCmd37，以指示计费触发设备立即恢复对所述用户业务的配额管理。计费处理设备为了恢复所述用户业务的配额管理，可以发送CurCmd37与GSU34X中的任意一个或两个：若只发送CurCmd37，则计费触发设备在收到该指示参数后，可以据此向计费处理设备发送为所述用户业务申请配额的计费请求消息，若只发送GSU34X，则相当于通过GSU34X为计费触发设备指明需要恢复所述用户业务的配额管理，从而计费触发设备可以据此为所述用户业务使用授予的配额GSU34X，且继续向计费处理设备发送为所述用户业务申请配额的计费请求消息。
关于如何确定不能再采用非阻塞模式的初始配额申请，可以参考图3A对应的方法流程 中的相关说明。计费处理设备确定需要恢复所述用户业务的配额管理的因素可以包括：确定需更改用户业务的初始配额申请模式为阻塞模式，且进一步确定当前存在信用控制风险。
如此，通过恢复配额管理可以降低本期用户业务的信用控制风险，通过更改所述用户业务的初始配额申请模式为阻塞模式可以降低下期用户业务的信用控制风险。
应理解，本申请实施例中关于恢复配额管理的CurCmd指令的表示方式是示例性的，而非限定，除了上面的方式，还可以采用其他的方式，例如，还可以用“enable QM”指示计费触发设备恢复配额管理，而用“disable QM”指示计费触发设备挂起配额管理。
关于计费处理设备记录或保存所述用户业务的初始配额申请模式IqrMod的过程，可以参考图3A对应方法流程中的相关描述，如步骤305-1、305-2等。
步骤330-4：计费处理设备向计费触发设备发送中期计费响应，其中包含CurCmd37、GSU34X和NxtCmd37。
该步骤的内容可参考步骤330-3的描述，其中可选参数是否携带具体参见步骤329-4生成参数的描述。
步骤331-4：计费触发设备恢复配额管理，基于NxtCmd37更新所述用户业务的初始配额申请模式。
具体地，计费触发设备接收并解析步骤330-4所述的中期计费响应，并执行以下操作：
如果所述计费响应中只有GSU34X(而无CurCmd37＝RsmQm等)，则恢复所述用户业务的配额管理，并为所述用户业务使用GSU34X(基于GSU34X放通所述用户业务)；或者
如果所述计费响应中有CurCmd37＝RsmQm(而无GSU34X)，则恢复所述用户业务的配额管理，并向计费处理设备发送用于申请配额的计费请求消息；
如果所述计费响应中有CurCmd37＝RsmQm和GSU34X,则根据CurCmd37＝RsmQm恢复所述用户业务的配额管理，并为所述用户业务使用GSU34X(基于GSU34X放通所述用户业务)；
关于基于NxtCmd37更新所述用户业务的初始配额申请模式的过程，可以参考步骤307-1的描述。
步骤332：所述用户业务结束。
该步骤的内容可参考步骤308。
步骤333：计费触发设备收到所述用户业务的开始请求StartReq34。
该步骤的内容可参考步骤309。
步骤334：计费触发设备获取所述用户业务的IqrMod(＝B)。
该步骤的内容可参考步骤310。
步骤335：计费触发设备向计费处理设备发送初始计费请求，其中包含配额申请信息RSU35和初始配额申请模式指示信息IqrModInd34。
该步骤的内容可参考步骤311。
步骤336：计费处理设备授予配额GSU35，保存IqrMod。
该步骤的内容可参考步骤312。
步骤337：计费处理设备向计费触发设备发送初始计费响应，其中包含授予的配额GSU35。
该步骤的内容可参考步骤313。
步骤338：计费触发设备基于GSU35开始所述用户业务。
该步骤的内容可参考步骤314。
上述步骤333-338中还可能会更改所述用户业务的初始配额申请模式，具体参见图3C的步骤341-346，在步骤338之后也可能会更改所述用户业务的初始配额申请模式，具体参见图3D的步骤367-370。
相对于图3A对应的方法流程，上述图3B对应的方法流程使得计费处理设备可以拥有更多的决策机会，更及时地平衡信用风险控制的需求和接入时延的需求(而不必等到用户业务再次开始)。
上述图3A和图3B对应的方法流程可以用于计费触发设备现有初始配额申请模式为非阻塞模式的场景，对于计费触发设备现有初始配额申请模式为阻塞模式的场景，本申请实施例提供图3C和图3D对应的方法流程。
图3C对应的方法流程中，起先计费触发设备对用户业务采用阻塞模式(第一模式)的初始配额申请，后来计费处理设备通过初始计费响应消息发送计费控制指令，使计费触发设备调整计费操作，例如：挂起配额管理、对所述用户业务改为采用非阻塞模式(第二模式)的初始配额申请。该方法流程主要包括如下步骤：
步骤341：计费触发设备收到所述用户业务的开始请求StartReq35。
该步骤的内容可参考步骤301。
步骤342：计费触发设备获取用户业务的初始配额申请模式IqrMod(＝B)
该步骤的内容可参考步骤302，所不同的是，本步骤获取的所述用户业务的初始配额申请模式为阻塞模式。
步骤343：计费触发设备向计费处理设备发送初始计费请求，其中包括配额申请信息RSU36和初始配额申请模式指示信息IqrModInd35。
由于初始配额申请模式为阻塞模式，计费触发设备在开始所述用户业务之前，先向计费处理设备申请配额，具体地，向计费处理设备发送所述初始计费请求，其中包括配额申请信息RSU36和初始配额申请模式指示信息IqrModInd35。关于IqrModInd35的内容，可以参考步骤304中IqrModInd31。
计费处理设备接收并解析上述初始计费请求，基于其中IqrModInd35所指示的情况(即所述计费触发设备对所述用户业务采用阻塞模式的初始配额申请)，对所述用户业务进行计费处理，生成本期计费控制指令CurCmd和/或下期计费控制指令NxtCmd，下发给计费触发设备执行。
步骤344：计费处理设备授予配额GSU36，确定应改用非阻塞模式/挂起配额管理，生成NxtCmd38＝ToNB/CurCmd38＝HngQm，保存IqrMod。
具体地，计费处理设备基于IqrModInd35所指示的情况，且在确定非阻塞模式的要求条件满足的情况下，确定应对所述用户业务改为采用非阻塞模式的初始配额申请，进而生成NxtCmd38。可选的，也可以不基于IqrModInd35所指示的情况，但确定非阻塞模式的要求条件满足的情况下，确定应对所述用户业务采用非阻塞模式的初始配额申请，进而生成NxtCmd38。可选地，在非阻塞模式的要求条件满足的情况下，计费处理设备还可以挂起所述用户业务当前的配额管理(由于非阻塞模式的要求条件满足意味着当前信用控制风险低)，进而生成CurCmd38，若确定挂起配额管理，则不为所述用户业务授予配额。
例如，计费处理设备获知当前计费触发设备为所述用户业务采用了阻塞模式的初始配额 申请，且在确定所述用户账户满足非阻塞模式的初始配额申请的要求条件时(例如，满足“账户中的套餐剩余有效期大于某个阈值”的条件，或者，满足“账户余额下降速度低于某个阈值”等)，从而确认信用控制风险低的情况下，确定需使计费触发设备对所述用户业务改为采用非阻塞模式的初始配额申请模式，进而生成NxtCmd38。
再如，计费处理设备也可以在确定用户账户满足非阻塞模式的要求条件，不管当前计费触发设备为所述用户业务采用了何种模式的初始配额申请，直接生成NxtCmd38。
NxtCmd38取值为“ToNB”(To Non-Blocking Mode，转为非阻塞模式)，以指示计费触发设备在再次收到所述用户业务的开始请求时，对所述用户业务采用非阻塞模式的初始配额申请。
可选地，计费处理设备可以基于IqrModInd35所指示的情况，对所述用户业务进行计费处理，包括针对RSU36授予配额GSU36，且在授予配额过程确定所述用户业务的信用控制风险较低而无需对本期用户业务进行在线信用控制，进而生成取值为“HngQm”的CurCmd38，以指示计费触发设备挂起本期所述用户业务的配额管理，这样可以适时地、在一定程度上降低计费处理设备和计费触发设备的性能负担，毕竟可以减少在两者之间的信息交互次数。
关于记录或保存所述用户业务的当前生效的初始配额申请模式的过程，可以参考步骤305-1中的相关描述。
步骤345：计费处理设备向计费触发设备发送初始计费响应消息，其中包含GSU36、CurCmd38和NxtCmd38。
其中，GSU36和CurCmd38都是可选的。
步骤346：计费触发设备基于GSU36开始所述用户业务，挂起配额管理，基于NxtCmd38更新所述用户业务的初始配额申请模式。
具体地，计费触发设备接收并解析步骤345-1所述的初始计费响应消息，从中获取GSU36(如果有)、CurCmd38(如果有)和NxtCmd38。若所述响应消息携带有GSU36，则基于GSU36开始所述用户业务并进行配额管理，若所述响应消息携带CurCmd38而不携带GSU36，则根据CurCmd38挂起所述用户业务的配额管理；关于计费触发设备基于NxtCmd38更新所述用户业务的初始配额申请模式，可以参考步骤307-1中的相关描述。
步骤347：用户业务结束。
该步骤的内容可参考步骤308。
步骤348：计费触发设备接收所述用户业务的开始请求StartReq36。
该步骤的内容可参考步骤321。
步骤349：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝NB)。
该步骤的内容可参考步骤322。
步骤350：计费触发设备开始所述用户业务，记录无配额使用量NQUSU。
该步骤的内容可参考步骤323。
步骤351：计费触发设备向计费处理设备发送初始计费请求，其中包含配额申请信息RSU37和初始配额申请模式指示信息IqrModInd36。
该步骤的内容可参考步骤324。
步骤352：计费处理设备授予配额GSU37，保存IqrMod。
该步骤的内容可参考步骤325。
步骤353：计费处理设备向计费触发设备发送初始计费响应消息，其中包含授予的配额GSU37。
该步骤的内容可参考步骤326。
步骤354：计费触发设备监控GSU37的使用(先扣减NQUSU)。
该步骤的内容可参考步骤327。
上述步骤348-354中还可能会更改所述用户业务的初始配额申请模式，具体参见图3A的步骤301-307，在步骤354之后也可能会更改所述用户业务的初始配额申请模式，具体参见图3B的步骤328-332。
上述步骤341-步骤346-1、步骤346-2的过程中，开始用户业务在申请配额之后，因此是阻塞模式的初始配额申请，步骤348-步骤354，开始用户业务在申请到配额之前，为非阻塞模式的初始配额申请，前后的变化由计费处理设备下发计费控制指令所致。
上述图3C对应的方法流程使得计费处理设备可以及时地将用户业务的初始配额申请模式从阻塞模式调整为非阻塞模式，有利于及时满足时延敏感性业务对接入时延的需求；在此基础上，该方法流程还使得计费处理设备及时挂起配额管理，以减少计费触发设备和计费处理设备之间的通信交互和数据处理，从而可以进一步减轻计费触发设备和计费处理设备的性能负担。
图3D对应的方法流程中，起先计费触发设备对用户业务采用阻塞模式(第一模式)的初始配额申请，后来计费处理设备通过中期计费响应消息发送计费控制指令，使计费触发设备调整计费操作，例如：挂起配额管理、对所述用户业务改为采用非阻塞模式(第二模式)的初始配额申请等。该方法流程主要包括如下步骤：
步骤361：计费触发设备收到用户业务的开始请求StartReq37。
该步骤的内容可参考步骤309。
步骤362：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝B)。
该步骤的内容可参考步骤310。
步骤363：计费触发设备向计费处理设备发送初始计费请求消息，其中包括配额申请信息RSU38和初始配额申请模式指示信息IqrModInd37。
该步骤的内容可参考步骤311。
步骤364：计费处理设备授予配额GSU38，保存所述用户业务的初始配额申请模式。
具体地，计费处理设备根据RSU38授予相应的配额GSU38，基于IqrModInd37记录或保存所述用户业务的初始配额申请模式，具体可参考步骤305-1、305-2中的相关描述。
步骤365：计费处理设备向计费触发设备发送初始计费响应消息，其中包括GSU38。
该步骤的内容可参考步骤313。
步骤366：计费触发设备基于GSU38开始所述用户业务。
该步骤的内容可参考步骤314。
至此，所述用户业务已经开始，计费触发设备可以继续向计费处理设备申请配额，以维持放通所述用户业务，具体如下述步骤所示。
步骤367：计费触发设备向计费处理设备发送中期计费请求，其中包含配额申请信息RSU39和初始配额申请模式指示信息IqrModInd37，其中，IqrModInd37为可选。
当所述中期计费请求不包含IqrModInd37的情况下，计费处理设备可以根据步骤364所记录或保存的初始配额申请模式确定计费触发设备对所述用户业务采用阻塞模式的初始配额申请。
计费处理设备接收并解析所述中期计费请求，从中获取配额申请信息RSU39和初始配额申请模式指示信息IqrModInd37，进而进行计费处理。
步骤368：计费处理设备授予配额GSU39，生成CurCmd3a＝HngQm/NxtCmd3a＝ToNB，保存IqrMod。
该步骤的内容可参考步骤344。
步骤369：计费处理设备向计费触发设备发送中期计费响应，其中包含GSU39、CurCmd3a和NxtCmd3a。
该步骤与步骤345类似,本步骤除了用中期计费响应代替步骤345的初始计费响应外，其余可参考步骤345。
步骤370：计费触发设备继续所述用户业务，挂起所述用户业务的配额管理，基于NxtCmd3a更新所述用户业务的初始配额申请模式。
具体地，计费触发设备接收并解析步骤369所述的中期计费响应消息，从中获取GSU39(如果有)、CurCmd3a和NxtCmd3a，若所述响应消息携带有GSU39，则监控所述用户业务对授予配额GSU39的使用，若所述响应消息携带CurCmd3a＝HngQm而不携带GSU39，则挂起所述用户业务的配额管理(如转成离线计费)；计费触发设备基于NxtCmd3a＝ToNB更新所述用户业务的初始配额申请模式，以在计费触发设备收到所述用户业务的下次开始请求时对所述用户业务采用非阻塞模式的初始配额申请。
步骤371：用户业务结束。
该步骤的内容可参考步骤308。
步骤372：计费触发设备接收所述用户业务的开始请求StartReq38。
该步骤的内容可参考步骤321。
步骤373：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝NB)。
该步骤的内容可参考步骤322。
步骤374：计费触发设备开始所述用户业务，记录无配额使用量NQUSU。
该步骤的内容可参考步骤323。
步骤375：计费触发设备向计费处理设备发送初始计费请求，其中包含配额申请信息RSU3a和初始配额申请模式指示信息IqrModInd38。
该步骤的内容可参考步骤324。
步骤376：计费处理设备授予配额GSU3a，保存IqrMod。
该步骤的内容可参考步骤325。
步骤377：计费处理设备向计费触发设备发送初始计费响应消息，其中包含授予的配额GSU3a。
该步骤的内容可参考步骤326。
步骤378：计费触发设备监控GSU3a的使用(先扣减NQUSU)。
该步骤的内容可参考步骤327。
上述步骤372-378中还可能会更改所述用户业务的初始配额申请模式，具体参见图3A 的步骤301-307，在步骤378之后也可能会更改所述用户业务的初始配额申请模式，具体参见图3B的步骤328-S332。
相对于图3C对应的方法流程，上述图3D对应的方法流程使得计费处理设备可以拥有更多的决策机会，更及时地平衡信用控制的需求、资源利用率的需求和接入时延的需求。
上述图3A-图3D对应的方法流程均是通过对用户业务本身的计费处理而获得该用户业务的账户余额、账户状态、账户使用趋势等信息，据此发送计费控制指令。但事实上，当多个用户业务对应相同的用户账户时(例如，一个用户从运营商订购了多个用户业务)，则还可以通过“兄弟业务”(或者称为“其他业务”，是指与所述用户业务对应相同的账户的业务)的计费处理而获得这些信息，甚至还可以通过对用户业务的对应的账户的管理消息(如来自BSS系统的账户管理消息)获得这些信息，进而根据这些信息向计费触发设备发送计费控制指令。为此，本申请实施例进一步提供了图4A-图4B对应的方法流程，下面分别进行描述。
图4A对应的方法流程中，起先计费触发设备对用户业务采用非阻塞模式(第一模式)的初始配额申请，后来计费处理设备通过计费通知消息发送计费控制指令，使计费触发设备调整计费操作，例如：恢复所述用户业务的配额管理、对所述用户业务改为采用阻塞模式(第二模式)的初始配额申请等。该方法流程主要包括如下步骤：
步骤401：计费触发设备接收所述用户业务的开始请求StartReq41。
该步骤的内容可参考步骤321。
步骤402：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝NB)。
该步骤的内容可参考步骤322。
步骤403：计费触发设备开始所述用户业务，记录无配额使用量NQUSU。
该步骤的内容可参考步骤323。
步骤404：计费触发设备向计费处理设备发送初始计费请求，其中包含配额申请信息RSU41和初始配额申请模式指示信息IqrModInd41。
该步骤的内容可参考步骤324。
步骤405：计费处理设备授予配额GSU41，保存IqrMod。
该步骤的内容可参考步骤325。
步骤406：计费处理设备向计费触发设备发送初始计费响应消息，其中包含授予的配额GSU41。
该步骤的内容可参考步骤326。
步骤407：计费触发设备监控GSU41的使用(NQUSU作为配额的已使用量)。
该步骤的内容可参考步骤327。
此后计费处理设备持续为所述用户业务授予配额(基于计费触发设备发送的计费请求)，使所述用户持续被放通；与此同时，计费处理设备还可能为其他用户业务进行计费处理，所述其他用户业务与所述用户业务对应相同的账户，还可能接收关于所述用户业务的属性信息的变化事件(如所述用户业务的套餐变更不足，用户等级的降低，等等)，则计费处理设备也可以基于所述其他用户业务的计费处理结果、所述用户业务的属性信息的变化事件等，向计费触发设备发送计费控制指令，以调整计费触发设备对所述用户业务的计费操作，例如，恢复对用户业务的配额管理、改为采用阻塞模式的初始配额申请。
步骤408：计费处理设备确定应改用阻塞模式/恢复配额管理，生成下期计费控制指令NxtCmd41＝ToB/本期计费控制指令CurCmd41＝RsmQm，保存所述用户业务的初始配额申请模式IqrMod。
具体地，计费处理设备确定应使计费触发设备对所述用户业务改为采用阻塞模式的配额管理，进而生成取值为“ToB”的下期计费控制指令NxtCmd41；在此基础上，可选地，计费处理设备还可以生成取值为“RsmQm”的本期计费控制指令CurCmd41；可选地，计费处理设备还可以基于NxtCmd41的生成情况，保存/更新初始配额申请模式指示信息。
具体地，计费处理设备根据根据此前为所述用户业务保存的初始配额申请模式，确定此前计费触发设备对所述用户业务采用非阻塞模式的初始配额申请，且根据对“兄弟业务”或“其他用户业务”的计费请求消息的计费处理结果，或者根据所述用户业务的账户的管理消息(例如，来自商业支撑系统，Business Support System，BSS的账户管理消息)的处理，发现所述用户业务的非阻塞模式的要求条件不满足，因而生成NxtCmd41。关于非阻塞模式的要求条件不满足的情况，本申请实施例不作限定，例如，对所述其他用户业务的计费处理结果表明，所述用户业务的账户(也是所述其他用户业务对应的账户)不再满足非阻塞模式的初始配额申请的要求条件，再如，计费处理设备收到的事件表明所述用户业务对应的用户的等级降低了，等等。
可选地，如果计费处理设备发现所述用户业务的配额管理已挂起(意味着可能已采用离线计费，或者不限量的配额管理)，若此时所述用户业务的账户(也是所述其他用户业务对应的账户)不再满足非阻塞模式的初始配额申请的要求条件，意味着信用控制风险变高，为降低信用控制风险，还可以生成取值为“RsmQm”的CurCmd41，以指示计费触发设备及时恢复所述用户业务的配额管理。
关于保存/更新所述用户业务初始配额申请模式的过程，可以参考步骤305-1中的相关描述。
步骤409：计费处理设备向计费触发设备发送通知请求，其中包含CurCmd41和NxtCmd41。
具体地，为将步骤408-1所生成的计费控制指令更及时地发送给计费触发设备，计费处理设备生成通知请求消息，其中包含所述CurCmd41和NxtCmd41，并将所述通知请求消息发送给计费触发设备；其中，CurCmd41是可选的；所述通知请求消息的通知地址(NotifyURL)可以标识计费触发设备及用户业务；如果所述用户业务为数据业务，则所述通知请求消息进一步还可以携带所述用户业务所在的费率组的标识RG。
步骤410：计费触发设备恢复配额管理，基于NxtCmd41更新所述用户业务的初始配额申请模式。
具体地，计费触发设备接收并解析所述通知请求消息，从中获取CurCmd41和NxtCmd41，在此基础上，对所述用户业务执行CurCmd41和NxtCmd41，具体是，恢复所述用户业务的配额管理(意味着，计费触发设备重新开始为所述用户业务向计费处理设备请求配额)，基于NxtCmd41更改所述用户业务的初始配额申请模式(例如，可以保存在计费触发设备本地，也可以保存到外部存储设施，或者发送给策略控制设备，具体可参考步骤307-1)，以在计费触发设备收到所述用户业务的下次开始请求时，对所述用户业务采用阻塞模式的初始配额申请。
步骤411：计费触发设备向计费处理设备返回通知响应消息。
具体地，计费触发设备根据步骤410的处理结果，向计费处理设备返回通知响应消息，其中包含指示步骤409的通知请求已得到成功处理的信息。
步骤412：所述用户业务结束。
该步骤的内容可参考步骤308。
步骤413：计费触发设备收到所述用户业务的开始请求StartReq42。
该步骤的内容可参考步骤333。
步骤414：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝B)。
该步骤的内容可参考步骤334。
步骤415：计费触发设备向计费处理设备发送初始计费请求，其中包含配额申请信息RSU32和初始配额申请模式指示信息IqrModInd42。
该步骤的内容可参考步骤335。
步骤416：计费处理设备授予配额GSU42，保存IqrMod。
该步骤的内容可参考步骤336。
步骤417：计费处理设备向计费触发设备发送初始计费响应消息，其中包含GSU42。
该步骤的内容可参考步骤337。
步骤418：计费触发设备基于GSU42开始所述用户业务。
该步骤的内容可参考步骤338。
上述步骤413-418中还可能会更改所述用户业务的初始配额申请模式，具体参见图3C的步骤341-346，在步骤418之后也可能会更改所述用户业务的初始配额申请模式，具体参见图3D的步骤367-370。
相对于上述图3A-图3B对应的方法流程，上述图4A对应的方法流程又进一步扩大了计费处理设备发现风险并作出决策的机会，从对用户业务进行计费处理上下文，扩大到了对其他用户业务的计费处理上下文，甚至对运营支撑系统的管理消息进行处理的上下文。
图4B对应的方法流程中，起先计费触发设备对用户业务采用阻塞模式(第一模式)的初始配额申请，后来计费处理设备通过计费通知消息发送计费控制指令，使计费触发设备调整计费操作，例如：挂起所述用户业务的配额管理、对所述用户业务改为采用非阻塞模式(第二模式)的初始配额申请等。该方法流程主要包括如下步骤：
步骤441：计费触发设备收到用户业务的开始请求StartReq43。
该步骤的内容可参考步骤309。
步骤442：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝B)。
该步骤的内容可参考步骤310。
步骤443：计费触发设备向计费处理设备发送初始计费请求消息，其中包括配额申请信息RSU46和初始配额申请模式指示信息IqrModInd43。
该步骤的内容可参考步骤311。
步骤444：计费处理设备授予配额GSU46，保存IqrMod。
具体地，计费处理设备根据配额申请信息RSU46授予相应的配额GSU46，基于IqrModInd43记录或保存所述用户业务的初始配额申请模式IqrMod，具体可参考步骤305-1中的相关描述。。
步骤445：计费处理设备向计费触发设备发送初始计费响应消息，其中包括GSU46。
该步骤的内容可参考步骤313。
步骤446：计费触发设备基于GSU46开始所述用户业务。
该步骤的内容可参考步骤314。
此后计费处理设备持续为所述用户业务授予配额(基于计费触发设备发送的计费请求)，使所述用户持续被放通；与此同时，计费处理设备还可能为其他用户业务进行计费处理，所述其他用户业务与所述用户业务对应相同的账户，还可能接收关于所述用户业务的属性信息的变化事件(如所述用户业务的套餐变更：延期，用户等级的提升，账户充值等等)，则计费处理设备也可以基于所述其他用户业务的计费处理结果、所述用户业务的属性信息的变化事件等，向计费触发设备发送计费控制指令，以调整计费触发设备对所述用户业务的计费操作，例如，挂起对用户业务的配额管理、改为采用非阻塞模式的初始配额申请。
步骤447：计费处理设备确定应改用非阻塞模式/挂起配额管理，生成下期计费控制指令NxtCmd43＝ToNB/本期计费控制指令CurCmd43＝HngQm，保存IqrMod。
具体地，计费处理设备确定应使计费触发设备对所述用户业务改为采用非阻塞模式的配额管理，进而生成取值为“ToNB”的下期计费控制指令NxtCmd43；在此基础上，可选地，计费处理设备还可以生成取值为“HngQm”的本期计费控制指令CurCmd43；可选地，计费处理设备还可以基于NxtCmd43的生成情况，保存/更新初始配额申请模式指示信息。
具体地，计费处理设备根据根据此前为所述用户业务保存的初始配额申请模式，确定此前计费触发设备对所述用户业务采用阻塞模式的初始配额申请；此时，计费处理设备发现非阻塞模式的要求条件满足，因而生成取值为“ToNB”的NxtCmd43。关于非阻塞模式的要求条件满足的情况，本申请实施例不作限定，例如，对所述其他用户业务的计费处理结果表明，所述用户业务的账户(也是所述其他用户业务对应的账户)满足阻塞模式的初始配额申请的要求条件，再如，计费处理设备收到的事件表明所述用户业务对应的用户的等级提高了。
此外，若此时所述用户业务的账户(也是所述其他用户业务对应的账户)满足非阻塞模式的初始配额申请的要求条件，意味着信用控制风险变低，为了降低系统负载，还可以生成取值为“HngQm”的CurCmd43，以指示计费触发设备及时挂起所述用户业务的配额管理。
关于保存/更新初始配额申请模式，可以参考步骤305-1中的相关描述。
步骤448：计费处理设备向计费触发设备发送通知请求，其中包含CurCmd43和NxtCmd43。
该步骤的内容可以参考步骤409-1。
步骤449：计费触发设备挂起配额管理，基于NxtCmd43更改所述用户业务的初始配额申请模式。
具体地，计费触发设备接收并解析所述通知请求消息，从中获取CurCmd43和NxtCmd43，在此基础上，对所述用户业务执行CurCmd43和NxtCmd43，具体是，挂起所述用户业务的配额管理(如果是转离线计费，则意味着，计费触发设备不再为所述用户业务向计费处理设备请求配额，如果是不限配额，则意味着，计费触发设备基于积累的使用量向计费处理设备申请等量的配额)，基于NxtCmd43更改所述用户业务的初始配额申请模式(例如，可以保存在计费触发设备本地，也可以保存到外部存储设施，或者发送给策略控制设备，具体可参考步骤307-1)，以在计费触发设备收到所述用户业务的下次开始请求时，对所述用户业务采用非阻塞模式的初始配额申请。
步骤450：计费触发设备向计费处理设备返回通知响应消息。
具体地，计费触发设备根据步骤449的处理结果，向计费处理设备返回通知响应消息，其中包含指示步骤448的通知请求已得到成功处理的信息。
步骤451：所述用户业务结束。
该步骤的内容可参考步骤308。
步骤452：计费触发设备接收所述用户业务的开始请求StartReq44。
该步骤的内容可参考步骤321。
步骤453：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝NB)。
该步骤的内容可参考步骤322。
步骤454：计费触发设备开始所述用户业务，记录无配额使用量NQUSU。
该步骤的内容可参考步骤323。
步骤455：计费触发设备向计费处理设备发送初始计费请求，其中包含配额申请信息RSU47和初始配额申请模式指示信息IqrModInd44，IqrModInd44指明计费触发设备对所述用户业务采用非阻塞模式的初始配额申请。
该步骤的内容可参考步骤324。
步骤456：计费处理设备授予配额GSU47，保存IqrMod。
该步骤的内容可参考步骤325。
步骤457：计费处理设备向计费触发设备发送初始计费响应消息，其中包含授予的配额GSU47。
该步骤的内容可参考步骤326。
步骤458：计费触发设备监控GSU47的使用(先扣减NQUSU)。
该步骤的内容可参考步骤327。
上述步骤452-458中还可能会更改所述用户业务的初始配额申请模式，具体参见图3C的步骤341-346，在步骤458之后也可能会更改所述用户业务的初始配额申请模式，具体参见图3D的步骤367-370。
相对于上述图3C-图3D对应的方法流程，上述图4B对应的方法流程又进一步扩大了计费处理设备发现低风险、降低用户业务接入时延的机会，从对用户业务进行计费处理上下文，扩大到了对其他用户业务的计费处理上下文，甚至对运营支撑系统的管理消息进行处理的上下文。
上述图3A-图3D以及图4A-图4B对应的方法流程都是以计费处理设备为控制者，计费触发设备为被控制者。但关于初始配额申请模式的切换或改变，计费触发设备也可以基于计费处理设备返回的结果参与决策。为此，本申请实施例提供了图5A-图5B对应的方法流程，下面分别进行描述。
图5A对应方法流程中，起先计费触发设备对用户业务采用非阻塞模式(第一模式)的初始配额申请，计费处理设备据此控制计费触发设备对本期用户业务的计费操作，计费触发设备根据计费处理设备返回的计费处理结果，对所述用户业务改为采用阻塞模式(第二模式)的初始配额申请，该方法流程主要包括如下步骤：
步骤501：计费触发设备收到用户业务的开始请求StartReq51。
该步骤的内容可以参考步骤301。
为确定开始所述用户业务和为所述用户业务申请配额的时间顺序，计费触发设备先获取所述用户业务的初始配额申请模式，如步骤502-1或者步骤502-2所示。
步骤502-1：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝NB)。
具体地，计费触发设备可以根据本地或外部存储设施保存的所述用户业务的配置信息得到所述用户业务的初始配额申请模式，或者从策略控制设备激活的所述用户业务的计费策略中获取所述用户业务的初始配额申请模式，为非阻塞模式,进而确定应对所述用户业务采用非阻塞模式的初始配额申请。
转步骤503。
步骤502-2：
若本地无所述用户业务的计费策略，则可以向策略控制设备请求所述用户业务的计费策略。
步骤502-2-1：计费触发设备向策略控制设备发送策略请求消息。
其中，所述策略请求消息包含用户标识、PDU会话的信息等可以用于标识所述用户业务的信息。
步骤502-2-2：策略控制设备向计费触发设备返回策略响应消息，其中包含所述用户业务的初始配额申请模式。
具体地，策略控制设备返回计费策略，其中包含所述用户业务的初始配额申请模式。
从而，计费触发设备可以接收并解析所述策略响应消息，从中获取所述用户业务的初始配额申请模式，，进而确定应对所述用户业务采用非阻塞模式的初始配额申请。
步骤503：计费触发设备开始所述用户业务，记录无配额使用量NQUSU。
具体地，由于计费触发设备此前确定应对所述用户业务采用非阻塞模式的初始配额申请，则立即开始所述用户业务(而不等待计费处理设备授予的配额)，且开始记录无配额情况下的使用量NQUSU。
步骤504：计费触发设备向计费处理设备发送计费请求消息，其中包含配额申请信息RSU51和初始配额申请模式指示信息IqrModInd51。
具体地，在所述用户业务开始之后，为维持放通所述用户业务，计费触发设备向计费处理设备发送计费请求消息；该计费请求消息可以是初始计费请求消息，也可以是中期计费请求消息；当该计费请求消息为初始计费请求消息时，其中包含配额申请信息RSU51和初始配额申请模式指示信息IqrModInd51；当该计费请求消息为中期计费请求消息时，其中包含配额申请信息RSU51，可选地，还可以包含IqrModInd51。IqrModInd51指明计费触发设备对所述用户业务采用初始配额申请模式为非阻塞模式。
计费处理设备接收并解析所述计费请求消息后，从中获取配额申请信息RSU51和初始配额申请模式指示信息IqrModInd51(如果有出现)，其后续处理过程，如示例5A-1或5A-2所示。
示例5A-1
步骤505-1：计费处理设备授予配额GSU51。
具体地，计费处理设备基于配额申请信息RSU51，为所述用户业务授予配额GSU51。
步骤506-1：计费处理设备向计费触发设备发送计费响应消息，其中包含GSU51。
相应地，该计费响应消息可以是初始计费响应消息，也可以是中期计费响应消息。
步骤507-1：计费触发设备监控GSU51的使用(NQUSU作为配额的已使用量)。
步骤505-1-步骤507-1是授权成功的过程，所授予的配额可作为计费触发设备确定改变初始配额申请模式的依据之一，详见步骤508。
转步骤508。
示例5A-2
步骤505-2：计费处理设备为所述用户业务授权失败，确定需中断所述用户业务或挂起所述用户业务的配额管理，生成CurCmd51＝Fail或HngQm。
具体地，计费处理设备为所述用户业务授权失败，例如，基于配额申请信息RSU51，确定授予配额的条件不满足(例如余额小于配额申请信息RSU51中的配额请求量)，授予配额失败，则进一步确定需中断所述用户业务或者挂起所述用户业务的配额管理，生成取值为“Fail”或“HngQm”的本期业务控制指令CurCmd51。
例如，计费处理设备根据所述用户业务的属性信息，如业务的可中断性，生成CurCmd51：如果获知所述用户业务是可中断业务，则生成取值为“HngQm”的CurCmd51；如果获知所述用户业务是可中断业务，则生成取值为“Fail”的CurCmd51。
步骤506-2：计费处理设备向计费触发设备发送计费响应消息，其中包含CurCmd51。
相应地，该计费响应消息可以是初始计费响应消息，也可以是中期计费响应消息。
步骤507-2：计费触发设备执行CurCmd51。
具体地，如果CurCmd51取值为“Fail”，则中断所述用户业务；如果CurCmd取值为“HngQm”，则挂起所述用户业务的配额管理，例如，转为离线计费，但维持放通所述用户业务。
步骤505-2-步骤507-2是授权失败的过程，所下发的控制指令可作为计费触发设备确定改变初始配额申请模式的依据之一，详见步骤508。
步骤508：计费触发设备基于计费处理结果确定应更改所述用户业务的初始配额申请模式为阻塞模式。
具体地，计费触发设备基于示例5A-1或示例5A-2的计费处理过程，确定应更改所述用户业务的初始配额申请模式，即：从此前的非阻塞模式(NB)更改为阻塞模式(B)。
例如，计费触发设备可以根据连续多次计费处理结果中的授予配额量呈下降趋势，则确定计费处理设备收紧信用控制，进而确定应将所述用户业务的初始配额申请模式改为阻塞模式；再如，根据授权失败的原因和/或次数，确定所述用户业务的信用控制风险加大，后续应改为采用阻塞模式的初始配额申请。
确定更改初始配额申请模式之后，计费触发设备可以为所述用户业务保存新的初始配额申请模式，如步骤509-1或步骤509-2所示。
步骤509-1：计费触发设备更新所述用户业务的初始配额申请模式。
具体地，计费触发设备将所述初始配额申请模式保存到本地或外部存储设施保存的所述用户业务的配置信息中，其中，在外部存储设施保存的初始配额申请模式可以在多个计费触发设备之间共用。
步骤509-2：
步骤509-2-1：计费触发设备向策略控制设备发送策略更新请求消息，其中包含更新所述用户业务的初始配额申请模式的指示信息。
具体的，计费触发设备更新本地生效的所述用户业务的计费策略中的初始配额申请模式后，进一步向策略控制设备发送策略更新请求，所述策略更新请求中包含更新所述用户业务的初始配额申请模式的指示信息，以使策略控制设备后续基于所述初始配额申请模式生成所述用户业务的计费策略；或者，不更新本地生效的所述用户业务的计费策略中的初始配额申请模式，而是直接向策略控制设备发送策略更新请求，所述更新请求中包括更新所述用户业务的初始配额申请模式的指示信息，之后，策略控制设备在所述策略更新请求的响应消息中下发所述用户业务的新的计费策略，所述新的计费策略中包含更新后的所述用户业务的初始配额申请模式，所述指示信息可以指示禁止对所述用户业务采用非阻塞模式，或者指示对所述用户业务采用阻塞模式。
其中，向策略控制设备发送策略更新请求消息示例如下：
Figure PCTCN2021083671-appb-000010
所述策略更新请求的响应消息中重新下发该用户业务的策略消息示例如下：
Figure PCTCN2021083671-appb-000011
步骤509-2-2：策略控制设备向计费触发设备返回策略更新响应消息(OK)。
相对于图3A-图3D以及图4A-图4B，上述图5A对应的方法流程可以在其基础上进一步降低计费处理设备的性能负担。
图5B对应方法流程中，计费触发设备对用户业务采用阻塞模式(第一模式)的初始配额申请，计费处理设备据此进行计费处理并下发计费处理结果以控制计费触发设备对本期用户业务的计费操作，计费触发设备根据计费处理设备返回的计费处理结果，对所述用户业务转为采用非阻塞模式(第二模式)的初始配额申请，该方法流程主要包括如下步骤：
步骤551：计费触发设备收到用户业务的开始请求StartReq52。
该步骤的内容可以参考步骤301。
为确定开始所述用户业务和为所述用户业务申请配额的时间顺序，计费触发设备先获取所述用户业务的初始配额申请模式，如步骤552-1或者步骤552-2所示。
步骤552-1：计费触发设备获取所述用户业务的初始配额申请模式IqrMod(＝B)。
该步骤的内容可以参考步骤502-1，所不同的是所述用户业务的初始配额申请模式为阻塞模式。
转步骤553。
步骤552-2：
步骤552-2-1：计费触发设备向策略控制设备发送策略请求消息。
该步骤的内容可以参考步骤502-2-1。
步骤552-2-2：策略控制设备向计费触发设备返回策略响应消息，其中包含所述用户业务的初始配额申请模式。
该步骤的内容可以参考步骤502-2-2。
步骤553：计费触发设备向计费处理设备发送计费请求消息，其中包含配额申请信息RSU52和初始配额申请模式指示信息IqrModInd53。
所述计费请求消息可以是初始计费请求消息，也可以中期计费请求消息；具体地，为开始所述用户业务，计费触发设备向计费处理设备发送初始计费请求消息，其中包含配额申请信息RSU52和初始配额申请模式指示信息IqrModInd53；所述用户业务开始之后，为维持放通所述用户业务，计费触发设备向计费处理设备发送中期计费请求消息，其中包含配额申请信息RSU52，可选地，还可以包含IqrModInd53。IqrModInd53指明计费触发设备对所述用户业务采用的初始配额申请模式是阻塞模式。
计费处理设备接收并解析所述计费请求消息后，从中获取配额申请信息RSU52和初始配额申请模式指示信息IqrModInd53(如果有)，其后续处理过程，如示例5B-1或5B-2所示。
示例5B-1
步骤554-1：计费处理设备授予配额GSU52。
具体地，计费处理设备基于配额申请信息RSU52，为所述用户业务授予配额GSU52。
步骤555-1：计费处理设备向计费触发设备发送计费响应消息，其中包含GSU52。
步骤556-1：计费触发设备基于GSU52开始所述用户业务，或者监控GSU52的使用。
具体地，如果上述计费响应消息是初始计费响应消息，则计费触发设备基于GSU52开始所述用户，如果上述计费响应消息是中期计费响应消息，则计费触发设备监控GSU52的使用。
步骤554-1-步骤556-1是正常授予配额的过程，授予的配额可作为计费触发设备确定改变初始配额申请模式的依据之一，详见步骤557。
转步骤557。
示例5B-2
步骤554-2：计费处理设备授予配额成功，生成CurCmd＝HngQm。
和步骤554-1相比，除了授予配额GSU52之外，计费处理设备还基于计费系统的性能负担等因素，生成CurCmd52＝HngQm，以使计费触发设备挂起所述用户业务的配额管理。。
步骤555-2：计费处理设备向计费触发设备发送计费响应消息，其中包含GSU52和CurCmd52。
和步骤555-1相比，该计费响应消息还包含CurCmd52。
步骤556-2：计费触发设备执行CurCmd52。
和步骤506-2相比，计费触发设备还根据CurCmd52＝HngQm，挂起所述用户业务的配额管理。
步骤554-1-步骤556-1是正常授予配额的过程，授予的配额和所下发的计费控制指令(CurCmd52)可作为计费触发设备确定改变初始配额申请模式的依据之一，详见步骤557。
步骤557：计费触发设备基于计费处理结果确定应更改所述用户业务的初始配额申请模式为非阻塞模式。
具体地，计费触发设备基于示例5B-1或示例5B-2的计费处理过程，确定应更改所述用户业务的初始配额申请模式，即从此前的阻塞模式(B)更改为非阻塞模式(NB)。例如，计费触发设备可以根据连续多次计费处理结果中授予的配额量呈上升趋势，则确定计费处理设备放松信用控制，进而确定应将所述用户业务的初始配额申请模式改为非阻塞模式。
确定更改初始配额申请模式之后，计费触发设备可以为所述用户业务保存新的初始配额申请模式，如步骤558-1或步骤558-2所示。
步骤558-1：计费触发设备更新所述用户业务的初始配额申请模式。
该步骤的内容可参考步骤509-1。
步骤558-2：
步骤558-2-1：计费触发设备向策略控制设备发送策略更新请求消息，其中包含更新所述用户业务的初始配额申请模式的指示信息。
该步骤的内容可以参考步骤509-2-1。
步骤558-2-2：策略控制设备向计费触发设备返回策略更新响应消息(OK)。
该步骤的内容可以参考步骤509-2-2。
相对于图3A-图3D以及图4A-图4B对应的方法流程，上述图5B对应的方法流程可以在其基础上进一步降低计费处理设备的性能负担。
图6为本申请实施例提供的计费触发设备、计费处理设备或策略控制设备的硬件结构图。本申请实施例中的所有计费触发设备(例如，图1的102)、计费处理设备(例如，图1的101)、策略控制设备(例如，图1的策略控制设备104)，均可以采用图6所示的通用的计算机硬件结构实现，其中包括处理器601、存储器602、总线603、输入设备604、输出设备605以及网络接口606，其中输入设备604与输出设备605为可选的。
具体地，存储器602可以包括以易失性和/或非易失性存储器形式的计算机存储媒体，如只读存储器和/或随机存取存储器。存储器602可以存储操作系统、应用程序、其他程序模块、可执行代码和程序数据。
输入设备604可以用于输入信息，便于系统管理员对计费触发设备、计费处理设备或策略控制设备进行操作和管理等，例如，在计费处理设备上配置用户账户风险阈值、在计费触发设备上管理初始配额申请模式指示信息的存储空间、在策略控制设备上管理初始配额申请模式指示信息的存储空间等；输入设备604可以为键盘或指向设备，如鼠标、轨迹球、触摸板、麦克风、操纵杆、游戏垫、卫星电视天线、扫描仪或类似设备，均可以通过总线603连接至处理器601。
输出设备605可以用于输出信息，便于系统管理员对计费触发设备、计费处理设备或策略控制设备进行操作和管理等；例如，在计费处理设备上显示用户账户风险阈值、在计费触 发设备上显示剩余存储空间、在策略控制设备上显示剩余存储空间等；除了监视器之外，输出设备605还可以为其他外围输出设备，如扬声器和/或打印设备，也均可以通过总线603连接到处理器601。
计费触发设备、计费处理设备或策略控制设备均可以通过网络接口606连接到网络中，例如连接到局域网(Local Area Network，LAN)。在联网环境下，计费触发设备、计费处理设备或策略控制设备中存储的计算机执行指令可以存储在远程存储设备中，而不限于在本地存储。
当计费触发设备中的处理器601执行存储器602中存储的可执行代码或应用程序时，计费触发设备可以执行以上所有实施例中与计费触发设备相对应的方法步骤，如步骤230、303、307-2、331-2、346、370、410、449、507-2和556-2等；具体执行过程均参见上述实施例，在此不再赘述。
当计费处理设备中的处理器601执行存储器602中存储的可执行代码或应用程序时，计费处理设备可以执行以上所有实施例中与计费处理设备相对应的方法步骤，如步骤220、305-1、329-1、344、368、408、447、505-2和554-2；具体执行过程均参见上述实施例，在此不再赘述。
当策略控制设备中的处理器601执行存储器602中存储的可执行代码或应用程序时，策略控制可以执行以上所有实施例中与策略控制设备相对应的方法步骤，如步骤502-2、509-2、552-2和558-2；具体执行过程均参见上述实施例，在此不再赘述。
图7为本申请实施例提供的计费处理设备(101)的逻辑结构示意图，所述计费处理设备(101)用于根据计费触发设备(102)对用户业务采用的初始配额申请模式控制计费触发设备(102)对所述用户业务的计费操作，包括：
-获取模块701，用于获取用户业务的初始配额申请模式指示信息等，所述初始配额申请模式指示信息指明计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式，具体执行过程参见上述实施例中计费处理设备侧的步骤说明，如步骤201、304、324和328-1等。
-发送模块702，用于向所述计费触发设备(102)发送计费处理结果等，所述计费处理结果为基于所述初始配额申请模式指示信息对所述用户业务进行计费处理的结果，具体执行过程参见上述实施例中计费处理设备侧的步骤说明，如步骤330-1、330-2和345等。
图8为本申请实施例提供的计费触发设备(102)的逻辑结构示意图，所述计费触发设备(102)用于向计费处理设备(101)发送用户业务的初始配额申请模式指示信息，且根据计费处理设备(101)发送的计费处理结果调整对所述用户业务的计费操作，包括：
-发送模块801，用于向计费处理设备(101)发送用户业务的初始配额申请模式指示信息等，所述初始配额申请模式指示信息指明所述计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式，具体执行过程参见上述实施 例中计费触发设备侧的步骤说明，如步骤201、304、324和328-1等。
-接收模块802，用于从所述计费处理设备(101)接收所述用户业务的计费处理结果等，具体执行过程参见上述实施例中计费触发设备侧的步骤说明，如步骤330-1、330-2和345等。
-处理模块803，用于基于所述计费处理结果处理所述用户业务等，具体执行过程参见上述实施例中计费触发设备侧的步骤说明，如步骤307-1、307-2、307-3、331-1、331-2、331-3和331-4等。
图9为本申请实施例提供的策略控制设备(104)的逻辑结构示意图，所述策略控制设备(104)用于为计费触发设备(102)保存用户业务的初始配额申请模式，包括：
-收发模块901，用于从所述计费触发设备(102)接收用户业务的初始配额申请模式，或者从计费触发设备(102)接收初始配额申请模式的查询请求等，具体执行过程参见上述实施例中计费触发设备侧的步骤说明，如步骤502-2-1和509-2-1等。
-存储模块902，用于将从所述计费触发设备(102)接收用户业务的初始配额申请模式保存到本地存储设施，可选地，通过收发模块901向所述计费触发设备(102)返回成功响应，或者根据从计费触发设备(102)接收初始配额申请模式的查询请求，从本地存储设置查找出所述用户业务的初始配额申请模式，并将其通过收发模块901发送给所述计费触发设备(102)，如步骤502-2-2和509-2-2等。
图7所示计费处理设备、图8所示计费触发设备和图9所示策略控制设备是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到这些设备也可以采用图6所示的形式。例如获取模块701、发送模块702、发送模块801、接收模块802、处理模块803、收发模块901和存储模块902都可以通过图6中的处理器601和存储器602来实现。例如，获取模块701获取用户业务的初始配额申请模式指示信息的功能、发送模块801发送初始配额申请模式指示信息的功能和存储模块901存储用户业务的初始配额申请模式的功能，均可以通过由处理器601来执行存储器602中存储的代码来实现。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本领域普通技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过 其它的方式实现。例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (36)

  1. 一种计费系统，包括：计费处理设备(101)和计费触发设备(102)，其特征在于：
    所述计费触发设备(102)用于：向所述计费处理设备(101)发送初始配额申请模式指示信息，所述初始配额申请模式指示信息指明所述计费触发设备(102)在收到用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
    所述计费处理设备(101)用于：获取所述初始配额申请模式指示信息，且向所述计费触发设备(102)发送计费处理结果，所述计费处理结果为基于所述初始配额申请模式指示信息对所述用户业务进行计费处理的结果；
    所述计费触发设备(102)还用于：基于所述计费处理结果处理所述用户业务。
  2. 根据权利要求1所述的计费系统，其特征在于：
    所述计费触发设备(102)还用于：在收到所述第一开始请求时对所述用户业务采用所述第一初始配额申请模式，且向所述计费处理设备(101)发送所述用户业务的初始计费请求消息，所述初始计费请求消息包含所述初始配额申请模式指示信息；
    所述计费处理设备(101)还用于：从所述初始计费请求消息中获取所述初始配额申请模式指示信息。
  3. 根据权利要求1或2所述的计费系统，其特征在于，所述计费处理设备(101)还用于向所述所述计费触发设备(102)发送包含以下任意一项的计费处理结果：
    用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，或者
    用于指示所述计费触发设备(102)中断所述用户业务的指示参数。
  4. 根据权利要求3所述的计费系统，其特征在于，所述计费处理设备(101)还用于在所述第一初始配额申请模式为非阻塞模式，且确定需使所述计费触发设备(102)挂起所述用户业务的配额管理时，向所述计费触发设备(102)发送包含用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数的计费处理结果，所述计费触发设备(102)还用于挂起所述用户业务的配额管理。
  5. 根据权利要求1-3中任一所述的计费系统，其特征在于，所述计费处理设备(101)还用于向所述计费触发设备(102)发送包含用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数的计费处理结果，所述第二开始请求晚于所述第一开始请求发生。
  6. 一种处理用户业务的方法，应用于计费处理设备(101)，其特征在于，包括：
    获取用户业务的初始配额申请模式指示信息，所述初始配额申请模式指示信息指明计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
    向所述计费触发设备(102)发送计费处理结果，所述计费处理结果为基于所述初始配额申请模式指示信息对所述用户业务进行计费处理的结果。
  7. 根据权利要求6所述的方法，其特征在于，所述获取所述初始配额申请模式指示信息，包括：
    从所述计费触发设备(102)接收所述用户业务的初始计费请求消息，所述初始计费请 求消息包含所述初始配额申请模式指示信息；
    从所述初始计费请求消息中获取所述初始配额申请模式指示信息。
  8. 根据权利要求6或7所述的方法，其特征在于，所述计费处理结果包含以下任意一项：
    用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，或者
    用于指示所述计费触发设备(102)中断所述用户业务的指示参数。
  9. 根据权利要求8所述的方法，其特征在于，当所述第一初始配额申请模式为非阻塞模式时，所述计费处理结果包含用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理包括：
    为所述用户业务授权失败，且基于所述初始配额申请模式指示信息确定需使所述计费触发设备(102)挂起所述用户业务的配额管理。
  10. 根据权利要求8所述的方法，其特征在于，当所述第一初始配额申请模式为非阻塞模式时，所述计费处理结果包含用于指示所述计费触发设备(102)中断所述用户业务的指示参数,所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理包括：
    为所述用户业务授权失败，且基于所述初始配额申请模式指示信息确定需使所述计费处理设备(101)中断所述用户业务。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    从所述计费触发设备(102)接收所述用户业务的无配额使用量。
  12. 根据权利要求6-8中任一所述的方法，其特征在于，所述计费处理结果还包含用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数，所述第二开始请求晚于所述第一开始请求发生。
  13. 根据权利要求12所述的方法，其特征在于，所述第一初始配额申请模式为非阻塞模式，所述第二初始配额申请模式为阻塞模式；或者，所述第一初始配额申请模式为阻塞模式，所述第二初始配额申请模式为非阻塞模式。
  14. 根据权利要求6-13中任一所述的方法，其特征在于:
    所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理由所述用户业务的初始计费请求消息触发，所述向所述计费触发设备(102)发送所述计费处理结果，包括：向所述计费触发设备(102)发送所述用户业务的初始计费响应消息，所述初始计费响应消息中包含所述计费处理结果；或者
    所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理由所述用户业务的中期计费请求消息触发，所述向所述计费触发设备(102)发送所述计费处理结果，包括：向所述计费触发设备(102)发送所述用户业务的中期计费响应消息，所述中期计费响应消息包含所述计费处理结果；或者
    所述基于所述初始配额申请模式指示信息对所述用户业务进行计费处理由其他计费请求消息或者账户管理消息触发，所述其他计费请求消息为其他用户业务的计费请求消息，所述其他用户业务与所述用户业务对应相同的账户，所述账户管理消息为所述用户业务对应的账户的管理消息，所述向所述计费触发设备(102)发送所述计费处理结果，包括：向所 述计费触发设备(102)发送通知消息，所述通知消息包含所述计费处理结果。
  15. 一种处理用户业务的方法，应用于计费触发设备(102)，其特征在于，包括：
    向计费处理设备(101)发送用户业务的初始配额申请模式指示信息，所述初始配额申请模式指示信息指明所述计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
    从所述计费处理设备(101)接收所述用户业务的计费处理结果；
    基于所述计费处理结果处理所述用户业务。
  16. 根据权利要求15所述的方法，其特征在于，所述向计费处理设备(101)发送用户业务的初始配额申请模式指示信息，具体为：
    在收到所述第一开始请求时对所述用户业务采用所述第一初始配额申请模式；
    向所述计费处理设备(101)发送所述用户业务的初始计费请求消息，所述初始计费请求消息包含所述初始配额申请模式指示信息。
  17. 根据权利要求15或16所述的方法，其特征在于，所述计费处理结果包含以下任意一项：
    用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，或者
    用于指示所述计费触发设备(102)中断所述用户业务的指示参数。
  18. 根据权利要求17所述的方法，其特征在于，所述计费处理结果包含用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，所述基于所述计费处理结果处理所述用户业务，包括：
    挂起所述用户业务的配额管理。
  19. 根据权利要求17所述的方法，其特征在于，所述计费处理结果包含用于指示所述计费触发设备(102)中断所述用户业务的指示参数，所述基于所述计费处理结果处理所述用户业务，包括：
    中断所述用户业务,
    且向所述计费处理设备(101)发送所述用户业务的无配额使用量。
  20. 根据权利要求15-17中任一所述的方法，其特征在于，所述计费处理结果还包含用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数，所述第二开始请求晚于所述第一开始请求发生，所述基于所述计费处理结果处理所述用户业务，还包括：
    将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式。
  21. 根据权利要求20所述的方法，其特征在于，所述从计费处理设备(101)接收所述用户业务的计费处理结果，包括：
    从所述计费处理设备(101)接收所述用户业务的初始计费响应消息，所述初始计费响应消息包含所述计费处理结果；或者
    从所述计费处理设备(101)接收所述用户业务的中期计费响应消息，所述中期计费响应消息包含所述计费处理结果；或者
    从所述计费处理设备(101)接收通知消息，所述通知消息包含所述计费处理结果。
  22. 根据权利要求15-19中任一所述的方法，其特征在于，所述基于所述计费处理结果 处理所述用户业务，包括：
    根据所述计费处理结果，确定在收到所述用户业务的第二开始请求时应对所述用户业务采用第二初始配额申请模式，所述第二开始请求晚于所述第一开始请求发生；
    将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式。
  23. 根据权利要求20-22中任一所述的方法，其特征在于，所述将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式，包括：
    向所述策略控制设备(104)发送对所述用户业务禁止采用所述第一初始配额申请模式的指示信息；或者，
    向所述策略控制设备(104)发送指示将所述用户业务对应的初始配额申请模式更改为所述第二初始配额申请模式的指示信息。
  24. 根据权利要求20-23中任一所述的方法，其特征在于，所述第一初始配额申请模式为非阻塞模式，所述第二初始配额申请模式为阻塞模式；或者，所述第一初始配额申请模式为阻塞模式，所述第二初始配额申请模式为非阻塞模式。
  25. 一种计费处理设备(101)，其特征在于，包括获取模块(701)和发送模块(702)，其中：
    所述获取模块(701)用于：获取用户业务的初始配额申请模式指示信息，所述初始配额申请模式指示信息指明计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
    所述发送模块(702)用于：向所述计费触发设备(102)发送计费处理结果，所述计费处理结果为基于所述初始配额申请模式指示信息对所述用户业务进行计费处理的结果。
  26. 根据权利要求25所述的计费处理设备(101)，其特征在于，所述获取模块(701)还用于：
    从所述计费触发设备(102)接收所述用户业务的初始计费请求消息，所述初始计费请求消息包含所述初始配额申请模式指示信息；
    从所述初始计费请求消息中获取所述初始配额申请模式指示信息。
  27. 根据权利要求25或26所述的计费处理设备(101)，其特征在于，所述发送模块还用于：
    基于所述初始配额申请模式指示信息生成以下任意一项并将以下任意一项包含在所述计费处理结果中：
    用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数，或者
    用于指示所述计费触发设备(102)中断所述用户业务的指示参数。
  28. 根据权利要求25-27中任一所述的计费处理设备(101)，其特征在于，所述发送模块还用于：
    基于所述初始配额申请模式指示信息生成用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数，并将该指示参数包含在所述计费处理结果中，所述第二开始请求晚于所述第一开始请求发生。
  29. 一种计费触发设备(102)，其特征在于，包括发送模块(801)、接收模块(802)和处理模块(803)，其中：
    所述发送模块(801)用于：向计费处理设备(101)发送用户业务的初始配额申请模式指示信息，所述初始配额申请模式指示信息指明所述计费触发设备(102)在收到所述用户业务的第一开始请求时对所述用户业务采用了第一初始配额申请模式；
    所述接收模块(802)用于：从所述计费处理设备(101)接收所述用户业务的计费处理结果；
    所述处理模块(803)用于：基于所述计费处理结果处理所述用户业务。
  30. 根据权利要求29所述的计费触发设备(102)，其特征在于，所述发送模块还用于：
    在收到所述第一开始请求时对所述用户业务采用所述第一初始配额申请模式；
    向所述计费处理设备(101)发送所述用户业务的初始计费请求消息，所述初始计费请求消息包含所述初始配额申请模式指示信息。
  31. 根据权利要求29或30所述的计费触发设备(102)，其特征在于：
    所述接收模块(802)还用于从所述计费处理设备(101)接收包含用于指示所述计费触发设备(102)挂起所述用户业务的配额管理的指示参数的计费处理结果，所述处理模块(803)还用于挂起所述用户业务的配额管理；或者
    所述接收模块(802)还用于从所述计费处理设备(101)接收包含用于指示所述计费触发设备(102)中断所述用户业务的指示参数的计费处理结果，所述处理模块(803)还用于中断所述用户业务。
  32. 根据权利要求29-31中任一项所述的计费触发设备(102)，其特征在于：
    所述接收模块(802)还用于从所述计费处理设备(101)接收包含用于指示计费触发设备在收到所述用户业务的第二开始请求时对所述用户业务采用第二初始配额申请模式的指示参数的计费处理结果，所述第二开始请求晚于所述第一开始请求发生，所述处理模块(803)还用于将所述用户业务的初始配额申请模式更新为所述第二初始配额申请模式。
  33. 一种计费处理设备(101)，其特征在于，包括处理器和存储器，其中：
    所述存储器，用于存储程序指令；
    所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费处理设备(101)执行权利要求6至14中任一项所述的处理用户业务的方法。
  34. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得所述计算机执行权利要求6至14中任一项所述的处理用户业务的方法。
  35. 一种计费触发设备(102)，其特征在于，包括处理器和存储器，其中：
    所述存储器，用于存储程序指令；
    所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费触发设备(102)执行权利要求15至24中任意一项所述的处理用户业务的方法。
  36. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得所述计算机执行权利要求15至24中任意一项项所述的处理用户业务的方法。
PCT/CN2021/083671 2020-04-01 2021-03-29 处理用户业务的方法、系统及相关设备 WO2021197278A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21781325.2A EP4120705A4 (en) 2020-04-01 2021-03-29 METHOD AND SYSTEM FOR PROCESSING A USER SERVICE AND ASSOCIATED DEVICE
US17/959,045 US20230045030A1 (en) 2020-04-01 2022-10-03 User service processing method, system, and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010251898.5 2020-04-01
CN202010251898.5A CN113498033A (zh) 2020-04-01 2020-04-01 处理用户业务的方法、系统及相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/959,045 Continuation US20230045030A1 (en) 2020-04-01 2022-10-03 User service processing method, system, and related device

Publications (1)

Publication Number Publication Date
WO2021197278A1 true WO2021197278A1 (zh) 2021-10-07

Family

ID=77927431

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/083671 WO2021197278A1 (zh) 2020-04-01 2021-03-29 处理用户业务的方法、系统及相关设备

Country Status (4)

Country Link
US (1) US20230045030A1 (zh)
EP (1) EP4120705A4 (zh)
CN (1) CN113498033A (zh)
WO (1) WO2021197278A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101136755A (zh) * 2006-08-31 2008-03-05 中兴通讯股份有限公司 一种区分预付费终端不同方向流的预付费方法
CN102957543A (zh) * 2011-08-22 2013-03-06 中国电信股份有限公司 针对时长用户的基于流的计费方法及系统
US20130176908A1 (en) * 2012-01-05 2013-07-11 Tekelec, Inc. Methods, systems, and computer readable media for utilizing quota usage policy control in a diameter-based communication network
US9531554B1 (en) * 2014-01-31 2016-12-27 Sprint Communications Company L.P. Default quota implementation for wireless devices
CN106550162A (zh) * 2012-08-08 2017-03-29 华为技术有限公司 计费控制的方法及计费触发装置、在线计费系统
CN107667550A (zh) * 2015-06-04 2018-02-06 Lg电子株式会社 无线通信系统中通过轮询信道来处理请求的方法及其设备
WO2019182572A1 (en) * 2018-03-20 2019-09-26 Nokia Solutions And Networks Oy Quota management in a session management function (smf) for online charging

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374056A (zh) * 2007-08-23 2009-02-25 华为技术有限公司 一种计费帐务数据能力开放的方法和系统
CN108259196B (zh) * 2016-12-28 2023-06-06 华为技术有限公司 一种配额管理方法及装置
CN112738744A (zh) * 2017-02-07 2021-04-30 华为技术有限公司 一种计费方法、装置和系统

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101136755A (zh) * 2006-08-31 2008-03-05 中兴通讯股份有限公司 一种区分预付费终端不同方向流的预付费方法
CN102957543A (zh) * 2011-08-22 2013-03-06 中国电信股份有限公司 针对时长用户的基于流的计费方法及系统
US20130176908A1 (en) * 2012-01-05 2013-07-11 Tekelec, Inc. Methods, systems, and computer readable media for utilizing quota usage policy control in a diameter-based communication network
CN106550162A (zh) * 2012-08-08 2017-03-29 华为技术有限公司 计费控制的方法及计费触发装置、在线计费系统
US9531554B1 (en) * 2014-01-31 2016-12-27 Sprint Communications Company L.P. Default quota implementation for wireless devices
CN107667550A (zh) * 2015-06-04 2018-02-06 Lg电子株式会社 无线通信系统中通过轮询信道来处理请求的方法及其设备
WO2019182572A1 (en) * 2018-03-20 2019-09-26 Nokia Solutions And Networks Oy Quota management in a session management function (smf) for online charging

Also Published As

Publication number Publication date
US20230045030A1 (en) 2023-02-09
EP4120705A1 (en) 2023-01-18
CN113498033A (zh) 2021-10-12
EP4120705A4 (en) 2023-08-23

Similar Documents

Publication Publication Date Title
Nahrstedt et al. Resource management in networked multimedia systems
US11032205B2 (en) Flow control method and switching device
US7548743B2 (en) Call control with converged application server logic and gateway logic in IMS networks
EP2466824B1 (en) Service scheduling method and device
CN110505155B (zh) 请求降级处理方法、装置、电子设备及存储介质
EP1892882A1 (en) Method of providing QoS for a flow
EP2395700B1 (en) Managing access to stream hosted on duplicating switches
Ramakrishnan et al. Operating system support for a video-on-demand file service
US10263906B2 (en) Flow scheduling device and method
US10078607B2 (en) Buffer management method and apparatus for universal serial bus communication in wireless environment
US8677046B2 (en) Deadlock resolution in end-to-end credit protocol
JP6114835B2 (ja) セッション復旧方法、デバイス及びシステム
WO2021197278A1 (zh) 处理用户业务的方法、系统及相关设备
CN107786371B (zh) 一种数据的加速方法、装置及存储介质
US7852865B2 (en) System and method for preferred service flow of high priority messages
US8869171B2 (en) Low-latency communications
WO2021012933A1 (zh) 一种计费处理的方法、系统及相关设备
WO2021027757A1 (zh) 保障数据业务的计费处理方法、系统及相关设备
CN110740472A (zh) 一种下行数据传输的控制方法和系统
Chou et al. System support for dynamic QOS control of continuous media communication
WO2020166617A1 (ja) リソース競合調停装置、リソース競合調停方法、及びプログラム
US20230362856A1 (en) Data transmission method, data transmission apparatus, computer-readable medium, and electronic device
CN110380987A (zh) 一种处理调用服务的请求的方法及装置
US20230109543A1 (en) User service processing method, system, and related device
CN110865895B (zh) 访问流量控制方法、装置、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21781325

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021781325

Country of ref document: EP

Effective date: 20221010

NENP Non-entry into the national phase

Ref country code: DE