WO2018120959A1 - 一种配额管理方法及装置 - Google Patents

一种配额管理方法及装置 Download PDF

Info

Publication number
WO2018120959A1
WO2018120959A1 PCT/CN2017/104544 CN2017104544W WO2018120959A1 WO 2018120959 A1 WO2018120959 A1 WO 2018120959A1 CN 2017104544 W CN2017104544 W CN 2017104544W WO 2018120959 A1 WO2018120959 A1 WO 2018120959A1
Authority
WO
WIPO (PCT)
Prior art keywords
quota
client
remaining
information
server
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/104544
Other languages
English (en)
French (fr)
Inventor
柴晓前
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP17888079.5A priority Critical patent/EP3554004A4/en
Priority to EP24206336.0A priority patent/EP4529095A3/en
Publication of WO2018120959A1 publication Critical patent/WO2018120959A1/zh
Priority to US16/453,733 priority patent/US11330114B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/5064—Customer relationship management
    • 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5044—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering hardware capabilities
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • 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 specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • 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/60—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on actual use of network resources
    • 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/82—Criteria or parameters used for performing billing operations
    • H04M15/8235—Access based
    • 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
    • H04M15/887—Provision for limiting connection, or expenditure limit per user or user related number
    • 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

Definitions

  • the present application relates to the field of communications, and in particular, to a quota management method and apparatus.
  • the credit-control client applies for quotas and uses it to the credit-control server.
  • the voice control client reports the quota usage information to the signal control server, and requests the information control server to issue a new quota.
  • the credit control server reclaims the remaining quota on the trusted client and re-issues the new quota.
  • the credit control client releases the service, it will cause the operator to lose; if the credit control client tentatively determines the service, it will cause service delay and reduce the user experience.
  • the embodiments of the present application provide a quota management method and apparatus, which can reduce service delays and ensure that the quota used by the service does not exceed the authorized quota.
  • the first aspect provides a quota management method, that is, the client sends a charging request to the server, where the information of the request quota and the information of the quota usage amount are carried; the client receives the quota of the authorization from the server and the indication information, according to The indication information is processed for the authorized quota and the remaining quota of the client.
  • the remaining quota is the difference between the last authorized quota of the server and the quota used amount in the charging request.
  • the client uses the processed quota and reports the used usage information of the processed quota when the reporting condition is met.
  • the client processes the authorized quota according to the indication information and the remaining quota of the client, and reports the processed quota when the reporting condition is met.
  • the usage information includes: the quota of the client merge authorization and the remaining quota, and reports the used usage information of the merged quota when the client reports the billing information.
  • the indication information includes a quota conversion coefficient
  • the quota of the client merge authorization and the remaining quota of the client include: the client The terminal converts the available remaining quota when the client receives the indication information, and combines the authorized quota and the converted remaining quota according to the quota conversion factor.
  • the client reports the charging information, it also reports the remaining information when the indication information is received. Used amount information for quotas.
  • the client allocates the quota according to the indication information and the remaining of the client The quota is processed.
  • the reporting condition is met, the used amount of the processed quota is reported.
  • the client uses the authorized quota after the remaining quota is used according to the indication information.
  • the client reports the accounting information, the client separately reports the information. Used amount information for the remaining quota, and used amount information for the authorized quota.
  • the client allocates the quota according to the indication information and the remaining of the client Match
  • the used amount information of the processed quota is reported: when the client receives the indication information, the client stops using the remaining quota, and starts to use the authorized quota, and the client separately reports the charging information.
  • the used amount information of the remaining quota is reported, and the used amount information of the authorized quota is reported.
  • the server When the client requests a new quota from the server, the server sends the authorized quota and the indication information to the client, so that the client can merge or switch the authorized quota and the remaining quota, and then report the merged result according to the processing result.
  • the client further sends information that carries the used amount of the quota to the server, However, the charging request does not carry the information requesting the quota; the client clears the remaining quota, suspends the service data flow, and the remaining quota that is cleared is carried in the charging request of the authorization quota and the information that does not carry the request quota. The difference in the amount of quota used.
  • the client further sends a charging request that carries the quota recovery indication to the server.
  • the client clears the remaining quota and suspends the service data flow.
  • the remaining quota that is cleared is the difference between the quota usage amount and the quota usage carried in the accounting request of the information that does not carry the request quota.
  • a seventh possible implementation manner when the client receives the authorization failure indication information from the server, Based on the authorization failure indication information, the client reports the used usage information of the remaining quota after using the remaining quota.
  • an eighth possible implementation manner when the client receives the authorization failure indication information from the server, The client stops using the remaining quota and reports the used amount information of the remaining quota.
  • a ninth possible implementation manner before the client sends a charging request to the server, or After the client reports the used usage information of the processed quota, the client sends the information carrying the used amount to the server, but does not carry the charging request for the information requesting the quota, so that the server deducts the carried amount from the authorized quota.
  • the amount used, the remaining part after deduction is used as the remaining quota; the client continues to use the remaining quota after deduction.
  • the server authorizes more quotas. If the triggering event occurs, reclaiming the remaining quota and re-granting the quota will increase the network burden. In this way, the server does not have to re-grant the quota when a part of the triggering event occurs, which reduces the network burden.
  • the second aspect provides a quota management method, including: receiving, by a server, a charging request from a client, where the information of the request quota and the quota usage information are carried; the server sends the authorized quota and the indication information to the client, where The indication information is used to instruct the client to process the quota of the authorization and the remaining quota of the client.
  • the remaining quota is the difference between the quota used by the server and the quota used in the billing request.
  • the indication information is used to indicate that the client processes the quota of the authorization and the remaining quota of the client, including: the indication information is used for Indicates the quota for client consolidation authorization and the remaining quota for the client.
  • the indication information includes a quota conversion coefficient
  • the quota indicating the client merge authorization and the remaining quota of the client include: Instructs the client to convert the available remaining quota when the client receives the indication information according to the quota conversion factor, merge the authorized quota, and convert the available remaining quota.
  • the indication information is used to indicate a quota of the client for the authorization and the client The remaining quotas are processed, including: the indication information is used to indicate that the client uses the authorized quota after using the remaining quota.
  • the indication information is used to indicate a quota of the client for the authorization and the client
  • the remaining quotas are processed, including: the indication information is used to instruct the client to stop using the remaining quotas and start using the authorized quotas when receiving the indication information.
  • the server When the client requests a new quota from the server, the server sends the authorized quota and the indication information to the client, so that the client can merge or switch the authorized quota and the remaining quota, and then report the merged result according to the processing result.
  • the server receives the information that carries the used amount of the quota, but does not When the charging request for the information requesting the quota is carried, the server returns the remaining quota to the user account, and the remaining quota returned is the difference between the quota usage amount and the quota usage amount carried in the charging request of the information that does not carry the request quota.
  • the server receives the charging request that carries the quota recovery indication from the client
  • the server returns the remaining quota to the user account, and the remaining quota returned is the difference between the authorized quota and the quota used amount carried in the charging request of the information that does not carry the request quota.
  • a seventh possible implementation manner when the server authorization quota fails, the server sends an authorization failure indication to the client The information, the authorization failure indication information is used to indicate that the client reports the used amount information of the remaining quota after using the remaining quota.
  • the server when the server authorization quota fails, the server sends an authorization failure to the client.
  • the indication information, the authorization failure indication information is used to instruct the client to stop using the remaining quotas and report the used amount information of the remaining quotas when receiving the authorization failure indication information.
  • a ninth possible implementation manner before the server receives the charging request from the client, or After the server sends the authorized quota and the indication information to the client, when the server receives the information carrying the used amount from the client but does not carry the charging request for the information requesting the quota, the server obtains the quota from the authorization. The deducted used amount is deducted, and the remaining part after the deduction is used as the remaining quota, and the used amount is deducted from the user account according to the information of the used usage amount.
  • the third aspect provides a quota management method, that is, the client sends a charging request to the server, where the information of the request quota and the quota usage information are carried; the client receives the quota of the authorization from the server; the client is in use Authorized quotas are used after the remaining quotas have been completed.
  • the remaining quota is the difference between the quota used by the server and the quota used in the accounting request.
  • the client separately reports the used usage information of the remaining quotas and the used usage information of the authorized quotas.
  • the fourth aspect provides a quota management method, that is, the client sends a charging request to the server, where the information of the request quota and the quota usage information are carried; the client receives the quota of authorization from the server; the client stops using The remaining quota starts to use the authorized quota, where the remaining quota is the difference between the last authorized quota of the server and the quota used in the charging request.
  • the client separately reports the used usage information of the remaining quotas and the used usage information of the authorized quotas.
  • the client sends the information that carries the quota usage amount to the server, but does not carry the charging request for the information requesting the quota; the client clears the remaining The quota is used to suspend the traffic of the service data, wherein the remaining quota that is cleared is the difference between the authorized amount and the used amount carried in the charging request that does not carry the information of the request quota.
  • the client when the client receives the authorization failure indication information from the server, the client reports the remaining failure quota after the remaining quota is used according to the authorization failure indication information. Used amount information for the remaining quota.
  • the client when the client receives the authorization failure indication information from the server, the client stops using the remaining quota and reports the used usage information of the remaining quota. .
  • a client including a sending module, a receiving module, and a processing module.
  • the sending module is configured to send a charging request to the server, where the information of the request quota and the quota usage information are carried;
  • the receiving module is configured to receive the quota and the indication information of the authorization from the server;
  • the processing module is configured to:
  • the indication information is used to process the quota of the authorization and the remaining quota of the client, where the remaining quota is the difference between the quota used by the server and the quota used in the charging request; the processing module is also used to process the processed
  • the quota module is also used to report the used amount information of the processed quota when the reporting condition is met.
  • the processing module is configured to process the quota of the authorization and the quota remaining by the client according to the indication information, where the sending module is configured to: when the reporting condition is met
  • the used usage information of the processed quota is as follows: the processing module is used to merge the authorized quota and the remaining quota, and the sending module is configured to report the used usage information of the combined quota when the client reports the charging information.
  • the indication information includes a quota conversion coefficient
  • the processing module is configured to merge the authorized quota and the remaining quota of the client includes The processing module is configured to convert the available remaining quota when the receiving module receives the indication information according to the quota conversion coefficient, and combine the authorized quota and the converted remaining quota; when the sending module reports the charging information, the sending module also reports the receiving the indication.
  • the processing module is configured to process, according to the indication information, the authorized quota and the remaining quota of the client, and the sending module is configured to report the used usage information of the processed quota when the reporting condition is met, including: processing The module is configured to use the authorized quota after the remaining quotas are used according to the indication information, and the sending module is configured to separately report the used amount information of the remaining quotas and the used amount of the authorized quotas when reporting the charging information. information.
  • the processing module is configured to use the quota for the authorization according to the indication information, and the client The remaining quota is processed, and the sending module is configured to report the used amount information of the processed quota when the reporting condition is met, where the processing module is configured to stop using the remaining quota when receiving the indication information, start using the authorized quota, and send the module.
  • the reporting condition is met
  • the processing module is configured to stop using the remaining quota when receiving the indication information, start using the authorized quota, and send the module.
  • the reported usage information of the remaining quotas and the used usage information of the authorized quotas are separately reported.
  • the sending module is further configured to send, to the server, a quota usage amount.
  • Information but does not carry the charging request for the information requesting the quota; the processing module is also used to clear the remaining quotas and suspend the passage of the service data flow, wherein the remaining quotas that are cleared are the information of the authorized quota and the non-carrying request quota The difference between the quota usage amount carried in the billing request.
  • the sending module is further configured to send, to the server, a meter that carries the quota recovery indication
  • the request is also used to clear the remaining quotas and suspend the service data flow, wherein the remaining quotas that are cleared are the quota usage carried in the charging request of the authorization quota and the information that does not carry the request quota. The difference.
  • a seventh possible implementation manner when the receiving module receives the authorization failure indication information from the server, the processing The module reports the used amount information of the remaining quotas after the remaining quotas are used according to the authorization failure indication information.
  • the processing The module stops using the remaining quota and reports the used amount information of the remaining quota.
  • the sending module before the sending module sends the charging request to the server, or After the module reports the used usage information of the processed quota, the sending module is further configured to send the information carrying the used amount to the server, but does not carry the charging request for the information requesting the quota, so that the server deducts the carried from the authorized quota.
  • the used amount the remaining part after the deduction as the remaining quota; the processing module continues to use the remaining quota after the deduction.
  • a server includes a receiving module and a sending module: a receiving module, configured to receive a charging request from a client, where the charging request carries the information of the request quota and the quota used information; The quota for indicating the authorization and the indication information are sent to the client, where the indication information is used to instruct the client to process the quota of the authorization and the remaining quota of the client, wherein the remaining quota is the quota and the quota of the last authorization of the server. The difference in the amount of quota used in the fee request.
  • the client is instructed to process the quota of the authorization and the remaining quota of the client, including: the indication information is used to indicate the quota of the client merge authorization and the remaining quota of the client.
  • the indication information includes a quota conversion coefficient
  • the quota indicating the client merge authorization and the remaining quota of the client include: Instructs the client to convert the available remaining quota when the client receives the indication information according to the quota conversion factor, merge the authorized quota, and convert the available remaining quota.
  • the indication information is used to indicate a client quota for the authorization and the client The remaining quotas are processed, including: the indication information is used to indicate that the client uses the authorized quota after using the remaining quota.
  • the indication information is used to indicate a quota of the client for the authorization and the client
  • the remaining quotas are processed, including: the indication information is used to instruct the client to stop using the remaining quotas and start using the authorized quotas when receiving the indication information.
  • the receiving module receives the information that carries the used amount of the quota, but When the charging request does not carry the information requesting the quota, the sending module returns the remaining quota to the user account, where the remaining quota returned is the quota carried in the charging request of the authorized quota and the information that does not carry the request quota. The difference in quantity.
  • the receiving module receives the counter carrying the quota recovery indication from the client
  • the sending module returns the remaining quota to the user account, wherein the remaining quota returned is the difference between the authorized quota and the quota used amount carried in the charging request of the information that does not carry the request quota.
  • the sending module when the authorization quota fails, is configured to send to the client Authorization failure indication information, the authorization failure indication information is used to indicate that the client reports the used amount information of the remaining quota after using the remaining quota.
  • the sending module when the authorization quota fails, is configured to send to the client
  • the authorization failure indication information is used to indicate that the client stops using the remaining quota and reports the used amount information of the remaining quota when receiving the authorization failure indication information.
  • the server further includes a processing module, where the receiving module receives the meter from the client Before the fee request, or after the sending module sends the authorized quota and the indication information to the client, when the receiving module receives the charging request from the client carrying the used amount but does not carry the information requesting the quota, the processing is processed.
  • the module is configured to deduct the used usage amount from the authorized quota, and the remaining part after the deduction is used as the remaining quota, and deduct the used amount in the user account according to the information of the used usage amount.
  • the seventh aspect provides a client, including a sending module, a receiving module, and a processing module: a sending module, configured to send a charging request to the server, where the charging request carries the information of the request quota and the information of the quota used amount.
  • a receiving module for receiving an authorized quota from the server;
  • a processing module for enabling After the remaining quotas are used, the authorized quotas are used.
  • the remaining quotas are the difference between the quotas used by the server and the quotas used in the accounting requests.
  • the sending module is also used to separately report the remaining quotas. Usage information, as well as usage information for authorized quotas.
  • the eighth aspect provides a client, including a sending module, a receiving module, and a processing module: a sending module, configured to send a charging request to the server, where the charging request carries the information of the request quota and the quota used information.
  • a receiving module configured to receive an authorized quota from the server;
  • a processing module configured to stop using the remaining quota, and start using the authorized quota, wherein the remaining quota is a quota in the last authorized quota and charging request of the server
  • the difference between the used amount; the sending module is also used to separately report the used amount information of the remaining quotas and the used amount information of the authorized quotas.
  • the sending module is further configured to send, to the server, information that carries the used amount of the quota, but does not carry the charging request for the information requesting the quota; the processing module further It is used to clear the remaining quotas and suspend the service data flow.
  • the remaining quotas that are cleared are the difference between the quota usage amount and the quota usage carried in the accounting request of the information that does not carry the request quota.
  • the processing module when the receiving module receives the authorization failure indication information from the server, the processing module is configured to use the remaining quota according to the authorization failure indication information.
  • the used amount information of the remaining quotas is reported later.
  • the processing module when the receiving module receives the authorization failure indication information from the server, the processing module is configured to stop using the remaining quota, and report the used remaining quota. Quantity information.
  • a ninth aspect a computing device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computing device to execute an instruction, and the processor is connected to the memory through the bus The processor executes the computer-executed instructions stored by the memory to cause the computing device to perform any of the first to fourth aspects and any of the possible implementations of the first to fourth aspects The method described in the manner.
  • Yet another aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • the server when the client requests a new quota from the server, the server sends the authorized quota and the indication information to the client, so that the client can merge or switch the authorized quota and the remaining quota.
  • the processing information is reported, and the usage information of the combined quotas is reported according to the processing result, or the authorized quota and the remaining quota usage information are respectively reported. It makes the application and grant of quotas more reasonable, effectively reducing the frequent quota granting process and reducing the network burden. Reduced business delays while ensuring that the quota used by the business does not exceed the authorized quota.
  • FIG. 1 is a schematic diagram of a network architecture applied in an embodiment of the present application.
  • FIG. 2 is a schematic diagram showing the hardware structure of a computer device 200 according to an embodiment of the present application
  • FIG. 3 is an exemplary flowchart of a quota management method 300 according to an embodiment of the present application
  • FIG. 4 is an exemplary flowchart of a quota management method 400 in accordance with an embodiment of the present application
  • FIG. 5 is an exemplary flowchart of a quota management method 500 according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a client 600 according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a server 700 according to an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a network architecture applied in an embodiment of the present application.
  • the client 101 is a network device that communicates using the Diameter protocol, and may be referred to as a signaling client, for example, may be a gateway.
  • the server 102 is a network device that communicates using the Diameter protocol, and may be referred to as a signaling server. For example, it may be an Online Charging System (OCS).
  • OCS Online Charging System
  • the client 101 requests the server 102 for a quota for business use.
  • the server 102 authorizes the quota to the client 101, and performs charging according to the quota usage amount reported by the client 101.
  • the quota refers to the number of quota types that the server 102 authorizes to the client 101 for service use.
  • the quota type is traffic
  • the quota is the number of traffic granted (for example, 5M traffic); if the quota type is duration, the quota is the duration of the grant (for example, 30 minutes).
  • the credit control server recovers the remaining quota on the credit control client and re-authorizes the quota, thereby causing service delay, etc. problem.
  • the client 101 when the client 101 reports the quota usage amount to the server 102 and requests to grant a new quota, the quota remaining on the client 101 can be valid, and the remaining quota is not recovered due to the report, thereby solving the service delay and frequently granting. Quotas and other issues.
  • FIG. 2 is a schematic diagram showing the hardware structure of a computer device 200 according to an embodiment of the present application.
  • computer device 200 includes a processor 202, a memory 204, a communication interface 206, and a bus 208.
  • the processor 202, the memory 204, and the communication interface 206 implement a communication connection with each other through the bus 208.
  • the processor 202 can be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the memory 204 can be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).
  • the memory 204 can store an operating system 2041 and other applications 2042.
  • the program code for implementing the technical solution provided by the embodiment of the present application is saved in the memory 204 and executed by the processor 202.
  • Communication interface 206 enables communication with other devices or communication networks using transceivers such as, but not limited to, transceivers.
  • Bus 208 can include a path for communicating information between various components (e.g., processor 202, memory 204, communication interface 206).
  • the processor 202 is configured to execute the program code stored in the memory 204 for implementing the technical solution provided by the embodiment of the present application to implement the method shown in the embodiments of FIG. 3 to FIG. 5.
  • the processor 202 is configured to execute the memory 204.
  • the program code for implementing the technical solution provided by the embodiment of the present application is implemented to implement the method shown in the embodiment of FIG. 3 to FIG. 5.
  • the quota management method provided by the present application will be described below in conjunction with several embodiments.
  • the processing of the quota, the reporting, the return, and the like are directed to the quotas of the same rate group or the service identifier. It can be understood that the processing methods of the quotas of other rate groups or service identifiers are the same.
  • FIG. 3 is an exemplary flowchart of a quota management method 300 in accordance with an embodiment of the present application.
  • the quota management method 300 can be performed by the client 101 and the server 102 shown in FIG.
  • a service flow flows on the client, and the client applies for a quota to the server for use by the service, and reports the quota used by the service to the server.
  • the client sends a charging request to the server, where the information of the request quota and the quota used amount information are carried.
  • the client may send the foregoing charging request to the server when a trigger event defined by RFC4006 occurs or a trigger event defined by 3GPP TS32.251 occurs.
  • the trigger events defined by 3GPP TS32.251 include, for example, the client available quota is lower than the threshold, the access network type switching, and the like.
  • the server receives a charging request from the client, where the information of the request quota and the information of the quota usage amount are carried.
  • the server determines that the client still needs to use the quota. Therefore, the server keeps the remaining quota of the client effective, and does not collect the remaining quota of the client. The client can continue to use the remaining quota. The server can keep the remaining quota of the client valid by the server not returning the remaining quota to the user account.
  • the server sends an authorized quota and indication information to the client, where the indication information is used to instruct the client to merge the authorized quota and the remaining quota.
  • the server determines whether the authorized quota and the remaining quota of the client can be merged. In this embodiment, the server determines that the authorized quota is merged with the remaining quota of the client, so the indication information instructs the client to merge the authorized quota and the remaining quota.
  • the remaining quota and the authorized quota type are the same and the unit value is the same, the remaining quota and the authorized quota may be combined. For example, the remaining quota is traffic, the unit value is 1 yuan/1Mbit, the authorized quota is also traffic, and the unit value is also 1 yuan/Mbit.
  • the remaining quota and the authorized quota are of the same type, and the unit value is also the same, so the remaining quota and authorization The quotas can be combined.
  • the remaining quota and the authorized quota type are different or the unit value is different, but the remaining quota and the authorized quota can be converted, the converted remaining quota and the authorized quota may also be combined. This situation will be described in detail below.
  • the server merges the authorized quota with the remaining quota of the client, and saves the combined quota, so that the subsequent quota is deducted from the merged quota.
  • the server can determine whether the authorized quota and the remaining quota of the client can be merged according to the reporting reason sent by the client or the configuration information on the server.
  • the indication information that the client is required to combine the remaining quota and the authorization quota is represented by two ways, one is to express the indication parameter, and the other is to not send the indication parameter.
  • the value of the indication parameter indicates that the client will allocate the remaining quota and authorization. The amount is merged.
  • the indication parameter may have a value of 1, 2, or 3. When the value is 2, the remaining quota and the authorization quota are combined. A value of 1 indicates that the quota is used after the remaining quota is used. A value of 3 indicates that the remaining quota is used when the indication is received, and the license quota is used.
  • the client In the second mode, if the client does not receive the indication parameter, it determines that the remaining quota and the authorization quota should be merged; if the client receives the indication parameter, it determines that the remaining quota and the authorization quota are not merged, but according to the indication parameter
  • the instructions are processed. For example, if the client receives the indication parameter and its value is 1, the client uses the authorization quota after using the remaining quota.
  • the authorization quota and indication information sent by the server to the client can be carried by a Credit Control Answer (CCA).
  • CCA Credit Control Answer
  • the type of the authorized quota is the traffic, and the type of the remaining quota is also the traffic.
  • the information carried by the CCA includes the following fields.
  • the Multiple-Services-Credit-Control is a multi-service MAC field, and includes a Granted-Service-Unit field and a Rating-Group field.
  • the Granted-Service-Unit field is information about the authorization quota.
  • the CC-Total-Octets field is the total amount of authorized traffic.
  • the Unit-Usage-Indicator field is the indication information, which is used to indicate the traffic of the client merge authorization and the client surplus. Traffic. Rating-Group is the rate group field.
  • the client receives the quota of the authorization from the server and the indication information.
  • the quota available to the client is the current remaining quota and the quota authorized by the server.
  • the client merges the quota of the authorization and the remaining quota of the client.
  • the client when the client sends the request quota information, the remaining quota is 5 Mbit traffic, the unit value is 1 yuan/Mbit, the authorized quota is 10 Mbit traffic, and the unit value is also 1 yuan/Mbit.
  • the client merges the remaining 5 Mbit quota and the authorized 10 Mbit quota, and the combined quota is 15 Mbit.
  • the remaining quota and the authorized quota can also be combined.
  • the indication includes a quota conversion factor.
  • the client first converts the available remaining quota when the client receives the indication according to the quota conversion factor, and then combines the authorized quota with the converted remaining quota.
  • the quota conversion factor is determined by the server. The case where the quota conversion factor can be used for conversion includes: the quota unit value is different, but the quota unit value can be converted; or the quota type is different, but the quota type can be converted.
  • the remaining quota is 5 Mbit traffic
  • the unit value is 1 yuan/Mbit
  • the authorized quota is 10 Mbit traffic
  • the unit value is 2 yuan/Mbit
  • the quota conversion factor is 2.
  • the unit value of the remaining quota and the authorized quota are different, but the value of the quota unit can be converted.
  • the client receives the indication, it has already used 2Mbit of the remaining 5Mbit quota. Therefore, the available remaining quota of the client is 3Mbit.
  • the client calculates according to the quota conversion factor and gets the change.
  • the client merges and converts the available remaining quota of 1.5 Mbit and the authorized 10 Mbit quota the combined quota is 11.5 Mbit.
  • the client reports the used usage information of the combined quota.
  • the client uses the combined quota.
  • the reporting condition is met, the client reports the used amount information of the merged quota to the server.
  • the client does not distinguish between the original remaining quota and the usage quota of the authorized quota delivered by the server.
  • the escalation condition satisfies the occurrence of a trigger event as defined by RFC4006 or a trigger event as defined by 3GPP TS 32.251.
  • the client reports the used amount information of the remaining quota, and reports the used amount information of the remaining quota, and the used amount of the remaining quota is the usage information of the unconverted portion of the remaining quota. .
  • the client can carry the used amount information of the merged quota through a credit control request (CCR).
  • CCR credit control request
  • the server when the client requests a new quota from the server, the server sends the authorized quota and the indication information to the client, so that the client can merge the authorized quota and the remaining quota, and then report the quota.
  • Information about the use of the combined quota It makes the application and grant of quotas more reasonable, effectively reducing the frequent quota granting process and reducing the network burden. Reduced business delays while ensuring that the quota used by the business does not exceed the authorized quota.
  • FIG. 4 is an exemplary flow chart of a quota management method 400 in accordance with an embodiment of the present application.
  • the quota management method 400 can be performed by the client 101 and the server 102 shown in FIG.
  • a service flow flows on the client, and the client applies for a quota to the server for use by the service, and reports the quota used by the service to the server.
  • the client sends a charging request to the server, where the information of the request quota and the quota used amount information are carried.
  • the server receives a charging request from the client, where the information of the request quota and the quota used amount information are carried.
  • S401 and S402 can be referred to the embodiment S301 and S302 of FIG. 3, and details are not described herein again.
  • the server sends the authorized quota and the indication information to the client, where the indication information is used to indicate that the client uses the authorized quota after using the remaining quota.
  • the server determines whether the authorized quota and the remaining quota of the client can be merged. In this embodiment, the server determines that the authorized quota is not merged with the remaining quota of the client, and the indication information indicates that the client uses the authorized quota after using the remaining quota. Wherein, when the remaining quota and the authorized quota type are different and cannot be converted, the remaining quota and the authorized quota cannot be combined.
  • the server saves the authorized quota and the remaining quota of the client separately, so that the subsequent quota is deducted from the authorized quota and the remaining quota respectively.
  • the server can determine whether the authorized quota and the remaining quota of the client can be merged according to the reporting reason sent by the client or the configuration information on the server.
  • the authorization quota and indication information sent by the server to the client can be carried by the CCA.
  • the type of the authorized quota is the traffic
  • the type of the remaining quota is the duration
  • the authorized traffic and the remaining duration are not convertible.
  • the information carried by the CCA includes the following fields.
  • the Multiple-Services-Credit-Control is a multi-service MAC field, and includes a Granted-Service-Unit field and a Rating-Group field.
  • the Granted-Service-Unit field is information about the authorization quota.
  • the CC-Total-Octets field is the total amount of authorized traffic.
  • the Unit-Usage-Indicator field is the indication information, which is used to indicate that the client uses the remaining time. Use authorized traffic.
  • the client receives the quota of the authorization from the server and the indication information.
  • the quota available to the client is the current remaining quota and the quota authorized by the server.
  • the client uses the authorized quota after using the remaining quota.
  • the remaining quota is 5 minutes and the authorized quota is 10 Mbits.
  • the client After receiving the indication from the server, the client runs out of the remaining 5 minutes and then uses the authorized 10 Mbit traffic.
  • S406 The client separately reports the used usage information of the remaining quota and the used usage information of the authorized quota.
  • the client When the client reports, it distinguishes the original remaining quota from the usage quota issued by the server.
  • the escalation condition satisfies the occurrence of a trigger event as defined by RFC4006 or a trigger event as defined by 3GPP TS32.251.
  • the client can carry the used amount information of the remaining quota and the used amount information of the authorized quota through the CCR.
  • the type of the remaining quota is the duration
  • the type of the authorized quota is the traffic
  • the information carried by the CCR includes the following fields.
  • the Used-Service-Unit field including the Original-Remain-Usage and the CC-Time is a usage information field of the remaining quota, and the Original-Remain-Usage is used to indicate that the Used-Service-Unit field is a usage information field of the remaining quota.
  • CC-Time is the amount of time remaining.
  • the Used-Service-Unit field containing CC-Total-Octets is the usage information field of the authorization quota, and CC-Total-Octets is the usage amount of the authorized traffic.
  • the type of the remaining quota is the duration
  • the type of the authorized quota is the traffic
  • the information carried by the CCR includes the following fields.
  • the Used-Service-Unit field containing the CC-Time is the usage information field of the remaining quota, and is indicated by the value of the Tariff-Change-Usage.
  • the Used-Service-Unit field containing CC-Total-Octets is the usage information field of the authorization quota, indicated by the value of Tariff-Change-Usage. You can set the value of Tariff-Change-Usage to 0 to indicate that the Used-Service-Unit field is the usage information field of the remaining quota. A value of 1 indicates that the Used-Service-Unit field is the usage information field of the authorization quota.
  • the value of the Tariff-Change-Usage value may be set to 1 to indicate that the Used-Service-Unit field is the usage information field of the remaining quota, and the value is 0 to indicate that the Used-Service-Unit field is the usage information field of the authorization quota.
  • the server when the client requests a new quota from the server, the server sends the authorized quota and the indication information to the client, so that the client can use the remaining quota and then use the authorized quota, and then Differentiate the usage information of the remaining quota and the usage information of the authorization quota. It makes the application and grant of quotas more reasonable, effectively reducing the frequent quota granting process and reducing the network burden. Reduced business delays while ensuring that the quota used by the business does not exceed the authorized quota.
  • FIG. 5 is an exemplary flowchart of a quota management method 500 in accordance with an embodiment of the present application.
  • the quota management method 500 can be performed by the client 101 and the server 102 shown in FIG.
  • a service flow flows on the client, and the client applies for a quota to the server for use by the service, and reports the quota used by the service to the server.
  • the client sends a charging request to the server, where the information of the request quota and the information of the quota usage amount are carried.
  • the server receives a charging request from the client, where the information of the request quota and the used amount of information are carried.
  • S503 The server sends the authorized quota and the indication information to the client, where the indication information is used to indicate that the client stops using the remaining quota of the client, and starts using the authorized quota.
  • the server determines whether the authorized quota and the remaining quota of the client can be merged. In this embodiment, the server determines that the authorized quota is not merged with the remaining quota of the client, and the indication information indicates that the client stops using the remaining quota and starts using the authorized quota. Wherein, when the remaining quota and the authorized quota type are different and cannot be converted, the remaining quota and the authorized quota cannot be combined.
  • the server saves the authorized quota and the remaining quota of the client separately, so that the subsequent quota is deducted from the authorized quota and the remaining quota respectively.
  • the server can determine whether the authorized quota and the remaining quota of the client can be merged according to the reporting reason sent by the client or the configuration information on the server.
  • the authorization quota and indication information sent by the server to the client can be carried by the CCA.
  • the type of the authorized quota is the traffic
  • the type of the remaining quota is the duration
  • the authorized traffic and the remaining duration are not convertible.
  • the information carried by the CCA includes the following fields.
  • the Multiple-Services-Credit-Control is a multi-service MAC field, and includes a Granted-Service-Unit field and a Rating-Group field.
  • the Granted-Service-Unit field is information about the authorization quota.
  • the CC-Total-Octets field is the total amount of authorized traffic.
  • the Unit-Usage-Indicator field is the indication information, which is used to indicate that the client stops using the remaining duration and starts to use. Authorized traffic.
  • the client receives the quota of the authorization from the server and the indication information.
  • the quota available to the client is the quota authorized by the server.
  • the client stops using the remaining quota and starts to use the authorized quota.
  • the client when the client sends the information requesting the quota, the remaining quota is 5 minutes, and the authorized quota is 10 Mbit.
  • the client receives the indication from the server, it has used 2 minutes of the remaining 5 minutes quota. At this time, the client stops using the remaining 3 minutes and starts to use the authorized 10 Mbit traffic.
  • S506 The client separately reports the used usage information of the remaining quota and the used usage information of the authorized quota.
  • the server when the client requests a new quota from the server, the server sends the authorized quota and the indication information to the client, so that the client stops using the remaining quota, and then uses the authorized quota, and then Differentiate the usage information of the remaining quota and the usage information of the authorization quota. It makes the application and grant of quotas more reasonable, effectively reducing the frequent quota granting process and reducing the network burden. Reduced business delays while ensuring that the quota used by the business does not exceed the authorized quota.
  • the server may not determine whether the authorized quota and the remaining quota of the client can be merged, but directly grant the quota to the client. And save the authorized quota and the remaining quota of the client separately.
  • the client does not send the indication.
  • the server may instruct the client to perform the above processing by sending the indication information to the client.
  • the specific process of the server instructing the client to perform the above processing by sending the indication information to the client may refer to the embodiment S503 to S506 of FIG. 5 and the embodiments S603 to S606 of FIG. 6, respectively.
  • the client when the client no longer needs to continue to use the rate group or the quota of the service identifier, the client clears the current remaining quota belonging to the rate group or the service identifier.
  • the server reclaims the current remaining quota belonging to the rate group or the service identifier. This can be achieved in the following two ways.
  • the first type the client clears the current remaining quota, and sends a charging request to the server that carries the quota used information but does not carry the information of the request quota.
  • the server returns the current remaining quota of the client to the user account. For example, if the server authorizes the rate group to be 10 Mbits of A for a certain time, the client no longer needs to continue to use the quota of the rate group as A after using for a period of time. At this time, the remaining quota of the client is 7 Mbit, and the client clears the remaining 7 Mbit quota.
  • the client reports the quota usage of 3 Mbit to the server through the accounting request, and the accounting request does not carry the information of the request quota.
  • the server returns the remaining 7Mbit quota to the user account.
  • the client clears the current remaining quota and sends a charging request carrying the quota recovery indication to the server.
  • the server returns the current remaining quota of the client to the user account. For example, if the server authorizes the rate group to be 10 Mbits of A for a certain time, the client no longer needs to continue to use the quota of the rate group as A after using for a period of time. At this time, the remaining quota of the client is 7 Mbit, and the client clears the remaining 7 Mbit quota.
  • the client sends a quota recovery indication to the server through the charging request.
  • the server returns the remaining 7Mbit quota to the user account.
  • the quota reclaiming indication may be carried in the CCR.
  • the new indication parameter is used as the quota recovery indication, and the unused quota is also carried in the CCR as the quota recovery indication.
  • the information carried by the CCR includes the following fields.
  • Quota-Final-indicator is a quota recovery instruction.
  • the client may send an accounting request carrying a quota recovery indication to the server, or the server may first send a re-authentication request (RAR) to the client, and the client returns a re-authentication response (Re-Auth- After the answer, RAA, the accounting request carrying the quota collection indication is sent to the server.
  • RAR re-authentication request
  • Re-Auth- re-authentication response
  • the server may also notify the client through the CCA that the quota of a certain rate group needs to be reclaimed, so that the client sends a charging request carrying the quota recovery indication to the server.
  • the server carries an indication in the event when it determines that certain events need to be re-granted.
  • the information carried by the CCA contains the following fields
  • the client When the client detects that the event occurs and needs to report, the client sends a CCR to the server and carries a quota recovery indication through the CCR.
  • the server sends an authorization failure indication information to the client, instructing the client to perform the following operations: report the used amount information of the remaining quota after using the remaining quota, Or, when receiving the authorization failure indication information, stop using the remaining quota and report the used usage information of the remaining quota. For example, if the remaining quota of the client is 5 Mbit, the server fails to request the quota when the server requests the authorization quota. The server sends a CCA to the client, which carries the authorization failure indication information. The client has used the 2Mbit quota when receiving the CCA, and the current remaining quota is 3Mbit.
  • the client performs the following operations: after the remaining 3 Mbits are used, the used usage information of the remaining 5 Mbit quotas is reported; or the client stops using the remaining 3 Mbit quotas, and the remaining 5 MBit quotas are used before reporting.
  • Quantity information ie 2Mbit.
  • the authorization failure indication information may be an authorization failure error code or an indication parameter.
  • the server deducts the used amount reported by the client from the authorized quota, but does not return the remaining quota to the user account.
  • the server returns result information to the client. Based on the result information, the client can continue to use the remaining quota after the deduction.
  • the quota of the server authorization is 100 Mbit.
  • the client will report the used usage information. The client reports that the 10 Mbit quota has been used.
  • the server deducts 10 Mbit from the authorized 100 Mbit quota and reserves the remaining.
  • the 90Mbit quota is used by the client and does not return the remaining 90Mbit quota to the user account.
  • the server sends a CCA to the client, confirming that the 10Mbit quota has been deducted, and the client can continue to use the remaining 90Mbit quota.
  • FIG. 6 is a schematic structural diagram of a client 600 according to an embodiment of the present application.
  • Client 600 includes a transmitting module 602, a receiving module 604, and a processing module 606.
  • the client 600 is the client 101 in FIG. 1, FIG. The computer device in the embodiment, and the client in the embodiment of Figures 3 to 5.
  • the sending module 602 can be used to execute S301 and S306 in the embodiment of FIG. 3, S401 and S406 in the embodiment of FIG. 4, and S501 and S506 in the embodiment of FIG. 5.
  • the receiving module 604 can be used to execute S304 in the embodiment of FIG. 3, S404 in the embodiment of FIG. 4, and S504 in the embodiment of FIG. 5.
  • the processing module 606 can be used to perform S305 in the embodiment of FIG. 3, S405 in the embodiment of FIG. 4, and S505 in the embodiment of FIG. 5.
  • FIG. 7 is a schematic structural diagram of a server 700 according to an embodiment of the present application.
  • Server 700 includes a receiving module 702 and a transmitting module 704.
  • Server 700 is server 102 in Figure 1, computer device in the embodiment of Figure 2, and servers in the embodiment of Figures 3 through 5.
  • the receiving module 702 can be used to execute S302 in the embodiment of FIG. 3, S402 in the embodiment of FIG. 4, and S502 in the embodiment of FIG. 5.
  • the sending module 704 can be used to execute S303 in the embodiment of FIG. 3, S403 in the embodiment of FIG. 4, and S503 in the embodiment of FIG. 5.
  • the "module" in the embodiment of FIG. 6 and FIG. 7 may be an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor and a memory that execute one or more software or firmware programs, a combination logic circuit, and Other components that provide the above features.
  • ASIC Application Specific Integrated Circuit
  • the client and the server are implemented by using a computer device.
  • the receiving module and the sending module may be implemented by a processor, a memory, and a communication interface of the computer device, where the processing module may pass through a processor and a memory of the computer device. to realise.
  • the computer device 200 shown in FIG. 2 only shows the processor 202, the memory 204, the communication interface 206, and the bus 208
  • the above-described client and server are understood in a specific implementation process. It also contains other devices necessary to get it running.
  • the above client and server may also include hardware devices that implement other additional functions, depending on the particular needs.
  • the above-described client and server may also only include the components necessary to implement the embodiments of the present application, and do not necessarily include all of the devices shown in FIG. 2.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Transfer from a computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer.
  • the computer instructions can be stored or transmitted using a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)).
  • SSD Solid State Disk
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium including a plurality of instructions for causing one
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • a processor performs all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请的实施例提供一种配额管理方法，包括客户端向服务器发送计费请求，所述计费请求携带请求配额的信息和配额已使用量的信息；所述客户端接收来自所述服务器的授权的配额以及指示信息；所述客户端根据所述指示信息对所述授权的配额以及所述客户端剩余的配额进行处理，所述剩余的配额为所述服务器上一次授权的配额与所述计费请求中的配额已使用量的差额；所述客户端使用所述处理后的配额，并在上报条件满足时上报所述处理后配额的已使用量信息。能够减少业务延迟，同时保证业务使用的配额不超过授权的配额。

