WO2016192441A1 - 扣费方法及系统 - Google Patents
扣费方法及系统 Download PDFInfo
- Publication number
- WO2016192441A1 WO2016192441A1 PCT/CN2016/076905 CN2016076905W WO2016192441A1 WO 2016192441 A1 WO2016192441 A1 WO 2016192441A1 CN 2016076905 W CN2016076905 W CN 2016076905W WO 2016192441 A1 WO2016192441 A1 WO 2016192441A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- deduction
- task
- party application
- information
- billing
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
Definitions
- the present invention relates to the field of communications, and in particular to a method and system for charging.
- the billing capability is open, which is one of the many open capabilities.
- the International Standards Organization's 3rd Generation Partnership Project (3GPP) released the payment capability in 2007 (6th edition). ).
- the main open logic of the opening of the charging capability is that the third-party application invokes the charging function once, and the open application programming interface (API) performs a charging operation on a user account, that is, The third party application actively controls the triggering of the charging operation.
- API application programming interface
- the third-party application has a single open billing capability and complicated operation, and no effective solution has been proposed yet.
- the present invention provides a method and system for deducting fees, so as to at least solve the problem that the charging capability of the third-party application in the related art is open and complicated.
- a method for debiting including:
- creating one or more debiting tasks based on the information includes:
- one or more deduction tasks are created based on the information.
- receiving a task query request of the third-party application receiving a task query request of the third-party application
- the method further includes:
- the method further includes:
- the method further includes:
- the result notification address of the third-party application setting is received, and the charging operation result corresponding to the deduction task is sent to the third-party application corresponding to the result notification address in real time.
- the information for creating a chargeback task for a third party application comprises at least one of the following:
- Third-party application identity authentication information billing destination number information, task life cycle, deduction cycle, billing and replenishment period, normal billing amount, replenishment billing amount, and billing result notification address.
- a method for deduction including:
- the third-party application is configured to create information for one or more debit tasks
- the third party application sends the information to the debit system.
- the information configured to create one or more debit tasks includes at least one of the following:
- Third-party application identity authentication information billing destination number information, task life cycle, deduction cycle, billing and replenishment period, normal billing amount, replenishment billing amount, and billing result notification address.
- a deduction system including:
- a first receiving module configured to receive information for creating a deduction task for a third-party application
- Creating a module configured to create one or more deduction tasks based on the information
- the charging module is configured to traverse the deduction task, and when there is a deduction operation in the deduction task, initiate a charging operation corresponding to the deduction operation to the camping system.
- system further comprises:
- the authentication module is configured to authenticate the identity authentication information of the third-party application, and confirm whether the third-party application is legal;
- the creation module is further configured to create one or more deduction tasks based on the information if the third party application is legitimate.
- system further comprises:
- a second receiving module configured to receive a task query request of the third-party application
- the query module is configured to send the charging operation result corresponding to the deduction task to the third-party application, triggered by the task query request.
- system further comprises:
- a maintenance module configured to receive a maintenance request of the third-party application, and modify the deduction task or terminate the deduction task triggered by the maintenance request.
- system further comprises:
- the replenishment module is configured to initiate a replenishment charging operation to the camping system when the charging operation corresponding to the deduction task fails.
- system further comprises:
- the notification module is configured to receive the result notification address set by the third-party application, and send the charging operation result corresponding to the deduction task to the third-party application corresponding to the result notification address in real time.
- the information for creating a chargeback task for a third party application comprises at least one of the following:
- Third-party application identity authentication information billing destination number information, task life cycle, deduction cycle, billing and replenishment period, normal billing amount, replenishment billing amount, and billing result notification address.
- a deduction system including:
- a configuration module configured to configure, for a third-party application, information for creating one or more deduction tasks
- a sending module configured to send the information to the debit system by the third party application.
- the information configured to create one or more debit tasks includes at least one of the following:
- Third-party application identity authentication information billing destination number information, task life cycle, deduction cycle, billing and replenishment period, normal billing amount, replenishment billing amount, and billing result notification address.
- the billing system by receiving information for creating a deduction task for creating a third-party application, one or more deduction tasks are created according to the information, and the deduction task is traversed, and when there is a deduction operation in the deduction task,
- the billing system initiates the billing operation corresponding to the deduction operation, which solves the problem that the third-party application billing capability is open and simple, and the operation is complicated, and provides more diverse billing capabilities.
- FIG. 1 is a flow chart 1 of a method for deduction according to an embodiment of the present invention.
- FIG. 3 is a structural block diagram 1 of a deduction system according to an embodiment of the present invention.
- FIG. 4 is a structural block diagram 2 of a deduction system according to an embodiment of the present invention.
- FIG. 5 is a schematic structural diagram of a deducting task capability open system according to a preferred embodiment of the present invention.
- FIG. 6 is a schematic diagram of a business process structure of an open fee task capability open system according to a preferred embodiment of the present invention.
- FIG. 1 is a flowchart 1 of a deduction method according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:
- Step S102 receiving information for creating a deduction task of a third-party application
- Step S104 creating one or more deduction tasks according to the information
- Step S106 traversing the deduction task, and when there is a deduction operation in the deduction task, initiating a charging operation corresponding to the deduction operation to the camping system.
- receiving information for creating a deduction task of the third-party application creating one or more deduction tasks according to the information, traversing the deduction task, and when there is a deduction operation in the deduction task, to the camp
- the system initiates the charging operation corresponding to the charging operation, and implements the information that the third-party application can set multiple charging tasks.
- the charging system completes multiple charging and complex charging, and solves the third-party application charging capability. Open single, complex operation issues, providing more diverse billing capabilities.
- the identity authentication information of the third-party application is authenticated to confirm whether the third-party application is legal. If the third-party application is legal, one or more deduction tasks are created according to the information.
- the query request, the maintenance request, the notification request, the statistical request, and the like of the third-party application may be responded to, and the deduction system feeds the corresponding request information to the third-party application, for example, may receive the third-party application.
- the task query request, the trigger operation result corresponding to the chargeback task is sent to the third-party application, triggered by the task query request.
- the maintenance request of the third-party application may be received, and the deduction task is terminated or the deduction task is terminated under the trigger of the maintenance request.
- a third-party application corresponding to the result notification address is sent.
- the replenishment charging operation is initiated to the camping system.
- the charging operation of the charging task succeeds or eventually fails.
- the information for creating a deduction task of the third-party application may include at least one of the following: third-party application identity authentication information, charging destination number information, task life cycle, deduction cycle, and charging and replenishing Period, normal billing amount, replenishment billing amount, billing result notification address.
- FIG. 2 is a flowchart 2 of a deduction method according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:
- Step S202 The third-party application configures information for creating one or more deduction tasks
- Step S204 the third party application sends the information to the debit system.
- the third-party application configures information for creating one or more deduction tasks, and the third-party application sends the information to the deduction system, and the deduction system traverses the deduction task, and the deduction task has a deduction.
- the billing operation corresponding to the deduction operation is initiated to the camping system, and the third party application can set information of multiple deduction tasks, and the deduction system completes multiple billing and complicated billing, and solves the problem.
- the third-party application billing capability is open and single, and the operation is complicated, which provides more diverse billing capabilities.
- a deduction system is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again.
- the term "module” may implement a combination of software and/or hardware of a predetermined function.
- the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
- FIG. 3 is a structural block diagram 1 of a deduction system according to an embodiment of the present invention. As shown in FIG. 3, the device includes
- the first receiving module 32 is configured to receive information for creating a deduction task of the third-party application
- a creating module 34 configured to create one or more deduction tasks based on the information
- the charging module 36 is configured to traverse the deduction task, and when there is a deduction operation in the deduction task, initiate a charging operation corresponding to the deduction operation to the camping system.
- the system initiates the charging operation corresponding to the charging operation, and implements the information that the third-party application can set multiple charging tasks.
- the charging system completes multiple charging and complex charging, and solves the third-party application charging capability. Open single, complex operation issues, providing more diverse billing capabilities.
- system further includes:
- the authentication module is configured to authenticate the identity authentication information of the third-party application, and confirm whether the third-party application is legal;
- the creation module 34 is further configured to create one or more debit tasks based on the information if the third party application is legitimate.
- system further includes:
- a second receiving module configured to receive a task query request of the third-party application
- the query module is configured to send the charging operation result corresponding to the deduction task to the third-party application under the trigger of the task query request.
- system further includes:
- the maintenance module is configured to receive the maintenance request of the third-party application, and modify the deduction task or terminate the deduction task triggered by the maintenance request.
- the replenishment module is configured to initiate a replenishment charging operation to the camping system when the charging operation corresponding to the deduction task fails.
- the notification module is configured to receive the result notification address set by the third-party application, and send the charging operation result corresponding to the deduction task to the third-party application corresponding to the result notification address in real time.
- FIG. 4 is a structural block diagram 2 of a deduction system according to an embodiment of the present invention. As shown in FIG. 4, the device includes
- the configuration module 42 is configured to configure, for the third party application, information for creating one or more deduction tasks
- the sending module 44 is configured to send the information to the debit system by the third party application.
- the third-party application is configured to create information of one or more deduction tasks, and the third-party application sends the information to the deduction system, and the deduction system traverses the deduction task, and the deduction task has a deduction
- the billing operation corresponding to the deduction operation is initiated to the camping system, and the third party application can set information of multiple deduction tasks, and the deduction system completes multiple billing and complicated billing, and solves the problem.
- the third-party application billing capability is open and single, and the operation is complicated, which provides more diverse billing capabilities.
- the preferred embodiment provides a deductible task capability open solution and system.
- the preferred embodiment allows the third-party application to establish a deduction task through the deductible task capability open interface; after the deduction task is established, the system provided by the preferred embodiment performs the deduction operation on the account system according to the task requirement;
- the system provided by the example can timely notify the third-party application of the execution of the deduction task, so that the third-party application can grasp the detailed information of the execution of the deduction task.
- the preferred embodiment of the present invention also illustrates the system architecture that implements the solution.
- the preferred embodiment provides an open charge task capability.
- the deduction task is open and mainly includes the following functions:
- the third-party application can create one or more deduction tasks in the system of the present invention, query the deduction task information, query the detailed result of the charging operation, modify or end the deduction task, and receive the notification of the charging operation result.
- the deduction task of the system of the preferred embodiment provides two functions of normal charging and replenishing.
- Normal billing refers to performing multiple billing operations in accordance with the set billing interval during the life of the task.
- the replenishment means that when a certain charging operation fails in normal charging (if the account balance is insufficient), the charging attempt is performed according to the set amount during the set replenishment period, and the deduction should be deducted after the completion of the normal charging. The amount or final billing failed.
- the deduction task can continue to be performed normally; when the amount deductible in normal billing is not completed in the replenishment period, the deduction task will be terminated.
- the system of the preferred embodiment can automatically complete the charging operation to the camping system according to the execution of the deduction task.
- the system of the preferred embodiment provides a statistical analysis function, and can actively notify the third-party application or the third-party application to query the charging operation result.
- the preferred embodiment system includes an API interface module, a task management module, a chargeback module, and a statistical analysis module.
- FIG. 5 is a schematic structural diagram of a system for unlocking a task capability according to a preferred embodiment of the present invention. As shown in FIG. 5, the meanings of the modules in the system of the preferred embodiment are as follows:
- the API interface module 501 provides an open API interface to a third-party application, including a task creation interface, a task query interface, a task maintenance interface, a query detail interface, and a charge notification interface.
- the task management module 502 is configured to manage the deduction task created by the third-party application, and notify the deduction module to perform the corresponding charging operation according to the task requirement.
- the deduction module 503 interacts with the camping system to complete a specific charging operation according to the notification of the task management module 502; and feeds the charging result to the statistical analysis module 504.
- the statistical analysis module 504 is configured to record the detailed charging operation result, notify the third-party application through the API interface module 501, and generate a statistical analysis report.
- the task interface in the API interface module 501 is responsible for completing the creation of the deduction task; the main information of the interface includes:
- the third-party application authentication information is used to identify whether the third-party application is legal.
- Billing destination number information that is, the number that is billed in the billing system.
- the task life cycle including the task start time and end time.
- the deduction cycle which is the cycle time interval for multiple billings during the life of the task.
- the charging and replenishing period is used to use the replenishment period after the failure of the normal charging operation to attempt to re-account until the charging succeeds or eventually fails.
- the normal billing amount that is, the amount of billing operation performed each time in a normal recurring billing operation.
- the amount of the billing charge is the amount of the attempted billing operation after entering the billing period; the billing amount is one or a group of amount figures.
- the billing result notification address is used for the notification address of the third party application that wants to passively receive the result of the billing operation.
- the business process of the system of the present invention is mainly divided into three parts:
- the creation, query and maintenance of the deduction task further include:
- Step 1 The third-party application invokes the creation of the task interface, and initiates a deduction task creation operation to the system of the present invention.
- Step 2 After completing the identity authentication check, the system of the present invention creates a required deduction task for the third-party application.
- Step 3 The third-party application invokes the task query interface, and can query one or more deduction task information that has been created in the system of the present invention.
- Step 4 The third-party application invokes the task maintenance interface to modify a deduction task (such as modifying the life cycle, deduction cycle, billing amount, etc.) or terminating the deduction task.
- a deduction task such as modifying the life cycle, deduction cycle, billing amount, etc.
- the automatic execution and automatic billing of the deduction task further includes:
- Step 1 The system of the present invention automatically scans the deduction task.
- Step 2 When it is found that there is a charging operation that needs to be performed, the system of the present invention initiates a charging operation to the camping system through the deduction module, and records the charging operation result in detail.
- Step 3 When the normal charging fails, the system of the present invention automatically triggers the replenishing operation, and continues to initiate the replenishment charging operation by the deduction module to the billing system, and records the charging operation result in detail.
- the query, notification, and statistical analysis of the billing result further include:
- Step 1 The third-party application may choose to invoke the query detail interface to obtain the detailed charging operation result of the deduction task execution.
- Step 2 The third-party application may also choose to provide a result notification address, and the system of the present invention notifies the third-party application of the detailed charging operation result in real time through the deduction notification interface.
- Step 3 The system of the present invention provides a statistical analysis function for use in reconciliation, auditing, and the like.
- FIG. 6 is a schematic diagram of a business process structure of a deductible task capability open system according to a preferred embodiment of the present invention, as shown in FIG. 6, illustrating a deduction task operation capability opening implementation step case 1, case 2, and case 3.
- Case 1 The life cycle of the typical deduction task is one year, and the deduction period is January, that is, the natural monthly deduction is charged during the life cycle, and the one-week replenishment period is provided.
- the specific implementation steps of the typical deduction task are as follows:
- Step S601 The third-party application invokes the task creation interface to request to create a deduction task; the request information includes third-party application identity authentication information, a billing destination number, and a task life cycle (January 1, 2016 to December 31, 2016). Deduction cycle (January), billing and replenishment period (1 week), normal billing amount 10 yuan, replenishment billing amount (5 yuan, 2 yuan, 1 yuan), billing result notification address (xx@ Yy.com).
- Step S602 After completing the third-party application identity verification check and the request parameter plausibility check, the API interface module notifies the task management module to establish a chargeback task.
- Step S603 when the system time running reaches the start time of the deduction task (January 1, 2016), the task management module triggers the deduction module. .
- step S604 the deduction module completes a normal charging operation (deducting 10 yuan) according to the requirement of the deduction task and the billing system.
- Step S605 the debiting module performs the charging operation successfully, and records the detailed charging result in the statistical analysis module.
- Step S606 The statistical analysis module notifies the third-party application of the charging operation result in real time via the API interface module.
- the task management module triggers a deduction module to complete the normal charging operation every one month (for example, February 1, March 1, etc.) according to the requirement of the deduction task. That is, steps S603 to S606 are completed.
- the result of the normal charging operation is a failure (such as June 1st), and the task management module finds that the deduction task has a replenishment period, and is in the replenishment period (June 1 to 6).
- the replenishment operation is performed multiple times using the replenishment amount, that is, the deduction of the deduction module by using the 5 yuan, 2 yuan, and 1 yuan multiple times in sequence (steps S603 to S606) until the replenishment period
- the normal charge amount (10 yuan) is deducted or until the end of the replenishment period.
- the deduction task can continue to be executed, that is, the next round of the deduction period (July 1)
- the task management module ends the deduction.
- the task also notifies the third party application via the API interface module.
- the third-party application may invoke the task query interface to query the deduction task information (such as setup time, life cycle, cycle period, replenishment period, amount, etc.).
- deduction task information such as setup time, life cycle, cycle period, replenishment period, amount, etc.
- the third-party application may invoke the query detail interface to query the details of the charging operation that has occurred; for example, the query detail interface is invoked on August 10, 2016, and can be queried from January 1 to August 1. Details of each billing operation (including normal billing and replenishment fees) that has occurred between days.
- the third-party application may invoke the task maintenance interface to modify or terminate the deduction task; for example, the task maintenance interface is invoked on September 20, 2016, and the deduction task is terminated, and no further October occurs. 1 day deduction operation.
- Case 2 The information of the typical deduction task is basically the same as Case 1, but there is no set-up period or replenishment amount, that is, no replenishment operation is required.
- the specific implementation steps S601-S606 of the typical deduction task are the same as the case 1 when the charging operation is successfully completed. Only when a normal billing operation fails, the task management module directly terminates the chargeback task and notifies the third-party application via the API interface module.
- Case 3 The typical deduction task information is a billing operation, that is, the start time in the life cycle is equal to the end time, or the deduction period is equal to the life cycle length.
- the specific implementation steps S601-S606 of the typical deduction task are exactly the same as the case 1, except that S603-S606 are only executed once.
- the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
- the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
- the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of various embodiments of the present invention.
- Embodiments of the present invention also provide a storage medium.
- the foregoing storage medium may be configured to store program code for performing the method steps of the above embodiment:
- the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
- ROM Read-Only Memory
- RAM Random Access Memory
- a mobile hard disk e.g., a hard disk
- magnetic memory e.g., a hard disk
- the processor performs the method steps of the foregoing embodiments according to the stored program code in the storage medium.
- modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
- the information about the deduction task for creating a third-party application is received, and one or more deduction tasks are created according to the information, and the deduction task is traversed, and the deduction task exists in the deduction task.
- the billing operation corresponding to the chargeback operation is initiated to the camping system, which solves the problem that the third-party application billing capability is open and simple, and the operation is complicated, and provides more diverse billing capabilities.
Abstract
本发明提供了一种扣费方法及系统，其中，该方法接收用于创建第三方应用的扣费任务的信息，根据该信息创建一个或多个扣费任务，遍历该扣费任务，在该扣费任务中存在扣费操作时，向营帐系统发起与该扣费操作对应的计费操作，解决了第三方应用计费能力开放单一，操作复杂的问题，提供了更加多样的计费能力开放。
Description
本发明涉及通信领域，具体而言，涉及一种扣费方法及系统。
目前，运营商的3G、4G技术正在逐渐快速发展。电信能力开放已经成为众多运营商进行新商业模式转型的重要途径。
计费能力开放，是众多能力开放中的一种，国际标准组织的第三代合作伙伴计划(3rd Generation Partnership Project，简称为3GPP)于2007年发布了计费(Payment)能力开放(第6版)。在相关技术中，计费能力开放的主要开放逻辑是由第三方应用调用一次计费能力，开放应用程序编程接口(Application Programming Interface，简称为API)对某个用户账户完成一次计费操作，即由第三方应用主动控制触发计费操作。当需要完成多次计费、完成复杂计费时，都必须由第三方应用自行完成控制操作。
针对相关技术中，第三方应用计费能力开放单一，操作复杂的问题，目前尚未提出有效的解决方案。
发明内容
本发明提供了一种扣费方法及系统，以至少解决相关技术中第三方应用计费能力开放单一，操作复杂的问题。
根据本发明的一个实施例，提供了一种扣费方法，包括：
接收用于创建第三方应用的扣费任务的信息；
根据所述信息创建一个或多个扣费任务；
遍历所述扣费任务，在所述扣费任务中存在扣费操作时，向营帐系统发起与所述扣费操作对应的计费操作。
在本发明的实施例中，根据信息创建一个或多个扣费任务包括：
对所述第三方应用的身份认账信息进行鉴权，确认所述第三方应用是否合法；
在所述第三方应用合法的情况下，根据所述信息创建一个或多个扣费任务。
在本发明的实施例中，接收所述第三方应用的任务查询请求；
在所述任务查询请求的触发下，将所述扣费任务对应的计费操作结果发送给所述第三方
应用。
在本发明的实施例中，根据信息创建一个或多个扣费任务之后，所述方法还包括：
接收所述第三方应用的维护请求，在所述维护请求的触发下，修改所述扣费任务或者终止所述扣费任务。
在本发明的实施例中，所述方法还包括：
在与所述扣费任务对应的计费操作失败时，向营帐系统发起补扣计费操作。
在本发明的实施例中，所述方法还包括：
接收所述第三方应用设置的结果通知地址，将所述扣费任务对应的计费操作结果实时发送给与所述结果通知地址对应的第三方应用。
在本发明的实施例中，创建第三方应用的扣费任务的所述信息包括以下至少之一：
第三方应用身份认证信息，计费目的号码信息，任务生命周期，扣费循环周期，计费补扣期，正常计费金额，补扣计费金额，计费结果通知地址。
根据本发明的另一个实施例，还提供了一种扣费方法，包括：
第三方应用配置用于创建一个或多个扣费任务的信息；
所述第三方应用向扣费系统发送所述信息。
在本发明的实施例中，配置用于创建一个或多个扣费任务的所述信息包括以下至少之一：
第三方应用身份认证信息，计费目的号码信息，任务生命周期，扣费循环周期，计费补扣期，正常计费金额，补扣计费金额，计费结果通知地址。
根据本发明的另一个实施例，还提供了一种扣费系统，包括：
第一接收模块，设置为接收用于创建第三方应用的扣费任务的信息；
创建模块，设置为根据所述信息创建一个或多个扣费任务；
计费模块，设置为遍历所述扣费任务，在所述扣费任务中存在扣费操作时，向营帐系统发起与所述扣费操作对应的计费操作。
在本发明的实施例中，所述系统还包括：
鉴权模块，设置为对所述第三方应用的身份认账信息进行鉴权，确认所述第三方应用是否合法；
所述创建模块还设置为在所述第三方应用合法的情况下，根据所述信息创建一个或多个扣费任务。
在本发明的实施例中，所述系统还包括：
第二接收模块，设置为接收所述第三方应用的任务查询请求；
查询模块，设置为在所述任务查询请求的触发下，将所述扣费任务对应的计费操作结果发送给所述第三方应用。
在本发明的实施例中，所述系统还包括：
维护模块，设置为接收所述第三方应用的维护请求，在所述维护请求的触发下，修改所述扣费任务或者终止所述扣费任务。
在本发明的实施例中，所述系统还包括：
补扣模块，设置为在与所述扣费任务对应的计费操作失败时，向营帐系统发起补扣计费操作。
在本发明的实施例中，所述系统还包括：
通知模块，设置为接收所述第三方应用设置的结果通知地址，将所述扣费任务对应的计费操作结果实时发送给与所述结果通知地址对应的第三方应用。
在本发明的实施例中，创建第三方应用的扣费任务的所述信息包括以下至少之一：
第三方应用身份认证信息，计费目的号码信息，任务生命周期，扣费循环周期，计费补扣期，正常计费金额，补扣计费金额，计费结果通知地址。
根据本发明的另一个实施例，还提供了一种扣费系统，包括：
配置模块，设置为第三方应用配置用于创建一个或多个扣费任务的信息；
发送模块，设置为所述第三方应用向扣费系统发送所述信息。
在本发明的实施例中，配置用于创建一个或多个扣费任务的所述信息包括以下至少之一：
第三方应用身份认证信息，计费目的号码信息，任务生命周期，扣费循环周期，计费补扣期，正常计费金额，补扣计费金额，计费结果通知地址。
通过本发明，采用接收用于创建第三方应用的扣费任务的信息，根据该信息创建一个或多个扣费任务，遍历该扣费任务，在该扣费任务中存在扣费操作时，向营帐系统发起与该扣费操作对应的计费操作，解决了第三方应用计费能力开放单一，操作复杂的问题，提供了更加多样的计费能力开放。
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的一种扣费方法的流程图一；
图2是根据本发明实施例的一种扣费方法的流程图二；
图3是根据本发明实施例的一种扣费系统的结构框图一；
图4是根据本发明实施例的一种扣费系统的结构框图二；
图5是根据本发明优选实施例的扣费任务能力开放系统的结构示意图；
图6是根据本发明优选实施例的扣费任务能力开放系统的业务流程结构示意图。
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种扣费方法，图1是根据本发明实施例的一种扣费方法的流程图一，如图1所示，该流程包括如下步骤：
步骤S102，接收用于创建第三方应用的扣费任务的信息；
步骤S104，根据该信息创建一个或多个扣费任务；
步骤S106，遍历该扣费任务，在该扣费任务中存在扣费操作时，向营帐系统发起与该扣费操作对应的计费操作。
通过上述步骤，接收用于创建第三方应用的扣费任务的信息，根据该信息创建一个或多个扣费任务，遍历该扣费任务，在该扣费任务中存在扣费操作时，向营帐系统发起与该扣费操作对应的计费操作，实现了第三方应用可以设置多个扣费任务的信息，扣费系统完成多次计费和复杂的计费，解决了第三方应用计费能力开放单一，操作复杂的问题，提供了更加多样的计费能力开放。
在本实施例中，对该第三方应用的身份认账信息进行鉴权，确认该第三方应用是否合法，在该第三方应用合法的情况下，根据该信息创建一个或多个扣费任务。
在本实施例中，可以响应第三方应用的查询请求，维护请求，通知请求，统计请求等等，扣费系统将对应的请求信息反馈给该第三方应用，例如，可以接收该第三方应用的任务查询请求，在该任务查询请求的触发下，将该扣费任务对应的计费操作结果发送给该第三方应用。可以接收该第三方应用的维护请求，在该维护请求的触发下，修改该扣费任务或者终止该扣费任务。
可以接收该第三方应用设置的结果通知地址，将该扣费任务对应的计费操作结果实时发
送给与该结果通知地址对应的第三方应用。
在本实施例中，在与该扣费任务对应的计费操作失败时，向营帐系统发起补扣计费操作。从而将该计费任务的计费操作成功或者最终失败。
在本实施例中，创建第三方应用的扣费任务的该信息可以包括以下至少之一：第三方应用身份认证信息，计费目的号码信息，任务生命周期，扣费循环周期，计费补扣期，正常计费金额，补扣计费金额，计费结果通知地址。
在本实施例中提供了一种扣费方法，图2是根据本发明实施例的一种扣费方法的流程图二，如图2所示，该流程包括如下步骤：
步骤S202，第三方应用配置用于创建一个或多个扣费任务的信息；
步骤S204，该第三方应用向扣费系统发送该信息。
通过上述步骤，第三方应用配置用于创建一个或多个扣费任务的信息，该第三方应用向扣费系统发送该信息，扣费系统遍历该扣费任务，在该扣费任务中存在扣费操作时，向营帐系统发起与该扣费操作对应的计费操作，实现了第三方应用可以设置多个扣费任务的信息，扣费系统完成多次计费和复杂的计费，解决了第三方应用计费能力开放单一，操作复杂的问题，提供了更加多样的计费能力开放。
在本实施例中还提供了一种扣费系统，该系统用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的一种扣费系统的结构框图一，如图3所示，该装置包括
第一接收模块32，设置为接收用于创建第三方应用的扣费任务的信息；
创建模块34，设置为根据该信息创建一个或多个扣费任务；
计费模块36，设置为遍历该扣费任务，在该扣费任务中存在扣费操作时，向营帐系统发起与该扣费操作对应的计费操作。
通过上述装置，接收用于创建第三方应用的扣费任务的信息，根据该信息创建一个或多个扣费任务，遍历该扣费任务，在该扣费任务中存在扣费操作时，向营帐系统发起与该扣费操作对应的计费操作，实现了第三方应用可以设置多个扣费任务的信息，扣费系统完成多次计费和复杂的计费，解决了第三方应用计费能力开放单一，操作复杂的问题，提供了更加多样的计费能力开放。
在本实施例中，该系统还包括：
鉴权模块，设置为对该第三方应用的身份认账信息进行鉴权，确认该第三方应用是否合法；
该创建模块34还设置为在该第三方应用合法的情况下，根据该信息创建一个或多个扣费任务。
在本实施例中，该系统还包括：
第二接收模块，设置为接收该第三方应用的任务查询请求；
查询模块，设置为在该任务查询请求的触发下，将该扣费任务对应的计费操作结果发送给该第三方应用。
在本实施例中，该系统还包括：
维护模块，设置为接收该第三方应用的维护请求，在该维护请求的触发下，修改该扣费任务或者终止该扣费任务。
补扣模块，设置为在与该扣费任务对应的计费操作失败时，向营帐系统发起补扣计费操作。
通知模块，设置为接收该第三方应用设置的结果通知地址，将该扣费任务对应的计费操作结果实时发送给与该结果通知地址对应的第三方应用。
图4是根据本发明实施例的一种扣费系统的结构框图二，如图4所示，该装置包括
配置模块42，设置为第三方应用配置用于创建一个或多个扣费任务的信息；
发送模块44，设置为该第三方应用向扣费系统发送该信息。
通过上述系统，第三方应用配置用于创建一个或多个扣费任务的信息，该第三方应用向扣费系统发送该信息，扣费系统遍历该扣费任务，在该扣费任务中存在扣费操作时，向营帐系统发起与该扣费操作对应的计费操作，实现了第三方应用可以设置多个扣费任务的信息，扣费系统完成多次计费和复杂的计费，解决了第三方应用计费能力开放单一，操作复杂的问题，提供了更加多样的计费能力开放。
下面结合优选实施例和实施方式对本发明进行详细说明。
本优选实施例提供一种扣费任务能力开放解决方案及系统。本优选实施例允许第三方应用通过扣费任务能力开放接口建立扣费任务；当扣费任务建立后，由本优选实施例所提供的系统按任务要求自行到营帐系统进行扣费操作；本优选实施例所提供的系统能够及时将扣费任务的执行情况通知给第三方应用，使第三方应用能够掌握扣费任务执行的详细信息。本本优选实施例同时说明了实现该解决方案的系统架构。
本优选实施例提供一种扣费任务能力开放。该扣费任务能力开放，主要包含如下功能：
为第三方应用提供一组API接口。通过API接口，第三方应用可以在本发明系统中创建一个或多个扣费任务，查询扣费任务信息，查询计费操作详细结果，修改或结束扣费任务，接收计费操作结果通知。
本优选实施例系统的扣费任务，提供正常计费和补扣两种功能。
正常计费，是指在任务生命周期内按照设定的计费间隔时间进行循环多次计费操作。
补扣，是指在正常计费中的某次计费操作失败时(如账户余额不足)在设定的补扣期内按照设定的金额进行计费尝试，直至完成正常计费中应扣的金额或最终计费失败。
当补扣期中完成了正常计费中应扣的金额时，扣费任务可以继续正常执行；当补扣期中未能完成正常计费中应扣的金额时，扣费任务将被终止。
本优选实施例系统能够根据扣费任务的执行情况，自动到营帐系统完成计费操作。
本优选实施例系统提供统计分析功能，能够将计费操作结果主动通知给第三方应用或供第三方应用来查询。
为实现上述目的，本优选实施例系统包括API接口模块、任务管理模块、扣费模块、统计分析模块。
图5是根据本发明优选实施例的扣费任务能力开放系统的结构示意图，如图5所示，本优选实施例系统中的各模块含义如下：
API接口模块501：提供扣费任务能力开放的API接口给第三方应用，具体包括任务创建接口、任务查询接口、任务维护接口、查询详情接口、扣费通知接口。
任务管理模块502：设置为管理第三方应用创建的扣费任务，并根据任务要求通知103扣费模块执行相应的计费操作。
扣费模块503：根据任务管理模块502的通知，与营帐系统交互完成具体的计费操作；并将计费结果反馈给统计分析模块504。
统计分析模块504：负责记录详细计费操作结果，将计费操作结果经过API接口模块501通知给第三方应用；并生成统计分析报表。
所述API接口模块501中的创建任务接口，负责完成扣费任务的创建；该接口的主要信息包括：
第三方应用身份认证信息，用于鉴别第三方应用是否合法。
计费目的号码信息，即对营帐系统中进行计费的号码。
任务生命周期，包含任务开始时间和结束时间。
扣费循环周期，即在任务生命周期内进行多次计费的循环时间间隔。
计费补扣期，用于在正常计费操作失败后使用补扣期来尝试重新计费直至计费成功或最终失败。
正常计费金额，即在正常的循环计费操作中每次进行计费操作的金额。
补扣计费金额，即进入计费补扣期后进行尝试计费操作的金额；补扣计费金额为一个或一组金额数字。
计费结果通知地址，用于第三方应用希望被动接收计费操作结果的通知地址。
本发明系统的业务流程，主要分为三个部分：
扣费任务的创建、查询、维护。
扣费任务的自动执行、自动计费。
计费结果的查询、通知、统计分析。
扣费任务的创建、查询、维护，进一步包括：
步骤1、第三方应用调用创建任务接口，向本发明系统发起扣费任务创建操作。
步骤2、本发明系统完成身份认证检查后，为第三方应用创建所需的扣费任务。
步骤3、第三方应用调用任务查询接口，可以查询出在本发明系统中已经创建的一个或多个扣费任务信息。
步骤4、第三方应用调用任务维护接口，对某个扣费任务进行修改(如修改生命周期、扣费循环周期、计费金额等)或终止扣费任务。
扣费任务的自动执行、自动计费，进一步包括：
步骤1、本发明系统自动扫描扣费任务。
步骤2、当发现有需要执行的计费操作时，本发明系统通过扣费模块对营帐系统发起计费操作，并详细记录计费操作结果。
步骤3、当正常计费失败时，本发明系统自动触发补扣操作，继续由扣费模块对营帐系统发起补扣计费操作，并详细记录计费操作结果。
计费结果的查询、通知、统计分析，进一步包括：
步骤1、第三方应用可以选择调用查询详情接口，获得扣费任务执行的详细计费操作结果。
步骤2、第三方应用也可以选择提供一个结果通知地址，由本发明系统通过扣费通知接口将详细计费操作结果实时通知给第三方应用。
步骤3、本发明系统提供统计分析功能，供对账、查账等使用。
图6是根据本发明优选实施例的扣费任务能力开放系统的业务流程结构示意图，如图6所示，说明扣费任务能力开放实施步骤案例1、案例2、案例3。
案例1：该典型扣费任务生命周期为一年，扣费循环期为1月，即生命周期内按自然月扣费，并提供1周的补扣期。该典型扣费任务的具体实施步骤如下：
步骤S601，第三方应用调用任务创建接口请求创建扣费任务；请求信息包括第三方应用身份认证信息，计费目的号码，任务生命周期(2016年1月1日～2016年12月31日)，扣费循环周期(1月)，计费补扣期(1周)，正常计费金额10元，补扣计费金额(5元、2元、1元)，计费结果通知地址(xx@yy.com)。
步骤S602，API接口模块完成第三方应用身份认证检查及请求参数合理性检查后，通知任务管理模块建立扣费任务。
步骤S603，当系统时间运行达到该扣费任务的开始时间时(2016年1月1日)，任务管理模块触发扣费模块。。
步骤S604，扣费模块根据扣费任务的要求与到营帐系统完成一次正常计费操作(扣除10元)。
步骤S605，扣费模块执行计费操作成功，将详细计费结果记录在统计分析模块。
步骤S606，统计分析模块经由API接口模块将计费操作结果实时通知给第三方应用。
在本发明的实施例中，步骤S603任务管理模块根据该扣费任务的要求每隔1个月(例如2月1日，3月1日等)均触发一次扣费模块完成正常计费操作，即完成步骤S603～S606。
在本发明的实施例中，某次(如6月1日)正常计费操作结果为失败，任务管理模块发现该扣费任务有补扣期，则在补扣期(6月1日～6月7日)内使用补扣金额多次进行尝试补扣操作，即依次多次使用5元、2元、1元通知扣费模块进行计费操作(步骤S603～S606)，直至在补扣期内扣满正常计费金额(10元)或直至补扣期结束。
在本发明的实施例中，如果补扣期内成功扣满本次应扣的正常计费金额时，则该扣费任务仍可继续执行，即到下一个循环扣费期(7月1日)时继续进行正常计费；如果补扣期结束时，仍未扣满本次应扣的正常计费金额(例如补扣成功金额为0元或7元)，则任务管理模块结束该扣费任务并经由API接口模块通知第三方应用。
在本发明的实施例中，第三方应用可以调用任务查询接口，查询该扣费任务信息(如建立时间、生命周期、循环周期、补扣期、金额等)。
在本发明的实施例中，第三方应用可以调用查询详情接口，查询已发生的计费操作详细情况；例如2016年8月10日调用查询详情接口，可以查询到1月1日到8月1日之间已发生的每次计费操作(含正常计费和补扣费)详情。
在本发明的实施例中，第三方应用可以调用任务维护接口，修改或终止扣费任务；例如，2016年9月20日调用任务维护接口，终止该扣费任务，则不会再发生10月1日的扣费操作。
案例2：该典型扣费任务信息基本同案例1，但没有设置补扣期、补扣金额，即不需要补扣操作。该典型扣费任务的具体实施步骤S601～S606，成功完成计费操作时步骤与案例1完全相同。仅当某次正常计费操作失败时，任务管理模块直接终止扣费任务并经由API接口模块通知给第三方应用。
案例3：按典型扣费任务信息为一次计费操作，即生命周期中开始时间等于结束时间，或扣费循环期等于生命周期长短。该典型扣费任务的具体实施步骤S601～S606与案例1完全相同，只是S603～S606仅会执行一次。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例该的方法。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行上述实施例方法步骤的程序代码：
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行上述实施例的方法步骤。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
基于本发明实施例提供的上述技术方案，接收用于创建第三方应用的扣费任务的信息，根据该信息创建一个或多个扣费任务，遍历该扣费任务，在该扣费任务中存在扣费操作时，向营帐系统发起与该扣费操作对应的计费操作，解决了第三方应用计费能力开放单一，操作复杂的问题，提供了更加多样的计费能力开放。
Claims (18)
- 一种扣费方法，包括：接收用于创建第三方应用的扣费任务的信息；根据所述信息创建一个或多个扣费任务；遍历所述扣费任务，在所述扣费任务中存在扣费操作时，向营帐系统发起与所述扣费操作对应的计费操作。
- 根据权利要求1所述的方法，其中，根据所述信息创建一个或多个扣费任务包括：对所述第三方应用的身份认账信息进行鉴权，确认所述第三方应用是否合法；在所述第三方应用合法的情况下，根据所述信息创建一个或多个扣费任务。
- 根据权利要求1所述的方法，其中，所述方法还包括：接收所述第三方应用的任务查询请求；在所述任务查询请求的触发下，将所述扣费任务对应的计费操作结果发送给所述第三方应用。
- 根据权利要求1所述的方法，其中，根据信息创建一个或多个扣费任务之后，所述方法还包括：接收所述第三方应用的维护请求，在所述维护请求的触发下，修改所述扣费任务或者终止所述扣费任务。
- 根据权利要求1所述的方法，其中，所述方法还包括：在与所述扣费任务对应的计费操作失败时，向营帐系统发起补扣计费操作。
- 根据权利要求1所述的方法，其中，所述方法还包括：接收所述第三方应用设置的结果通知地址，将所述扣费任务对应的计费操作结果实时发送给与所述结果通知地址对应的第三方应用。
- 根据权利要求1至6任一项所述的方法，其中，创建第三方应用的扣费任务的所述信息包括以下至少之一：第三方应用身份认证信息，计费目的号码信息，任务生命周期，扣费循环周期，计费补扣期，正常计费金额，补扣计费金额，计费结果通知地址。
- 一种扣费方法，包括：第三方应用配置用于创建一个或多个扣费任务的信息；所述第三方应用向扣费系统发送所述信息。
- 根据权利要求8所述的方法，其中，配置用于创建一个或多个扣费任务的所述信息包括以下至少之一：第三方应用身份认证信息，计费目的号码信息，任务生命周期，扣费循环周期，计费补扣期，正常计费金额，补扣计费金额，计费结果通知地址。
- 一种扣费系统，包括：第一接收模块，设置为接收用于创建第三方应用的扣费任务的信息；创建模块，设置为根据所述信息创建一个或多个扣费任务；计费模块，设置为遍历所述扣费任务，在所述扣费任务中存在扣费操作时，向营帐系统发起与所述扣费操作对应的计费操作。
- 根据权利要求10所述的系统，其中，所述系统还包括：鉴权模块，设置为对所述第三方应用的身份认账信息进行鉴权，确认所述第三方应用是否合法；所述创建模块还设置为在所述第三方应用合法的情况下，根据所述信息创建一个或多个扣费任务。
- 根据权利要求10所述的系统，其中，所述系统还包括：第二接收模块，设置为接收所述第三方应用的任务查询请求；查询模块，设置为在所述任务查询请求的触发下，将所述扣费任务对应的计费操作结果发送给所述第三方应用。
- 根据权利要求10所述的系统，其中，所述系统还包括：维护模块，设置为接收所述第三方应用的维护请求，在所述维护请求的触发下，修改所述扣费任务或者终止所述扣费任务。
- 根据权利要求10所述的系统，其中，所述系统还包括：补扣模块，设置为在与所述扣费任务对应的计费操作失败时，向营帐系统发起补扣计费操作。
- 根据权利要求10所述的系统，其中，所述系统还包括：通知模块，设置为接收所述第三方应用设置的结果通知地址，将所述扣费任务对应的计费操作结果实时发送给与所述结果通知地址对应的第三方应用。
- 根据权利要求10至15任一项所述的系统，其中，创建第三方应用的扣费任务的所述信 息包括以下至少之一：第三方应用身份认证信息，计费目的号码信息，任务生命周期，扣费循环周期，计费补扣期，正常计费金额，补扣计费金额，计费结果通知地址。
- 一种扣费系统，包括：配置模块，设置为第三方应用配置用于创建一个或多个扣费任务的信息；发送模块，设置为所述第三方应用向扣费系统发送所述信息。
- 根据权利要求17所述的系统，其中，配置用于创建一个或多个扣费任务的所述信息包括以下至少之一：第三方应用身份认证信息，计费目的号码信息，任务生命周期，扣费循环周期，计费补扣期，正常计费金额，补扣计费金额，计费结果通知地址。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510297249.8 | 2015-06-02 | ||
| CN201510297249.8A CN106301851A (zh) | 2015-06-02 | 2015-06-02 | 扣费方法及系统 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016192441A1 true WO2016192441A1 (zh) | 2016-12-08 |
Family
ID=57440140
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/076905 WO2016192441A1 (zh) | 2015-06-02 | 2016-03-21 | 扣费方法及系统 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106301851A (zh) |
| WO (1) | WO2016192441A1 (zh) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108335192B (zh) * | 2018-01-09 | 2020-07-28 | 阿里巴巴集团控股有限公司 | 业务处理、扣款方法及装置 |
| CN108389127A (zh) * | 2018-03-22 | 2018-08-10 | 中国银行股份有限公司 | 一种费用自动追缴方法及装置 |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101945366A (zh) * | 2009-07-07 | 2011-01-12 | 中国移动通信集团公司 | 体验式计费的方法、代理模块、终端及系统 |
| CN102404707A (zh) * | 2011-11-28 | 2012-04-04 | 深圳市五巨科技有限公司 | 一种移动终端视频聊天的计费方法及其移动终端 |
| US20120329425A1 (en) * | 2011-06-27 | 2012-12-27 | Verizon Patent And Licensing Inc. | Multi-tiered, usage-based pricing service plan |
| CN103248495A (zh) * | 2012-02-10 | 2013-08-14 | 中国移动通信集团公司 | 一种应用内付费的方法、服务器、客户端和系统 |
| CN103716762A (zh) * | 2012-09-29 | 2014-04-09 | 卓望数码技术（深圳）有限公司 | 一种互联网计费系统以及其实现安全计费的方法 |
| CN104363570A (zh) * | 2014-09-05 | 2015-02-18 | 中国联合网络通信有限公司上海市分公司 | 一种基于通信帐户以整月为周期的按次代缴付费方法 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101447878B (zh) * | 2008-12-31 | 2014-11-05 | 中兴通讯股份有限公司 | 一种预付费业务的计费方法与系统 |
-
2015
- 2015-06-02 CN CN201510297249.8A patent/CN106301851A/zh not_active Withdrawn
-
2016
- 2016-03-21 WO PCT/CN2016/076905 patent/WO2016192441A1/zh active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101945366A (zh) * | 2009-07-07 | 2011-01-12 | 中国移动通信集团公司 | 体验式计费的方法、代理模块、终端及系统 |
| US20120329425A1 (en) * | 2011-06-27 | 2012-12-27 | Verizon Patent And Licensing Inc. | Multi-tiered, usage-based pricing service plan |
| CN102404707A (zh) * | 2011-11-28 | 2012-04-04 | 深圳市五巨科技有限公司 | 一种移动终端视频聊天的计费方法及其移动终端 |
| CN103248495A (zh) * | 2012-02-10 | 2013-08-14 | 中国移动通信集团公司 | 一种应用内付费的方法、服务器、客户端和系统 |
| CN103716762A (zh) * | 2012-09-29 | 2014-04-09 | 卓望数码技术（深圳）有限公司 | 一种互联网计费系统以及其实现安全计费的方法 |
| CN104363570A (zh) * | 2014-09-05 | 2015-02-18 | 中国联合网络通信有限公司上海市分公司 | 一种基于通信帐户以整月为周期的按次代缴付费方法 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106301851A (zh) | 2017-01-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11457111B2 (en) | Method and apparatus for verifying the correctness of a roaming account balance | |
| US8832250B2 (en) | Method and server for agent service applied to widget | |
| US20110251921A1 (en) | Method and system to facilitate billing of embedded applications in a serving platform | |
| CN108009823A (zh) | 基于区块链智能合约的分布式算力资源的调用方法和系统 | |
| US11551196B2 (en) | Systems and methods for real-time, distributed processing of group bill payments | |
| CN111833034B (zh) | 一种批量扣款方法、支付服务器、计算机设备及存储介质 | |
| US8942673B2 (en) | Method and apparatus for providing cellphone service from any device | |
| US8838488B1 (en) | Maintaining a common identifier for a user session on a communication network | |
| CN103401859B (zh) | 一种协议转换的方法及协议转换器 | |
| WO2016192441A1 (zh) | 扣费方法及系统 | |
| US10944874B2 (en) | Telecommunication system for monitoring and controlling of a network providing resource to a user | |
| WO2019101082A1 (zh) | 一种增值业务的实现方法、装置和行业应用鉴权中心 | |
| CN102821379B (zh) | 一种计费重批的方法及装置 | |
| CN112286574A (zh) | 统计应用程序版本的方法、装置、终端设备和存储介质 | |
| EP3104550B1 (en) | Mobile digital cellular telecommunication system with advanced functionality for rating correction | |
| US10171466B2 (en) | Maintaining a common identifier for a user session on a communication network | |
| US20170068577A1 (en) | Computing consumption of application programming interfaces | |
| CN112953731B (zh) | 一种基于api网关的api高级流控及计量方法 | |
| WO2017067455A1 (zh) | 一种基于指纹应用的验证装置及方法 | |
| EP3331196A1 (en) | Telecommunication system for monitoring and controlling of a network providing resource to a user | |
| CN108471409B (zh) | 语音对话平台的应用程序接口鉴权配置方法及系统 | |
| US20100017317A1 (en) | Handling of open reservations in real-time environment | |
| CN105792200A (zh) | 一种鉴权方法、系统及相关装置 | |
| CN107708082A (zh) | 一种补充计费方法和装置 | |
| US10587425B2 (en) | Real-time co-ordinated fulfillment of refill transactions of a user account in a communication system |
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: 16802364 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 16802364 Country of ref document: EP Kind code of ref document: A1 |