WO2019033994A1 - 一种账户创建、账户充值、数据同步方法及设备 - Google Patents

一种账户创建、账户充值、数据同步方法及设备 Download PDF

Info

Publication number
WO2019033994A1
WO2019033994A1 PCT/CN2018/099869 CN2018099869W WO2019033994A1 WO 2019033994 A1 WO2019033994 A1 WO 2019033994A1 CN 2018099869 W CN2018099869 W CN 2018099869W WO 2019033994 A1 WO2019033994 A1 WO 2019033994A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
data
synchronization
identifier
terminal device
Prior art date
Application number
PCT/CN2018/099869
Other languages
English (en)
French (fr)
Inventor
翟芬
顾春雷
沈凌楠
陈戈
齐杰
靳慧峰
宋学夫
Original Assignee
阿里巴巴集团控股有限公司
翟芬
顾春雷
沈凌楠
陈戈
齐杰
靳慧峰
宋学夫
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 翟芬, 顾春雷, 沈凌楠, 陈戈, 齐杰, 靳慧峰, 宋学夫 filed Critical 阿里巴巴集团控股有限公司
Priority to KR1020197030513A priority Critical patent/KR102259714B1/ko
Priority to MYPI2019005808A priority patent/MY191630A/en
Priority to AU2018317073A priority patent/AU2018317073A1/en
Priority to EP18846030.7A priority patent/EP3611684A4/en
Priority to SG11201909626V priority patent/SG11201909626VA/en
Priority to JP2019556177A priority patent/JP6946461B2/ja
Priority to CA3059627A priority patent/CA3059627C/en
Publication of WO2019033994A1 publication Critical patent/WO2019033994A1/zh
Priority to PH12019502426A priority patent/PH12019502426A1/en
Priority to US16/698,327 priority patent/US10902412B2/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327Short range or proximity payments by means of M-devices
    • G06Q20/3278RFID or NFC payments by means of M-devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/349Rechargeable cards
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/351Virtual cards
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/363Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G06Q20/3678Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes e-cash details, e.g. blinded, divisible or detecting double spending

