Bill processing method under data API cross-service request scene

Abstract

The invention discloses a bill processing method in a data API (Application Program Interface) cross-service request scene, relates to an information technology, and solves the technical problems that the existing data API cross-service request scene is not disclosed, opaque and insufficient in reliability. The method comprises the following steps: S11, authenticating a data API (Application Program Interface) associated party through a block chain technology, and requesting authorization for the authenticated data API associated party; and S12, generating multiple bills according to the authorized data API associated party, and integrating the multiple bills to generate a summarized bill. According to the method, the tampering resistance of the data is ensured, the credibility of the bill data is enhanced, the bill is fully automatically generated, manual accounting links are reduced, the error rate is reduced, and the processing efficiency is improved.

Description

Technical Field

[0001] The present invention relates to information technology, and more specifically, to a bill processing method in a data API cross-service request scenario. Background Art

[0002] Currently, in the data API product transaction scenario, the bill is generally generated based on the basic data generated by the API interface call and processed by the logic algorithm. The existing technology focuses on the storage, transmission, and processing logic optimization of the basic data. In the scenario where the data API involves cross-service requests (that is, one data API connects to multiple different service provider interfaces), users need to connect to different service providers separately, generate multiple bills, and process multiple different bills accordingly. In this scenario, conventional bill processing methods have the shortcomings of low efficiency and prone to errors. In the prior art, such as patent CN202410847703.1 "A bill processing method for data API cross-service request scenarios", although it solves the problem of bill allocation, it still has the following major defects in the data API cross-service request scenario:

[0003] 1. Non-disclosure and opacity: Users cannot view detailed information about the bill generation process in real time. There is a lack of transparency in the bill generation process, making it difficult to trust the bills generated by the system.

[0004] 2. Insufficient reliability: When processing cross-service requests, existing methods may cause data loss or errors due to network fluctuations or unstable service provider interfaces, affecting the accuracy and completeness of bills.

[0005] To address these issues, an improved approach is urgently needed to increase the efficiency, reliability, and transparency of bill processing while ensuring data security and user privacy. Summary of the invention

[0006] The technical problem to be solved by the present invention is to provide a bill processing method in a data API cross-service request scenario in response to the shortcomings of the existing technology, so as to solve the technical problems of non-disclosure, opacity and insufficient reliability in the existing data API cross-service request scenario.

[0007] The present invention provides a bill processing method in a data API cross-service request scenario, the method comprising:

[0008] S11: Authenticate the data API associated party through blockchain technology, and request authorization from the authenticated data API associated party;

[0009] S12: Generate multiple bills according to the authorized data API associated parties, and integrate the multiple bills to generate a summary bill.

[0010] As a further improvement, in S11, the method for authenticating the data API associated party is:

[0011] S21: Authentication of the identity information of the data API associated party and the identity information of the data service provider;

[0012] S22: Allocate an identity and a key to the data API associated party that has passed the identity authentication, and associate the identity with a corresponding business number.

[0013] Furthermore, in S21, the identity information of the data API associated party is authenticated through a smart contract based on blockchain technology.

[0014] Furthermore, in S22, a public key is generated based on the data API associated party that has passed the identity authentication and using the asymmetric encryption technology in the blockchain technology, and the public key is used as the authorization credential of the data API associated party.

[0015] Furthermore, it is characterized in that, in S11, the method of requesting authorization for the data API associated party that has passed the authentication is:

[0016] S31: Performing authorization verification on the authorization credentials of the data API associated party that has passed the authentication;

[0017] S32: Record and store the requests and responses of the data API associated parties that have passed the verification.

[0018] Furthermore, it is characterized in that, in S31, the method for performing authorization verification on the authorization credential of the data API associated party that has passed the authentication is to compare the public key of the data API associated party with the public key of the entity, and when the public key of the data API associated party is consistent with the public key of the entity, it is determined that the data API associated party has passed the authorization verification;

[0019] When the public key of the data API associated party is inconsistent with the public key of the entity, it is determined that the data API associated party fails the authorization verification.

[0020] Furthermore, it is characterized in that in S32, the method for recording and storing the requests and responses of the data API associated parties that have passed the verification is to package the request and response records of the data API associated parties into blocks, broadcast the blocks through the blockchain network, and store the blocks on the blockchain through the consensus mechanism of the blockchain.

[0021] Furthermore, it is characterized in that in S12: a plurality of bills are automatically generated according to the authorized data API associated parties, and a method for integrating the plurality of bills to generate a summary bill is:

