Account creation, account recharging, data synchronization method and device

Abstract

The present specification discloses an account creation, account recharge, data synchronization method and device, comprising: creating a second account for a first account contained in a specified carrier on a terminal device, and using the second account in the terminal device to realize the recharge for the first account and ensure the data consistency between the first account and the second account through a close-range communication mode.

Description

Technical Field

[0001] This specification relates to the fields of Internet information processing technology and computer technology, and in particular to a method and device for account creation, account top-up, and data synchronization. Background Technology

[0002] Cash payment, as a traditional payment method, is very familiar to everyone living in modern society. However, in some areas (such as public transportation and supermarket shopping), cash payment brings some inconvenience (such as needing to prepare enough change).

[0003] To address these inconveniences, top-up payment emerged. Top-up payment can be understood as users directly transferring money or cash from their bank accounts to a designated IC card (Integrated Circuit Card), which is then used for purchases. This method is also known as an electronic wallet. However, current top-up methods generally require performing the relevant top-up operation on a specific device.

[0004] Based on this payment method, there is an urgent need for a more convenient processing method to improve the convenience of top-up payment. Summary of the Invention

[0005] In view of this, the embodiments of this specification provide a method and device for account creation, account top-up, and data synchronization to improve the convenience of top-up payment.

[0006] The embodiments in this specification provide the following technical solutions:

[0007] This specification provides an account creation method, including:

[0008] The first terminal device obtains the account identifier of the first account from the designated carrier in a predefined manner;

[0009] The first terminal device creates an account identifier for the second account based on the account identifier of the first account;

[0010] The first terminal device establishes and stores a mapping relationship between the account identifier of the first account and the account identifier of the second account.

[0011] This specification provides an account top-up method, including:

[0012] The first terminal device establishes a data channel with a designated carrier containing the account identifier of the first account through near-field communication technology;

[0013] The first terminal device writes the recharge data of the second account into the designated carrier through the data channel to recharge the first account.

[0014] This specification provides an account top-up method, including:

[0015] The designated carrier receives recharge data sent by the first terminal device after establishing a data channel with the first terminal device through short-range communication technology;

[0016] Based on the recharge data, the balance data of the first account is processed.

[0017] This specification provides a data synchronization method in which a primary account in a server is associated with a first account in a designated carrier and a second account in a first terminal device, including:

[0018] The server obtains the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier through short-range communication.

[0019] The server receives the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device;

[0020] The server determines synchronization data for a synchronization period based on the first transaction data and the second transaction data, and sends the synchronization data to the first terminal device so that the data corresponding to the second account is consistent with the data corresponding to the main account.

[0021] This specification provides a data synchronization method, including:

[0022] The first terminal device establishes a data channel with the designated carrier through short-range communication.

[0023] The first terminal device synchronizes the balance data corresponding to the second account to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account.

[0024] This specification provides a data synchronization method, including:

[0025] The first terminal device establishes a data channel with the designated carrier through short-range communication.

[0026] The first terminal device obtains the account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier through the data channel;

[0027] The first terminal device determines the second transaction data corresponding to the second account associated with the first account;

[0028] The first terminal device synchronizes data between the first account and the second account based on the first transaction data and the second transaction data.

[0029] This specification provides an account creation device, including:

[0030] The acquisition unit acquires the account identifier of the first account from a specified carrier through a set method;

[0031] Create a unit to create an account identifier for the second account based on the account identifier of the first account;

[0032] The storage unit establishes and stores the mapping relationship between the account identifier of the first account and the account identifier of the second account.

[0033] This specification provides an account top-up device, comprising:

[0034] The unit establishes a data channel with a designated carrier containing the account identifier of the first account through near-field communication technology;

[0035] The recharge unit writes the recharge data of the second account into the designated carrier through the data channel to recharge the first account.

[0036] This specification provides an account top-up device, comprising:

[0037] The receiving unit receives recharge data sent by the first terminal device after establishing a data channel with the first terminal device through short-range communication technology.

[0038] The processing unit processes the balance data of the first account based on the recharge data.

[0039] This specification provides a data synchronization device in which a master account in a server establishes an association with a first account in a designated carrier and a second account in a first terminal device, including:

[0040] The acquisition unit acquires the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier through a short-range communication method.

[0041] The receiving unit receives the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device;

[0042] The synchronization unit determines synchronization data for a synchronization cycle based on the first transaction data and the second transaction data, and sends the synchronization data to the first terminal device so that the data corresponding to the second account is consistent with the data corresponding to the main account.

[0043] This specification provides a data synchronization device, including:

[0044] Establish a unit to establish a data channel with a designated carrier via short-range communication;

[0045] The synchronization unit synchronizes the balance data corresponding to the second account to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account.

[0046] This specification provides a data synchronization device, including:

[0047] Establish a unit to establish a data channel with a designated carrier via short-range communication;

[0048] The acquisition unit acquires the account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier through the data channel;

[0049] The determining unit determines the second transaction data corresponding to the second account associated with the first account;

[0050] The synchronization unit performs data synchronization between the first account and the second account based on the first transaction data and the second transaction data.

[0051] This specification provides an account creation device, comprising: at least one memory and at least one processor, wherein the memory stores a program configured to be executed by the processor in the following steps:

[0052] The account identifier of the first account is obtained from the specified carrier through a set method;

[0053] Create an account identifier for the second account based on the account identifier of the first account;

[0054] Establish and store the mapping relationship between the account identifier of the first account and the account identifier of the second account.

[0055] This specification provides an account top-up device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to execute the following steps by the processor:

[0056] A data channel is established with a designated carrier containing the account identifier of the first account through near-field communication technology;

[0057] The recharge data of the second account is written into the designated carrier through the data channel to recharge the first account.

[0058] This specification provides an account top-up device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to execute the following steps by the processor:

[0059] When a data channel is established with the first terminal device through short-range communication technology, the recharge data sent by the first terminal device is received;

[0060] Based on the recharge data, the balance data of the first account is processed.

[0061] This specification provides a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to be executed by the processor in the following steps:

[0062] The account identifier of the first account and the first transaction data corresponding to the first account are obtained from the designated carrier through a near-field communication method.

[0063] Receive the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device;

[0064] Based on the first transaction data and the second transaction data, a synchronization data for a synchronization period is determined, and the synchronization data is sent to the first terminal device so that the data corresponding to the second account is consistent with the data corresponding to the main account;

[0065] The server establishes an association between the main account contained in the server and the first account contained in the designated carrier and the second account contained in the first terminal device.

[0066] This specification provides a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to be executed by the processor in the following steps:

[0067] Establish a data channel with a designated carrier through short-range communication methods;

[0068] The balance data corresponding to the second account is synchronized to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account.

[0069] This specification provides a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to be executed by the processor in the following steps:

[0070] Establish a data channel with a designated carrier through short-range communication methods;

[0071] The account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier are obtained through the data channel.

[0072] Determine the second transaction data corresponding to the second account associated with the first account;

[0073] Based on the first transaction data and the second transaction data, data synchronization is performed between the first account and the second account.

[0074] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

[0075] By creating a second account on a terminal device for a first account contained in a specified carrier, and utilizing the second account on the terminal device, a near-field communication method is used to recharge the first account and ensure data consistency between the first and second accounts. In other words, assuming the first account is an account stored in a specified carrier, and the second account is a virtual electronic account associated with the first account, then a user can complete transactions using either the first or the second account. Furthermore, the technical solution provided in the embodiments of this specification ensures data consistency between the two accounts, thereby improving the user's payment experience. Attached Figure Description

[0076] The accompanying drawings, which are included to provide a further understanding of this specification and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0077] Figure 1 A flowchart illustrating an account creation method provided in an embodiment of this specification;

[0078] Figure 2 A flowchart illustrating an account top-up method provided in an embodiment of this specification;

[0079] Figure 3 A flowchart illustrating an account top-up method provided in an embodiment of this specification;

[0080] Figure 4(a) is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification;

[0081] Figure 4(b) is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification;

[0082] Figure 5 This is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification.

[0083] Figure 6(a) is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification;

[0084] Figure 6(b) is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification;

[0085] Figure 7 This is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification.

[0086] Figure 8 This is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification.

[0087] Figure 9 This is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification.

[0088] Figure 10 This is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification.

[0089] Figure 11 This is a schematic diagram of the structure of an account creation device provided in an embodiment of this specification;

[0090] Figure 12 This is a schematic diagram of the structure of an account recharge device provided in an embodiment of this specification;

[0091] Figure 13 This is a schematic diagram of the structure of an account recharge device provided in an embodiment of this specification;

[0092] Figure 14 This is a schematic diagram of the structure of a data synchronization device provided in an embodiment of this specification;

[0093] Figure 15 This is a schematic diagram of the structure of a data synchronization device provided in an embodiment of this specification;

[0094] Figure 16 This is a schematic diagram of the structure of a data synchronization device provided in an embodiment of this specification. Detailed Implementation

[0095] While mobile payment solutions offer convenience, they also present some inconveniences for users. For example, if a user doesn't have a mobile device or their device is out of power, they cannot make payments. This means that if card payments and mobile payments could complement each other, it would greatly benefit users' daily lives and work.

