Digital hard wallet security module, acquirer system and offline transaction data batch synchronization method

Abstract

The application relates to the technical field of electronic networks, in particular to a digital hard wallet security module, a collecting system, and a method for batch synchronization of offline transaction data, which comprises the following steps: in response to receiving a synchronization data instruction sent by a collecting device, the digital hard wallet transmits offline transaction data corresponding to a piece of / one synchronization batch of offline transaction flow to the collecting device, so that the collecting device synchronously uploads the offline transaction data to a digital renminbi background for accounting; in response to receiving a new coin string obtained by the digital renminbi background after accounting and issued by the collecting device, the digital hard wallet security module stores the new coin string and deletes the offline transaction data corresponding to the piece of / one synchronization batch of offline transaction flow, so as to complete the offline transaction indicated by the piece of / one synchronization batch of transaction flow. The application can improve the number of offline transactions of the digital hard wallet security module and avoid affecting the experience of users on the digital hard wallet security module.

Description

Technical Field

[0001] This application relates to the field of electronic network technology, and in particular to a digital hard wallet security module, an acquiring system, and a method for batch synchronization of offline transaction data. Background Technology

[0002] The digital yuan, tentatively abbreviated as "e-CNY" according to international convention, is a digital form of legal tender issued by the People's Bank of China. It is operated by designated institutions and exchanged with the public. Based on a broad account system, it supports loosely coupled functions of bank accounts, is equivalent to paper money and coins, possesses value characteristics and legal tender status, and supports controlled anonymity. A significant feature of the digital yuan is its ability to make payments offline. For example, after conducting two offline transactions, offline acquiring terminals store the offline transaction data in the secure module of the digital hard wallet.

[0003] Since the digital hard wallet security module itself cannot directly connect to the digital RMB backend, it requires the use of acquiring devices to upload offline transaction data stored within the digital hard wallet security module to the digital RMB backend. Meanwhile, due to compatibility considerations, the digital RMB backend largely retains the processing interfaces of the existing bank backends. This results in a limitation that the amount of offline transaction data received at one time cannot exceed 10KB, becoming a bottleneck. Modifying the existing bank backends is risky and costly, so the digital RMB backend, even when connected to the existing bank backends, still has the limitation of receiving no more than 10KB of offline transaction data at one time. This further limits the number of offline transactions that the digital hard wallet security module can perform, thus impacting the user experience.

[0004] Therefore, without requiring banks to upgrade their back-end systems, how to increase the number of offline transactions that the security module of a digital hard wallet can handle, and avoid affecting the user's offline transaction experience, is a technical problem that those skilled in the art need to solve. Summary of the Invention

[0005] This application provides a digital hard wallet security module, an acquiring system, and a method for batch synchronization of offline transaction data, in order to increase the number of offline transactions that the digital hard wallet security module can perform without the need for bank back-end modifications and upgrades, thus avoiding impacting the user's offline transaction experience.

[0006] To solve the above-mentioned technical problems, this application provides the following technical solution:

[0007] A method for batch synchronization of offline transaction data, applied to the security module side of a digital hard wallet, includes the following steps: Step S120: In response to receiving a synchronization data instruction sent by an acquiring terminal, the digital hard wallet transmits offline transaction data corresponding to one / one batch of offline transaction flows to the acquiring terminal, so that the acquiring terminal synchronously uploads the one / one batch of offline transaction data to the digital RMB backend for calculation; Step S130: In response to receiving a new coin string issued by the acquiring terminal and calculated by the digital RMB backend, the digital hard wallet security module stores the new coin string and deletes the offline transaction data corresponding to the one / one batch of offline transaction flows to complete the offline transaction indicated by the one / one batch of offline transaction flows.

[0008] The offline transaction data batch synchronization method described above preferably includes, before step S120: step S110, in response to the power-on of the digital hard wallet security module, or in response to the amount of offline transaction data stored in the digital hard wallet security module reaching a predetermined value, the digital hard wallet security module sends a request to the acquiring device to synchronize data, so that the acquiring device sends a synchronization data instruction.

[0009] In the offline transaction data batch synchronization method described above, preferably, the request for data synchronization includes the number of offline transaction records / synchronization batches stored in the digital hard wallet security module, so that the acquiring device knows how many times it should send synchronization data instructions to the digital hard wallet security module.

[0010] In the offline transaction data batch synchronization method described above, preferably, in response to receiving an instruction from the acquiring device to obtain the number of offline transaction records / synchronization batches, the digital hard wallet security module sends the number of offline transaction records / synchronization batches stored therein to the acquiring device, so that the acquiring device knows how many times it should send synchronization data instructions to the digital hard wallet security module.