Description

一种配额管理方法及装置
本申请要求于2016年12月28日提交中国专利局、申请号为201611238536.2，发明名称为“一种配额管理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种配额管理方法及装置。
背景技术
第三代合作伙伴项目(the 3rd Generation Partnership Project，3GPP)中，信控客户端(credit-control client)向信控服务器(credit-control server)申请配额并使用。当触发事件发生时，信控客户端向信控服务器上报配额使用信息，同时请求信控服务器下发新的配额。信控服务器回收信控客户端上的剩余配额，并重新下发新的配额。此时，如果信控客户端放通业务，会造成运营商损失；如果信控客户端暂定业务，会造成业务延迟，降低用户体验。
发明内容
本申请的实施例提供一种配额管理方法和装置，能够减少业务延迟，同时保证业务使用的配额不超过授权的配额。
第一方面，提供了一种配额管理方法，包括客户端向服务器发送计费请求，其中携带请求配额的信息和配额已使用量的信息；客户端接收来自服务器的授权的配额以及指示信息，根据指示信息对授权的配额以及客户端剩余的配额进行处理。其中，剩余的配额为服务器上一次授权的配额与该计费请求中的配额已使用量的差额。客户端使用处理后的配额，并在上报条件满足时上报处理后配额的已使用量信息。
结合第一方面的实现方式，在第一方面第一种可能的实现方式中，客户端根据指示信息对授权的配额以及客户端剩余的配额进行处理，在上报条件满足时上报处理后配额的已使用量信息包括：客户端合并授权的配额和剩余的配额，并在客户端上报计费信息时，上报合并后的配额的已使用量信息。
结合第一方面或第一方面的第一种可能的实现方式，在第二种可能实现的方式中，指示信息包含配额换算系数，则客户端合并授权的配额和客户端剩余的配额包括：客户端根据配额换算系数换算客户端在接收到指示信息时的可用剩余配额，合并授权的配额和换算后的可用剩余配额；则客户端上报计费信息时，还上报在接收到指示信息时剩余的配额的已使用量信息。
结合第一方面或第一方面的第一种至第二种可能的实现方式中的任意一种，在第三种可能实现的方式中，客户端根据指示信息对授权的配额以及客户端剩余的配额进行处理，在上报条件满足时上报处理后配额的已使用量信息包括：客户端根据指示信息，在使用完剩余的配额后再使用授权的配额，客户端在上报计费信息时，分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
结合第一方面或第一方面的第一种至第三种可能的实现方式中的任意一种，在第四种可能实现的方式中，客户端根据指示信息对授权的配额以及客户端剩余的配 额进行处理，在上报条件满足时上报处理后配额的已使用量信息包括：客户端在接收到指示信息时停止使用剩余的配额，开始使用授权的配额，客户端在上报计费信息时，分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
在客户端向服务器请求新的配额时，服务器通过向客户端发送授权的配额和指示信息，使得客户端可以对授权的配额和剩余配额进行合并或切换等处理，再根据处理结果上报合并后的配额的使用信息，或分别上报授权的配额和剩余配额的使用信息。使得配额的申请和授予更合理，有效减少了频繁的配额授予过程，减轻了网络负担。减少了业务延迟，同时保证了业务使用的配额不超过授权的配额。
结合第一方面或第一方面的第一种至第四种可能的实现方式中的任意一种，在第五种可能实现的方式中，客户端还向服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；客户端清零剩余的配额，暂停业务数据流通过，被清零的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
结合第一方面或第一方面的第一种至第五种可能的实现方式中的任意一种，在第六种可能实现的方式中，客户端还向服务器发送携带配额回收指示的计费请求；客户端清零剩余的配额，暂停业务数据流通过，被清零的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
客户端在不需要继续使用配额时，剩余配额被回收。
结合第一方面或第一方面的第一种至第六种可能的实现方式中的任意一种，在第七种可能实现的方式中，当客户端接收到来自服务器的授权失败指示信息时，客户端根据授权失败指示信息，在使用完剩余的配额后上报剩余的配额的已使用量信息。
结合第一方面或第一方面的第一种至第七种可能的实现方式中的任意一种，在第八种可能实现的方式中，当客户端接收到来自服务器的授权失败指示信息时，客户端停止使用剩余的配额，上报剩余配额的已使用量信息。
结合第一方面或第一方面的第一种至第八种可能的实现方式中的任意一种，在第九种可能实现的方式中，在客户端向服务器发送计费请求之前，或者，在客户端上报处理后配额的已使用量信息之后，客户端向服务器发送携带已使用量的信息，但未携带请求配额的信息的计费请求，以使服务器从授权的配额中扣减携带的已使用量，扣减之后剩余的部分作为剩余的配额；客户端继续使用扣减后剩余的配额。
有时服务器授权的配额较多，如果触发事件发生就回收剩余配额并重新授予配额会增加网络负担。通过这种方式能够使得在一部分触发事件发生时，服务器不必重新授予配额，减轻了网络负担。
第二方面，提供了一种配额管理方法，包括服务器接收来自客户端的计费请求，其中携带请求配额的信息和配额已使用量的信息；服务器向客户端发送授权的配额以及指示信息，其中，指示信息用于指示客户端对授权的配额以及客户端剩余的配额进行处理。剩余的配额为服务器上一次授权的配额与计费请求中的配额已使用量的差额。
结合第二方面的实现方式，在第二方面第一种可能的实现方式中，指示信息用于指示客户端对授权的配额以及客户端剩余的配额进行处理，包括：指示信息用于 指示客户端合并授权的配额和客户端剩余的配额。
结合第二方面或第二方面的第一种可能的实现方式，在第二种可能实现的方式中，指示信息包含配额换算系数，则指示客户端合并授权的配额和客户端剩余的配额包括：指示客户端根据配额换算系数换算客户端在接收到指示信息时的可用剩余配额，合并授权的配额和换算后的可用剩余配额。
结合第二方面或第二方面的第一种至第二种可能的实现方式中的任意一种，在第三种可能实现的方式中，指示信息用于指示客户端对授权的配额以及客户端剩余的配额进行处理，包括：指示信息用于指示客户端在使用完剩余的配额后再使用授权的配额。
结合第二方面或第二方面的第一种至第三种可能的实现方式中的任意一种，在第四种可能实现的方式中，指示信息用于指示客户端对授权的配额以及客户端剩余的配额进行处理，包括：指示信息用于指示客户端在接收到指示信息时，停止使用剩余的配额，开始使用授权的配额。
在客户端向服务器请求新的配额时，服务器通过向客户端发送授权的配额和指示信息，使得客户端可以对授权的配额和剩余配额进行合并或切换等处理，再根据处理结果上报合并后的配额的使用信息，或分别上报授权的配额和剩余配额的使用信息。使得配额的申请和授予更合理，有效减少了频繁的配额授予过程，减轻了网络负担。减少了业务延迟，同时保证了业务使用的配额不超过授权的配额。
结合第二方面或第二方面的第一种至第四种可能的实现方式中的任意一种，在第五种可能实现的方式中，在服务器接收到携带配额已使用量的信息，但未携带请求配额的信息的计费请求时，服务器向用户账户返还剩余的配额，被返还的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
结合第二方面或第二方面的第一种至第五可能的实现方式中的任意一种，在第六种可能实现的方式中，在服务器接收到来自客户端的携带配额回收指示的计费请求时，服务器向用户账户返还剩余的配额，被返还的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
客户端在不需要继续使用配额时，剩余配额被回收。
结合第二方面或第二方面的第一种至第六可能的实现方式中的任意一种，在第七种可能实现的方式中，当服务器授权配额失败时，服务器向客户端发送授权失败指示信息，授权失败指示信息用于指示客户端在使用完剩余的配额后上报剩余配额的已使用量信息。
结合第二方面或第二方面的第一种至第七种可能的实现方式中的任意一种，在第八种可能实现的方式中，当服务器授权配额失败时，服务器向客户端发送授权失败指示信息，授权失败指示信息用于指示客户端在接收到授权失败指示信息时，停止使用剩余的配额，上报剩余配额的已使用量信息。
结合第二方面或第二方面的第一种至第八种可能的实现方式中的任意一种，在第九种可能实现的方式中，在服务器接收来自客户端的计费请求之前，或者，在服务器向客户端发送授权的配额以及指示信息之后，当服务器接收到来自客户端的携带已使用量的信息，但未携带请求配额的信息的计费请求时，服务器从授权的配额 中扣减携带的已使用量，扣减后剩余的部分作为剩余的配额，并根据携带的已使用量的信息在用户账户中扣除已使用量。
第三方面，提供了一种配额管理方法，包括客户端向服务器发送计费请求，其中携带请求配额的信息和配额已使用量的信息；客户端接收来自服务器的授权的配额；客户端在使用完剩余的配额后，使用授权的配额。其中，剩余的配额为服务器上一次授权的配额与计费请求中的配额已使用量的差额。客户端分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
第四方面，提供了一种配额管理方法，包括客户端向服务器发送计费请求，其中携带请求配额的信息和配额已使用量的信息；客户端接收来自服务器的授权的配额；客户端停止使用剩余的配额，开始使用授权的配额，其中，剩余的配额为服务器上一次授权的配额与计费请求中的配额已使用量的差额。客户端分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
结合第三方面和第四方面的实现方式，在一种实现方式中，客户端还向服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；客户端清零剩余的配额，暂停业务数据流通过，其中，被清零的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的已使用量的差额。
结合第三方面和第四方面的实现方式，在另一种实现方式中，当客户端接收到来自服务器的授权失败指示信息时，客户端根据授权失败指示信息，在使用完剩余的配额后上报剩余的配额的已使用量信息。
结合第三方面和第四方面的实现方式，在又一种实现方式中，当客户端接收到来自服务器的授权失败指示信息时，客户端停止使用剩余的配额，上报剩余配额的已使用量信息。
第五方面，提供了一种客户端，包括发送模块，接收模块和处理模块。其中，发送模块，用于向服务器发送计费请求，其中携带请求配额的信息和配额已使用量的信息；接收模块，用于接收来自服务器的授权的配额以及指示信息；处理模块，用于根据指示信息对授权的配额以及客户端剩余的配额进行处理，其中，剩余的配额为服务器上一次授权的配额与计费请求中的配额已使用量的差额；处理模块，还用于使用处理后的配额；发送模块，还用于在上报条件满足时上报处理后配额的已使用量信息。
结合第五方面的实现方式，在第五方面第一种可能的实现方式中，处理模块用于根据指示信息对授权的配额以及客户端剩余的配额进行处理，发送模块用于在上报条件满足时上报处理后配额的已使用量信息包括：处理模块用于合并授权的配额和剩余的配额，发送模块用于在客户端上报计费信息时，上报合并后的配额的已使用量信息。
结合第五方面或第五方面的第一种可能的实现方式，在第二种可能实现的方式中，指示信息包含配额换算系数，则处理模块用于合并授权的配额和客户端剩余的配额包括：处理模块用于根据配额换算系数换算接收模块在接收到指示信息时的可用剩余配额，合并授权的配额和换算后的可用剩余配额；则发送模块上报计费信息时，还上报在接收到指示信息时剩余的配额的已使用量信息。
结合第五方面或第五方面的第一种至第二种可能的实现方式中的任意一种，在 第三种可能实现的方式中，处理模块用于根据指示信息对授权的配额以及客户端剩余的配额进行处理，发送模块用于在上报条件满足时上报处理后配额的已使用量信息包括：处理模块用于根据指示信息，在使用完剩余的配额后再使用授权的配额，发送模块用于在上报计费信息时，分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
结合第五方面或第五方面的第一种至第三种可能的实现方式中的任意一种，在第四种可能实现的方式中，处理模块用于根据指示信息对授权的配额以及客户端剩余的配额进行处理，发送模块用于在上报条件满足时上报处理后配额的已使用量信息包括：处理模块用于在接收到指示信息时停止使用剩余的配额，开始使用授权的配额，发送模块用于在上报计费信息时，分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
结合第五方面或第五方面的第一种至第四种可能的实现方式中的任意一种，在第五种可能实现的方式中，发送模块还用于向服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；处理模块还用于清零剩余的配额，暂停业务数据流通过，其中，被清零的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
结合第五方面或第五方面的第一种至第五种可能的实现方式中的任意一种，在第六种可能实现的方式中，发送模块还用于向服务器发送携带配额回收指示的计费请求；处理模块还用于清零剩余的配额，暂停业务数据流通过，其中，被清零的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
结合第五方面或第五方面的第一种至第六可能的实现方式中的任意一种，在第七种可能实现的方式中，当接收模块接收到来自服务器的授权失败指示信息时，处理模块根据授权失败指示信息，在使用完剩余的配额后上报剩余的配额的已使用量信息。
结合第五方面或第五方面的第一种至第七可能的实现方式中的任意一种，在第八种可能实现的方式中，当接收模块接收到来自服务器的授权失败指示信息时，处理模块停止使用剩余的配额，上报剩余配额的已使用量信息。
结合第五方面或第五方面的第一种至第八可能的实现方式中的任意一种，在第九种可能实现的方式中，在发送模块向服务器发送计费请求之前，或者，在发送模块上报处理后配额的已使用量信息之后，发送模块还用于向服务器发送携带已使用量的信息，但未携带请求配额的信息的计费请求，以使服务器从授权的配额中扣减携带的已使用量，扣减之后剩余的部分作为剩余的配额；处理模块继续使用扣减后剩余的配额。
第六方面，提供了一种服务器，包括接收模块和发送模块：接收模块，用于接收来自客户端的计费请求，其中，计费请求携带请求配额的信息和配额已使用量的信息；发送模块，用于向客户端发送授权的配额以及指示信息，其中，指示信息用于指示客户端对授权的配额以及客户端剩余的配额进行处理，其中，剩余的配额为服务器上一次授权的配额与计费请求中的配额已使用量的差额。
结合第六方面的实现方式，在第六方面第一种可能的实现方式中，指示信息用 于指示客户端对授权的配额以及客户端剩余的配额进行处理，包括：指示信息用于指示客户端合并授权的配额和客户端剩余的配额。
结合第六方面或第六方面的第一种可能的实现方式，在第二种可能实现的方式中，指示信息包含配额换算系数，则指示客户端合并授权的配额和客户端剩余的配额包括：指示客户端根据配额换算系数换算客户端在接收到指示信息时的可用剩余配额，合并授权的配额和换算后的可用剩余配额。
结合第六方面或第六方面的第一种至第二种可能的实现方式中的任意一种，在第三种可能实现的方式中，指示信息用于指示客户端对授权的配额以及客户端剩余的配额进行处理，包括：指示信息用于指示客户端在使用完剩余的配额后再使用授权的配额。
结合第六方面或第六方面的第一种至第三种可能的实现方式中的任意一种，在第四种可能实现的方式中，指示信息用于指示客户端对授权的配额以及客户端剩余的配额进行处理，包括：指示信息用于指示客户端在接收到指示信息时，停止使用剩余的配额，开始使用授权的配额。
结合第六方面或第六方面的第一种至第四种可能的实现方式中的任意一种，在第五种可能实现的方式中，在接收模块接收到携带配额已使用量的信息，但未携带请求配额的信息的计费请求时，发送模块向用户账户返还剩余的配额，其中，被返还的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
结合第六方面或第六方面的第一种至第五种可能的实现方式中的任意一种，在第六种可能实现的方式中，在接收模块接收到来自客户端的携带配额回收指示的计费请求时，发送模块向用户账户返还剩余的配额，其中，被返还的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
结合第六方面或第六方面的第一种至第六种可能的实现方式中的任意一种，在第七种可能实现的方式中，当授权配额失败时，发送模块用于向客户端发送授权失败指示信息，授权失败指示信息用于指示客户端在使用完剩余的配额后上报剩余配额的已使用量信息。
结合第六方面或第六方面的第一种至第七种可能的实现方式中的任意一种，在第八种可能实现的方式中，当授权配额失败时，发送模块用于向客户端发送授权失败指示信息，授权失败指示信息用于指示客户端在接收到授权失败指示信息时，停止使用剩余的配额，上报剩余配额的已使用量信息。
结合第六方面或第六方面的第一种至第八种可能的实现方式中的任意一种，在第九种可能实现的方式中，服务器还包括处理模块，在接收模块接收来自客户端的计费请求之前，或者，在发送模块向客户端发送授权的配额以及指示信息之后，当接收模块接收到来自客户端的携带已使用量的信息，但未携带请求配额的信息的计费请求时，处理模块用于从授权的配额中扣减携带的已使用量，扣减后剩余的部分作为剩余的配额，并根据携带的已使用量的信息在用户账户中扣除已使用量。
第七方面，提供了一种客户端，包括发送模块，接收模块和处理模块：发送模块，用于向服务器发送计费请求，其中，计费请求携带请求配额的信息和配额已使用量的信息；接收模块，用于接收来自服务器的授权的配额；处理模块，用于在使 用完剩余的配额后，使用授权的配额，其中，剩余的配额为服务器上一次授权的配额与计费请求中的配额已使用量的差额；发送模块，还用于分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
第八方面，提供了一种客户端，包括发送模块，接收模块和处理模块：发送模块，用于向服务器发送计费请求，其中，计费请求携带请求配额的信息和配额已使用量的信息；接收模块，用于接收来自服务器的授权的配额；处理模块，用于停止使用剩余的配额，开始使用授权的配额，其中，剩余的配额为服务器上一次授权的配额与计费请求中的配额已使用量的差额；发送模块，还用于分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
结合第七方面和第八方面的实现方式，在一种实现方式中，发送模块还用于向服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；处理模块还用于清零剩余的配额，暂停业务数据流通过，其中，被清零的剩余的配额为授权配额与未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
结合第七方面和第八方面的实现方式，在另一种实现方式中，当接收模块接收到来自服务器的授权失败指示信息时，处理模块用于根据授权失败指示信息，在使用完剩余的配额后上报剩余的配额的已使用量信息。
结合第七方面和第八方面的实现方式，在又一种实现方式中，当接收模块接收到来自服务器的授权失败指示信息时，处理模块用于停止使用剩余的配额，上报剩余配额的已使用量信息。
第九方面，提供了一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述计算设备执行第一方面至第四方面及第一方面至第四方面的任一可能的实现方式所述的方法。
本申请的又一方面提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
根据本申请实施例提供的技术方案，在客户端向服务器请求新的配额时，服务器通过向客户端发送授权的配额和指示信息，使得客户端可以对授权的配额和剩余配额进行合并或切换等处理，再根据处理结果上报合并后的配额的使用信息，或分别上报授权的配额和剩余配额的使用信息。使得配额的申请和授予更合理，有效减少了频繁的配额授予过程，减轻了网络负担。减少了业务延迟，同时保证了业务使用的配额不超过授权的配额。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
图1是本申请实施例应用的网络架构的示意图；
图2是依据本申请一实施例的计算机设备200的硬件结构示意图；
图3是依据本申请一实施例的配额管理方法300的示范性流程图；
图4是依据本申请一实施例的配额管理方法400的示范性流程图；
图5是依据本申请一实施例的配额管理方法500的示范性流程图；
图6是依据本申请一实施例的客户端600的结构示意图；
图7是依据本申请一实施例的服务器700的结构示意图。
具体实施方式
图1是本申请实施例应用的网络架构的示意图。其中，客户端101为使用Diameter协议进行通信的网络设备，可以称为信控客户端，例如可以为网关。服务器102为使用Diameter协议进行通信的网络设备，可以称为信控服务器，例如可以为在线计费系统(Online Charging System，OCS)。客户端101向服务器102申请配额供业务使用。服务器102向客户端101授权配额，并根据客户端101上报的配额已使用量进行计费。其中，配额指服务器102授权给客户端101供业务使用的配额类型的数量。若配额类型为流量，则配额为授予的流量数(如5M流量)；若配额类型为时长，则配额为授予的时长(如30分钟)。现有技术中，信控客户端向信控服务器上报配额已使用量信息并请求授予新配额时，会导致信控服务器回收信控客户端上的剩余配额并重新授权配额，从而造成业务延迟等问题。本申请中，在客户端101向服务器102上报配额已使用量并请求授予新配额时，能够实现客户端101上剩余的配额有效，不因为上报而导致剩余配额回收，解决了业务延迟以及频繁授予配额等问题。
客户端101和服务器102可以通过计算机设备的形式实现。图2是依据本申请一实施例的计算机设备200的硬件结构示意图。如图2所示，计算机设备200包括处理器202、存储器204、通信接口206和总线208。其中，处理器202、存储器204和通信接口206通过总线208实现彼此之间的通信连接。
处理器202可以采用通用的中央处理器(Central Processing Unit，CPU)，微处理器，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，或者一个或多个集成电路，用于执行相关程序，以实现本申请实施例所提供的技术方案。
存储器204可以是只读存储器(Read Only Memory，ROM)，静态存储设备，动态存储设备或者随机存取存储器(Random Access Memory，RAM)。存储器204可以存储操作系统2041和其他应用程序2042。在通过软件或者固件来实现本申请实施例提供的技术方案时，用于实现本申请实施例提供的技术方案的程序代码保存在存储器204中，并由处理器202来执行。
通信接口206使用例如但不限于收发器一类的收发装置，来实现与其他设备或通信网络之间的通信。
总线208可包括一通路，在各个部件(例如处理器202、存储器204、通信接口206)之间传送信息。
当客户端101通过计算机设备200实现时，处理器202用于执行存储器204存储的用于实现本申请实施例提供的技术方案的程序代码，以实现图3至图5实施例所示的方法。
当服务器102通过计算机设备200实现时，处理器202用于执行存储器204存 储的用于实现本申请实施例提供的技术方案的程序代码，以实现图3至图5实施例所示的方法。
下面结合几个实施例来对本申请提供的配额管理方法进行说明。以下实施例中，配额的处理、上报、返还等操作针对的是同一费率组或业务标识的配额，可以理解的是，其他费率组或业务标识的配额的处理方法相同。
图3是依据本申请一实施例的配额管理方法300的示范性流程图。在具体实现过程中，配额管理方法300可以由图1所示的客户端101和服务器102来执行。
客户端上有业务流流过，客户端向服务器申请配额供该业务使用，并向服务器上报该业务已经使用了的配额。
S301，客户端向服务器发送计费请求，其中携带请求配额的信息和配额已使用量的信息。
具体的，客户端可以在RFC4006定义的触发事件发生或3GPP TS32.251定义的触发事件发生时向服务器发送上述计费请求。其中，3GPP TS32.251定义的触发事件包括例如客户端可用配额低于门限值，接入网类型切换等。
S302，服务器接收来自客户端的计费请求，其中携带请求配额的信息和配额已使用量的信息。
服务器根据接收到的请求配额的信息确定客户端仍需要使用配额，因此服务器保持客户端剩余的配额有效，不对客户端剩余的配额进行回收。客户端可以继续使用剩余的配额。服务器可以通过如下方式来保持客户端剩余的配额有效：服务器不向用户账户返还所述剩余的配额。
S303，服务器向客户端发送授权的配额以及指示信息，所述指示信息用于指示所述客户端合并所述授权的配额和所述剩余的配额。
可选的，在向客户端发送授权的配额之前，服务器判断授权的配额与客户端剩余的配额是否可以合并。在本实施例中，服务器确定授权的配额与客户端剩余的配额可合并，因此指示信息指示客户端将授权的配额和剩余配额进行合并。其中，当剩余配额和授权的配额类型相同并且单位价值相同时，剩余配额和授权的配额可合并。例如，剩余配额为流量，单位价值为1元/1Mbit，授权的配额也为流量，单位价值也为1元/Mbit，剩余配额和授权配额的类型相同，单位价值也相同，因此剩余配额和授权的配额可合并。另外，当剩余配额和授权的配额类型不同或者单位价值不同时，但剩余配额和授权配额可换算时，换算后的剩余配额和授权的配额也可合并。这种情况将在下文进行详细描述。
当授权的配额与客户端剩余的配额可以合并时，服务器合并授权的配额与客户端剩余的配额，并保存合并后的配额，以便后续进行计费时从合并后的配额中进行扣减。服务器可以根据客户端发送的上报原因或服务器上的配置信息确定授权的配额和客户端剩余的配额是否可以合并。
本实施例中，要求客户端将剩余配额和授权配额进行合并的指示信息的表示方式有两种，一种是通过下发指示参数的方式来表示，另一种是通过不下发指示参数的方式来表示。在第一种方式中，指示参数的值为指示客户端将剩余配额和授权配 额进行合并。例如，指示参数可能的取值为1,2,3，当取值为2时表示将剩余配额和授权配额合并。取值为1可以表示使用完剩余配额后再使用授权配额，取值为3可以表示在接收到指示信息时停止使用剩余配额，开始使用授权配额。在第二种方式中，客户端没有接收到指示参数，则确定应将剩余配额和授权配额合并；如果客户端接收到指示参数，则确定不将剩余配额和授权配额合并，而是按照指示参数的指示进行处理。例如，客户端接收到指示参数，并且其值为1，则客户端在使用完剩余配额后再使用授权配额。
服务器向客户端发送的授权配额和指示信息可以通过信用控制应答(Credit Control Answer，CCA)携带。
在一个例子中，假设授权配额的类型为流量，剩余配额的类型也为流量，CCA携带的信息包括如下字段
Multiple-Services-Credit-Control
        Granted-Service-Unit
               CC-Total-Octets
               Unit-Usage-Indicator
         Rating-Group