[0096] However, with the development of internet technology, a new payment method has emerged: electronic payment. Electronic payment refers to the monetary payment or fund transfer conducted by parties involved in e-commerce transactions (including consumers, manufacturers, and financial institutions) through information networks, using digital methods and secure information transmission. Compared to cash payments and prepaid payments, it offers users greater convenience.

[0097] To achieve this objective, embodiments of this specification provide a method and apparatus for account creation, account top-up, and data synchronization. This involves creating a second account on a terminal device for a first account contained in a specified carrier, and using the second account on the terminal device to top up the first account and ensure data consistency between the first and second accounts via near-field communication. In other words, assuming the first account is an account hosted on a specified carrier, and the second account is a virtual electronic account associated with the first account, then a user can complete transactions using either the first or the second account. Furthermore, the technical solution provided by these embodiments ensures data consistency between the two accounts, thereby improving the user's payment experience.

[0098] It should be noted that the technical solutions described in the embodiments of this specification can be applied in public transportation scenarios, as well as in other application scenarios involving similar IC card applications, without specific limitations here.

[0099] An IC card (Integrated Circuit Card), also known as a smart card, is characterized by its readability, writability, large capacity, encryption, reliable data recording, and ease of use. For example, a public transport card. Users can use a public transport card to pay for fares. When the public transport card interacts with the card reader, the card reads the value and deducts the fare. Currently, public transport card top-ups are generally done through a pre-load system, requiring users to visit designated top-up stations and use special equipment.

[0100] To make the objectives, technical solutions, and advantages of the embodiments in this specification clearer, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments in this specification, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments in this specification without creative effort are within the scope of protection of this application.

[0101] The technical solutions provided by the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0102] Figure 1 This is a flowchart illustrating an account creation method provided for the implementation of this specification. The method can be as follows. The execution subject of this embodiment is a terminal device.

[0103] Step 101: The first terminal device obtains the account identifier of the first account from the designated carrier through a set method.

[0104] In the embodiments described in this specification, the first terminal device obtains the account identifier of the first account from a designated carrier through a set method, including:

[0105] The first method:

[0106] The first terminal device establishes a data channel with a designated carrier through near-field communication technology, and obtains the account identifier of the first account from the designated carrier through the data channel.

[0107] The second method:

[0108] The first terminal device obtains the account identifier of the first account from the designated carrier by scanning.

[0109] The specified carrier described herein includes at least one or more of the following: a card device supporting near-field communication technology, a second terminal device containing an account identifier of the first account, and an application client containing an account identifier of the first account.

[0110] Step 103: The first terminal device creates an account identifier for the second account based on the account identifier of the first account.

[0111] In the embodiments of this specification, after obtaining the account identifier of the first account, the first terminal device can create the account identifier of the second account based on the account identifier of the first account, or it can create the account identifier of the second account separately, without any specific limitation.

[0112] The second account described herein includes one of the following: a virtual account or an electronic account.

[0113] Step 105: The first terminal device establishes and stores the mapping relationship between the account identifier of the first account and the account identifier of the second account.

[0114] In the embodiments described in this specification, the method further includes:

[0115] After obtaining the account identifier of the second account, the first terminal device establishes and stores the association between the account identifier of the second account and the application account used for payment.

[0116] Figure 2 This is a flowchart illustrating an account top-up method provided in an embodiment of this specification. The method can be as follows. The executing entity in this embodiment can be a smart terminal device, such as a mobile terminal device.

[0117] Step 201: The first terminal device establishes a data channel with a designated carrier containing the account identifier of the first account through near-field communication technology.

[0118] In the embodiments described in this specification, before establishing a data channel, the method further includes:

[0119] The first terminal device uses the application account used for payment to perform a transfer operation to the second account, generating recharge data for the second account.

[0120] The specified carrier described herein includes at least one or more of the following: a card device supporting near-field communication technology, a second terminal device containing an account identifier of the first account, and an application client containing an account identifier of the first account.

[0121] Step 203: The first terminal device writes the recharge data of the second account into the designated carrier through the data channel to recharge the first account.

[0122] Figure 3 This is a flowchart illustrating an account top-up method provided in an embodiment of this specification. The method can be as follows. The executing entity in this embodiment can be a specified carrier, such as an IC card, terminal device, etc.

[0123] Step 301: The designated carrier receives the recharge data sent by the first terminal device after establishing a data channel with the first terminal device through short-range communication technology.

[0124] Step 303: Process the balance data of the first account based on the recharge data.

[0125] In this embodiment of the specification, when the balance data of the first account is zero, the recharge data is written into the first account;

[0126] If the balance data of the first account is not zero, the balance data of the first account is modified using the recharge data.

[0127] Through the examples in this specification Figure 2 and Figure 3 The scheme described herein utilizes mobile terminal devices (such as smartphones) to recharge IC card devices, effectively avoiding the various inconveniences caused by fixed recharge devices in real life (such as long waiting times, needing to reach the location of the recharge device, etc.), thus effectively improving recharge efficiency and providing users with an excellent user experience.

[0128] Figure 4(a) is a flowchart illustrating a data synchronization method provided in an embodiment of this specification. The method can be as follows. The execution entity of this embodiment is a server, and an association is established between the main account contained in the server and the first account contained in the designated carrier and the second account contained in the first terminal device.

[0129] Assuming the server here is a public transportation server, the public transportation server can create a primary account for the user based on the user's identity. When the user applies for a public transportation card, the public transportation server can establish a mapping relationship between the primary account and the card identifier of the public transportation card (i.e., the account identifier of the first account). In addition, assuming the user creates a virtual electronic card associated with the card number of the public transportation card on the terminal device, a further mapping relationship can be established between the primary account and the card identifier of the virtual electronic card (i.e., the account identifier of the second account).

[0130] Step 401: The server obtains the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier through short-range communication.

[0131] In the embodiments described in this specification, the server establishes a data channel with the designated carrier via short-range communication.

[0132] When the server determines that a transaction has occurred, it obtains the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier through the data channel.

[0133] For example, when a user uses a public transport card to make a purchase, the transaction data of the public transport card can be sent to the server through the POS machine or card reader provided by the merchant. In this way, the server can promptly obtain the account identifier of the first account contained in the public transport card and the first transaction data corresponding to the first account.

[0134] Step 403: The server receives the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device.

[0135] Step 405: The server determines synchronization data for a synchronization period based on the first transaction data and the second transaction data, and sends the synchronization data to the first terminal device so that the data corresponding to the second account is consistent with the data corresponding to the main account.

[0136] In the embodiments described in this specification, the method further includes:

[0137] If the synchronized data is negative, a deduction request is sent to the first terminal device. The deduction request is used to request the amount corresponding to the negative number to be deducted from the application account associated with the second account for payment.

[0138] Figure 4(b) is a schematic flowchart of a data synchronization method provided in an embodiment of this specification. The method can be as follows. The execution subject of this embodiment is a terminal device.

[0139] Step 402: The first terminal device establishes a data channel with the designated carrier through short-range communication.

[0140] Step 404: The first terminal device synchronizes the balance data corresponding to the second account to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account.

[0141] In the embodiments described in this specification, before the data channel is established, the method further includes:

[0142] The first terminal device receives synchronization data sent by the server, the synchronization data being obtained by the server according to the method shown in Figure 4(a);

[0143] The first terminal device uses the synchronization data to modify the data corresponding to the second account, so that the data corresponding to the second account is consistent with the data corresponding to the main account contained in the server.

[0144] The server establishes an association between the main account contained in the server and the first account contained in the designated carrier and the second account contained in the first terminal device.

[0145] Figure 5This is a flowchart illustrating a data processing method provided in an embodiment of this specification. The method can be as follows. This embodiment uses a public transportation scenario as an example for illustration. Here, the first account corresponds to the account in the physical bus card, and the second account corresponds to the account in the virtual electronic card. An association is established between the first account and the second account.

[0146] For physical bus cards, recharge data and payment data are written into the physical bus card, meaning that the physical bus card has data storage function and can record the generated transaction data in real time; for virtual electronic cards, recharge data and payment data are stored in the terminal device, which can record the generated transaction data in real time.

[0147] Step 501: The terminal device creates a virtual electronic card associated with the physical bus card.

[0148] Step 503: Specify the carrier to use a physical bus card, obtain the first transaction data corresponding to the physical bus card, and send the first transaction data to the server.

[0149] Step 505: The terminal device uses the virtual electronic card to obtain the second transaction data corresponding to the virtual electronic card.

[0150] There is no strict execution order for steps 503 and 505. They can be implemented simultaneously, or in accordance with the method described in the embodiments of this specification. Alternatively, step 305 can be executed first, followed by step 303. No specific limitations are made here.

[0151] Step 507: The terminal device obtains the first transaction data from the server.

[0152] Step 509: The terminal device modifies the balance data in the virtual electronic card based on the first and second transaction data.

[0153] Step 511: The terminal device establishes a data channel between the physical bus card and the virtual electronic card through near-field communication.

[0154] Step 513: The terminal device uses the data channel to synchronize the modified balance data in the virtual electronic card to the physical bus card.

[0155] Figure 6(a) is a schematic flowchart of a data synchronization method provided in an embodiment of this specification. The method can be as follows. The execution subject of this embodiment is a terminal device.

[0156] Step 602: The first terminal device establishes a data channel with the designated carrier through short-range communication.