[0011] In the offline transaction data batch synchronization method described above, preferably, the offline transaction count / synchronization batch number acquisition indication is sent by the acquiring device after receiving a request from the digital hard wallet security module to synchronize data.

[0012] In the offline transaction data batch synchronization method described above, preferably, the digital hard wallet security module organizes the offline transaction data corresponding to one or more offline transaction flows into synchronization batches, and ensures that the data volume of the offline transaction data corresponding to each organized synchronization batch is less than the single data limit that the digital RMB backend can receive.

[0013] The offline transaction data batch synchronization method described above preferably further includes the following steps: Step S310: Determine whether the digital hard wallet security module has a synchronization batch formed by offline transaction data; Step S320: If the digital hard wallet security module has a synchronization batch, determine whether the synchronization batch can accommodate the offline transaction data corresponding to the current offline transaction flow; Step S330: If the synchronization batch can accommodate the offline transaction data corresponding to the current offline transaction flow, organize the offline transaction data corresponding to the current offline transaction flow into the synchronization batch; Step S340: If the digital hard wallet security module does not have a synchronization batch, or if the existing synchronization batch cannot accommodate the offline transaction data corresponding to the current offline transaction flow, create a new synchronization batch and organize the offline transaction data corresponding to the current offline transaction flow into the new synchronization batch.

[0014] A digital hard wallet security module is characterized by performing the offline transaction data batch synchronization method as described in any of the preceding claims.

[0015] A method for batch synchronization of offline transaction data, applied to the acquiring system side, includes the following steps: Step S420: The acquiring device sends a synchronization data instruction to the digital hard wallet security module; Step S430: In response to receiving the synchronization data instruction sent by the acquiring device, the digital hard wallet transmits offline transaction data corresponding to one / one batch of offline transaction flows to the acquiring device; Step S440: In response to receiving the offline transaction data corresponding to one / one batch of offline transaction flows transmitted by the digital hard wallet security module, the acquiring device synchronously uploads the offline transaction data to the digital RMB backend for calculation to obtain a new coin string; Step S450: In response to receiving the new coin string calculated by the digital RMB backend, the acquiring device sends the new coin string to the digital hard wallet security module; Step S460: In response to receiving the new coin string sent by the acquiring device, the digital hard wallet security module stores the new coin string and deletes the offline transaction data corresponding to the one / one batch of offline transaction flows to complete the offline transaction indicated by the one / one batch of offline transaction flows.

[0016] In the offline transaction data batch synchronization method described above, preferably, the acquiring device sends a synchronization data instruction to the digital hard wallet security module in response to receiving a request from the digital hard wallet security module for data synchronization, or in response to the completion of the offline transaction indicated by the previous / previous synchronization batch transaction flow.

[0017] The offline transaction data batch synchronization method described above preferably includes, before step S420: step S410, in response to the power-on of the digital hard wallet security module, or in response to the amount of offline transaction data stored in the digital hard wallet security module reaching a predetermined value, the digital hard wallet security module sends a request to the acquiring device to synchronize the data.

[0018] A payment acquiring system includes: a digital hard wallet security module and a payment acquiring device, the digital hard wallet security module and the payment acquiring device performing the offline transaction data batch synchronization method as described in any of the preceding claims.

[0019] In the acquiring system described above, preferably, the digital hard wallet security module is a PSAM card, the acquiring machine is a POS machine, and the PSAM card is installed in the POS machine.

[0020] Compared to the aforementioned background technology, the offline transaction data corresponding to each offline transaction in this application is relatively small and will not exceed the data transmission limit specified in the prior art. However, the amount of offline transaction data for n offline transactions stored in the digital hard wallet can be much larger than the data transmission limit (10K), and can reach the maximum storage space of the digital hard wallet security module. Therefore, this application can make full use of all the storage space of the digital hard wallet security module, increase the number of offline transactions that the digital hard wallet security module can perform without the need for bank back-end modifications and upgrades, and avoid affecting the user's experience with the digital hard wallet security module. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention. For those skilled in the art, other drawings can be obtained based on these drawings.

[0022] Figure 1 This is the flowchart of the offline transaction data batch synchronization method provided in the embodiments of this application. Figure 1 ;

[0023] Figure 2 This is a schematic diagram illustrating the relationship between offline transaction records, coin strings, and offline transaction vouchers provided in the embodiments of this application;

[0024] Figure 3 This is a flowchart of the synchronous batch organization provided in the embodiments of this application;