其中，Multiple-Services-Credit-Control为多业务信控字段，包含Granted-Service-Unit字段和Rating-Group字段。Granted-Service-Unit字段为授权配额的信息，包含的CC-Total-Octets字段为授权流量的总量，Unit-Usage-Indicator字段为指示信息，用于指示客户端合并授权的流量和客户端剩余的流量。Rating-Group为费率组字段。
S304，客户端接收来自服务器的授权的配额以及指示信息。
具体的，在接收到来自服务器授权的配额后，客户端可用的配额为当前剩余的配额以及服务器授权的配额。
S305，客户端合并所述授权的配额和所述客户端剩余的配额。
例如，客户端在发送请求配额的信息时剩余的配额为5Mbit流量，单位价值为1元/Mbit，授权的配额为10Mbit流量，单位价值也为1元/Mbit。客户端合并剩余的5Mbit配额和授权的10Mbit配额，得到合并后的配额为15Mbit。
当剩余配额和授权的配额可换算时，剩余配额和授权的配额也可合并。当剩余配额和授权配额可换算时，指示信息包含配额换算系数。客户端先根据配额换算系数换算客户端在接收到指示信息时的可用剩余配额，再将授权的配额与换算后的可用剩余配额合并。配额换算系数由服务器确定。可以利用配额换算系数进行换算的情况包括：配额单位价值不同，但配额单位价值之间可换算；或者，配额类型不同，但配额类型之间可换算。例如，客户端在发送请求配额的信息时剩余的配额为5Mbit流量，单位价值为1元/Mbit，授权的配额为10Mbit流量，单位价值为2元/Mbit，配额换算系数为2。剩余配额和授权配额的单位价值不同，但配额单位价值之间可换算。客户端在接收到指示信息时，已经使用了5Mbit剩余配额中的2Mbit，因此此时客户端的可用剩余配额为3Mbit。客户端根据配额换算系数进行计算，得到换 算后的可用剩余配额为3Mbit/2＝1.5Mbit。客户端合并换算后的可用剩余配额1.5Mbit和授权的10Mbit配额，得到合并后的配额为11.5Mbit。
S306，客户端上报合并后的配额的已使用量信息。
客户端使用合并后的配额。在上报条件满足时，客户端向服务器上报合并后的配额的已使用量信息。在上报时，客户端不区分原来的剩余配额和服务器下发的授权配额的使用信息。上报条件满足包括RFC4006定义的触发事件发生或3GPPTS32.251定义的触发事件发生。
当剩余配额和授权配额可换算时，客户端除了上报合并后的配额的已使用量信息，还上报剩余配额的已使用量信息，该剩余配额的已使用量为剩余配额未换算部分的使用信息。
客户端可以通过信用控制请求(Credit Control Request，CCR)携带合并后的配额的已使用量信息。
根据本申请实施例提供的技术方案，在客户端向服务器请求新的配额时，服务器通过向客户端发送授权的配额和指示信息，使得客户端可以对授权的配额和剩余配额进行合并，再上报合并后的配额的使用信息。使得配额的申请和授予更合理，有效减少了频繁的配额授予过程，减轻了网络负担。减少了业务延迟，同时保证了业务使用的配额不超过授权的配额。
图4是依据本申请一实施例的配额管理方法400的示范性流程图。在具体实现过程中，配额管理方法400可以由图1所示的客户端101和服务器102来执行。
客户端上有业务流流过，客户端向服务器申请配额供该业务使用，并向服务器上报该业务已经使用了的配额。
S401，客户端向服务器发送计费请求，其中携带请求配额的信息和配额已使用量的信息。
S402，服务器接收来自客户端的计费请求，其中携带请求配额的信息和配额已使用量的信息。
S401和S402的具体内容可参考图3实施例S301和S302，此处不再赘述。
S403，服务器向客户端发送授权的配额以及指示信息，所述指示信息用于指示所述客户端在使用完所述剩余的配额后再使用所述授权的配额。
可选的，在向客户端发送授权的配额之前，服务器判断授权的配额与客户端剩余的配额是否可以合并。在本实施例中，服务器确定授权的配额与客户端剩余的配额不可合并，指示信息指示客户端在使用完剩余的配额后再使用授权的配额。其中，当剩余配额和授权配额类型不同，并且不可换算时，剩余配额和授权的配额不可合并。
当授权的配额与客户端剩余的配额不可合并时，服务器分别保存授权的配额和客户端剩余的配额，以便后续进行计费时分别从授权的配额和剩余配额中进行扣减。服务器可以根据客户端发送的上报原因或服务器上的配置信息确定授权的配额和客户端剩余的配额是否可以合并。
可以通过下发指示参数的方式来表示要求客户端在使用完剩余配额后再使用 授权配额的指示信息。可以参考图3实施例S303中相关例子，此处不再赘述。
服务器向客户端发送的授权配额和指示信息可以通过CCA携带。
在一个例子中，假设授权配额的类型为流量，剩余配额的类型为时长，并且授权的流量和剩余的时长不可换算，CCA携带的信息包括如下字段
Multiple-Services-Credit-Control
        Granted-Service-Unit
               CC-Total-Octets
               Unit-Usage-Indicator
         Rating-Group