Definitions

  • the present specification relates to the field of Internet information processing technology and computer technology, and in particular, to an account creation, account refilling, data synchronization method and device.
  • cash payment is a payment method that is very familiar to everyone living in modern society.
  • cash payments bring some inconvenience to people (for example, need to prepare a small amount of change, etc.).
  • deposit payment can be understood as a user directly depositing money or cash in a bank account into a designated IC card (Integrated Circuit Card), and then using the designated IC card for consumption.
  • IC card Integrated Circuit Card
  • This method can also be called an electronic wallet.
  • the current implementation of the circle generally requires the implementation of related storage operations in a specific device.
  • the embodiment of the present specification provides an account creation, account refilling, data synchronization method and device, so as to improve the convenience of the deposit payment.
  • the embodiment of the present specification provides an account creation method, including:
  • the first terminal device creates an account identifier of the second account according to the account identifier of the first account;
  • the first terminal device establishes and stores a mapping relationship between an account identifier of the first account and an account identifier of the second account.
  • the embodiment of the present specification provides a method for recharging an account, including:
  • the first terminal device establishes a data channel by using a short-range communication technology with a designated carrier that includes an account identifier of the first account;
  • the first terminal device writes the recharge data of the second account into the designated carrier by using the data channel, so as to implement recharging for the first account.
  • the embodiment of the present specification provides a method for recharging an account, including:
  • the designated carrier receives the refill data sent by the first terminal device when the data channel is established with the first terminal device by using the short-range communication technology
  • the balance data of the first account is processed according to the recharge data.
  • the embodiment of the present specification provides a data synchronization method, and the relationship between the primary account included in the server and the first account included in the specified carrier and the second account included in the first terminal device includes:
  • the embodiment of the present specification provides a data synchronization method, including:
  • the first terminal device establishes a data channel with the designated carrier by using a short-range communication manner
  • the first terminal device synchronizes the balance data corresponding to the second account to the designated carrier by using the data channel, so that the data corresponding to the first account included in the specified carrier and the data corresponding to the second account Consistent.
  • the embodiment of the present specification provides a data synchronization method, including:
  • the first terminal device establishes a data channel with the designated carrier by using a short-range communication manner
  • the first terminal device performs data synchronization between the first account and the second account according to the first flow data and the second flow data.
  • the embodiment of the present specification provides an account creation device, including:
  • a storage unit establishing and storing a mapping relationship between the account identifier of the first account and the account identifier of the second account.
  • the embodiment of the present specification provides an account refilling device, including:
  • a refilling unit wherein the refill data of the second account is written into the designated carrier through the data channel, so as to perform recharging for the first account.
  • the embodiment of the present specification provides an account refilling device, including:
  • the receiving unit receives the refill data sent by the first terminal device in the case that the data channel is established with the first terminal device by using the short-range communication technology
  • the processing unit processes the balance data of the first account according to the recharge data.
  • the embodiment of the present specification provides a data synchronization device, and the relationship between the primary account included in the server and the first account included in the specified carrier and the second account included in the first terminal device includes:
  • the receiving unit receives the account identifier of the second account sent by the first terminal device and the second pipeline data corresponding to the second account;
  • a synchronization unit according to the first flow data and the second flow data, determining synchronization data of a synchronization period, and transmitting the synchronization data to the first terminal device, so that the second account corresponds to The data is consistent with the data corresponding to the primary account.
  • the embodiment of the present specification provides a data synchronization device, including:
  • 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 included in the specified carrier is consistent with the data corresponding to the second account.
  • the embodiment of the present specification provides a data synchronization device, including:
  • Determining a unit determining second flow data corresponding to the second account associated with the first account
  • the synchronization unit performs data synchronization between the first account and the second account according to the first flow data and the second flow data.
  • the embodiment of the present specification provides an account creation device, including: at least one memory and at least one processor, wherein the memory stores a program, and is configured by the processor to perform the following steps:
  • An embodiment of the present specification provides an account refilling device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured by the processor to perform the following steps:
  • the refill data of the second account is written into the designated carrier through the data channel to implement recharging of the first account.
  • the embodiment of the present specification provides an account refilling device, including: at least one memory and at least one processor, wherein the memory stores a program, and is configured by the processor to perform the following steps:
  • the balance data of the first account is processed according to the recharge data.
  • the embodiment of the present specification provides a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program, and is configured by the processor to perform the following steps:
  • the primary account included in the server establishes an association relationship with the first account included in the specified carrier and the second account included in the first terminal device.
  • the embodiment of the present specification provides a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program, and is configured by the processor to perform the following steps:
  • the balance data corresponding to the second account is synchronized to the designated carrier by the data channel, so that the data corresponding to the first account included in the specified carrier is consistent with the data corresponding to the second account.
  • the embodiment of the present specification provides a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program, and is configured by the processor to perform the following steps:
  • Replenishing the first account and securing the first account and the second account by means of short-range communication by creating a second account for the first account included in the designated carrier on the terminal device and using the second account in the terminal device Data consistency between. That is, 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 either use the first account to complete the transaction or use the second account. The account completes the transaction.
  • the technical solution provided by the embodiments of the present specification can ensure the consistency of data between the two accounts, thereby improving the payment experience of the user.
  • FIG. 1 is a schematic flowchart diagram of an account creation method according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of a method for recharging an account according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a method for recharging an account according to an embodiment of the present disclosure
  • FIG. 4(a) is a schematic flow chart of a data synchronization method according to an embodiment of the present specification
  • 4(b) is a schematic flow chart of a data synchronization method according to an embodiment of the present specification
  • FIG. 5 is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure
  • FIG. 6(a) is a schematic flow chart of a data synchronization method according to an embodiment of the present specification
  • FIG. 6(b) is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of an account creation device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of an account refilling device according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of an account refilling device according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of a data synchronization device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a data synchronization device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a data synchronization device according to an embodiment of the present disclosure.
  • the use of a mobile payment scheme can bring convenience in payment, but there are some inconveniences for the user. For example, if the user does not carry the mobile terminal or the mobile terminal is in a power-free state, the user will not be able to use the mobile terminal for payment, which means that if the card payment and the mobile payment can complement each other, the user's production and life will be facilitated.
  • the so-called electronic payment method refers to the parties engaged in e-commerce transactions (including: consumers, manufacturers and financial institutions), through the information network, using digital methods and secure information transmission means for money payment or capital flow. Compared with cash payment and deposit payment, it can bring more convenience to users.
  • an embodiment of the present specification provides an account creation, an account refill, a data synchronization method, and a device, by creating a second account for a first account included in a specified carrier on the terminal device, and using the terminal device.
  • the first account is recharged by means of short-range communication and the data consistency between the first account and the second account is guaranteed. That is, 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 either use the first account to complete the transaction or use the second account. The account completes the transaction.
  • the technical solution provided by the embodiments of the present specification can ensure the consistency of data between the two accounts, thereby improving the payment experience of the user.
  • IC card Integrated circuit card
  • Smart Card Smart Card
  • bus card When the user takes public transportation, the user can pay the transportation fee through the bus card. When the data exchange between the bus card and the credit card machine of the public transportation is performed, the value in the bus card is read, and the transportation fee is deducted.
  • the recharge of the bus card is generally completed by means of a circle, that is, it needs to be recharged by a special device to the designated recharge station.
  • FIG. 1 is a schematic flowchart diagram of an account creation method provided by an implementation of the present specification.
  • the method can be as follows.
  • the execution subject of the embodiment of the present specification is a terminal device.
  • Step 101 The first terminal device acquires the account identifier of the first account from the designated carrier by using a set manner.
  • the first terminal device obtains the account identifier of the first account from the specified carrier by using a setting manner, including:
  • the first terminal device establishes a data channel with the designated carrier by using a short-range communication technology, and obtains an account identifier of the first account from the designated carrier through the data channel.
  • the first terminal device obtains the account identifier of the first account from the specified carrier by scanning.
  • the specified carrier described herein includes at least one of a card device supporting a short-range communication technology, a second terminal device including an account identifier of the first account, and an application client including an account identifier of the first account.
  • a card device supporting a short-range communication technology includes at least one of a card device supporting a short-range communication technology, a second terminal device including an account identifier of the first account, and an application client including an account identifier of the first account.
  • Step 103 The first terminal device creates an account identifier of the second account according to the account identifier of the first account.
  • the first terminal device may create an account identifier of the second account based on the account identifier of the first account, or may separately create an account identifier of the second account, where not Make specific limits.
  • the second account described herein includes one of a virtual account and an electronic account.
  • Step 105 The first terminal device establishes and stores a mapping relationship between an account identifier of the first account and an account identifier of the second account.
  • the method further includes:
  • the first terminal device 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 an application account for payment.
  • FIG. 2 is a schematic flowchart diagram of an account refilling method according to an embodiment of the present disclosure.
  • the method can be as follows.
  • the execution body of the embodiment of the present specification may be a smart terminal device, for example, a mobile terminal device.
  • Step 201 The first terminal device establishes a data channel by using a short-range communication technology with a designated carrier that includes an account identifier of the first account.
  • the method before the data channel is established, the method further includes:
  • the first terminal device performs a transfer operation to the second account by using an application account for payment, and generates recharge data of the second account.
  • the specified carrier described herein includes at least one of a card device supporting a short-range communication technology, a second terminal device including an account identifier of the first account, and an application client including an account identifier of the first account.
  • a card device supporting a short-range communication technology includes at least one of a card device supporting a short-range communication technology, a second terminal device including an account identifier of the first account, and an application client including an account identifier of the first account.
  • Step 203 The first terminal device writes the recharge data of the second account into the designated carrier by using the data channel, so as to perform recharging for the first account.
  • FIG. 3 is a schematic flowchart diagram of an account refilling method according to an embodiment of the present disclosure.
  • the method can be as follows.
  • the executive body of the embodiment of the present specification may be a designated carrier, such as an IC card, a terminal device, or the like.
  • Step 301 The designated carrier receives the recharge data sent by the first terminal device in the case that the data channel is established with the first terminal device by using the short-range communication technology.
  • Step 303 Process the balance data of the first account according to the recharge data.
  • the refill data is written into the first account
  • the balance data of the first account is not zero
  • the balance data of the first account is modified using the refill data.
  • the mobile device for example, a smart phone or the like
  • the mobile device can be used to recharge the card type device of the IC card type used, thereby effectively avoiding the actual life.
  • the recharge equipment such as: long waiting time, need to reach the location of the recharge equipment, etc.
  • it can effectively improve the recharge efficiency, while giving users excellent users.
  • the recharge equipment such as: long waiting time, need to reach the location of the recharge equipment, etc.
  • FIG. 4(a) is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • the method can be as follows.
  • the executor of the embodiment of the present specification is a server, and the primary account included in the server establishes an association relationship with the first account included in the specified carrier and the second account included in the first terminal device.
  • the public transportation server can establish a master account for the user according to the identity of the user. Then, when the user applies for the bus card, the public transportation server can establish the card identifier of the master account and the bus card (That is, the mapping relationship between the account identifiers of the first account; in addition, if the user creates a virtual electronic card associated with the card number of the bus card on the terminal device, the card of the master account and the virtual electronic card may be further established.
  • the mapping relationship between the identifiers ie, the account identifiers of the second accounts).
  • Step 401 The server acquires an account identifier of the first account and the first pipeline data corresponding to the first account from the specified carrier by using a short-range communication manner.
  • the server establishes a data channel with the specified carrier by using a short-range communication manner
  • the POS machine or the card swiping machine provided by the merchant can send the consumption data of the bus card to the server, so that the server can timely obtain the account identifier of the first account included in the bus card.
  • the first flow data corresponding to the first account can be sent to the server, so that the server can timely obtain the account identifier of the first account included in the bus card.
  • Step 403 The server receives an account identifier of the second account sent by the first terminal device and second flow data corresponding to the second account.
  • Step 405 The server determines synchronization data of one synchronization period according to the first flow data and the second flow data, and sends the synchronization data to the first terminal device, so that the second The data corresponding to the account is consistent with the data corresponding to the primary account.
  • the method further includes:
  • the synchronization data is a negative number
  • sending a debit request to the first terminal device where the debit request is used to request to deduct the negative number from an application account for payment associated with the second account The amount.
  • FIG. 4(b) is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • the method can be as follows.
  • the execution subject of the embodiment of the present specification is a terminal device.
  • Step 402 The first terminal device establishes a data channel with the designated carrier by using a short-range communication manner.
  • Step 404 The first terminal device synchronizes the balance data corresponding to the second account to the designated carrier by using the data channel, so that the data corresponding to the first account included in the specified carrier is related to the second account. The corresponding data is consistent.
  • the method before the data channel is established, the method further includes:
  • 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 primary account included in the server;
  • the primary account included in the server establishes an association relationship with the first account included in the specified carrier and the second account included in the first terminal device.
  • FIG. 5 is a schematic flowchart diagram of a data processing method according to an embodiment of the present disclosure.
  • the method can be as follows.
  • the embodiment of the present specification is described by taking a public transportation scenario as an example.
  • the first account corresponds to the account in the physical bus card
  • the second account corresponds to the account in the virtual electronic card
  • the first account and the second account establish an association relationship.
  • the recharge data and payment data are written into the physical bus card, that is, the physical bus card has a data storage function, and the generated flow data can be recorded in real time; for the virtual electronic card, the recharge data and the payment data are stored in the terminal. In the device, the generated flow data can be recorded in real time.
  • Step 501 The terminal device creates a virtual electronic card associated with the terminal based on the physical bus card.
  • Step 503 The specified carrier uses the physical bus card to obtain the first flow data corresponding to the physical bus card, and sends the first flow data to the server.
  • Step 505 The terminal device uses the virtual electronic card to obtain second flow data corresponding to the virtual electronic card.
  • step 503 and the step 505 are not strictly performed, and may be implemented in a synchronous manner, or may be implemented in the manner described in the embodiment of the present specification.
  • Step 305 may be performed first, and then step 303 is performed, which is not specifically limited herein.
  • Step 507 The terminal device acquires the first flow data from the server.
  • Step 509 The terminal device modifies the balance data in the virtual electronic card based on the first flow data and the second flow data.
  • Step 511 The terminal device establishes a data channel between the physical bus card and the virtual electronic card by using a short-range communication manner.
  • Step 513 The terminal device synchronizes the modified balance data in the virtual electronic card to the physical bus card by using the data channel.
  • FIG. 6(a) is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • the method can be as follows.
  • the execution subject of the embodiment of the present specification is a terminal device.
  • Step 602 The first terminal device establishes a data channel with the designated carrier by using a short-range communication manner.
  • the method before the first terminal device establishes the data channel, the method further includes:
  • the first terminal device sends prompt information, where the prompt information is used to prompt the user to be in the first account and the second account. Data synchronization is performed.
  • Step 604 The first terminal device acquires, by using the data channel, an account identifier of the first account included in the specified carrier and first flow data corresponding to the first account.
  • Step 606 The first terminal device determines second flow data corresponding to the second account associated with 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 first account;
  • Step 608 The first terminal device performs data synchronization between the first account and the second account according to the first flow data and the second flow data.
  • the synchronization data for synchronization is calculated according to the first flow data and the second flow data;
  • the synchronization data is synchronized to the first account and the second account, respectively.
  • the amount corresponding to the negative number is deducted from an application account for payment associated with the second account.
  • the method further includes:
  • the pipeline data includes at least one or more of consumption data and recharge data.
  • FIG. 6(b) is a schematic flowchart diagram of a data processing method according to an embodiment of the present disclosure.
  • the method can be as follows.
  • the embodiment of the present specification is described by taking a public transportation scenario as an example.
  • the first account corresponds to the account in the physical bus card
  • the second account corresponds to the account in the virtual electronic card
  • the first account and the second account establish an association relationship.
  • the recharge data and payment data are written into the physical bus card, that is, the physical bus card has a data storage function, and the generated flow data can be recorded in real time; for the virtual electronic card, the recharge data and the payment data are stored in the terminal. In the device, the generated flow data can be recorded in real time.
  • Step 601 The terminal device creates a virtual electronic card associated with the terminal based on the physical bus card.
  • Step 603 The specified carrier uses the physical bus card to obtain the first flow data corresponding to the physical bus card and stores the data; the terminal device uses the virtual electronic card to obtain the second flow data corresponding to the virtual electronic card and stores the data.
  • Step 605 The terminal device establishes a data channel between the physical bus card and the virtual electronic card by using a short-range communication manner.
  • 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 performs data synchronization between the physical bus card and the virtual electronic card according to the first flow data and the second flow data.
  • Figure 5 is different from the embodiment shown in Figure 6(b).
  • the difference is that when the flow data of the physical bus card is generated, it is not only stored in the physical bus card, but also sent to the server corresponding to the physical bus card, in the virtual electronic card.
  • the running water data is generated, it is not only stored in the terminal device but also sent to the server.
  • the terminal device where the virtual electronic card is located can obtain the first flow data of the physical bus card from the server, and the terminal device can modify the data in the virtual electronic card based on the stored second flow data and the acquired first flow data. To ensure that the modified data is consistent with the data of the user's primary account in the server.
  • FIG. 7 is a schematic flowchart of a data synchronization method according to an embodiment of the present disclosure.
  • the method can be as follows.
  • the executor of the embodiment of the present disclosure may be a terminal device, or may be an application client that has the technical solution provided by the embodiments of the present disclosure, and is not specifically limited herein.
  • Step 701 Determine whether the set synchronization condition is met. If yes, execute step 703; otherwise, wait for the set time to continue to perform step 701.
  • the set synchronization condition may include, but is not limited to, the following conditions:
  • a data synchronization request is received. If the data synchronization request is received, further determining whether the bearer carrying the first account is detected, if the bearer carrying the first account is detected, indicating that the set synchronization condition is met; if the bearer carrying the first account has not been detected, Sending prompt information, the prompt information is used to remind the user to provide the bearer carrying the first account, and establish a data channel; if the data synchronization request has not been received, it indicates that the set synchronization condition is not satisfied.
  • the set synchronization period has arrived. If the set synchronization period arrives, it is further determined whether the bearer carrying the first account is detected. If the bearer carrying the first account is detected, it indicates that the set synchronization condition is met; if the bearer carrying the first account has not been detected, Sending a prompt message, the prompt information is used to remind the user to provide the bearer carrying the first account, and establish a data channel; if the set synchronization period has not arrived, it indicates that the set synchronization condition is not satisfied.
  • the set synchronization conditions are not limited to those listed in the embodiments of the present specification, and may be determined according to actual needs, and are not specifically limited herein.
  • the bearer carrying the first account when detecting the bearer carrying the first account, it may further determine whether there is a second account associated with the account identifier of the first account, if not, first, based on The account identifier of the first account creates a second account associated therewith, and secondly, triggers the execution of the data synchronization operation; if so, performs the following operations in accordance with the scheme described in the embodiments of the present specification.
  • the bearer carrying the first account described in the embodiment of the present disclosure may be a card (for example, an IC card) supporting a short-range communication method, where the short-range communication method includes but is not limited to Bluetooth, infrared, NFC, RFID and the like are not specifically limited herein.
  • Step 703 Acquire an account identifier of the first account and first flow data corresponding to the first account.
  • the manner of obtaining the account identifier of the first account and the first pipeline data corresponding to the first account includes but is not limited to:
  • the account identifier of the first account and the first pipeline data corresponding to the first account are obtained from the carrier.
  • the terminal device can establish a data channel with the card by using the NFC method, and the data channel can be used to obtain the account identifier of the first account from the card (for example, a card). Card number) The first stream data corresponding to the first account.
  • the card can record the generated flow data when performing data interaction with other devices, such as consumption data, recharge data, and the like, and record the time when the flow data occurs.
  • the carrier carrying the first account includes a two-dimensional code picture
  • the two-dimensional code picture includes the account identifier of the first account
  • the account identifier of the first account can be obtained from the carrier by scanning, and further The running water data corresponding to the account identifier of the first account is found by the account identifier of the first account.
  • a user interface is provided in 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, and the account identifier of the first account herein can be understood as the card number of the card carrying the first account. Further, the account data corresponding to the account identifier of the first account may be acquired through the account identifier of the first account.
  • the method before acquiring the account identifier of the first account and the first flow data corresponding to the first account, the method further includes:
  • the prompt information is sent, and the prompt information is used to prompt the user to perform data synchronization between the first account and the second account.
  • the user may be prompted to send the prompt information.
  • Data synchronization between the first account and the second account is described.
  • the first flow data generated by the first account in one synchronization period is acquired.
  • the synchronization period herein can be understood as the time during which two consecutive synchronization operations occur.
  • the synchronization period here may be a fixed period or an unfixed period, which is not specifically limited herein.
  • the time T of the last synchronization operation or the last data synchronization completion is determined, then the determined time T is the starting point, and the time for initiating the synchronization operation is the end point, and it is determined here.
  • Step 705 Determine second flow data corresponding to the second account associated with 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 first account;
  • the account identifier of the first account is obtained.
  • the manner of obtaining the account identifier of the first account includes but is not limited to:
  • the account identifier of the first account input by the user is received through the user interface.
  • an account identifier of the second account is created according to 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 is not specifically limited herein.
  • At least one second account may be created for the first account, and data synchronization between the virtual account and the entity account may be performed when the data synchronization is performed, that is, the first description in the embodiment of the present specification.
  • the account and the second account represent the entity account and the virtual account respectively, and the physical account and the virtual account have an association relationship, and how many virtual accounts are not limited here.
  • the method further includes:
  • a virtual account ie, a second account
  • signing a withholding agreement with the user that is, establishing an association relationship between the account identifier of the second account and an application account for payment, and once the second account is found to be malicious If the overdraft or the malicious overdraft is found after data synchronization between the first account and the second account, the fee for the malicious overdraft can be deducted from the application account for payment associated with the account identifier of the second account.
  • first and “second” in the “first account” and the “second account” described in the embodiments of the present specification have no special meaning and are only used to distinguish accounts.
  • the bearer carrying the first account is an entity, such as an IC card, but the bearer carrying the second account is virtual, such as an electronic card.
  • Step 707 Perform data synchronization between the first account and the second account according to the first flow data and/or the second flow data.
  • the synchronization data for synchronization is calculated according to the first flow data and/or the second flow data;
  • the synchronization data is synchronized to the first account and the second account, respectively.
  • the balance data is synchronized to the second account according to the balance data corresponding to the first account.
  • the synchronization data is a negative number
  • the method further comprises:
  • the flowing water data described in the embodiments of the present specification includes at least one or more of payment data and refill data.
  • the technical solution provided by the embodiment of the present disclosure if the set synchronization condition is met, acquiring an account identifier of the first account and the first flow data corresponding to the first account; and determining the association with the first account The second flow data corresponding to the second account; and data synchronization between the first account and the second account according to the first flow data and/or the second flow data.
  • the first account is an account carried in the carrier and the second account is a virtual electronic account associated with the first account
  • the user can either use the first account to complete the transaction or use the second account. Seal the deal.
  • the technical solution provided by the embodiments of the present specification can ensure the consistency of data between the two accounts, thereby improving the payment experience of the user.
  • FIG. 8 is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • the data processing method is as follows.
  • the execution entity may be a client, and the client may be an application APP running in the smart terminal.
  • the smart terminal includes but is not limited to a mobile smart terminal, such as a smart phone or a tablet computer, and includes other intelligent terminals such as a computer and a notebook.
  • Step 801 Acquire a balance in the first account and the first account recorded in the carrier.
  • the first account may be provided by the main body of the distribution carrier, and is written into the carrier.
  • the form of the first account may include numbers, letters, and combinations thereof, and is not specifically limited herein.
  • the form of the carrier may include but is limited to a physical card, a button card, etc., and is not specifically limited herein.
  • the numbers in the carrier can be read to form a balance in the first account.
  • the carrier includes a Near Field Communication (NFC) module, and the NFC-enabled terminal device can write a number to the NFC module when the transaction occurs, and can read the number in the NFC module.
  • NFC Near Field Communication
  • Embodiments of the present specification may provide, but are not limited to, the following implementations:
  • the carrier when the user generates the payment data through the first account in the carrier or the second account in the client, the carrier may be close to the device where the client is located, and the client transmits the radio frequency signal to the carrier through the NFC module.
  • the NFC module in the carrier In order to transmit a short-range radio frequency signal to the carrier, the NFC module in the carrier generates a response signal in response, and the response signal carries the balance in the first account and the first account.
  • the client receives the response signal through the NFC module, and uses the parsing module to parse the balance in the first account and the first account.
  • the carrier includes a response module that can receive and respond to other frequency RF signals
  • the device at which the client is operating transmits other frequency RF signals that can be responded to. Therefore, the radio frequency signal transmitted by the client includes, but is not limited to, a short-range radio frequency signal, which is not limited herein, on the premise that the radio frequency signal transmitted by the device of the client is responsive to the carrier.
  • the receiving device that generates the payment data with the carrier writes the latest balance to the first account
  • the balance in the first account may also be stored in the server, and the client The latest account of the first account can be searched by the first account entered by the user in the server.
  • the client may scan the surface of the carrier to obtain the first account.
  • the existence form of the first account may include, but is not limited to: being highlighted so that the client obtains the first account by means of graphic recognition; or the first account is recorded in an identification code such as a two-dimensional code or a barcode, Enables the client to scan and parse the identification code to obtain the first account.
  • Step 803 Create a second account associated with the first account on the client according to the first account, and write the balance in the first account into the second account.
  • the second account may be a virtual account associated with the entity account.
  • the virtual account can be stored in the form of a user graphical interface on the client, and the balance in the virtual account and the virtual account can be displayed on the user graphical interface.
  • the user graphical interface provides interface objects, and through the operation interface objects, the payment service can be processed.
  • the interface object includes a two-dimensional code generation object, and the QR code generation object is clicked, and the payment two-dimensional code can be generated, and the two-dimensional code is paid for the payment service.
  • the client may send the balance in the second account and the first account to the server.
  • the client can send the payment data to the server for storage, which can avoid increasing the storage load of the client, and during the subsequent balance synchronization between the first account and the second account. , it is convenient to obtain the payment data and balance generated by the second account from the server.
  • the second account associated with the first account is created on the client according to the first account, which may include, but is not limited to:
  • a second account identical to the first account is created at the client, and the second account identical to the first account is determined as the second account associated with the first account.
  • the identification information of the first account and the second account are the same, for example, having the same letters, numbers, and combinations thereof.
  • the second account and the first account may also be different, but an association relationship is formed according to the association rule.
  • the user can create a second account associated with the first account at any time, so that the first account in the carrier can be used to generate payment data, or the second in the client.
  • the account has a collection and payment data, which can be selected to a high degree. In particular, even when one of the carrier or the client is not carried or can not be used while consuming, the carrier or the other of the clients can be used for consumer payment, thereby improving the user's payment experience.
  • FIG. 9 is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • the method is as follows, and is intended to implement balance synchronization between a first account and a second account associated with the first account.
  • the execution body of the processing method of the account may be a client, and the client may be an application APP running in the smart terminal, and the smart terminal includes but is not limited to a mobile intelligent terminal, such as a smart phone, a tablet computer, etc., and also includes a computer and a notebook. Other smart terminals.
  • Step 901 Acquire a balance in the first account and the first account recorded in the carrier.
  • step 801 For the manner of obtaining the balance in the first account and the first account in the carrier, refer to the content of step 801 above, and details are not described herein again.
  • the processing method in order to enable the user to synchronize the payment data generated by the second account to the first account after the receipt of the payment data through the second account, the first account and the first account recorded in the carrier are acquired. Before the balance in an account, the processing method also includes:
  • an alert signal is transmitted, the alert signal being used to prompt the user to provide the first account associated with the second account. This can bring convenience to the user and reduce the memory burden of the user.
  • the user After receiving the reminder signal, the user can provide the balance in the first account and the first account to the client by using the three acquisition methods described in step 801 above.
  • the form of the alert signal may include, but is not limited to, a voice, a sound, a vibration, a graphic, a text, and the like, and is not specifically limited herein.
  • the alert signal is transmitted, and the at least one or more of the following may be included:
  • a reminder signal is transmitted every time a receipt and payment data occurs
  • Step 903 Determine at least one payment data and a balance in the second account that occur in the second account associated with the first account, and the payment data includes one or two of each of the consumption amount and the refill amount.
  • determining at least one of the receipt and payment data and the balance in the second account that are generated by the second account associated with the first account includes:
  • the method for determining the second account associated with the first account may include:
  • the second account running in the second account of the client is determined to be the second account associated with the first account.
  • the method for determining the second account associated with the first account may further include:
  • the second account acquired from the server that is 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:
  • 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.
  • the client storing the second account and the background server may establish a connection relationship at any time. Therefore, determining the at least one payment data and the balance in the second account that occur in the second account may include:
  • the respective payment data generated by the second account is stored in the server, which can save the storage burden of the local client.
  • determining at least one payment data that occurs in the second account includes the following two situations:
  • the update cycle is a time interval in which the balances in the first account and the second account are updated to the same update balance twice.
  • the payment data acquisition request sent to the server is used to request the server to transmit each payment data occurring in the adjacent update period, and the latest balance in the second account. Based on the receipt and payment data acquisition request, the server transmits the latest payment data to the client in the current adjacent update period.
  • Step 905 Update the balance in the first account and the balance in the second account to the same update balance based on the assumption that the payment data occurs in the first account.
  • step 903 if the determined payment data generated by the second account is at least one of the receipt and payment data of the second account occurring in the adjacent update period, based on the assumption that the receipt and payment data occurs in the first account Condition, updating the balance in the first account and the balance in the second account to the same updated balance, including:
  • the balance in the first account and the balance in the second account are updated to the same updated balance based on the assumption that the first account generates the respective payment data in the adjacent update period.
  • the payment data occurring in the second account may be equivalent to occurring in the first account, so the first account may be set to occur in the adjacent update cycle. Pay the assumptions of the data to determine the same update balance.
  • the receipt and payment data generated by the second account includes: a recharge amount of 10 yuan; a consumption amount of 14 yuan, a current balance of the second account of 16 yuan, and the first account
  • the current balance is $17.
  • the balance in the first account and the balance in the second account are updated to the same updated balance based on the assumption that the receipt data occurs in the first account, including:
  • the balance in the first account and the balance in the second account are updated to the updated balance.
  • the updated balance of the balance in the first account after the receipt of the payment data is calculated, including:
  • the recharge amount is added to the balance in the first account
  • the amount of each consumption is subtracted from the balance in the first account
  • the obtained processing result is taken as the updated balance.
  • the method for determining the at least one payment data that occurs in the second account is particularly applicable to the case where the carrier that records the first account cannot connect to the server in real time, or the client that stores the second account is used frequently, and the first account can be solved.
  • the connection problem that exists in the carrier is particularly applicable to the case where the carrier that records the first account cannot connect to the server in real time, or the client that stores the second account is used frequently, and the first account can be solved.
  • step 903 If it is determined in step 903 that the payment data generated by the second account is the real-time payment data, the same update of the first account and the second account may be determined by referring to the example in Table 1, and details are not described herein again.
  • the client may directly update the balance in the second account to the updated balance.
  • the manner of updating the balance in the first account to update the balance includes:
  • the balance of the first account recorded in the NFC module can be updated to the updated balance.
  • the balance of the first account in the NFC module in the carrier may be modified to update the balance.
  • the client requests the server to send the updated balance to the carrier, and then the device that generates the payment data with the carrier writes the updated balance to the carrier.
  • the receiving and paying equipment such as the bus POS machine and the cash register POS machine
  • the receiving and paying equipment such as the bus POS machine and the cash register POS machine can modify the balance of the first account recorded in the carrier as the updated balance.
  • the first way of updating the balance in the first account is to update the balance.
  • the operation can be performed anytime and anywhere, and the operation convenience is good.
  • the balances in the first account and the second account may be synchronized to realize the unification of the first account and the second account.
  • This may be particularly applicable to, but not limited to, the case where the carrier in which the first account is recorded cannot be connected to the server, or the carrier cannot be connected to the server in real time.
  • FIG. 10 is a schematic flowchart diagram of a data synchronization method according to an embodiment of the present disclosure.
  • This processing method is as follows.
  • the execution body of the processing method is a server.
  • the method is particularly applicable to, but not limited to, the carrier that records the first account can facilitate or implement the connection server.
  • Step 1001 Receive payment data generated by at least one of the first account and the second account associated with the first account.
  • the payment data generated in the first account is determined when the client obtains the first account from the carrier that records the first account, and the payment data includes the recharge amount and the consumption amount.
  • the server may receive the receipt of the first account by the receiving device that generates the payment data with the carrier. Pay the data.
  • the server can receive the payment data generated by the second account directly from the client storing 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 receipt of the payment data.
  • the update balance in the first account is written into the carrier by the receiving device.
  • the processing method may further include:
  • the update period being a time interval in which the balances in the first account and the second account are updated to the same update balance twice;
  • the balance in the first account and the balance in the second account are both updated to the same updated balance after the receipt of the payment data, including:
  • Both the balance in the first account and the balance in the second account are updated to the same updated balance after the receipt and payment data occurring in the adjacent update period.
  • one of the first account and the second account is determined as the reference account, and it is assumed that the payment data incurred by the reference account also occurs in another account. To determine an update account.
  • each update can process multiple payment data at the same time, improving processing efficiency.
  • the balance in the first account and the balance in the second account are both updated to the same updated balance after the receipt of the payment data, and may further include:
  • the balance in the first account and the balance in the second account are updated to the same updated balance after the receipt of the receipt data.
  • the processing method may further include:
  • the reminder information is sent to the client running the second account, and the reminder information is used to notify the user that the balance is insufficient.
  • the server can notify the receiving device that the account balance is insufficient and cannot complete the deduction.
  • the embodiment of the present specification provides another technical means for realizing the synchronization update of the balance in the first account and the second account to the updated balance, keeping the balances in the first account and the second account consistent.
  • FIG. 11 is a schematic structural diagram of an account creation device according to an embodiment of the present disclosure.
  • the account creation device includes: an acquisition unit 1101, a creation unit 1102, and a storage unit 1103, where:
  • the obtaining unit 1101 acquires an account identifier of the first account from the specified carrier by using a setting manner
  • the creating unit 1102 is configured to create an account identifier of the second account according to 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.
  • the obtaining unit 1101 obtains an account identifier of the first account from the specified carrier by setting, including:
  • a data channel is established with the designated carrier by the short-range communication technology, and the account identifier of the first account is obtained from the designated carrier through the data channel.
  • the obtaining unit 1101 obtains an account identifier of the first account from the specified carrier by setting, including:
  • the account identifier of the first account is obtained from the specified carrier by scanning.
  • the storage unit 1103 after obtaining the account identifier of the second account, establishes and stores an association between the account identifier of the second account and an application account for payment. relationship.
  • the designated carrier includes a card device supporting a short-range communication technology, a second terminal device including an account identifier of the first account, and an account identifier including the first account. At least one or more of the application clients.
  • the second account includes one of a virtual account and an electronic account.
  • account creation device described in the embodiment of the present disclosure may be implemented by software or by hardware, and is not specifically limited herein.
  • an embodiment of the present specification further provides an account creation device, including: 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. :
  • an embodiment of the present specification further provides a computer readable storage medium including a program for use in conjunction with an electronic device, the program being executable by the processor to perform the following steps:
  • FIG. 12 is a schematic structural diagram of an account refilling device according to an embodiment of the present disclosure.
  • the account refilling device includes: an establishing unit 1201 and a refilling unit 1202, wherein:
  • the establishing unit 1201 establishes a data channel by using a short-range communication technology and a designated carrier that includes an account identifier of the first account;
  • the refilling unit 1202 writes the refill data of the second account into the designated carrier through the data channel to implement recharging for the first account.
  • the account refilling device further includes: a generating unit 1203, wherein:
  • the generating unit 1203 performs a transfer operation to the second account by using an application account for payment, and generates recharge data of the second account.
  • the designated carrier includes a card device supporting a short-range communication technology, a second terminal device including an account identifier of the first account, and an account identifier including the first account. At least one or more of the application clients.
  • account recharging device described in the embodiments of the present disclosure may be implemented by using a software, or may be implemented by using a hardware, and is not specifically limited herein.
  • an embodiment of the present specification provides an account refilling device, including: at least one memory and at least one processor, wherein the memory stores a program, and is configured by the processor to perform the following steps:
  • the refill data of the second account is written into the designated carrier through the data channel to implement recharging of the first account.
  • an embodiment of the present specification further provides a computer readable storage medium including a program for use in conjunction with an electronic device, the program being executable by the processor to perform the following steps:
  • the refill data of the second account is written into the designated carrier through the data channel to implement recharging for the first account.
  • FIG. 13 is a schematic structural diagram of an account refilling device according to an embodiment of the present disclosure.
  • the account refilling device includes: a receiving unit 1301 and a processing unit 1302, wherein:
  • the receiving unit 1301 receives the refill data sent by the first terminal device when the data channel is established with the first terminal device by using the short-range communication technology
  • the processing unit 1302 processes the balance data of the first account according to the recharge data.
  • the processing unit 1302 processes the balance data of the first account according to the recharge data, including:
  • the balance data of the first account is not zero
  • the balance data of the first account is modified using the refill data.
  • account recharging device described in the embodiments of the present disclosure may be implemented by using a software, or may be implemented by using a hardware, and is not specifically limited herein.
  • an embodiment of the present specification provides an account refilling device, including: at least one memory and at least one processor, wherein the memory stores a program, and is configured by the processor to perform the following steps:
  • the balance data of the first account is processed according to the recharge data.
  • an embodiment of the present specification further provides a computer readable storage medium including a program for use in conjunction with an electronic device, the program being executable by the processor to perform the following steps:
  • the balance data of the first account is processed according to the recharge data.
  • FIG. 14 is a schematic structural diagram of a data synchronization device according to an embodiment of the present disclosure.
  • the data synchronization device includes: an obtaining unit 1401, a receiving unit 1402, and a synchronization unit 1403, where:
  • the obtaining unit 1401 acquires an account identifier of the first account and the first pipeline data corresponding to the first account from the specified carrier by using a short-range communication manner;
  • the receiving unit 1402 receives an account identifier of the second account sent by the first terminal device and second flow data corresponding to the second account;
  • the synchronization unit 1403 determines synchronization data of one synchronization period according to the first flow data and the second flow data, and sends the synchronization data to the first terminal device, so that the second account corresponds to The data is consistent with the data corresponding to the primary account.
  • the data processing device described in the embodiment of the present invention may be applied to a server, and the primary account included in the server is associated with the first account included in the specified carrier and the second account included in the first terminal device. .
  • the acquiring unit 1401 obtains the account identifier of the first account and the first pipeline data corresponding to the first account from the specified carrier by using a short-range communication manner, including:
  • the account identifier of the first account and the first pipeline data corresponding to the first account are obtained from the designated carrier through the data channel.
  • the data synchronization device further includes: a sending unit 1404, where:
  • the sending unit 1404 if the synchronization data is a negative number, sending a debit request to the first terminal device, where the debit request is for requesting an application account for payment associated with the second account The amount corresponding to the negative number is subtracted.
  • data synchronization device described in the embodiments of the present disclosure may be implemented by using a software, or may be implemented by using a hardware, and is not specifically limited herein.
  • an embodiment of the present specification provides a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured by the processor to perform the following steps:
  • the primary account included in the server establishes an association relationship with the first account included in the specified carrier and the second account included in the first terminal device.
  • an embodiment of the present specification further provides a computer readable storage medium including a program for use in conjunction with an electronic device, the program being executable by the processor to perform the following steps:
  • the primary account included in the server establishes an association relationship with the first account included in the specified carrier and the second account included in the first terminal device.
  • FIG. 15 is a schematic structural diagram of a data synchronization device according to an embodiment of the present disclosure.
  • the data synchronization device includes: an establishing unit 1501 and a synchronization unit 1502, wherein:
  • the establishing unit 1501 establishes a data channel with the designated carrier by using a short-range communication method
  • the synchronization unit 1502 synchronizes the balance data corresponding to the second account to the designated carrier by using the data channel, so that the data corresponding to the first account included in the specified carrier is consistent with the data corresponding to the second account.
  • 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, and the synchronization data is obtained by the server according to the synchronization manner described above;
  • the processing unit 1504 by using the synchronization data, to modify data corresponding to the second account, so that the data corresponding to the second account is consistent with the data corresponding to the primary account included in the server;
  • the primary account included in the server establishes an association relationship with the first account included in the specified carrier and the second account included in the first terminal device.
  • data synchronization device described in the embodiments of the present disclosure may be implemented by using a software, or may be implemented by using a hardware, and is not specifically limited herein.
  • an embodiment of the present specification provides a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured by the processor to perform the following steps:
  • the balance data corresponding to the second account is synchronized to the designated carrier by the data channel, so that the data corresponding to the first account included in the specified carrier is consistent with the data corresponding to the second account.
  • an embodiment of the present specification further provides a computer readable storage medium including a program for use in conjunction with an electronic device, the program being executable by the processor to perform the following steps:
  • the balance data corresponding to the second account is synchronized to the designated carrier by the data channel, so that the data corresponding to the first account included in the specified carrier is consistent with the data corresponding to the second account.
  • FIG. 16 is a schematic structural diagram of a data synchronization device according to an embodiment of the present disclosure.
  • the data synchronization device includes: an establishing unit 1601, an obtaining unit 1602, a determining unit 1603, and a synchronization unit 1604, where:
  • the establishing unit 1601 establishes a data channel with the designated carrier by using a short-range communication method
  • the obtaining unit 1602 is configured to acquire, by using the data channel, an account identifier of the first account included in the specified carrier and first flow data corresponding to the first account;
  • the synchronization unit 1604 performs data synchronization between the first account and the second account according to the first flow data and the second flow data.
  • the data synchronization device further includes: a sending unit 1605, where:
  • the sending unit 1605 after detecting that the data corresponding to the second account associated with the first account changes, before the data channel is established, sending prompt information, where the prompt information is used to prompt the user in the first account Data synchronization is performed between the second accounts.
  • the determining unit 1603 determines second flow data corresponding to the second account associated with the first account, including:
  • the synchronization unit 1604 performs data synchronization between the first account and the second account according to the first flow data and the second flow data, including:
  • the synchronization data is synchronized to the first account and the second account, respectively.
  • the synchronization unit 1604 synchronizes the synchronization data to the first account and the second account, including:
  • the amount corresponding to the negative number is deducted from an application account for payment associated with the second account.
  • the data synchronization device further includes: a deleting unit 1606, wherein:
  • the deleting unit 1606, the synchronization time, the account identifier of the first account, the first running water data is sent to the server, and the first running water data recorded in the carrier carrying the first account is deleted; and /or,
  • the pipeline data includes at least one or more of consumption data and recharge data.
  • data synchronization device described in the embodiments of the present disclosure may be implemented by using a software, or may be implemented by using a hardware, and is not specifically limited herein.
  • an embodiment of the present specification provides a data synchronization device, including: at least one memory and at least one processor, wherein the memory stores a program and is configured by the processor to perform the following steps:
  • an embodiment of the present specification further provides a computer readable storage medium including a program for use in conjunction with an electronic device, the program being executable by the processor to perform the following steps:
  • a second account is created on the terminal device for the first account included in the designated carrier, and the second account in the terminal device is used to recharge the first account by using the short-range communication method. And ensuring data consistency between the first account and the second account. That is, 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 either use the first account to complete the transaction or use the second account. The account completes the transaction.
  • the technical solution provided by the embodiments of the present specification can ensure the consistency of data between the two accounts, thereby improving the payment experience of the user.
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor.
  • computer readable program code eg, software or firmware
  • examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.
  • the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding.
  • Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component.
  • a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer.
  • the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, 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.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • the application can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
  • program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
  • the present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种账户创建、账户充值、数据同步方法及设备,所述方法包括:在终端设备上为指定载体中包含的第一账户创建第二账户,以及利用该终端设备中的第二账户,通过近距离通信方式实现为第一账户充值以及保证第一账户与第二账户之间的数据一致性。