[0157] In this embodiment of the specification, before the first terminal device establishes a data channel, the method further includes:

[0158] If a change is detected in the data corresponding to the second account associated with the first account, the first terminal device sends a prompt message to remind the user to synchronize data between the first account and the second account.

[0159] Step 604: The first terminal device obtains the account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier through the data channel.

[0160] Step 606: The first terminal device determines the second transaction data corresponding to the second account associated with the first account.

[0161] In this embodiment of the specification, the account identifier of the second account that is associated with the account identifier of the first account is determined based on the account identifier of the first account;

[0162] Based on the account identifier of the second account, locate the second transaction data that corresponds to the account identifier of the second account.

[0163] Step 608: The first terminal device synchronizes data between the first account and the second account based on the first transaction data and the second transaction data.

[0164] In the embodiments of this specification, synchronization data for synchronization is calculated based on the first flow data and the second flow data;

[0165] The synchronized data is then synchronized to the first account and the second account, respectively.

[0166] If the synchronized data is negative, then empty numbers will be written to the first account and the second account respectively;

[0167] The amount corresponding to the negative number is deducted from the application account associated with the second account used for payment.

[0168] In the embodiments described in this specification, the method further includes:

[0169] Send the synchronization time, the account identifier of the first account, and the first transaction data to the server, and delete the first transaction data recorded in the carrier of the first account; and / or,

[0170] The synchronization time, the account identifier of the second account, and the second transaction data are sent to the server, and the second transaction data is deleted.

[0171] In the embodiments of this specification, the transaction data includes at least one or more of consumption data and recharge data.

[0172] Figure 6(b) is a flowchart illustrating a data processing method provided in an embodiment of this specification. The method can be described as follows. This embodiment uses a public transportation scenario as an example for illustration. Here, the first account corresponds to the account in the physical bus card, and the second account corresponds to the account in the virtual electronic card. An association is established between the first account and the second account.

[0173] For physical bus cards, recharge data and payment data are written into the physical bus card, meaning that the physical bus card has data storage function and can record the generated transaction data in real time; for virtual electronic cards, recharge data and payment data are stored in the terminal device, which can record the generated transaction data in real time.

[0174] Step 601: The terminal device creates a virtual electronic card associated with the physical bus card.

[0175] Step 603: The designated carrier uses a physical bus card, obtains and stores the first transaction data corresponding to the physical bus card; the terminal device uses a virtual electronic card, obtains and stores the second transaction data corresponding to the virtual electronic card.

[0176] Step 605: The terminal device establishes a data channel between the physical bus card and the virtual electronic card through near-field communication.

[0177] Step 607: The terminal device uses the data channel to obtain the first transaction data corresponding to the physical bus card.

[0178] Step 609: The terminal device synchronizes data between the physical bus card and the virtual electronic card based on the first and second transaction data.

[0179] Figure 5 Unlike the embodiment shown in Figure 6(b), the difference lies in the following: when the transaction data of a physical bus card is generated, it is not only stored in the physical bus card but also sent to the server corresponding to the physical bus card. When the transaction data of a virtual electronic card is generated, it is not only stored in the terminal device but also sent to the server. The terminal device containing the virtual electronic card can obtain the first transaction data of the physical bus card from the server. Based on the stored second transaction data and the obtained first transaction data, the terminal device can modify the data in the virtual electronic card to ensure that the modified data is consistent with the data in the user's main account on the server.

[0180] Based on the same inventive concept Figure 7This is a flowchart illustrating a data synchronization method provided in an embodiment of this specification. The method can be as follows. The executing entity of this embodiment can be a terminal device or an application client equipped with the technical solutions provided in this embodiment; no specific limitation is made here.

[0181] Step 701: Determine whether the set synchronization conditions are met. If they are met, proceed to step 703; otherwise, wait for the set time and continue to proceed to step 701.

[0182] In the embodiments described in this specification, the synchronization conditions may include, but are not limited to, the following conditions:

[0183] 1. Has a carrier for the first account been detected? If a carrier for the first account is detected, the set synchronization conditions are met; if no carrier for the first account is detected, the set synchronization conditions are not met.

[0184] 2. Has a data synchronization request been received? If a data synchronization request is received, further determine whether the carrier of the first account has been detected. If the carrier of the first account has been detected, it means that the set synchronization conditions are met; if the carrier of the first account has not been detected, a prompt message is sent to remind the user to provide the carrier of the first account and to establish a data channel; if no data synchronization request has been received, it means that the set synchronization conditions are not met.

[0185] 3. Has the set synchronization period been reached? If the set synchronization period has been reached, further determine whether the carrier of the first account has been detected. If the carrier of the first account has been detected, it means that the set synchronization conditions have been met. If the carrier of the first account has not been detected, a prompt message is sent to remind the user to provide the carrier of the first account and to establish a data channel. If the set synchronization period has not been reached, it means that the set synchronization conditions have not been met.

[0186] One or more of the synchronization conditions listed in the embodiments of this specification can be used. Furthermore, the synchronization conditions set are not limited to those listed in the embodiments of this specification; they can be determined according to actual needs, and no specific limitations are made here.

[0187] Preferably, in the embodiments of this specification, when a carrier carrying the first account is detected, it can be further determined whether there is a second account associated with the account identifier of the first account. If there is no second account, firstly, a second account associated with the first account is created based on the account identifier of the first account, and secondly, a data synchronization operation is triggered. If there is a second account, the following operations are performed according to the scheme described in the embodiments of this specification.

[0188] It should be noted that the carrier of the first account described in the embodiments of this specification can be a card that supports short-range communication (e.g., an IC card). The short-range communication method here includes, but is not limited to, Bluetooth, infrared, NFC, RFID, etc., and is not specifically limited here.

[0189] Step 703: Obtain the account identifier of the first account and the first transaction data corresponding to the first account.

[0190] In the embodiments of this specification, the methods for obtaining the account identifier of the first account and the first transaction data corresponding to the first account include, but are not limited to:

[0191] The first method:

[0192] A data channel is established between the device carrying the first account and the device using short-range communication methods;

[0193] Using the data channel, the account identifier of the first account and the first transaction data corresponding to the first account are obtained from the carrier.

[0194] Assuming the carrier of the first account is a card that supports NFC communication, the terminal device can establish a data channel with the card via NFC. Using this data channel, the account identifier (e.g., the card number) and the first transaction data corresponding to the first account can be obtained from the card.

[0195] It should be noted that the card can record transaction data, such as consumption data and recharge data, when interacting with other devices, and also record the time when the transaction data occurs.

[0196] The second method:

[0197] The account identifier of the first account is obtained from the carrier of the first account by scanning.

[0198] Based on the account identifier of the first account, the first transaction data corresponding to the account identifier of the first account is obtained from the server.

[0199] For example, if the carrier of the first account contains a QR code image, and the QR code image contains the account identifier of the first account, then the account identifier of the first account can be obtained from the carrier by scanning it, and then the transaction data corresponding to the account identifier of the first account can be found through the account identifier of the first account.

[0200] The third method:

[0201] Provide a user interface and receive, through the user interface, the account identifier of the first account input by the user;

[0202] Based on the account identifier of the first account, the first transaction data corresponding to the account identifier of the first account is obtained from the server.

[0203] For example, a user interface is provided in the terminal device, through which data synchronization operations can be initiated. Specifically, the user interface can be used to obtain the account identifier of the first account, which can be understood as the card number of the card carrying the first account. Furthermore, the transaction data corresponding to the account identifier can be obtained.

[0204] Preferably, before obtaining the account identifier of the first account and the first transaction data corresponding to the first account, the method further includes:

[0205] If a data change is detected in the second account associated with the first account, a notification message is sent to prompt the user to synchronize data between the first account and the second account.

[0206] For example, to ensure data consistency between the first account and its associated second account, when a change is detected in the data of the second account associated with the first account, a notification message can be sent to prompt the user to synchronize the data between the first account and the second account.

[0207] Preferably, in the embodiments of this specification, the first transaction data generated by the first account within a synchronization period is obtained.

[0208] The synchronization period here can be understood as the time between two adjacent synchronization operations. This synchronization period can be a fixed period or a variable period; no specific limitation is made here. For example, when initiating this synchronization operation, the time T of the last synchronization operation or the last data synchronization completion is determined. Then, taking the determined time T as the starting point and the time of initiating this synchronization operation as the ending point, the streaming data generated in this time period (from the starting point to the ending point) is determined.

[0209] Step 705: Determine the second transaction data corresponding to the second account associated with the first account.

[0210] In this embodiment of the specification, the account identifier of the second account that is associated with the account identifier of the first account is determined based on the account identifier of the first account;

[0211] Based on the account identifier of the second account, locate the second transaction data that corresponds to the account identifier of the second account.

[0212] The following details how to create a second account associated with the first account.

[0213] First, obtain the account identifier of the first account.

[0214] The methods for obtaining the account identifier of the first account here include, but are not limited to:

[0215] The account identifier of the first account is obtained from the carrier of the first account through short-range communication.

[0216] The account identifier of the first account is obtained from the carrier of the first account by scanning.

[0217] The user interface receives the account identifier of the first account.

[0218] Secondly, based on the account identifier of the first account, create the account identifier of the second account.