[0022] S41: Setting the time interval for generating the bill;

[0023] S42: Generate a bill according to the time interval;

[0024] S43: querying the request and response data of the data API associated party according to the business number;

[0025] S44: Calculate the corresponding bill according to the request and response data of the data API associated party;

[0026] S45: Integrate bills to generate summary bills through smart contracts in blockchain technology;

[0027] S46: Storing the summary bill in the blockchain.

[0028] Furthermore, it is characterized in that in S44, the request and response data of the data API associated party include the total amount, number of requests, unit price, data volume and service type fee, and the expression for calculating the corresponding bill according to the request and response data of the data API associated party is,

[0029] Total amount = ∑(number of requests × unit price + data volume × unit price + service type fee).

[0030] Furthermore, it is characterized in that the data service provider is notified via SMS to confirm the summary bill.

[0031] Beneficial Effects

[0032] The advantages of the present invention are:

[0033] The present invention authenticates data API associated parties, requests authorization from data API associated parties that have passed the authentication, generates multiple bills based on the authorized data API associated parties, integrates the multiple bills to generate a summary bill, ensures that data cannot be tampered with, enhances the credibility of bill data, generates bills fully automatically, reduces manual accounting steps, reduces error rates, and improves processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 A flowchart of data API related party authentication and request authorization of the present invention;

[0035] Figure 2 An integrated flow chart is automatically generated for the bill of the present invention. DETAILED DESCRIPTION

[0036] The present invention will be further described below in conjunction with the embodiments, but it does not constitute any limitation to the present invention. Any limited number of modifications made by anyone within the scope of the claims of the present invention are still within the scope of the claims of the present invention.

[0037] See also Figure 1-Figure 2 The present invention provides a bill processing method for a data API cross-service request scenario, which includes two processes: data API associated party on-chain authentication, authorization, and automatic bill generation and integration.

[0038] like Figure 1 As shown in the figure, the process of data API related party authentication and authorization is as follows:

[0039] S11. Identity verification and authorization: Use blockchain technology to verify the identity information of data API users and data service providers to ensure the legitimacy of business relationships. The specific methods are as follows:

[0040] S111. Use blockchain-based smart contracts to verify submitted registrations, including but not limited to corporate registration information, legal person information, corporate legal person face recognition, etc.

[0041] S112. The submitted information is verified through the preset logic in the smart contract, and only entities that pass the verification can obtain further operation permissions.

[0042] S12. Key application and distribution: Assign identities and keys to each authenticated party, and associate the identities with the business numbers. The key distribution mainly uses the asymmetric encryption technology of blockchain to generate a pair of public and private keys for each authenticated entity. The private key is kept by the entity and used to sign transactions; the public key is used to verify the validity of the signature.

[0043] S13. Request authorization and forwarding: The integrated gateway receives the data API request, verifies the authorization certificate through the blockchain, and forwards the request to the destination data service according to the policy. The specific method is as follows:

[0044] S131. After receiving the request, the gateway first verifies whether the authorization certificate carried in the request is valid.

[0045] S132. The validity of the authorization credential is verified by comparing the signature in the request with the entity's public key.

[0046] S133: After the verification is passed, the gateway forwards the request to the corresponding data service according to the preset strategy.

[0047] S14. Request and response records: Record and store the requests and responses of the data API users, and store them on the blockchain. The specific method is as follows:

[0048] S141. Pack the request and response data into blocks and broadcast them through the blockchain network.

[0049] S142. Use the consensus mechanism of blockchain to ensure the consistency and immutability of data.

[0050] S143. Store relevant information on the blockchain.

[0051] like Figure 2 As shown, the specific process for automatically generating bills and integrating them is as follows:

[0052] S21. Bill generation strategy: According to the preset bill generation strategy, query the correspondence between the data API and the cross-service data service through the chain block height. The specific method is as follows:

[0053] S211. Set the time interval and conditions for bill generation, such as generating bills daily, weekly or monthly.

[0054] S212. The management tool automatically triggers the bill generation task according to the set time interval.

[0055] S22, data detail screening and bill generation: Screen out the basic request data details of each user-data service, and generate multiple bills based on the details and bill generation rules. The specific method is as follows:

[0056] S221. Query the relevant request and response data details according to the business number.

[0057] S222. Apply the preset bill generation rules, such as billing by request times, data volume or service type, to calculate the bill for each user. The specific calculation formula is:

[0058] Total amount = ∑(number of requests × unit price + data volume × unit price + service type fee).