[0025] Figure 4 This is the flowchart of the offline transaction data batch synchronization method provided in the embodiments of this application. Figure 2 . Detailed Implementation

[0026] Embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0027] Example 1

[0028] Please see Figure 1 This application provides a method for batch synchronization of offline transaction data, applied to the digital hard money security module package side, including the following steps:

[0029] Step S110: In response to the power-on of the digital hard wallet security module, or in response to the amount of offline transaction data stored in the digital hard wallet security module reaching a predetermined value, the digital hard wallet security module sends a request to the acquiring device to synchronize data, so that the acquiring device sends a synchronization data instruction.

[0030] Offline transaction data includes: offline transaction logs, offline transaction vouchers, and / or coin strings. Each offline transaction log records one offline transaction. Specifically, an offline transaction log may include: transaction type, business type code, business category code, transaction amount, transaction timestamp, serial number, transaction index, paying wallet ID, paying wallet name, receiving wallet ID, receiving wallet name, and remarks. An offline transaction voucher is a certificate obtained during an offline transaction. When online, the digital RMB backend can use the offline transaction voucher to calculate the coin string. Specifically, an offline transaction voucher may include: transaction amount, transaction index, receiving party's public key, and paying party's signature. For example: Offline transaction voucher 1 includes: transaction amount, transaction index, receiving party's public key 1, and paying party's signature 1; Offline transaction voucher 2 includes: transaction amount, transaction index, receiving party's public key 2, and paying party's signature 2; Offline transaction voucher n-1 includes: transaction amount, transaction index, receiving party's public key n-1, and paying party's signature n-1; Offline transaction voucher n includes: transaction amount, transaction index, receiving party's public key n, and paying party's signature n. A coin string is a digital currency that has been verified and issued by the digital RMB backend after online transactions such as deposit, withdrawal, and synchronization. Specifically, a coin string can include: version, serial number, People's Bank of China signature, institutional signature, etc.

[0031] Each offline transaction record corresponds to an offline transaction voucher and / or coin string belonging to that offline transaction record. For example... Figure 2As shown, offline transaction flow 1 corresponds to a coin string 1 belonging to offline transaction flow 1, offline transaction flow 2 corresponds to an offline transaction voucher 2 belonging to offline transaction flow 2 (offline transaction voucher 2 can be a single offline transaction voucher or multiple offline transaction vouchers), and offline transaction flow 3 corresponds to a coin string 3 and an offline transaction voucher 3 belonging to offline transaction flow 3.

[0032] Offline transaction data is stored in the memory of a digital hard wallet security module (e.g., a PSAM(SE) card installed in a POS machine). The predetermined value in this application is any value greater than the maximum data that the digital RMB backend can receive at one time (e.g., 10K) and less than the maximum storage space of the memory.

[0033] In this application, synchronized data refers to the uploading of offline transaction data, such as offline transaction records, offline transaction vouchers, and cryptocurrency strings, to the digital RMB backend. This offline transaction data is generated when the acquiring device is offline (e.g., the POS machine is not connected to the digital RMB backend).

[0034] In this application, the digital hard wallet security module can respond to its power-on, or to the amount of offline transaction data stored therein reaching a predetermined value, or of course, to other conditions, by sending a request to the acquiring device to synchronize data, so that the acquiring device sends a synchronization data instruction.

[0035] Of course, the digital hard wallet security module may also not actively send a request to the acquiring device to synchronize data, but passively wait for the acquiring device to actively send a synchronization data instruction. In other words, the digital hard wallet security module does not perform step S110 but directly performs step S120.

[0036] Step S120: In response to receiving the synchronization data instruction sent by the acquiring device, the digital hard wallet transmits the offline transaction data corresponding to one / one synchronous batch of offline transaction flow to the acquiring device, so that the acquiring device can synchronously upload the offline transaction data of one / one synchronous batch to the digital RMB backend for calculation.

[0037] After receiving a data synchronization request from the digital hard wallet security module, the acquiring device needs to send a synchronization data instruction to the digital hard wallet security module. Alternatively, if the acquiring device does not receive a data synchronization request from the digital hard wallet security module, it must proactively send a synchronization data instruction to the digital hard wallet security module. However, since the digital hard wallet security module sends offline transaction data corresponding to one / one synchronization batch of offline transaction records to the acquiring device each time a synchronization data instruction is sent, the acquiring device can know how many offline transaction records or how many synchronization batches of offline transaction records are stored in the digital hard wallet security module's memory before sending the synchronization data instruction to the digital hard wallet security module. This allows the acquiring device to determine the number of synchronization data instructions it should send to the digital hard wallet security module next.