[0219] The account identifier of the second account created here can be the same as or different from the account identifier of the first account; no specific restrictions are imposed here.

[0220] Finally, the association between the account identifier of the first account and the account identifier of the second account is established and stored.

[0221] It should be noted that at least one second account can be created for the first account. When performing data synchronization, it can be between virtual accounts and physical accounts. That is to say, the first account and the second account described in the embodiments of this specification represent physical accounts and virtual accounts respectively, and there is an association relationship between physical accounts and virtual accounts. As for the number of virtual accounts, it is not limited here.

[0222] Preferably, to prevent users from maliciously using virtual accounts, the method further includes:

[0223] After obtaining the account identifier of the second account, establish the association between the account identifier of the second account and the application account used for payment.

[0224] When creating a virtual account (i.e., a second account), a deduction agreement is signed with the user, which establishes an association between the account identifier of the second account and the application account used for payment. If malicious overdraft is discovered in the second account or after data synchronization between the first and second accounts, the malicious overdraft fee can be deducted from the application account used for payment that is associated with the account identifier of the second account.

[0225] It should be noted that the terms "first account" and "second account" used in the embodiments of this specification have no special meaning and are merely used to distinguish between accounts. Furthermore, the carrier of the first account is a physical entity, such as an IC card, while the carrier of the second account is a virtual entity, such as an electronic card.

[0226] Step 707: Synchronize data between the first account and the second account based on the first transaction data and / or the second transaction data.

[0227] In the embodiments of this specification, synchronization data for synchronization is calculated based on the first flow data and / or the second flow data;

[0228] The synchronized data is then synchronized to the first account and the second account, respectively.

[0229] Suppose that when creating a second account, the balance data corresponding to the first account is synchronized to the second account.

[0230] If the synchronized data is negative, then empty spaces will be written to the first account and the second account respectively; and the amount corresponding to the negative number will be deducted from the application account associated with the second account for payment.

[0231] Preferably, the method further includes:

[0232] Send the synchronization time, the account identifier of the first account, and the first transaction data to the server, and delete the first transaction data recorded in the carrier of the first account; and / or,

[0233] The synchronization time, the account identifier of the second account, and the second transaction data are sent to the server, and the second transaction data is deleted.

[0234] The transaction data described in the embodiments of this specification includes at least one or more of payment data and recharge data.

[0235] The technical solution provided in the embodiments of this specification, under the condition of meeting the set synchronization conditions, obtains the account identifier of the first account and the first transaction data corresponding to the first account; determines the second transaction data corresponding to the second account associated with the first account; and performs data synchronization between the first account and the second account based on the first transaction data and / or the second transaction data. This effectively ensures data consistency between the first account and the second account. That is, assuming the first account is an account carried in a carrier, and the second account is a virtual electronic account associated with the first account, then the user can complete transactions using either the first account or the second account. Furthermore, the technical solution provided in the embodiments of this specification ensures data consistency between these two accounts, thereby improving the user's payment experience.

[0236] Figure 8 This is a flowchart illustrating a data synchronization method provided in an embodiment of this specification. The data processing method is shown below. The executing entity can be a client, which can be an application program (APP) running on a smart terminal. Smart terminals include, but are not limited to, mobile smart terminals such as smartphones and tablets, and also include other smart terminals such as computers and laptops.

[0237] Step 801: Obtain the first account and the balance in the first account recorded in the carrier.

[0238] In the embodiments described in this specification, the first account can be provided by the main body of the issuing carrier and written into the carrier. The form of the first account can include numbers, letters, and combinations thereof, and is not specifically limited here. The form of the carrier can include, but is limited to, physical cards, button cards, etc., and is not specifically limited here.

[0239] In the embodiments described in this specification, numbers in the carrier can be read to form the balance in the first account. For example, the carrier contains a Near Field Communication (NFC) module, and terminal devices that support NFC can write numbers to the NFC module when a transaction occurs and can read the numbers in the NFC module.

[0240] The embodiments in this specification may provide, but are not limited to, the following implementation methods:

[0241] 1. Transmit radio frequency signals to the carrier, causing the carrier to send a response signal in response to the radio frequency signals;

[0242] Receive the response signal; and parse the first account and the balance in the first account from the response signal.

[0243] In the embodiments of this specification, when a user makes a payment or receipt transaction through a first account in the carrier or a second account in the client, the carrier and the client device can be brought close together. The client transmits a radio frequency signal to the carrier via its NFC module, which is equivalent to transmitting a short-range radio frequency signal to the carrier. The NFC module in the carrier responds by generating a response signal, which carries the first account and the balance in the first account. The client receives the response signal via its NFC module and uses a parsing module to parse out the first account and the balance in the first account.

[0244] If the carrier contains a response module capable of receiving and responding to other frequency radio frequency signals, then the client device can transmit other frequency radio frequency signals that can be responded to. Therefore, provided that the radio frequency signals transmitted by the client device can be responded to by the carrier, the radio frequency signals transmitted by the client include, but are not limited to, short-range wireless radio frequency signals, and are not limited here.

[0245] 2. Receive the first account entered by the user; and based on the first account, retrieve the balance in the first account from the server.

[0246] In the embodiments of this specification, if the payment device that exchanges payment data with the carrier writes the latest balance to the first account, it can also store the balance in the first account in the server. Then, the client can retrieve the latest balance of the first account in the server by using the first account entered by the user.

[0247] 3. Scan the carrier to obtain the first account; and based on the first account, retrieve the balance in the first account from the server.

[0248] In the embodiments of this specification, if the first account is displayed on the surface of the carrier, the client can scan the surface of the carrier to obtain the first account. In this case, the first account may exist in the form of, but is not limited to: being highlighted so that the client can obtain the first account through graphic recognition; or, the first account is recorded in an identification code such as a QR code or barcode so that the client can scan and parse the identification code to obtain the first account.

[0249] To retrieve the balance of the first account from the server, please refer to the second method described above, which will not be repeated here.

[0250] Step 803: Based on the first account, create a second account associated with the first account on the client, and write the balance in the first account into the second account.

[0251] In the embodiments described in this specification, if the first account is considered a physical account recorded in a carrier, the second account can be a virtual account associated with the physical account. The virtual account can be stored on the client in the form of a user graphical interface, which can display the virtual account and its balance. The user graphical interface provides interface objects; by operating these objects, payment and receipt transactions can be processed. For example, the interface objects include a QR code generation object; clicking the QR code generation object generates a payment QR code, which is used for payment and receipt transactions.

[0252] In the embodiments described in this specification, after the client creates a second account, the client can send the second account and the balance in the first account to the server. Simultaneously, when subsequent payment or receipt data occurs in the second account, the client can send this data to the server for storage. This avoids increasing the client's storage burden, and during subsequent balance synchronization between the first and second accounts, the client can easily retrieve the payment and receipt data and balance of the second account from the server.

[0253] In the embodiments described in this specification, creating a second account associated with the first account on the client, based on the first account, may include, but is not limited to:

[0254] A second account identical to the first account is created on the client side, and this second account is identified as the second account associated with the first account. In this case, the identification information of the first and second accounts is the same, such as having the same letters, numbers, and combinations thereof.

[0255] The second account can be different from the first account, but they can form a relationship based on association rules.

[0256] Using the account processing method provided in this embodiment, users can create a second account associated with the first account at any time. This allows them to use either the first account on the carrier or the second account on the client for payment transactions, offering a high degree of choice. In particular, even if one of the carrier or client is not carried or is unusable during a transaction, the other can be used for payment, improving the user's payment experience.

[0257] Figure 9 This document provides a flowchart illustrating a data synchronization method according to an embodiment. The method, shown below, aims to synchronize the balances between a first account and a second account associated with that first account. The entity executing this account processing method can be a client, which can be an application (APP) running on a smart terminal. Smart terminals include, but are not limited to, mobile smart terminals such as smartphones and tablets, and also include other smart terminals such as computers and laptops.

[0258] Step 901: Obtain the first account and the balance in the first account recorded in the carrier.

[0259] The method for obtaining the first account recorded in the carrier and the balance in the first account can be referred to the content of step 801 above, and will not be repeated here.

[0260] In this embodiment of the specification, in order to promptly synchronize the payment and receipt data generated by the second account to the first account after the user has made a payment or receipt through the second account, the processing method further includes the following steps before obtaining the first account and its balance recorded in the carrier:

[0261] If at least one payment or receipt occurs in the second account, an alert signal is emitted to remind the user to provide the information for the first account associated with the second account. This provides convenience for the user and reduces their memory burden.

[0262] After receiving the notification signal, the user can use the three methods described in step 801 above to provide the first account and the balance in the first account to the client.

[0263] In the embodiments described in this specification, the form of the reminder signal may include, but is not limited to, voice, sound, vibration, graphics, text, etc., and is not specifically limited herein.

[0264] In the embodiments of this specification, if at least one payment or receipt occurs in the second account, an alert signal is emitted, which may include at least one or more of the following:

[0265] An alert signal will be sent for each payment or receipt transaction.

[0266] Once a set number of payment or receipt transactions have occurred, an alert signal will be sent.

[0267] Regularly send reminder signals; or

[0268] If the balance in the second account becomes 0 or insufficient due to payment or receipt data, an alert signal will be sent.