其中，Multiple-Services-Credit-Control为多业务信控字段，包含Granted-Service-Unit字段和Rating-Group字段。Granted-Service-Unit字段为授权配额的信息，包含的CC-Total-Octets字段为授权流量的总量，Unit-Usage-Indicator字段为指示信息，用于指示客户端在使用完剩余的时长后再使用授权的流量。
S404，客户端接收来自服务器的授权的配额以及指示信息。
具体的，在接收到来自服务器授权的配额后，客户端可用的配额为当前剩余的配额以及服务器授权的配额。
S405，客户端在使用完剩余的配额后再使用授权的配额。
例如，剩余的配额为5分钟时长，授权的配额为10Mbit流量。客户端在接收到来自服务器的指示信息后，先将剩余的5分钟时长用完，再使用授权的10Mbit流量。
S406，客户端分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
客户端在上报时区分原来的剩余配额和服务器下发的授权配额的使用信息。上报条件满足包括RFC4006定义的触发事件发生或3GPP TS32.251定义的触发事件发生。客户端可以通过CCR携带剩余的配额的已使用量信息和授权的配额的已使用量信息。
在一个例子中，假设剩余配额的类型为时长，授权配额的类型为流量，CCR携带的信息包括如下字段
Multiple-Services-Credit-Control
        Used-Service-Unit
             Original-Remain-Usage
             CC-Time
         Used-Service-Unit
              CC-Total-Octets
          Rating-Group