[0038] As an example, the data synchronization request sent by the digital hard wallet security module to the acquiring terminal includes the number of offline transaction records (n) / the number of synchronization batches (n) stored in the digital hard wallet security module. This allows the acquiring terminal to parse the data synchronization request and obtain the number of offline transaction records (n) / the number of synchronization batches (n), thus knowing how many times it should send a data synchronization instruction to the digital hard wallet security module.

[0039] As another example, after receiving a data synchronization request from the digital hard wallet security module, the acquiring terminal sends an offline transaction count / synchronization batch number retrieval instruction to the digital hard wallet security module; or, if the acquiring terminal does not receive a data synchronization request from the digital hard wallet security module, it proactively sends the offline transaction count / synchronization batch number retrieval instruction to the digital hard wallet security module. In response to receiving the offline transaction count / synchronization batch number retrieval instruction from the acquiring terminal, the digital hard wallet security module sends the number of offline transaction records (n) / the synchronization batch number (n) stored in its memory to the acquiring terminal, so that the acquiring terminal knows how many times it should send synchronization data instructions to the digital hard wallet security module.

[0040] Based on the above, offline transaction records are recorded in the memory of the digital hard wallet security module in chronological order to form offline transaction record records. The number of offline transaction records n stored is determined by the spacing between the head and tail of the offline transaction record.

[0041] Specifically, a variable `offNewLog` is set in memory to indicate the offset of the offline transaction log record to be written, which is the starting address of the next offline transaction log entry. A variable `offSynLog` is also set in memory to indicate the offset of the offline transaction data to be synchronized within the offline transaction log record, which is the starting address of the next offline transaction data to be synchronized and uploaded. If `offSynLog` equals `offNewLog`, it means there is no offline transaction data to be synchronized and uploaded. If `offSynLog` > `offNewLog`, the amount of offline transaction data to be synchronized and uploaded is: the end of the offline transaction log record (excluding unused space) – `offSynLog` + `offNewLog`. If `offSynLog` < `offNewLog`, the amount of offline transaction data to be synchronized and uploaded is: `offNewLog` – `offSynLog`. When `offNewLog` reaches the end of the offline transaction log record, it checks whether the space at the beginning of the offline transaction log record has been synchronized. If it has, it can loop back to the beginning of the offline transaction log record and start writing offline transaction logs from the beginning. If there is not enough remaining space at the end of the offline transaction record to record the offline transaction records, then write 0 in that segment to indicate that the space is not being used.

[0042] When writing offline transaction logs in a loop, the space available for writing data needs to be greater than the length of the data to be written (that is, to avoid the situation where variable offSynLog = variable offNewLog), so as to distinguish whether the transaction data has been synchronized.

[0043] Of course, before the acquiring device sends a synchronization data instruction to the digital hard wallet security module, it does not need to know the number of offline transaction records / synchronization batches stored in the digital hard wallet security module's memory, and can directly send the synchronization data instruction to the digital hard wallet security module. The number of times the synchronization data instruction is sent can be a predetermined number, or it can be sent until there is no offline transaction data in the digital hard wallet security module.

[0044] When the digital hard wallet security module transmits offline transaction data to the acquiring device in batches, the digital hard wallet security module needs to organize the offline transaction data corresponding to one or more offline transaction flows into batches in advance, and ensure that the data volume of the offline transaction data corresponding to each batch is less than the single data limit (10K) that the digital RMB backend can receive.

[0045] Specifically, such as Figure 3 As shown, it includes the following steps:

[0046] Step S310: Determine whether the digital hard wallet security module contains a synchronized batch formed by offline transaction data;

[0047] Since the digital RMB backend has a single data receiving limit (e.g., 10KB), if the total offline transaction data corresponding to m offline transaction flows is no greater than the single receiving limit, and the total offline transaction data corresponding to m+1 offline transaction flows is greater than the single receiving limit, then the offline transaction data corresponding to these m offline transaction flows will be organized into a single synchronization batch. Of course, each synchronization batch can hold fewer offline transaction flows, as long as the total offline transaction data contained in the synchronization batch is less than the single receiving limit of the digital RMB backend.

[0048] During offline transactions, it is necessary to check whether the storage of the digital hard wallet security module contains a synchronization batch consisting of offline transaction data corresponding to one or more offline transaction flows, in order to organize the subsequent synchronization batches.

[0049] Step S320: If the digital hard wallet security module has a synchronization batch, determine whether the synchronization batch can accommodate the offline transaction data corresponding to this offline transaction flow.