[0059] S23. Bill integration: Integrate multiple bills into a summary bill and store it on the blockchain. The specific method is as follows:

[0060] S231, Integration and Evidence Storage: Use smart contracts to integrate various bills, ensure the consistency and accuracy of bills, automatically obtain the height of the current blockchain, and record it in the bill.

[0061] Current block height = blockchain node API (getBlockHeight).

[0062] S232. The integrated summary bill is stored on the blockchain to ensure the immutability and transparency of the bill.

[0063] S24. Bill confirmation and electronic signature.

[0064] S241. Notify the relevant data service providers via SMS to confirm the billing data, and affix an electronic signature on the management tool interface.

[0065] S242. Use smart contracts to manage the bill confirmation process to ensure that only authorized entities can confirm bills.

[0066] S243. After the bill is confirmed, use electronic signature technology to ensure the legitimacy and non-repudiation of the bill.

[0067] The present invention improves the reliability of bill data, ensures the immutability of data through blockchain technology, and enhances the credibility of bill data. It improves bill processing efficiency, generates bills automatically, reduces manual accounting links, reduces error rates, and improves processing efficiency.

[0068] The above is only a preferred embodiment of the present invention. It should be pointed out that for those skilled in the art, several modifications and improvements can be made without departing from the structure of the present invention, which will not affect the effect of the implementation of the present invention and the practicality of the patent.

Claims

1. A bill processing method in a data API cross-service request scenario, characterized in that: The method includes, S11: Authenticate the data API associated party through blockchain technology, and request authorization from the authenticated data API associated party; S12: Generate multiple bills according to the authorized data API associated parties, and integrate the multiple bills to generate a summary bill.

2. According to claim 1, a bill processing method in a data API cross-service request scenario is characterized in that: In S11, the method for authenticating the data API associated party is: S21: Authentication of the identity information of the data API associated party and the identity information of the data service provider; S22: Allocate an identity and a key to the data API associated party that has passed the identity authentication, and associate the identity with a corresponding business number.

3. According to the bill processing method in a data API cross-service request scenario described in claim 2, in S21, the identity information of the data API associated party is authenticated through a smart contract based on blockchain technology.

4. According to claim 2, a bill processing method in a data API cross-service request scenario is characterized in that: In S22, a public key is generated based on the data API associated party that has passed the identity authentication and using the asymmetric encryption technology in the blockchain technology, and the public key is used as the authorization credential of the data API associated party.

5. According to claim 4, a bill processing method in a data API cross-service request scenario is characterized in that: In S11, the method of requesting authorization from the data API associated party that has passed the authentication is: S31: Performing authorization verification on the authorization credentials of the data API associated party that has passed the authentication; S32: Record and store the request and response data of the data API associated party that has passed the authorization verification.

6. The bill processing method in a data API cross-service request scenario according to claim 5, characterized in that: In S31, the method for performing authorization verification on the authorization credential of the data API associated party that has passed the authentication is to compare the public key of the data API associated party with the public key of the entity. When the public key of the data API associated party is consistent with the public key of the entity, it is determined that the data API associated party has passed the authorization verification; When the public key of the data API associated party is inconsistent with the public key of the entity, it is determined that the data API associated party fails the authorization verification.

7. The bill processing method in a data API cross-service request scenario according to claim 5, characterized in that: In S32, the method for recording and storing the request and response data of the data API associated party that has passed the authorization verification is to package the request and response data of the data API associated party into blocks, broadcast the blocks through the blockchain network, and store the blocks on the blockchain through the consensus mechanism of the blockchain.

8. The bill processing method in a data API cross-service request scenario according to claim 7, characterized in that: In S12: a method of automatically generating multiple bills according to the authorized data API associated party and integrating the multiple bills to generate a summary bill is as follows: S41: Setting the time interval; S42: Generate a bill according to the time interval; S43: querying the request and response data of the data API associated party according to the business number; S44: Calculate the corresponding bill according to the request and response data of the data API associated party; S45: Integrate bills to generate summary bills through smart contracts in blockchain technology; S46: Storing the summary bill in the blockchain.

9. The bill processing method in a data API cross-service request scenario according to claim 8, characterized in that: In S44, the request and response data of the data API associated party include the total amount, number of requests, unit price, data volume and service type fee. The expression for calculating the corresponding bill based on the request and response data of the data API associated party is: Total amount = ∑(number of requests × unit price + data volume × unit price + service type fee).

10. The bill processing method in a data API cross-service request scenario according to claim 1, characterized in that: The data service provider is notified via SMS to confirm the summary bill.

Images