其中，包含Original-Remain-Usage和CC-Time的Used-Service-Unit字段为剩余配额的使用信息字段，Original-Remain-Usage用于指示该Used-Service-Unit字段为剩余配额的使用信息字段，CC-Time为剩余时长的使用量。包含CC-Total-Octets的Used-Service-Unit字段为授权配额的使用信息字段，CC-Total-Octets为授权流量的使用量。
在另一个例子中，假设剩余配额的类型为时长，授权配额的类型为流量，CCR携带的信息包括如下字段
Multiple-Services-Credit-Control
        Used-Service-Unit
             Tariff-Change-Usage
             CC-Time
         Used-Service-Unit
              Tariff-Change-Usage
              CC-Total-Octets
          Rating-Group
其中，包含CC-Time的Used-Service-Unit字段为剩余配额的使用信息字段，通过Tariff-Change-Usage的值来指示。包含CC-Total-Octets的Used-Service-Unit字段为授权配额的使用信息字段，通过Tariff-Change-Usage的值来指示。可以设置Tariff-Change-Usage的值为0来表示Used-Service-Unit字段为剩余配额的使用信息字段，值为1来表示Used-Service-Unit字段为授权配额的使用信息字段。或者，可以设置Tariff-Change-Usage的值为1来表示Used-Service-Unit字段为剩余配额的使用信息字段，值为0来表示Used-Service-Unit字段为授权配额的使用信息字段。
根据本申请实施例提供的技术方案，在客户端向服务器请求新的配额时，服务器通过向客户端发送授权的配额和指示信息，使得客户端可以先使用完剩余配额再使用授权的配额，然后区分上报剩余配额的使用信息和授权配额的使用信息。使得配额的申请和授予更合理，有效减少了频繁的配额授予过程，减轻了网络负担。减少了业务延迟，同时保证了业务使用的配额不超过授权的配额。
图5是依据本申请一实施例的配额管理方法500的示范性流程图。在具体实现过程中，配额管理方法500可以由图1所示的客户端101和服务器102来执行。
客户端上有业务流流过，客户端向服务器申请配额供该业务使用，并向服务器上报该业务已经使用了的配额。
S501，客户端向服务器发送计费请求，其中携带请求配额的信息和配额已使用量的信息。
S502，服务器接收来自客户端的计费请求，其中携带请求配额的信息和已使用量的信息。
S501和S502的具体内容可参考图3实施例S301和S302，以及图4实施例S401 和S402，此处不再赘述。
S503，服务器向客户端发送授权的配额以及指示信息，所述指示信息用于指示所述客户端停止使用所述客户端剩余的配额，开始使用所述授权的配额。
可选的，在向客户端发送授权的配额之前，服务器判断授权的配额与客户端剩余的配额是否可以合并。在本实施例中，服务器确定授权的配额与客户端剩余的配额不可合并，指示信息指示客户端停止使用剩余的配额，开始使用授权的配额。其中，当剩余配额和授权配额类型不同，并且不可换算时，剩余配额和授权的配额不可合并。
当授权的配额与客户端剩余的配额不可合并时，服务器分别保存授权的配额和客户端剩余的配额，以便后续进行计费时分别从授权的配额和剩余配额中进行扣减。服务器可以根据客户端发送的上报原因或服务器上的配置信息确定授权的配额和客户端剩余的配额是否可以合并。
可以通过下发指示参数的方式来表示要求客户端停止使用剩余配额，开始使用授权配额的指示信息。可以参考图3实施例S303中相关例子，此处不再赘述。
服务器向客户端发送的授权配额和指示信息可以通过CCA携带。
在一个例子中，假设授权配额的类型为流量，剩余配额的类型为时长，并且授权的流量和剩余的时长不可换算，CCA携带的信息包括如下字段
Multiple-Services-Credit-Control
       Granted-Service-Unit
              CC-Total-Octets
              Unit-Usage-Indicator
        Rating-Group