Description

一种账户创建、账户充值、数据同步方法及设备 技术领域
本说明书涉及互联网信息处理技术以及计算机技术领域,尤其涉及一种账户创建、账户充值、数据同步方法及设备。
背景技术
现金支付作为一种传统支付方式,是每个生活在现代社会的人们所非常熟悉的支付方式。但是,在有些领域(例如:公共交通领域、超市购物领域),现金支付给人们带来一些不便(例如:需要准备足数的零钱等等)。
为了解决这些不便,出现了圈存支付。所谓圈存支付可以理解为用户将银行账户中的钱或者现金直接圈存至指定的IC卡(Integrated circuit Card,集成电路卡)中,之后利用指定的IC卡进行消费。这种方式又可以称之为电子钱包。但是,目前实现圈存的方式一般需要在特定设备中执行相关圈存操作。
基于这种支付方法,亟需一种更便捷的处理方法,以提升圈存支付的便捷性。
发明内容
有鉴于此,本说明书实施例提供了一种账户创建、账户充值、数据同步方法及设备,以提升圈存支付的便捷性。
本说明书实施例提供下述技术方案:
本说明书实施例提供一种账户创建方法,包括:
第一终端设备通过设定的方式从指定载体中获取第一账户的账户标识;
所述第一终端设备根据所述第一账户的账户标识,创建第二账户的账户标识;
所述第一终端设备建立并存储所述第一账户的账户标识与所述第二账户 的账户标识之间的映射关系。
本说明书实施例提供一种账户充值方法,包括:
第一终端设备通过近距离通信技术与包含第一账户的账户标识的指定载体建立数据通道;
所述第一终端设备通过所述数据通道将第二账户的充值数据写入所述指定载体中,以实现为所述第一账户进行充值。
本说明书实施例提供一种账户充值方法,包括:
指定载体在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一终端设备发送的充值数据;
根据所述充值数据,对第一账户的余额数据进行处理。
本说明书实施例提供一种数据同步方法,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系,包括:
所述服务器通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据;
所述服务器接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据;
所述服务器根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致。
本说明书实施例提供一种数据同步方法,包括:
第一终端设备通过近距离通信方式与指定载体建立数据通道;
所述第一终端设备通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
本说明书实施例提供一种数据同步方法,包括:
第一终端设备通过近距离通信方式与指定载体建立数据通道;
所述第一终端设备通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据;
所述第一终端设备确定与所述第一账户关联的第二账户对应的第二流水数据;
所述第一终端设备根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
本说明书实施例提供一种账户创建设备,包括:
获取单元,通过设定的方式从指定载体中获取第一账户的账户标识;
创建单元,根据所述第一账户的账户标识,创建第二账户的账户标识;
存储单元,建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的映射关系。
本说明书实施例提供一种账户充值设备,包括:
建立单元,通过近距离通信技术与包含第一账户的账户标识的指定载体建立数据通道;
充值单元,通过所述数据通道将第二账户的充值数据写入所述指定载体中,以实现为所述第一账户进行充值。
本说明书实施例提供一种账户充值设备,包括:
接收单元,在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一终端设备发送的充值数据;
处理单元,根据所述充值数据,对第一账户的余额数据进行处理。
本说明书实施例提供一种数据同步设备,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系,包括:
获取单元,通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据;
接收单元,接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据;
同步单元,根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致。
本说明书实施例提供一种数据同步设备,包括:
建立单元,通过近距离通信方式与指定载体建立数据通道;
同步单元,通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
本说明书实施例提供一种数据同步设备,包括:
建立单元,通过近距离通信方式与指定载体建立数据通道;
获取单元,通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据;
确定单元,确定与所述第一账户关联的第二账户对应的第二流水数据;
同步单元,根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
本说明书实施例提供一种账户创建设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
通过设定的方式从指定载体中获取第一账户的账户标识;
根据所述第一账户的账户标识,创建第二账户的账户标识;
建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的映射关系。
本说明书实施例提供一种账户充值设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下 步骤:
通过近距离通信技术与包含第一账户的账户标识的指定载体建立数据通道;
通过所述数据通道将第二账户的充值数据写入所述指定载体中,以实现为所述第一账户进行充值。
本说明书实施例提供一种账户充值设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一终端设备发送的充值数据;
根据所述充值数据,对第一账户的余额数据进行处理。
本说明书实施例提供一种数据同步设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据;
接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据;
根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致;
其中,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系。
本说明书实施例提供一种数据同步设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
通过近距离通信方式与指定载体建立数据通道;
通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
本说明书实施例提供一种数据同步设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
通过近距离通信方式与指定载体建立数据通道;
通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据;
确定与所述第一账户关联的第二账户对应的第二流水数据;
根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
本说明书实施例采用的上述至少一个技术方案能够达到以下有益效果:
通过在终端设备上为指定载体中包含的第一账户创建第二账户,以及利用该终端设备中的第二账户,通过近距离通信方式实现为第一账户充值以及保证第一账户与第二账户之间的数据一致性。也就是说,假设第一账户是承载在指定载体中的账户,第二账户为与所述第一账户关联的虚拟的电子账户,那么用户既可以使用第一账户完成交易,也可以使用第二账户完成交易。同时,通过本说明书实施例提供的技术方案,能够保证这两个账户之间数据的一致性,进而提升用户的支付体验。
附图说明
此处所说明的附图用来提供对本说明书的进一步理解,构成本申请的一部分,本说明书的示意性实施例及其说明用于解释本申请,并不构成对本申请的不当限定。在附图中:
图1为本说明书实施例提供的一种账户创建方法的流程示意图;
图2为本说明书实施例提供的一种账户充值方法的流程示意图;
图3为本说明书实施例提供的一种账户充值方法的流程示意图;
图4(a)为本说明书实施例提出的一种数据同步方法的流程示意图;
图4(b)为本说明书实施例提出的一种数据同步方法的流程示意图;
图5为本说明书实施例提出的一种数据同步方法的流程示意图;
图6(a)为本说明书实施例提出的一种数据同步方法的流程示意图;
图6(b)为本说明书实施例提出的一种数据同步方法的流程示意图;
图7为本说明书实施例提出的一种数据同步方法的流程示意图;
图8为本说明书实施例提出的一种数据同步方法的流程示意图;
图9为本说明书实施例提出的一种数据同步方法的流程示意图;
图10为本说明书实施例提出的一种数据同步方法的流程示意图;
图11为本说明书实施例提供的一种账户创建设备的结构示意图;
图12为本说明书实施例提供的一种账户充值设备的结构示意图;
图13为本说明书实施例提供的一种账户充值设备的结构示意图;
图14为本说明书实施例提供的一种数据同步设备的结构示意图;
图15为本说明书实施例提供的一种数据同步设备的结构示意图;
图16为本说明书实施例提供的一种数据同步设备的结构示意图。
具体实施方式
在现有技术中,使用移动支付方案纵然可以带来支付上的便利,但对于用户来说,也存在一些不便之处。例如,若用户未携带移动终端或移动终端处于没电状态,用户将无法使用移动终端进行支付,那么也就意味着如果卡片支付和移动支付能够相辅相成,将给用户的生产生活带来便利。
然而,随着互联网技术的发展,出现了一种新的支付方式,即电子支付方式。所谓电子支付方式是指从事电子商务交易的当事人(包括:消费者、厂商和金融机构),通过信息网络,采用数字化方式以及安全的信息传输手段进行 的货币支付或资金流转。相对于现金支付、圈存支付,能给用户带来更大便利。
为了实现这一目的,本说明书实施例提供了一种账户创建、账户充值、数据同步方法及设备,通过在终端设备上为指定载体中包含的第一账户创建第二账户,以及利用该终端设备中的第二账户,通过近距离通信方式实现为第一账户充值以及保证第一账户与第二账户之间的数据一致性。也就是说,假设第一账户是承载在指定载体中的账户,第二账户为与所述第一账户关联的虚拟的电子账户,那么用户既可以使用第一账户完成交易,也可以使用第二账户完成交易。同时,通过本说明书实施例提供的技术方案,能够保证这两个账户之间数据的一致性,进而提升用户的支付体验。
需要说明的是,本说明书实施例记载的技术方案可以应用在公共交通场景中,也可以应用在涉及类似IC卡应用的其他应用场景中,这里不做具体限定。
IC卡(Integrated circuit Card,集成电路卡),又可称之为智能卡(Smart Card),这种卡片具备可读写、容量大、有加密功能、数据记录可靠,使用方便等特点。例如:公交卡。用户在乘坐公共交通工具的时候可以通过公交卡实现交通费的支付。当公交卡与公共交通工具的刷卡机之间进行数据交互时,读取公交卡中的数值,并实现交通费的扣除。而目前公交卡的充值一般都是通过圈存的方式完成的,即需要到指定的充值站点通过特殊设备进行充值。
为使本说明书实施例的目的、技术方案和优点更加清楚,下面将结合本说明书具体实施例及相应的附图对本说明书技术方案进行清楚、完整地描述。显然,所描述的实施例仅是本说明书一部分实施例,而不是全部的实施例。基于本说明书中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
以下结合说明书附图,详细说明本说明书各实施例提供的技术方案。
图1为本说明书实施提供的一种账户创建方法的流程示意图。所述方法可以如下所示。本说明书实施例的执行主体为终端设备。
步骤101:第一终端设备通过设定的方式从指定载体中获取第一账户的账 户标识。
在本说明书实施例中,第一终端设备通过设定的方式从指定载体中获取第一账户的账户标识,包括:
第一种方式:
第一终端设备通过近距离通信技术与指定载体建立数据通道,并通过所述数据通道从所述指定载体中获取第一账户的账户标识。
第二种方式:
第一终端设备通过扫描的方式从指定载体中获取第一账户的账户标识。
这里所记载的所述指定载体包含支持近距离通信技术的卡式装置、包含所述第一账户的账户标识的第二终端设备、包含所述第一账户的账户标识的应用客户端中的至少一种或者多种。
步骤103:所述第一终端设备根据所述第一账户的账户标识,创建第二账户的账户标识。
在本说明书实施例中,第一终端设备在得到第一账户的账户标识之后,可以基于第一账户的账户标识创建第二账户的账户标识,也可以单独创建第二账户的账户标识,这里不做具体限定。
这里记载的所述第二账户包含虚拟账户、电子账户中的一种。
步骤105:所述第一终端设备建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的映射关系。
在本说明书实施例中,所述方法还包括:
在得到所述第二账户的账户标识后,所述第一终端设备建立并存储所述第二账户的账户标识与用于支付的应用账户之间的关联关系。
图2为本说明书实施例提供的一种账户充值方法的流程示意图。所述方法可以如下所示。本说明书实施例的执行主体可以为智能终端设备,例如:移动终端设备。
步骤201:第一终端设备通过近距离通信技术与包含第一账户的账户标识 的指定载体建立数据通道。
在本说明书实施例中,在建立数据通道之前,所述方法还包括:
第一终端设备利用用于支付的应用账户向第二账户执行转账操作,生成第二账户的充值数据。
这里所记载的所述指定载体包含支持近距离通信技术的卡式装置、包含所述第一账户的账户标识的第二终端设备、包含所述第一账户的账户标识的应用客户端中的至少一种或者多种。
步骤203:所述第一终端设备通过所述数据通道将第二账户的充值数据写入所述指定载体中,以实现为所述第一账户进行充值。
图3为本说明书实施例提供的一种账户充值方法的流程示意图。所述方法可以如下所示。本说明书实施例的执行主体可以为指定载体,例如:IC卡、终端设备等等。
步骤301:指定载体在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一终端设备发送的充值数据。
步骤303:根据所述充值数据,对第一账户的余额数据进行处理。
在本说明书实施例中,在第一账户的余额数据为零的情况下,将所述充值数据写入所述第一账户中;
在第一账户的余额数据不为零的情况下,利用所述充值数据,修改所述第一账户的余额数据。
通过本说明书实施例中图2和图3中所记载的方案,利用移动终端设备(例如:智能手机等)能够实现对所使用的IC卡类型的卡式装置进行充值,这样有效避免了实际生活中因为充值设备的固定所带给人们的各种不方面(例如:较长的等待时间、需要到达充值设备所在的位置等等),能够有效提升充值效率,同时给用户带来极好的用户体验。
图4(a)为本说明书实施例提供的一种数据同步方法的流程示意图。所述方法可以如下所示。本说明书实施例的执行主体为服务器,该服务器中包含的 主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系。
假设这里的服务器为公共交通服务器,公共交通服务器可以根据用户的身份标识为用户建立主账户,那么用户在申请到公交卡的情况下,公共交通服务器可以建立主账户与该公交卡的卡标识(即第一账户的账户标识)之间的映射关系;此外,假设用户在终端设备上创建了与该公交卡的***关联的虚拟电子卡,那么还可以进一步建立主账户与该虚拟电子卡的卡标识(即第二账户的账户标识)之间的映射关系。
步骤401:所述服务器通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据。
在本说明书实施例中,所述服务器通过近距离通信方式与所述指定载体建立数据通道;
所述服务器在确定交易发生的情况下,通过所述数据通道从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据。
例如:用户在使用公交卡***时,通过商家所提供的POS机或者刷卡机可以将该公交卡的消费数据发送给服务器,这样,服务器能够及时获取公交卡中包含的第一账户的账户标识和所述第一账户对应的第一流水数据。
步骤403:所述服务器接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据。
步骤405:所述服务器根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致。
在本说明书实施例中,所述方法还包括:
若所述同步数据为负数,那么向所述第一终端设备发送扣款请求,所述扣款请求用于请求从与所述第二账户关联的用于支付的应用账户中扣除所述负数对应的金额。
图4(b)为本说明书实施例提供的一种数据同步方法的流程示意图。所述方法可以如下所示。本说明书实施例的执行主体为终端设备。
步骤402:第一终端设备通过近距离通信方式与指定载体建立数据通道。
步骤404:所述第一终端设备通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
在本说明书实施例中,在数据通道建立之前,所述方法还包括:
第一终端设备接收服务器发送的同步数据,所述同步数据是所述服务器根据图4(a)所记载的方式得到的;
所述第一终端设备利用所述同步数据修改所述第二账户对应的数据,以使所述第二账户对应的数据与服务器中包含的主账户对应的数据一致;
其中,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系。
图5为本说明书实施例提供的一种数据处理方法的流程示意图。所述方法可以如下所示。本说明书实施例以公共交通场景为例进行说明。这里的第一账户对应实体公交卡中的账户,第二账户对应虚拟电子卡中的账户,第一账户与第二账户之间建立关联关系。
对于实体公交卡,充值数据、付款数据被写入实体公交卡中,即实体公交卡具备数据存储功能,能够实时记录所产生的流水数据;对于虚拟电子卡,充值数据、付款数据被存储在终端设备中,能够实时记录所产生的流水数据。
步骤501:终端设备基于实体公交卡,创建与其关联的虚拟电子卡。
步骤503:指定载体使用实体公交卡,得到该实体公交卡对应的第一流水数据,并将第一流水数据发送给服务器。
步骤505:终端设备使用虚拟电子卡,得到该虚拟电子卡对应的第二流水数据。
这里步骤503和步骤505没有严格的执行顺序,可以同步实施,也可以按 照本说明书实施例中记载的方式实施,还可以先执行步骤305,再执行步骤303,这里不做具体限定。
步骤507:终端设备从服务器中获取该第一流水数据。
步骤509:终端设备基于该第一流水数据和第二流水数据,对该虚拟电子卡中的余额数据进行修改。
步骤511:终端设备通过近距离通信方式,建立该实体公交卡与该虚拟电子卡之间的数据通道。
步骤513:终端设备利用所述数据通道,将虚拟电子卡中修改后的余额数据同步给实体公交卡。
图6(a)为本说明书实施例提供的一种数据同步方法的流程示意图。所述方法可以如下所示。本说明书实施例的执行主体为终端设备。
步骤602:第一终端设备通过近距离通信方式与指定载体建立数据通道。
在本说明书实施例中,所述第一终端设备在建立数据通道之前,所述方法还包括:
若检测到与第一账户关联的第二账户对应的数据发生变化,则所述第一终端设备发送提示信息,所述提示信息用于提示用户在所述第一账户与所述第二账户之间进行数据同步。
步骤604:所述第一终端设备通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据。
步骤606:所述第一终端设备确定与所述第一账户关联的第二账户对应的第二流水数据。
在本说明书实施例中,根据所述第一账户的账户标识,确定与所述第一账户的账户标识建立关联关系的第二账户的账户标识;
根据所述第二账户的账户标识,查找与所述第二账户的账户标识建立对应关系的第二流水数据。
步骤608:所述第一终端设备根据所述第一流水数据和所述第二流水数据, 在所述第一账户和所述第二账户之间进行数据同步。
在本说明书实施例中,根据所述第一流水数据和所述第二流水数据,计算得到用于同步的同步数据;
分别将所述同步数据同步至所述第一账户和所述第二账户。
若所述同步数据为负数,那么将空分别写入所述第一账户和所述第二账户;
从与所述第二账户关联的用于支付的应用账户中扣除所述负数对应的金额。
在本说明书实施例中,所述方法还包括:
将同步时间、所述第一账户的账户标识、所述第一流水数据发送给服务器,并删除承载所述第一账户的载体中记录的所述第一流水数据;和/或,
将同步时间、所述第二账户的账户标识、所述第二流水数据发送给所述服务器,并删除所述第二流水数据。
在本说明书实施例中,所述流水数据包含消费数据、充值数据中的至少一种或者多种。
图6(b)为本说明书实施例提供的一种数据处理方法的流程示意图。所述方法可以如下所示。本说明书实施例以公共交通场景为例进行说明。这里的第一账户对应实体公交卡中的账户,第二账户对应虚拟电子卡中的账户,第一账户与第二账户之间建立关联关系。
对于实体公交卡,充值数据、付款数据被写入实体公交卡中,即实体公交卡具备数据存储功能,能够实时记录所产生的流水数据;对于虚拟电子卡,充值数据、付款数据被存储在终端设备中,能够实时记录所产生的流水数据。
步骤601:终端设备基于实体公交卡,创建与其关联的虚拟电子卡。
步骤603:指定载体使用实体公交卡,得到该实体公交卡对应的第一流水数据并存储;终端设备使用虚拟电子卡,得到该虚拟电子卡对应的第二流水数据并存储。
步骤605:终端设备通过近距离通信方式,建立该实体公交卡与该虚拟电子卡之间的数据通道。
步骤607:终端设备利用所述数据通道,获取该实体公交卡对应的第一流水数据。
步骤609:终端设备根据该第一流水数据和第二流水数据,在实体公交卡与虚拟电子卡之间进行数据同步。
图5与图6(b)所示的实施例不同,区别在于:在实体公交卡的流水数据产生时,不仅存储在实体公交卡中,还发送给实体公交卡对应的服务器,在虚拟电子卡的流水数据产生时,不仅存储在终端设备中,还发送给服务器。虚拟电子卡所在的终端设备能够从服务器中获取到实体公交卡的第一流水数据,终端设备能够基于存储的第二流水数据和获取到的第一流水数据,对虚拟电子卡中的数据进行修改,以保证修改后的数据与用户在服务器中主账户的数据一致。
基于同一个发明构思,图7为本说明书实施例提供的一种数据同步方法的流程示意图。所述方法可以如下所示。本说明书实施例的执行主体可以为终端设备,也可以为具备本说明书实施例提供的技术方案的应用客户端,这里不做具体限定。
步骤701:判断是否满足设定的同步条件,若满足,则执行步骤703;否则,等待设定时间继续执行步骤701。
在本说明书实施例中,设定的同步条件可以包含但不限于以下条件:
1、是否检测到承载第一账户的载体。若检测到承载第一账户的载体,则说明满足设定的同步条件;若尚未检测到承载第一账户的载体,则说明不满足设定的同步条件。
2、是否接收到数据同步请求。若接收到数据同步请求,进一步判断是否检测到承载第一账户的载体,若检测到承载第一账户的载体,则说明满足设定的同步条件;若尚未检测到承载第一账户的载体,则发送提示信息,该提示信 息用于提醒用户提供承载第一账户的载体,并建立数据通道;若尚未接收到数据同步请求,则说明不满足设定的同步条件。
3、设定的同步周期是否到达。若设定的同步周期到达,进一步判断是否检测到承载第一账户的载体,若检测到承载第一账户的载体,则说明满足设定的同步条件;若尚未检测到承载第一账户的载体,则发送提示信息,该提示信息用于提醒用户提供承载第一账户的载体,并建立数据通道;若设定的同步周期尚未到达,则说明不满足设定的同步条件。
对于本说明书实施例中列举的同步条件可以选择其一使用,也可以选择几个混合使用。同时,设定的同步条件也不限于本说明书实施例中所列举的这些,还可以根据实际需要确定,这里不做具体限定。
较优地,在本说明书实施例中,当检测到承载第一账户的载体时,还可以进一步判断是否存在与所述第一账户的账户标识关联的第二账户,若不存在,首先,基于第一账户的账户标识创建与其关联的第二账户,其次,触发执行数据同步操作;若存在,则按照本说明书实施例中记载的方案执行以下操作。
需要说明的是,本说明书实施例中记载的承载第一账户的载体可以为支持近距离通信方式的卡片(例如:IC卡),这里的近距离通信方式包含但不限于蓝牙、红外、NFC、RFID等等,这里不做具体限定。
步骤703:获取第一账户的账户标识和所述第一账户对应的第一流水数据。
在本说明书实施例中,获取第一账户的账户标识和所述第一账户对应的第一流水数据的方式包括但不限于:
第一种方式:
通过近距离通信方式与承载第一账户的载体之间建立数据通道;
利用所述数据通道,从所述载体中获取所述第一账户的账户标识和所述第一账户对应的第一流水数据。
假设承载第一账户的载体为支持NFC通信方式的卡片,那么终端设备通过NFC方式可以与该卡片建立数据通道,利用该数据通道,可以从该卡片中 获取第一账户的账户标识(例如:卡片的***)和第一账户对应的第一流水数据。
需要说明的是,该卡片可以在与其他设备进行数据交互时,可以记录所产生的流水数据,例如:消费数据、充值数据等等,并且记录流水数据发生的时间。
第二种方式:
通过扫描的方式,从承载第一账户的载体中获取所述第一账户的账户标识;
根据所述第一账户的账户标识,从服务器中获取所述第一账户的账户标识对应的第一流水数据。
例如:在承载第一账户的载体中包含二维码图片,该二维码图片中包含了第一账户的账户标识,那么通过扫描的方式可以从该载体中获取第一账户的账户标识,进而通过该第一账户的账户标识查找到与该第一账户的账户标识对应的流水数据。
第三种方式:
提供用户界面,并通过所述用户界面接收用户输入的第一账户的账户标识;
根据所述第一账户的账户标识,从服务器中获取所述第一账户的账户标识对应的第一流水数据。
例如:在终端设备中提供用户界面,并可以通过该用户界面发起数据同步操作。即通过该用户界面可以获取第一账户的账户标识,这里的第一账户的账户标识可以理解为承载第一账户的卡片的***。进而通过第一账户的账户标识可以获取与该第一账户的账户标识对应的流水数据。
较优地,在获取第一账户的账户标识和所述第一账户对应的第一流水数据之前,所述方法还包括:
若检测到与第一账户关联的第二账户发生数据变化,则发送提示信息,所 述提示信息用于提示用户在所述第一账户与所述第二账户之间进行数据同步。
例如:为了保证第一账户与其关联的第二账户之间的数据一致性,在检测到与第一账户关联的第二账户的数据发生变化时,可以通过发送提示信息的方式,提示用户在所述第一账户与第二账户之间进行数据同步。
较优地,在本说明书实施例中,获取所述第一账户在一个同步周期内产生的第一流水数据。
这里的同步周期可以理解为相邻两次同步操作发生期间的时间,这里的同步周期可以是固定周期,也可以是不固定周期,这里不做具体限定。例如:在发起本次同步操作时,确定上一次发起同步操作或者上一次数据同步完成的时间T,那么以确定的该时间T为起点、以发起本次同步操作的时间为终点,确定在这一时间段(从起点到终点)中产生的流水数据。
步骤705:确定与所述第一账户关联的第二账户对应的第二流水数据。
在本说明书实施例中,根据所述第一账户的账户标识,确定与所述第一账户的账户标识建立关联关系的第二账户的账户标识;
根据所述第二账户的账户标识,查找与所述第二账户的账户标识建立对应关系的第二流水数据。
下面详细说明如何建立与所述第一账户关联的第二账户。
首先,获取第一账户的账户标识。
这里获取第一账户的账户标识的方式包括但不限于:
通过近距离通信方式,从承载第一账户的载体中获取第一账户的账户标识;
通过扫描的方式,从承载第一账户的载体中获取第一账户的账户标识;
通过用户界面接收用户输入的第一账户的账户标识。
其次,根据所述第一账户的账户标识,创建第二账户的账户标识。
这里所创建的第二账户的账户标识可以与第一账户的账户标识相同,也可以不相同,这里不做具体限定。
最后,建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的关联关系。
需要说明的是,针对第一账户可以创建至少一个第二账户,在执行数据同步的时候,可以是虚拟账户与实体账户之间的数据同步,也就是说,本说明书实施例中记载的第一账户和第二账户分别代表实体账户和虚拟账户,而实体账户与虚拟账户之间具备关联关系,至于多少个虚拟账户这里不做限定。
较优地,为了防止用户恶意使用虚拟账户,所述方法还包括:
在得到所述第二账户的账户标识后,建立所述第二账户的账户标识与用于支付的应用账户之间的关联关系。
即在创建虚拟账户(即第二账户)时,与用户签署代扣协议,即建立所述第二账户的账户标识与用于支付的应用账户之间的关联关系,一旦发现第二账户出现恶意透支或者在第一账户与第二账户之间实现数据同步之后发现恶意透支,那么可以从与第二账户的账户标识建立关联关系的用于支付的应用账户中扣除恶意透支的费用。
需要说明的是,本说明书实施例中记载的“第一账户”和“第二账户”中的“第一”和“第二”没有特殊含义,仅仅是用来区分账户。进一步,承载第一账户的载体为实体的,例如:IC卡,但是承载第二账户的载体为虚拟的,例如:电子卡片。
步骤707:根据所述第一流水数据和/或所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
在本说明书实施例中,根据所述第一流水数据和/或所述第二流水数据,计算得到用于同步的同步数据;
分别将所述同步数据同步至所述第一账户和所述第二账户。
假设在创建第二账户时,根据第一账户对应的余额数据,将该余额数据同步至第二账户中。
若所述同步数据为负数,那么将空分别写入所述第一账户和所述第二账 户;并从与所述第二账户关联的用于支付的应用账户中扣除所述负数对应的金额。
较优地,所述方法还包括:
将同步时间、所述第一账户的账户标识、所述第一流水数据发送给服务器,并删除承载所述第一账户的载体中记录的所述第一流水数据;和/或,
将同步时间、所述第二账户的账户标识、所述第二流水数据发送给所述服务器,并删除所述第二流水数据。
本说明书实施例中记载的所述流水数据包含付款数据、充值数据中的至少一种或者多种。
通过本说明书实施例提供的技术方案,在满足设定的同步条件的情况下,获取第一账户的账户标识和所述第一账户对应的第一流水数据;确定与所述第一账户关联的第二账户对应的第二流水数据;根据所述第一流水数据和/或所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。这样,能够有效保证第一账户与第二账户之间数据一致性。也就是说,假设第一账户是承载在载体中的账户,第二账户为与所述第一账户关联的虚拟的电子账户,那么用户既可以使用第一账户完成交易,也可以使用第二账户完成交易。同时,通过本说明书实施例提供的技术方案,能够保证这两个账户之间数据的一致性,进而提升用户的支付体验。
图8为本说明书实施例提供的一种数据同步方法的流程示意图,该数据处理方法如下所示。执行主体可以为客户端,该客户端可以是运行在智能终端中的应用程序APP,智能终端包含但不限于移动智能终端,如智能手机、平板电脑等,还包含计算机、笔记本等其他智能终端。
步骤801:获取记载在载体中的第一账户和第一账户中的余额。
在本说明书实施例中,第一账户可以为发行载体的主体所提供,并被写入到载体中,第一账户的形式可以包含数字、字母及其组合,在此不做具体限定。载体的形式可以包含但限于实体卡、纽扣卡等,在此不作具体限定。
在本说明书实施例中,可以读取载体中的数字,以形成第一账户中的余额。例如:该载体中包含近距离无线通讯NFC(Near Field Communication,缩写:NFC)模块,支持NFC功能的终端设备可以在交易发生时向NFC模块中写入数字,并能够读取NFC模块中的数字。
本说明书实施例可以提供但不限于如下实现方式:
1、向载体发射射频信号,使载体根据射频信号发送响应信号;
接收响应信号;并从响应信号中解析出第一账户和第一账户中的余额。
在本说明书实施例中,当用户通过载体中的第一账户或客户端中的第二账户发生收付数据,可将载体与客户端所在设备贴近,客户端通过NFC模块向载体发射射频信号即为向载体发射近距离无线射频信号,载体中的NFC模块响应而生成响应信号,响应信号中携带第一账户和第一账户中的余额。客户端通过NFC模块接收响应信号,并利用解析模块从中解析出第一账户和第一账户中的余额。
若载体中包含可接收并响应其他频率射频信号的响应模块,则操作客户端所在设备发射可被响应的其他频率射频信号。因此,在满足客户端所在设备发射的射频信号可被载体响应的前提下,客户端发射的射频信号包含但不限于近距离无线射频信号,在此不作限定。
2、接收用户输入的第一账户;并基于第一账户,从服务器中获取第一账户中的余额。
在本说明书实施例中,若与所述载体之间发生收付数据的收付设备向第一账户写入最新的余额后,还可以将第一账户中的余额存储在服务器中,则客户端可以通过用户输入的第一账户在服务器中检索,查找第一账户的最新余额。
3、扫描载体,得到第一账户;并基于第一账户,从服务器中获取第一账户中的余额。
在本说明书实施例中,若第一账户显示在载体表面,则可以利用客户端扫描载体表面,获得第一账户。此时,第一账户的存在形式可以包含但不限于: 突出显示,以使得客户端通过图形识别的方式获取第一账户;或者,第一账户记载在二维码或条形码等识别码中,以使得客户端扫描并解析识别码,获得第一账户。
从服务器中获取第一账户中的余额,可参考上文第二种获取第一账户中余额的方法,在此不再赘述。
步骤803:根据第一账户,在客户端创建第一账户关联的第二账户,并将第一账户中的余额写入第二账户中。
在本说明书实施例中,若第一账户视为记载在载体中的实体账户,第二账户可以为实体账户关联的虚拟账户。虚拟账户可以以用户图形界面的形式存储在客户端,在用户图形界面可以显示虚拟账户和虚拟账户中的余额。用户图形界面提供界面对象,通过操作界面对象,可以处理收付业务。例如,界面对象包含二维码生成对象,点击二维码生成对象,可以生成支付二维码,支付二维码用于收付业务。
在本说明书实施例中,在客户端创建第二账户之后,客户端可以将第二账户及第一账户中的余额发送到服务器。同时,当后续第二账户发生收付数据之后,客户端可将收付数据发送给服务器进行存储,这可以避免增加客户端的存储负担,而且在后续第一账户和第二账户进行余额同步过程中,可以方便地从服务器中获取第二账户发生的收付数据和余额。
在本说明书实施例中,根据第一账户,在客户端创建第一账户关联的第二账户,可以包括但不限于:
在客户端创建与第一账户相同的第二账户,将与第一账户相同的第二账户确定为第一账户关联的第二账户。在这种情况下,第一账户和第二账户的标识信息相同,例如具有相同的字母、数字及其组合。
第二账户与第一账户也可以不相同,而是根据关联规则形成关联关系。
利用本说明实施例提供的账户的处理方法,用户可以随时创建与第一账户关联的第二账户,从而既可以利用载体中的第一账户发生收付数据,也可以利 用客户端中的第二账户发生收付数据,可选择度高。尤其是,即使在消费时,遇到载体或客户端中的其中之一未随身携带、或者无法使用,也可以使用载体或客户端中的另一个进行消费支付,提升用户支付体验。
图9为本说明书实施例提供的一种数据同步方法的流程示意图,该方法如下所示,旨在实现第一账户和第一账户关联的第二账户之间的余额同步。该账户的处理方法的执行主体可以为客户端,客户端可以是运行在智能终端中的应用程序APP,智能终端包含但不限于移动智能终端,如智能手机、平板电脑等,还包含计算机、笔记本等其他智能终端。
步骤901:获取记载在载体中的第一账户和第一账户中的余额。
获取记载在载体中的第一账户和第一账户中的余额的方式,可以参考上文步骤801的内容,在此不再赘述。
在本说明书实施例中,为了使用户在通过第二账户发生收付数据之后,能够及时将第二账户发生的收付数据同步到第一账户,在获取记载在载体中的第一账户和第一账户中的余额之前,处理方法还包括:
若第二账户中发生至少一个收付数据,则发射提醒信号,提醒信号用于提醒用户提供与第二账户关联的第一账户。这可以给用户带来方便,减轻用户的记忆负担。
在收到提醒信号后,用户可以采用上文步骤801介绍的三种获取方式,将第一账户和第一账户中的余额提供给客户端。
在本说明书实施例中,该提醒信号的形式可以包含但不限于:语音、声音、振动、图形、文字等形式,在此不作具体限定。
在本说明书实施例中,第二账户中发生至少一个收付数据,则发射提醒信号,可以包含以下至少一种或多种:
每发生一个收付数据,则发射提醒信号;
发生设定数量的收付数据之后,则发射提醒信号;
定期发射提醒信号;或
若第二账户中因发生收付数据而导致余额为0或者余额不足,则发射提醒信号。
步骤903:确定所述第一账户关联的第二账户发生的至少一个收付数据和第二账户中的余额,收付数据包含各消费金额和充值金额中的一种或两种。
在本说明书实施例中,确定所述第一账户关联的第二账户发生的至少一个收付数据和第二账户中的余额,包括:
确定第一账户关联的第二账户;
确定第二账户发生的至少一个收付数据和第二账户中的余额。
在本说明书实施例中,确定第一账户关联的第二账户的方法可以包括:
在获取记载在载体中的第一账户和第一账户的余额之后,将运行于客户端的各第二账户中,与第一账户相同的第二账户确定为第一账户关联的第二账户。
确定第一账户关联的第二账户的方法还可以包括:
向服务器发送第一账户,使服务器确定与第一账户相同的第二账户;
将从服务器获取的与第一账户相同的第二账户确定为第一账户关联的第二账户。
确定第一账户关联的第二账户的方法还可以包括:
若基于上文步骤803创建的第二账户与第一账户不同,则根据第一账户与第二账户的关联关系,从本地或服务器中获取与第一账户关联的第二账户。
在本说明书实施例中,存储第二账户的客户端与后台服务器可以随时建立连接关系,因此确定第二账户发生的至少一个收付数据和第二账户中的余额,可以包括:
通过客户端向服务器发送收付数据获取请求,收付数据获取请求用于请求服务器发送第二账户发生的各收付数据和第二账户中的余额;
接收服务器发送的第二账户发生的各收付数据和第二账户中的余额。
在这种情形下,第二账户发生的各收付数据存储在服务器中,可以节省本 地客户端的存储负担。
在本说明书实施例中,确定第二账户发生的至少一个收付数据,包括如下两种情形:
1、确定第二账户在相邻更新周期中发生的至少一个收付数据,更新周期为相邻两次将第一账户和第二账户中的余额更新为同一更新余额的时间区间。此时,向服务器发送的收付数据获取请求用于请求服务器发送相邻更新周期中发生的各收付数据,和第二账户中的最新余额。基于收付数据获取请求,服务器将从最新一次金额更新到当前这一相邻更新周期中发生的各收付数据发送给客户端。
2、确定第二账户实时发生的收付数据。参考上文步骤501所称第二账户中每发生一次收付数据,便获取第一账户中的余额。
步骤905:基于第一账户中发生收付数据的假设条件,将第一账户中的余额和第二账户中的余额更新为同一更新余额。
若根据步骤903,若确定的第二账户发生的收付数据为第二账户在相邻更新周期中发生的至少一个收付数据,则基于所述第一账户中发生所述收付数据的假设条件,将所述第一账户中的余额和第二账户中的余额更新为同一更新余额,包括:
基于第一账户在相邻更新周期中发生各收付数据的假设条件,将第一账户中的余额和第二账户中的余额更新为同一更新余额。
由于第一账户和第二账户之间具有统一性,因此发生在第二账户中的收付数据可等同于发生在第一账户,因此可以设定第一账户在相邻更新周期中发生各收付数据的假设条件,来确定同一更新余额。
例如,参照表1所示:
表1
  第一账户 第二账户
最近一次更新余额 20元 20元
消费金额 3元 14元
充值金额   10元
当前余额 17元 16元
更新余额 13元 13元
在从最近一次更新到当前之间的相邻更新周期内,第二账户所发生的收付数据包含:充值金额10元;消费金额14元,第二账户的当前余额16元,而第一账户的当前余额为17元。
站在第一账户和第二账户统一的角度,基于第一账户中发生收付数据的假设条件,将第一账户中的余额和第二账户中的余额更新为同一更新余额,包括:
基于第一账户中发生收付数据的假设条件,计算第一账户中的余额在发生收付数据之后的更新余额;
将第一账户中的余额和第二账户中的余额更新为更新余额。
根据各收付数据的种类不同,计算第一账户中的余额在发生收付数据之后的更新余额,包括:
若收付数据中包含至少一个充值金额,则对第一账户中的余额加上各充值金额;
若收付数据中包含至少一个消费金额,则对第一账户中的余额减去各消费金额;
将得到的处理结果作为更新余额。
例如,参考表1,假设第二账户所发生的收付数据发生于第一账户,则计算第一账户中的当前余额为17-14+10=13元,并确定更新余额为13元。之后,将第一账户和第二账户的中余额更新为13元。
以上表1示例仅供参考,在具体应用场景发生的收付数据具有其他多种情形,不作具体限定。
这种确定第二账户发生的至少一个收付数据的方法尤其可适用于记载第一账户的载体无法实时连接服务器、或存储第二账户的客户端使用频率较大的 情形,可以解决第一账户所在载体所存在的连接问题。
这样,在每次对第一账户和第二账户的余额进行同步更新时,可以同时处理多个收付数据,处理效率更加高效。
若根据步骤903,确定第二账户发生的收付数据为实时收付数据,则可以参考表一所举示例,来确定第一账户和第二账户的同一更新,在此不再赘述。
在本说明书实施例中,在确定更新余额之后,客户端可以直接将第二账户中的余额更新为更新余额。
参考上文步骤801中获取记载在载体中的第一账户中的余额的三种方式,将第一账户中的余额更新为更新余额的方式包括:
1、若载体与客户端之间可以通过射频信号通信,则可以将NFC模块中记载的第一账户的余额更新为更新余额。例如在载体与客户端所在设备贴近时,可以将载体中的NFC模块中第一账户的余额修改为更新余额。
2、若载体通过与其发生收付数据的收付设备与服务器连接,则客户端请求服务器将更新余额发送至载体,之后与载体发生收付数据的设备向载体中写入更新余额。例如,在载体与公交POS机、收银POS机等收付设备贴近时,该公交POS机、收银POS机等收付设备可修改记载在载体中的第一账户的余额为更新余额。
将第一账户中的余额更新为更新余额的第一种方式,对用户来说,可以随时随地进行操作,操作便利性好。
使用本说明书实施例提出的账户的处理方法,可以将第一账户和第二账户中的余额进行同步,实现第一账户和第二账户的统一。
这尤其可以适用于但不限于记载第一账户的载体无法连接服务器,或者载体不能实时连接至服务器的情形。
图10为本说明书实施例提出的一种数据同步方法的流程示意图。该处理方法如下所示。该处理方法的执行主体为服务器。该方法尤其适用于但不限于记载第一账户的载体可以方便或实施连接服务器。
步骤1001:接收第一账户和第一账户关联的第二账户中的至少一个账户发生的收付数据。
第一账户中发生的收付数据为通过客户端从记载第一账户的载体中获取第一账户时所确定,收付数据包含充值金额、消费金额。
参考上文步骤803中获取记载在载体中的第一账户和第一账户中的余额的第二种方式,服务器可以通过与载体之间发生收付数据的收付设备接收第一账户发生的收付数据。服务器可以直接从存储第二账户的客户端接收第二账户发生的收付数据。
步骤1003:将第一账户中的余额和第二账户中的余额均更新为发生收付数据之后的同一更新余额。
其中,第一账户中的更新余额是通过收付设备写入到载体中。
在本说明书实施例中,在接收第一账户和第一账户关联的第二账户中的至少一个账户发生的收付数据之后,处理方法还可以包括:
确定在相邻更新周期中接收的至少一个收付数据,更新周期为相邻两次将第一账户和第二账户中的余额更新为同一更新余额的时间区间;
将第一账户中的余额和第二账户中的余额均更新为发生收付数据之后的同一更新余额,包括:
将第一账户中的余额和第二账户中的余额均更新为在相邻更新周期中发生的收付数据之后的同一更新余额。
在这种情况下,可以参考上文步骤905中的内容,将第一账户和第二账户中的其中一个账户确定为基准账户,假设该基准账户所发生的收付数据也发生在另一个账户,从而确定一个更新账户。
此时,每次更新可以同时处理多个收付数据,提高处理效率。
在本说明书实施例中,将第一账户中的余额和第二账户中的余额均更新为发生收付数据之后的同一更新余额,还可以包括:
在每接收一个收付数据时,将第一账户中的余额和第二账户中的余额均更 新为发生所述收付数据之后的同一更新余额。
在本说明书实施例中,该处理方法还可以包括:
若接收到第一账户的收付数据小于第二账户的余额,则向运行第二账户的客户端发送提醒信息,提醒信息用于告知用户余额不足。同时,服务器可以通知收付设备账户余额不足,无法完成扣款。
本说明书实施例提供另一种实现第一账户和第二账户中的余额同步更新至更新余额的技术手段,保持第一账户和第二账户中的余额一致。
图11为本说明书实施例提供的一种账户创建设备的结构示意图。该账户创建设备包括:获取单元1101、创建单元1102和存储单元1103,其中:
获取单元1101,通过设定的方式从指定载体中获取第一账户的账户标识;
创建单元1102,根据所述第一账户的账户标识,创建第二账户的账户标识;
存储单元1103,建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的映射关系。
在本说明书的另一个实施例中,所述获取单元1101通过设定的方式从指定载体中获取第一账户的账户标识,包括:
通过近距离通信技术与指定载体建立数据通道,并通过所述数据通道从所述指定载体中获取第一账户的账户标识。
在本说明书的另一个实施例中,所述获取单元1101通过设定的方式从指定载体中获取第一账户的账户标识,包括:
通过扫描的方式从指定载体中获取第一账户的账户标识。
在本说明书的另一个实施例中,所述存储单元1103,在得到所述第二账户的账户标识后,建立并存储所述第二账户的账户标识与用于支付的应用账户之间的关联关系。
在本说明书的另一个实施例中,所述指定载体包含支持近距离通信技术的卡式装置、包含所述第一账户的账户标识的第二终端设备、包含所述第一账户的账户标识的应用客户端中的至少一种或者多种。
在本说明书的另一个实施例中,所述第二账户包含虚拟账户、电子账户中的一种。
需要说明的是,本说明书实施例中所记载的账户创建设备可以通过软件方式实现,也可以通过硬件方式实现,这里不做具体限定。
基于同一个发明构思,本说明书实施例还提供一种账户创建设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
通过设定的方式从指定载体中获取第一账户的账户标识;
根据所述第一账户的账户标识,创建第二账户的账户标识;
建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的映射关系。
其中,处理器的其他功能还可以参见上述实施例中记载的内容,这里不再一一赘述。
基于同一个发明构思,本说明书实施例还提供一种计算机可读存储介质,该计算机可读存储介质包括与电子设备结合使用的程序,程序可被处理器执行以完成以下步骤:
通过设定的方式从指定载体中获取第一账户的账户标识;
根据所述第一账户的账户标识,创建第二账户的账户标识;
建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的映射关系。
其中,处理器的其他功能还可以参见上述实施例中记载的内容,这里不再一一赘述。
图12为本说明书实施例提供的一种账户充值设备的结构示意图。所述账户充值设备包括:建立单元1201和充值单元1202,其中:
建立单元1201,通过近距离通信技术与包含第一账户的账户标识的指定载体建立数据通道;
充值单元1202,通过所述数据通道将第二账户的充值数据写入所述指定载体中,以实现为所述第一账户进行充值。
在本说明书的另一个实施例中,所述账户充值设备还包括:生成单元1203,其中:
所述生成单元1203,利用用于支付的应用账户向第二账户执行转账操作,生成第二账户的充值数据。
在本说明书的另一个实施例中,所述指定载体包含支持近距离通信技术的卡式装置、包含所述第一账户的账户标识的第二终端设备、包含所述第一账户的账户标识的应用客户端中的至少一种或者多种。
需要说明的是,本说明书实施例中所记载的账户充值设备可以通过软件方式实现,也可以通过硬件方式实现,这里不做具体限定。
基于同一个发明构思,本说明书实施例提供一种账户充值设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
通过近距离通信技术与包含第一账户的账户标识的指定载体建立数据通道;
通过所述数据通道将第二账户的充值数据写入所述指定载体中,以实现为所述第一账户进行充值。
其中,处理器的其他功能还可以参见上述实施例中记载的内容,这里不再一一赘述。
基于同一个发明构思,本说明书实施例还提供一种计算机可读存储介质,该计算机可读存储介质包括与电子设备结合使用的程序,程序可被处理器执行以完成以下步骤:
通过近距离通信技术与包含第一账户的账户标识的指定载体建立数据通道;
通过所述数据通道将第二账户的充值数据写入所述指定载体中,以实现为 所述第一账户进行充值。
图13为本说明书实施例提供的一种账户充值设备的结构示意图。所述账户充值设备包括:接收单元1301和处理单元1302,其中:
接收单元1301,在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一终端设备发送的充值数据;
处理单元1302,根据所述充值数据,对第一账户的余额数据进行处理。
在本说明书的另一个实施例中,所述处理单元1302根据所述充值数据,对第一账户的余额数据进行处理,包括:
在第一账户的余额数据为零的情况下,将所述充值数据写入所述第一账户中;
在第一账户的余额数据不为零的情况下,利用所述充值数据,修改所述第一账户的余额数据。
需要说明的是,本说明书实施例中所记载的账户充值设备可以通过软件方式实现,也可以通过硬件方式实现,这里不做具体限定。
基于同一个发明构思,本说明书实施例提供一种账户充值设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一终端设备发送的充值数据;
根据所述充值数据,对第一账户的余额数据进行处理。
其中,处理器的其他功能还可以参见上述实施例中记载的内容,这里不再一一赘述。
基于同一个发明构思,本说明书实施例还提供一种计算机可读存储介质,该计算机可读存储介质包括与电子设备结合使用的程序,程序可被处理器执行以完成以下步骤:
在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一 终端设备发送的充值数据;
根据所述充值数据,对第一账户的余额数据进行处理。
图14为本说明书实施例提供的一种数据同步设备的结构示意图。所述数据同步设备包括:获取单元1401、接收单元1402和同步单元1403,其中:
获取单元1401,通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据;
接收单元1402,接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据;
同步单元1403,根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致。
其中,本说明书实施例中记载的数据处理设备可以应用在服务器中,该服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系。
在本说明书的另一个实施例中,所述获取单元1401通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据,包括:
通过近距离通信方式与所述指定载体建立数据通道;
在确定交易发生的情况下,通过所述数据通道从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据。
在本说明书的另一个实施例中,所述数据同步设备还包括:发送单元1404,其中:
所述发送单元1404,若所述同步数据为负数,那么向所述第一终端设备发送扣款请求,所述扣款请求用于请求从与所述第二账户关联的用于支付的应用账户中扣除所述负数对应的金额。
需要说明的是,本说明书实施例中所记载的数据同步设备可以通过软件方 式实现,也可以通过硬件方式实现,这里不做具体限定。
基于同一个发明构思,本说明书实施例提供一种数据同步设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据;
接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据;
根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致;
其中,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系。
其中,处理器的其他功能还可以参见上述实施例中记载的内容,这里不再一一赘述。
基于同一个发明构思,本说明书实施例还提供一种计算机可读存储介质,该计算机可读存储介质包括与电子设备结合使用的程序,程序可被处理器执行以完成以下步骤:
通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据;
接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据;
根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致;
其中,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设 备中包含的第二账户之间建立关联关系。
图15为本说明书实施例提供的一种数据同步设备的结构示意图。所述数据同步设备包括:建立单元1501和同步单元1502,其中:
建立单元1501,通过近距离通信方式与指定载体建立数据通道;
同步单元1502,通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
在本说明书的另一个实施例中,所述数据同步设备还包括:接收单元1503和处理单元1504,其中:
所述接收单元1503,接收服务器发送的同步数据,所述同步数据是所述服务器根据上述记载的同步方式得到的;
所述处理单元1504,利用所述同步数据修改所述第二账户对应的数据,以使所述第二账户对应的数据与服务器中包含的主账户对应的数据一致;
其中,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系。
需要说明的是,本说明书实施例中所记载的数据同步设备可以通过软件方式实现,也可以通过硬件方式实现,这里不做具体限定。
基于同一个发明构思,本说明书实施例提供一种数据同步设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
通过近距离通信方式与指定载体建立数据通道;
通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
其中,处理器的其他功能还可以参见上述实施例中记载的内容,这里不再一一赘述。
基于同一个发明构思,本说明书实施例还提供一种计算机可读存储介质, 该计算机可读存储介质包括与电子设备结合使用的程序,程序可被处理器执行以完成以下步骤:
通过近距离通信方式与指定载体建立数据通道;
通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
图16为本说明书实施例提供的一种数据同步设备的结构示意图。所述数据同步设备包括:建立单元1601、获取单元1602、确定单元1603和同步单元1604,其中:
建立单元1601,通过近距离通信方式与指定载体建立数据通道;
获取单元1602,通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据;
确定单元1603,确定与所述第一账户关联的第二账户对应的第二流水数据;
同步单元1604,根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
在本说明书的另一个实施例中,所述数据同步设备还包括:发送单元1605,其中:
所述发送单元1605,在建立数据通道之前,若检测到与第一账户关联的第二账户对应的数据发生变化,则发送提示信息,所述提示信息用于提示用户在所述第一账户与所述第二账户之间进行数据同步。
在本说明书的另一个实施例中,所述确定单元1603确定与所述第一账户关联的第二账户对应的第二流水数据,包括:
根据所述第一账户的账户标识,确定与所述第一账户的账户标识建立关联关系的第二账户的账户标识;
根据所述第二账户的账户标识,查找与所述第二账户的账户标识建立对应关系的第二流水数据。
在本说明书的另一个实施例中,所述同步单元1604根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步,包括:
根据所述第一流水数据和所述第二流水数据,计算得到用于同步的同步数据;
分别将所述同步数据同步至所述第一账户和所述第二账户。
在本说明书的另一个实施例中,所述同步单元1604将所述同步数据同步至所述第一账户和所述第二账户,包括:
若所述同步数据为负数,那么将空分别写入所述第一账户和所述第二账户;
从与所述第二账户关联的用于支付的应用账户中扣除所述负数对应的金额。
在本说明书的另一个实施例中,所述数据同步设备还包括:删除单元1606,其中:
所述删除单元1606,将同步时间、所述第一账户的账户标识、所述第一流水数据发送给服务器,并删除承载所述第一账户的载体中记录的所述第一流水数据;和/或,
将同步时间、所述第二账户的账户标识、所述第二流水数据发送给所述服务器,并删除所述第二流水数据。
在本说明书的另一个实施例中,所述流水数据包含消费数据、充值数据中的至少一种或者多种。
需要说明的是,本说明书实施例中所记载的数据同步设备可以通过软件方式实现,也可以通过硬件方式实现,这里不做具体限定。
基于同一个发明构思,本说明书实施例提供一种数据同步设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
通过近距离通信方式与指定载体建立数据通道;
通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据;
确定与所述第一账户关联的第二账户对应的第二流水数据;
根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
其中,处理器的其他功能还可以参见上述实施例中记载的内容,这里不再一一赘述。
基于同一个发明构思,本说明书实施例还提供一种计算机可读存储介质,该计算机可读存储介质包括与电子设备结合使用的程序,程序可被处理器执行以完成以下步骤:
通过近距离通信方式与指定载体建立数据通道;
通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据;
确定与所述第一账户关联的第二账户对应的第二流水数据;
根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
通过本说明书实施例提供的技术方案,在终端设备上为指定载体中包含的第一账户创建第二账户,以及利用该终端设备中的第二账户,通过近距离通信方式实现为第一账户充值以及保证第一账户与第二账户之间的数据一致性。也就是说,假设第一账户是承载在指定载体中的账户,第二账户为与所述第一账户关联的虚拟的电子账户,那么用户既可以使用第一账户完成交易,也可以使用第二账户完成交易。同时,通过本说明书实施例提供的技术方案,能够保证这两个账户之间数据的一致性,进而提升用户的支付体验。
在20世纪90年代,对于一个技术的改进可以很明显地区分是硬件上的改进(例如,对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对 于方法流程的改进)。然而,随着技术的发展,当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此,不能说一个方法流程的改进就不能用硬件实体模块来实现。例如,可编程逻辑器件(Programmable Logic Device,PLD)(例如现场可编程门阵列(Field Programmable Gate Array,FPGA))就是这样一种集成电路,其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字***“集成”在一片PLD上,而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且,如今,取代手工地制作集成电路芯片,这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现,它与程序开发撰写时所用的软件编译器相类似,而要编译之前的原始代码也得用特定的编程语言来撰写,此称之为硬件描述语言(Hardware Description Language,HDL),而HDL也并非仅有一种,而是有许多种,如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)等,目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚,只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中,就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现,例如,控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit,ASIC)、可编程逻辑控制器和嵌入微控制器的形式,控制器的例子包括但不限于以下微控制器:ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320,存储器控制器还可以被实现为存 储器的控制逻辑的一部分。本领域技术人员也知道,除了以纯计算机可读程序代码方式实现控制器以外,完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件,而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至,可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的***、装置、模块或单元,具体可以由计算机芯片或实体实现,或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的,计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便,描述以上装置时以功能分为各种单元分别描述。当然,在实施本申请时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白,本发明的实施例可提供为方法、***、或计算机程序产品。因此,本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中,计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器,随机存取存储器(RAM)和/或非易失性内存等形式,如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括,但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带,磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质,可用于存储可以被计算设备访问的信息。按照本文中的界定,计算机可读介质不包括暂存电脑可读媒体(transitory media),如调制的数据信号和载波。
还需要说明的是,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、 方法、商品或者设备所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本申请可以在由计算机执行的计算机可执行指令的一般上下文中描述,例如程序模块。一般地,程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本申请,在这些分布式计算环境中,由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中,程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述,各个实施例之间相同相似的部分互相参见即可,每个实施例重点说明的都是与其他实施例的不同之处。尤其,对于***实施例而言,由于其基本相似于方法实施例,所以描述的比较简单,相关之处参见方法实施例的部分说明即可。
以上所述仅为本申请的实施例而已,并不用于限制本申请。对于本领域技术人员来说,本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等,均应包含在本申请的权利要求范围之内。

