CN108366176B - Charging method, device and system for terminal application - Google Patents
Charging method, device and system for terminal application Download PDFInfo
- Publication number
- CN108366176B CN108366176B CN201810072792.1A CN201810072792A CN108366176B CN 108366176 B CN108366176 B CN 108366176B CN 201810072792 A CN201810072792 A CN 201810072792A CN 108366176 B CN108366176 B CN 108366176B
- Authority
- CN
- China
- Prior art keywords
- charging
- data
- acceleration
- request
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/51—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for resellers, retailers or service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
Abstract
The embodiment of the application discloses a charging method, a device and a system for terminal application. After receiving service data of an application to be charged and an enterprise client identifier of the application to be charged, which are sent by an SDK, an acceleration server executing acceleration service acquires charging information of the service data to obtain charging data of the service data, and then sends a charging request to a charging management system, wherein the charging request comprises the charging data and authentication information of first security authentication, so that the charging management system carries out charging statistics on target charging data after determining that the charging data is the target charging data. Therefore, when the application to be charged is in the open state, the method finishes the collection and reporting work of the charging data by accelerating the server, and reduces the performance loss of the terminal application; and the validity of the charging data reported by the acceleration server is ensured and the benefit of the enterprise client is ensured through the authentication process of the acceleration server and the charging management system.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a charging method, device, and system for a terminal application.
Background
When charging service data of a terminal application, a Software Development Kit (SDK) is usually embedded in an application program of the terminal application, the SDK proxies the service data of the application and forwards the service data to a Content Delivery Network (CDN) in a cloud server for service acceleration, and then the SDK collects charging data of all forwarded service data and reports the collected charging data to a charging management system in real time, and the charging management system performs charging statistics on the charging data, where the acceleration service can reliably and quickly transmit the service data of the application outside the cloud server to reduce bandwidth cost of a user. At present, the flow of the charging method applied by the existing terminal is shown in fig. 1, and the method may include:
step 110, the SDK is embedded in the terminal application.
Step 120, after the terminal application is started, the SDK forwards the service data of the terminal application to the CDN to provide an acceleration service for the service data.
Step 130, after receiving the response of the acceleration service sent by the CDN, the SDK collects the charging data of the service data, and reports the charging data to the charging management system in real time.
Step 140, the charging management system performs charging statistics on the charging data.
However, in the above charging method, when the application is in a running state, the SDK may frequently perform charging data acquisition and charging data reporting on the service data of the application, which increases performance loss of the terminal application. Meanwhile, when the SDK receives the failure response of the acceleration service, the SDK reports the collected charging data to the charging management system, that is, the charging data is collected for the service data (or called invalid service data) that does not pass through the acceleration service, so that the effectiveness of the reported charging data is reduced, and the extra cost of the enterprise client is increased.
Disclosure of Invention
The embodiment of the application provides a charging method, a device and a system for a terminal application, which are used for reducing the performance loss of the terminal application and ensuring the effectiveness of charging data.
In a first aspect, a charging method for a terminal application is provided, where the method may include: after receiving service data of an application to be charged and an application identifier to be charged, which are sent by a Software Development Kit (SDK), acquiring charging information of the service data to obtain the charging data of the service data; and sending a charging request to a charging management system, wherein the charging request comprises charging data and authentication information of the first security authentication, and the charging request is used for requesting the charging management system to carry out charging statistics on the target charging data. Therefore, when the application to be charged is in the running state, the embodiment of the invention finishes the collection and reporting work of the charging data through the acceleration server, reduces the performance loss of the terminal application, and ensures the effectiveness of the charging data reported by the acceleration server through the authentication process of the acceleration server and the charging management system, thereby ensuring the benefits of enterprise clients.
In an optional example, the authentication information of the first security certificate includes an acceleration server identifier, and the authentication information of the first security certificate is used for the charging management system to determine that the charging data is the target charging data.
In an alternative example, the application to be billed is identified as an enterprise client to which the application to be billed belongs.
In an alternative example, the sending of the charging request to the charging management system includes: the charging request is sent to the charging management system after the first preset time period, namely the charging request is sent to the charging management system regularly, so that the condition that the charging data report fails due to the fact that the acceleration server is in a busy working state can be avoided, and the stability of the charging process is improved.
In an optional example, after sending the charging request to the charging management system, the method further includes: receiving a response of refusing the charging request sent by the charging management system; generating log information recording the charging request as an illegal request based on the response rejecting the charging request so as to show the reason why the charging process is stopped to the enterprise client.
In an optional example, after generating log information that records the charging request as an illegal request, the method further includes: and displaying the log information to the enterprise client logged in the billing management system.
In a second aspect, there is provided another charging method for a terminal application, the method including: receiving authentication information of a second security certificate sent by a Software Development Kit (SDK); acquiring a security authentication result according to authentication information of the second security authentication to trigger the SDK to start acceleration service, wherein the authentication information of the second security authentication comprises an application identifier to be charged; receiving a charging request sent by an acceleration server, wherein the charging request comprises charging data and authentication information of first security authentication; matching the authentication information of the first safety certificate with the pre-stored authentication information of the first safety certificate; if the matching is successful, determining the charging data as target charging data; and carrying out charging statistics on the target charging data to generate statistical data. Therefore, the method ensures the legality of the acceleration service through the authentication process of the SDK and the charging management system, and ensures the validity of the charging data reported by the acceleration server through the authentication process of the acceleration server and the charging management system, thereby ensuring the benefits of enterprise clients.
In an optional example, the charging data is data obtained by the acceleration server performing charging information collection on service data of the application to be charged, and the authentication information of the first security certificate includes an acceleration server identifier.
In an optional example, obtaining the authentication result according to the authentication information of the second security authentication includes: matching the authentication information of the second security certificate with the pre-stored authentication information of the second security certificate; if the matching is successful, triggering the SDK to start acceleration service so as to carry out charging statistics. This approach provides a way to obtain the authentication result.
In a third aspect, an acceleration service apparatus is provided, which may include:
and the receiving unit is used for receiving the service data of the application to be charged and the identification of the application to be charged, which are sent by the SDK.
And the acquisition unit is used for acquiring the charging information of the service data and acquiring the charging data of the service data.
And the sending unit is used for sending a charging request to the charging management system, wherein the charging request comprises charging data and an authentication information charging request of the first security authentication and is used for requesting the charging management system to carry out charging statistics on the target charging data.
In an optional example, the authentication information of the first security certificate includes the device identifier, and the authentication information of the first security certificate is used for the charging management system to determine that the charging data is the target charging data.
In an alternative example, the application to be billed is identified as an enterprise client to which the application to be billed belongs.
In an optional example, the sending unit is configured to send the charging request to the charging management system after a first preset time period.
In an optional example, the apparatus further comprises a generating unit. The receiving unit is also used for receiving a response of refusing the charging request sent by the charging management system; a generating unit configured to generate log information recording the charging request as an illegal request based on a response rejecting the charging request.
In an optional example, the apparatus further comprises: and the display unit is used for displaying the log information to the enterprise client logging in the charging management system after the generation unit generates the log information recording the charging request as an illegal request.
In a fourth aspect, there is provided a charging management apparatus, comprising:
and the receiving unit is used for receiving the authentication information of the second security certificate sent by the software development kit SDK.
And the obtaining unit is used for obtaining the security authentication result according to the authentication information of the second security authentication so as to trigger the SDK to start the acceleration service, wherein the authentication information of the second security authentication comprises the application identifier to be charged.
And the receiving unit is further used for receiving a charging request sent by the acceleration server, wherein the charging request comprises charging data and authentication information of the first security certificate.
And the matching unit is used for matching the authentication information of the first safety certificate with the pre-stored authentication information of the first safety certificate.
And the determining unit is used for determining the charging data as the target charging data if the matching is successful.
And the statistical unit is used for carrying out charging statistics on the target charging data to generate statistical data.
In an optional example, the charging data is data obtained by the acceleration server performing charging information collection on service data of the application to be charged, and the authentication information of the first security certificate includes an acceleration server identifier.
In an optional example, the obtaining unit is configured to match authentication information of the second security certificate with pre-stored authentication information of the second security certificate; and if the matching is successful, determining to perform charging statistics, and triggering the SDK to start acceleration service so as to perform charging statistics.
In a fifth aspect, a billing system is provided that includes an acceleration server and a billing management system. Wherein the acceleration server and the charging management system are used for executing the charging method.
In the embodiment of the application, on the acceleration server side, after receiving service data of an application to be charged and an enterprise client identifier of the application to be charged, sent by the SDK, the acceleration server executing the acceleration service collects charging information on the service data to obtain charging data of the service data, and then sends a charging request to the charging management system, where the charging request includes the charging data and authentication information of the first security certificate, so that the charging management system performs charging statistics on target charging data after determining that the charging data is the target charging data. When the application to be charged is in the running state, the method finishes the collection and reporting work of the charging data through the acceleration server, and reduces the performance loss of the terminal application. And meanwhile, before the charging process is started, the charging management system side firstly determines the validity of the verification acceleration service through an SDK authentication process in the terminal application, and then ensures the validity of the charging data reported by the acceleration server and the benefit of enterprise clients through the authentication process of the acceleration server and the charging management system.
Drawings
Fig. 1 is a schematic flowchart of a charging method for a terminal application in the prior art;
fig. 2 is a system framework diagram of an application of a charging method for a terminal application according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a charging method for a terminal application according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of a charging method for another terminal application according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an acceleration service apparatus according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a charging management apparatus according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without any creative effort belong to the protection scope of the present application.
The charging method for the terminal application provided by the embodiment of the invention can be applied to the system framework described in fig. 2, and the system can comprise a terminal, an acceleration service platform and a charging management platform. The application to be charged of the terminal is embedded with the SDK, and the acceleration service platform and the charging management platform are located on the cloud server.
The SDK is used to forward the service data of the application to be charged to the acceleration server, and the application to be charged may be WeChat, QQ, or the like. The SDK is the SDK of an acceleration service manufacturer embedded in terminal application developed by the enterprise customer.
The acceleration service platform is composed of a distributed acceleration server cluster. And the acceleration server in the acceleration service platform is used for providing acceleration service for the received business data. The acceleration server can comprise a charging data acquisition module and a reporting module, wherein the charging data acquisition module is used for acquiring charging information of accelerated service data and acquiring charging data, and the reporting module is used for reporting the charging data to the charging management system in real time or at regular time. The acceleration server may be a CDN having a charging data acquisition function and a reporting function.
The charging management system is used for performing authority authentication and control on the acceleration service of the SDK, issuing configuration information for providing the acceleration service to the acceleration server, and counting and displaying received charging data, and comprises a manageable application identifier, an enterprise client identifier to which the application identifier belongs and an acceleration server identifier.
The terminal according to the embodiments of the present invention may include a Mobile device with a wireless communication function, such as a handheld device, a vehicle-mounted device, a wearable device, a computing device, other processing devices connected to a wireless modem, various forms of user equipment, a Mobile Station (MS), and the like.
The working process of the system is as follows:
and after the acceleration server executing the acceleration service receives the service data of the application to be charged and the application identifier to be charged, which are sent by the SDK, the acceleration server acquires charging information of the service data to obtain the charging data of the service data. And then the acceleration server sends a charging request to the charging management system, wherein the charging request comprises charging data and authentication information of the first security certificate, and the authentication information of the first security certificate can comprise an acceleration server identifier, so that the charging management system determines that the charging data is target charging data according to the acceleration server identifier. And the charging management system carries out charging statistics on the target charging data, wherein the identifier of the application to be charged can also be an enterprise client identifier to which the application to be charged belongs, and the enterprise client identifier is an account number or a name of a developer of the application to be charged.
The charging management system receives authentication information of a second security certificate sent by the SDK before starting charging statistics; and acquiring a security authentication result according to the authentication information of the second security authentication, and determining to perform charging statistics if the security authentication result is authentication passing, wherein the authentication information of the second security authentication comprises an application identifier to be charged.
Therefore, compared with the prior art, when the application to be charged is in the running state, the embodiment of the invention finishes the collection and report work of the charging data through the acceleration server, reduces the performance loss of the terminal application, ensures the legality of the acceleration service through the authentication process of the SDK and the charging management system, and ensures the validity of the charging data reported by the acceleration server through the authentication process of the acceleration server and the charging management system, thereby ensuring the benefits of enterprise clients.
The preferred embodiments of the present application will be described below with reference to the accompanying drawings of the specification, it should be understood that the preferred embodiments described herein are merely for illustrating and explaining the present application, and are not intended to limit the present application, and that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
Fig. 3 is a flowchart illustrating a charging method for a terminal application according to an embodiment of the present invention. As shown in fig. 3, the executing entity of the method may be a server acceleration, and the method may include:
and step 310, receiving the service data of the application to be charged and the identification of the application to be charged, which are sent by the SDK.
Before executing the step, after the application to be charged is started, the SDK sends authentication information of a second security certificate to the charging management system, wherein the authentication information of the second security certificate comprises the identification of the application to be charged.
And the charging management system acquires a security authentication result according to the authentication information of the second security authentication so as to determine whether to carry out charging statistics. The process of security authentication may be: and the charging management system matches the application identifier to be charged with the application identifier prestored in the charging management system. And when the application identifier to be charged is successfully matched with the pre-stored application identifier, the authentication is successful. And the charging management system sends the acceleration service starting indication information to the SDK to carry out charging statistics. The indication information for starting the acceleration service may include an enterprise client identifier of the application to be billed.
Therefore, the charging management system authenticates the acceleration service of the SDK, the charging management system can check the legality of the current SDK for starting the acceleration service, and the successful authentication indicates that the SDK is legal when the SDK starts the acceleration service. If the authentication fails, the charging management system can control the SDK acceleration service to be closed so as to control the abnormal condition of the acceleration service, thereby enhancing the monitoring of the application to be charged and facilitating the operation and maintenance of the application. Meanwhile, the charging management system sends configuration information to the acceleration server, and the configuration information is used for the acceleration server to configure the acceleration service.
It should be noted that, when the matching between the identifier of the application to be charged and the identifier of the pre-stored application is unsuccessful, the authentication fails, which indicates that the charging management system cannot perform charging management on the application to be charged. The charging management system sends the indication information of authentication failure to the SDK, and the SDK transmits and interacts the service data applied by the terminal according to the original transmission mode. Therefore, the reliability of service operation is improved in the authentication process, and the service data is not included in the effective service data, so that the benefit of enterprise customers is ensured.
Returning to step 310, after the SDK starts the acceleration service, the acceleration server may receive an acceleration service request sent by the SDK, where the acceleration service request includes the service data of the application to be charged and the identifier of the application to be charged. The application identifier to be charged is used as a charging identifier, wherein the application identifier to be charged may also be an enterprise client identifier to which the application to be charged belongs.
Therefore, the SDK is used for carrying out acceleration service on the service data of the terminal application and forwarding the service data and the application identifier to be charged to the acceleration server, namely, related charging operations are transferred to the acceleration server, and performance loss of the terminal application is reduced.
And step 320, collecting the charging information of the service data to obtain the charging data of the service data.
When the acceleration service is in a normal service state, the acceleration server sends a response of receiving the acceleration service request to the SDK, and the acceleration server collects the charging information of the service data to obtain the charging data of the service data, wherein the charging information may include information such as the data size, the data type, and the data uploading address of the service data.
In one example, when the service data is voice service data, the acceleration server performs collection of charging information on the voice service data, and the obtained charging data includes that the data type is voice data, the data size is 6M, and the domain name of the data upload address is a.
Optionally, when the acceleration service is in an abnormal service state, the acceleration server sends a response to the SDK, which rejects the acceleration service request, at this time, the acceleration server rejects the collection of the charging information for the service data, and the SDK transmits and interacts the service data according to an original transmission mode, where the original transmission mode is a transmission mode in which the service data does not adopt the acceleration service.
Therefore, when the acceleration service is in an abnormal service state, the acceleration server does not acquire the charging information of the service data, namely, the charging information is not included in the effective charging data, so that the effectiveness of the charging data is ensured, and the benefit of an enterprise client is ensured.
Step 330, sending a charging request to the charging management system, where the charging request includes charging data and authentication information of the first security authentication, and the charging request is used to request the charging management system to perform charging statistics on the charging data.
The authentication information of the first security authentication comprises the accelerating server identification, so that the charging management system determines the charging data as target charging data according to the accelerating server identification, and the charging request is used for requesting the charging management system to perform charging statistics on the target charging data.
After the charging data is collected, the acceleration server can send a charging request to the charging management system in real time according to the current working state, such as an idle state or a busy state, or send the charging request to the charging management system after a first preset time period, that is, send the charging request to the charging management system at regular time, so that the occurrence of the situation that the charging data report fails due to the fact that the acceleration server is in the busy state is avoided, and the stability of the charging process is improved.
And the charging management system matches the received acceleration server identification with a prestored acceleration server identification based on the authentication information of the first security certificate in the charging request.
And when the received acceleration server identification is successfully matched with the prestored acceleration server identification, the authentication is successful, the charging management system determines that the charging data is the target charging data (or called legal charging data), and sends a response of receiving the charging request to the acceleration processor. Therefore, the validity of the charging data reported by the acceleration server is ensured through the authentication process of the acceleration server and the charging management system, and the behavior of illegally impersonating and stealing information is avoided.
And then, the charging management system performs charging statistics on the target charging data to generate statistical data, wherein the statistical data can be bandwidth values or flow values required by the service data. When an enterprise client logs into the billing management system, the billing management system may present the statistics to the enterprise client.
Optionally, when the received acceleration server identifier is unsuccessfully matched with the pre-stored acceleration server identifier, the charging management system determines that the charging data is non-target charging data (or called illegal charging data), and the charging management system sends a response rejecting the charging request to the acceleration server.
The acceleration server generates log information for recording the charging request as an illegal request based on the refusal of the charging request response. When the enterprise client logs into the acceleration server, the acceleration server presents the log information to the enterprise client to show to the enterprise client that the billing process was stopped because the billing request was denied.
In the above embodiment, on the acceleration server side, after receiving the service data of the application to be charged and the enterprise client identifier of the application to be charged, sent by the SDK, the acceleration server executing the acceleration service collects charging information for the service data to obtain charging data of the service data, and then sends a charging request to the charging management system, where the charging request includes the charging data and authentication information of the first security certificate, so that the charging management system performs charging statistics on the target charging data after determining that the charging data is the target charging data. When the application to be charged is in the running state, the method finishes the collection and reporting work of the charging data through the acceleration server, and reduces the performance loss of the terminal application. And meanwhile, before the charging process is started, the charging management system side firstly determines the validity of the verification acceleration service through an SDK authentication process in the terminal application, and then ensures the validity of the charging data reported by the acceleration server and the benefit of enterprise clients through the authentication process of the acceleration server and the charging management system.
The following describes the acceleration service of the acceleration server in detail as a normal service state.
Fig. 4 is a flowchart illustrating another charging method for a terminal application according to an embodiment of the present invention. As shown in fig. 4, the method may include:
step 401, the charging management system receives authentication information of the second security authentication sent by the SDK, where the authentication information of the second security authentication includes an application identifier to be charged.
And when the application to be charged is started, the SDK sends authentication information of second security authentication to the charging management system, wherein the authentication information of the second security authentication is used for verifying the legality of the acceleration service started by the SDK. The authentication information of the second security certificate comprises the identifier of the application to be charged.
Step 402, the charging management system matches the application identifier to be charged with the pre-stored application identifier, if the matching is successful, step 403 is executed, and if the matching is unsuccessful, step 404 is executed.
The charging management system searches for the identifier matched with the application identifier to be charged in the prestored application identifiers, if the identifier is found, the matching is successful, and if the identifier is not found, the matching is unsuccessful.
Step 403, the charging management system sends the indication information for starting the acceleration service to the SDK, and sends the configuration information to the acceleration server, and then step 405 is executed.
And when the application identifier to be charged is successfully matched with the pre-stored application identifier, the authentication is successful, the charging management system sends the indication information for starting the acceleration service to the SDK so as to indicate the SDK to start the acceleration service, and sends the configuration information to the acceleration server so as to provide the acceleration service for the acceleration server.
Step 404, the acceleration server receives the service data of the application to be charged and the identifier of the application to be charged, which are sent by the SDK.
Step 405, the acceleration server performs acceleration service and charging information collection on the service data based on the configuration information, and obtains charging data.
Step 406, the acceleration server sends a charging request to the charging management system, where the charging request includes charging data and authentication information of the first security certificate.
The authentication information of the first security certificate comprises an application identifier to be charged and an acceleration server identifier.
Step 407, the charging management system matches the acceleration server identifier in the authentication information with a pre-stored acceleration server identifier, if the matching is successful, step 408 is executed, and if the matching is unsuccessful, step 410 is executed.
Step 408, the charging management system determines the received charging data as the target charging data, and performs charging statistics on the target charging data to generate statistical data.
Step 409, the charging management system sends a response of receiving the charging request to the acceleration server, and the charging process is ended.
Step 410, the billing management system determines that the billing data is non-target billing data, and then step 411 is executed.
Step 411, the billing management system sends a response rejecting the billing request to the acceleration server.
Step 412, the acceleration server generates log information for recording the charging request as an illegal request based on the response of rejecting the charging request, and ends the charging process.
In summary, on the acceleration server side, after receiving the service data of the application to be charged and the enterprise client identifier of the application to be charged, sent by the SDK, the acceleration server executing the acceleration service collects charging information for the service data to obtain charging data of the service data, and then sends a charging request to the charging management system, where the charging request includes the charging data and authentication information of the first security certificate, so that the charging management system performs charging statistics on the target charging data after determining that the charging data is the target charging data. When the application to be charged is in the running state, the method finishes the collection and reporting work of the charging data through the acceleration server, and reduces the performance loss of the terminal application. And meanwhile, before the charging process is started, the charging management system side firstly determines the validity of the verification acceleration service through an SDK authentication process in the terminal application, and then ensures the validity of the charging data reported by the acceleration server and the benefit of enterprise clients through the authentication process of the acceleration server and the charging management system.
Corresponding to the foregoing method, an embodiment of the present invention further provides an acceleration service apparatus, where the apparatus is located in a cloud server, and as shown in fig. 5, the apparatus may include: a receiving unit 510, an acquisition unit 520 and a transmitting unit 530.
The receiving unit 510 is configured to receive the service data of the application to be charged and the identifier of the application to be charged, which are sent by the SDK.
The collecting unit 520 is configured to collect charging information of the service data and obtain charging data of the service data.
A sending unit 530, configured to send a charging request to the charging management system, where the charging request includes charging data and authentication information of the first security authentication, the authentication information of the first security authentication includes the device identifier, the authentication information of the first security authentication is used for the charging management system to determine, according to the device identifier, that the charging data is target charging data, and the charging request is used to request the charging management system to perform charging statistics on the target charging data.
Optionally, the authentication information of the first security authentication includes an acceleration server identifier, and the authentication information of the first security authentication is used by the charging management system to determine that the charging data is the target charging data.
Optionally, the sending unit 530 is specifically configured to send the charging request to the charging management system after the first preset time period.
Optionally, the apparatus further comprises a generating unit 540.
The receiving unit 510 is further configured to receive a response sent by the charging management system to reject the charging request.
A generating unit 540 configured to generate log information for recording the charging request as an illegal request based on the response rejecting the charging request.
Optionally, the apparatus may further comprise a presentation unit 550.
A presentation unit 550, configured to, after the generation unit 540 generates log information for recording the charging request as an illegal request, present the log information to the enterprise client logged in the apparatus.
Therefore, after receiving the service data of the application to be charged and the enterprise client identifier of the application to be charged, which are sent by the SDK, the acceleration server executing the acceleration service collects charging information of the service data to obtain charging data of the service data, and then sends a charging request to the charging management system, where the charging request includes the charging data and authentication information of the first security certificate, so that the charging management system performs charging statistics on the target charging data after determining that the charging data is the target charging data. When the application to be charged is in the running state, the method finishes the collection and reporting work of the charging data through the acceleration server, and reduces the performance loss of the terminal application.
Corresponding to the foregoing method, an embodiment of the present invention further provides a charging management apparatus, where the apparatus is located in a cloud server, and as shown in fig. 6, the apparatus may include: a receiving unit 610, an obtaining unit 620, a matching unit 630, a determining unit 640 and a counting unit 650.
The receiving unit 610 is configured to receive authentication information of the second security certificate sent by the software development kit SDK.
The obtaining unit 620 is configured to obtain a security authentication result according to authentication information of the second security authentication, so as to trigger the SDK to start the acceleration service, where the authentication information of the second security authentication includes an application identifier to be charged.
The receiving unit 610 is further configured to receive a charging request sent by the acceleration server, where the charging request includes charging data and authentication information of the first security certificate.
The matching unit 630 is configured to match the authentication information of the first security authentication with the pre-stored authentication information of the first security authentication.
And the determining unit 640 is configured to determine that the charging data is the target charging data if the matching is successful.
A statistical unit 650, configured to perform charging statistics on the target charging data, and generate statistical data.
Optionally, the charging data is acquired by the acceleration server by collecting charging information of the service data of the application to be charged, and the authentication information of the first security certificate includes an identification of the acceleration server.
Optionally, the obtaining unit 620 is specifically configured to match the authentication information of the second security authentication with the pre-stored authentication information of the second security authentication; if the matching is successful, triggering the SDK to start the acceleration service for carrying out charging statistics.
Therefore, when the application to be charged is in the running state, the charging data is collected and reported through the acceleration server, the performance loss of the terminal application is reduced, the legality of the acceleration service is ensured through the authentication process of the SDK and the charging management system, the validity of the charging data reported by the acceleration server is ensured through the authentication process of the acceleration server and the charging management system, and the benefit of enterprise clients is ensured.
An embodiment of the present invention further provides an electronic device, as shown in fig. 7, including a processor 710, a communication interface 720, a memory 730, and a communication bus 740, where the processor 710, the communication interface 720, and the memory 730 complete mutual communication through the communication bus 740.
A memory 730 for storing a computer program;
the processor 710 is configured to implement the execution process of each functional unit in fig. 5 or fig. 6 when executing the program stored in the memory 730.
It can be seen that when the application to be charged is in the running state, the acceleration server completes the collection and reporting of the charging data, reduces the performance loss of the terminal application, ensures the validity of the acceleration service through the authentication process of the SDK and the charging management system, and ensures the validity of the charging data reported by the acceleration server through the authentication process of the acceleration server and the charging management system, thereby ensuring the benefit of enterprise clients.
In yet another embodiment provided by the present application, a billing system is also provided, and the system may include the acceleration server and the billing management system in fig. 3.
In another embodiment provided by the present application, a computer-readable storage medium is further provided, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the instructions cause the computer to perform the charging method for a terminal application according to any one of the foregoing embodiments.
In another embodiment provided by the present application, there is also provided a computer program product containing instructions, which when run on a computer, causes the computer to execute the charging method for a terminal application according to any one of the above embodiments.
As will be appreciated by one of skill in the art, the embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all changes and modifications that fall within the true scope of the embodiments of the present application.
It is apparent that those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the embodiments of the present application and their equivalents, the embodiments of the present application are also intended to include such modifications and variations.
Claims (17)
1. A charging method for a terminal application is characterized in that the method comprises the following steps:
the method comprises the steps that an acceleration server receives an acceleration service request sent by a Software Development Kit (SDK), wherein the acceleration service request comprises service data of an application to be charged and an application identifier to be charged;
if the acceleration server is in a normal service state, the acceleration server sends a response for receiving the acceleration service request to the SDK, and collects charging information of the service data to acquire the charging data of the service data;
if the charging information collection of the service data is selected, after the collection is finished, the acceleration server sends a charging request to a charging management system in real time or after a preset time period according to the working state of the acceleration server, wherein the charging request comprises the charging data and authentication information of first security authentication, and the charging request is used for requesting the charging management system to carry out charging statistics on target charging data;
the authentication information of the first security certificate comprises an acceleration server identifier, and the authentication information of the first security certificate is used for the charging management system to determine that the charging data is the target charging data.
2. The method of claim 1, wherein the application identifier to be billed is an enterprise client identifier to which the application to be billed belongs.
3. The method of claim 1, wherein said sending a charging request to a charging management system comprises:
and sending a charging request to the charging management system after the first preset time period.
4. The method of claim 1 or 3, wherein after sending the charging request to the charging management system, the method further comprises:
receiving a response of refusing the charging request sent by the charging management system;
and generating log information for recording the charging request as an illegal request based on the response of rejecting the charging request.
5. The method of claim 4, wherein after generating log information that records the charging request as an illegal request based on the response rejecting the charging request, the method further comprises:
and displaying the log information to the enterprise client logging in the acceleration server.
6. A charging method for a terminal application is characterized in that the method comprises the following steps:
the charging management system receives authentication information of a second security certificate sent by the software development kit SDK;
acquiring a security authentication result according to the authentication information of the second security authentication to trigger the SDK to start acceleration service, wherein the authentication information of the second security authentication comprises an application identifier to be charged;
receiving a charging request sent by an acceleration server, wherein the charging request comprises charging data and authentication information of first security authentication, and the charging request is used for requesting the charging management system to perform charging statistics on target charging data;
matching the authentication information of the first security certificate with the pre-stored authentication information of the first security certificate;
if the matching is successful, determining the charging data as target charging data;
carrying out charging statistics on the target charging data to generate statistical data;
when the acceleration server is in a normal service state, sending a response for receiving the acceleration service request to the SDK according to the acceleration service request sent by the SDK, and acquiring charging information of service data to acquire the charging data of the service data; if the charging information collection of the service data is selected, after the collection is finished, the acceleration server sends a charging request to a charging management system in real time or after a preset time period according to the working state of the acceleration server.
7. The method of claim 6, wherein the charging data is obtained by the acceleration server performing charging information collection on service data of an application to be charged, and the authentication information of the first security certificate includes an acceleration server identifier.
8. The method as claimed in claim 6, wherein said obtaining an authentication result according to the authentication information of the second security authentication comprises:
matching the authentication information of the second security certificate with the pre-stored authentication information of the second security certificate;
if the matching is successful, triggering the SDK to start acceleration service so as to carry out charging statistics.
9. An acceleration server, characterized in that the acceleration server comprises:
the system comprises a receiving unit, a service charging unit and a charging unit, wherein the receiving unit is used for receiving an acceleration service request sent by a Software Development Kit (SDK), and the acceleration service request comprises service data of an application to be charged and an application identifier to be charged;
acquisition unit forIf it isIf the acceleration server is in a normal service state, sending a response for receiving the acceleration service request to the SDK, and acquiring charging information of the service data to acquire the charging data of the service data;
the system comprises a sending unit, a charging management system and a charging unit, wherein the sending unit is used for sending a charging request to the charging management system in real time or within a preset time period according to the working state of the acceleration server after the acquisition is finished, the charging request comprises charging data and authentication information of first security authentication, and the charging request is used for requesting the charging management system to carry out charging statistics on target charging data;
the authentication information of the first security certificate comprises an acceleration server identifier, and the authentication information of the first security certificate is used for the charging management system to determine that the charging data is target charging data.
10. An acceleration server according to claim 9, characterized in that the application identity to be billed is an enterprise client identity to which the application to be billed belongs.
11. The acceleration server of claim 9, wherein the sending unit is configured to send a charging request to the charging management system after a first preset time period.
12. An acceleration server according to claim 9 or 11, characterized in that the acceleration server further comprises a generation unit;
the receiving unit is further configured to receive a response of rejecting the charging request sent by the charging management system;
and the generating unit is used for generating log information for recording the charging request as an illegal request based on the response of rejecting the charging request.
13. An acceleration server according to claim 12, characterized in that the acceleration server further comprises a presentation unit;
the display unit is used for displaying the log information to the enterprise client logging in the acceleration server after the generation unit generates the log information recording the charging request as an illegal request.
14. An apparatus for billing management, the apparatus comprising:
the receiving unit is used for receiving authentication information of the second security certificate sent by the software development kit SDK;
the obtaining unit is used for obtaining a security authentication result according to the authentication information of the second security authentication so as to trigger the SDK to start an acceleration service, wherein the authentication information of the second security authentication comprises an application identifier to be charged;
the receiving unit is further configured to receive a charging request sent by the acceleration server, where the charging request includes charging data and authentication information of the first security certificate, and the charging request is used to request the charging management system to perform charging statistics on target charging data;
the matching unit is used for matching the authentication information of the first safety certificate with the pre-stored authentication information of the first safety certificate;
the determining unit is used for determining the charging data as target charging data if the matching is successful;
the statistical unit is used for carrying out charging statistics on the target charging data to generate statistical data;
when the acceleration server is in a normal service state, sending a response for receiving the acceleration service request to the SDK according to the acceleration service request sent by the SDK, and acquiring charging information of service data to acquire the charging data of the service data; if the charging information collection of the service data is selected, after the collection is finished, the acceleration server sends a charging request to a charging management system in real time or after a preset time period according to the working state of the acceleration server.
15. The apparatus of claim 14, wherein the charging data is obtained by the acceleration server performing charging information collection on service data of an application to be charged, and the authentication information of the first security certificate includes an acceleration server identifier.
16. The apparatus according to claim 14, wherein the obtaining unit is configured to match authentication information of the second security certificate with pre-stored authentication information of the second security certificate;
and if the matching is successful, determining to perform charging statistics, and triggering the SDK to start acceleration service so as to perform charging statistics.
17. A charging system, characterized in that the system comprises an acceleration server performing the charging method of any of claims 1 to 5 and a charging management system performing the charging method of any of claims 6 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810072792.1A CN108366176B (en) | 2018-01-25 | 2018-01-25 | Charging method, device and system for terminal application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810072792.1A CN108366176B (en) | 2018-01-25 | 2018-01-25 | Charging method, device and system for terminal application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108366176A CN108366176A (en) | 2018-08-03 |
| CN108366176B true CN108366176B (en) | 2020-07-10 |
Family
ID=63006909
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810072792.1A Expired - Fee Related CN108366176B (en) | 2018-01-25 | 2018-01-25 | Charging method, device and system for terminal application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108366176B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109450991A (en) * | 2018-10-19 | 2019-03-08 | 网宿科技股份有限公司 | Data transmission acceleration method, relevant device and acceleration system based on mobile application |
| CN109756857B (en) * | 2019-01-04 | 2021-07-20 | 中国联合网络通信集团有限公司 | Charging method and system based on mobile network acceleration |
| CN110930185A (en) * | 2019-11-15 | 2020-03-27 | 新华三技术有限公司 | Tester management method, system and device |
| CN111309758B (en) * | 2020-01-19 | 2024-02-13 | 北京金堤科技有限公司 | Charging data verification comparison method and device |
| CN114584398B (en) * | 2022-04-28 | 2022-08-02 | 新华三人工智能科技有限公司 | Charging management method and system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101132291A (en) * | 2006-08-26 | 2008-02-27 | 华为技术有限公司 | Charging system, charging point and method for charging point reporting user's charging information |
| CN101325780A (en) * | 2007-06-15 | 2008-12-17 | 华为技术有限公司 | Method and system for implementing tactics control, entity for executing tactics and charging |
| CN101800964A (en) * | 2009-02-10 | 2010-08-11 | 华为软件技术有限公司 | Charging method, device and system as well as content/service server |
| CN103248495A (en) * | 2012-02-10 | 2013-08-14 | 中国移动通信集团公司 | In-app paying method, server, client side and system |
| CN103634773A (en) * | 2013-11-25 | 2014-03-12 | 华为技术有限公司 | Safe charging implementation method and device |
| CN103826213A (en) * | 2012-11-16 | 2014-05-28 | 深圳市华营数字商业有限公司 | Application program charging point generation, protection and verification method based on digital signature |
| CN106572453A (en) * | 2015-10-09 | 2017-04-19 | 中国电信股份有限公司 | Content charging method, charging network element, SP server and charging system |
-
2018
- 2018-01-25 CN CN201810072792.1A patent/CN108366176B/en not_active Expired - Fee Related
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101132291A (en) * | 2006-08-26 | 2008-02-27 | 华为技术有限公司 | Charging system, charging point and method for charging point reporting user's charging information |
| CN101325780A (en) * | 2007-06-15 | 2008-12-17 | 华为技术有限公司 | Method and system for implementing tactics control, entity for executing tactics and charging |
| CN101800964A (en) * | 2009-02-10 | 2010-08-11 | 华为软件技术有限公司 | Charging method, device and system as well as content/service server |
| CN103248495A (en) * | 2012-02-10 | 2013-08-14 | 中国移动通信集团公司 | In-app paying method, server, client side and system |
| CN103826213A (en) * | 2012-11-16 | 2014-05-28 | 深圳市华营数字商业有限公司 | Application program charging point generation, protection and verification method based on digital signature |
| CN103634773A (en) * | 2013-11-25 | 2014-03-12 | 华为技术有限公司 | Safe charging implementation method and device |
| CN106572453A (en) * | 2015-10-09 | 2017-04-19 | 中国电信股份有限公司 | Content charging method, charging network element, SP server and charging system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108366176A (en) | 2018-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108366176B (en) | Charging method, device and system for terminal application | |
| US11966916B2 (en) | Resource transfer method and apparatus, storage medium, and computer device | |
| CN110941844B (en) | Authentication method, system, electronic equipment and readable storage medium | |
| CN107086979B (en) | User terminal verification login method and device | |
| CN106600275B (en) | Risk identification method and device | |
| CN108259618B (en) | Synchronous data interaction processing method and device | |
| CN109639719B (en) | Identity verification method and device based on temporary identifier | |
| CN109166040B (en) | Transaction auditing method, device, equipment and storage medium based on block chain | |
| CN109936556B (en) | Monitoring method and device for account stealing event | |
| CN104933207A (en) | Method and system for acquiring user behavior data in application | |
| CN106850518B (en) | Security authentication method and device | |
| CN105516135A (en) | Method and device used for account login | |
| CN114004319A (en) | Rail transit riding verification method, system and device | |
| WO2016188325A1 (en) | Data charging method and apparatus | |
| CN108009406B (en) | Account freezing method, account unfreezing method and server | |
| CN114157693A (en) | Power-on authentication method of communication equipment, communication module and server | |
| CN105812380A (en) | Verification method and device | |
| CN113067802A (en) | User identification method, device, equipment and computer readable storage medium | |
| CN106878099B (en) | Traffic management method, terminal equipment, server and system | |
| CN107864146A (en) | A kind of safe cloud storage system | |
| CN114554251B (en) | Multimedia data requesting method and device, storage medium and electronic device | |
| CN105227305B (en) | Security verification method and device | |
| WO2014177098A1 (en) | Application software online payment processing method and system | |
| CN111835765B (en) | Verification method and device | |
| US20170026524A1 (en) | Charging method and apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20200710 Termination date: 20220125 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |