HK1248892B - Account creation, account recharging and data synchronization method and device - Google Patents

Description

Account creation, account recharge, and data synchronization method and device

Technical Field

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 recharge, and data synchronization.

Background Art

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 inconveniences to people (for example, the need to prepare sufficient change, etc.).

To address these inconveniences, payment by deposit has emerged. Payment by deposit can be understood as a user depositing money or cash from a bank account directly onto a designated IC card (Integrated Circuit Card), which can then be used to make purchases. This method is also known as an e-wallet. However, current methods for implementing payment by deposit generally require executing the relevant payment operation on a specific device.

Based on this payment method, a more convenient processing method is urgently needed to improve the convenience of deposit payment.

Summary of the Invention

In view of this, the embodiments of this specification provide a method and device for account creation, account recharge, and data synchronization to improve the convenience of load payment.

The embodiments of this specification provide the following technical solutions:

This embodiment of the present invention provides an account creation method, including:

The first terminal device obtains the account identifier of the first account from the designated carrier in a set manner;

The first terminal device creates an account identifier of a second account based on the account identifier of the first account;

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.

The present invention provides an account recharging method, including:

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

The first terminal device writes the recharge data of the second account into the designated carrier through the data channel to realize recharging for the first account.

The present invention provides an account recharging method, including:

The designated carrier receives the recharge data sent by the first terminal device when establishing a data channel with the first terminal device through the near field communication technology;

The balance data of the first account is processed according to the recharge data.

An embodiment of this specification provides a data synchronization method, wherein an association relationship is established between a primary account included in a server, a first account included in a designated carrier, and a second account included in a first terminal device, including:

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;

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 of 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.

This embodiment of the present invention provides a data synchronization method, including:

The first terminal device establishes a data channel with the designated carrier through a short-range communication method;

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.

This embodiment of the present invention provides a data synchronization method, including:

The first terminal device establishes a data channel with the designated carrier through a short-range communication method;

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

Determining, by the first terminal device, second transaction data corresponding to a second account associated with the first account;

The first terminal device synchronizes data between the first account and the second account according to the first transaction data and the second transaction data.

The present invention provides an account creation device, including:

an acquiring unit, configured to acquire the account identifier of the first account from a designated carrier in a set manner;

a creating unit, configured to create an account identifier for a second account based on the account identifier of the first account;

A storage unit is configured to establish and store a mapping relationship between the account identifier of the first account and the account identifier of the second account.

The embodiment of this specification provides an account recharging device, including:

an establishing unit, which establishes a data channel with a designated carrier including an account identifier of the first account through a near field communication technology;

The recharging unit writes the recharging data of the second account into the designated carrier through the data channel to realize recharging for the first account.

The embodiment of this specification provides an account recharging device, including:

a receiving unit, configured to receive the recharge data sent by the first terminal device when a data channel is established with the first terminal device through a near field communication technology;

The processing unit processes the balance data of the first account according to the recharge data.

An embodiment of the present disclosure provides a data synchronization device, wherein an association relationship is established between a primary account included in a server, a first account included in a designated carrier, and a second account included in a first terminal device, including:

an acquiring unit, configured to acquire an account identifier of a first account and first transaction data corresponding to the first account from the designated carrier through a short-range communication method;

a receiving unit, receiving the account identifier of the second account and second transaction data corresponding to the second account sent by the first terminal device;

The synchronization unit determines synchronization data of a synchronization cycle according to 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.

An embodiment of this specification provides a data synchronization device, including:

Establishing unit, establishing a data channel with a designated carrier through short-range communication;

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.

An embodiment of this specification provides a data synchronization device, including:

Establishing unit, establishing a data channel with a designated carrier through short-range communication;

an acquiring unit, configured to acquire, through the data channel, an account identifier of a first account and first transaction data corresponding to the first account contained in the designated carrier;

a determining unit, configured to determine second transaction data corresponding to a second account associated with the first account;

A synchronization unit is configured to synchronize data between the first account and the second account based on the first transaction data and the second transaction data.

An embodiment of this specification provides an account creation device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to perform the following steps:

Obtaining the account identifier of the first account from the specified carrier in a set manner;

Creating an account identifier for a second account based on the account identifier of the first account;

A mapping relationship between the account identifier of the first account and the account identifier of the second account is established and stored.

An embodiment of this specification provides an account recharging device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

establishing a data channel with a designated carrier including the account identifier of the first account through a near field communication technology;

The recharge data of the second account is written into the designated carrier through the data channel to realize recharging the first account.

An embodiment of this specification provides an account recharging device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

When a data channel is established with the first terminal device through the near field communication technology, receiving recharge data sent by the first terminal device;

The balance data of the first account is processed according to the recharge data.

An embodiment of this specification provides a data synchronization device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

Obtaining an account identifier of a first account and first transaction data corresponding to the first account from the designated carrier through a near field communication method;

receiving the account identifier of the second account and second transaction data corresponding to the second account sent by the first terminal device;

determining synchronization data for a synchronization period based on the first transaction data and the second transaction data, and sending the synchronization data to the first terminal device so that data corresponding to the second account is consistent with data corresponding to the primary account;

Among them, an association relationship is established between the main account contained in the server, the first account contained in the designated carrier, and the second account contained in the first terminal device.

An embodiment of this specification provides a data synchronization device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

Establish a data channel with a designated carrier through short-range communication;

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.

An embodiment of this specification provides a data synchronization device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

Establish a data channel with a designated carrier through short-range communication;

Acquire, through the data channel, an account identifier of a first account and first transaction data corresponding to the first account contained in the designated carrier;

Determining second transaction data corresponding to a second account associated with the first account;

Data synchronization is performed between the first account and the second account based on the first transaction data and the second transaction data.

At least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects:

By creating a second account on a terminal device for a first account contained in a designated carrier, and utilizing the second account in the terminal device, the first account can be recharged and data consistency between the first and second accounts can be ensured through near-field communication. In other words, assuming the first account is an account contained in a designated carrier and the second account is a virtual electronic account associated with the first account, the user can complete transactions using either the first account or the second account. Furthermore, the technical solutions provided in the embodiments of this specification ensure data consistency between the two accounts, thereby enhancing the user's payment experience.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings described herein are used to provide a further understanding of this specification and constitute a part of this application. The illustrative embodiments and descriptions of this specification are used to explain this application and do not constitute an improper limitation on this application. In the drawings:

FIG1 is a flow chart of an account creation method provided in an embodiment of this specification;

FIG2 is a flow chart of an account recharging method provided in an embodiment of this specification;

FIG3 is a flow chart of an account recharging method provided in an embodiment of this specification;

FIG4( a ) is a flow chart of a data synchronization method proposed in an embodiment of this specification;

FIG4( b ) is a flow chart of a data synchronization method proposed in an embodiment of this specification;

FIG5 is a flow chart of a data synchronization method proposed in an embodiment of this specification;

FIG6( a ) is a flow chart of a data synchronization method proposed in an embodiment of this specification;

FIG6( b ) is a flow chart of a data synchronization method proposed in an embodiment of this specification;

FIG7 is a flow chart of a data synchronization method proposed in an embodiment of this specification;

FIG8 is a flow chart of a data synchronization method proposed in an embodiment of this specification;

FIG9 is a flow chart of a data synchronization method proposed in an embodiment of this specification;

FIG10 is a flow chart of a data synchronization method proposed in an embodiment of this specification;

FIG11 is a schematic diagram of the structure of an account creation device provided in an embodiment of this specification;

FIG12 is a schematic diagram of the structure of an account recharging device provided in an embodiment of this specification;

FIG13 is a schematic diagram of the structure of an account recharging device provided in an embodiment of this specification;

FIG14 is a schematic diagram of the structure of a data synchronization device provided in an embodiment of this specification;

FIG15 is a schematic diagram of the structure of a data synchronization device provided in an embodiment of this specification;

FIG16 is a schematic diagram of the structure of a data synchronization device provided in an embodiment of this specification.

DETAILED DESCRIPTION

While existing mobile payment solutions offer convenience, they also come with some inconveniences for users. For example, if a user doesn't have their mobile device with them or it's out of battery, they won't be able to make payments. This suggests that if card and mobile payment can complement each other, they could greatly improve users' lives and productivity.

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 between parties involved in e-commerce transactions (including consumers, manufacturers, and financial institutions) via information networks, using digital methods and secure information transmission. Compared to cash payments or deposit payments, electronic payment offers greater convenience to users.

To achieve this purpose, the embodiments of this specification provide a method and device for account creation, account recharge, and data synchronization. By creating a second account for a first account contained in a designated carrier on a terminal device, and utilizing the second account in the terminal device, the first account is recharged and data consistency between the first and second accounts is ensured through short-range communication. In other words, assuming that the first account is an account carried in a designated carrier and the second account is a virtual electronic account associated with the first account, the user can complete the transaction using either the first account or the second account. At the same time, the technical solution provided in the embodiments of this specification can ensure the consistency of data between the two accounts, thereby improving the user's payment experience.

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, and are not specifically limited here.

IC cards (Integrated Circuit Cards), also known as smart cards, are readable and writable, have large storage capacities, encryption capabilities, reliable data recording, and are easy to use. For example, bus cards allow users to pay for public transportation using these cards. When the bus card interacts with the public transportation card reader, the value on the card is read and the fare is deducted. Currently, bus card top-ups are typically completed through a rollover method, requiring users to visit designated top-up locations and use special equipment to top up their card.

To make the purpose, technical solutions, and advantages of the embodiments of this specification more clear, the technical solutions of this specification will be clearly and completely described below in conjunction with the specific embodiments of this specification and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

Figure 1 is a flow chart of an account creation method provided by the present specification. The method may be as follows. The execution subject of the embodiment of the present specification is a terminal device.

Step 101: The first terminal device obtains the account identifier of the first account from a designated carrier in a set manner.

In the embodiment of this specification, the first terminal device obtains the account identifier of the first account from the designated carrier in a set manner, including:

First way:

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

Second way:

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

The designated carrier recorded here includes at least one or more of a card-type device supporting near-field communication technology, a second terminal device including the account identification of the first account, and an application client including the account identification of the first account.

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

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 can create the account identifier of the second account separately, which is not specifically limited here.

The second account recorded here includes one of a virtual account and an electronic account.

Step 105: 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.

In the embodiment of this specification, the method further includes:

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

Figure 2 is a flow chart of an account recharge method provided in an embodiment of this specification. The method may be as follows. The execution subject of the embodiment of this specification may be a smart terminal device, such as a mobile terminal device.

Step 201: The first terminal device establishes a data channel with a designated carrier containing an account identifier of a first account through short-range communication technology.

In this embodiment of the present specification, before establishing the data channel, the method further includes:

The first terminal device uses the application account used for payment to perform a transfer operation on the second account, and generates recharge data for the second account.

The designated carrier recorded here includes at least one or more of a card-type device supporting near-field communication technology, a second terminal device including the account identification of the first account, and an application client including the account identification of the first account.

Step 203: The first terminal device writes the recharge data of the second account into the designated carrier through the data channel to realize recharging for the first account.

Figure 3 is a flow chart of an account recharge method provided in an embodiment of this specification. The method may be as follows. The execution subject of the embodiment of this specification may be a designated carrier, such as an IC card, a terminal device, etc.

Step 301: The designated carrier receives recharge data sent by the first terminal device while establishing a data channel with the first terminal device through the near field communication technology.

Step 303: Process the balance data of the first account according to the recharge data.

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

When the balance data of the first account is not zero, the balance data of the first account is modified using the recharge data.

Through the schemes described in Figures 2 and 3 of the embodiments of this specification, the IC card type card device used can be recharged using a mobile terminal device (for example, a smart phone, etc.). This effectively avoids the various inconveniences caused by the fixed recharge device in real life (for example, long waiting time, the need to reach the location of the recharge device, etc.), effectively improves the recharge efficiency, and provides users with an excellent user experience.

Figure 4(a) is a flow chart of a data synchronization method provided in an embodiment of this specification. The method may be as follows. The execution subject of this embodiment of this specification is a server, and an association is established between a primary account contained in the server, a first account contained in a designated carrier, and a second account contained in a first terminal device.

Assuming that the server here is a public transportation server, the public transportation server can establish a master account for the user based on the user's identity identifier. Then, when the user applies for a public transportation card, the public transportation server can establish a mapping relationship between the master account and the card identifier of the public transportation card (that is, the account identifier of the first account); in addition, assuming that the user creates a virtual electronic card associated with the card number of the public transportation card on the terminal device, then a mapping relationship can be further established between the master account and the card identifier of the virtual electronic card (that is, the account identifier of the second account).

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.

In the embodiment of this specification, the server establishes a data channel with the designated carrier via short-range communication;

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

For example, when a user uses a bus card to pay, the consumption data of the bus card can be sent to the server through the POS machine or card swiping machine provided by the merchant. In this way, the server can promptly obtain the account identifier of the first account contained in the bus card and the first transaction data corresponding to the first account.

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.

Step 405: The server determines synchronization data of a synchronization cycle based on the first transaction data and the second transaction data, and sends the synchronization data to the first terminal device to make the data corresponding to the second account consistent with the data corresponding to the primary account.

In the embodiment of this specification, the method further includes:

If the synchronization data is a negative number, a deduction request is sent to the first terminal device, where the deduction request is used to request to deduct an amount corresponding to the negative number from an application account for payment associated with the second account.

FIG4( b ) is a flow chart of a data synchronization method provided in an embodiment of this specification. The method may be as follows. The execution subject of the embodiment of this specification is a terminal device.

Step 402: The first terminal device establishes a data channel with a designated carrier via short-range communication.

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.

In this embodiment of the present specification, before the data channel is established, the method further includes:

The first terminal device receives synchronization data sent by the server, where the synchronization data is obtained by the server according to the method described in FIG4(a);

The first terminal device modifies data corresponding to the second account using the synchronization data so that the data corresponding to the second account is consistent with the data corresponding to the primary account contained in the server;

Among them, an association relationship is established between the main account contained in the server, the first account contained in the designated carrier, and the second account contained in the first terminal device.

Figure 5 is a flow chart of a data processing method provided in an embodiment of this specification. The method may be as follows. This specification uses a public transportation scenario as an example. 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.

For physical bus cards, recharge data and payment data are written into the physical bus card, that is, 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.

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

Step 503: The designated carrier uses the physical bus card, obtains first transaction data corresponding to the physical bus card, and sends the first transaction data to the server.

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

There is no strict execution order for step 503 and step 505. They can be executed simultaneously, or in the manner described in the embodiments of this specification. Step 305 can also be executed first, and then step 303. No specific limitation is made here.

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

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

Step 511: The terminal device establishes a data channel between the physical bus card and the virtual electronic card through short-range communication.

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.

Figure 6(a) is a flow chart of a data synchronization method provided in an embodiment of this specification. The method may be as follows. The execution subject of the embodiment of this specification is a terminal device.

Step 602: The first terminal device establishes a data channel with a designated carrier via short-range communication.

In this embodiment of the present specification, before the first terminal device establishes the 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, where the prompt message is used to prompt the user to synchronize data between the first account and the second account.

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

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

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

According to the account identifier of the second account, second transaction data corresponding to the account identifier of the second account is searched.

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.

In the embodiment of this specification, synchronization data for synchronization is calculated based on the first pipeline data and the second pipeline data;

The synchronization data is synchronized to the first account and the second account respectively.

If the synchronization data is a negative number, write null to the first account and the second account respectively;

An amount corresponding to the negative number is deducted from an application account for payment associated with the second account.

In the embodiment of this specification, the method further includes:

Sending the synchronization time, the account identifier of the first account, and the first transaction data to the server, and deleting the first transaction data recorded in the carrier carrying 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.

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

Figure 6(b) is a flow chart of a data processing method provided in an embodiment of this specification. The method may be as follows. This specification uses a public transportation scenario as an example. 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.

For physical bus cards, recharge data and payment data are written into the physical bus card, that is, 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.

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

Step 603: The designated carrier uses a physical bus card to obtain and store first transaction data corresponding to the physical bus card; the terminal device uses a virtual electronic card to obtain and store second transaction data corresponding to the virtual electronic card.

Step 605: The terminal device establishes a data channel between the physical bus card and the virtual electronic card through short-range communication.

Step 607: The terminal device uses the data channel to obtain the first flow data corresponding to the physical bus card.

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

The embodiments shown in Figures 5 and 6(b) differ in that, when the transaction data for a physical bus card is generated, it is not only stored on the physical bus card but also transmitted to the physical bus card's corresponding server. However, when the transaction data for a virtual electronic card is generated, it is not only stored on the terminal device but also transmitted to the server. The terminal device containing the virtual electronic card can retrieve the physical bus card's first transaction data from the server. Based on the stored second transaction data and the retrieved 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 primary account on the server.

Based on the same inventive concept, FIG7 is a flow chart of a data synchronization method provided in an embodiment of this specification. The method may be as follows. The execution subject of the embodiment of this specification may be a terminal device or an application client that has the technical solution provided in the embodiment of this specification, and no specific limitation is made here.

Step 701: Determine whether the set synchronization condition is met. If so, execute step 703; otherwise, wait for the set time and continue to execute step 701.

In the embodiments of this specification, the synchronization conditions set may include but are not limited to the following conditions:

1. Whether the carrier carrying the first account is detected. If the carrier carrying the first account is detected, it means that the set synchronization conditions are met; if the carrier carrying the first account is not detected, it means that the set synchronization conditions are not met.

2. Whether a data synchronization request has been received. If a data synchronization request has been received, the system further determines whether a carrier carrying the first account has been detected. If a carrier carrying the first account has been detected, the system indicates that the set synchronization conditions have been met. If a carrier carrying the first account has not been detected, the system sends a prompt message to remind the user to provide the carrier carrying the first account and establish a data channel. If a data synchronization request has not been received, the system indicates that the set synchronization conditions have not been met.

3. Whether the set synchronization period has arrived. If the set synchronization period has arrived, it is further determined whether the carrier carrying the first account is detected. If the carrier carrying the first account is detected, it means that the set synchronization conditions are met. If the carrier carrying the first account has not been detected, a prompt message is sent to remind the user to provide the carrier carrying the first account and establish a data channel. If the set synchronization period has not arrived, it means that the set synchronization conditions are not met.

For the synchronization conditions listed in the embodiments of this specification, one can be selected for use, or several can be selected for use in combination. At the same time, the synchronization conditions set are not limited to those listed in the embodiments of this specification, and can also be determined according to actual needs, which is not specifically limited here.

Preferably, in the embodiment of the present specification, when a carrier carrying a first account is detected, it is possible to further determine whether there is a second account associated with the account identifier of the first account. If not, first, 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 it exists, the following operations are performed according to the scheme described in the embodiment of the present specification.

It should be noted that the carrier of the first account recorded in the embodiment of this specification can be a card that supports short-range communication (for example, 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.

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

In the embodiment of this specification, the method of obtaining the account identifier of the first account and the first transaction data corresponding to the first account includes but is not limited to:

First way:

Establishing a data channel with the carrier carrying the first account through a short-range communication method;

The account identifier of the first account and the first transaction data corresponding to the first account are obtained from the carrier by utilizing the data channel.

Assuming that the carrier of the first account is a card that supports NFC communication, the terminal device can establish a data channel with the card through NFC. Using this data channel, the account identifier of the first account (for example, the card number) and the first transaction data corresponding to the first account can be obtained from the card.

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

Second way:

Obtaining, by scanning, an account identifier of the first account from a carrier carrying the first account;

According to the account identifier of the first account, first transaction data corresponding to the account identifier of the first account is obtained from a server.

For example, if a QR code image is included in a carrier carrying a first account, and the QR code image includes the account ID of the first account, the account ID of the first account can be obtained from the carrier by scanning, and then the transaction data corresponding to the account ID of the first account can be found through the account ID of the first account.

The third way:

providing a user interface, and receiving, through the user interface, an account identifier of a first account input by a user;

According to the account identifier of the first account, first transaction data corresponding to the account identifier of the first account is obtained from a server.

For example, a user interface is provided on the terminal device, and a data synchronization operation can be initiated through the user interface. That is, the account identifier of the first account can be obtained through the user interface. Here, the account identifier of the first account can be understood as the card number of the card carrying the first account. Then, the transaction data corresponding to the account identifier of the first account can be obtained through the account identifier of the first account.

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

If a data change is detected in a second account associated with a first account, a prompt message is sent, where the prompt message is used to prompt a user to synchronize data between the first account and the second account.

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

Preferably, in the embodiment of the present specification, first transaction data generated by the first account within a synchronization cycle is obtained.

The synchronization period here can be understood as the time between two consecutive synchronization operations. The synchronization period here can be fixed or variable, and is not specifically limited 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, with the determined time T as the starting point and the time of initiating this synchronization operation as the end point, the flow data generated during this time period (from the starting point to the end point) is determined.

Step 705: Determine second transaction data corresponding to a second account associated with the first account.

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

According to the account identifier of the second account, second transaction data corresponding to the account identifier of the second account is searched.

The following describes in detail how to establish a second account associated with the first account.

First, obtain the account ID of the first account.

Here, the methods for obtaining the account ID of the first account include but are not limited to:

Obtaining the account identifier of the first account from the carrier carrying the first account through a near field communication method;

Obtaining the account identifier of the first account from the carrier carrying the first account by scanning;

An account identifier of a first account input by a user is received through a user interface.

Next, an account identifier of a second account is created based on the account identifier of the first account.

The account identifier of the second account created here may be the same as or different from the account identifier of the first account, and this is not specifically limited here.

Finally, an association relationship between the account identifier of the first account and the account identifier of the second account is established and stored.

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

Preferably, in order to prevent users from maliciously using virtual accounts, the method further includes:

After obtaining the account identifier of the second account, an association relationship is established between the account identifier of the second account and the application account used for payment.

That is, when creating a virtual account (i.e., the second account), a debit agreement is signed with the user, that is, an association relationship is established between the account identification of the second account and the application account used for payment. Once a malicious overdraft is discovered in the second account or a malicious overdraft is discovered after data synchronization is achieved between the first account and the second account, the malicious overdraft fee can be deducted from the application account used for payment that has established an association relationship with the account identification of the second account.

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

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

In the embodiment of the present specification, synchronization data for synchronization is calculated based on the first pipeline data and/or the second pipeline data;

The synchronization data is synchronized to the first account and the second account respectively.

Assume that when the second account is created, the balance data corresponding to the first account is synchronized to the second account.

If the synchronization data is a negative number, then null is written into the first account and the second account respectively; and the amount corresponding to the negative number is deducted from the application account for payment associated with the second account.

Preferably, the method further comprises:

Sending the synchronization time, the account identifier of the first account, and the first transaction data to the server, and deleting the first transaction data recorded in the carrier carrying 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.

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

Through the technical solution provided in the embodiments of this specification, when the set synchronization conditions are met, the account identification of the first account and the first transaction data corresponding to the first account are obtained; the second transaction data corresponding to the second account associated with the first account is determined; and data synchronization is performed between the first account and the second account based on the first transaction data and/or the second transaction data. In this way, the data consistency between the first account and the second account can be effectively guaranteed. That is to say, assuming that the first account is an account carried in a carrier, and the second account is a virtual electronic account associated with the first account, the user can use either the first account or the second account to complete the transaction. At the same time, through the technical solution provided in the embodiments of this specification, the consistency of the data between the two accounts can be guaranteed, thereby improving the user's payment experience.

Figure 8 is a flow chart of a data synchronization method provided in an embodiment of this specification. The data processing method is as follows. The execution subject may be a client, which may 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.

Step 801: Obtain a first account and a balance in the first account recorded in a carrier.

In the embodiments of this specification, the first account may be provided by the entity issuing the medium and written into the medium. The format of the first account may include numbers, letters, and combinations thereof, without specific limitation herein. The form of the medium may include, but is not limited to, a physical card, a button card, etc., without specific limitation herein.

In the embodiments of this specification, the numbers in the carrier can be read to form the balance in the first account. For example, the carrier includes a Near Field Communication (NFC) module, and a terminal device supporting the NFC function can write numbers to the NFC module and read numbers from the NFC module when a transaction occurs.

The embodiments of this specification may provide but are not limited to the following implementations:

1. Transmitting a radio frequency signal to the carrier, causing the carrier to send a response signal according to the radio frequency signal;

receiving a response signal; and parsing the response signal to obtain the first account and the balance in the first account.

In the embodiments of this specification, when a user makes a payment or receipt through a first account in a carrier or a second account in a client, the user brings the carrier and the client device close together. The client transmits a radio frequency signal to the carrier via the NFC module, i.e., transmits a short-range wireless radio frequency signal to the carrier. The NFC module in the carrier responds by generating a response signal that carries the first account and the balance in the first account. The client receives the response signal via the NFC module and uses a parsing module to parse the signal to determine the first account and the balance in the first account.

If the carrier includes a response module capable of receiving and responding to RF signals of other frequencies, the client device is operated to transmit RF signals of other frequencies that can be responded to. Therefore, provided that the RF signals transmitted by the client device can be responded to by the carrier, the RF signals transmitted by the client include, but are not limited to, short-range wireless RF signals, and are not limited here.

2. Receive a first account number input by the user; and based on the first account number, obtain the balance in the first account number from the server.

In an embodiment of the present specification, if the payment and collection device that receives and pays 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. The client can search the server through the first account entered by the user to find the latest balance of the first account.

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

In the embodiments of this specification, if the first account is displayed on the surface of the carrier, the client can scan the carrier surface to obtain the first account. In this case, the first account may be displayed in a prominent manner, allowing the client to obtain the first account through graphic recognition; or the first account may be recorded in an identification code such as a QR code or barcode, allowing the client to scan and interpret the identification code to obtain the first account.

To obtain the balance in the first account from the server, refer to the second method for obtaining the balance in the first account above, which will not be repeated here.

Step 803: Based on the first account, a second account associated with the first account is created on the client, and the balance in the first account is written into the second account.

In the embodiments of 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 graphical user interface, which can display the virtual account and the balance in the virtual account. The graphical user interface provides interface objects, and by operating the interface objects, payment transactions can be processed. For example, the interface objects include a QR code generation object. Clicking the QR code generation object can generate a payment QR code, which is used for payment transactions.

In the embodiments of this specification, after a client creates a second account, the client can send the second account and the balance in the first account to the server. Furthermore, when subsequent payment and receipt data is generated in the second account, the client can send this data to the server for storage. This avoids increasing the client's storage burden and allows convenient access to the second account's payment and receipt data and balance from the server during subsequent balance synchronization between the first and second accounts.

In the embodiment of this specification, based on the first account, creating a second account associated with the first account on the client may include but is not limited to:

A second account identical to the first account is created on the client, and the second account identical to the first account is determined as the second account associated with the first account. In this case, the identification information of the first account and the second account is the same, for example, having the same letters, numbers, or combinations thereof.

The second account and the first account may also be different, but an association relationship is formed according to an association rule.

Using the account processing method provided in this embodiment, users can create a second account associated with a first account at any time. This allows them to use either the first account in the carrier or the second account in the client to process payments, providing a high level of choice. In particular, even if one of the carrier or client is not available or cannot be used during a purchase, the other can still be used to make payments, enhancing the user's payment experience.

Figure 9 is a flow chart of a data synchronization method provided in an embodiment of this specification. The method, as shown below, aims to synchronize the balances of a first account and a second account associated with the first account. The execution entity of this account processing method may be a client, which may be an application running on a smart terminal. Smart terminals include, but are not limited to, mobile smart terminals such as smartphones and tablets, as well as other smart terminals such as computers and laptops.

Step 901: Obtain a first account and a balance in the first account recorded in a carrier.

The method of obtaining the first account recorded in the carrier and the balance in the first account can refer to the content of step 801 above, which will not be repeated here.

In the embodiment of this specification, in order to enable the user to promptly synchronize the payment and receipt data generated in the second account to the first account after the user generates payment and receipt data through the second account, before obtaining the first account and the balance in the first account recorded in the carrier, the processing method further includes:

If at least one payment or receipt data occurs in the second account, a reminder signal is transmitted, which is used to remind the user to provide the first account associated with the second account. This can bring convenience to the user and reduce the user's memory burden.

After receiving the reminder signal, the user may provide the first account and the balance in the first account to the client by using the three obtaining methods described in step 801 above.

In the embodiments of 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 here.

In the embodiment of this specification, when at least one payment or receipt data occurs in the second account, the reminder signal is transmitted, which may include at least one or more of the following:

Every time a payment or receipt data occurs, a reminder signal is emitted;

After a set number of payment and receipt data occurs, a reminder signal is emitted;

transmit reminder signals at regular intervals; or

If the balance in the second account is 0 or insufficient due to the occurrence of payment data, a reminder signal is transmitted.

Step 903: Determine at least one payment and receipt data of the second account associated with the first account and the balance in the second account, where the payment and receipt data includes one or both of consumption amounts and recharge amounts.

In this embodiment of the present specification, determining at least one payment and receipt data of a second account associated with the first account and the balance in the second account includes:

Determining a second account associated with the first account;

At least one payment data generated by the second account and the balance in the second account are determined.

In an embodiment of this specification, a method for determining a second account associated with a first account may include:

After obtaining the first account and the balance of the first account recorded in the carrier, a second account identical to the first account among the second accounts running on the client is determined as a second account associated with the first account.

The method for determining the second account associated with the first account may further include:

sending the first account to the server, so that the server determines a second account that is identical to the first account;

A second account obtained from the server and identical to the first account is determined as the second account associated with the first account.

The method for determining the second account associated with the first account may further include:

If the second account created based on the above step 803 is different from the first account, the second account associated with the first account is obtained from the local or server according to the association relationship between the first account and the second account.

In the embodiment of this specification, the client storing the second account can establish a connection with the backend server at any time, so determining at least one payment data of the second account and the balance in the second account may include:

Sending a payment data acquisition request to the server through the client, where the payment data acquisition request is used to request the server to send payment data of the second account and the balance in the second account;

The receiving server sends various payment and receipt data of the second account and the balance in the second account.

In this case, the payment and receipt data of the second account are stored in the server, which can save the storage burden of the local client.

In the embodiment of this specification, determining at least one payment data of the second account includes the following two situations:

1. Determine at least one payment and receipt data item for the second account in adjacent update cycles. An update cycle is defined as the time interval between two consecutive updates of the balances in the first and second accounts to the same updated balance. In this case, a payment and receipt data acquisition request is sent to the server, requesting the server to send each payment and receipt data item from the adjacent update cycles and the latest balance in the second account. Based on the payment and receipt data acquisition request, the server sends each payment and receipt data item from the most recently updated balance to the current adjacent update cycle to the client.

2. Determine the real-time payment and receipt data of the second account. With reference to step 501 above, each time payment and receipt data occurs in the second account, the balance in the first account is obtained.

Step 905: Based on the assumption that payment and receipt data occurs in the first account, the balance in the first account and the balance in the second account are updated to the same updated balance.

If, according to step 903, the payment and receipt data determined to have occurred in the second account is at least one payment and receipt data occurring in the second account in adjacent update cycles, then, based on the assumption that the payment and receipt data occurred in the first account, updating the balance in the first account and the balance in the second account to the same updated balance includes:

Based on an assumption that various payment and receipt data occur in the first account in adjacent update cycles, the balance in the first account and the balance in the second account are updated to the same updated balance.

Since the first account and the second account are unified, the payment and receipt data in the second account can be equivalent to those in the first account. Therefore, the assumption conditions for the payment and receipt data in the first account in adjacent update cycles can be set to determine the same updated balance.

For example, refer to Table 1:

Table 1

In the adjacent update cycle from the most recent update to the current one, the payment and receipt data of the second account include: recharge amount of 10 yuan; consumption amount of 14 yuan, the current balance of the second account is 16 yuan, and the current balance of the first account is 17 yuan.

From the perspective of unifying the first account and the second account, based on the assumption that payment and receipt data occurs in the first account, updating the balances in the first account and the second account to the same updated balance includes:

Based on the assumption that payment data occurs in the first account, calculating an updated balance in the first account after the payment data occurs;

The balance in the first account and the balance in the second account are updated to the updated balance.

Calculating the updated balance of the first account after the payment data is generated based on the type of each payment data includes:

If the payment data includes at least one recharge amount, then add the recharge amount to the balance in the first account;

If the payment data contains at least one consumption amount, subtract the consumption amount from the balance in the first account;

The obtained processing result is used as the updated balance.

For example, referring to Table 1, assuming that the payment data of the second account occurs in the first account, the current balance of the first account is calculated to be 17-14+10=13 yuan, and the updated balance is determined to be 13 yuan. Then, the balance of the first account and the second account is updated to 13 yuan.

The examples in Table 1 above are for reference only. The payment and receipt data in specific application scenarios may have other situations and are not specifically limited.

This method of determining at least one payment and receipt data of the second account is particularly applicable to situations where the carrier recording the first account cannot connect to the server in real time, or the client storing the second account is used frequently, and can solve the connection problem existing in the carrier where the first account is located.

In this way, each time the balances of the first account and the second account are synchronously updated, multiple payment and receipt data can be processed simultaneously, and the processing efficiency is more efficient.

If, according to step 903, it is determined that the payment and receipt data of the second account is real-time payment and receipt data, the same update of the first account and the second account can be determined by referring to the example in Table 1, which will not be repeated here.

In the embodiment of the present specification, after determining the updated balance, the client may directly update the balance in the second account to the updated balance.

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 the updated balance include:

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 device are close together, the balance of the first account recorded in the NFC module of the carrier can be modified to the updated balance.

2. If the carrier is connected to the server via a payment device with which it receives or receives payment data, the client requests the server to send the updated balance to the carrier. The device then writes the updated balance to the carrier. For example, when the carrier is in close proximity to a payment device such as a public transportation POS terminal or a cash register POS terminal, the POS terminal or cash register POS terminal can modify the balance of the first account recorded in the carrier to the updated balance.

Updating the balance in the first account is the first way of updating the balance. For the user, the operation can be performed anytime and anywhere, and the operation is convenient.

By 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.

This is particularly applicable to, but not limited to, situations where the carrier recording the first account is unable to connect to the server, or the carrier cannot connect to the server in real time.

FIG10 is a flow chart of a data synchronization method proposed in an embodiment of this specification. The processing method is as follows. The execution subject of the processing method is a server. The method is particularly applicable to, but not limited to, the carrier recording the first account can facilitate or implement connection to the server.

Step 1001: Receive payment and receipt data of at least one of a first account and a second account associated with the first account.

The payment and receipt data generated in the first account is determined when the client obtains the first account from the carrier recording the first account, and the payment and receipt data includes the recharge amount and the consumption amount.

Referring to the second method for obtaining the first account and the balance in the first account recorded in step 803 above, the server can receive the payment data of the first account through the payment device that exchanges payment data with the carrier. The server can also receive the payment data of the second account directly from the client that stores the second account.

Step 1003: Update the balance in the first account and the balance in the second account to the same updated balance after the payment and receipt data occurs.

The updated balance in the first account is written into the carrier through the payment device.

In the embodiment of this specification, after receiving payment data generated by the first account and at least one of the second accounts associated with the first account, the processing method may further include:

Determining at least one payment and receipt data received in adjacent update cycles, where an update cycle is a time interval between two adjacent updates of the balances in the first account and the second account to the same updated balance;

The balance in the first account and the balance in the second account are updated to the same updated balance after the payment data is generated, including:

The balance in the first account and the balance in the second account are both updated to the same updated balance after the payment and receipt data occurs in adjacent update cycles.

In this case, referring to the content in step 905 above, one of the first account and the second account can be determined as the base account, assuming that the payment and receipt data of the base account also occurs in the other account, thereby determining an updated account.

At this time, each update can process multiple payment and receipt data at the same time, improving processing efficiency.

In the embodiment of this specification, updating the balance in the first account and the balance in the second account to the same updated balance after the payment data is generated may further include:

Each time a payment data is received, the balance in the first account and the balance in the second account are updated to the same updated balance after the payment data is generated.

In the embodiments of this specification, the processing method may further include:

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

The embodiments of this specification provide another technical means for synchronously updating the balances in the first account and the second account to the updated balances, thereby keeping the balances in the first account and the second account consistent.

Figure 11 is a schematic diagram of the structure 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:

The acquiring unit 1101 acquires the account identifier of the first account from the designated carrier in a set manner;

A creating unit 1102 creates an account identifier for a second account based on the account identifier of the first account;

The storage unit 1103 establishes and stores a mapping relationship between the account identifier of the first account and the account identifier of the second account.

In another embodiment of the present specification, the acquiring unit 1101 acquires the account identifier of the first account from the designated carrier in a set manner, including:

A data channel is established with a designated carrier through a near field communication technology, and an account identifier of the first account is obtained from the designated carrier through the data channel.

In another embodiment of the present specification, the acquiring unit 1101 acquires the account identifier of the first account from the designated carrier in a set manner, including:

The account identifier of the first account is obtained from the designated carrier by scanning.

In another embodiment of the present specification, after obtaining the account identifier of the second account, the storage unit 1103 establishes and stores an association relationship between the account identifier of the second account and the application account used for payment.

In another embodiment of the present specification, the designated carrier includes at least one or more of a card-type device supporting near-field communication technology, a second terminal device including the account identification of the first account, and an application client including the account identification of the first account.

In another embodiment of the present specification, the second account includes one of a virtual account and an electronic account.

It should be noted that the account creation device described in the embodiments of this specification can be implemented by software or hardware, and is not specifically limited here.

Based on the same inventive concept, an embodiment of this specification further provides an account creation device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

Obtaining the account identifier of the first account from the specified carrier in a set manner;

Creating an account identifier for a second account based on the account identifier of the first account;

A mapping relationship between the account identifier of the first account and the account identifier of the second account is established and stored.

Among them, other functions of the processor can also refer to the contents recorded in the above embodiments, which will not be repeated here.

Based on the same inventive concept, an embodiment of this specification further provides a computer-readable storage medium, which includes a program for use in conjunction with an electronic device. The program can be executed by a processor to complete the following steps:

Obtaining the account identifier of the first account from the specified carrier in a set manner;

Creating an account identifier for a second account based on the account identifier of the first account;

A mapping relationship between the account identifier of the first account and the account identifier of the second account is established and stored.

Among them, other functions of the processor can also refer to the contents recorded in the above embodiments, which will not be repeated here.

Figure 12 is a schematic diagram of the structure 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:

An establishing unit 1201 establishes a data channel with a designated carrier including an account identifier of a first account through a near field communication technology;

The recharging unit 1202 writes the recharging data of the second account into the designated carrier through the data channel to realize recharging for the first account.

In another embodiment of the present specification, the account recharging device further includes: a generating unit 1203, wherein:

The generating unit 1203 performs a transfer operation on the second account using the application account used for payment to generate recharge data of the second account.

In another embodiment of the present specification, the designated carrier includes at least one or more of a card-type device supporting near-field communication technology, a second terminal device including the account identification of the first account, and an application client including the account identification of the first account.

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

Based on the same inventive concept, an embodiment of this specification provides an account recharging device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

establishing a data channel with a designated carrier including the account identifier of the first account through a near field communication technology;

The recharge data of the second account is written into the designated carrier through the data channel to realize recharging the first account.

Among them, other functions of the processor can also refer to the contents recorded in the above embodiments, which will not be repeated here.

Based on the same inventive concept, an embodiment of this specification further provides a computer-readable storage medium, which includes a program for use in conjunction with an electronic device. The program can be executed by a processor to complete the following steps:

establishing a data channel with a designated carrier including the account identifier of the first account through a near field communication technology;

The recharge data of the second account is written into the designated carrier through the data channel to realize recharging the first account.

FIG13 is a schematic diagram of the structure 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:

The receiving unit 1301 receives the recharge data sent by the first terminal device when establishing a data channel with the first terminal device through the near field communication technology;

The processing unit 1302 processes the balance data of the first account according to the recharge data.

In another embodiment of the present specification, the processing unit 1302 processes the balance data of the first account according to the recharge data, including:

When the balance data of the first account is zero, writing the recharge data into the first account;

When the balance data of the first account is not zero, the balance data of the first account is modified using the recharge data.

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

Based on the same inventive concept, an embodiment of this specification provides an account recharging device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

When a data channel is established with the first terminal device through the near field communication technology, receiving recharge data sent by the first terminal device;

The balance data of the first account is processed according to the recharge data.

Among them, other functions of the processor can also refer to the contents recorded in the above embodiments, which will not be repeated here.

Based on the same inventive concept, an embodiment of this specification further provides a computer-readable storage medium, which includes a program for use in conjunction with an electronic device. The program can be executed by a processor to complete the following steps:

When a data channel is established with the first terminal device through the near field communication technology, receiving recharge data sent by the first terminal device;

The balance data of the first account is processed according to the recharge data.

FIG14 is a schematic diagram of the structure of a data synchronization device provided by an embodiment of this specification. The data synchronization device includes: an acquisition unit 1401, a receiving unit 1402 and a synchronization unit 1403, wherein:

The acquiring 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 near field communication method;

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;

The synchronization unit 1403 determines synchronization data of a synchronization cycle based on the first transaction data and the second transaction data, and sends the synchronization data to the first terminal device to make the data corresponding to the second account consistent with the data corresponding to the main account.

Among them, the data processing device described in the embodiments of this specification can be used in a server, and an association relationship 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.

In another embodiment of the present specification, the acquiring 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 short-range communication, including:

Establishing a data channel with the designated carrier via short-range communication;

When it is determined that the transaction has 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.

In another embodiment of the present specification, the data synchronization device further includes: a sending unit 1404, wherein:

The sending unit 1404 sends a deduction request to the first terminal device if the synchronization data is a negative number, where the deduction request is used to request to deduct an amount corresponding to the negative number from an application account for payment associated with the second account.

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

Based on the same inventive concept, an embodiment of this specification provides a data synchronization device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

Obtaining an account identifier of a first account and first transaction data corresponding to the first account from the designated carrier through a near field communication method;

receiving the account identifier of the second account and second transaction data corresponding to the second account sent by the first terminal device;

determining synchronization data for a synchronization period based on the first transaction data and the second transaction data, and sending the synchronization data to the first terminal device so that data corresponding to the second account is consistent with data corresponding to the primary account;

Among them, an association relationship is established between the main account contained in the server, the first account contained in the designated carrier, and the second account contained in the first terminal device.

Among them, other functions of the processor can also refer to the contents recorded in the above embodiments, which will not be repeated here.

Based on the same inventive concept, an embodiment of this specification further provides a computer-readable storage medium, which includes a program for use in conjunction with an electronic device. The program can be executed by a processor to complete the following steps:

Obtaining an account identifier of a first account and first transaction data corresponding to the first account from the designated carrier through a near field communication method;

receiving the account identifier of the second account and second transaction data corresponding to the second account sent by the first terminal device;

determining synchronization data for a synchronization period based on the first transaction data and the second transaction data, and sending the synchronization data to the first terminal device so that data corresponding to the second account is consistent with data corresponding to the primary account;

Among them, an association relationship is established between the main account contained in the server, the first account contained in the designated carrier, and the second account contained in the first terminal device.

FIG15 is a schematic diagram of the structure of a data synchronization device provided by an embodiment of this specification. The data synchronization device includes: an establishment unit 1501 and a synchronization unit 1502, wherein:

Establishing unit 1501, establishing a data channel with a designated carrier via short-range communication;

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.

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

The receiving unit 1503 receives synchronization data sent by the server, where the synchronization data is obtained by the server according to the synchronization method described above;

The processing unit 1504 modifies the data corresponding to the second account using the synchronized data so that the data corresponding to the second account is consistent with the data corresponding to the primary account in the server;

Among them, an association relationship is established between the main account contained in the server, the first account contained in the designated carrier, and the second account contained in the first terminal device.

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

Based on the same inventive concept, an embodiment of this specification provides a data synchronization device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

Establish a data channel with a designated carrier through short-range communication;

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.

Among them, other functions of the processor can also refer to the contents recorded in the above embodiments, which will not be repeated here.

Based on the same inventive concept, an embodiment of this specification further provides a computer-readable storage medium, which includes a program for use in conjunction with an electronic device. The program can be executed by a processor to complete the following steps:

Establish a data channel with a designated carrier through short-range communication;

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.

Figure 16 is a schematic diagram of the structure of a data synchronization device provided by 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:

Establishing unit 1601, establishing a data channel with a designated carrier via a short-range communication method;

An acquiring unit 1602 acquires, through the data channel, an account identifier of a first account and first transaction data corresponding to the first account contained in the designated carrier;

The determining unit 1603 determines second transaction data corresponding to a second account associated with the first account;

The synchronization unit 1604 performs data synchronization between the first account and the second account according to the first transaction data and the second transaction data.

In another embodiment of the present specification, the data synchronization device further includes: a sending unit 1605, wherein:

Before establishing the data channel, the sending unit 1605 sends a prompt message if it is detected that the data corresponding to the second account associated with the first account has changed. The prompt message is used to prompt the user to synchronize data between the first account and the second account.

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

Determining, based on the account identifier of the first account, the account identifier of a second account associated with the account identifier of the first account;

According to the account identifier of the second account, second transaction data corresponding to the account identifier of the second account is searched.

In another embodiment of the present specification, the synchronization unit 1604 synchronizes data between the first account and the second account according to the first transaction data and the second transaction data, including:

Calculating synchronization data for synchronization based on the first pipeline data and the second pipeline data;

The synchronization data is synchronized to the first account and the second account respectively.

In another embodiment of the present specification, the synchronization unit 1604 synchronizes the synchronization data to the first account and the second account, including:

If the synchronization data is a negative number, write null to the first account and the second account respectively;

An amount corresponding to the negative number is deducted from an application account for payment associated with the second account.

In another embodiment of the present specification, the data synchronization device further includes: a deleting unit 1606, wherein:

The deleting 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 carrying 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.

In another embodiment of the present specification, the transaction data includes at least one or more of consumption data and recharge data.

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

Based on the same inventive concept, an embodiment of this specification provides a data synchronization device, comprising: at least one memory and at least one processor, wherein the memory stores a program and is configured to cause the processor to execute the following steps:

Establish a data channel with a designated carrier through short-range communication;

Acquire, through the data channel, an account identifier of a first account and first transaction data corresponding to the first account contained in the designated carrier;

Determining second transaction data corresponding to a second account associated with the first account;

Data synchronization is performed between the first account and the second account based on the first transaction data and the second transaction data.

Among them, other functions of the processor can also refer to the contents recorded in the above embodiments, which will not be repeated here.

Based on the same inventive concept, an embodiment of this specification further provides a computer-readable storage medium, which includes a program for use in conjunction with an electronic device. The program can be executed by a processor to complete the following steps:

Establish a data channel with a designated carrier through short-range communication;

Acquire, through the data channel, an account identifier of a first account and first transaction data corresponding to the first account contained in the designated carrier;

Determining second transaction data corresponding to a second account associated with the first account;

Data synchronization is performed between the first account and the second account based on the first transaction data and the second transaction data.

Through the technical solutions provided in the embodiments of this specification, a second account is created on a terminal device for a first account contained in a designated carrier, and the second account in the terminal device is used to recharge the first account and ensure data consistency between the first and second accounts through short-range communication. In other words, assuming that the first account is an account carried in a designated carrier and the second account is a virtual electronic account associated with the first account, the user can complete the transaction using either the first account or the second account. At the same time, the technical solutions provided in the embodiments of this specification can ensure data consistency between the two accounts, thereby improving the user's payment experience.

In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD through their own programming, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, 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, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

The controller can be implemented in any suitable manner. For example, the controller 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 Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules that implement the method and structures within the hardware component.

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

For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this application, the functions of each unit can be implemented in the same or multiple software and/or hardware.

It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

The present invention is described with reference to the flowcharts and/or block diagrams of the methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of processes and/or boxes in the flowchart and/or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

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

Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules 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 technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included within the scope of the claims of the present application.

Claims (52)

1. An account creation method, comprising: The first terminal device obtains the account identifier of the first account from the designated carrier in a set manner, wherein the first account is the account carried in the designated carrier; The first terminal device creates an account identifier for a second account based on the account identifier of the first account, wherein the second account is a virtual electronic account associated with the first account; 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, so that 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, it can synchronize the data between the first account and the second account, so that the data of the first account and the second account are consistent. 2. The account creation method according to claim 1, wherein the first terminal device obtains the account identifier of the first account from a designated carrier through a set method, 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. 3. The account creation method according to claim 1, wherein the first terminal device obtains the account identifier of the first account from a designated carrier through a set method, including: The first terminal device obtains the account identifier of the first account from the designated carrier by scanning. 4. 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. 5. 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. 6. The account creation method according to claim 1, wherein the second account includes one of a virtual account and an electronic account. 7. An account top-up method, comprising: 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 account is an account carried in the designated carrier. 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 second account is created by the first terminal device based on the account identifier of the first account and is a virtual electronic account associated with the first account. 8. The account recharge method according to claim 7, 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. 9. The account recharge method according to claim 7, 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. 10. A method for topping up an account, comprising: When a designated carrier establishes a data channel with a first terminal device through near-field communication technology, it receives recharge data sent by the first terminal device. The recharge data is recharge data of a second account written by the first terminal device to the designated carrier through the data channel. The second account is created by the first terminal device based on the account identifier of the first account, and the second account is a virtual electronic account associated with the first account. Based on the recharge data, the balance data of the first account is processed. 11. The account recharge method according to claim 10, wherein the balance data of the first account is processed based on the recharge data, including: 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. 12. A data synchronization method, wherein a primary account contained in a server is associated with a first account contained in a specified carrier and a second account contained in a first terminal device, the association enabling data corresponding to the primary account, data corresponding to the first account, and data corresponding to the second account to remain consistent, 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 short-range communication. 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 second account is created by the first terminal device based on the account identifier of the first account, and the second account is a virtual electronic account associated with the first account. 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. 13. The data synchronization method according to claim 12, 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 via short-range communication, 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. 14. The data synchronization method according to claim 12, 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. 15. A data synchronization method, comprising: The first terminal device establishes a data channel with the designated carrier through short-range communication. 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 second account is created by the first terminal device based on the account identifier of the first account, and the second account is a virtual electronic account associated with the first account. 16. The data synchronization method according to claim 15, further comprising: The first terminal device receives synchronization data sent by the server, wherein the synchronization data is obtained by the server in the manner described in claim 12; 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. 17. A data synchronization method, comprising: The first terminal device establishes a data channel with the designated carrier through short-range communication. 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 second account is created by the first terminal device based on the account identifier of the first account. The second account is a virtual electronic 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. 18. The data synchronization method according to claim 17, wherein before the first terminal device establishes a data channel, the method further comprises: 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. 19. The data synchronization method according to claim 17, 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. 20. The data synchronization method according to claim 17, 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. 21. The data synchronization method according to claim 20, 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. 22. The data synchronization method according to claim 17 or 21, 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. 23. The data synchronization method according to claim 17, wherein the transaction data includes at least one or more of consumption data and recharge data. 24. An account creation device, comprising: The acquisition unit acquires the account identifier of a first account from a specified carrier in a set manner, wherein the first account is an account carried in the specified 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 establishes and stores a mapping relationship between the account identifier of the first account and the account identifier of the second account, so that 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, it can synchronize the data between the first account and the second account, so that the data of the first account and the second account are consistent. 25. The account creation device according to claim 24, wherein the acquisition unit acquires the account identifier of the first account from a designated carrier in a predetermined manner, comprising: 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. 26. The account creation device according to claim 24, wherein the obtaining unit obtains the account identifier of the first account from a designated carrier in a predetermined manner, comprising: The account identifier of the first account is obtained from the specified carrier by scanning. 27. The account creation device according to claim 24, After obtaining the account identifier of the second account, the storage unit establishes and stores the association between the account identifier of the second account and the application account used for payment. 28. The account creation device according to claim 24, wherein the designated carrier comprises 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. 29. The account creation device according to claim 24, wherein the second account includes one of a virtual account and an electronic account. 30. An account recharge device, comprising: The unit establishes a data channel with a designated carrier containing an account identifier of a first account through near-field communication technology; the first account is an account carried on the designated carrier. 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 second account is created by the first terminal device based on the account identifier of the first account and is a virtual electronic account associated with the first account. 31. The account recharge device according to claim 30, further comprising: a generation unit, wherein: The generation unit uses the application account used for payment to perform a transfer operation to the second account, generating the recharge data for the second account. 32. The account recharge device according to claim 30, wherein the designated carrier comprises 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. 33. An account top-up device, comprising: The receiving unit, when establishing a data channel with the first terminal device through near-field communication technology, receives recharge data sent by the first terminal device. The recharge data is the recharge data of the second account written by the first terminal device to a designated carrier through the data channel. The second account is created by the first terminal device based on the account identifier of the first account, and the second account is a virtual electronic account associated with the first account. The processing unit processes the balance data of the first account based on the recharge data. 34. The account recharge device according to claim 33, wherein the processing unit processes the balance data of the first account based on the recharge data, including: 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. 35. 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, including: 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. 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 second account is created by the first terminal device based on the account identifier of the first account, and the second account is a virtual electronic account associated with the first account. 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. 36. The data synchronization device according to claim 35, wherein 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 via short-range communication, comprising: A data channel is established with the designated carrier via short-range communication. 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. 37. The data synchronization device according to claim 35, further comprising: a sending unit, wherein: If the synchronization data is negative, the sending unit 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. 38. A data synchronization device, comprising: Establish a unit to establish a data channel with a designated carrier via short-range communication; 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 second account is created by the first terminal device based on the account identifier of the first account, and the second account is a virtual electronic account associated with the first account. 39. The data synchronization device according to claim 38, further comprising: a receiving unit and a processing unit, wherein: The receiving unit receives synchronization data sent by the server, the synchronization data being obtained by the server in the manner described in claim 12; The processing unit 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. 40. A data synchronization device, comprising: Establish a unit to establish a data channel with a designated carrier via short-range communication; 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 second account is created by the first terminal device based on the account identifier of the first account, and the second account is a virtual electronic account associated with the first account. 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. 41. The data synchronization device according to claim 40, further comprising: a sending unit, wherein: Before establishing a data channel, if the sending unit 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. 42. The data synchronization device according to claim 40, wherein the determining unit determines 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. 43. The data synchronization device according to claim 40, wherein 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, 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. 44. The data synchronization device according to claim 43, wherein the synchronization unit synchronizes the synchronization data to the first account and the second account, comprising: 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. 45. The data synchronization device according to claim 40 or 44, further comprising: a deletion unit, wherein: The deletion unit 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, 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. 46. The data synchronization device according to claim 40, wherein the transaction data includes at least one or more of consumption data and recharge data. 47. 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 account identifier of the first account is obtained from the specified carrier by a set method, wherein the first account is the account carried in the specified carrier; Based on the account identifier of the first account, an account identifier for the second account is created, wherein the second account is a virtual electronic account associated with the first account; A mapping relationship is established and stored between the account identifier of the first account and the account identifier of the second account, so that 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, the data between the first account and the second account is synchronized, so that the data of the first account and the second account are consistent. 48. 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: A data channel is established with a designated carrier containing the account identifier of a first account through near-field communication technology, wherein the first account is an account carried on the designated carrier; The recharge data of the second account is written into the designated carrier through the data channel to recharge the first account. The second account is created by the first terminal device based on the account identifier of the first account and is a virtual electronic account associated with the first account. 49. 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: When a data channel is established with a first terminal device through near-field communication technology, the recharge data sent by the first terminal device is received. The recharge data is the recharge data of the second account written by the first terminal device to a designated carrier through the data channel. The second account is created by the first terminal device based on the account identifier of the first account. The second account is a virtual electronic account associated with the first account. Based on the recharge data, the balance data of the first account is processed. 50. 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 through short-range communication. The system 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 second account is created by the first terminal device based on the account identifier of the first account, and the second account is a virtual electronic account associated with the first account. 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; 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 remain consistent. 51. A data synchronization 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: Establish a data channel with a designated carrier through short-range communication methods; 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 second account is created by the first terminal device based on the account identifier of the first account, and the second account is a virtual electronic account associated with the first account. 52. A data synchronization 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: Establish a data channel with a designated carrier through short-range communication methods; 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. The second account is created by the first terminal device based on the account identifier of the first account. The second account is a virtual electronic 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.