[0050] If the storage of the digital hard wallet security module contains a synchronized batch formed by offline transaction data, then check the amount of offline transaction data corresponding to the synchronized batch, and determine whether the amount of offline transaction data corresponding to this offline transaction exceeds the single data limit that the digital RMB backend can receive after adding the amount of offline transaction data corresponding to the offline transaction flow in the synchronized batch.

[0051] Step S330: If the synchronization batch can accommodate the offline transaction data corresponding to the current offline transaction flow, then organize the offline transaction data corresponding to the current offline transaction flow into the synchronization batch.

[0052] If the total amount of offline transaction data corresponding to this offline transaction flow, after adding the amount of offline transaction data organized in the synchronous batch, still does not exceed the single data limit that the digital RMB backend can receive, then the offline transaction data corresponding to this offline transaction flow will be organized into the synchronous batch.

[0053] Step S340: If the digital hard wallet security module does not have a synchronization batch, or if the existing synchronization batch cannot accommodate the offline transaction data corresponding to this offline transaction flow, a new synchronization batch is created, and the offline transaction data corresponding to this offline transaction flow is organized into the new synchronization batch.

[0054] If the storage of the digital hard wallet security module does not contain a synchronization batch composed of offline transaction data corresponding to one or more offline transaction flows, a new synchronization batch is created, and the offline transaction data corresponding to the current offline transaction flow is organized into the new synchronization batch. If the storage of the digital hard wallet security module contains a synchronization batch, but the data volume of the offline transaction data organized in the synchronization batch, after adding the data volume of the offline transaction data corresponding to the current offline transaction flow, exceeds the single data receiving limit of the digital RMB backend, a new synchronization batch is created, and the offline transaction data corresponding to the current offline transaction flow is organized into the new synchronization batch.

[0055] Since the digital hard wallet contains a synchronization batch of offline transaction data corresponding to one or more offline transaction flows, the synchronization process can be saved when transmitting offline transaction data in the form of synchronization batches, thereby saving the time of uploading offline transaction data to the digital RMB backend.

[0056] In addition, the digital hard wallet security module transmits the offline transaction data corresponding to the earliest generated offline transaction to the acquiring device in chronological order. The offline transaction data includes: offline transaction flow, offline transaction certificate and / or coin string, so that the acquiring device can synchronously upload the offline transaction flow, offline transaction certificate and / or coin string to the digital RMB backend. The digital RMB backend calculates the new coin string based on the received offline transaction data and sends the new coin string to the acquiring device, which then sends the new coin string to the digital hard wallet security module.

[0057] Step S130: In response to receiving the new currency string issued by the acquiring terminal and calculated by the digital RMB backend, the digital hard wallet security module stores the new currency string and deletes the offline transaction data corresponding to the offline transaction flow of the transaction / the synchronous batch, so as to complete the offline transaction indicated by the transaction / the synchronous batch.

[0058] Once the digital hard wallet security module receives the new coin string, it proves that the digital RMB backend has already calculated the offline transaction data corresponding to the offline transaction flow of the transaction / synchronous batch. Therefore, the offline transaction flow, offline transaction voucher and / or coin string of the transaction / synchronous batch recorded in the storage of the digital hard wallet security module are deleted, and the newly issued coin string after calculation is stored, thus completing the offline transaction indicated by the offline transaction flow of the transaction / synchronous batch.

[0059] After the offline transaction indicated by the offline transaction flow of the current / synchronous batch is completed, the acquiring device continues to send synchronization data instructions to the digital hard wallet security module to synchronize and upload the offline transaction data corresponding to the next / next synchronous batch of offline transaction flow and issue new coin strings.

[0060] Example 2

[0061] This application provides a digital hard wallet security module that performs the offline transaction data batch synchronization method described in Embodiment 1.

[0062] Example 3

[0063] Please continue reading. Figure 4 This application provides a method for batch synchronization of offline transaction data, applied to the acquiring system side. The acquiring system includes: acquiring equipment and a digital hardware wallet security module, and includes the following steps:

[0064] Step S410: In response to the power-on of the digital hard wallet security module, or in response to the amount of offline transaction data stored in the digital hard wallet security module reaching a predetermined value, the digital hard wallet security module sends a request to the acquiring device to synchronize data.

[0065] In this application, the digital hard wallet security module can respond to its power-on, or to the amount of offline transaction data stored therein reaching a predetermined value, or of course, to other conditions, by sending a request to the acquiring device to synchronize data, so that the acquiring device sends a synchronization data instruction.

[0066] Step S420: In response to receiving a request from the digital hard wallet security module to synchronize data, or in response to the completion of the offline transaction indicated by the previous / previous synchronized batch transaction, the acquiring device sends a synchronization data instruction to the digital hard wallet security module.