[0269] Step 903: Determine at least one payment or receipt data item that occurred in the second account associated with the first account and the balance in the second account. The payment or receipt data item includes one or both of the consumption amount and the recharge amount.

[0270] In this embodiment of the specification, determining at least one payment or receipt transaction occurring in the second account associated with the first account and the balance in the second account includes:

[0271] Identify the second account associated with the first account;

[0272] Determine at least one payment or receipt transaction in the second account and the balance in the second account.

[0273] In the embodiments of this specification, the method for determining the second account associated with the first account may include:

[0274] After obtaining the first account and its balance recorded in the carrier, the second accounts running on the client are identified as the second accounts associated with the first account.

[0275] Methods for identifying a second account associated with a first account may also include:

[0276] Send the first account to the server so that the server can identify the second account that is the same as the first account;

[0277] The second account obtained from the server that is identical to the first account will be identified as the second account associated with the first account.

[0278] Methods for identifying a second account associated with a first account may also include:

[0279] If the second account created based on step 803 above is different from the first account, then the second account associated with the first account is retrieved from the local machine or the server according to the association relationship between the first account and the second account.

[0280] In the embodiments described in this specification, the client storing the second account can establish a connection with the backend server at any time. Therefore, determining at least one payment or receipt transaction in the second account and the balance in the second account can include:

[0281] The client sends a payment data retrieval request to the server. The payment data retrieval request is used to request the server to send the payment data of the second account and the balance in the second account.

[0282] Receive and send data on payments and receipts in the second account from the server, and the balance in the second account.

[0283] In this scenario, all payment and receipt data generated by the second account are stored on the server, which can save the storage burden on the local client.

[0284] In the embodiments of this specification, determining at least one payment or receipt data occurrence in the second account includes the following two scenarios:

[0285] 1. Determine at least one payment or receipt record for the second account within an adjacent update cycle. The update cycle is the time interval between two consecutive updates where the balances in the first and second accounts are updated to the same balance. At this point, a payment or receipt data retrieval request is sent to the server, requesting the server to send all payment or receipt records occurring within the adjacent update cycle, along with the latest balance in the second account. Based on the payment or receipt data retrieval request, the server sends all payment or receipt records from the latest amount update to the current adjacent update cycle to the client.

[0286] 2. Determine the real-time payment and receipt data of the second account. Referring to step 501 above, obtain the balance in the first account for each payment and receipt transaction that occurs in the second account.

[0287] Step 905: Based on the assumption that payment and receipt data have occurred in the first account, update the balance in the first account and the balance in the second account to the same updated balance.

[0288] If, according to step 903, the determined payment / receipt data for the second account is at least one payment / receipt data occurrence in an adjacent update cycle for the second account, then based on the assumption that the payment / receipt data occurred in the first account, the balance in the first account and the balance in the second account are updated to the same updated balance, including:

[0289] Based on the assumption that the first account has different receipts and payments in adjacent update cycles, the balance in the first account and the balance in the second account are updated to the same updated balance.

[0290] Since the first account and the second account are consistent, the receipts and payments that occur in the second account are equivalent to those that occur in the first account. Therefore, we can set the assumption that the first account will have receipts and payments in adjacent update cycles to determine the same updated balance.

[0291] For example, refer to Table 1:

[0292] Table 1

[0293]

[0294]

[0295] Within the adjacent update cycles from the most recent update to the present, the payment data for the second account includes: a recharge amount of 10 yuan; a consumption amount of 14 yuan; the current balance of the second account is 16 yuan, while the current balance of the first account is 17 yuan.

[0296] From the perspective of unifying the first and second accounts, and based on the assumption that payment and receipt data occur in the first account, the balance in the first account and the balance in the second account are updated to the same updated balance, including:

[0297] Based on the assumption that payment and receipt data occurred in the first account, calculate the updated balance of the first account after the payment and receipt data occurred;

[0298] Update the balance in the first account and the balance in the second account to the updated balance.

[0299] Depending on the type of each payment / receipt data, calculate the updated balance in the first account after the payment / receipt data occurs, including:

[0300] If the payment data contains at least one recharge amount, then add each recharge amount to the balance in the first account;

[0301] If the payment data contains at least one consumption amount, then subtract each consumption amount from the balance in the first account;

[0302] The processing result will be used to update the balance.

[0303] For example, referring to Table 1, assuming that the payment data for the second account occurred in the first account, the current balance in the first account is calculated as 17 - 14 + 10 = 13 yuan, and the updated balance is determined to be 13 yuan. Then, the balances of both the first and second accounts are updated to 13 yuan.

[0304] The example in Table 1 above is for reference only. In specific application scenarios, payment and receipt data may have many other situations, which are not specifically limited.

[0305] This method of determining at least one payment or receipt data occurrence in the second account is particularly applicable to situations where the carrier storing the first account cannot connect to the server in real time, or where the client storing the second account is used frequently, thus solving the connection problems existing in the carrier where the first account is located.

[0306] In this way, multiple payment and receipt data can be processed simultaneously each time the balances of the first and second accounts are synchronized, making the processing efficiency more efficient.

[0307] If, according to step 903, it is determined that the payment and receipt data generated by the second account is real-time payment and receipt data, then the example given in Table 1 can be used to determine the same update for the first account and the second account, which will not be elaborated here.

[0308] In the embodiments described in this specification, after determining the updated balance, the client can directly update the balance in the second account to the updated balance.

[0309] Referring to the three methods for obtaining the balance of the first account recorded in the carrier in step 801 above, the methods for updating the balance of the first account to an updated balance include:

[0310] 1. If the carrier and the client can communicate via radio frequency signals, the balance of the first account recorded in the NFC module can be updated to the updated balance. For example, when the carrier and the client's device are close together, the balance of the first account in the NFC module of the carrier can be modified to the updated balance.

[0311] 2. If the carrier is connected to the server through a payment device with which it exchanges payment data, the client requests the server to send an updated balance to the carrier. The device then writes the updated balance into the carrier. For example, when the carrier is close to a payment device such as a bus POS machine or a cash register POS machine, the device can modify the balance of the first account recorded in the carrier to the updated balance.

[0312] Updating the balance in the first account to the first method of updating the balance is convenient for users to operate anytime and anywhere.

[0313] Using the account processing method proposed in the embodiments of this specification, the balances in the first account and the second account can be synchronized, thereby achieving the unification of the first account and the second account.

[0314] This is particularly applicable to situations where the carrier recording the first account cannot connect to the server, or the carrier cannot connect to the server in real time.

[0315] Figure 10 This is a flowchart illustrating a data synchronization method proposed in an embodiment of this specification. The processing method is shown below. The executing entity of this processing method is a server. This method is particularly applicable to, but not limited to, carriers that record the first account and can easily or practically connect to the server.

[0316] Step 1001: Receive payment data from at least one of the first account and the second account associated with the first account.

[0317] The payment and receipt data occurring in the first account is determined when the first account is obtained from the carrier that records the first account through the client. The payment and receipt data includes the recharge amount and the consumption amount.

[0318] Referring to the second method in step 803 above for obtaining the first account and its balance recorded in the carrier, the server can receive payment and receipt data generated by the first account through a payment and receipt device that exchanges payment and receipt data with the carrier. The server can also directly receive payment and receipt data generated by the second account from the client storing the second account.

[0319] Step 1003: Update the balance in the first account and the balance in the second account to the same updated balance after the receipt and payment data occurred.

[0320] The updated balance in the first account is written into the carrier through the payment and receipt device.

[0321] In the embodiments of this specification, after receiving payment data from at least one of the first account and the second account associated with the first account, the processing method may further include:

[0322] Determine at least one payment or receipt data received in an adjacent update cycle, wherein the update cycle is the time interval between two consecutive updates of the balances in the first account and the second account to the same updated balance;

[0323] Update both the balance in the first account and the balance in the second account to the same updated balance after the receipt and payment data occurred, including:

[0324] Update both the balance in the first account and the balance in the second account to the same updated balance following the receipt and payment data that occurred in adjacent update cycles.

[0325] In this case, we can refer to step 905 above and determine one of the first account and the second account as the base account. Assuming that the receipt and payment data of the base account also occurs in the other account, we can then determine an update account.

[0326] At this point, each update can process multiple payment and receipt data simultaneously, improving processing efficiency.

[0327] In the embodiments of this specification, updating both the balance in the first account and the balance in the second account to the same updated balance after the receipt and payment data occurred may further include:

[0328] Upon receiving each payment or receipt, the balances in both the first and second accounts are updated to the same updated balance following the occurrence of the payment or receipt.

[0329] In the embodiments described in this specification, the processing method may further include:

[0330] If the received payment data from the first account is less than the balance in the second account, a notification message is sent to the client running the second account to inform the user of the insufficient balance. Simultaneously, the server can notify the payment device that the account balance is insufficient and the deduction cannot be completed.

[0331] This specification provides another technical means to synchronize the balances of the first account and the second account to the updated balance, so as to keep the balances of the first account and the second account consistent.

[0332] Figure 11This is a schematic diagram of an account creation device provided in an embodiment of this specification. The account creation device includes: an acquisition unit 1101, a creation unit 1102, and a storage unit 1103, wherein:

[0333] The acquisition unit 1101 acquires the account identifier of the first account from a specified carrier in a set manner;

