WO2014063513A1

WO2014063513A1 - Charging process method and device for embedded charging point

Info

Publication number: WO2014063513A1
Application number: PCT/CN2013/081077
Authority: WO
Inventors: 黄国腾
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-10-26
Filing date: 2013-08-08
Publication date: 2014-05-01
Also published as: CN103795552A; CN103795552B

Abstract

The present invention provides a charging process method and device for an embedded charging point, the method comprising: receiving a purchase request for the application charging point; sending an authorization request to a charging management server located on the carrier side, wherein, the authorization request used for authorizing the purchase request; performing the charging process for the application charging point according to the authorization result. By using the technical scheme provided by the invention, the problems in the related art that the charging scheme of the embedded charging point is low in security and the difficulty is high in development and the like can be solved. Consequently, the control power on the application embedded charging by the carrier is enhanced, and the problem that an application developer carries out arbitrary charging, overcharging, and repeated charging on a terminal user is avoided.

Description

Billing processing method and device for embedded charging point

TECHNICAL FIELD The present invention relates to the field of network communications, and in particular to a charging processing method and apparatus for embedded charging points. BACKGROUND With the development of mobile communication technologies and the improvement of processing capabilities of mobile terminals, the application store business has been vigorously developed, and it is bound to become a key business of major operators. In the sales process, the application developer handles the copyright usage fee of the application, and after the application is sold, the application of embedded charging to the mobile terminal during use also becomes an important source of income for the application developer. The application embedded charging of the mobile terminal means that the mobile terminal user needs to obtain an additional service or content based on the application from the service provider of the application or the server of the content provider by paying for the mobile terminal application. In summary, the embedded charging methods used in the terminal equipment are: triggering charging through the application operating environment, triggering charging through short messages, and triggering charging through the Wireless Application Protocol (WAP). Mode. For example: Currently common Apple, Qualcomm wireless binary operating environment (Binary Runtime

End applications such as Environment for Wireless (BREW) use the operating environment to trigger charging. Generally, the application implements the underlying functions of the running environment. It relies heavily on the terminal and needs to be customized for the terminal operating system. , the workload is large. For another example: At present, the embedded billing point application triggered by short message and WAP triggers, because the implementation of the billing code is completely combined with the application code, the application development complexity is increased, and the application developer completely controls the application embedding. In the billing charging process, the operator cannot supervise the embedded billing process. There are problems such as the application developer's deduction of the end user, multiple deductions, and repeated deductions, which seriously damage the economic interests of the end user. Therefore, how to make the embedded billing point application convenient and safe to pay has become an urgent problem to be solved. In view of the above problems in the related art, an effective solution has not yet been proposed. SUMMARY OF THE INVENTION The present invention provides a billing processing method and apparatus for embedded billing points, which are related to technical problems such as low security of the charging scheme of the embedded billing point and difficulty in development. To solve at least the above problems. According to an embodiment of the present invention, a charging processing method for embedding a multi-mode charging point is provided, including: receiving a purchase request for an application charging point; and transmitting an authentication to a charging management server located at an operator side The request, where the authentication request is used to authenticate the purchase request; and according to the authentication result, the application charging point is charged. And performing charging processing on the application charging point according to the authentication result, including: if the authentication result indicates that the authentication is successful, directly using the service or content corresponding to the application charging point. And performing charging processing on the application charging point according to the authentication result, including: if the authentication result indicates that the authentication fails, indicating to purchase the application charging point. When the authentication result indicates that the authentication fails, the charging process of the application charging point includes: sending a charging request to the charging point to the charging management server; and performing payment purchase on the application charging point according to the charging request. After the payment is made to the application charging point according to the charging request, the method further includes: generating verification information for the payment result after the payment is purchased; forwarding the verification information to the online game server for verification; and transmitting the application charging point after the verification is passed The corresponding service or content. According to another embodiment of the present invention, an accounting processing apparatus for an embedded charging point is provided, including: a receiving module, configured to receive a purchase request for an application charging point; and a sending module, configured to be located at an operator The accounting management server of the side sends an authentication request, where the authentication request is set to authenticate the purchase request, and the processing module is configured to perform charging processing on the application charging point according to the authentication result. The processing module is configured to directly use the service or content corresponding to the application charging point if the authentication result indicates that the authentication is successful. The processing module is configured to instruct to perform the purchase of the application charging point if the authentication result indicates that the authentication fails. The processing module includes: a sending unit, configured to: when the authentication result indicates that the authentication fails, send a charging request to the charging management server to the charging management server; and the purchasing unit is configured to apply the charging point to the application according to the charging request. Make a payment purchase. The device further includes: a verification information generating module, configured to generate verification information for the payment result after the payment is purchased; and a forwarding module configured to forward the verification information to the online game server for verification; and the sending module is set to be verified after passing the verification Send the service or content corresponding to the application billing point. According to the present invention, after receiving the purchase request of the application charging point, the charging management server authenticates the charging request by using the charging management server, and solves the related art, the charging scheme of the embedded charging point is secure. Technical problems such as low sexuality and difficulty in development have strengthened the operator's in-house billing control, which avoids the problem of application developers' deduction of fees, deductions and repeated deductions for end users. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a flowchart of a charging processing method of an embedded charging point according to Embodiment 1 of the present invention; FIG. 2 is a diagram showing a structure of an accounting processing apparatus for embedding a charging point according to Embodiment 1 of the present invention; 3 is a block diagram of another structure of a charging processing device embedding a charging point according to Embodiment 1 of the present invention; FIG. 4 is a multi-mode charging method based on an application embedded charging point according to Embodiment 3 of the present invention; FIG. 5 is a schematic diagram of a multi-mode charging method and a system prop purchase process based on an application embedded charging point according to Embodiment 4 of the present invention; FIG. 6 is an application-based embedded charging according to Embodiment 5 of the present invention; FIG. 7 is a flow chart of a multi-mode charging method based on an application embedded charging point and a system online shopping application purchase flow chart according to Embodiment 6 of the present invention; FIG. A schematic diagram of a structure of a multi-mode charging system based on an application-embedded charging point according to Embodiment 7 of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. Considering the technical problems of the related art, the charging scheme of the embedded charging point is not high, and the development is difficult, the related solutions are provided in the following embodiments, which will be described in detail. Embodiment 1 FIG. 1 is a flowchart of a charging processing method of an embedded charging point according to Embodiment 1 of the present invention. As shown in FIG. 1, the method includes: Step S102: Receive a purchase request for an application charging point; Step S104, send an authentication request to a charging management server located at an operator side, where the authentication request is used for purchase Requesting for authentication; Step S106, performing charging processing on the application charging point according to the authentication result. Through the above processing steps, since the charging management server authenticates the charging request after receiving the purchase request of the application charging point, the application of the embedded multi-mode charging does not depend on the terminal device. It does not depend on the application itself, so it does not need to increase the complexity of application development, and it simplifies the design difficulty of the application developer. In addition, it divests the application developer's control over the embedded billing point, and strengthens the operator's right. The application of embedded charging control strength avoids the problem that application developers are deducting fees, deducting fees and repeating deductions for end users. To improve the user experience, when the authentication result indicates that the authentication is successful, the service or content corresponding to the application charging point is directly used. This eliminates the request response process with the billing server for applying the billing point billing. In this embodiment, when the authentication result indicates that the authentication fails, the purchase of the application charging point is instructed. At this time, when the authentication result indicates that the authentication fails, the charging process for applying the charging point may include, but is not limited to, the following processing flow: sending a charging request to the charging account to the charging management server; The fee requests a payment purchase for the application billing point. In order to prevent the end user from cracking the application of the embedded billing point and unconditionally defrauding the service of the online game server, the service provider of the online game (ie, online game) is harmed, and after the payment is made to the application billing point according to the billing request, The following processing may be performed: generating verification information for the payment result after the payment is purchased; forwarding the verification information to the online game server for verification; and delivering the service or content corresponding to the application charging point after the verification is passed. In this embodiment, a billing processing device is also provided, which is used to implement the foregoing embodiments and preferred embodiments. The descriptions of the foregoing embodiments are omitted. The module is explained. As used hereinafter, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable. 2 is a block diagram showing the structure of a charging processing apparatus for embedding a charging point according to Embodiment 1 of the present invention. As shown in FIG. 2, the device includes: a receiving module 20, connected to the sending module 22, configured to receive a purchase request for an application charging point; and a sending module 22 connected to the processing module 24, configured to be located at an operator side The charging management server sends an authentication request, where the authentication request is used to authenticate the purchase request, and the processing module 24 is configured to perform charging processing on the application charging point according to the authentication result. The functions implemented by the above modules can also make the application embedded multi-mode charging neither rely on the terminal device nor the application itself, so there is no need to increase the complexity of application development, and simplify the design difficulty of the application developer. In addition, the application developer's control over the embedded billing point is stripped off, and the operator's embedded billing control is strengthened, which avoids the application developer's deduction, end-of-charge and repeated deduction for the end user. problem. In this embodiment, in order to improve the user experience, the processing module 24 is configured to directly use the service or content corresponding to the application charging point if the authentication result indicates that the authentication is successful. In this embodiment, the processing module 24 is configured to instruct to perform the purchase of the application charging point if the authentication result indicates that the authentication fails. Preferably, as shown in FIG. 3, the processing module 24 includes: a sending unit 240, connected to the purchasing unit 242, configured to send a meter to the charging management server to the charging management server when the authentication result indicates that the authentication fails. The fee request; the purchasing unit 242 is configured to make a payment purchase to the application billing point according to the billing request. As shown in FIG. 3, the foregoing apparatus further includes: a verification information generating module 26, connected to the forwarding module 28, configured to generate verification information for the payment result after the payment is purchased; and a forwarding module 28 connected to the sending module 30, configured to The verification information is forwarded to the online game server for verification; the delivery module 30 is configured to deliver the service or content corresponding to the application charging point after the verification is passed. Embodiment 2 This embodiment provides a multi-mode charging method based on an application embedded charging point. For the terminal application, the embedded multi-mode charging point does not depend on the mobile terminal, and the application developer is avoided without increasing the complexity of application development. The problem of deducting charges, multiple deductions, and repeated deductions for the end user, and avoiding the unconditional defrauding of the online game server service by the end user after the application of the embedded charging point is avoided, thereby ensuring the interests of the online game service provider. To achieve the above objective, the technical solution provided by this embodiment is as follows: A multi-mode billing software development kit (Software Development Kit, referred to as SDK), after receiving an application billing point purchase request, acquiring a configuration parameter developer in an application configuration file Encryption key, developer ID and billing point ID, and obtain the identifier of the terminal itself; and encrypt the purchase request and initiate a billing authentication request to the multi-mode billing management system. After obtaining the charging point authentication request of the multi-mode charging SDK, the multi-mode charging management system first decrypts the obtained charging request parameter, and then authenticates the developer, the charging point, and the terminal identification relationship, and the terminal After the authentication of the subscription relationship is successful, return directly; otherwise, return the amount of the billing point. After the multi-mode charging SDK obtains the authentication response of the multi-mode charging management system, if the authentication is successful, the charging point is directly used; if the authentication fails, the charging account name/password is input and the purchase is confirmed. The multi-mode charging SDK obtains the terminal user input charging account name/password, and obtains the configuration parameter developer encryption key, developer ID and charging point ID in the application configuration file, and acquires the terminal own identifier; The billing management system initiates a billing point billing request. After obtaining the multi-mode charging SDK charging request, the multi-mode charging management system verifies the charging account/password, and after the verification succeeds, initiates a charging request to the payment system; after obtaining the payment system successfully, the multi-mode charging management system Generate an order record and generate a payment result verification string for subsequent online game service to perform billing verification. After the multi-mode charging SDK obtains the charging result, the current charging result is displayed to the user; and the multi-mode charging SDK charging returns the current charging result and the verification string to the application; if the application requires the online payment payment verification, the following process is performed. Otherwise, the multi-mode billing point purchase flow ends here. After the application obtains the multi-mode charging SDK billing return verification string, the verification string is forwarded to the online game server. After obtaining the application forwarding multi-mode charging management system verification string, the online game server initiates an authentication request to the multi-mode charging management system, and the multi-mode charging management system returns the verification result according to the verification and returns the verification result to the online game server. After obtaining the verification result of the multi-mode charging management system verification string, the online game server delivers the current purchase service or content to the terminal user. The billing point mode includes item billing, level billing, and billing period billing. The item billing is required to charge each time the item is purchased. The level billing is the level of billing after the level is purchased. The billing mode does not require billing again during its cycle time. In order to better understand the above embodiments, the following detailed description will be given in conjunction with Embodiments 3-5. The following embodiments are based on a multi-mode billing processing technology that uses an embedded billing point. The embedded multi-mode billing point supports charging in multiple modes such as props, levels, and cycles. The embedded multi-mode billing SDK supports mobile phones. Terminals, Pad terminals, and TV set-top boxes, etc.; in particular, the built-in multi-mode billing point provides security verification after billing is completed, which ensures the reliability and security of online game billing. Embodiment 3 FIG. 4 is a schematic overall flow chart of a multi-mode charging method based on an application-embedded charging point according to Embodiment 3 of the present invention. As shown in FIG. 4, the method includes: Step S402: The developer registers with the operator after registration, and obtains an encryption key assigned by the system to the developer after successful signing. Once you become a contract developer, you can settle with your carrier. Step S404: The developer applies to the operator for the charging point, and the charging point includes: a charging point ID, a charging point name, a charging mode, and a charging amount, where the charging mode includes pressing the item, pressing the level, and pressing the period. Three modes, such as billing; the billing point can take effect after the operator passes the audit. Step S406: The developer obtains the multi-mode billing SDK and its help document, obtains the developer encryption key, the developer ID, and the billing point ID, in preparation for making the embedded multi-mode SDK application. Step S408: The developer creates an application embedded multi-mode charging SDK; and configures the developer encryption key, the developer ID, and the charging point ID as application parameters in the application, so as to be acquired by the subsequent multi-mode charging SDK basic module. Step S410: The developer application is released for download and use by the terminal user; the application may be a mobile phone application, a pad application, or a TV set-top box application. Step S412: The end user downloads and installs the embedded multi-mode charging SDK application. Step S414: The terminal user runs and uses the embedded multi-mode charging SDK application, and thus completely describes the whole process of the production, distribution and propagation of the embedded multi-mode charging SDK application, and then describes the user purchasing the charging point. The overall process. Step S416: When the terminal user selects the service of purchasing the item, purchasing the level, subscribing, recharging, etc. when using the multi-mode charging SDK application, the application triggers the multi-type charging SDK to initiate the purchase of the charging point stream stalk. Step S418: Before the terminal user purchases the charging point, the multi-mode charging SDK basic module acquires the developer encryption key, the developer ID, and the charging point ID in the configuration file, and acquires the identifier of the terminal itself; After the SDK charging communication module is encrypted, the charging point authentication and pricing request is initiated to the multi-mode charging management system. Step S420: After obtaining the charging point authentication and rating request of the multi-mode charging SDK, the multi-mode charging management system first decrypts and obtains the charging request parameter, and then the developer authentication, the charging point authentication, and the terminal identification ordering relationship. Authentication, after the terminal identification subscription relationship is successfully authenticated, return directly; otherwise, the billing point amount is returned. Step S422: After the multi-mode charging SDK obtains the authentication quota of the multi-mode charging management system, if the authentication is successful, the charging point is directly used; if the authentication fails, the multi-mode charging SDK human-computer interaction module is used. The user displays the price after the authentication is approved, and prompts the end user to purchase. Step S424: The terminal user multi-mode charging SDK human-computer interaction module inputs the charging account name/password. After confirmation, the multi-mode charging SDK sets the charging account name/password, the developer ID and the charging point ID, and the terminal itself. The identifier; after the multi-mode billing SDK billing communication module encrypts using the developer encryption key, initiates a billing point billing request to the multi-mode billing management system. Step S426: After obtaining the charging point charging request, the multi-mode charging management system initiates a charging request to the payment system after the charging account/password authentication is successful. After the payment system is completed, the purchase record is recorded and the payment result is generated. Verify the string for subsequent online game service to perform billing verification. Step S428: After the multi-mode charging SDK human-computer interaction module obtains the charging result, the current charging result is displayed to the user; and the multi-mode charging SDK charging communication module returns the current charging result and the verification string to the application; The application requires online game payment verification, and step S430 is performed; otherwise, step S436 is performed. Step S430: After obtaining the verification string of the multi-mode charging SDK charging communication module, the application forwards the verification string to the online game server. Step S432: After obtaining the application forwarding multi-mode charging management system verification string, the online game server initiates verification to the multi-mode charging management system charging result verification module, and the multi-mode charging management system charging result verification module performs verification according to the verification serialization. And returning the verification result to the online game server; the verification of the verification string is mainly to prevent the application from being cracked and simulating the charging success to defraud the service of the online game server. Step S434: After the online game server obtains the verification result of the multi-mode charging management system verification string, the online game server determines whether to issue the current purchase service according to the verification result; the verification of the verification string is mainly to prevent the application from being cracked and the analog charging success to defraud Online game server service. Step S436: The terminal user obtains the content or service purchased this time. The purchase process for the end user to purchase the embedded multi-mode billing point has been completely described so far. Embodiment 4 FIG. 5 is a schematic diagram of a multi-mode charging method and a system prop purchase process based on an application-embedded charging point according to Embodiment 4 of the present invention. The so-called purchase by prop, that is, each purchase requires payment, for example, the purchase of the first designated weapon requires payment, and the purchase of the second designated weapon also requires payment. As shown in FIG. 5, the method includes: Step S502: The terminal user purchases a charging point, such as an item and a recharge, of the embedded multi-mode charging SDK application. Step S504: The terminal application invokes an application program interface (Application Program Interface (API) provided by the multi-mode charging SDK to initiate a purchase charging point request. Step S506: The multi-mode charging SDK acquires a developer encryption key through the basic module. The developer ID, the billing point ID, and the identifier of the terminal itself; after the encryption by the billing communication module, the authentication and bidding request is initiated to the multi-mode billing management system. Step S508: The multi-mode charging management system authentication and pricing module performs the evaluation by the developer, the charging point, and the like, and returns the charging point rating result to the multi-mode charging SDK. Step S510: Multi-mode The billing SDK human-computer interaction module displays the result of the authentication and rating, and prompts the end user to make a purchase. Step S512: The terminal user inputs the billing account name/password and confirms the purchase. Step S514: The multi-mode charging SDK encrypts the charging account name/password, the developer ID, the charging point ID, and the terminal identifier by using the developer encryption key through the multi-mode charging SDK charging communication module. The multi-mode charging management system initiates a charging point charging request. Step S516: The multi-mode charging management system verifies the charging account name/password, and if the account name does not exist, the password is incorrect, etc., the user is prompted with an error; if the account name/password verification is successful, the payment system performs payment. Step S518: After the payment system successfully pays, the multi-mode billing management system records the purchase order, and the purchase order includes the developer ID, the billing point ID, the billing point name, the billing point amount, the billing point mode, and the billing account name. , terminal identification, purchase time and other information. Step S520: The multi-mode charging management system returns the charging result to the multi-mode charging SDK and presents it to the user. Step S522: The multi-mode charging SDK returns the charging result to the terminal application; Step S524: The terminal application purchases the service or the props according to the charging result; if it is a stand-alone application or does not need to go to the online game server for verification, the process ends here; For the online game verification, refer to the process shown in Figure 7. The following is a detailed description, and details are not described here. Embodiment 5 FIG. 6 is a schematic diagram of a multi-mode charging method based on an application-embedded charging point and a system level/per-cycle purchase process according to Embodiment 5 of the present invention. The so-called purchase by level, that is, can be used multiple times after purchase, for example, the purchase of the tenth level requires payment, the second use of the tenth level does not need to pay again; the so-called cycle purchase, that is, after the purchase, is free during the cycle Use, such as subscribing to a monthly magazine, is free for one month. As shown in FIG. 6, the method includes: Step S602: The terminal user purchases a charging point of the embedded multi-mode charging SDK application, such as a level card and a subscription. Step S604: The terminal application invokes an API provided by the multi-mode charging SDK to initiate a purchase charging point request. Step S606: The multi-mode charging SDK acquires a developer encryption key, a developer ID, a charging point ID, and a terminal through the basic module. The self-identification, after being encrypted by the charging communication module, initiates an authentication and rating request to the multi-mode charging management system. Step S608: The multi-mode charging management system authentication and pricing module performs the pricing of the developer, the charging point, and the like, and the most important is to perform the order relationship verification according to the terminal identifier. If the terminal has paid and is within the validity period, proceed to step S610; if the terminal has not been purchased or has expired after the purchase, the billing point rating result is returned to the multi-mode charging SDK, and step S614 is performed; Step S610: The multi-mode charging SDK returns to the terminal application after the authentication verification is passed. Step S612: The terminal application allows the terminal application to continue to use, so as to avoid the verification of the charging account name/password every time the terminal is used, thereby improving the user experience. Step S614: After the mode charging SDK or the authentication verification fails, the multi-mode charging SDK human-computer interaction module displays the authentication rating result, and prompts the terminal user to make a purchase. Step S616: The terminal user inputs the billing account name/password and confirms the purchase. Step S618: The multi-mode charging SDK encrypts the charging account name/password, the developer ID, the charging point ID, and the terminal identifier by using the developer encryption key through the multi-mode charging SDK charging communication module. The multi-mode charging management system initiates a charging point charging request. Step S620: The multi-mode charging management system verifies the charging account name/password, and if the account name does not exist, the password is incorrect, etc., the user is prompted with an error; if the account name/password verification is successful, the payment system is paid. Step S622: After the payment system successfully pays, the multi-mode billing management system records the purchase order, and the purchase order includes the developer ID, the billing point ID, the billing point name, the billing point amount, the billing point mode, and the billing account name. , terminal identification, purchase time and other information. Step S624: The multi-mode charging management system returns the charging result to the multi-mode charging SDK and presents it to the user. Step S626: The multi-mode charging SDK returns a charging result to the terminal application. Step S628: The terminal application purchases a service or a level according to the charging result, and the process ends; if it is a stand-alone application or does not need to be verified by the online game server; If online game verification is required, the process shown in Figure 7 will be described in detail below, and will not be described here. Embodiment 6 FIG. 7 is a flowchart of a multi-mode charging method based on an application-embedded charging point and a system online shopping application purchase according to Embodiment 6 of the present invention. The so-called online game purchase, specifically the online game server does not trust the payment result of the client application feedback, so the online game server obtains the purchase process of the client application feedback payment result and the verification string and then goes to the billing party to perform the payment result verification. As shown in FIG. 7, the method includes: Step S702: The terminal user purchases a charging point of the embedded multi-mode charging SDK application, such as recharging to an online game coin; Step S704: the terminal application invokes the multi-mode charging SDK to provide The API initiates the purchase of the charging point request; Step S706: The multi-mode charging SDK acquires the developer encryption key, the developer ID, the charging point ID, and the identity of the terminal itself through the basic module; and encrypts the backward multi-mode through the charging communication module. The charging management system initiates the authentication and rating request; Step S708: The multi-mode charging management system authentication and pricing module performs the evaluation by the developer, the charging point, etc., and returns the charging point rating result. Multi-mode billing SDK; Step S710: The multi-mode charging SDK human-computer interaction module displays the authentication rating result, and prompts the terminal user to make a purchase; Step S712: the terminal user inputs the charging account name/password, and confirms the purchase; Step S714: Multi-mode charging The SDK sends the billing account name/password, developer ID and billing point ID, and the terminal's own identifier to the multi-mode billing management system after being encrypted by the multi-mode billing SDK billing communication module using the developer encryption key. Step S716: The multi-mode charging management system verifies the charging account name/password, and if the account name does not exist, the password is incorrect, etc., the user is prompted with an error; if the account name/password verification is successful, the payment system is reached. Step S718: After the payment system successfully pays, the multi-mode billing management system records the purchase order, and the purchase order includes the developer ID, the billing point ID, the billing point name, the billing point amount, the billing point mode, and the billing point. Information such as account name, terminal identification, purchase time, etc.; Step S720: The multi-mode charging management system returns the charging result to the multi-mode charging SDK, and uses Step S722: The multi-mode charging SDK returns a charging result and a verification string to the terminal application. Step S724: After the terminal application obtains the charging result and the verification string returned by the multi-mode charging SDK, the terminal application forwards the request to the online game server. The sub-purchase service; Step S726: The online game server sends the verification result to the multi-mode charging management system charging result verification module according to the transparent transmission verification string; the verification of the verification string is mainly to prevent the application from being cracked and simulating the charging success to defraud the online game server. Step S728: The multi-mode charging management system informs the online game server of the verification result of the verification string; Step S730: The online game server delivers the service purchased this time to the terminal application; Step S732: The terminal application provides the terminal user with the current use Purchased Service; Embodiment 7 FIG. 8 is a schematic structural diagram of a multi-mode charging system based on an application-embedded charging point according to Embodiment 7 of the present invention. As shown in Figure 8, the system includes: The multi-mode charging management system 80, that is, the multi-mode charging method based on the application of the embedded charging point and the server of the system; the multi-mode charging management system includes 6 parts, respectively, a developer, an end user management module 802, The key management module 804, the billing management module 806, the order management module 808, the online game verification module 810, and the authentication payment module 812. The functions implemented by the above modules are as follows - the developer and the end user management module 802 in the multi-mode billing management system; mainly providing developer registration, developer signing, developer management, and administrator reviewing developer signing information; , end user management and other functions to provide basic data management for multi-mode billing management systems. The key management module 804 in the multi-mode charging management system mainly provides key generation, key verification, key encryption and decryption functions. When the developer is successful, the key management module 804 generates a key for the successful developer; when the authentication payment module 812 obtains the multi-mode charging SDK authentication or charging request, the request and the response result are decrypted and encrypted; The verification module 810 provides a decryption function for the encrypted verification string and the verification string. The key management module 804 is a multi-mode billing management system security guarantee. The billing management module 806 in the multi-mode billing management system provides functions for developers to apply for multi-mode billing points, administrators to audit billing points, and billing point management. The multi-mode billing point mode includes 3 types of items, by level, and by subscription. The billing management module provides guarantee for the operator to uniformly and standardize the management of billing points. The order management module 808 in the multi-mode billing management system is set to the original record end user purchase record function. The authentication payment module 812 is provided with an authentication rating basis to provide a data foundation for the developer to settle later. The online game verification module 810 in the multi-mode charging management system provides a verification string for the authentication payment module 812, and the verification string is an encrypted string encrypted according to a certain rule according to the order record; the online game verification module 810 opens the verification API to the public network. The online game server performs payment result verification; the verification of the verification string is mainly to prevent the application from being cracked and simulating the charging success message to defraud the service of the online game server. The authentication payment module 812 in the multi-mode charging management system is configured to implement three main functions including authentication, rating, and payment; authentication includes developer authentication, charging point authentication, user authentication, and subscription relationship checking. The rating is mainly based on the user or terminal identification and ordering relationship, preferential policies, etc.; the payment function is mainly to connect with the payment system and complete the payment; the authentication payment module receives the authentication request of the multi-mode charging SDK or When the payment request is made, the key management module 804 is called to perform decryption. After the authentication and payment are completed, the key management module 804 is invoked to encrypt the response message and generate a verification string. The multi-mode charging SDK 82, that is, the multi-mode charging method based on the application of the embedded charging point and the client of the system; the multi-mode charging SDK includes three parts, namely, the charging communication module 820 and the human-computer interaction module 822 respectively. , the base module 824. The functions implemented by each module are as follows: The charging communication module 820 of the multi-mode charging SDK provides an API to the application 84, and the main API is an authentication rating API and a payment API, and returns a charging result and a verification string to the application; the charging communication module 820 completes and multi-mode The accounting payment module 812 performs message interaction in the billing management system; the billing communication module 820 obtains configuration information, terminal information, and completes encryption and decryption operations through the base module 824; the billing communication module performs interaction with the user through the human-machine interaction module S510. . The human-computer interaction module 822 in the multi-mode charging SDK mainly prompts the user according to the authentication or payment status of the charging communication module 820, and guides the user to complete the payment. The basic module 824 in the multi-mode charging SDK mainly completes application configuration information reading, terminal information reading, such as mobile phone IMEI number; and completion of authentication, payment request, and response encryption and decryption operations. The application 84 running on the terminal, referred to as the application 84, includes a mobile application, a pad application, and a TV set top box application. The terminal device 86 provides an environment for the application to operate; the terminal device 86 includes a mobile phone, a pad, a television set top box, and the like. The online game server 88 or the online game verification module 880 in the online game server 88 mainly completes the verification of the charging result verification string. The payment system 90, such as a mobile phone bill payment system and a third party payment system, requires a docking between the multi-mode billing system and the payment system to complete the system. It can be seen from the foregoing embodiment that the foregoing embodiment achieves the following beneficial effects: When the application initiates the embedded charging, the application does not directly trigger the charging, but sends the charging request information to the multi-mode charging SDK, and the multi-mode charging is performed. The SDK interacts with the multi-mode charging system to complete the charging request; after the charging request is completed, the verification of the serial server authentication is also provided. Compared with the prior art, the application of embedded multi-mode charging is independent of the terminal device and does not depend on the application itself, so there is no need to increase the complexity of application development, and simplify the design difficulty of the application developer, and in addition, stripped off The application developer's control over the embedded billing point of the application strengthens the operator's in-house billing control, which avoids the problem of the application developer's deduction, deduction and repeated deduction for the end user. The billing point server verification function prevents the end user from cracking the application of the embedded billing point and unconditionally defrauding the service of the online game server, thereby ensuring the interests of the online game service provider. In another embodiment, software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments. In another embodiment, a storage medium is provided, the software being stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed 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 are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

1. A charging processing method for embedding a multi-mode charging point, comprising:

Receiving a purchase request for an application billing point;

And sending an authentication request to the charging management server located at the operator side, where the authentication request is used to authenticate the purchase request;

Performing charging processing on the application charging point according to the authentication result.

The method according to claim 1, wherein the charging of the application charging point is performed according to the authentication result, including:

If the authentication result indicates that the authentication is successful, the service or content corresponding to the application charging point is directly used.

If the authentication result indicates that the authentication fails, then the purchase of the application billing point is instructed.

The method according to claim 3, wherein, when the authentication result indicates that the authentication fails, performing charging processing on the application charging point includes:

Sending a charging request to the charging management server to the application charging point;

Payment purchase is performed on the application billing point according to the billing request.

The method according to claim 4, further comprising: after performing the payment purchase on the application charging point according to the charging request, further comprising:

Generating verification information for payment results after payment purchase;

Forwarding the verification information to the online game server for verification;

After the verification is passed, the service or content corresponding to the application charging point is delivered.

6. A billing processing device with a built-in billing point, comprising:

a receiving module, configured to receive a purchase request for an application charging point;

The sending module is configured to send an authentication request to the charging management server located at the operator side, where the authentication request is used to query the purchase of the dragon: The processing module is configured to perform charging processing on the application charging point according to the authentication result.

The device according to claim 6, wherein the processing module is configured to directly use the service or content corresponding to the application charging point if the authentication result indicates that the authentication is successful.

The device according to claim 6, wherein the processing module is configured to instruct to perform the purchase of the application charging point if the authentication result indicates that the authentication fails.

9. The device according to claim 8, wherein the processing module comprises:

a sending unit, configured to send, to the charging management server, a charging request for the application charging point when the authentication result indicates that the authentication fails;

The purchasing unit is configured to perform a payment purchase on the application charging point according to the charging request.

10. The device according to claim 9, further comprising:

The verification information generating module is configured to generate verification information for the payment result after the payment is purchased; the forwarding module is configured to forward the verification information to the online game server for verification; and the sending module is configured to deliver the verification after the verification is passed Apply the service or content corresponding to the billing point.