[0067] After receiving a request from the digital hard wallet security module to synchronize data, the acquiring device (e.g., a POS machine) needs to send a synchronization data instruction to the digital hard wallet security module. Each time a synchronization data instruction is sent, the digital hard wallet security module sends the offline transaction data corresponding to one / one synchronization batch of offline transactions to the acquiring device. Therefore, before sending a synchronization data instruction to the digital hard wallet security module, the acquiring device can also know how many offline transaction records are stored in the digital hard wallet security module's memory, or how many synchronization batches of offline transaction records are stored in the digital hard wallet security module's memory, to determine the next number of times the acquiring device will send a synchronization data instruction to the digital hard wallet security module. Thus, after completing the offline transaction indicated by one / one synchronization batch of offline transaction records, the acquiring device also sends a synchronization data instruction to the digital hard wallet security module.

[0068] As an example, the data synchronization request sent by the digital hard wallet security module to the acquiring terminal includes the number of offline transaction records (n) / the number of synchronization batches (n) stored in the digital hard wallet security module. This allows the acquiring terminal to parse the data synchronization request and obtain the number of offline transaction records (n) / the number of synchronization batches (n), thus knowing how many times it should send a data synchronization instruction to the digital hard wallet security module.

[0069] As another example, after receiving a data synchronization request from the digital hard wallet security module, the acquiring terminal sends an instruction to the digital hard wallet security module to retrieve the number of offline transaction records / synchronization batches; or, if the acquiring terminal does not receive a data synchronization request from the digital hard wallet security module, it proactively sends an instruction to the digital hard wallet security module to retrieve the number of offline transaction records / synchronization batches. In response to receiving the offline transaction record retrieval instruction from the acquiring terminal, the digital hard wallet security module sends the number of offline transaction records (n) / the number of synchronization batches (n) stored in its memory to the acquiring terminal, so that the acquiring terminal knows how many times it should send synchronization data instructions to the digital hard wallet security module. Of course, before sending synchronization data instructions to the digital hard wallet security module, the acquiring terminal may not need to know the number of offline transaction records / synchronization batches stored in the digital hard wallet security module's memory and can directly send synchronization data instructions to the digital hard wallet security module. The number of times a synchronization data indication is sent can be predetermined, or it can be sent until there is no offline transaction data in the digital hard wallet security module.

[0070] Of course, the digital hard wallet security module may also not actively send a request to the acquiring device to synchronize data, but passively wait for the acquiring device to actively send a synchronization data instruction. That is, steps S410 and S420 are not performed, but step S420' is performed directly: the acquiring device sends a synchronization data instruction to the digital hard wallet security module so that the digital hard wallet security module can transmit the offline transaction data corresponding to one / one synchronization batch of offline transaction flow.

[0071] In this scenario, the acquiring device did not receive a request from the digital hard wallet security module to synchronize data before sending the synchronization data instruction to the digital hard wallet security module. In other words, the acquiring device actively sent the synchronization data instruction to the digital hard wallet security module.

[0072] Step S430: In response to receiving the synchronization data instruction sent by the acquiring device, the digital hardware wallet transmits the offline transaction data corresponding to one / one synchronization batch of offline transaction flow to the acquiring device;

[0073] After receiving a data synchronization request from the digital hard wallet security module, the acquiring device needs to send a synchronization data instruction to the digital hard wallet security module. Alternatively, if the acquiring device does not receive a data synchronization request from the digital hard wallet security module, it must proactively send a synchronization data instruction to the digital hard wallet security module. However, since the digital hard wallet security module sends offline transaction data corresponding to one / one synchronization batch of offline transaction records to the acquiring device each time a synchronization data instruction is sent, the acquiring device can know how many offline transaction records or how many synchronization batches of offline transaction records are stored in the digital hard wallet security module's memory before sending the synchronization data instruction to the digital hard wallet security module. This allows the acquiring device to determine the number of synchronization data instructions it should send to the digital hard wallet security module next.

[0074] Of course, before the acquiring device sends a synchronization data instruction to the digital hard wallet security module, it does not need to know the number of offline transaction records / synchronization batches stored in the digital hard wallet security module's memory, and can directly send the synchronization data instruction to the digital hard wallet security module. The number of times the synchronization data instruction is sent can be a predetermined number, or it can be sent until there is no offline transaction data in the digital hard wallet security module.