[0334] Creation unit 1102 creates an account identifier for the second account based on the account identifier of the first account;

[0335] Storage unit 1103 establishes and stores the mapping relationship between the account identifier of the first account and the account identifier of the second account.

[0336] In another embodiment of this specification, the acquisition unit 1101 acquires the account identifier of the first account from a designated carrier through a set method, including:

[0337] A data channel is established with a designated carrier using short-range communication technology, and the account identifier of the first account is obtained from the designated carrier through the data channel.

[0338] In another embodiment of this specification, the acquisition unit 1101 acquires the account identifier of the first account from a designated carrier through a set method, including:

[0339] The account identifier of the first account is obtained from the specified carrier by scanning.

[0340] In another embodiment of this specification, after obtaining the account identifier of the second account, the storage unit 1103 establishes and stores the association between the account identifier of the second account and the application account used for payment.

[0341] In another embodiment of this specification, the designated carrier includes at least one or more of the following: a card device supporting near-field communication technology, a second terminal device containing an account identifier of the first account, and an application client containing an account identifier of the first account.

[0342] In another embodiment of this specification, the second account includes one of a virtual account and an electronic account.

[0343] It should be noted that the account creation device described in the embodiments of this specification can be implemented by software or by hardware, and no specific limitation is made here.

[0344] Based on the same inventive concept, embodiments of this specification also provide an account creation device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to be executed by the processor of the following steps:

[0345] The account identifier of the first account is obtained from the specified carrier through a set method;

[0346] Create an account identifier for the second account based on the account identifier of the first account;

[0347] Establish and store the mapping relationship between the account identifier of the first account and the account identifier of the second account.

[0348] Other functions of the processor can be found in the above embodiments, and will not be repeated here.

[0349] Based on the same inventive concept, embodiments of this specification also provide a computer-readable storage medium including a program for use in conjunction with an electronic device, the program being executable by a processor to perform the following steps:

[0350] The account identifier of the first account is obtained from the specified carrier through a set method;

[0351] Create an account identifier for the second account based on the account identifier of the first account;

[0352] Establish and store the mapping relationship between the account identifier of the first account and the account identifier of the second account.

[0353] Other functions of the processor can be found in the above embodiments, and will not be repeated here.

[0354] Figure 12 This is a schematic diagram of an account recharge device provided in an embodiment of this specification. The account recharge device includes: an establishment unit 1201 and a recharge unit 1202, wherein:

[0355] Establishment unit 1201 establishes a data channel with a designated carrier containing the account identifier of the first account through near-field communication technology;

[0356] The recharge unit 1202 writes the recharge data of the second account into the designated carrier through the data channel to recharge the first account.

[0357] In another embodiment of this specification, the account recharge device further includes: a generation unit 1203, wherein:

[0358] The generation unit 1203 uses the application account used for payment to perform a transfer operation to the second account, generating the recharge data for the second account.

[0359] In another embodiment of this specification, the designated carrier includes at least one or more of the following: a card device supporting near-field communication technology, a second terminal device containing an account identifier of the first account, and an application client containing an account identifier of the first account.

[0360] It should be noted that the account recharge device described in the embodiments of this specification can be implemented by software or by hardware, and no specific limitation is made here.

[0361] Based on the same inventive concept, embodiments of this specification provide an account recharge device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to be executed by the processor in the following steps:

[0362] A data channel is established with a designated carrier containing the account identifier of the first account through near-field communication technology;

[0363] The recharge data of the second account is written into the designated carrier through the data channel to recharge the first account.

[0364] Other functions of the processor can be found in the above embodiments, and will not be repeated here.

[0365] Based on the same inventive concept, embodiments of this specification also provide a computer-readable storage medium including a program for use in conjunction with an electronic device, the program being executable by a processor to perform the following steps:

[0366] A data channel is established with a designated carrier containing the account identifier of the first account through near-field communication technology;

[0367] The recharge data of the second account is written into the designated carrier through the data channel to recharge the first account.

[0368] Figure 13 This is a schematic diagram of an account recharge device provided in an embodiment of this specification. The account recharge device includes: a receiving unit 1301 and a processing unit 1302, wherein:

[0369] The receiving unit 1301 receives recharge data sent by the first terminal device when a data channel is established with the first terminal device through short-range communication technology.

[0370] The processing unit 1302 processes the balance data of the first account based on the recharge data.

[0371] In another embodiment of this specification, the processing unit 1302 processes the balance data of the first account based on the recharge data, including:

[0372] If the balance of the first account is zero, the recharge data is written into the first account;

[0373] If the balance data of the first account is not zero, the balance data of the first account is modified using the recharge data.

[0374] It should be noted that the account recharge device described in the embodiments of this specification can be implemented by software or by hardware, and no specific limitation is made here.

[0375] Based on the same inventive concept, embodiments of this specification provide an account recharge device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to be executed by the processor in the following steps:

[0376] When a data channel is established with the first terminal device through short-range communication technology, the recharge data sent by the first terminal device is received;

[0377] Based on the recharge data, the balance data of the first account is processed.

[0378] Other functions of the processor can be found in the above embodiments, and will not be repeated here.

[0379] Based on the same inventive concept, embodiments of this specification also provide a computer-readable storage medium including a program for use in conjunction with an electronic device, the program being executable by a processor to perform the following steps:

[0380] When a data channel is established with the first terminal device through short-range communication technology, the recharge data sent by the first terminal device is received;

[0381] Based on the recharge data, the balance data of the first account is processed.

[0382] Figure 14 This is a schematic diagram of a data synchronization device provided in an embodiment of this specification. The data synchronization device includes: an acquisition unit 1401, a receiving unit 1402, and a synchronization unit 1403, wherein:

[0383] The acquisition unit 1401 acquires the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier through a short-range communication method.

[0384] The receiving unit 1402 receives the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device;

[0385] Synchronization unit 1403 determines synchronization data for a synchronization cycle based on the first flow data and the second flow data, and sends the synchronization data to the first terminal device so that the data corresponding to the second account is consistent with the data corresponding to the main account.

[0386] In this embodiment, the data processing device described can be applied in a server, and an association is established between the main account contained in the server and the first account contained in the designated carrier and the second account contained in the first terminal device.

[0387] In another embodiment of this specification, the acquisition unit 1401 acquires the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier via near-field communication, including:

[0388] A data channel is established with the designated carrier via short-range communication.

[0389] If a transaction is confirmed to have occurred, the account identifier of the first account and the first transaction data corresponding to the first account are obtained from the designated carrier through the data channel.

[0390] In another embodiment of this specification, the data synchronization device further includes: a sending unit 1404, wherein:

[0391] If the synchronization data is negative, the sending unit 1404 sends a deduction request to the first terminal device. The deduction request is used to request the deduction of the amount corresponding to the negative number from the application account associated with the second account for payment.

[0392] It should be noted that the data synchronization device described in the embodiments of this specification can be implemented by software or by hardware, and no specific limitation is made here.

[0393] Based on the same inventive concept, embodiments of this specification provide a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to be executed by the processor in the following steps:

[0394] The account identifier of the first account and the first transaction data corresponding to the first account are obtained from the designated carrier through a near-field communication method.

[0395] Receive the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device;

[0396] Based on the first transaction data and the second transaction data, a synchronization data for a synchronization period is determined, and the synchronization data is sent to the first terminal device so that the data corresponding to the second account is consistent with the data corresponding to the main account;

[0397] The server establishes an association between the main account contained in the server and the first account contained in the designated carrier and the second account contained in the first terminal device.

[0398] Other functions of the processor can be found in the above embodiments, and will not be repeated here.

[0399] Based on the same inventive concept, embodiments of this specification also provide a computer-readable storage medium including a program for use in conjunction with an electronic device, the program being executable by a processor to perform the following steps:

[0400] The account identifier of the first account and the first transaction data corresponding to the first account are obtained from the designated carrier through a near-field communication method.

[0401] Receive the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device;

[0402] Based on the first transaction data and the second transaction data, a synchronization data for a synchronization period is determined, and the synchronization data is sent to the first terminal device so that the data corresponding to the second account is consistent with the data corresponding to the main account;

[0403] The server establishes an association between the main account contained in the server and the first account contained in the designated carrier and the second account contained in the first terminal device.

[0404] Figure 15 This is a schematic diagram of a data synchronization device provided in an embodiment of this specification. The data synchronization device includes: an establishment unit 1501 and a synchronization unit 1502, wherein:

[0405] Unit 1501 establishes a data channel with a designated carrier via short-range communication.

[0406] The synchronization unit 1502 synchronizes the balance data corresponding to the second account to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account.

[0407] In another embodiment of this specification, the data synchronization device further includes: a receiving unit 1503 and a processing unit 1504, wherein:

[0408] The receiving unit 1503 receives synchronization data sent by the server, the synchronization data being obtained by the server according to the synchronization method described above.

[0409] The processing unit 1504 uses the synchronization data to modify the data corresponding to the second account so that the data corresponding to the second account is consistent with the data corresponding to the main account contained in the server.

[0410] The server establishes an association between the main account contained in the server and the first account contained in the designated carrier and the second account contained in the first terminal device.

[0411] It should be noted that the data synchronization device described in the embodiments of this specification can be implemented by software or by hardware, and no specific limitation is made here.