其中，Multiple-Services-Credit-Control为多业务信控字段，包含Granted-Service-Unit字段和Rating-Group字段。Granted-Service-Unit字段为授权配额的信息，包含的CC-Total-Octets字段为授权流量的总量，Unit-Usage-Indicator字段为指示信息，用于指示客户端停止使用剩余的时长，开始使用授权的流量。
S504，客户端接收来自服务器的授权的配额以及指示信息。
具体的，在接收到来自服务器授权的配额后，客户端可用的配额为服务器授权的配额。
S505，客户端停止使用剩余的配额，开始使用授权的配额。
例如，客户端在发送请求配额的信息时剩余的配额为5分钟时长，授权的配额为10Mbit流量。客户端在接收到来自服务器的指示信息时，已经使用了5分钟剩余配额中的2分钟，此时客户端停止使用剩余的3分钟时长，开始使用授权的10Mbit流量。
S506，客户端分别上报剩余的配额的已使用量信息，以及授权的配额的已使用量信息。
具体内容可以参考图4实施例S406，此处不再赘述。
根据本申请实施例提供的技术方案，在客户端向服务器请求新的配额时，服务器通过向客户端发送授权的配额和指示信息，使得客户端停止使用剩余配额，转为使用授权的配额，然后区分上报剩余配额的使用信息和授权配额的使用信息。使得配额的申请和授予更合理，有效减少了频繁的配额授予过程，减轻了网络负担。减少了业务延迟，同时保证了业务使用的配额不超过授权的配额。
在图3至图5实施例中，可选的，在向客户端发送授权的配额之前，服务器可以不判断授权的配额与客户端剩余的配额是否可以合并，而是直接向客户端授予配额，并且分别保存授权的配额和客户端剩余的配额。在下发授权配额时不下发指示信息，客户端在接收到授权的配额后，可以在使用完剩余配额后再使用授权的配额，也可以停止使用剩余的配额，开始使用授权的配额。或者，服务器也可以通过向客户端发送指示信息的方式指示客户端进行上述处理。服务器通过向客户端发送指示信息的方式指示客户端进行上述处理的具体过程可以分别参考图5实施例S503至S506，以及图6实施例S603至S606。
在图3至图5实施例中，当客户端不再需要继续使用该费率组或该业务标识的配额时，客户端将属于该费率组或该业务标识的当前的剩余配额清零，服务器回收属于该费率组或该业务标识的当前的剩余配额。具体可以通过以下两种方式实现。
第一种，客户端清零当前剩余的配额，向服务器发送携带配额已使用量信息，但未携带请求配额的信息的计费请求。服务器在接收到该计费请求时，向用户账户返还客户端当前剩余的配额。例如，服务器某次授权了费率组为A的配额10Mbit，客户端在使用一段时间后不再需要继续使用费率组为A的配额。此时客户端剩余的配额为7Mbit，客户端清零剩余的7Mbit配额。客户端通过计费请求向服务器上报配额已使用量3Mbit，计费请求中未携带请求配额的信息。服务器向用户账户返还剩余的7Mbit配额。
第二种，客户端清零当前剩余的配额，向服务器发送携带配额回收指示的计费请求。服务器在接收到来自客户端的携带配额回收指示的计费请求时，向用户账户返还客户端当前剩余的配额。例如，服务器某次授权了费率组为A的配额10Mbit，客户端在使用一段时间后不再需要继续使用费率组为A的配额。此时客户端剩余的配额为7Mbit，客户端清零剩余的7Mbit配额。客户端通过计费请求向服务器发送配额回收指示。服务器向用户账户返还剩余的7Mbit配额。
在第二种方式中，配额回收指示可以携带在CCR中，通过新增一个指示参数作为配额回收指示，也可以在CCR中携带未使用的配额来作为配额回收指示。
在一个例子中，通过新增一个指示参数作为配额回收指示，CCR携带的信息包含以下字段
Multiple-Services-Credit-Control
       Used-Service-Unit
       Rating-Group
       Service-Identifier
       Quota-Final-indicator
其中，Quota-Final-indicator为配额回收指示。
客户端可以主动向服务器发送携带配额回收指示的计费请求，也可以由服务器先向客户端发送重认证请求(Re-Auth-Request，RAR)，客户端在返回重认证应答(Re-Auth-Answer，RAA)后，向服务器发送携带配额回收指示的计费请求。还可以由服务器通过CCA通知客户端某一费率组的配额需要回收，使得客户端向服务器发送携带配额回收指示的计费请求。服务器在确定某些事件发生需要重新授予配额时，在该事件中携带指示。在一个例子中，CCA携带的信息包含以下字段
Multiple-Services-Credit-Control
        Granted-Service-Unit
        Rating-Group
        Service-Identifier
        Trigger
             Trigger-Type
             Quota-Final-indicator