[0075] When the digital hard wallet security module transmits offline transaction data to the acquiring device in batches, the digital hard wallet security module needs to organize the offline transaction data corresponding to one or more offline transaction flows into batches in advance, and ensure that the amount of offline transaction data corresponding to each batch is less than the single data limit (10K) that the digital RMB backend can receive.

[0076] Step S440: In response to receiving offline transaction data corresponding to one / one synchronous batch of offline transaction data transmitted by the digital hard wallet security module, the acquiring device synchronously uploads the offline transaction data of one / one synchronous batch to the digital RMB backend for calculation to obtain the new coin string;

[0077] Specifically, after receiving the offline transaction data corresponding to a single offline transaction flow or a synchronous batch of offline transactions transmitted by the digital hard wallet security module, the acquiring terminal synchronously uploads the offline transaction flow, offline transaction voucher, and / or coin string to the digital RMB backend. The digital RMB backend calculates the new coin string based on the received offline transaction data and then sends the new coin string to the acquiring terminal.

[0078] Step S450: In response to receiving the new currency string calculated by the digital RMB backend, the acquiring device sends the new currency string to the digital hard wallet security module;

[0079] Once the acquiring device receives the new coin string, it proves that the digital RMB backend has already calculated the offline transaction data corresponding to the offline transaction flow of that / synchronous batch. The acquiring device then sends the new coin string to the digital hard wallet security module.

[0080] Step S460: In response to receiving a new coin string from the acquiring device, the digital hard wallet security module stores the new coin string and deletes the offline transaction data corresponding to the offline transaction flow of the transaction / the synchronous batch, so as to complete the offline transaction indicated by the offline transaction flow of the transaction / the synchronous batch.

[0081] Once the digital hard wallet security module receives the new coin string, it proves that the digital RMB backend has already calculated the offline transaction data corresponding to the offline transaction flow for that / synchronous batch of offline transactions. Therefore, it deletes the offline transaction flow, offline transaction voucher, and / or coin string, etc., recorded in the digital hard wallet's storage, and stores the newly issued coin string after calculation, thus completing the offline transaction indicated by the offline transaction flow for that / synchronous batch of offline transactions. In response to the completion of the transaction indicated by the transaction flow, the acquiring device continues to send synchronization data instructions to the digital hard wallet security module to synchronize and upload the offline transaction data corresponding to the next / next synchronous batch of offline transactions and issue the new coin string.

[0082] Example 4

[0083] This application provides an acquiring system, including: a digital hard wallet security module and an acquiring device, wherein the digital hard wallet security module and the acquiring device perform the offline transaction data batch synchronization method described in Embodiment 3.

[0084] Based on the above, the preferred security module for the digital hard wallet is a PSAM(SE) card, and the preferred acquiring device is a POS machine, with the PSAM(SE) card installed in the POS machine.

[0085] In this application, since the offline transaction data corresponding to each offline transaction in each / synchronous batch is relatively small, it will not exceed the data transmission limit specified in the prior art. However, the amount of offline transaction data for n offline transactions stored in the digital hard wallet can be much larger than the data transmission limit (10K), reaching the maximum storage space of the digital hard wallet security module. Therefore, this application can fully utilize all the storage space of the digital hard wallet security module, increasing the number of offline transactions that the digital hard wallet security module can perform without requiring bank back-end modifications and upgrades, thus avoiding impacting the user experience of the digital hard wallet security module. It is obvious to those skilled in the art that this invention is not limited to the details of the above exemplary embodiments, and that the invention can be implemented in other specific forms without departing from the spirit or basic characteristics of the invention. Therefore, the embodiments should be considered exemplary and non-limiting in all respects. The scope of the invention is defined by the appended claims rather than the foregoing description, and all changes falling within the meaning and scope of the equivalents of the claims are intended to be included within the invention. No reference numerals in the claims should be construed as limiting the scope of the claims.

[0086] Furthermore, it should be understood that although this specification describes embodiments, not every embodiment contains only one independent technical solution. This narrative style is merely for clarity. Those skilled in the art should consider the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other embodiments that can be understood by those skilled in the art.

Claims