Claims (52)

  1. 一种账户创建方法,包括:
    第一终端设备通过设定的方式从指定载体中获取第一账户的账户标识;
    所述第一终端设备根据所述第一账户的账户标识,创建第二账户的账户标识;
    所述第一终端设备建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的映射关系。
  2. 根据权利要求1所述的账户创建方法,第一终端设备通过设定的方式从指定载体中获取第一账户的账户标识,包括:
    第一终端设备通过近距离通信技术与指定载体建立数据通道,并通过所述数据通道从所述指定载体中获取第一账户的账户标识。
  3. 根据权利要求1所述的账户创建方法,第一终端设备通过设定的方式从指定载体中获取第一账户的账户标识,包括:
    第一终端设备通过扫描的方式从指定载体中获取第一账户的账户标识。
  4. 根据权利要求1所述的账户创建方法,所述方法还包括:
    在得到所述第二账户的账户标识后,所述第一终端设备建立并存储所述第二账户的账户标识与用于支付的应用账户之间的关联关系。
  5. 根据权利要求1所述的账户创建方法,所述指定载体包含支持近距离通信技术的卡式装置、包含所述第一账户的账户标识的第二终端设备、包含所述第一账户的账户标识的应用客户端中的至少一种或者多种。
  6. 根据权利要求1所述的账户创建方法,所述第二账户包含虚拟账户、电子账户中的一种。
  7. 一种账户充值方法,包括:
    第一终端设备通过近距离通信技术与包含第一账户的账户标识的指定载体建立数据通道;
    所述第一终端设备通过所述数据通道将第二账户的充值数据写入所述指 定载体中,以实现为所述第一账户进行充值。
  8. 根据权利要求7所述的账户充值方法,所述方法还包括:
    第一终端设备利用用于支付的应用账户向第二账户执行转账操作,生成第二账户的充值数据。
  9. 根据权利要求7所述的账户充值方法,所述指定载体包含支持近距离通信技术的卡式装置、包含所述第一账户的账户标识的第二终端设备、包含所述第一账户的账户标识的应用客户端中的至少一种或者多种。
  10. 一种账户充值方法,包括:
    指定载体在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一终端设备发送的充值数据;
    根据所述充值数据,对第一账户的余额数据进行处理。
  11. 根据权利要求10所述的账户充值方法,根据所述充值数据,对第一账户的余额数据进行处理,包括:
    在第一账户的余额数据为零的情况下,将所述充值数据写入所述第一账户中;
    在第一账户的余额数据不为零的情况下,利用所述充值数据,修改所述第一账户的余额数据。
  12. 一种数据同步方法,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系,包括:
    所述服务器通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据;
    所述服务器接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据;
    所述服务器根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致。
  13. 根据权利要求12所述的数据同步方法,所述服务器通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据,包括:
    所述服务器通过近距离通信方式与所述指定载体建立数据通道;
    所述服务器在确定交易发生的情况下,通过所述数据通道从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据。
  14. 根据权利要求12所述的数据同步方法,所述方法还包括:
    若所述同步数据为负数,那么向所述第一终端设备发送扣款请求,所述扣款请求用于请求从与所述第二账户关联的用于支付的应用账户中扣除所述负数对应的金额。
  15. 一种数据同步方法,包括:
    第一终端设备通过近距离通信方式与指定载体建立数据通道;
    所述第一终端设备通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
  16. 根据权利要求15所述的数据同步方法,所述方法还包括:
    第一终端设备接收服务器发送的同步数据,所述同步数据是所述服务器根据权利要求12中所记载的方式得到的;
    所述第一终端设备利用所述同步数据修改所述第二账户对应的数据,以使所述第二账户对应的数据与服务器中包含的主账户对应的数据一致;
    其中,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系。
  17. 一种数据同步方法,包括:
    第一终端设备通过近距离通信方式与指定载体建立数据通道;
    所述第一终端设备通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据;
    所述第一终端设备确定与所述第一账户关联的第二账户对应的第二流水数据;
    所述第一终端设备根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
  18. 根据权利要求17所述的数据同步方法,所述第一终端设备在建立数据通道之前,所述方法还包括:
    若检测到与第一账户关联的第二账户对应的数据发生变化,则所述第一终端设备发送提示信息,所述提示信息用于提示用户在所述第一账户与所述第二账户之间进行数据同步。
  19. 根据权利要求17所述的数据同步方法,确定与所述第一账户关联的第二账户对应的第二流水数据,包括:
    根据所述第一账户的账户标识,确定与所述第一账户的账户标识建立关联关系的第二账户的账户标识;
    根据所述第二账户的账户标识,查找与所述第二账户的账户标识建立对应关系的第二流水数据。
  20. 根据权利要求17所述的数据同步方法,根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步,包括:
    根据所述第一流水数据和所述第二流水数据,计算得到用于同步的同步数据;
    分别将所述同步数据同步至所述第一账户和所述第二账户。
  21. 根据权利要求20所述的数据同步方法,将所述同步数据同步至所述第一账户和所述第二账户,包括:
    若所述同步数据为负数,那么将空分别写入所述第一账户和所述第二账户;
    从与所述第二账户关联的用于支付的应用账户中扣除所述负数对应的金额。
  22. 根据权利要求17或21所述的数据同步方法,所述方法还包括:
    将同步时间、所述第一账户的账户标识、所述第一流水数据发送给服务器,并删除承载所述第一账户的载体中记录的所述第一流水数据;和/或,
    将同步时间、所述第二账户的账户标识、所述第二流水数据发送给所述服务器,并删除所述第二流水数据。
  23. 根据权利要求17所述的数据同步方法,所述流水数据包含消费数据、充值数据中的至少一种或者多种。
  24. 一种账户创建设备,包括:
    获取单元,通过设定的方式从指定载体中获取第一账户的账户标识;
    创建单元,根据所述第一账户的账户标识,创建第二账户的账户标识;
    存储单元,建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的映射关系。
  25. 根据权利要求24所述的账户创建设备,所述获取单元通过设定的方式从指定载体中获取第一账户的账户标识,包括:
    通过近距离通信技术与指定载体建立数据通道,并通过所述数据通道从所述指定载体中获取第一账户的账户标识。
  26. 根据权利要求24所述的账户创建设备,所述获取单元通过设定的方式从指定载体中获取第一账户的账户标识,包括:
    通过扫描的方式从指定载体中获取第一账户的账户标识。
  27. 根据权利要求24所述的账户创建设备,
    所述存储单元,在得到所述第二账户的账户标识后,建立并存储所述第二账户的账户标识与用于支付的应用账户之间的关联关系。
  28. 根据权利要求24所述的账户创建设备,所述指定载体包含支持近距离通信技术的卡式装置、包含所述第一账户的账户标识的第二终端设备、包含所述第一账户的账户标识的应用客户端中的至少一种或者多种。
  29. 根据权利要求24所述的账户创建设备,所述第二账户包含虚拟账户、 电子账户中的一种。
  30. 一种账户充值设备,包括:
    建立单元,通过近距离通信技术与包含第一账户的账户标识的指定载体建立数据通道;
    充值单元,通过所述数据通道将第二账户的充值数据写入所述指定载体中,以实现为所述第一账户进行充值。
  31. 根据权利要求30所述的账户充值设备,所述账户充值设备还包括:生成单元,其中:
    所述生成单元,利用用于支付的应用账户向第二账户执行转账操作,生成第二账户的充值数据。
  32. 根据权利要求30所述的账户充值设备,所述指定载体包含支持近距离通信技术的卡式装置、包含所述第一账户的账户标识的第二终端设备、包含所述第一账户的账户标识的应用客户端中的至少一种或者多种。
  33. 一种账户充值设备,包括:
    接收单元,在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一终端设备发送的充值数据;
    处理单元,根据所述充值数据,对第一账户的余额数据进行处理。
  34. 根据权利要求33所述的账户充值设备,所述处理单元根据所述充值数据,对第一账户的余额数据进行处理,包括:
    在第一账户的余额数据为零的情况下,将所述充值数据写入所述第一账户中;
    在第一账户的余额数据不为零的情况下,利用所述充值数据,修改所述第一账户的余额数据。
  35. 一种数据同步设备,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系,包括:
    获取单元,通过近距离通信方式从所述指定载体中获取第一账户的账户标 识和所述第一账户对应的第一流水数据;
    接收单元,接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据;
    同步单元,根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致。
  36. 根据权利要求35所述的数据同步设备,所述获取单元通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据,包括:
    通过近距离通信方式与所述指定载体建立数据通道;
    在确定交易发生的情况下,通过所述数据通道从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据。
  37. 根据权利要求35所述的数据同步设备,所述数据同步设备还包括:发送单元,其中:
    所述发送单元,若所述同步数据为负数,那么向所述第一终端设备发送扣款请求,所述扣款请求用于请求从与所述第二账户关联的用于支付的应用账户中扣除所述负数对应的金额。
  38. 一种数据同步设备,包括:
    建立单元,通过近距离通信方式与指定载体建立数据通道;
    同步单元,通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
  39. 根据权利要求38所述的数据同步设备,所述数据同步设备还包括:接收单元和处理单元,其中:
    所述接收单元,接收服务器发送的同步数据,所述同步数据是所述服务器根据权利要求12中所记载的方式得到的;
    所述处理单元,利用所述同步数据修改所述第二账户对应的数据,以使所述第二账户对应的数据与服务器中包含的主账户对应的数据一致;
    其中,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系。
  40. 一种数据同步设备,包括:
    建立单元,通过近距离通信方式与指定载体建立数据通道;
    获取单元,通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据;
    确定单元,确定与所述第一账户关联的第二账户对应的第二流水数据;
    同步单元,根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
  41. 根据权利要求40所述的数据同步设备,所述数据同步设备还包括:发送单元,其中:
    所述发送单元,在建立数据通道之前,若检测到与第一账户关联的第二账户对应的数据发生变化,则发送提示信息,所述提示信息用于提示用户在所述第一账户与所述第二账户之间进行数据同步。
  42. 根据权利要求40所述的数据同步设备,所述确定单元确定与所述第一账户关联的第二账户对应的第二流水数据,包括:
    根据所述第一账户的账户标识,确定与所述第一账户的账户标识建立关联关系的第二账户的账户标识;
    根据所述第二账户的账户标识,查找与所述第二账户的账户标识建立对应关系的第二流水数据。
  43. 根据权利要求40所述的数据同步设备,所述同步单元根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步,包括:
    根据所述第一流水数据和所述第二流水数据,计算得到用于同步的同步数 据;
    分别将所述同步数据同步至所述第一账户和所述第二账户。
  44. 根据权利要求43所述的数据同步设备,所述同步单元将所述同步数据同步至所述第一账户和所述第二账户,包括:
    若所述同步数据为负数,那么将空分别写入所述第一账户和所述第二账户;
    从与所述第二账户关联的用于支付的应用账户中扣除所述负数对应的金额。
  45. 根据权利要求40或44所述的数据同步设备,所述数据同步设备还包括:删除单元,其中:
    所述删除单元,将同步时间、所述第一账户的账户标识、所述第一流水数据发送给服务器,并删除承载所述第一账户的载体中记录的所述第一流水数据;和/或,
    将同步时间、所述第二账户的账户标识、所述第二流水数据发送给所述服务器,并删除所述第二流水数据。
  46. 根据权利要求40所述的数据同步设备,所述流水数据包含消费数据、充值数据中的至少一种或者多种。
  47. 一种账户创建设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
    通过设定的方式从指定载体中获取第一账户的账户标识;
    根据所述第一账户的账户标识,创建第二账户的账户标识;
    建立并存储所述第一账户的账户标识与所述第二账户的账户标识之间的映射关系。
  48. 一种账户充值设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
    通过近距离通信技术与包含第一账户的账户标识的指定载体建立数据通 道;
    通过所述数据通道将第二账户的充值数据写入所述指定载体中,以实现为所述第一账户进行充值。
  49. 一种账户充值设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
    在通过近距离通信技术与第一终端设备建立数据通道的情况下,接收第一终端设备发送的充值数据;
    根据所述充值数据,对第一账户的余额数据进行处理。
  50. 一种数据同步设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
    通过近距离通信方式从所述指定载体中获取第一账户的账户标识和所述第一账户对应的第一流水数据;
    接收所述第一终端设备发送的所述第二账户的账户标识和所述第二账户对应的第二流水数据;
    根据所述第一流水数据和所述第二流水数据,确定一个同步周期的同步数据,并将所述同步数据发送给所述第一终端设备,以使所述第二账户对应的数据与所述主账户对应的数据一致;
    其中,服务器中包含的主账户与指定载体中包含的第一账户、第一终端设备中包含的第二账户之间建立关联关系。
  51. 一种数据同步设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
    通过近距离通信方式与指定载体建立数据通道;
    通过所述数据通道将第二账户对应的余额数据同步给所述指定载体,以使所述指定载体中包含的第一账户对应的数据与所述第二账户对应的数据一致。
  52. 一种数据同步设备,包括:至少一个存储器和至少一个处理器,其中,所述存储器中存储有程序,并被配置由所述处理器执行以下步骤:
    通过近距离通信方式与指定载体建立数据通道;
    通过所述数据通道获取所述指定载体中包含的第一账户的账户标识和所述第一账户对应的第一流水数据;
    确定与所述第一账户关联的第二账户对应的第二流水数据;
    根据所述第一流水数据和所述第二流水数据,在所述第一账户和所述第二账户之间进行数据同步。
PCT/CN2018/099869 2017-08-16 2018-08-10 一种账户创建、账户充值、数据同步方法及设备 WO2019033994A1 (zh)

Priority Applications (9)

Application Number Priority Date Filing Date Title
KR1020197030513A KR102259714B1 (ko) 2017-08-16 2018-08-10 계좌 생성, 계좌 리필 및 데이터 동기화를 위한 방법 및 디바이스
MYPI2019005808A MY191630A (en) 2017-08-16 2018-08-10 Method and device for account creation, account refilling and data synchronization
AU2018317073A AU2018317073A1 (en) 2017-08-16 2018-08-10 Method and device for account creation, account refilling and data synchronization
EP18846030.7A EP3611684A4 (en) 2017-08-16 2018-08-10 METHOD AND DEVICE FOR CREATING ACCOUNT, FILLING ACCOUNT AND SYNCHRONIZING DATA
SG11201909626V SG11201909626VA (en) 2017-08-16 2018-08-10 Method and device for account creation, account refilling and data synchronization
JP2019556177A JP6946461B2 (ja) 2017-08-16 2018-08-10 アカウント作成、アカウント補充、およびデータ同期のための方法およびデバイス
CA3059627A CA3059627C (en) 2017-08-16 2018-08-10 Method and device for account creation, account refilling and data synchronization
PH12019502426A PH12019502426A1 (en) 2017-08-16 2019-10-25 Method and device for account creation, account refilling and data synchronization
US16/698,327 US10902412B2 (en) 2017-08-16 2019-11-27 Method and device for account creation, account refilling and data synchronization

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710701052.5A CN107657448B (zh) 2017-08-16 2017-08-16 一种账户创建、账户充值、数据同步方法及设备
CN201710701052.5 2017-08-16

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/698,327 Continuation US10902412B2 (en) 2017-08-16 2019-11-27 Method and device for account creation, account refilling and data synchronization

Publications (1)

Publication Number Publication Date
WO2019033994A1 true WO2019033994A1 (zh) 2019-02-21

Family

ID=61128344

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/099869 WO2019033994A1 (zh) 2017-08-16 2018-08-10 一种账户创建、账户充值、数据同步方法及设备

Country Status (12)

Country Link
US (1) US10902412B2 (zh)
EP (1) EP3611684A4 (zh)
JP (1) JP6946461B2 (zh)
KR (1) KR102259714B1 (zh)
CN (2) CN114663086A (zh)
AU (1) AU2018317073A1 (zh)
CA (1) CA3059627C (zh)
MY (1) MY191630A (zh)
PH (1) PH12019502426A1 (zh)
SG (1) SG11201909626VA (zh)
TW (1) TW201911168A (zh)
WO (1) WO2019033994A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115118735A (zh) * 2022-06-08 2022-09-27 腾讯科技(深圳)有限公司 数据同步方法、群组管理方法、装置、设备及存储介质

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114663086A (zh) 2017-08-16 2022-06-24 创新先进技术有限公司 一种账户创建、账户充值、数据同步方法及设备
FR3076034B1 (fr) * 2017-12-22 2022-12-02 Oberthur Technologies Collecte de donnees d'historique de transaction sur un terminal
CN109146444B (zh) * 2018-08-31 2021-09-28 创新先进技术有限公司 虚拟账户创建方法及装置、账户信息更新方法及装置
CN111726321A (zh) * 2019-03-19 2020-09-29 阿里巴巴集团控股有限公司 公共账户管理方法、通信***互方法及相应的装置和***
CN110223179B (zh) * 2019-06-10 2022-07-26 网联清算有限公司 资金的数据处理方法、装置、***、介质
CN114402347A (zh) * 2019-12-30 2022-04-26 连株式会社 程序、信息处理方法、终端
CN112365254A (zh) * 2020-11-20 2021-02-12 马卓 一种基于虚拟账户的无卡取现方法、装置和存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101201956A (zh) * 2007-12-25 2008-06-18 侯万春 自动圈存pos和实现电子钱包ic卡自动圈存的***及方法
CN101252729A (zh) * 2008-04-10 2008-08-27 上海柯源软件有限公司 采用sim卡增强支付类芯片功能的方法
CN103577983A (zh) * 2013-11-25 2014-02-12 成都中联信通科技股份有限公司 一种脱机消费电子货币的圈存方法
CN105096452A (zh) * 2014-05-22 2015-11-25 中兴通讯股份有限公司 短距离通信终端、智能卡充值***及方法
CN105590202A (zh) * 2015-08-28 2016-05-18 ***股份有限公司 使用移动终端进行支付的方法和装置
CN105631657A (zh) * 2014-11-06 2016-06-01 深圳市千讯数据股份有限公司 一种基于非接触式移动支付终端的支付方法
CN107657448A (zh) * 2017-08-16 2018-02-02 阿里巴巴集团控股有限公司 一种账户创建、账户充值、数据同步方法及设备

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2838006B1 (fr) * 2002-04-02 2004-11-12 St Microelectronics Sa Dispositif et procede pour synchroniser un echange de donnees avec un organe distant
JP4278404B2 (ja) * 2003-02-24 2009-06-17 日立オムロンターミナルソリューションズ株式会社 携帯情報端末決済方法と携帯情報端末決済システム
US20050235167A1 (en) * 2004-04-16 2005-10-20 Harry Tiotantra Data streaming system with environment sensor
KR20050018895A (ko) * 2005-01-26 2005-02-28 백원모 네트워크 지불수단의 가치와 모바일 선불가치수단의 가치의 동기화와 동기화된 가치 사용방법 및 시스템
WO2011031768A2 (en) * 2009-09-08 2011-03-17 Cubic Corporation Association of contactless payment card primary account number
CN101799954B (zh) 2009-11-20 2012-08-08 飞天诚信科技股份有限公司 一种对双电子钱包进行圈存的方法
US20110258160A1 (en) * 2010-04-15 2011-10-20 Po-Yen Lee Data synchronization methods for synchronizing data in communication system and communication systems
US8523054B2 (en) * 2011-03-17 2013-09-03 Ebay Inc. Gift card conversion and digital wallet
US20130222583A1 (en) * 2012-02-28 2013-08-29 Research In Motion Limited System and Method for Obtaining Images from External Cameras Using a Mobile Device
AU2013266099A1 (en) * 2012-05-24 2015-01-22 Paypal, Inc. Method and systems for wallet enrollment
US9602848B2 (en) * 2013-03-04 2017-03-21 Comcast Cable Communications, Llc Optimized content delivery
US9922339B2 (en) * 2013-03-15 2018-03-20 Google Llc Randomized reward system for stored value transactions
WO2014205849A1 (zh) * 2013-06-29 2014-12-31 华为终端有限公司 非接触支付方法、设备和***
GB2518392A (en) 2013-09-19 2015-03-25 Visa Europe Ltd Account association systems and methods
US20150142657A1 (en) 2013-11-21 2015-05-21 Mastercard International Incorporated Linking physical card to virtual card account method and apparatus
JP2017168874A (ja) * 2014-08-05 2017-09-21 シャープ株式会社 端末装置、基地局装置、集積回路、および、無線通信方法
SG10201405789YA (en) 2014-09-16 2016-04-28 Smart Communications Inc System, method and apparatus for updating a stored value card
CN104392347B (zh) 2014-10-23 2017-12-12 中国建设银行股份有限公司 一种账户申请方法、创建方法、相关设备及***
WO2016076812A1 (en) 2014-11-14 2016-05-19 Gulay Berkin A method for displaying and topping up balance of nfc enabled units
US11657386B2 (en) 2015-08-21 2023-05-23 Samsung Electronics Co., Ltd. Reference-based card enrollment for secondary devices
CN105205659A (zh) * 2015-08-28 2015-12-30 深圳市雪球科技有限公司 移动支付装置及其移动支付方法、联机清算方法
JP6308986B2 (ja) * 2015-09-18 2018-04-11 株式会社日本総合研究所 現金払出制御システム、現金払出システム及びプログラム
CN106845975A (zh) 2015-12-05 2017-06-13 上海阿艾依智控***有限公司 基于射频识别卡及智能手机连动嵌入式续费装置及其方法
KR20160006652A (ko) * 2015-12-29 2016-01-19 주식회사 비즈모델라인 결제계좌와 결제수단 연계 방법
CN106134163B (zh) * 2016-06-22 2018-06-12 北京小米移动软件有限公司 信息显示方法、信息推送方法、装置及***

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101201956A (zh) * 2007-12-25 2008-06-18 侯万春 自动圈存pos和实现电子钱包ic卡自动圈存的***及方法
CN101252729A (zh) * 2008-04-10 2008-08-27 上海柯源软件有限公司 采用sim卡增强支付类芯片功能的方法
CN103577983A (zh) * 2013-11-25 2014-02-12 成都中联信通科技股份有限公司 一种脱机消费电子货币的圈存方法
CN105096452A (zh) * 2014-05-22 2015-11-25 中兴通讯股份有限公司 短距离通信终端、智能卡充值***及方法
CN105631657A (zh) * 2014-11-06 2016-06-01 深圳市千讯数据股份有限公司 一种基于非接触式移动支付终端的支付方法
CN105590202A (zh) * 2015-08-28 2016-05-18 ***股份有限公司 使用移动终端进行支付的方法和装置
CN107657448A (zh) * 2017-08-16 2018-02-02 阿里巴巴集团控股有限公司 一种账户创建、账户充值、数据同步方法及设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115118735A (zh) * 2022-06-08 2022-09-27 腾讯科技(深圳)有限公司 数据同步方法、群组管理方法、装置、设备及存储介质
CN115118735B (zh) * 2022-06-08 2023-12-01 腾讯科技(深圳)有限公司 数据同步方法、群组管理方法、装置、设备及存储介质

Also Published As

Publication number Publication date
AU2018317073A1 (en) 2019-10-31
US20200097947A1 (en) 2020-03-26
JP2020522038A (ja) 2020-07-27
CA3059627A1 (en) 2019-02-21
CN114663086A (zh) 2022-06-24
CN107657448B (zh) 2022-03-04
PH12019502426A1 (en) 2020-10-05
TW201911168A (zh) 2019-03-16
SG11201909626VA (en) 2019-11-28
KR102259714B1 (ko) 2021-06-03
EP3611684A1 (en) 2020-02-19
KR20190130142A (ko) 2019-11-21
CN107657448A (zh) 2018-02-02
JP6946461B2 (ja) 2021-10-06
CA3059627C (en) 2021-06-15
EP3611684A4 (en) 2020-05-06
US10902412B2 (en) 2021-01-26
MY191630A (en) 2022-07-04

Similar Documents

Publication Publication Date Title
WO2019033994A1 (zh) 一种账户创建、账户充值、数据同步方法及设备
US11836732B2 (en) Method and apparatus for offline payment, service processing, and payment processing
WO2019196543A1 (zh) 二维码图片获取方法、装置以及设备
KR102399908B1 (ko) 결제 방법, 장치 및 디바이스
WO2018103553A1 (zh) 信息交互方法及装置
JP2020522038A5 (zh)
KR20170118431A (ko) 전자 장치 및 이를 이용한 결제 방법
WO2019062691A1 (zh) 一种虚拟卡的开卡方法、***和支付***、发卡***
TW201926176A (zh) Nfc可攜式設備的寫入、支付方法、裝置以及設備
TW201931818A (zh) 電子憑證的傳輸方法、裝置及設備
WO2020093812A1 (zh) 移动支付方法及装置和电子设备
WO2019214305A1 (zh) 一种基于doi的支付方法、装置及设备
WO2020093826A1 (zh) 移动支付方法及装置和电子设备
WO2019137357A1 (zh) 付款码获取、支付请求响应方法、装置以及设备
KR20180000582A (ko) 결제 방법 및 이를 사용하는 전자 장치
CN111985919B (zh) 支付数据处理方法、装置及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18846030

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3059627

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2019556177

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20197030513

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018317073

Country of ref document: AU

Date of ref document: 20180810

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018846030

Country of ref document: EP

Effective date: 20191115

NENP Non-entry into the national phase

Ref country code: DE