[0412] Based on the same inventive concept, embodiments of this specification provide a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to be executed by the processor in the following steps:

[0413] Establish a data channel with a designated carrier through short-range communication methods;

[0414] The balance data corresponding to the second account is synchronized to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account.

[0415] Other functions of the processor can be found in the above embodiments, and will not be repeated here.

[0416] Based on the same inventive concept, embodiments of this specification also provide a computer-readable storage medium including a program for use in conjunction with an electronic device, the program being executable by a processor to perform the following steps:

[0417] Establish a data channel with a designated carrier through short-range communication methods;

[0418] The balance data corresponding to the second account is synchronized to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account.

[0419] Figure 16 This is a schematic diagram of a data synchronization device provided in an embodiment of this specification. The data synchronization device includes: an establishment unit 1601, an acquisition unit 1602, a determination unit 1603, and a synchronization unit 1604, wherein:

[0420] Unit 1601 establishes a data channel with a designated carrier via short-range communication.

[0421] The acquisition unit 1602 acquires the account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier through the data channel;

[0422] Determining unit 1603 determines the second transaction data corresponding to the second account associated with the first account;

[0423] Synchronization unit 1604 performs data synchronization between the first account and the second account based on the first transaction data and the second transaction data.

[0424] In another embodiment of this specification, the data synchronization device further includes: a sending unit 1605, wherein:

[0425] Before establishing a data channel, if the sending unit 1605 detects a change in the data corresponding to the second account associated with the first account, it sends a prompt message to remind the user to synchronize data between the first account and the second account.

[0426] In another embodiment of this specification, the determining unit 1603 determines the second transaction data corresponding to the second account associated with the first account, including:

[0427] Based on the account identifier of the first account, determine the account identifier of the second account that is associated with the account identifier of the first account;

[0428] Based on the account identifier of the second account, locate the second transaction data that corresponds to the account identifier of the second account.

[0429] In another embodiment of this specification, the synchronization unit 1604 performs data synchronization between the first account and the second account based on the first transaction data and the second transaction data, including:

[0430] Based on the first flow data and the second flow data, synchronization data for synchronization is calculated;

[0431] The synchronized data is then synchronized to the first account and the second account, respectively.

[0432] In another embodiment of this specification, the synchronization unit 1604 synchronizes the synchronization data to the first account and the second account, including:

[0433] If the synchronized data is negative, then empty numbers will be written to the first account and the second account respectively;

[0434] The amount corresponding to the negative number is deducted from the application account associated with the second account used for payment.

[0435] In another embodiment of this specification, the data synchronization device further includes: a deletion unit 1606, wherein:

[0436] The deletion unit 1606 sends the synchronization time, the account identifier of the first account, and the first transaction data to the server, and deletes the first transaction data recorded in the carrier of the first account; and / or,

[0437] The synchronization time, the account identifier of the second account, and the second transaction data are sent to the server, and the second transaction data is deleted.

[0438] In another embodiment of this specification, the transaction data includes at least one or more of consumption data and recharge data.

[0439] It should be noted that the data synchronization device described in the embodiments of this specification can be implemented by software or by hardware, and no specific limitation is made here.

[0440] Based on the same inventive concept, embodiments of this specification provide a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured to be executed by the processor in the following steps:

[0441] Establish a data channel with a designated carrier through short-range communication methods;

[0442] The account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier are obtained through the data channel.

[0443] Determine the second transaction data corresponding to the second account associated with the first account;

[0444] Based on the first transaction data and the second transaction data, data synchronization is performed between the first account and the second account.

[0445] Other functions of the processor can be found in the above embodiments, and will not be repeated here.

[0446] Based on the same inventive concept, embodiments of this specification also provide a computer-readable storage medium including a program for use in conjunction with an electronic device, the program being executable by a processor to perform the following steps:

[0447] Establish a data channel with a designated carrier through short-range communication methods;

[0448] The account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier are obtained through the data channel.

[0449] Determine the second transaction data corresponding to the second account associated with the first account;

[0450] Based on the first transaction data and the second transaction data, data synchronization is performed between the first account and the second account.

[0451] The technical solutions provided in the embodiments of this specification enable the creation of a second account on a terminal device for a first account contained in a designated carrier, and the use of the second account on the terminal device to recharge the first account and ensure data consistency between the first and second accounts via near-field communication. In other words, assuming the first account is an account stored in a designated carrier, and the second account is a virtual electronic account associated with the first account, then a user can complete transactions using either the first or the second account. Furthermore, the technical solutions provided in the embodiments of this specification ensure data consistency between the two accounts, thereby improving the user's payment experience.

[0452] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0453] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0454] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0455] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0456] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0457] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0458] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0459] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0460] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0461] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0462] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0463] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0464] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0465] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0466] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. An account creation method, comprising: The first terminal device that supports NFC function obtains the account identifier of the first account from a designated carrier that supports NFC communication through a set method; The first terminal device creates an account identifier for the second account based on the account identifier of the first account; The first terminal device establishes a data channel with a designated carrier containing the account identifier of the first account through near-field communication technology. The first account and the second account synchronize data through the data channel to make the data corresponding to the first account consistent with the data corresponding to the second account. The near-field communication technology is NFC technology. Transactions can be completed using the first account or the second account.

2. The account creation method according to claim 1, wherein the first account is an account carried in the designated carrier, and the second account is a virtual electronic account associated with the first account.

3. The account creation method according to claim 1, after the first terminal device creates the account identifier of the second account based on the account identifier of the first account, the method further includes: The first terminal device establishes and stores a mapping relationship between the account identifier of the first account and the account identifier of the second account.

4. The account creation method according to claim 1, wherein the first terminal device obtains the account identifier of the first account from the designated carrier, specifically including: The first terminal device establishes a data channel with a designated carrier through near-field communication technology, and obtains the account identifier of the first account from the designated carrier through the data channel.

5. The account creation method according to claim 1, wherein the first terminal device obtains the account identifier of the first account from the designated carrier, specifically including: The first terminal device obtains the account identifier of the first account from the designated carrier by scanning.

6. The account creation method according to claim 1, further comprising: After obtaining the account identifier of the second account, the first terminal device establishes and stores the association between the account identifier of the second account and the application account used for payment.

7. The account creation method according to claim 1, wherein the designated carrier includes at least one or more of the following: a card device supporting near-field communication technology, a second terminal device containing an account identifier of the first account, and an application client containing an account identifier of the first account.

8. The account creation method according to claim 1, wherein the second account includes one of a virtual account and an electronic account.

9. A method for topping up an account, comprising: The first terminal device establishes a data channel with a designated carrier containing the account identifier of the first account through near-field communication technology; The first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the near-field communication technology is NFC technology; The first terminal device writes the recharge data of the second account into the designated carrier through the data channel to recharge the first account; the transaction can be completed using the first account or the second account; the second account is an account associated with the first account.

10. The account recharge method according to claim 9, further comprising: The first terminal device uses the application account used for payment to perform a transfer operation to the second account, generating recharge data for the second account.

11. A method for topping up an account, comprising: When a designated carrier establishes a data channel with a first terminal device via near-field communication (NFC) technology, it receives recharge data sent by the first terminal device. The recharge data is generated when the first terminal device writes recharge data of a second account to the designated carrier via the data channel. The first terminal device is the same as in claim 1, the designated carrier is the same as in claim 1, and the near-field communication technology is NFC technology. Transactions can be completed using either the first account or the second account. The second account is an account associated with the first account. Based on the recharge data, the balance data of the first account is processed.

12. The account recharge method according to claim 11, wherein processing of the balance data of the first account based on the recharge data includes: If the balance of the first account is zero, the recharge data is written into the first account; If the balance data of the first account is not zero, the balance data of the first account is modified using the recharge data.

13. A data synchronization method, wherein a master account contained in a server establishes an association relationship with a first account contained in a designated carrier and a second account contained in a first terminal device, the association relationship enabling data corresponding to the master account, data corresponding to the first account, and data corresponding to the second account to remain consistent, the first terminal device being the first terminal device of claim 1, the designated carrier being the designated carrier of claim 1, and the second account being an account associated with the first account, comprising: The server obtains the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier through near-field communication technology. The server receives the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device; The server determines synchronization data for a synchronization period based on the first transaction data and the second transaction data, and sends the synchronization data to the first terminal device so that the data corresponding to the second account is consistent with the data corresponding to the main account. The near-field communication technology is NFC technology. Transactions can be completed using either the first account or the second account.

14. The data synchronization method according to claim 13, wherein the server obtains the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier through near-field communication technology, comprising: The server establishes a data channel with the designated carrier via short-range communication. When the server determines that a transaction has occurred, it obtains the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier through the data channel.

15. The data synchronization method according to claim 13, further comprising: If the synchronized data is negative, a deduction request is sent to the first terminal device. The deduction request is used to request the amount corresponding to the negative number to be deducted from the application account associated with the second account for payment.

16. A data synchronization method, comprising: The first terminal device establishes a data channel with the designated carrier through short-range communication technology; The first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the near-field communication technology is NFC technology; The first terminal device synchronizes the balance data corresponding to the second account to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account. The transaction can be completed using the first account or the transaction can be completed using the second account, where the second account is an account associated with the first account.