1. An offline transaction data batch synchronization method, characterized in that, Applied to the digital hard wallet security module side, including the following steps: Step S120, in response to receiving the synchronization data indication sent by the acquirer, the digital hard wallet transmits the offline transaction data corresponding to a pen / synchronization batch offline transaction flow to the acquirer as the transmission unit according to the synchronization batch, so that the acquirer synchronously uploads the offline transaction data to the digital RMB background for accounting, wherein the offline transaction data includes: offline transaction flow, offline transaction voucher and / or coin string; In the process of offline transaction, it is necessary to check whether the memory of the digital hard wallet security module has a synchronization batch formed by the offline transaction data corresponding to one or more offline transaction flows; If there is no synchronization batch, a new synchronization batch is created, and the offline transaction data corresponding to the offline transaction flow is organized into the new synchronization batch; If there is a synchronization batch, the data amount of the offline transaction data corresponding to the synchronization batch is checked, and it is judged whether the data amount of the offline transaction data corresponding to the offline transaction flow is accumulated on the basis of the data amount of the offline transaction data corresponding to the synchronization batch, and whether it exceeds the upper limit of the single receivable data of the digital RMB background; If it does not exceed the upper limit of the single receivable data of the digital RMB background, the offline transaction data corresponding to the offline transaction flow is organized into the synchronization batch; If it exceeds the upper limit of the single receivable data of the digital RMB background, a new synchronization batch is created, and the offline transaction data corresponding to the offline transaction flow is organized into the new synchronization batch; Step S130, in response to receiving the new coin string issued by the acquirer and calculated by the digital RMB background, the digital hard wallet security module stores the new coin string, and deletes the offline transaction data corresponding to the offline transaction flow, to complete the offline transaction indicated by the offline transaction flow.

2. The method of claim 1, wherein, Before step S120, it includes: Step S110, in response to the power-on of the digital hard wallet security module, or in response to the data amount of the offline transaction data stored in the digital hard wallet security module reaching a predetermined value, the digital hard wallet security module sends a request for synchronization data to the acquirer, so that the acquirer sends a synchronization data indication.

3. The method of claim 2, wherein, The request for synchronization data contains the number of offline transaction flows / synchronization batches stored in the digital hard wallet security module, so that the acquirer knows the number of times it should send the synchronization data indication to the digital hard wallet security module.

4. The method of claim 2, wherein, In response to receiving the offline transaction flow number / synchronization batch number acquisition indication sent by the acquirer, the digital hard wallet security module sends the number of offline transaction flows / synchronization batches stored by it to the acquirer, so that the acquirer knows the number of times it should send the synchronization data indication to the digital hard wallet security module.

5. An offline transaction data batch synchronization method, characterized in that, Applied to the acquirer system side, including the following steps: Step S420, the acquirer sends a synchronization data indication to the digital hard wallet security module; Step S430, in response to receiving the synchronization data indication sent by the acquirer device, the digital hardware wallet transmits the offline transaction data corresponding to the offline transaction flow indicated by the offline transaction flow corresponding to the synchronization batch to the acquirer device as a transmission unit of the synchronization batch, wherein the offline transaction data includes: offline transaction flow, offline transaction voucher and / or coin string; In the process of offline transaction, it is necessary to check whether there is a synchronization batch formed by offline transaction data corresponding to one or more offline transaction flows in the memory of the digital hardware wallet security module; If there is no synchronization batch, a new synchronization batch is created, and the offline transaction data corresponding to the offline transaction flow is organized into the new synchronization batch; If there is a synchronization batch, the data amount of the offline transaction data corresponding to the synchronization batch is checked, and it is judged whether the data amount of the offline transaction data corresponding to the offline transaction flow is accumulated on the basis of the data amount of the offline transaction data corresponding to the synchronization batch, and whether it exceeds the upper limit of the single receivable data of the digital RMB background; If it does not exceed the upper limit of the single receivable data of the digital RMB background, the offline transaction data corresponding to the offline transaction flow is organized into the synchronization batch; If it exceeds the upper limit of the single receivable data of the digital RMB background, a new synchronization batch is created, and the offline transaction data corresponding to the offline transaction flow is organized into the new synchronization batch; Step S440, in response to receiving the offline transaction data corresponding to the offline transaction flow transmitted by the digital hardware wallet security module, the acquirer device synchronously uploads the offline transaction data to the digital RMB background for accounting to obtain a new coin string; Step S450, in response to receiving the new coin string accounted by the digital RMB background, the acquirer device issues the new coin string to the digital hardware wallet security module; Step S460, in response to receiving the new coin string issued by the acquirer device, the digital hardware wallet security module stores the new coin string, and deletes the offline transaction data corresponding to the offline transaction flow, to complete the offline transaction indicated by the offline transaction flow.

6. The method of claim 5, wherein, The acquirer device sends a synchronization data indication to the digital hardware wallet security module in response to receiving the request for synchronization data sent by the digital hardware wallet security module, or in response to the completion of the offline transaction indicated by the last offline transaction flow.

7. An acquirer system, characterized by, Comprise: The digital hardware wallet security module and the acquirer device execute the offline transaction data batch synchronization method of claim 5 or 6.

Images