CN111598558B - Billing method, billing node server and payer node server - Google Patents

Billing method, billing node server and payer node server Download PDF

Info

Publication number
CN111598558B
CN111598558B CN202010402462.1A CN202010402462A CN111598558B CN 111598558 B CN111598558 B CN 111598558B CN 202010402462 A CN202010402462 A CN 202010402462A CN 111598558 B CN111598558 B CN 111598558B
Authority
CN
China
Prior art keywords
transaction
node
payer
blockchain
information
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.)
Active
Application number
CN202010402462.1A
Other languages
Chinese (zh)
Other versions
CN111598558A (en
Inventor
田新雪
肖征荣
马书惠
杨子文
董慧
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China United Network Communications Group Co Ltd
Original Assignee
China United Network Communications Group Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China United Network Communications Group Co Ltd filed Critical China United Network Communications Group Co Ltd
Priority to CN202010402462.1A priority Critical patent/CN111598558B/en
Publication of CN111598558A publication Critical patent/CN111598558A/en
Application granted granted Critical
Publication of CN111598558B publication Critical patent/CN111598558B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • 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/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Abstract

The invention discloses a billing method, a billing node server and a payer node server, wherein the method comprises the following steps: acquiring a first broadcast message sent by a transaction node of a payer from a blockchain network, wherein the first broadcast message comprises a blockchain identifier of the transaction node of the payer and first transaction information, the first transaction information is generated when the transaction node of the payer and the transaction node of a payee finish a first transaction, and the first transaction information comprises first transaction parameters; searching a blockchain account book according to the blockchain identification of the transaction node of the payer, and obtaining second transaction information of the transaction node of the payer when the transaction node of the payer carries out the last transaction, wherein the second transaction information comprises second transaction parameters; comparing the first transaction parameter with the second transaction parameter to obtain a comparison result; and determining whether to write the first transaction information into the blockchain ledger according to the comparison result. The transaction information written into the blockchain account book is ensured to be correct, and the safety and the reliability of the blockchain network are improved.

Description

Billing method, billing node server and payer node server
Technical Field
The invention relates to the technical field of blockchains, in particular to a billing method, a billing node server and a payer node server.
Background
Replay Attacks (RA), also known as Replay Attacks and Replay Attacks, refer to that an attacker sends a data packet received by the attacker to achieve the purpose of spoofing the attacker, and are mainly applied to the process of identity authentication to destroy the correctness of the authentication. The attacker can be an initiator or a third party device, and the third party device can steal the authentication credentials by utilizing network monitoring or other modes and resend the authentication credentials to the attacked, so as to acquire the information or data of the attacked. RA may occur in any communication network, one of the common ways of attack by hackers.
In the blockchain under the account system such as the ethernet, an attacker first performs a transaction (for example, a transaction is carried out from a transaction center), then grabs the data of the transaction in the blockchain network, modifies the information such as the timestamp in the data, and sends the modified transaction data to the blockchain network. Because the Hash value of the modified transaction data has changed significantly, each node in the blockchain network may consider the modified transaction data to be a new transaction. When the victim obtains the modified transaction data from the blockchain network, the modified transaction data is judged to be new transaction data because the private key signature and the public key in the transaction data are encrypted completely, and when the balance of the victim is checked to be enough, the modified transaction is considered to be legal and is transferred to the attacker, so that the account balance of the victim is deducted after multiple times of transfer. The attacker can gratuitously acquire funds of the victim, the rights and interests of the victim are damaged, and the safety and reliability of the blockchain network are reduced.
Disclosure of Invention
Therefore, the invention provides a billing method, a billing node server and a payer node server, which are used for solving the problems that the rights and interests of attacked persons are infringed and the safety and reliability of a blockchain network are reduced due to replay attacks in the blockchain network in the prior art.
To achieve the above object, a first aspect of the present invention provides a billing method, including: acquiring a first broadcast message sent by a transaction node of a payer from a blockchain network, wherein the first broadcast message comprises a blockchain identifier of the transaction node of the payer and first transaction information, the first transaction information is generated when the transaction node of the payer and the transaction node of a payee finish a first transaction, and the first transaction information comprises first transaction parameters; searching a blockchain account book according to the blockchain identification of the transaction node of the payer, and obtaining second transaction information of the transaction node of the payer when the transaction node of the payer carries out the last transaction, wherein the second transaction information comprises second transaction parameters; comparing the first transaction parameter with the second transaction parameter to obtain a comparison result; and determining whether to write the first transaction information into the blockchain ledger according to the comparison result.
In some implementations, determining whether to write the first transaction information into the blockchain ledger based on the comparison results includes: if the first transaction parameter is equal to the second transaction parameter plus one, writing the first transaction information into the blockchain ledger; otherwise, judging that the first transaction is replay attack, and not writing the first transaction information into the blockchain ledger.
In some implementations, before the step of obtaining the first broadcast message sent by the payer transaction node from the blockchain network, the method further includes: acquiring a third broadcast message sent by a transaction node of a receiver from a blockchain network, wherein the third broadcast message comprises a blockchain identification of the transaction node of the receiver and first transaction information; starting a timer to obtain waiting time; if the waiting time exceeds the preset duration, generating and sending an inquiry message to the blockchain network according to the first transaction information, so that the payer transaction node obtains the inquiry message and confirms whether the first transaction is effective according to the first transaction information.
In some implementations, obtaining a first broadcast message sent by a payer transaction node from a blockchain network includes: acquiring a first broadcast message which is sent by a payment transaction node and signed by a private key of the payment transaction node from a blockchain network; searching a blockchain account book to obtain a public key of a transaction node of a payer; and verifying the private key signature of the first broadcast message according to the public key of the transaction node of the payer, and obtaining the first broadcast message when the verification passes.
To achieve the above object, a second aspect of the present invention provides a billing method, the method comprising: determining that a first transaction is completed with a transaction node of a payee, and generating first transaction information, wherein the first transaction information comprises a first transaction parameter which is equal to a third transaction parameter added by one after the last transaction is completed; generating a first broadcast message according to the first transaction information and the block chain identification of the first transaction information; the method comprises the steps of signing a first broadcast message by using a private key of the user, sending the signed first broadcast message to a blockchain network, enabling an accounting node to acquire a first transaction parameter and a blockchain identification of a transaction node of a payer, searching a blockchain ledger according to the blockchain identification of the transaction node of the payer, acquiring a second transaction parameter of the transaction node of the payer when the transaction node of the payer carries out the last transaction, comparing the first transaction parameter with the second transaction parameter, acquiring a comparison result, and determining whether to write first transaction information into the blockchain ledger according to the comparison result.
In some implementations, the method further includes: encrypting the first transaction parameters by using the public key of the creator node to obtain a parameter encryption result; generating and sending a second broadcast message to the blockchain network according to the parameter encryption result so that the creator node obtains the first transaction parameter and the blockchain identification of the payer transaction node, and determining whether to inform the payer transaction node and the payee transaction node of stopping the first transaction according to the first transaction parameter, the blockchain identification of the payer transaction node and the transaction parameter record table stored by the creator node.
In some implementations, after the step of generating and sending the second broadcast message to the blockchain network according to the encrypted result, the method further includes: receiving alarm information sent by an initiator node, wherein the alarm information comprises a cancel operation instruction; stopping the first transaction according to the cancel operation instruction; adding the payee transaction node to the transaction blacklist.
In some implementations, the first transaction information further includes timestamp information.
To achieve the above object, a third aspect of the present invention provides an accounting node server comprising: the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a first broadcast message sent by a transaction node of a payer from a blockchain network, the first broadcast message comprises a blockchain identification of the transaction node of the payer and first transaction information, the first transaction information is generated when the transaction node of the payer and the transaction node of a payee completes a first transaction, and the first transaction information comprises first transaction parameters; the searching module is used for searching the blockchain account book according to the blockchain identification of the transaction node of the payer, and obtaining second transaction information of the transaction node of the payer when the transaction node of the payer carries out the last transaction, wherein the second transaction information comprises second transaction parameters; the comparison module is used for comparing the first transaction parameter with the second transaction parameter to obtain a comparison result; and the writing module is used for determining whether to write the first transaction information into the blockchain ledger according to the comparison result.
In order to achieve the above object, a fourth aspect of the present invention provides a payer transaction node server, including: the transaction information generation module is used for determining that a transaction node with a payee completes a first transaction and generating first transaction information, wherein the first transaction information comprises a first transaction parameter which is equal to a third transaction parameter added one after the last transaction is completed; the broadcast message generation module is used for generating a first broadcast message according to the first transaction information and the block chain identification of the first transaction information; the sending module is used for signing the first broadcast message by using the private key of the sending module, sending the signed first broadcast message to the blockchain network, enabling the accounting node to acquire the first transaction parameter and the blockchain identification of the transaction node of the payer, searching the blockchain account book according to the blockchain identification of the transaction node of the payer, acquiring the second transaction parameter of the transaction node of the payer when the transaction node of the payer carries out the last transaction, comparing the first transaction parameter with the second transaction parameter, acquiring a comparison result, and determining whether to write the first transaction information into the blockchain account book according to the comparison result.
The invention has the following advantages: according to the obtained blockchain identification of the transaction node of the payer, searching a blockchain account book, obtaining a second transaction parameter in second transaction information of the transaction node of the payer when the transaction node of the payer carries out the last transaction, and comparing the first transaction parameter with the second transaction parameter to ensure whether the first transaction is a repeated transaction which has been carried out before, namely judging whether the first transaction is replay attack or not, ensuring that the transaction information written into the blockchain account book is correct, ensuring the interests of both parties of the transaction, and improving the safety and reliability of a blockchain network.
Drawings
The accompanying drawings are included to provide a further understanding of embodiments of the disclosure, and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure, without limitation to the disclosure. The above and other features and advantages will become more readily apparent to those skilled in the art by describing in detail exemplary embodiments with reference to the attached drawings, in which:
fig. 1 is a flow chart of a billing method according to a first embodiment of the application.
Fig. 2 is a flow chart of a billing method according to a second embodiment of the application.
Fig. 3 is a block diagram of a billing node server according to a third embodiment of the application.
Fig. 4 is a block diagram showing a payment transaction node server according to a fourth embodiment of the present application.
Fig. 5 is a block diagram showing the components of a billing system according to a fifth embodiment of the application.
Fig. 6 is a flowchart of the operation method of the billing system in the fifth embodiment of the application.
In the drawings:
301: the acquisition module 302: searching module
303: the comparison module 304: writing module
401: transaction information generation module 402: broadcast message generation module
403: the sending module 501: accounting node server
502: payer transaction node server 503: payee transaction node server
504: creator node server
Detailed Description
The following describes specific embodiments of the present application in detail with reference to the drawings. It should be understood that the detailed description and specific examples, while indicating and illustrating the application, are not intended to limit the application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the application by showing examples of the application.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
Example 1
The embodiment of the application provides a billing method which can be applied to a billing node server in a blockchain network. Fig. 1 is a flowchart of a billing method in the present embodiment, including:
step 110, a first broadcast message sent by a payer transaction node is obtained from a blockchain network.
The first broadcast message includes a blockchain identifier of the payment transaction node and first transaction information, the first transaction information is information generated by the payment transaction node and the payee transaction node when the first transaction is completed, and the first transaction information includes a first transaction parameter. The first transaction parameter is equal to the number of transactions issued from the payer transaction node server, and the value of the first transaction parameter is automatically increased by one when the transaction is completed and verified.
In some implementations, a first broadcast message sent by a payer transaction node and signed by a private key of the payer transaction node is obtained from a blockchain network; searching a blockchain account book to obtain a public key of a transaction node of a payer; and verifying the private key signature of the first broadcast message according to the public key of the transaction node of the payer, and obtaining the first broadcast message when the verification passes.
The private key signature is carried out on the first broadcast message through the payment transaction node, and after the billing node receives the first broadcast message signed by the private key, the public key of the payment transaction node is used for verifying the private key signature of the first broadcast message, so that the safety of the first broadcast message is ensured, the first broadcast message cannot be obtained by the third party equipment because the public key of the payment transaction node cannot be obtained, and the leakage of the message content is avoided.
Step 120, searching the blockchain ledger according to the blockchain identifier of the payment transaction node to obtain the second transaction information of the payment transaction node when the payment transaction node performs the last transaction.
Wherein the second transaction information includes a second transaction parameter. The second transaction parameter is the number of times the payer transaction node has completed the last transaction and verified that the last transaction was truly valid.
And 130, comparing the first transaction parameter with the second transaction parameter to obtain a comparison result.
Specifically, after the comparison result is obtained, it is required to determine whether the first transaction information is truly valid based on the comparison result of the first transaction parameter and the second transaction parameter. If the first transaction parameter is determined to be equal to the second transaction parameter plus one, determining that the first transaction information is truly valid; otherwise, the transaction corresponding to the first transaction information may have an error. For example, the first transaction information is fake transaction information which is kneaded by a third party device including the past transaction information.
Step 140, determining whether to write the first transaction information into the blockchain ledger according to the comparison result.
In some implementations, if the comparison result is determined that the first transaction parameter is equal to the second transaction parameter plus one, writing the first transaction information into the blockchain ledger; otherwise, judging that the first transaction is replay attack, and not writing the first transaction information into the blockchain ledger.
It should be noted that replay attack refers to that an attacker sends a data packet that has been received by the attacker, so as to achieve the purpose of spoofing the attacker. Replay attacks are mainly applied in the process of identity authentication to destroy the correctness of transactions. For example, a third party device falsifies a transaction node of a payee and sends a request for payment to the transaction node of a payer, wherein the request comprises transaction information of a certain transaction in a historical transaction performed between the transaction node of the payee and the transaction node of the payer, but due to the existence of a first transaction parameter, an accounting node can timely determine whether the transaction is correct or not, further judge whether the transaction is recorded in a blockchain account book or not, ensure the security of the transaction and maintain the interests of both sides of the transaction.
Another possible implementation manner is provided by an embodiment of the present application, where before step 110, the method further includes:
step 150, obtaining a third broadcast message sent by the transaction node of the payee from the blockchain network.
Wherein the third broadcast message includes a blockchain identification of the payee transaction node and the first transaction information.
It should be noted that, in the process of proceeding the transaction, both the payment party transaction node and the collection party transaction node will send the transaction information corresponding to the current transaction to the accounting node, so that the accounting node can learn the specific content of the transaction conducted by each node in the blockchain network, so as to verify the correctness of each transaction.
When both parties of the transaction conduct the transaction, the transaction parameters recorded by each party are calculated according to the transaction parameters of the transaction node after the last transaction is completed, so that the accounting node takes the transaction parameters sent by the transaction node of the payer as the reference, and the correctness of the transaction parameters is ensured.
Step 160, starting a timer to obtain the waiting time.
Specifically, the accounting node presets a preset duration (e.g., 10 seconds or 20 seconds, etc.), starts a timer, and obtains a waiting time after counting a period of time.
Step 170, if the waiting time exceeds the preset duration, generating and sending an inquiry message to the blockchain network according to the first transaction information.
When the timer reaches a preset time point, namely when the waiting time exceeds a preset duration, if the accounting node does not receive the transaction information corresponding to the transaction sent by the transaction node of the payer, the accounting node actively sends an inquiry message to the blockchain network so that the transaction node of the payer can acquire the inquiry message and confirm whether the first transaction is effective according to the first transaction information.
In a specific implementation, after receiving the inquiry message, the payment transaction node executes step 110, so that the accounting node can combine the transaction information reported by the payment transaction node and the payee transaction node respectively to determine whether the transaction is normal, and write the first transaction information into the blockchain ledger when verifying that the transaction is correct.
The blockchain account book is searched according to the acquired blockchain identification of the payment party transaction node, a second transaction parameter in second transaction information of the payment party transaction node when the payment party transaction node performs the last transaction is obtained, and whether the first transaction is a repeated transaction implemented before or not can be judged by comparing the first transaction parameter with the second transaction parameter, namely whether the first transaction is replay attack or not is judged, so that the transaction information written into the blockchain account book is ensured to be correct, the interests of both transaction parties are ensured, and the safety and the reliability of the blockchain network are improved.
Example two
The embodiment of the application provides a billing method which can be applied to a payer transaction node server in a blockchain network. Fig. 2 is a flowchart of the billing method in the present embodiment, including:
step 210, determining that the first transaction is completed with the payee transaction node, and generating first transaction information.
The first transaction information comprises a first transaction parameter which is equal to a third transaction parameter added by one after the last transaction is completed. For example, the third transaction parameter is set to RRRf n-1 The first transaction parameter is set to RRRf n RRRf n ＝RRRf n-1 +1, wherein n is a positive integer greater than 1.
In some implementations, the first transaction information further includes timestamp information. The specific time of transaction corresponding to the first transaction information can be known through the time stamp information, and the number of specific transactions performed by the transaction node of the payer can be known through statistics of the time stamp information. When the number of transactions exceeds a preset range, it may be determined that the payer transaction node is likely to be attacked by a third-party device, and the attack type may be replay attack.
For example, if 60 transactions are performed by the payer transaction node within 1 minute, i.e., the time stamp information of one transaction is recorded every 1 second, it indicates that the transaction performed by the payer transaction node is too frequent to meet the conventional transaction, i.e., the payer transaction node may be attacked.
Step 220, generating a first broadcast message according to the first transaction information and the own blockchain identification.
In step 230, the first broadcast message is signed using its own private key, and the signed first broadcast message is sent to the blockchain network.
The first broadcast information is signed by the private key, the security of the information is guaranteed, the signed first broadcast information can be verified only by the corresponding public key, and the information in the first broadcast information is obtained after verification is passed. For example, the billing node server obtains the signed first broadcast message in the blockchain network. The accounting node server obtains the public key of the transaction node of the payer by searching the blockchain ledger, and verifies the private key signature of the first broadcast message according to the public key of the transaction node of the payer. And when the verification is passed, obtaining a first transaction parameter in the first broadcast message and the blockchain identification of the transaction node of the payer.
Then, the billing node server searches a blockchain account book according to the blockchain identification of the transaction node of the payer, obtains a second transaction parameter of the transaction node of the payer when the transaction node of the payer carries out the last transaction, compares the first transaction parameter with the second transaction parameter, and obtains a comparison result; judging whether the first transaction is normal and legal or not according to the comparison result, if yes, writing the first transaction information into the blockchain account book, otherwise, not writing the first transaction information into the blockchain account book, so as to ensure the correctness of the transaction information.
Another possible implementation manner is provided by an embodiment of the present application, where the accounting method may further include the following steps while performing step 230.
Step 240, encrypting the first transaction parameter by using the public key of the creator node, and obtaining a parameter encryption result.
Step 250, generating and sending a second broadcast message to the blockchain network according to the parameter encryption result.
The originator node obtains a second broadcast message from the blockchain network, and because the second broadcast message is signed using the private key of the payer transaction node, the originator node verifies the second broadcast message using the public key of the payer transaction node, and after verification, the originator node obtains the first transaction parameter and the blockchain identification of the payer transaction node. The creator node then determines whether to inform the payer transaction node and the payee transaction node to stop the first transaction based on the first transaction parameter, the blockchain identification of the payer transaction node, and the transaction parameter record table stored by the creator node.
Specifically, the creator node stores a transaction parameter list therein, where the transaction parameter list includes transaction parameters reported by each transaction node and timestamp information of each transaction node when the transaction is successfully completed. The information in the transaction parameter list is updated in real time to ensure synchronization with the transaction information of each node in the blockchain network. After the creator node obtains the decrypted first transaction parameter, searching a transaction parameter list according to the blockchain identifier of the payer transaction node, determining whether the first transaction parameter appears in the transaction parameter list, if so, indicating that the payer transaction node server which reports the second broadcast message is subjected to replay attack, and immediately stopping the transaction which is ongoing by the payer transaction node server; otherwise, the transaction currently reported to the payment side transaction node server of the second broadcast message is normal and valid, and the transaction can be continued by both sides. Thus, the creator node can play a role in supervising the transaction in the blockchain network, and ensure the normal and effective transaction.
Embodiments of the present application provide another possible implementation, where following step 250 may be included.
In step 260, the alarm information sent by the creator node is received, where the alarm information includes a cancel operation instruction.
It should be noted that, when the creator node obtains the decrypted first transaction parameter and determines that the first transaction parameter has appeared in the transaction parameter list, the creator node will send out an alarm message to alert both parties to the transaction. The alert information may include "current transaction has an abnormal problem, and needs to be noted.
Step 270, stopping the first transaction according to the cancel operation instruction.
Step 280, adding the payee transaction node to the transaction blacklist.
Specifically, the creator node adds the payee transaction node to the transaction blacklist, or the creator node takes a deposit submitted by the payee transaction node in the blockchain network as a fine and withholds the deposit to ensure that the payee transaction node will not use replay attacks to attack other transaction nodes.
In this embodiment, after the payment transaction node and the payee transaction node complete the first transaction, the first transaction parameter is generated, so that the accounting node can determine whether the current transaction is a normal transaction according to the first transaction parameter and the second transaction parameter of the payment transaction node when the payment transaction node performs the last transaction. Under the condition that the transaction information is legal, the first transaction information is written into the blockchain account book, so that the benefits of both transaction parties are guaranteed, and the security of the blockchain network is improved. Meanwhile, the creator node automatically maintains a transaction parameter list stored in the creator node, and when a first transaction parameter sent by a payer transaction node is obtained, the transaction parameter list is searched, whether the first transaction parameter is a parameter corresponding to a completed transaction is determined, the authenticity of the transaction is ensured, and the payer transaction node can avoid unnecessary economic loss and improve the transaction safety through timely alarming.
Example III
Fig. 3 is a schematic structural diagram of an accounting node server according to an embodiment of the present application, and the implementation of the server may be referred to the description related to the first embodiment, and the repetition is omitted. It should be noted that the specific implementation of the server in this embodiment is not limited to the above embodiments, and other non-illustrated embodiments are also within the scope of protection of the server.
As shown in fig. 3, the accounting node server comprises in particular: the acquiring module 301 is configured to acquire, from a blockchain network, a first broadcast message sent by a payment transaction node, where the first broadcast message includes a blockchain identifier of the payment transaction node and first transaction information, where the first transaction information is information generated by the payment transaction node and a payee transaction node when completing a first transaction, and the first transaction information includes a first transaction parameter; the searching module 302 is configured to search a blockchain ledger according to the blockchain identifier of the payment transaction node, and obtain second transaction information of the payment transaction node when performing the last transaction, where the second transaction information includes a second transaction parameter; the comparison module 303 is configured to compare the first transaction parameter and the second transaction parameter to obtain a comparison result; the writing module 304 is configured to determine whether to write the first transaction information into the blockchain ledger according to the comparison result.
In this embodiment, the search module is enabled to search the blockchain ledger according to the blockchain identifier of the payer transaction node obtained by the obtaining module, obtain the second transaction parameter in the second transaction information of the payer transaction node when the last transaction is performed, and then compare the first transaction parameter with the second transaction parameter by the comparing module, so as to determine whether the first transaction is a repeated transaction implemented before, that is, determine whether the first transaction is a replay attack, so as to ensure that the transaction information written into the blockchain ledger is correct, thereby ensuring the rights of both parties of the transaction, and improving the security and reliability of the blockchain network.
It is to be noted that this embodiment mode is an embodiment of the apparatus corresponding to the first embodiment mode, and this embodiment mode can be implemented in cooperation with the first embodiment mode. The related technical details mentioned in the first embodiment are still valid in this embodiment, and in order to reduce repetition, they are not repeated here. Accordingly, the related technical details mentioned in the present embodiment can also be applied in the first embodiment.
Example IV
Fig. 4 is a schematic structural diagram of a server for a transaction node of a payer, and the implementation of the server can be referred to the description of the second embodiment, and the repetition is omitted. It should be noted that the specific implementation of the server in this embodiment is not limited to the above embodiments, and other non-illustrated embodiments are also within the scope of protection of the server.
As shown in fig. 4, the payer transaction node server specifically includes: the transaction information generating module 401 is configured to determine that the transaction node with the payee completes a first transaction, and generate first transaction information, where the first transaction information includes a first transaction parameter, and the first transaction parameter is equal to a third transaction parameter added by one after the last transaction is completed; a broadcast message generating module 402, configured to generate a first broadcast message according to the first transaction information and the own blockchain identifier; the sending module 403 is configured to sign the first broadcast message by using its private key, send the signed first broadcast message to the blockchain network, so that the accounting node obtains the first transaction parameter and the blockchain identifier of the transaction node of the payer, search the blockchain ledger according to the blockchain identifier of the transaction node of the payer, obtain the second transaction parameter of the transaction node of the payer when performing the last transaction, compare the first transaction parameter with the second transaction parameter, obtain a comparison result, and determine whether to write the first transaction information into the blockchain ledger according to the comparison result.
In this embodiment, the transaction information generating module generates the first transaction parameter after the payment side transaction node and the payment side transaction node complete the first transaction, and sends the first broadcast message carrying the first transaction parameter to the blockchain network, so that the accounting node can determine whether the transaction is a normal transaction according to the first transaction parameter in the first broadcast message and the second transaction parameter of the payment side transaction node when the payment side transaction node performs the last transaction after acquiring the first broadcast message. Under the condition that the transaction information is legal, the first transaction information is written into the blockchain account book, so that the benefits of both transaction parties are guaranteed, and the security of the blockchain network is improved.
It is to be noted that the present embodiment is an example of the apparatus corresponding to the second example, and the present embodiment can be implemented in cooperation with the second example. The related technical details mentioned in the second embodiment are still valid in this embodiment, and in order to reduce repetition, they are not repeated here. Accordingly, the related technical details mentioned in the present embodiment can also be applied in the second embodiment.
It should be noted that each module in this embodiment is a logic module, and in practical application, one logic unit may be one physical unit, or may be a part of one physical unit, or may be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present application, units that are not so close to solving the technical problem presented by the present application are not introduced in the present embodiment, but this does not indicate that other units are not present in the present embodiment.
Example five
An embodiment of the present application provides an accounting system, and fig. 5 is a block diagram of the accounting system, specifically including: an accounting node server 501, a payer transaction node server 502, a payee transaction node server 503, and an creator node server 504.
It should be noted that, after the payment side transaction node server 502 and the payment side transaction node server 503 complete the transaction, the payment side transaction node server 502 will automatically record the transaction parameters corresponding to the current transaction, and report the transaction parameters to the accounting node server 501, so that the accounting node server 501 confirms the correctness of the transaction, and records the current transaction into the blockchain account book when determining that the transaction is correct and legal. When the payment transaction node server 502 is under replay attack, since an attacker cannot modify the transaction parameters in the payment transaction node server 502, after receiving the transaction parameters sent by the payment transaction node server 502, the accounting node server 501 determines whether the transaction parameters corresponding to the transaction appear in the historical transaction record, and if it is determined that the transaction parameters corresponding to the transaction appear in the historical transaction record, determines that the transaction is invalid, thereby preventing replay attack.
Specifically, fig. 6 is a flowchart of the working method of the billing system, as shown in fig. 6, specifically including the following steps.
In step 601, the payee transaction node server 503 sends a transfer transaction request to the payer transaction node server 502, hopefully the payer transaction node server 502 can transfer 5-elements to the payee transaction node server 503.
In step 602, the payer transaction node server 502 transfers 5-tuple to the payee transaction node server 503, and generates the first transaction information after determining that the transfer transaction is completed with the payee transaction node server 503.
Wherein the first transaction information comprises a first transaction parameter RRR f The first transaction parameter RRR f Equal to the third transaction parameter RRRf n-1 Adding one, i.e. RRRf n ＝RRRf n-1 +1, wherein RRRf n-1 Is a parameter of the payer transaction node server 502 after the last transaction is completed, and n is a positive integer greater than 1. The first transaction parameter is equal to the number of transactions sent from the payer transaction node server 502, and the value of the first transaction parameter is automatically incremented by one when the transaction is completed and verified.
In step 603, the payee transaction node server 503 generates a third broadcast message according to the first transaction information in step 602 and the blockchain identifier of the payee transaction node server 503, signs the third broadcast message using the private key of the payee transaction node server 503, and sends the signed third broadcast message to the blockchain network, so that the billing node server 501 receives the third broadcast message.
Wherein the first transaction information further includes a transaction parameter RRR of the payee transaction node server 503 S Transaction parameters RRRs for payee n Is the transaction parameter RRRs of the last transaction after the completion of the last transaction by the payee transaction node server 503 n-1 And adding one to obtain the transaction parameters.
In step 604, after the accounting node server 501 obtains the third broadcast information sent by the payee transaction node server 503 from the blockchain network, the blockchain identifier and the first transaction information of the payee transaction node server 503 are obtained by analyzing the third broadcast information.
Step 605, the accounting node server 501 starts a timer, hopefully receives the first transaction information sent by the payer transaction node server 502 within a preset time period (e.g. within 10 seconds or 20 seconds), and obtains the first transaction parameter RRRf of the payer transaction node server 502 n . When the waiting time exceeds the preset duration, the billing node server 501 does not receive the first transaction information sent by the payment transaction node server 502, and the billing node server 501 generates and sends an inquiry message to the blockchain network according to the first transaction information, so that the payment transaction node server 502 can receive the inquiry message.
In step 606, the payer transaction node server 502 generates a first broadcast message according to the first transaction information generated in step 602 and the blockchain identifier of the payer transaction node server 502, signs the first broadcast message using its private key, and sends the signed first broadcast message to the blockchain network, so that the billing node server 501 can receive the first broadcast message.
Step 607, the billing node server 501 parses the first broadcast message to obtain the blockchain identification and the first transaction parameter RRRf of the payer transaction node server 502 n . The accounting node server 501 searches the blockchain ledger according to the blockchain identifier of the payer transaction node server 502 to obtain second transaction information of the payer transaction node server 502 when the last transaction is performed, wherein the second transaction information comprises a second transaction parameter RRRf n-1 By comparing the first transaction parameters RRRf n And a second transaction parameter RRRf n-1 Obtaining a comparison result, if the comparison result is that the first transaction parameter is equal to the second transaction parameter plus one, namely RRRf n ＝RRRf n-1 +1, determining that the first transaction information is truly valid, and writing the transaction corresponding to the first transaction information into the blockchain ledger by the accounting node server 501; otherwise, it indicates that the transaction corresponding to the first transaction information is a replay attack, that is, fake transaction information made by the third party device including the previous transaction information, and the accounting node server 501 does not write the transaction corresponding to the first transaction information into the blockchain ledger.
Step 608, while executing step 606, the payer transaction node server 502 uses the public key of the creator node server 504 to pair the first transaction parameter RRRf n Encrypting to obtain a parameter encryption result; then, the payer transaction node server 502 generates and sends a second broadcast message to the blockchain network according to the parameter encryption result, so that the creator node server 504 can obtain the second broadcast message and supervise the change condition of the first transaction parameter of the payer transaction node server 502 according to the second broadcast message.
Before sending the second broadcast message to the blockchain network, the payer transaction node server 502 also signs the second broadcast message with its private key to ensure the security of the transmission of the second broadcast message in the blockchain network.
Step 609, the creator node server 504 verifies the private key signature of the received second broadcast message by using the public key of the payer transaction node server 502, and after the verification is passed, the creator node server 504 decrypts the parameter encryption result in the second broadcast message by using its private key to obtain the first transaction information, wherein the first transaction information includes the first transaction parameter RRRf n 。
It should be noted that, the creator node server 504 stores a transaction parameter list therein, where the transaction parameter list includes transaction parameters reported by each transaction node and timestamp information of each transaction node when the transaction is successfully completed. And, each item of information in the transaction parameter list is updated in real time to ensure that the information of each node in the blockchain network can be synchronized.
When the originator node server 504 obtains the decrypted first transaction parameter RRRf n Thereafter, the blockchain identification of the payer transaction node server 502 is used to search the transaction parameter list to determine the first transaction parameter RRRf n Whether or not it has appeared in the list of transaction parameters, if it is determined that the first transaction parameter RRRf n If the transaction information has been found in the transaction parameter list, it indicates that the transaction corresponding to the first transaction information is a replay attack, the transaction needs to be terminated immediately, and step 610 is performed; otherwise, the transaction is indicated to be normal and valid, and the transaction parties can continue the transaction. In this way, the creator node server 504 can play a role in supervising transactions in the blockchain network, ensuring that the transactions are normal and valid.
Step 610, generating and sending alarm information to the blockchain network according to the first transaction information and the result obtained by searching the transaction parameter list, so that the payer transaction node server 502 and the payee transaction node server 503 receive the alarm information.
The alarm information includes a cancel operation instruction for stopping the transaction between the two parties (i.e., the payor transaction node server 502 and the payee transaction node server 503). Meanwhile, the creator node server 504 adds the payee transaction node server 503 to the transaction blacklist, or the creator node server 504 takes the deposit submitted by the payee transaction node server 503 in the blockchain network as a fine and withholds the deposit to ensure that the payee transaction node server 503 will not use replay attacks to attack other transaction nodes.
In this embodiment, the accounting node server searches the blockchain account book according to the obtained blockchain identifier of the payment party transaction node, obtains the second transaction parameter in the second transaction information of the payment party transaction node when the payment party transaction node performs the last transaction, and can determine whether the first transaction is a replay attack by comparing the first transaction parameter with the second transaction parameter, so as to ensure that the transaction information written into the blockchain account book is correct, ensure the rights of both parties of the transaction, and improve the security and reliability of the blockchain network. Meanwhile, the creator node server automatically maintains a transaction parameter list stored in the creator node server, and searches the transaction parameter list according to the obtained first transaction parameter sent by the payer transaction node server, so that whether the first transaction parameter is a parameter corresponding to the completed transaction can be determined, the authenticity of the transaction is ensured, the payer transaction node server can avoid unnecessary economic loss through timely alarming, and the safety of the blockchain network is improved.
It is to be understood that the above embodiments are merely illustrative of the application of the principles of the present application, but not in limitation thereof. Various modifications and improvements may be made by those skilled in the art without departing from the spirit and substance of the application, and are also considered to be within the scope of the application.

Claims (3)

1. A billing method, the method comprising:
acquiring a first broadcast message sent by a transaction node of a payer from a blockchain network, wherein the first broadcast message comprises a blockchain identifier of the transaction node of the payer and first transaction information, the first transaction information is generated when the transaction node of the payer and the transaction node of a payee completes a first transaction, and the first transaction information comprises a first transaction parameter;
searching a blockchain account book according to the blockchain identification of the payment transaction node to obtain second transaction information of the payment transaction node when performing the last transaction, wherein the second transaction information comprises second transaction parameters;
comparing the first transaction parameter with the second transaction parameter to obtain a comparison result;
determining whether to write the first transaction information into the blockchain ledger according to the comparison result;
wherein, according to the comparison result, determining whether to write the first transaction information into the blockchain ledger includes:
if the comparison result is that the first transaction parameter is equal to the second transaction parameter plus one, writing the first transaction information into the blockchain ledger;
Otherwise, judging that the first transaction is a replay attack, and not writing the first transaction information into the blockchain ledger;
before the step of obtaining the first broadcast message sent by the transaction node of the payer in the slave blockchain network, the method further comprises the following steps:
acquiring a third broadcast message sent by a transaction node of a receiver from a blockchain network, wherein the third broadcast message comprises a blockchain identification of the transaction node of the receiver and the first transaction information;
starting a timer to obtain waiting time;
if the waiting time exceeds the preset duration, generating and sending an inquiry message to a blockchain network according to the first transaction information so that the payer transaction node obtains the inquiry message and confirms whether the first transaction is effective according to the first transaction information.
2. The method of claim 1, wherein obtaining the first broadcast message sent by the payer transaction node from the blockchain network comprises:
acquiring a first broadcast message which is sent by the payer transaction node and signed by a private key of the payer transaction node from a blockchain network;
Searching a blockchain account book to obtain a public key of the transaction node of the payer;
and verifying the private key signature of the first broadcast message according to the public key of the payer transaction node, and obtaining the first broadcast message when the verification passes.
3. An accounting node server, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a first broadcast message sent by a transaction node of a payer from a blockchain network, the first broadcast message comprises a blockchain identification of the transaction node of the payer and first transaction information, the first transaction information is generated when the transaction node of the payer and the transaction node of the payee finish a first transaction, and the first transaction information comprises a first transaction parameter;
the searching module is used for searching a blockchain account book according to the blockchain identification of the transaction node of the payer to obtain second transaction information of the transaction node of the payer when the transaction node of the payer carries out the last transaction, wherein the second transaction information comprises second transaction parameters;
the comparison module is used for comparing the first transaction parameter with the second transaction parameter to obtain a comparison result;
the writing module is used for determining whether to write the first transaction information into the blockchain ledger according to the comparison result;
Wherein, according to the comparison result, determining whether to write the first transaction information into the blockchain ledger includes:
if the comparison result is that the first transaction parameter is equal to the second transaction parameter plus one, writing the first transaction information into the blockchain ledger;
otherwise, judging that the first transaction is a replay attack, and not writing the first transaction information into the blockchain ledger;
before the step of obtaining the first broadcast message sent by the transaction node of the payer in the slave blockchain network, the method further comprises the following steps:
acquiring a third broadcast message sent by a transaction node of a receiver from a blockchain network, wherein the third broadcast message comprises a blockchain identification of the transaction node of the receiver and the first transaction information;
starting a timer to obtain waiting time;
if the waiting time exceeds the preset duration, generating and sending an inquiry message to a blockchain network according to the first transaction information so that the payer transaction node obtains the inquiry message and confirms whether the first transaction is effective according to the first transaction information.
CN202010402462.1A 2020-05-13 2020-05-13 Billing method, billing node server and payer node server Active CN111598558B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010402462.1A CN111598558B (en) 2020-05-13 2020-05-13 Billing method, billing node server and payer node server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010402462.1A CN111598558B (en) 2020-05-13 2020-05-13 Billing method, billing node server and payer node server

Publications (2)

Publication Number Publication Date
CN111598558A CN111598558A (en) 2020-08-28
CN111598558B true CN111598558B (en) 2023-08-22

Family

ID=72188736

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010402462.1A Active CN111598558B (en) 2020-05-13 2020-05-13 Billing method, billing node server and payer node server

Country Status (1)

Country Link
CN (1) CN111598558B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112261427B (en) * 2020-10-20 2022-04-29 中国联合网络通信集团有限公司 Malicious node identification method and device and electronic equipment

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107480990A (en) * 2017-08-01 2017-12-15 中国联合网络通信集团有限公司 Block chain bookkeeping methods and device
CN108765150A (en) * 2018-05-11 2018-11-06 中国联合网络通信集团有限公司 Exchange information processing method and memory node
CN108881120A (en) * 2017-05-12 2018-11-23 阿里巴巴集团控股有限公司 A kind of data processing method and equipment based on block chain
CN109584063A (en) * 2018-10-25 2019-04-05 阿里巴巴集团控股有限公司 Transaction processing method and device, electronic equipment based on block chain
CN109767220A (en) * 2019-01-15 2019-05-17 中国联合网络通信集团有限公司 Method of commerce based on block chain and the transaction system based on block chain
CN110349029A (en) * 2019-07-17 2019-10-18 中国银行股份有限公司 A kind of processing method, equipment and the system of the trade identity based on block chain
CN110458542A (en) * 2019-08-02 2019-11-15 中国工商银行股份有限公司 Offline electronic payment system and method based on block chain
CN110717832A (en) * 2019-10-21 2020-01-21 腾讯科技（深圳）有限公司 Clean energy trading method, system, device and storage medium based on block chain
CN111149122A (en) * 2018-05-30 2020-05-12 重庆小雨点小额贷款有限公司 Block chain-based security management method, related device and storage medium
US10785035B1 (en) * 2019-04-26 2020-09-22 Alibaba Group Holding Limited Anti-replay attack authentication protocol

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108881120A (en) * 2017-05-12 2018-11-23 阿里巴巴集团控股有限公司 A kind of data processing method and equipment based on block chain
CN107480990A (en) * 2017-08-01 2017-12-15 中国联合网络通信集团有限公司 Block chain bookkeeping methods and device
CN108765150A (en) * 2018-05-11 2018-11-06 中国联合网络通信集团有限公司 Exchange information processing method and memory node
CN111149122A (en) * 2018-05-30 2020-05-12 重庆小雨点小额贷款有限公司 Block chain-based security management method, related device and storage medium
CN109584063A (en) * 2018-10-25 2019-04-05 阿里巴巴集团控股有限公司 Transaction processing method and device, electronic equipment based on block chain
CN109767220A (en) * 2019-01-15 2019-05-17 中国联合网络通信集团有限公司 Method of commerce based on block chain and the transaction system based on block chain
US10785035B1 (en) * 2019-04-26 2020-09-22 Alibaba Group Holding Limited Anti-replay attack authentication protocol
CN110349029A (en) * 2019-07-17 2019-10-18 中国银行股份有限公司 A kind of processing method, equipment and the system of the trade identity based on block chain
CN110458542A (en) * 2019-08-02 2019-11-15 中国工商银行股份有限公司 Offline electronic payment system and method based on block chain
CN110717832A (en) * 2019-10-21 2020-01-21 腾讯科技（深圳）有限公司 Clean energy trading method, system, device and storage medium based on block chain

Also Published As

Publication number Publication date
CN111598558A (en) 2020-08-28

Similar Documents

Publication Publication Date Title
JP4546240B2 (en) User authentication method and system using challenge / response method
KR101019006B1 (en) Certify and split system and method for replacing cryptographic keys
JP2018121328A (en) Event certificate for electronic device
CN108737442A (en) A kind of cryptographic check processing method
CN102868531B (en) Networked transaction certification system and method
CN108243176B (en) Data transmission method and device
CN109687965A (en) The real name identification method of subscriber identity information in a kind of protection network
CN109754226B (en) Data management method, device and storage medium
CN114244527B (en) Block chain-based electric power Internet of things equipment identity authentication method and system
CN105447715A (en) Method and apparatus for anti-theft electronic coupon sweeping by cooperating with third party
CN114362993B (en) Block chain assisted Internet of vehicles security authentication method
CN111538784A (en) Block chain-based digital asset transaction method and device and storage medium
WO2013120317A1 (en) Message filtering method and system
CN111148094B (en) Registration method of 5G user terminal, user terminal equipment and medium
CN111080299B (en) Anti-repudiation method for transaction information, client and server
CN111831974A (en) Interface protection method and device, electronic equipment and storage medium
US10122755B2 (en) Method and apparatus for detecting that an attacker has sent one or more messages to a receiver node
CN106657002A (en) Novel crash-proof base correlation time multi-password identity authentication method
CN110213232B (en) fingerprint feature and key double verification method and device
CN111598558B (en) Billing method, billing node server and payer node server
CN110572392A (en) Identity authentication method based on HyperLegger network
WO2015076715A1 (en) Method and system for synchronization of two databases in a lawful interception network by comparing checksum values
CN112383577A (en) Authorization method, device, system, equipment and storage medium
CN111371555A (en) Signature authentication method and system
CN111510302A (en) Method and system for improving certificate verification efficiency in secure communication protocol

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