17. The data synchronization method according to claim 16, further comprising: The first terminal device receives synchronization data sent by the server. The synchronization data is synchronization data for a synchronization cycle determined by the server based on the first flow data and the second flow data. The first terminal device uses the synchronization data to modify the data corresponding to the second account, so that the data corresponding to the second account is consistent with the data corresponding to the main account contained in the server. The server contains a master account that is associated with a first account contained in a designated carrier and a second account contained in a first terminal device. The association ensures that the data corresponding to the master account, the first account, and the second account remain consistent.

18. A data synchronization method, comprising: The first terminal device establishes a data channel with the designated carrier through short-range communication technology; The first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the near-field communication technology is NFC technology; The first terminal device obtains the account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier through the data channel; The first terminal device determines the second transaction data corresponding to the second account associated with the first account; The first terminal device synchronizes data between the first account and the second account based on the first transaction data and the second transaction data, so that the data corresponding to the first account and the second account are consistent, and the transaction can be completed using the first account or the second account.

19. The data synchronization method according to claim 18, wherein before the first terminal device establishes a data channel, the method further includes: If a change is detected in the data corresponding to the second account associated with the first account, the first terminal device sends a prompt message to remind the user to synchronize data between the first account and the second account.

20. The data synchronization method according to claim 18, determining the second transaction data corresponding to the second account associated with the first account, comprising: Based on the account identifier of the first account, determine the account identifier of the second account that is associated with the account identifier of the first account; Based on the account identifier of the second account, locate the second transaction data that corresponds to the account identifier of the second account.

21. The data synchronization method according to claim 18, wherein data synchronization is performed between the first account and the second account based on the first transaction data and the second transaction data, comprising: Based on the first flow data and the second flow data, synchronization data for synchronization is calculated; The synchronized data is then synchronized to the first account and the second account, respectively.

22. The data synchronization method according to claim 21, wherein synchronizing the synchronized data to the first account and the second account comprises: If the synchronized data is negative, then empty numbers will be written to the first account and the second account respectively; The amount corresponding to the negative number is deducted from the application account associated with the second account used for payment.

23. The data synchronization method according to claim 18 or 22, further comprising: Send the synchronization time, the account identifier of the first account, and the first transaction data to the server, and delete the first transaction data recorded in the carrier of the first account; and / or, The synchronization time, the account identifier of the second account, and the second transaction data are sent to the server, and the second transaction data is deleted.

24. The data synchronization method according to claim 18, wherein the transaction data includes at least one or more of consumption data and recharge data.

25. An account creation device, comprising: The acquisition unit allows a first terminal device supporting NFC function to acquire the account identifier of a first account from a designated carrier supporting NFC communication through a set method. The first account is an account carried in the designated carrier. Create a unit to create an account identifier for the second account based on the account identifier of the first account; The storage unit, when the first terminal device establishes a data channel with a designated carrier containing the account identifier of the first account through near-field communication technology, synchronizes data between the first account and the second account so that the data corresponding to the first account is consistent with the data corresponding to the second account, so that the data of the first account and the second account are consistent. The near-field communication technology is NFC technology; a transaction can be completed using the first account or the second account.

26. An account recharge device, comprising: The establishment unit, wherein the first terminal device establishes a data channel with a designated carrier containing an account identifier of a first account through near-field communication technology, wherein the first account is an account carried in the designated carrier; the first terminal device is the first terminal device of claim 1, the designated carrier is the designated carrier of claim 1, and the near-field communication technology is NFC technology; The recharge unit writes the recharge data of the second account into the designated carrier through the data channel to recharge the first account. The transaction can be completed using the first account or the second account; the second account is an account associated with the first account.

27. An account top-up device, comprising: The receiving unit, after establishing a data channel with the first terminal device via near-field communication (NFC) technology, receives recharge data sent by the first terminal device. The recharge data is data from the second account written by the first terminal device to a designated carrier via the data channel. The first terminal device is the same as in claim 1, the designated carrier is the same as in claim 1, and the near-field communication technology is NFC technology. Transactions can be completed using either the first account or the second account. The second account is an account associated with the first account. The processing unit processes the balance data of the first account based on the recharge data.

28. A data synchronization device, wherein a master account contained in a server establishes an association relationship with a first account contained in a designated carrier and a second account contained in a first terminal device, the association relationship enabling data corresponding to the master account, data corresponding to the first account, and data corresponding to the second account to remain consistent, the first terminal device being the first terminal device of claim 1, the designated carrier being the designated carrier of claim 1, and the second account being an account associated with the first account, comprising: The acquisition unit acquires the account identifier of the first account and the first transaction data corresponding to the first account from the designated carrier through near-field communication technology. The receiving unit receives the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device; The synchronization unit determines synchronization data for a synchronization cycle based on the first transaction data and the second transaction data, and sends the synchronization data to the first terminal device so that the data corresponding to the second account is consistent with the data corresponding to the main account. The near-field communication technology is NFC technology. Transactions can be completed using either the first account or the second account.

29. A data synchronization device, comprising: In the establishment unit, the first terminal device establishes a data channel with the designated carrier through near-field communication technology; The first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the near-field communication technology is NFC technology; The synchronization unit synchronizes the balance data corresponding to the second account to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account. The transaction can be completed using the first account or the transaction can be completed using the second account, where the second account is an account associated with the first account.

30. A data synchronization device, comprising: In the establishment unit, the first terminal device establishes a data channel with the designated carrier through near-field communication technology; The first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the near-field communication technology is NFC technology; The acquisition unit acquires the account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier through the data channel; The determining unit determines the second transaction data corresponding to the second account associated with the first account; The synchronization unit synchronizes data between the first account and the second account based on the first transaction data and the second transaction data, so that the data corresponding to the first account and the second account are consistent, and the transaction can be completed using the first account or the transaction can be completed using the second account.

31. An account creation device, comprising: At least one memory and at least one processor, wherein the memory stores a program and is configured to perform the following steps by the processor: The first terminal device that supports NFC function obtains the account identifier of the first account from a designated carrier that supports NFC communication through a set method; Create an account identifier for the second account based on the account identifier of the first account; A data channel is established between the first account and a designated carrier containing the account identifier of the first account through near-field communication technology. The first account and the second account synchronize data through the data channel so that the data corresponding to the first account is consistent with the data corresponding to the second account. The near-field communication technology is NFC technology. Transactions can be completed using either the first account or the second account.

32. An account top-up device, comprising: At least one memory and at least one processor, wherein the memory stores a program and is configured to perform the following steps by the processor: The first terminal device establishes a data channel with a designated carrier containing an account identifier of the first account through near-field communication technology; the first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the near-field communication technology is NFC technology; The recharge data of the second account is written into the designated carrier through the data channel to recharge the first account. The transaction can be completed using the first account or the second account. The second account is an account associated with the first account.

33. An account recharge device, comprising: At least one memory and at least one processor, wherein the memory stores a program and is configured to perform the following steps by the processor: When a data channel is established with a first terminal device via near-field communication (NFC) technology, recharge data sent by the first terminal device is received. The recharge data is data from the second account written by the first terminal device to a designated carrier via the data channel. The first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the near-field communication technology is NFC technology. Transactions can be completed using either the first account or the second account. The second account is an account associated with the first account. Based on the recharge data, the balance data of the first account is processed.

34. A data synchronization device, comprising: At least one memory and at least one processor, wherein the memory stores a program and is configured to perform the following steps by the processor: The account identifier of the first account and the first transaction data corresponding to the first account are obtained from a designated carrier using near-field communication technology. Receive the account identifier of the second account and the second transaction data corresponding to the second account sent by the first terminal device; Based on the first transaction data and the second transaction data, synchronization data for a synchronization period is determined, and the synchronization data is sent to the first terminal device to ensure that the data corresponding to the second account is consistent with the data corresponding to the main account; the near-field communication technology is NFC technology; transactions can be completed using either the first account or the second account; The server contains a master account that is associated with a first account contained in a designated carrier and a second account contained in a first terminal device. The association ensures that the data corresponding to the master account, the data corresponding to the first account, and the data corresponding to the second account are consistent. The first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the second account is an account associated with the first account.

35. A data synchronization device, comprising: At least one memory and at least one processor, wherein the memory stores a program and is configured to perform the following steps by the processor: The first terminal device establishes a data channel with a designated carrier through near-field communication technology; the first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the near-field communication technology is NFC technology; The balance data corresponding to the second account is synchronized to the designated carrier through the data channel, so that the data corresponding to the first account contained in the designated carrier is consistent with the data corresponding to the second account. The transaction can be completed using the first account or the transaction can be completed using the second account, where the second account is an account associated with the first account.

36. A data synchronization device, comprising: At least one memory and at least one processor, wherein the memory stores a program and is configured to perform the following steps by the processor: The first terminal device establishes a data channel with a designated carrier through near-field communication technology; the first terminal device is the first terminal device in claim 1, the designated carrier is the designated carrier in claim 1, and the near-field communication technology is NFC technology; The account identifier of the first account and the first transaction data corresponding to the first account contained in the designated carrier are obtained through the data channel. Determine the second transaction data corresponding to the second account associated with the first account; Based on the first transaction data and the second transaction data, data synchronization is performed between the first account and the second account to ensure that the data corresponding to the first account and the second account are consistent, so that the transaction can be completed using the first account or the transaction can be completed using the second account.

Images