客户端在检测到该事件发生，并且需要上报时，向服务器发送CCR，通过CCR携带配额回收指示。
在图3至图5实施例中，如果服务器授权配额失败，则服务器向客户端发送授权失败指示信息，指示客户端进行如下操作：在使用完剩余的配额后上报剩余配额的已使用量信息，或者，在接收到授权失败指示信息时，停止使用剩余的配额，上报剩余配额的已使用量信息。例如，客户端剩余配额为5Mbit，向服务器请求授权配额时服务器授权配额失败，服务器向客户端发送CCA，其中携带授权失败指示信息。客户端在接收到该CCA时已使用了2Mbit的配额，当前剩余的配额为3Mbit。此时客户端进行如下操作：在使用完此时剩余的3Mbit后，上报之前剩余的5Mbit配额的已使用量信息；或者，客户端停止使用剩余的3Mbit配额，上报之前剩余的5MBit配额的已使用量信息(即2Mbit)。所述授权失败指示信息可以是授权失败错误码，也可以是指示参数。
在一种实现方式中，如果服务器一次授权的配额量较大，在上报条件满足，客户端上报已使用量信息时，不会请求新的配额。对于这种情况，在图3至图5实施例中，服务器从授权的配额中扣减掉客户端上报的已使用量，但并不向用户账户返还剩余的配额。服务器向客户端返回结果信息。客户端基于该结果信息可以继续使用扣减后剩余的配额。例如，服务器授权的配额为100Mbit，当例如客户端位置改变时，会触发客户端上报已使用量信息，客户端上报已使用了10Mbit配额，服务器从授权的100Mbit配额中扣掉10Mbit，保留剩余的90Mbit配额供客户端使用，不向用户账户返还剩余的90Mbit配额。服务器向客户端发送CCA，确认已扣除10Mbit配额，以及客户端可以继续使用剩余的90Mbit配额。
图6是依据本申请一实施例的客户端600的结构示意图。客户端600包括发送模块602，接收模块604和处理模块606。客户端600为图1中的客户端101，图2 实施例中的计算机设备，以及图3至图5实施例中的客户端。发送模块602可以用来执行图3实施例中的S301和S306，图4实施例中的S401和S406，图5实施例中的S501和S506。接收模块604可以用来执行图3实施例中的S304，图4实施例中的S404，图5实施例中的S504。处理模块606可以用来执行图3实施例中的S305，图4实施例中的S405，图5实施例中的S505。
图7是依据本申请一实施例的服务器700的结构示意图。服务器700包括接收模块702和发送模块704。服务器700为图1中的服务器102，图2实施例中的计算机设备，以及图3至图5实施例中的服务器。接收模块702可以用来执行图3实施例中的S302，图4实施例中的S402，图5实施例中的S502。发送模块704可以用来执行图3实施例中的S303，图4实施例中的S403，图5实施例中的S503。
其中，图6和图7实施例中的“模块”可以为专用集成电路(Application Specific Integrated Circuit，ASIC)、电子线路、执行一个或多个软件或固件程序的处理器和存储器、组合逻辑电路和其他提供上述功能的组件。可选的，上述客户端和服务器通过计算机设备的形式来实现，上述接收模块、发送模块可以通过计算机设备的处理器、存储器和通信接口来实现，上述处理模块可以通过计算机设备的处理器和存储器来实现。
应注意，尽管图2所示的计算机设备200仅仅示出了处理器202、存储器204、通信接口206和总线208，但是在具体实现过程中，本领域的技术人员应当明白，上述客户端和服务器还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，上述客户端和服务器还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，上述客户端和服务器也可仅仅包含实现本申请实施例所必须的器件，而不必包含图2中所示的全部器件。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质。例如，可以利用磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))来存储或传输所述计算机指令。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术 方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (61)

  1. 一种配额管理方法，其特征在于，包括以下步骤：
    客户端向服务器发送计费请求，所述计费请求携带请求配额的信息和配额已使用量的信息；
    所述客户端接收来自所述服务器的授权的配额以及指示信息；
    所述客户端根据所述指示信息对所述授权的配额以及所述客户端剩余的配额进行处理，所述剩余的配额为所述服务器上一次授权的配额与所述计费请求中的配额已使用量的差额；
    所述客户端使用所述处理后的配额，并在上报条件满足时上报所述处理后配额的已使用量信息。
  2. 根据权利要求1所述的方法，其特征在于，所述客户端根据所述指示信息对所述授权的配额以及所述客户端剩余的配额进行处理，在上报条件满足时上报所述处理后配额的已使用量信息包括：
    所述客户端合并所述授权的配额和所述剩余的配额，并在所述客户端上报计费信息时，上报合并后的配额的已使用量信息。
  3. 根据权利要求2所述的方法，其特征在于，所述指示信息包含配额换算系数，则所述客户端合并所述授权的配额和所述客户端剩余的配额包括：
    所述客户端根据所述配额换算系数换算所述客户端在接收到所述指示信息时的可用剩余配额，合并所述授权的配额和所述换算后的可用剩余配额；
    则所述客户端上报计费信息时，还上报在接收到所述指示信息时所述剩余的配额的已使用量信息。
  4. 根据权利要求1所述的方法，其特征在于，所述客户端根据所述指示信息对所述授权的配额以及所述客户端剩余的配额进行处理，在上报条件满足时上报所述处理后配额的已使用量信息包括：
    所述客户端根据所述指示信息，在使用完所述剩余的配额后再使用所述授权的配额，所述客户端在上报计费信息时，分别上报所述剩余的配额的已使用量信息，以及所述授权的配额的已使用量信息。
  5. 根据权利要求1所述的方法，其特征在于，所述客户端根据所述指示信息对所述授权的配额以及所述客户端剩余的配额进行处理，在上报条件满足时上报所述处理后配额的已使用量信息包括：
    所述客户端在接收到所述指示信息时停止使用所述剩余的配额，开始使用所述授权的配额，所述客户端在上报计费信息时，分别上报所述剩余的配额的已使用量信息，以及所述授权的配额的已使用量信息。
  6. 根据权利要求1至5任意一项所述的方法，其特征在于，所述客户端还向所述服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；
    所述客户端清零剩余的配额，暂停业务数据流通过，所述被清零的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
  7. 根据权利要求1至5任意一项所述的方法，其特征在于，所述客户端还向所述服务器发送携带配额回收指示的计费请求；
    所述客户端清零剩余的配额，暂停业务数据流通过，所述被清零的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
  8. 根据权利要求1所述的方法，其特征在于，当所述客户端接收到来自所述服务器的授权失败指示信息时，所述客户端根据所述授权失败指示信息，在使用完所述剩余的配额后上报所述剩余的配额的已使用量信息。
  9. 根据权利要求1所述的方法，其特征在于，当所述客户端接收到来自所述服务器的授权失败指示信息时，所述客户端停止使用所述剩余的配额，上报所述剩余配额的已使用量信息。
  10. 根据权利要求1所述的方法，其特征在于，在所述客户端向所述服务器发送所述计费请求之前，或者，在所述客户端上报所述处理后配额的已使用量信息之后，所述方法还包括：
    所述客户端向所述服务器发送携带已使用量的信息，但未携带请求配额的信息的计费请求，以使所述服务器从授权的配额中扣减所述携带的已使用量，扣减之后剩余的部分作为剩余的配额；所述客户端继续使用所述扣减后剩余的配额。
  11. 一种配额管理方法，其特征在于，包括以下步骤：
    服务器接收来自客户端的计费请求，所述计费请求携带请求配额的信息和配额已使用量的信息；
    所述服务器向所述客户端发送授权的配额以及指示信息，所述指示信息用于指示所述客户端对所述授权的配额以及所述客户端剩余的配额进行处理，所述剩余的配额为所述服务器上一次授权的配额与所述计费请求中的配额已使用量的差额。
  12. 根据权利要求11所述的方法，其特征在于，所述指示信息用于指示所述客户端对所述授权的配额以及所述客户端剩余的配额进行处理，包括：
    所述指示信息用于指示所述客户端合并所述授权的配额和所述客户端剩余的配额。
  13. 根据权利要求12所述的方法，其特征在于，所述指示信息包含配额换算系数，则所述指示所述客户端合并所述授权的配额和所述客户端剩余的配额包括：
    指示所述客户端根据所述配额换算系数换算所述客户端在接收到所述指示信息时的可用剩余配额，合并所述授权的配额和所述换算后的可用剩余配额。
  14. 根据权利要求11所述的方法，其特征在于，所述指示信息用于指示所述客户端对所述授权的配额以及所述客户端剩余的配额进行处理，包括：
    所述指示信息用于指示所述客户端在使用完所述剩余的配额后再使用所述授权的配额。
  15. 根据权利要求11所述的方法，其特征在于，所述指示信息用于指示所述客户端对所述授权的配额以及所述客户端剩余的配额进行处理，包括：
    所述指示信息用于指示所述客户端在接收到所述指示信息时，停止使用所述剩余的配额，开始使用所述授权的配额。
  16. 根据权利要求11至15任意一项所述的方法，其特征在于，在所述服务器接收到携带配额已使用量的信息，但未携带请求配额的信息的计费请求时，所述服务器向用户账户返还剩余的配额，所述被返还的剩余的配额为授权配额与所述未携 带请求配额的信息的计费请求中携带的配额已使用量的差额。
  17. 根据权利要求11至15任意一项所述的方法，其特征在于，在所述服务器接收到来自所述客户端的携带配额回收指示的计费请求时，所述服务器向用户账户返还剩余的配额，所述被返还的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
  18. 根据权利要求11所述的方法，其特征在于，当所述服务器授权配额失败时，所述服务器向所述客户端发送授权失败指示信息，所述授权失败指示信息用于指示所述客户端在使用完所述剩余的配额后上报所述剩余配额的已使用量信息。
  19. 根据权利要求11所述的方法，其特征在于，当所述服务器授权配额失败时，所述服务器向所述客户端发送授权失败指示信息，所述授权失败指示信息用于指示所述客户端在接收到所述授权失败指示信息时，停止使用所述剩余的配额，上报所述剩余配额的已使用量信息。
  20. 根据权利要求11所述的方法，其特征在于，在所述服务器接收来自所述客户端的所述计费请求之前，或者，在所述服务器向所述客户端发送所述授权的配额以及指示信息之后，所述方法还包括：
    当所述服务器接收到来自所述客户端的携带已使用量的信息，但未携带请求配额的信息的计费请求时，所述服务器从授权的配额中扣减所述携带的已使用量，扣减后剩余的部分作为剩余的配额，并根据所述携带的已使用量的信息在用户账户中扣除已使用量。
  21. 一种配额管理方法，其特征在于，包括以下步骤：
    客户端向服务器发送计费请求，所述计费请求携带请求配额的信息和配额已使用量的信息；
    所述客户端接收来自所述服务器的授权的配额；
    所述客户端在使用完剩余的配额后，使用所述授权的配额，所述剩余的配额为所述服务器上一次授权的配额与所述计费请求中的配额已使用量的差额；
    所述客户端分别上报所述剩余的配额的已使用量信息，以及所述授权的配额的已使用量信息。
  22. 根据权利要求21所述的方法，其特征在于，所述客户端还向所述服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；
    所述客户端清零剩余的配额，暂停业务数据流通过，所述被清零的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的已使用量的差额。
  23. 根据权利要求21所述的方法，其特征在于，当所述客户端接收到来自所述服务器的授权失败指示信息时，所述客户端根据所述授权失败指示信息，在使用完所述剩余的配额后上报所述剩余的配额的已使用量信息。
  24. 根据权利要求21所述的方法，其特征在于，当所述客户端接收到来自所述服务器的授权失败指示信息时，所述客户端停止使用所述剩余的配额，上报所述剩余配额的已使用量信息。
  25. 一种配额管理方法，其特征在于，包括以下步骤：
    客户端向服务器发送计费请求，所述计费请求携带请求配额的信息和配额已使用量的信息；
    所述客户端接收来自所述服务器的授权的配额；
    所述客户端停止使用剩余的配额，开始使用所述授权的配额，所述剩余的配额为所述服务器上一次授权的配额与所述计费请求中的配额已使用量的差额；
    所述客户端分别上报所述剩余的配额的已使用量信息，以及所述授权的配额的已使用量信息。
  26. 根据权利要求25所述的方法，其特征在于，所述客户端还向所述服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；
    所述客户端清零剩余的配额，暂停业务数据流通过，所述被清零的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
  27. 根据权利要求25所述的方法，其特征在于，当所述客户端接收到来自所述服务器的授权失败指示信息时，所述客户端根据所述授权失败指示信息，在使用完所述剩余的配额后上报所述剩余的配额的已使用量信息。
  28. 根据权利要求25所述的方法，其特征在于，当所述客户端接收到来自所述服务器的授权失败指示信息时，所述客户端停止使用所述剩余的配额，上报所述剩余配额的已使用量信息。
  29. 一种客户端，其特征在于，包括发送模块，接收模块和处理模块：
    所述发送模块，用于向服务器发送计费请求，所述计费请求携带请求配额的信息和配额已使用量的信息；
    所述接收模块，用于接收来自所述服务器的授权的配额以及指示信息；
    所述处理模块，用于根据所述指示信息对所述授权的配额以及所述客户端剩余的配额进行处理，所述剩余的配额为所述服务器上一次授权的配额与所述计费请求中的配额已使用量的差额；
    所述处理模块，还用于使用所述处理后的配额；
    所述发送模块，还用于在上报条件满足时上报所述处理后配额的已使用量信息。
  30. 根据权利要求29所述的客户端，其特征在于，所述处理模块用于根据所述指示信息对所述授权的配额以及所述客户端剩余的配额进行处理，所述发送模块用于在上报条件满足时上报所述处理后配额的已使用量信息包括：
    所述处理模块用于合并所述授权的配额和所述剩余的配额，所述发送模块用于在所述客户端上报计费信息时，上报合并后的配额的已使用量信息。
  31. 根据权利要求30所述的客户端，其特征在于，所述指示信息包含配额换算系数，则所述处理模块用于合并所述授权的配额和所述客户端剩余的配额包括：
    所述处理模块用于根据所述配额换算系数换算所述接收模块在接收到所述指示信息时的可用剩余配额，合并所述授权的配额和所述换算后的可用剩余配额；
    则所述发送模块上报计费信息时，还上报在接收到所述指示信息时所述剩余的配额的已使用量信息。
  32. 根据权利要求29所述的客户端，其特征在于，所述处理模块用于根据所述指示信息对所述授权的配额以及所述客户端剩余的配额进行处理，所述发送模块用于在上报条件满足时上报所述处理后配额的已使用量信息包括：
    所述处理模块用于根据所述指示信息，在使用完所述剩余的配额后再使用所述授权的配额，所述发送模块用于在上报计费信息时，分别上报所述剩余的配额的已使用量信息，以及所述授权的配额的已使用量信息。
  33. 根据权利要求29所述的客户端，其特征在于，所述处理模块用于根据所述指示信息对所述授权的配额以及所述客户端剩余的配额进行处理，所述发送模块用于在上报条件满足时上报所述处理后配额的已使用量信息包括：
    所述处理模块用于在接收到所述指示信息时停止使用所述剩余的配额，开始使用所述授权的配额，所述发送模块用于在上报计费信息时，分别上报所述剩余的配额的已使用量信息，以及所述授权的配额的已使用量信息。
  34. 根据权利要求29至33任意一项所述的客户端，其特征在于，所述发送模块还用于向所述服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；
    所述处理模块还用于清零剩余的配额，暂停业务数据流通过，所述被清零的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
  35. 根据权利要求29至33任意一项所述的客户端，其特征在于，所述发送模块还用于向所述服务器发送携带配额回收指示的计费请求；
    所述处理模块还用于清零剩余的配额，暂停业务数据流通过，所述被清零的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
  36. 根据权利要求29所述的客户端，其特征在于，当所述接收模块接收到来自所述服务器的授权失败指示信息时，所述处理模块根据所述授权失败指示信息，在使用完所述剩余的配额后上报所述剩余的配额的已使用量信息。
  37. 根据权利要求29所述的客户端，其特征在于，当所述接收模块接收到来自所述服务器的授权失败指示信息时，所述处理模块停止使用所述剩余的配额，上报所述剩余配额的已使用量信息。
  38. 根据权利要求29所述的客户端，其特征在于，在所述发送模块向所述服务器发送所述计费请求之前，或者，在所述发送模块上报所述处理后配额的已使用量信息之后，所述发送模块还用于：
    向所述服务器发送携带已使用量的信息，但未携带请求配额的信息的计费请求，以使所述服务器从授权的配额中扣减所述携带的已使用量，扣减之后剩余的部分作为剩余的配额；所述处理模块继续使用所述扣减后剩余的配额。
  39. 一种服务器，其特征在于，包括接收模块和发送模块：
    所述接收模块，用于接收来自客户端的计费请求，所述计费请求携带请求配额的信息和配额已使用量的信息；
    所述发送模块，用于向所述客户端发送授权的配额以及指示信息，所述指示信息用于指示所述客户端对所述授权的配额以及所述客户端剩余的配额进行处理，所述剩余的配额为服务器上一次授权的配额与所述计费请求中的配额已使用量的差额。
  40. 根据权利要求39所述的服务器，其特征在于，所述指示信息用于指示所 述客户端对所述授权的配额以及所述客户端剩余的配额进行处理，包括：
    所述指示信息用于指示所述客户端合并所述授权的配额和所述客户端剩余的配额。
  41. 根据权利要求40所述的服务器，其特征在于，所述指示信息包含配额换算系数，则所述指示所述客户端合并所述授权的配额和所述客户端剩余的配额包括：
    指示所述客户端根据所述配额换算系数换算所述客户端在接收到所述指示信息时的可用剩余配额，合并所述授权的配额和所述换算后的可用剩余配额。
  42. 根据权利要求39所述的服务器，其特征在于，所述指示信息用于指示所述客户端对所述授权的配额以及所述客户端剩余的配额进行处理，包括：
    所述指示信息用于指示所述客户端在使用完所述剩余的配额后再使用所述授权的配额。
  43. 根据权利要求39所述的服务器，其特征在于，所述指示信息用于指示所述客户端对所述授权的配额以及所述客户端剩余的配额进行处理，包括：
    所述指示信息用于指示所述客户端在接收到所述指示信息时，停止使用所述剩余的配额，开始使用所述授权的配额。
  44. 根据权利要求39至43任意一项所述的服务器，其特征在于，在所述接收模块接收到携带配额已使用量的信息，但未携带请求配额的信息的计费请求时，所述发送模块向用户账户返还剩余的配额，所述被返还的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
  45. 根据权利要求39至43任意一项所述的服务器，其特征在于，在所述接收模块接收到来所述自客户端的携带配额回收指示的计费请求时，所述发送模块向用户账户返还剩余的配额，所述被返还的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
  46. 根据权利要求39所述的服务器，其特征在于，当授权配额失败时，所述发送模块用于向所述客户端发送授权失败指示信息，所述授权失败指示信息用于指示所述客户端在使用完所述剩余的配额后上报所述剩余配额的已使用量信息。
  47. 根据权利要求39所述的服务器，其特征在于，当授权配额失败时，所述发送模块用于向所述客户端发送授权失败指示信息，所述授权失败指示信息用于指示所述客户端在接收到所述授权失败指示信息时，停止使用所述剩余的配额，上报所述剩余配额的已使用量信息。
  48. 根据权利要求39所述的服务器，其特征在于，所述服务器还包括处理模块，在所述接收模块接收来自所述客户端的所述计费请求之前，或者，在所述发送模块向所述客户端发送所述授权的配额以及指示信息之后，
    当所述接收模块接收到来自所述客户端的携带已使用量的信息，但未携带请求配额的信息的计费请求时，所述处理模块用于从授权的配额中扣减所述携带的已使用量，扣减后剩余的部分作为剩余的配额，并根据所述携带的已使用量的信息在用户账户中扣除已使用量。
  49. 一种客户端，其特征在于，包括发送模块，接收模块和处理模块：
    所述发送模块，用于向服务器发送计费请求，所述计费请求携带请求配额的信 息和配额已使用量的信息；
    所述接收模块，用于接收来自所述服务器的授权的配额；
    所述处理模块，用于在使用完剩余的配额后，使用所述授权的配额，所述剩余的配额为所述服务器上一次授权的配额与所述计费请求中的配额已使用量的差额；
    所述发送模块，还用于分别上报所述剩余的配额的已使用量信息，以及所述授权的配额的已使用量信息。
  50. 根据权利要求49所述的客户端，其特征在于，所述发送模块还用于向所述服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；
    所述处理模块还用于清零剩余的配额，暂停业务数据流通过，所述被清零的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的已使用量的差额。
  51. 根据权利要求49所述的客户端，其特征在于，当所述接收模块接收到来自所述服务器的授权失败指示信息时，所述处理模块用于根据所述授权失败指示信息，在使用完所述剩余的配额后上报所述剩余的配额的已使用量信息。
  52. 根据权利要求49所述的客户端，其特征在于，当所述接收模块接收到来自所述服务器的授权失败指示信息时，所述处理模块用于停止使用所述剩余的配额，上报所述剩余配额的已使用量信息。
  53. 一种客户端，其特征在于，包括发送模块，接收模块和处理模块：
    所述发送模块，用于向服务器发送计费请求，所述计费请求携带请求配额的信息和配额已使用量的信息；
    所述接收模块，用于接收来自所述服务器的授权的配额；
    所述处理模块，用于停止使用剩余的配额，开始使用所述授权的配额，所述剩余的配额为所述服务器上一次授权的配额与所述计费请求中的配额已使用量的差额；
    所述发送模块，还用于分别上报所述剩余的配额的已使用量信息，以及所述授权的配额的已使用量信息。
  54. 根据权利要求53所述的客户端，其特征在于，所述发送模块还用于向所述服务器发送携带配额已使用量的信息，但未携带请求配额的信息的计费请求；
    所述处理模块还用于清零剩余的配额，暂停业务数据流通过，所述被清零的剩余的配额为授权配额与所述未携带请求配额的信息的计费请求中携带的配额已使用量的差额。
  55. 根据权利要求53所述的客户端，其特征在于，当所述接收模块接收到来自所述服务器的授权失败指示信息时，所述处理模块用于根据所述授权失败指示信息，在使用完所述剩余的配额后上报所述剩余的配额的已使用量信息。
  56. 根据权利要求53所述的客户端，其特征在于，当所述接收模块接收到来自所述服务器的授权失败指示信息时，所述处理模块用于停止使用所述剩余的配额，上报所述剩余配额的已使用量信息。
  57. 一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算设备执行指令，以使所 述计算设备执行权利要求1至10任意一项所述的方法。
  58. 一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算设备执行指令，以使所述计算设备执行权利要求11至20任意一项所述的方法。
  59. 一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算设备执行指令，以使所述计算设备执行权利要求21至24任意一项所述的方法。
  60. 一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算设备执行指令，以使所述计算设备执行权利要求25至28任意一项所述的方法。
  61. 一种配额管理系统，其特征在于，包括权利要求29至38任意一项所述的客户端，以及权利要求39至48任意一项所述的服务器。
PCT/CN2017/104544 2016-12-28 2017-09-29 一种配额管理方法及装置 Ceased WO2018120959A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP17888079.5A EP3554004A4 (en) 2016-12-28 2017-09-29 PROCESS AND DEVICE FOR QUOTA MANAGEMENT
EP24206336.0A EP4529095A3 (en) 2016-12-28 2017-09-29 Quota management method and apparatus
US16/453,733 US11330114B2 (en) 2016-12-28 2019-06-26 Quota management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611238536.2A CN108259196B (zh) 2016-12-28 2016-12-28 一种配额管理方法及装置
CN201611238536.2 2016-12-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/453,733 Continuation US11330114B2 (en) 2016-12-28 2019-06-26 Quota management method and apparatus

Publications (1)

Publication Number Publication Date
WO2018120959A1 true WO2018120959A1 (zh) 2018-07-05

Family

ID=62706832

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/104544 Ceased WO2018120959A1 (zh) 2016-12-28 2017-09-29 一种配额管理方法及装置

Country Status (4)

Country Link
US (1) US11330114B2 (zh)
EP (2) EP3554004A4 (zh)
CN (1) CN108259196B (zh)
WO (1) WO2018120959A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113015116B (zh) * 2019-12-20 2022-06-03 中国移动通信集团陕西有限公司 一种基于流量预测的动态配额方法和装置
CN113498033B (zh) * 2020-04-01 2024-10-11 华为技术有限公司 处理用户业务的方法、系统及相关设备
CN116074135B (zh) * 2023-01-31 2024-05-03 中国联合网络通信集团有限公司 一种配额配置方法及装置
CN120475349B (zh) * 2025-06-04 2026-04-17 重庆赛力斯凤凰智创科技有限公司 车云策略执行方法、装置、车机端、服务端和车辆

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011157123A2 (zh) * 2011-05-31 2011-12-22 华为技术有限公司 在线计费方法、在线计费系统及策略和计费规则功能实体
CN102308604A (zh) * 2011-07-07 2012-01-04 华为技术有限公司 集群在线计费方法和设备
CN105515793A (zh) * 2014-09-23 2016-04-20 中国电信股份有限公司 在线计费处理方法和系统、Openflow控制器和Openflow交换机

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0512557D0 (en) * 2005-06-20 2005-07-27 Nokia Corp Controlling provision of services in a communications network
CN101507306A (zh) * 2006-06-22 2009-08-12 艾利森电话股份有限公司 有选择地对移动电话在电信系统中的操作进行限制的系统和方法
CN102244581B (zh) * 2010-05-12 2014-09-03 华为技术有限公司 一种计费方法和装置
US9461829B2 (en) * 2011-12-27 2016-10-04 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for controlling charging in a communication network
WO2014113019A1 (en) * 2013-01-18 2014-07-24 Nokia Siemens Networks Oy Solution to enforce time and usage threshold for monitoring
US9654650B1 (en) * 2014-03-05 2017-05-16 Sprint Communications Company L.P. Data quotas based on online charging server load
WO2015161361A1 (en) * 2014-04-25 2015-10-29 Redknee Inc. Method, system and apparatus for adaptive quota determination for shared resources
CN104469728A (zh) 2014-11-17 2015-03-25 华为技术有限公司 一种计费方法、计费设备和计费系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011157123A2 (zh) * 2011-05-31 2011-12-22 华为技术有限公司 在线计费方法、在线计费系统及策略和计费规则功能实体
CN102308604A (zh) * 2011-07-07 2012-01-04 华为技术有限公司 集群在线计费方法和设备
CN105515793A (zh) * 2014-09-23 2016-04-20 中国电信股份有限公司 在线计费处理方法和系统、Openflow控制器和Openflow交换机

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3554004A4

Also Published As

Publication number Publication date
EP3554004A1 (en) 2019-10-16
US11330114B2 (en) 2022-05-10
EP3554004A4 (en) 2019-12-11
CN108259196B (zh) 2023-06-06
US20190320073A1 (en) 2019-10-17
EP4529095A2 (en) 2025-03-26
CN108259196A (zh) 2018-07-06
EP4529095A3 (en) 2025-06-11

Similar Documents

Publication Publication Date Title
CN110971419B (zh) 一种计费会话管理方法、装置
CN110519069B (zh) 一种计费方法及设备
CN103765814B (zh) 计费控制的方法及计费触发装置、在线计费系统
US10609225B2 (en) Charging method, apparatus, and system
WO2019001109A1 (zh) 一种计费方法及设备
CN106301805B (zh) 一种策略和计费执行功能装置、在线计费装置及在线计费方法
WO2018120959A1 (zh) 一种配额管理方法及装置
CN105101136A (zh) 一种数据业务的计费方法、装置及系统
WO2012149853A1 (zh) 计费方法、计费设备、计费系统和认证设备
WO2016107177A1 (zh) 一种计费方法、装置及系统
CN106714129A (zh) 漫游计费方法、相关装置及在线计费系统
CN104702529A (zh) 控制业务带宽的方法、系统和设备
WO2017161522A1 (zh) 流量使用量统计方法、装置及系统
CN1848900B (zh) 一种预付费的计费方法
CN110324802A (zh) 一种流量计费方法及mme
CN103945355B (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: 17888079

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017888079

Country of ref document: EP

Effective date: 20190710

WWW Wipo information: withdrawn in national office

Ref document number: 2017888079

Country of ref document: EP