AU2021311260B2 - Information processing method and apparatus, device and medium - Google Patents
Information processing method and apparatus, device and medium Download PDFInfo
- Publication number
- AU2021311260B2 AU2021311260B2 AU2021311260A AU2021311260A AU2021311260B2 AU 2021311260 B2 AU2021311260 B2 AU 2021311260B2 AU 2021311260 A AU2021311260 A AU 2021311260A AU 2021311260 A AU2021311260 A AU 2021311260A AU 2021311260 B2 AU2021311260 B2 AU 2021311260B2
- Authority
- AU
- Australia
- Prior art keywords
- target
- token
- state
- payment
- wearable device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000010365 information processing Effects 0.000 title claims abstract description 102
- 238000003672 processing method Methods 0.000 title claims abstract description 63
- 238000012508 change request Methods 0.000 claims abstract description 134
- 230000004044 response Effects 0.000 claims abstract description 36
- 230000004913 activation Effects 0.000 claims description 87
- 238000000034 method Methods 0.000 claims description 72
- 238000012545 processing Methods 0.000 claims description 31
- 230000002159 abnormal effect Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 12
- 230000008859 change Effects 0.000 abstract description 13
- 230000006870 function Effects 0.000 description 32
- 230000008569 process Effects 0.000 description 25
- 238000010586 diagram Methods 0.000 description 19
- 238000004891 communication Methods 0.000 description 11
- 230000003213 activating effect Effects 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
- G06Q20/3278—RFID or NFC payments by means of M-devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Multi-Process Working Machines And Systems (AREA)
- General Factory Administration (AREA)
Abstract
An information processing method and apparatus, a device and a medium.
The information processing method comprises: receiving a state change request sent by a target electronic device (S510); in response to the state change request, parsing the state change request, and obtaining state change request information which comprises a target payment token and a target payment state of a target wearable device, the target wearable device being a wearable device bound to the target electronic device and the target payment token being stored in a target security element of the target wearable device (S520); and updating a target token state corresponding to the target payment token to the target payment state, the target token state being used for determining, when a transaction request corresponding to the target payment token is received, whether a transaction corresponding to the transaction request is executed, the transaction request being generated according to the target payment token acquired from the target security element (S530).
The problem that a user cannot change the payment state of the wearable device after the wearable device is lost can thus be solved.
Description
[0001] This application claims priority to Chinese Patent Application No. 202010722517.7, filed on July 24, 2020 and entitled "INFORMATION PROCESSING METHOD, APPARATUS, DEVICE AND MEDIUM", which is hereby incorporated by reference in its
entirety.
[0002] The present application relates to the field of communication technology, and in
particular, to an information processing method, apparatus, device and a medium.
[0003] With the development of technology, the Near Field Communication (NFC) payment
function has gradually become a standard configuration of a wearable device. When a user is
shopping or taking public transportation, he or she only needs to bring the wearable device
close to a Point of Sale (POS) terminal or a credit card machine on public transportation, and
the payment may be completed in a short period of time.
[0004] Although the wearable device may be used by the user for performing payment operation more conveniently, the payment state of the wearable device cannot be changed by
the user after the wearable device is lost, which leads to the risk of the fraudulent use of the
bank account associated with the wearable device, thereby reducing the security of the user's
bank account.
[0005] The embodiments of the present disclosure provide an information processing method,
apparatus, device, and a medium, which may solve the problem that the payment state of the
wearable device cannot be changed by a user after the wearable device is lost.
[0006] In a first aspect, an embodiment of the present disclosure provides an information
processing method including: receiving a state change request sent by a target electronic device; parsing, in response to the state change request, the state change request to obtain state change request information, wherein the state change request information includes a target payment token and a target payment state for a target wearable device, and the target wearable device is a wearable device bound to the target electronic device and includes a target secure element having the target payment token stored therein; and updating a target token state corresponding to the target payment token to the target payment state, wherein when a transaction request corresponding to the target payment token is received, whether to perform a transaction corresponding to the transaction request is determined based on the target token state, and the transaction request is generated based on the target payment token obtained from the target secure element.
[0007] In a second aspect, an embodiment of the present disclosure provides an information processing method including: receiving a target payment state for a target wearable device
input by a user, wherein the target wearable device is in a bound state; searching a target
payment token corresponding to the target wearable device, wherein the target payment token
is a payment token stored in a target secure element of the target wearable device; generating
a state change request based on the target payment token and the target payment state; and
sending the state change request to a target server, wherein the state change request is to update
a target token state corresponding to the target payment token stored in the target server to the
target payment state, and when a transaction request corresponding to the target payment token
is received by the target server, whether to perform a transaction corresponding to the
transaction request is determined based on the target token state, and the transaction request is
generated based on the target payment token obtained from the target secure element.
[0008] In a third aspect, an embodiment of the present disclosure provides an information
processing apparatus including: a first receiving module configured to receive a state change
request sent by a target electronic device; a first parsing module configured to parse, in response
to the state change request, the state change request to obtain state change request information,
wherein the state change request information includes a target payment token and a target
payment state for a target wearable device, and the target wearable device is a wearable device
bound to the target electronic device and includes a target secure element having the target
payment token stored therein; and a first processing module configured to update a target token state corresponding to the target payment token to the target payment state, wherein when a transaction request corresponding to the target payment token is received, whether to perform a transaction corresponding to the transaction request is determined based on the target token state, and the transaction request is generated based on the target payment token obtained from the target secure element.
[0009] In a fourth aspect, an embodiment of the present disclosure provides an information
processing device including: a second receiving module configured to receive a target payment
state for a target wearable device input by a user, wherein the target wearable device is in a
bound state; a first searching module configured to search a target payment token
corresponding to the target wearable device, wherein the target payment token is a payment
token stored in a target secure element of the target wearable device; a second processing
module configured to generate a state change request based on the target payment token and
the target payment state; a first sending module configured to send the state change request to
a target server, wherein the state change request is to update a target token state corresponding
to the target payment token stored in the target server to the target payment state, and when a
transaction request corresponding to the target payment token is received by the target server,
whether to perform a transaction corresponding to the transaction request is determined based
on the target token state, and the transaction request is generated based on the target payment
token obtained from the target secure element.
[0010] In a fifth aspect, an embodiment of the present disclosure provides an information
processing device including: a processor and a memory having computer program instructions
stored thereon, wherein the computer program instructions, when executed by the processor,
cause the processor to implement the information processing method according to the first
aspect or the second aspect.
[0011] In a sixth aspect, an embodiment of the present disclosure provides a computer
readable storage medium having computer program instructions stored thereon, wherein the
computer program instructions, when executed by a processor cause, the processor to
implement the information processing method according to first aspect or the second aspect.
[0012] The information processing method, apparatus, device, and the medium of the
embodiments of the present disclosure may be able to: after receiving the state change request sent by the target electronic device, parse out the target payment token stored in the target secure element of the target wearable device bound to the target electronic device and the target payment state for the target wearable device from the state change request; and update the target token state corresponding to the target payment token to the target payment state, to indicate the target payment state for the target wearable device by the target token state corresponding to the target payment token. Thus, the updating of the target payment state for the target wearable device may be realized by way of updating the target token state corresponding to the target payment token. Then, when the transaction request generated based on the target payment token obtained from the target secure element of the target wearable device is received, whether to perform the transaction corresponding to the transaction request may be determined based on the target token state corresponding to the target payment token. Therefore, the payment state for the wearable device can be updated by the electronic device bound to the wearable device, the problem that the payment state for the wearable device cannot be changed by the user after the wearable device is lost can be avoided, the risk of the fraudulent use of the bank account associated with the wearable device can be reduced, and the security of the user's bank account can be improved.
[0013] In order to illustrate the technical solutions of the embodiments of the present application more clearly, the drawings required for the embodiments of the present application
will be briefly described. For a person skilled in the art, other drawings may also be obtained
from these drawings without any inventive effort.
[0014] Fig. 1 is an architectural diagram of an example of an information processing of an embodiment of an information processing method according to a first aspect of the present
disclosure;
[0015] Fig. 2 is an architectural diagram of an example of another information processing of
an embodiment of an information processing method according to the first aspect of the present
disclosure;
[0016] Fig. 3 is an architectural diagram of an example of yet another information processing
of an embodiment of an information processing method according to the first aspect of the present disclosure;
[0017] Fig. 4 is an architectural diagram of an example of yet another information processing of an embodiment of an information processing method according to the first aspect of the
present disclosure;
[0018] Fig. 5 is a schematic flowchart of an embodiment of an information processing method according to the first aspect of the present disclosure;
[0019] Fig. 6 is a schematic flowchart of another embodiment of an information processing method according to the first aspect of the present disclosure;
[0020] Fig.7 is a schematic flowchart of a process of activating a payment function of an embodiment of an information processing method of the first aspect of the present disclosure;
[0021] Fig.8 is a schematic flowchart of a process of modifying a bound payment card account number of an embodiment of an information processing method of the first aspect of the present
disclosure;
[0022] Fig.9 is a schematic flowchart of a process of unbounding a payment card account
number of an embodiment of an information processing method of the first aspect of the present
disclosure;
[0023] Fig.10 is a schematic structural diagram of an embodiment of an information processing
apparatus according to a second aspect of the present disclosure;
[0024] Fig.11 is a schematic structural diagram of another embodiment of an information
processing apparatus according to the second aspect of the present disclosure; and
[0025] Fig.12 is a schematic diagram of a hardware structure of an embodiment of an
information processing device according to a third aspect of the present disclosure.
[0026] The features and exemplary embodiments of various aspects of the present disclosure
will be described in detail below. In order to make the objects, technical solutions and
advantages of the present disclosure more clear, the present disclosure will be further described
in detail below with reference to the accompanying drawings and specific embodiments. It
should be understood that the specific embodiments described herein are only configured to
explain the present disclosure, and not to limit the present disclosure. It will be apparent to a person skilled in the art that the present disclosure may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present disclosure by illustrating examples of the present disclosure.
[0027] It should be noted that, in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or sequence existing between these entities or operations. Moreover, the terms "include", "comprise" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or device including a list of elements includes not only those elements, but also includes not explicitly listed other elements or elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "include" does not preclude the presence of additional identical elements in a process, method, article, or device that includes the element.
[0028] The information processing method provided by the present disclosure may be applied to the architectures as shown in Figs. 1 to 4, and will be described in detail with reference to Figs. 1 to 4.
[0029] Fig. 1 is an architectural diagram of an example of an information processing of an embodiment of an information processing method according to a first aspect of the present disclosure. As shown in Fig. 1, the architecture diagram may include at least one wearable device 110, at least one electronic device 120, at least one acquiring device 130, and a Token Service Provider (TSP) platform server 140.
[0030] An example of the wearable device 110 may be a portable device that may be worn by a user or integrated into the user's clothing or accessories, such as a smart bracelet, a smart watch, the smart sports shoes, the smart clothing, the smart glasses, a smart helmet, a smart ring, a smart accessory and so on, and the wearable device 110 has an NFC payment function. The electronic device 120 may be a device with a communication function, such as a mobile phone, a tablet computer, a desktop computer, a vehicle-mounted terminal and so on. The acquiring device 130 may be a mobile phone, a tablet computer, a point of sale (POS) terminal and so on, and the acquiring device 130 has an NFC information reading function. The TSP platform server 140 is configured to manage and verify payment tokens (Tokens), and the TSP platform server 140 may be a device with storage and computing functions such as a cloud server or a server cluster and so on.
[0031] Continuing to refer to Fig. 1, each electronic device 120 may be bound to and wirelessly communicate with the at least one wearable device 110, so that data transmission
between the electronic device 120 and its bound wearable device 110 may be performed
through wireless communication. In some embodiments, the wireless communication may be
short-range wireless communication, e.g., Bluetooth or Wireless Fidelity (WIFI). Each
electronic device 120 may further communicate with the TSP platform server 140, to cause the
TSP platform server 140 to change a token state corresponding to the payment token stored in
a secure element of the wearable device 110 bound to the electronic device, wherein there is a
one-to-one correspondence relationship between the payment token and the payment card
account number. Each acquiring device 130 may also communicate with the TSP platform
server 140, to send a transaction request carrying the payment token read from the wearable
device 110 to the TSP platform server 140, so that the TSP platform server 140 may verify the
payment token based on a payment state corresponding to the payment token, and determine
whether to perform a transaction corresponding to the transaction request based on the
verification result. In some embodiments, the payment token stored in the wearable device may
be a character string generated based on a payment card account number bound to the wearable
device.
[0032] In particular, the following will describe the specific method for the electronic device
120 to cause the TSP platform server 140 to change the token state corresponding to the
payment token stored in the secure element of the wearable device 110 bound to the electronic
device.
[0033] The electronic device 120 first receives the payment state for its bound specified
wearable device 110 input by the user, then searches the payment token stored in the secure
element of the specified wearable device 110, and then generates a state change request based
on the searched payment token and the payment state input by the user, and finally sends the
state change request to the TSP platform server 140.
[0034] After receiving the state change request sent by the electronic device 120, the TSP
platform server 140 may parse the received state change request to obtain the payment token and payment state carried in the state change request, and update the token state corresponding to the payment token carried in the state change request to the payment state carried in the state change request, and then when the transaction request generated based on the payment token carried in the state change request is received, determine whether to perform the transaction corresponding to the transaction request based on the token state corresponding to the payment token.
[0035] Therefore, in the information processing architecture shown in Fig. 1, the wearable device has the NFC payment function, and when the wearable device performs payment, the
acquiring device 130 may directly read the payment token stored in the wearable device, and
send the transaction request generated based on the payment token to the TSP platform server,
so that the TSP platform server determines whether to perform the transaction corresponding
to the transaction request based on the payment state corresponding to the payment token
carried in the transaction request. If it is determined to perform the transaction, the transaction
may be completed based on the payment token, such that the wearable device may realize the
payment function without being connected to the Internet.
[0036] In some embodiments of the present disclosure, the secure element may be an
embedded Secure Element (eSE) to improve the security of the payment token.
[0037] Fig. 2 is an architectural diagram of an example of another information processing of
an embodiment of an information processing method according to the first aspect of the present
disclosure. As shown in Fig. 2, the architecture diagram may include at least one wearable
device 110, at least one electronic device 120, at least one acquiring device 130, a TSP platform
server 140, an Internet financial platform server 150 and an acquiring platform server 160.
[0038] In some embodiments, the principles of the wearable device 110, the electronic device
120, the acquiring device 130, and the TSP platform server 140 are the same as those of the
embodiment shown in Fig. 1, which will not be repeated here.
[0039] The Internet financial platform server 150 may be configured to provide Internet
financial services, the acquiring platform server 160 may be configured to provide acquiring
services, and each of the Internet financial platform server 150 and the acquiring platform
server 160 may be a device with storage and computing functions such as a cloud server or a
server cluster and so on.
[0040] The electronic device 120 may be installed with afinancial application corresponding to an Internet financial platform, and the Internet financial platform may be a third-party
financial platform or a card organization platform. First, the payment state for the designated
wearable device 110 in a bound state may be input by the user on an application interface of
the financial application, and then the electronic device 120 may search the payment token
stored in the secure element of the designated wearable device 110 from the Internet financial
platform server 150, then generate the state change request based on the searched payment
token and the payment state input by the user, and finally send the state change request to the
TSP platform server 140 through the Internet financial platform server 150.
[0041] An acquiring application corresponding to an acquiring platform may be installed in the
acquiring device 130. The acquiring device 130 may read the payment token stored in the
secure element of the wearable device 110 through the acquiring application, and then send the
transaction request carrying the read payment token to the TSP platform server 140 through the
acquiring platform server 160.
[0042] Fig. 3 is an architectural diagram of an example of yet another information processing
of an embodiment of an information processing method according to the first aspect of the
present disclosure. As shown in Fig. 3, the architecture diagram may include at least one
wearable device 110, at least one electronic device 120, at least one acquiring device 130, a
TSP platform server 140, an Internet financial platform server 150, an acquiring platform server
160 and a Trusted Service Management (TSM) platform server 170.
[0043] In some embodiments, the principles of the wearable device 110, the electronic device 120, the acquiring device 130, the TSP platform server 140, the Internet financial platform
server 150 and the acquiring platform server 160 are the same as those of the embodiment
shown in Fig. 2, which will not be repeated here.
[0044] The TSM platform server 170 may be configured to implement secure forwarding of
information, and the TSM platform server 170 may be a device with storage and computing
functions such as a cloud server or a server cluster and so on. In particular, the TSM platform
server 170 may communicably connect with the TSP platform server 140 through a trusted
channel, so as to further improve the security of the information transmission.
[0045] Each of the intemet finance platform server 150 and the acquiring platform server 160 may communicate with the TSM platform server 170. The Internet finance platform server 150 may send the state change request to the TSM platform server 170, and then the TSM platform server 170 sends the state change request to the TSP platform server 140 through the trusted channel. The acquiring platform server 160 may send the transaction request to the TSM platform server 170, and then the TSM platform server 170 sends the transaction request to the
TSP platform server 140 through the trusted channel.
[0046] Fig. 4 is an architectural diagram of an example of yet another information processing of an embodiment of an information processing method according to the first aspect of the
present disclosure. As shown in Fig. 4, the architecture diagram may include at least one
wearable device 110, at least one electronic device 120, at least one acquiring device 130, a
TSP platform server 140, an Internet financial platform server 150, an acquiring platform server
160, a TSM platform server 170 and a card issuer server 180.
[0047] In some embodiments, the principles of the wearable device 110, the electronic device 120, the acquiring device 130, the TSP platform server 140, the Internet financial platform
server 150, the acquiring platform server 160 and the TSM platform server 170 are the same
as those of the embodiment shown in Fig. 3, which will not be repeated here.
[0048] In the case that the TSP platform server 140 determines to perform the transaction, the
TSP platform server 140 may obtain an acquiring device identification and a transaction
amount carried in the transaction request, search a payment card account number which is
stored in association with the payment token and is a payment account number bound to the
wearable device, and then send the obtained acquiring device identification, the transaction
amount and the payment account number to the card issuer server 180, so that the card issuer
server 180 completes the transaction corresponding to the transaction request by transferring
the transaction amount from the obtained payment account number to a payment account
corresponding to the acquiring device identification, and then feeds back a transaction
completion result to the TSP platform server 140, and the TSP platform server 140 may send
the transaction completion result to the acquiring device 130 through the TSM platform server
170 and the acquiring platform server 160 successively.
[0049] Alternatively, the payment card account number may be a physical payment card
account number or a virtual payment card account number. In some embodiments, the physical payment card account number may be a physical bank card account number, and the virtual payment card account number may be an electronic bank card account number.
[0050] Therefore, in the information processing architecture shown in Fig. 4, there is no need to pre-recharge the wearable device, and the transaction may be completed directly by using
the payment token through the bank card account corresponding to the bank account number
bound to the wearable device.
[0051] Based on the above architectures, the information processing method provided by the embodiments of the present disclosure will be described in detail below with reference to Figs.
to 9.
[0052] Fig. 5 is a schematic flowchart of an embodiment of an information processing method
according to the first aspect of the present disclosure.
[0053] In some embodiments of the present disclosure, the method shown in Fig. 5 may be
performed by any of the TSP platform servers 140 shown in Figs. 1 to 4.
[0054] As shown in Fig. 5, the information processing method may include S510, in which the
state change request sent by a target electronic device is received.
[0055] In some embodiments, the target electronic device may be any electronic device that is
communicably connected to the TSP platform server and is installed with the financial
application corresponding to the Internet financial platform.
[0056] The state change request is to request the TSP platform server to update a target token state corresponding to a target payment token designed by the user to a target payment state
designed by the user.
[0057] The target payment state may include any one of an activated state, a suspended state,
a loss reporting state, and an unbound state. The target payment state may be classified as a
normal state and an abnormal state. The abnormal state may include any one of the suspended
state, the loss reporting state and the unbound state, and the normal state may include the
activated state.
[0058] The activated state means that the NFC payment function of the wearable device has
been activated and is available. The suspended state means that the NFC payment function of
the wearable device has been activated and is in a suspended state. The loss reporting state
means that the NFC payment function of the wearable device has been activated and is in the loss reporting registration state. In the loss reporting state, the NFC payment function is suspended. The unbound state means that the NFC payment function of the wearable device has been activated and the wearable device is not bound to a payment card account number, and in the unbound state, the NFC payment function is also suspended.
[0059] In the embodiments of the present disclosure, the target electronic device may directly communicate with the TSP platform server, the target electronic device may communicate with
the TSP platform server through the Internet financial platform server, or the target electronic
device may communicate with the TSP platform server through the Internet financial platform
server and the TSM platform server successively, which is not limited here.
[0060] As shown in Fig. 5, the information processing method further includes S520, in which
in response to the state change request, the state change request is parsed to obtain state change
request information.
[0061] In some embodiments, the state change request information includes the target payment token and the target payment state for the target wearable device, and the target wearable device
is a wearable device bound to the target electronic device and includes the target secure element
having the target payment token stored therein.
[0062] In particular, the target wearable device is a wearable device whose payment state is to
be changed and designed by the user, and the target payment token is a payment token stored
in the target secure element of the target wearable device designed by the user
[0063] As shown in Fig. 5, the information processing method further includes S530, in which
the target token state corresponding to the target payment token is updated to the target payment
state.
[0064] When the transaction request corresponding to the target payment token is received,
whether to perform the transaction corresponding to the transaction request is determined based
on the target token state, and the transaction request is generated based on the target payment
token obtained from the target secure element.
[0065] In some embodiments of the present disclosure, the TSP platform server may store the
payment token and the token state corresponding to the payment token. For example, the TSP
platform server may add a state bit to the payment token, wherein the state bit is provided with
a state value representing a payment state, and different state values represent different payment states.
[0066] In these embodiments, alternatively, the TSP platform server may determine a target state value corresponding to the target payment state, and set the state bit of the target payment
token to the target state value, so as to realize the updating of the target token state
corresponding to the target payment token to the target payment state.
[0067] In other embodiments of the present disclosure, the payment token may be stored in
personalized data that may be stored in the TSP platform server, wherein the personalized data
may be provided with a state bit that may be provided with a state value representing a payment
state, and different state values represent different payment states.
[0068] In these embodiments, alternatively, the TSP platform server may determine the target
state value corresponding to the target payment state, and set the state bit in the target
personalized data to which the target payment token belongs to the target state value, so as to
realize the updating of the target token state corresponding to the target payment token to the
target payment state.
[0069] In some embodiments, the personalized data may be a personalized application
identifier (AID), which is composed of character strings. The personalized AID includes a
general character string, a payment token, and a state value. The payment token is also
composed of character strings, and the payment token and state value may be placed behind
the general character string.
[0070] For example, the general character string of the personalized AID may be: A000000333
010102 00 63020000 010000. The first 10 bits may be a fixed character string; the 1 th 1 to 1 6 th
bits may be to indicate a payment card type, such as 010101for a debit card type, 010102 for a
credit card type, and 010103 for a quasi-credit card type; 1 7 th to 1 8 th bits may indicate an
application type, such as 00 for a financial application, and 01 for non-financial application;
the 1 9 th to 2 6 th bits may be an institution code of an application provider; the 2 7th to 2 8 thbits
may be extension bits and corresponding functions may be customized; and the 2 9th to 3 2 thbits
may indicate a chip card type, such as 0000 for a PBOC2.0 type and 1000 for a PBOC3.0 type.
[0071] In the embodiments of the present disclosure, since each wearable device only stores a
payment token in the activated state, different wearable devices store different payment tokens
in the activated state, and the token state corresponding to the payment token is the same as the payment state, the TSP platform server may determine the payment state for the wearable device having the payment token stored in the secure element, based on the token state corresponding to the payment token, and then may determine whether to perform the transaction corresponding to the transaction request carrying the payment token, based on the payment state for the wearable device.
[0072] In the embodiment of the present disclosure, it is possible to: after receiving the state change request sent by the target electronic device, parse out the target payment token stored
in the target secure element of the target wearable device bound to the target electronic device
and the target payment state for the target wearable device from the state change request; and
update the target token state corresponding to the target payment token to the target payment
state, to indicate the target payment state for the target wearable device by the target token state
corresponding to the target payment token. Thus, the updating of the target payment state for
the target wearable device may be realized by way of updating the target token state
corresponding to the target payment token. Then, when the transaction request generated based
on the target payment token obtained from the target secure element of the target wearable
device is received, whether to perform the transaction corresponding to the transaction request
may be determined based on the target token state corresponding to the target payment token.
Therefore, the payment state for the wearable device can be updated by the electronic device
bound to the wearable device, the problem that the payment state for the wearable device cannot
be changed by the user after the wearable device is lost can be avoided, the risk of the fraudulent
use of the bank account associated with the wearable device can be reduced, and the security
of the user's bank account can be improved.
[0073] In another embodiment of the present disclosure, the information processing method
may further include:
receiving the transaction request sent by a target acquiring device, wherein the
transaction request is generated based on the target payment token obtained by the target
acquiring device from the target secure element;
parsing, in response to the transaction request, the transaction request to obtain
transaction request information including the target payment token;
searching the target token state corresponding to the target payment token; and refusing to perform the transaction corresponding to the transaction request under a condition that the target token state is an abnormal state.
[0074] In some embodiments, the target acquiring device may be any acquiring device that is communicably connected to the TSP platform server and installed with the acquiring
application corresponding to the acquiring platform.
[0075] In particular, when the target wearable device is used for payment by the user, the target payment token stored in the target secure element of the target wearable device may be read by
the target acquiring device, and the target acquiring device may generate the transaction request
based on the target payment token, an target acquiring device identification of the target
acquiring device and the transaction amount, and then send the transaction request to the TSP
platform server.
[0076] In some embodiments, the target acquiring device identification may be an Internet
Protocol (IP) address identified for the target acquiring device, or may be a device identity
document (ID) identified for the target acquiring device, and the device ID may be a device
identification code.
[0077] The TSP platform server may receive the transaction request sent by the target acquiring
device, and parse the transaction request to obtain the target payment token, the target acquiring
device identification and the transaction amount, and then search the target token state
corresponding to the target payment token. The TSP platform server may refuse to perform the
transaction corresponding to the transaction request under the condition that the target token
state is an abnormal state; or under the condition that the target token state is a normal state,
search the target payment card account number stored in association with the target payment
token, and send the target payment card account number, the target acquiring device
identification and the transaction amount to the card issuer server, so that the card issuer server
completes the transaction corresponding to the transaction request by transferring the
transaction amount from the target payment card account number to the payment card account
number corresponding to the target acquiring device identification, and then feeds back the
transaction completion result to the TSP platform server. After receiving the transaction
completion result, the TSP platform server may forward the transaction completion result to
the target acquiring device.
[0078] In the embodiments of the present disclosure, the target acquiring device may directly communicate with the TSP platform server, the target acquiring device may communicate with
the TSP platform server through the acquiring platform server, or the target acquiring device
may communicate with the TSP platform server through the acquiring platform server and the
TSM platform server successively, which is not limited here.
[0079] Therefore, after the wearable device is lost, the payment state for the wearable device
may be changed to the abnormal state by the user by changing the token state of the payment
token corresponding to the wearable device to the abnormal state, so that when the wearable
device is used for payment next time, the transaction may be refused to be performed by the
TSP platform server. Thus, the fraudulent use of the bank account associated with the wearable
device may be avoided, and the security of the user's bank account can be improved.
[0080] In some embodiments of the present disclosure, after refusing to perform the transaction
corresponding to the transaction request, the information processing method may further
include:
generating transaction feedback information corresponding to the transaction request
based on the target token state; and
sending the transaction feedback information to the target acquiring device.
[0081] In particular, the TSP platform server may generate the transaction feedback
information corresponding to the transaction request and carrying the target token state therein,
and then sends the transaction feedback information to the target acquiring device. After
receiving the transaction feedback information, the target acquiring device may display the
target token state carried by the transaction feedback information, so as to display the target
payment state for the target wearable device to the transaction-related person (payee or payer)
and inform the transaction related person the reason for the refusal of the transaction.
[0082] In yet another embodiment of the present disclosure, before S510, the information
processing method may further include:
receiving a token generating request sent by the target electronic device;
parsing, in response to the token generating request, the token generating request to
obtain token generating request information including a target payment card account
number; generating the target payment token based on the target payment card account number; and storing the target payment card account number and the target payment token by associating them with each other.
[0083] In particular, the TSP platform server may receive the token generating request sent by the target electronic device, and parse the token generating request to obtain the target payment
card account number, then generate the target payment token corresponding to the target
payment card account number, and store the target payment card account number and the target
payment token by associating them with each other.
[0084] In some embodiments, the TSP platform server may generate the target payment token
corresponding to the target payment card account number by using a preset token generating
method.
[0085] For example, the token generating method may encrypt all of the numbers in the target payment card account number by using a preset encryption algorithm to obtain an encrypted
character string as the target payment token. For another example, the token generating method
may encrypt a portion of the numbers in the target payment card account number by using a
preset encryption algorithm to obtain an encrypted character string, and splice the unencrypted
numbers in the target payment card account number and the encrypted character string to obtain
the target payment token.
[0086] Alternatively, after generating the target payment token, the information processing
method may further include:
sending the target payment token to the target electronic device, so that the target
electronic device sends the target payment token and an activation instruction
corresponding to the target payment token to the target wearable device, wherein the
activation instruction is to cause the target wearable device to load the target payment
token into target personalized data corresponding to the target payment token and stored
in the target secure element and to activate the loaded target payment token to the
activated state;
receiving an activation result sent by the target electronic device, wherein the activation
result is to indicate that the target wearable device has activated the target payment token loaded into the target personalized data to the activated state; and setting, in response to the activation result, the target token state corresponding to the target payment token to the activated state.
[0087] In particular, after generating the target payment token, the TSP platform server may send the target payment token to the target electronic device, so that the target electronic device determines an activation instruction corresponding to the target payment token, and sends the target payment token and the activation instruction corresponding to the target payment token to the target wearable device, to cause the target wearable device to load the target payment token into the target personalized data corresponding to the target payment token and stored in the target secure element and to activate the loaded target payment token to the activated state. After activating the target payment token loaded into the target personalized data to the activated state, the target wearable device may send the activation result indicating that the target wearable device has activated the target payment token loaded into the target personalized data to the activated state, to the TSP platform server through the target electronic device. After receiving the activation result sent by the target electronic device, the TSP platform server may set the target token state corresponding to the target payment token to the activated state, thereby making the NFC payment function of the target wearable device in the activated state.
[0088] The method for activating the target payment token by the target wearable device will be described in detail later.
[0089] Alternatively, sending the target payment token to the target electronic device may particularly include: sending the target payment card account number and the target payment token to the target electronic device, so that the target electronic device determines the target payment card account number to which the target payment token belongs, and then determines target wearable device bound to the target payment card account number, and determines the activation instruction corresponding to the target payment card type of the target payment card account number.
[0090] In some embodiments of the present disclosure, after storing the target payment card account number and the target payment token by associating them with each other, the information processing method may further include: receiving an account number change request sent by the target electronic device; parsing, in response to the account number change request, the account number change request to obtain account number change request information including the target payment token and a to-be-changed-to payment card account number; and storing the to-be-changed-to payment card account number as a new target payment card account number.
[0091] In particular, the TSP platform server may receive the account number change request sent by the target electronic device, and parse the account number change request to obtain the
target payment token stored in the target secure element of the target wearable device whose
payment card account number and bank account number are to be changed, and then replace
the existing target payment card account with the to-be-changed-to payment card account
number to store the to-be-changed-to payment card account number, so that the to-be-changed
to payment card account number is used as a new target payment card account number, the new
target payment card account number and the target payment token are stored by associating
them with each other, and the updating of the target bank account number stored in association
with target payment token in the TSP platform server can be completed.
[0092] In some embodiments, the association relationship between the target payment token
and the original target payment card account number may be released, and an association
relationship between a new target payment card account number and the target payment token
may be established. In other embodiments, the original target payment card account number
may be directly overwritten by the new target payment card account number.
[0093] In other embodiments of the present disclosure, after storing the target payment card
account number and the target payment token by associating them with each other, the
information processing method may further include:
receiving a token change request sent by the target electronic device;
parsing, in response to the token change request, the token change request to obtain token
change request information including a to-be-changed-to payment card account number;
generating a to-be-changed-to payment token based on the to-be-changed-to payment
card account number;
storing the to-be-changed-to payment card account number as a new target bank account number; and storing the to-be-changed-to payment token as a new target payment token.
[0094] In particular, the TSP platform server may receive the token change request sent by the target electronic device, and parse the token change request to obtain the to-be-changed-to payment card account number as the new target bank account number, generate the to-be changed-to payment token corresponding to the to-be-changed-to payment card account number as the new target payment token, and store the new target bank account number and the new target payment token by associating them with each other, to complete the updating of the payment card account number and the target payment token stored in the TSP platform server.
[0095] Alternatively, the original target payment card account number ever bound to the target wearable device and the target payment token corresponding to the original target payment card account number may be retained or deleted, which is not limited herein.
[0096] Alternatively, after using to-be-changed-to payment card account number as the new target payment card account number, the information processing method may further include: sending the target payment token to the target electronic device, so that the target electronic device sends the target payment token and an activation instruction corresponding to the target payment token to the target wearable device, wherein the activation instruction is to cause the target wearable device to load the target payment token into target personalized data corresponding to the target payment token and stored in the target secure element and to activate the loaded target payment token to an activated state; receiving an activation result sent by the target electronic device, wherein the activation result is to indicate that the target wearable device has activated the target payment token loaded into the target personalized data to the activated state; and setting, in response to the activation result, the target token state corresponding to the target payment token to the activated state, wherein the activated state is the normal state.
[0097] In particular, after generating the to-be-changed-to payment token and using it as the new target payment token, the TSP platform server may further send the target payment token to the target electronic device, so as to cause the target wearable device to activate the target payment token through the target electronic device, receive the activation result fed back by the target wearable device through the target electronic device, and set the token state corresponding to the target payment token to the activated state. As the particular process has been described in detail above, it will not be repeated here.
[0098] Fig. 6 is a schematic flowchart of another embodiment of an information processing method according to the first aspect of the present disclosure.
[0099] In some embodiments of the present disclosure, the method shown in Fig. 6 may be performed by any of the electronic devices 120 shown in Figs. 1 to 4.
[00100] As shown in Fig. 6, the information processing method may include S610, in which the target payment state for the target wearable device input by the user is received, wherein
the target wearable device is in a bound state.
[00101] Here, the target wearable device may be any wearable device bound to the electronic
device.
[00102] The electronic device may be installed with the financial application corresponding to
the Internet financial platform, the target payment state for the target wearable device may be
input by the user on the application interface of the financial application, and the target payment
state may be a payment state for the target wearable device intended to be changed to by the
user.
[00103] In particular, the target payment state may include any one of the activated state, the suspended state, the loss reporting state, and the unbound state. The target payment state may
be classified as the normal state and the abnormal state. The abnormal state may include any
one of the suspended state, the loss reporting state and the unbound state, and the normal state
may include the activated state.
[00104] As shown in Fig. 6, the information processing method further includes S620, in which
the target payment token corresponding to the target wearable device is searched.
[00105] In some embodiments, the target payment token is a payment token stored within the
target secure element of the target wearable device.
[00106] In some embodiments of the present disclosure, after a target wearable device is
selected by the user on the application interface of the financial application, the electronic
device may further search a target wearable device identification corresponding to the target wearable device from the locally stored wearable device identifications corresponding to at least one wearable device bound to the electronic device, and search the target payment token stored in the target secure element of the target wearable device based on the target wearable device identification.
[00107] In some embodiments, the wearable device identification may be an IP address of the wearable device, or may be a device ID of the wearable device, and the device ID may be a device identification code.
[00108] In some embodiments of the present disclosure, on the condition that the electronic device has locally stored at least one payment token, the electronic device may search the target payment token stored in association with the target wearable device identification from the locally stored at least one payment token.
[00109] In other embodiments of the present disclosure, on the condition that the electronic device does not locally store any payment token, the electronic device may generate a token search request based on the target wearable device identification, and send the token search request to a device for storing the payment token, so that the device, in response to the token search request, searches the target payment token stored in association with the target wearable device identification for the electronic device.
[00110] In some embodiments, on the condition that the electronic device directly communicates with the TSP platform server, the device for storing the payment token may be the TSP platform server.
[00111] In other embodiments, on the condition that the electronic device communicates with the TSP platform server through the Internet financial platform server, the device for storing the payment token may be the Internet financial platform server, that is, the Internet financial platform server may store, after receiving the target payment token sent by the TSP platform server, the target payment token.
[00112] Alternatively, the TSP platform server may further send the target bank account number together with the target payment token to the Internet financial platform server, to cause the Internet financial platform server to determine the target payment card account number to which the target payment token belongs, and store the target payment card account number and the target payment token by associating them with each other.
[00113] As shown in Fig. 6, the information processing method further includes S630, in which a state change request is generated based on the target payment token and the target payment
state.
[00114] In the embodiments of the present disclosure, the state change request generated based on the target payment token and the target payment state may be used for updating the target
token state corresponding to the target payment token to the target payment state.
[00115] As shown in Fig. 6, the information processing method further includes S640, in which the state change request is sent to a target server.
[00116] In some embodiments, the state change request is to update the target token state corresponding to the target payment token and stored in the target server to the target payment
state, and when the transaction request corresponding to the target payment token is received
by the target server, whether to perform the transaction corresponding to the transaction request
is determined based on the target token state, and the transaction request is generated based on
the target payment token obtained from the target secure element.
[00117] In particular, the target server may be any one of the TSP platform servers shown in
Figs. 1 to 4.
[00118] It should be noted that the method for updating the target token state corresponding to the target payment token to the target payment state by the target server and the method for
determining whether to perform the transaction corresponding to the transaction request by the
target server have been described above and will not be repeated here.
[00119] In the embodiment of the present disclosure, it is possible to: after receiving the target
payment state for the target wearable device in the bound state input by the user, generate the
state change request based on the target payment token stored in the target secure element of
the target wearable device and the target payment state for the target wearable device, and send
the state change request to the target server, to cause the target server to update the target token
state corresponding to the target payment token and stored in the target server to the target
payment state, to indicate the target payment state for the target wearable device by the target
token state of the target payment token. Thus, the updating of the target payment state for the
target wearable device may be realized by way of updating the target token state of the target
payment token. Then, when the transaction request corresponding to the target payment token is received, whether to perform the transaction corresponding to the transaction request may be determined based on the target token state corresponding to the target payment token.
Therefore, the target payment state for the target wearable device can be updated by the target
electronic device bound to the target wearable device, the problem that the payment state for
the wearable device cannot be changed by the user after the wearable device is lost can be
avoided, the risk of the fraudulent use of the bank account associated with the wearable device
can be reduced, and the security of the user's bank account can be improved.
[00120] In another embodiment of the present disclosure, before S610, the information
processing method may further include:
receiving the target payment card account number input by the user;
generating the token generating request based on the target payment card account
number; and
sending the token generating request to the target server, wherein the token generating
request is to cause the target server to generate the target payment token corresponding
to the target payment card account number.
[00121] When binding a target bank account number to the target wearable device, the target
payment card account number intended to be bound to the target wearable device may be input
by the user on the application interface of the financial application, and the electronic device
may generate the token generating request based on the target payment card account number,
and then send the token generating request to the TSP platform server, to cause the TSP
platform server to generate, in response to the token generating request, the target payment
token corresponding to target payment card account number.
[00122] In some embodiments, the method for generating the target payment token
corresponding to the target payment card account number by the TSP platform server has been
described above and will not be repeated here.
[00123] Therefore, the binding setting of the target wearable device and the target payment
card account number can be completed by the user.
[00124] Alternatively, after sending the token generating request to the target server, the
information processing method may further include:
receiving the target payment token sent by the target server; sending the target payment token and the activation instruction corresponding to the target payment token to the target wearable device, wherein the activation instruction is to cause the target wearable device to load the target payment token into the target personalized data corresponding to the target payment token and stored in the target secure element and to activate the loaded target payment token to an activated state; receiving the activation result sent by the target wearable device, wherein the activation result is to indicate that the target wearable device has activated the target payment token loaded into the target personalized data to the activated state; and sending the activation result to the target server.
[00125] After sending the token generating request to the TSP platform server, the electronic
device may receive the target payment token sent by the TSP platform server, and send the
target payment token to the target wearable device, to cause the target wearable device to load
the target payment token into the target personalized data stored within the target secure
element of the target wearable device and to activate the loaded target payment token. After
activating the target payment token loaded into the target personalized data to the activated
state, the target wearable device may feed the activation result back to the target electronic
device. After receiving the activation result fed back by the target wearable device, the
electronic device may forward the activation result to the TSP platform server, to cause the TSP
platform server to set the target token state corresponding to the target payment token to the
activated state.
[00126] Alternatively, the TSP platform server may further send the target payment card account number together with the target payment token to the electronic device, so that the
electronic device may determine the target payment card account number to which the target
payment token belongs.
[00127] In some embodiments, the target wearable device may store the target payment token
in the target personalized data, so that the acquiring device may read the target personalized
data and obtain the target payment token in the target personalized data.
[00128] Alternatively, before receiving the target payment card account number input by the
user, the information processing method may further include:
sending a plurality of sets of personalized data to the target wearable device, wherein each of the sets of the personalized data corresponds to a payment card type.
[00129] Correspondingly, before sending the target payment token and the activation instruction corresponding to the target payment token to the target wearable device, the
information processing method may further include:
obtaining a target payment card type of the target payment card account number
corresponding to the target payment token.
[00130] Correspondingly, sending the target payment token and the activation instruction corresponding to the target payment token to the target wearable device may include:
sending the target payment token and the activation instruction corresponding to the
target payment card type to the target wearable device;
[00131] In some embodiments, the target personalized data is personalized data corresponding to the target payment card type.
[00132] In particular, the electronic device may first perform Bluetooth pairing to the target wearable device to be bound to it, and send the plurality of sets of personalized data to the
target wearable device, wherein each of the sets of the personalized data corresponds to an
activation instruction. Then, the target payment card account number intended to be bound to
the target wearable device may be input by the user on the application interface of the financial
application, and the electronic device may generate the token generating request based on the
target payment card account number, then send the token generating request to the TSP
platform server, so that the TSP platform server may generate, in response to the token
generating request, the target payment token corresponding to the target payment card account
number. After sending the token generating request to the TSP platform server, the electronic
device may receive the target payment token sent by the TSP platform server, further obtain
the target payment card type of the target payment card account number corresponding to the
target payment token, search the activation instruction corresponding to the target payment
card type, and send the target payment token and the activation instruction corresponding to
the target payment token to the target wearable device, to cause the target wearable device to
load, in response to the activation instruction, the target payment token into the target
personalized data corresponding to the target payment card type and to activate the target
personalized data, thereby realizing the activating of the target payment token.
[00133] Alternatively, sending the plurality of sets of personalized data to the target wearable device may particularly include: sending the plurality of sets of personalized data and
personalized data activation program to the target wearable device. Therefore, after receiving
the activation instruction, the target wearable device may perform the activation operation by
the personalized data activation program, that is, loading the target payment token into the
target personalized data corresponding to the target bank card type and activating the target
personalized data by the personalized data activation program, thereby realizing the activating
of the target payment token..
[00134] Alternatively, before sending the plurality of sets of personalized data to the target wearable device, the information processing method may further include:
obtaining a storage state of the target secure element of the target wearable device;
on the condition that the storage state is a downloadable state, sending the plurality of
sets of personalized data to the target wearable device;
on the condition that the storage state is a full-load state, refusing to send the plurality of
sets of personalized data to the target wearable device.
[00135] In particular, the electronic device may obtain a full-load state value representing the
storage state of the target secure element, and determine the storage state of the target secure
element based on the full-load state value. In case that the full-load state value represents a full
load condition, it is determined that the storage state is the full-load state, and in case that the
full-load state value represents a non-full-load condition, it is determined that the storage state
is the downloadable state.
[00136] Therefore, the embodiments of the present disclosure may realize determining the
storage state of the target security element of the target wearable device, and the sending the
plurality of sets of personalized data to the target wearable device on the condition that the
target wearable device is in the downloadable state, which improves the reliability of activating
the NFC payment function of the target wearable device.
[00137] In some embodiments of the present disclosure, after sending the token generating
request to the target server, the information processing method may further include:
receiving a to-be-changed-to payment card account number input by the user;
searching the target payment token corresponding to the target wearable device; generating an account number change request based on the target payment token and the to-be-changed-to payment card account number; and sending the account number change request to the target server, wherein the account number change request is to cause the target server to store the to-be-changed-to payment card account number as a new target payment card account number.
[00138] When changing the bound payment card account number for the target wearable device, the to-be-changed-to payment card account number intended to be changed to by the
user for the target wearable device may be input by the user on the application interface of the
financial application, and the electronic device may generate the account number change
request based on the target payment token and the to-be-changed-to payment card account
number, and then send the account number change request to the TSP platform server, so that
the TSP platform server may change, in response to the account number change request, the
payment card account number stored in association with the target payment token.
[00139] In some embodiments, the method for changing the payment card account number
stored in association with the target payment token by the TSP platform server has been
described above and will not be repeated here.
[00140] Thus, the change setting of the payment card account number bound to the target
wearable device may be completed by the user.
[00141] Alternatively, before searching the target payment token corresponding to the target wearable device, the information processing method may further include:
obtaining a to-be-changed-to payment card type of the to-be-changed-to payment card
account number and a target payment card type of the target payment card account
number.
[00142] Correspondingly, searching the target payment token corresponding to the target
wearable device may particularly include:
searching the target payment token corresponding to the target wearable device under a
condition that the to-be-changed-to payment card type is the same as the target payment
card type.
[00143] When changing the bank account for the target wearable device, the to-be-changed-to
payment card type of the to-be-changed-to payment card account number intended to be changed to by the user may be the same as or different from the target payment card type of the target payment card account number having been bound to the target wearable device. As different payment card types correspond to different personalized data, it is necessary to obtain the to-be-changed-to payment card type of the to-be-changed-to payment card account number and the target payment card type of the target payment card account number first, then whether the to-be-changed-to payment card type is the same as the target payment card type may be determined, and if they are the same, the target payment token corresponding to the target wearable device may be searched, and the payment card account number stored in association with the target payment token in the TSP platform server may be directly changed to the to-be changed-to payment card account number.
[00144] Alternatively, after obtaining the to-be-changed-to payment card type corresponding to the to-be-changed-to payment card account number and the target payment card type
corresponding to the target payment card account number, the information processing method
may further include:
generating a token change request based on the to-be-changed-to payment card account
number under a condition that the to-be-changed-to payment card type is different from
the target payment card type; and
sending the token change request to the target server, wherein the token change request
is to cause the target server to generate a to-be-changed-to payment token corresponding
to the to-be-changed-to payment card account number, as a new target payment token,
and use the to-be-changed-to payment card account number under as a new target
payment card account number.
[00145] In particular, if the to-be-changed-to payment card type is different from the target
payment card type, the token change request may be generated based on the to-be-changed-to
payment card account number, and the token change request may be sent to the TSP platform
server, so that the TSP platform server may use the to-be-changed-to payment card account
number as a new target payment card account number, generate a new target payment token
corresponding to the new target payment card account number, and then feed the new target
payment token back to the electronic device.
[00146] In other embodiments of the present disclosure, after sending the token generating request to the target server, the information processing method may further include: receiving the to-be-changed-to payment card account number input by the user; generating an token change request based on the to-be-changed-to payment card account number; and sending the token change request to the target server, wherein the token change request is to cause the target server to generate the to-be-changed-to payment token corresponding to the to-be-changed-to payment card account number, as a new target payment token, and use the to-be-changed-to payment card account number under as a new target payment card account number.
[00147] In particular, regardless of whether the to-be-changed-to payment card type and the
target payment card type are the same, the electronic device may generate a token change
request based on the to-be-changed-to payment card account number, and send the token
change request to the TSP platform server, so that the TSP platform server will take the to-be
changed-to payment card account number as a new target payment card account number,
generate a new target payment token corresponding to the new target payment card account
number, and then feed the new target payment token back to the electronic device.
[00148] Alternatively, after sending the token change request to the target server, the
information processing method may further include:
receiving the target payment token sent by the target server;
sending the target payment token and an activation instruction corresponding to the
target payment token to the target wearable device, wherein the activation instruction is
to cause the target wearable device to load the target payment token into target
personalized data corresponding to the target payment token and stored in the target
secure element and to activate the loaded target payment token to an activated state;
receiving an activation result sent by the target wearable device, wherein the activation
result is to indicate that the target wearable device has activated the target payment token
loaded into the target personalized data to the activated state; and
sending the activation result to the target server.
[00149] After sending the token change request to the TSP platform server, the electronic
device may receive the new target payment token sent by the TSP platform server; send the new target payment token and the activation instruction corresponding to the new target payment token to the target wearable device, to cause the target wearable device to load the target payment token into the target personalized data corresponding to the target payment token and stored in the target secure element, and to activate the loaded target payment token to the activated state; then receive the activation result feedback from the target wearable device; and forward the activation result to the TSP platform server, so that the TSP platform server sets the target token state of the new target payment token to the activated state.
[00150] In some embodiments, under a condition that a payment card type of a new target
payment card account number bound to the target wearable device is the same as a payment
card type of the original target payment card account number, when loading the new target
payment token into target personalized data corresponding to the target payment token and
stored in the target secure element, the original target payment token may be directly
overwritten by the new target payment token.
[00151] In other embodiments, under a condition that a payment card type of a new target
payment card account number bound to the target wearable device is the different from a
payment card type of the original target payment card account number, after the target
personalized data and the new target payment token are activated, the original target
personalized data and the original target payment token should further be set to an un-activated
state or the original target payment token in the original target personalized data should be
deleted, such that only one target payment token in the activated state is present in the target
wearable devices.
[00152] The respective processes of the information processing according to the embodiments
of the present disclosure will be described in detail below by taking Fig. 7 to Fig. 9 as examples.
[00153] Fig.7 is a schematic flowchart of a process of activating a payment function of an
embodiment of an information processing method of the first aspect of the present disclosure.
As shown in Fig.7, the process of activating the payment function includes the following steps.
[00154] In S701, the application interface of the financial application is opened and a wearable
device to be activated a NFC payment function is selected by a user on the application interface
of the financial application, such that the electronic device and the wearable device complete
the Bluetooth pairing.
[00155] In S702, a full-load state value representing a storage state of the eSE is searched.
[00156] In S703, the full-load state value is received, and the storage state of the eSE is determined based on the full-load state value.
[00157] In S704, on the condition that the storage state is a downloadable state, loading data is sent to the eSE of the target wearable device, wherein the loading data includes two sets of
personalized data and the personalized data activation program, one set of personalized data
corresponding to the type of the credit card, and one set of personalized data corresponding to
the type of the debit card.
[00158] In S705, a bank card is selected by the user on the application interface as a default card to be bound to the wearable device, so that the electronic device obtains the bank card
account number corresponding to the default card, and generates a token generating request
based on the bank card account number.
[00159] In S706, the electronic device sends the token generating request to the Internet financial platform server.
[00160] In S707, the Internet financial platform server sends the token generating request to
the TSM platform server.
[00161] In S708, the TSM platform server sends the token generating request to the TSP
platform server.
[00162] In S709, the TSP platform server generates, in response to the token generating request, a payment token corresponding to the bank card account number, and stores the bank card
account number and the payment token by associating them with each other.
[00163] In S710, the TSP platform server sends the payment token corresponding to the bank
card account number to the TSM platform server.
[00164] In S711, the TSM platform server sends the payment token corresponding to the bank
card account number to the Internet financial platform server.
[00165] In S712, the Internet financial platform server stores the bank card account number
and the payment token by associating them with each other, and sends the payment token
corresponding to the bank card account number to the electronic device.
[00166] In S713, the electronic device sends the payment token and an activation instruction
corresponding to a bank card type of the default card to the wearable device.
[00167] In S714, the personalized data activation program in the eSE of the target wearable device executes the activation instruction, to write the payment token into the personalized data
corresponding to the bank card type, activate the personalized data to activate the payment
token, and send an activation result to electronic device after the activation is completed.
[00168] In S715, the electronic device sends the activation result to the Internet financial platform server.
[00169] In S716, the Internet financial platform server sends the activation result to the TSM platform server.
[00170] In S717, the TSM platform server sends the activation result to the TSP platform server.
[00171] In S718, the TSP platform server sets, in response to the activation result, a token state
of the payment token to the activated state.
[00172] In S719, the TSP platform server sends a setting result to the TSM platform server.
[00173] In S720, the TSM platform server sends the setting result to the Internet financial platform server.
[00174] In S721, the Internet financial platform server sends the setting result to the electronic
device.
[00175] In S722, the electronic device displays the setting result to notify the user that the NFC
payment function of the target wearable device is successfully activated.
[00176] Fig.8 is a schematic flowchart of a process of modifying a bound payment card account number of an embodiment of an information processing method of the first aspect of
the present disclosure. As shown in Figure 8, the process of modifying the binding payment
card account number includes the following steps.
[00177] In S801, a bank card is selected by the user on the application interface as anew default
card bound to the wearable device, so that the electronic device obtains a to-be-changed-to
bank card account number corresponding to the new default card, and generates a token change
request based on the to-be-changed-to bank card account number.
[00178] In S802, the electronic device sends the token change request to the Internet financial
platform server.
[00179] In S803, the Internet financial platform server sends the token change request to the
TSM platform server.
[00180] In S804, the TSM platform server sends the token change request to the TSP platform server.
[00181] In S805, the TSP platform server generates, in response to the token change request, a to-be-changed-to payment token corresponding to the to-be-changed-to bank card account
number, uses the to-be-changed-to bank card account number as a new bank card account
number, uses the to-be-changed-to payment token as a new payment token, and stores the new
bank card account number and the new payment token by associating them with each other.
[00182] In S806, the TSP platform server sends the new payment token corresponding to the
new bank card account number to the TSM platform server.
[00183] In S807, the TSM platform server sends the new payment token corresponding to the
new bank card account number to the Internet financial platform server.
[00184] In S808, the Internet financial platform server sends the new payment token
corresponding to the new bank card account number to the electronic device.
[00185] In S809, the electronic device sends the new payment token and an activation
instruction corresponding to a bank card type of the new default card to the wearable device.
[00186] In S810, the personalized data activation program in the eSE of the target wearable
device executes the activation instruction, to write the new payment token into the personalized
data corresponding to the bank card type, activate the personalized data to activate the new
payment token, and send an activation result to the electronic device after the activation is
completed.
[00187] In S811, the electronic device sends the activation result to the Internet financial
platform server.
[00188] In S812, the Internet financial platform server sends the activation result to the TSM
platform server.
[00189] In S813, the TSM platform server sends the activation result to the TSP platform server.
[00190] In S814, the TSP platform server sets, in response to the activation result, a token state
of the new payment token to an activated state.
[00191] In S815, the TSP platform server sends a setting result to the TSM platform server.
[00192] In S816, the TSM platform server sends the setting result to the Internet financial
platform server.
[00193] In S817, the Internet financial platform server sends the setting result to the electronic device.
[00194] In S818, the electronic device displays the setting result to notify the user that the default card is successfully updated.
[00195] Fig.9 is a schematic flowchart of a process of unbounding a payment card account number of an embodiment of an information processing method of the first aspect of the present
disclosure. As shown in Fig.9, the process of unbinding the payment card account number
includes the following steps.
[00196] In S901, an unbinding function for the wearable device is clicked by a user on the application interface, so that the electronic device searches a payment token stored in the secure
element of the wearable device, and generates an unbinding request corresponding to the
payment token.
[00197] In S902, the electronic device sends the unbinding request to the Internet financial
platform server.
[00198] In S903, the Internet financial platform server sends the unbinding request to the TSM
platform server.
[00199] In S904, the TSM platform server sends the unbinding request to the TSP platform
server.
[00200] In S905, the TSP platform server obtains, in response to the unbinding request, a to be-unbound payment token in the unbinding request, and updates a token state of the payment
token to an unbound state.
[00201] In S906, the TSP platform server sends an update result to the TSM platform server.
[00202] In S907, the TSM platform server sends the update result to the Internet financial
platform server.
[00203] In S908, the Internet financial platform server sends the update result to the electronic
device.
[00204] In S909, the electronic device displays the update result to notify the user that the
wearable device is successfully unbound. After the wearable device is successfully unbound,
if the TSP platform server receives a transaction request corresponding to the payment token
sent by the acquiring device, the TSP platform server may refuse to perform a transaction corresponding to the transaction request when the token state of the payment token is found to be the unbound state.
[00205] It should be noted that, the unbinding function may be clicked by the user, to update the token state of the payment token stored in the TSP platform server to the unbound state.
Further, a suspending function may be clicked by the user, to update the token state of the
payment token stored in the TSP platform server to a suspended state. A loss reporting function
may be clicked by the user, to update the token state of the payment token stored in the TSP
platform server to a loss reporting state. In particular, the process of suspending the NFC
payment function and the process of loss reporting the wearable device are similar to the
process of unbinding the wearable device and the payment card account, and will not be
repeated here.
[00206] In addition, after the token state of the payment token stored in the TSP platform server
is updated to the unbound state, the loss reporting state or the suspended state, a rebinding
function, a canceling of the loss reporting function or a recovery function may further be
clicked by the user, to re-update the token state of the payment token stored in the TSP platform
server to the activated state, of which the process is similar to the process of unbinding the
payment card account, and will not be repeated here.
[00207] Therefore, in the embodiments of the present disclosure, after the token state of the
payment token stored in the TSP platform server is changed, there is no need to change a token
state of the payment token in the wearable device, and there is no need to delete the payment
token in the wearable device, and when the wearable device is used for transaction, the
transaction may fail due to the token state of the payment token stored in the TSP platform
server, which enables a changing of the payment state of the wearable device under a condition
that the wearable device cannot communicate with the electronic device via Bluetooth.
[00208] Fig.10 is a schematic structural diagram of an embodiment of an information
processing apparatus according to a second aspect of the present disclosure.
[00209] In some embodiments of the present disclosure, the apparatus shown in Fig. 10 may
be any one of the TSP platform servers 140 shown in Figs. I to 4, or may be a functional module
in any one of the TSP platform servers 140 shown in Figs. 1 to 4.
[00210] As shown in Fig. 10, the information processing apparatus 1000 may include a first receiving module 1010, a first parsing module 1020 and a first processing module 1030.
[00211] The first receiving module 1010 is configured to receive a state change request sent
by a target electronic device.
[00212] The first parsing module 1020 is configured to parse, in response to the state change request, the state change request to obtain state change request information, wherein the state
change request information includes a target payment token and a target payment state for a
target wearable device, and the target wearable device is a wearable device bound to the target
electronic device and includes a target secure element having the target payment token stored
therein.
[00213] The first processing module 1030 is configured to update a target token state
corresponding to the target payment token to the target payment state, wherein when a
transaction request corresponding to the target payment token is received, whether to perform
a transaction corresponding to the transaction request is determined based on the target token
state, and the transaction request is generated based on the target payment token obtained from
the target secure element.
[00214] In the embodiment of the present disclosure, it is possible to: after receiving the state
change request sent by the target electronic device, parse out the target payment token stored
in the target secure element of the target wearable device bound to the target electronic device
and the target payment state for the target wearable device from the state change request; and
update the target token state corresponding to the target payment token to the target payment
state, to indicate the target payment state for the target wearable device by the target token state
corresponding to the target payment token. Thus, the updating of the target payment state for
the target wearable device may be realized by way of updating the target token state
corresponding to the target payment token. Then, when the transaction request generated based
on the target payment token obtained from the target secure element of the target wearable
device is received, whether to perform the transaction corresponding to the transaction request
may be determined based on the target token state corresponding to the target payment token.
Therefore, the payment state for the wearable device can be updated by the electronic device
bound to the wearable device, the problem that the payment state for the wearable device cannot
be changed by the user after the wearable device is lost can be avoided, the risk of the fraudulent use of the bank account associated with the wearable device can be reduced, and the security of the user's bank account can be improved.
[00215] In some embodiments of the present disclosure, the information processing apparatus 1000 may further include a third receiving module, a second parsing module and a second searching module and a third processing module.
[00216] The third receiving module is configured to receive the transaction request sent by a target acquiring device, wherein the transaction request is generated based on the target payment token obtained by the target acquiring device from the target secure element.
[00217] The second parsing module is configured to parse, in response to the transaction request, the transaction request to obtain transaction request information including the target payment token.
[00218] The second searching module is configured to search the target token state corresponding to the target payment token.
[00219] The third processing module is configured to refuse to perform the transaction corresponding to the transaction request under a condition that the target token state is an abnormal state.
[00220] In some embodiments of the present disclosure, the abnormal state may include any one of a suspended state, a loss reporting state and an unbound state.
[00221] In some embodiments of the present disclosure, the information processing apparatus 1000 may further include a fourth processing module and a second sending module.
[00222] The fourth processing module is configured to generate transaction feedback information corresponding to the transaction request based on the target token state.
[00223] The second sending module is configured to send the transaction feedback information to the target acquiring device.
[00224] In some embodiments of the present disclosure, the information processing apparatus 1000 may further include a fourth receiving module, a third parsing module, a fifth processing module and a first storage module.
[00225] The fourth receiving module is configured to receive a token generating request sent by the target electronic device.
[00226] The third parsing module is configured to parse, in response to the token generating request, the token generating request to obtain token generating request information including a target payment card account number.
[00227] The fifth processing module is configured to generate the target payment token based on the target payment card account number.
[00228] The first storage module is configured to store the target payment card account number and the target payment token by associating them with each other.
[00229] In some embodiments of the present disclosure, the information processing apparatus 1000 may further include a fifth receiving module, a fourth parsing module and a first update
module.
[00230] The fifth receiving module is configured to receive an account number change request
sent by the target electronic device.
[00231] The fourth parsing module is configured to parse, in response to the account number
change request, the account number change request to obtain account number change request
information including the target payment token and a to-be-changed-to payment card account
number.
[00232] The first update module is configured to store the to-be-changed-to payment card
account number as a new target payment card account number.
[00233] In some embodiments of the present disclosure, the information processing apparatus
1000 may further include a sixth receiving module, a fifth parsing module, a sixth processing
module, a second update module and a third update module.
[00234] The sixth receiving module is configured to receive a token change request sent by the
target electronic device.
[00235] The fifth parsing module is configured to parse, in response to the token change
request, the token change request to obtain token change request information including a to
be-changed-to payment card account number.
[00236] The sixth processing module is configured to generate a to-be-changed-to payment
token based on the to-be-changed-to payment card account number.
[00237] The second update module is configured to store the to-be-changed-to payment card
account number as a new target bank account number.
[00238] The third update module is configured to store the to-be-changed-to payment token as a new target payment token.
[00239] In some embodiments of the present disclosure, the information processing apparatus 1000 may further include a third sending module, a seventh receiving module and a fourth
update module.
[00240] The third sending module is configured to send the target payment token to the target electronic device, so that the target electronic device sends the target payment token and an
activation instruction corresponding to the target payment token to the target wearable device,
wherein the activation instruction is to cause the target wearable device to load the target
payment token into target personalized data corresponding to the target payment token and
stored in the target secure element and to activate the loaded target payment token to an
activated state.
[00241] The seventh receiving module is configured to receive an activation result sent by the
target electronic device, wherein the activation result is to indicate that the target wearable
device has activated the target payment token loaded into the target personalized data to the
activated state.
[00242] The fourth update module is configured to set, in response to the activation result, the
target token state corresponding to the target payment token to the activated state.
[00243] It should be noted that the information processing apparatus 1000 shown in Fig. 10
may execute the various steps in the method embodiments shown in Fig. 5, and realize the
various processes and effects in the method embodiments shown in Fig. 5, which will not be
repeated here.
[00244] Fig.11 is a schematic structural diagram of another embodiment of an information
processing apparatus according to the second aspect of the present disclosure.
[00245] In some embodiments of the present disclosure, the apparatus shown in Fig. 11 may
be any one of the electronic devices 110 shown in Figs. 1 to 4, or may be a functional module
in any one of the electronic devices 110 shown in Figs. 1 to 4.
[00246] As shown in Fig. 11, the information processing apparatus 1100 may include a second
receiving module 1110, a first searching module 1120, a second processing module 1130 and a
first sending module 1140.
[00247] The second receiving module 1110 is configured to receive a target payment state for a target wearable device input by a user, wherein the target wearable device is in a bound state.
[00248] The first searching module 1120 is configured to search a target payment token corresponding to the target wearable device, wherein the target payment token is a payment token stored in a target secure element of the target wearable device.
[00249] The second processing module 1130 is configured to generate a state change request based on the target payment token and the target payment state.
[00250] The first sending module 1140 is configured to send the state change request to a target server, wherein the state change request is to update a target token state corresponding to the target payment token and stored in the target server to the target payment state, and when a transaction request corresponding to the target payment token is received by the target server, whether to perform a transaction corresponding to the transaction request is determined based on the target token state, and the transaction request is generated based on the target payment token obtained from the target secure element.
[00251] In the embodiment of the present disclosure, it is possible to: after receiving the target payment state for the target wearable device in the bound state input by the user, generate the state change request based on the target payment token stored in the target secure element of the target wearable device and the target payment state for the target wearable device, and send the state change request to the target server, to cause the target server to update the target token state corresponding to the target payment token and stored in the target server to the target payment state, to indicate the target payment state for the target wearable device by the target token state of the target payment token. Thus, the updating of the target payment state for the target wearable device may be realized by way of updating the target token state of the target payment token. Then, when the transaction request corresponding to the target payment token is received, whether to perform the transaction corresponding to the transaction request may be determined based on the target token state corresponding to the target payment token. Therefore, the target payment state for the target wearable device can be updated by the target electronic device bound to the target wearable device, the problem that the payment state for the wearable device cannot be changed by the user after the wearable device is lost can be avoided, the risk of the fraudulent use of the bank account associated with the wearable device can be reduced, and the security of the user's bank account can be improved.
[00252] In some embodiments of the present disclosure, the target payment state may include any one of a suspended state, a loss reporting state and an unbound state.
[00253] In some embodiments of the present disclosure, the information processing apparatus 1100 may further include an eighth receiving module, a seventh processing module and a fourth
sending module.
[00254] The eighth receiving module is configured to receive a target payment card account
number input by the user.
[00255] The seventh processing module is configured to generate a token generating request
based on the target payment card account number.
[00256] The fourth sending module is configured to send the token generating request to the
target server, wherein the token generating request is to cause the target server to generate the
target payment token corresponding to the target payment card account number.
[00257] In some embodiments of the present disclosure, the information processing apparatus
1100 may further include a ninth receiving module, a third searching module, an eighth
processing module and a fifth sending module.
[00258] The ninth receiving module is configured to receive a to-be-changed-to payment card
account number input by the user.
[00259] The third searching module is configured to search the target payment token
corresponding to the target wearable device.
[00260] The eighth processing module is used to generate an account number change request
based on the target payment token and the to-be-changed-to payment card account number.
[00261] The fifth sending module is configured to send the account number change request to
the target server, wherein the account number change request is to cause the target server to
store the to-be-changed-to payment card account number as a new target payment card account
number.
[00262] In some embodiments of the present disclosure, the information processing apparatus
1100 may further include a first obtaining module.
[00263] The first obtaining module is configured to obtain a to-be-changed-to payment card
type of the to-be-changed-to payment card account number and a target payment card type of
the target payment card account number.
[00264] In some embodiments, the third searching module may be specifically configured to search the target payment token corresponding to the target wearable device under a condition
that the to-be-changed-to payment card type is the same as the target payment card type
[00265] In some embodiments of the present disclosure, the information processing apparatus 1100 may further include a ninth processing module and a sixth sending module.
[00266] The ninth processing module is configured to generate a token change request based
on the to-be-changed-to payment card account number under a condition that the to-be
changed-to payment card type is different from the target payment card type.
[00267] The sixth sending module is configured to send the token change request to the target server, wherein the token change request is to cause the target server to generate a to-be
changed-to payment token corresponding to the to-be-changed-to payment card account
number, as a new target payment token.
[00268] In some embodiments of the present disclosure, the information processing apparatus
1100 may further include a tenth receiving module, a seventh sending module, an eleventh
receiving module and an eighth sending module.
[00269] The tenth receiving module is configured to receive the target payment token sent by
the target server.
[00270] The seventh sending module is configured to send the target payment token and an
activation instruction corresponding to the target payment token to the target wearable device,
wherein the activation instruction is to cause the target wearable device to load the target
payment token into target personalized data corresponding to the target payment token and
stored in the target secure element and to activate the loaded target payment token to an
activated state.
[00271] The eleventh receiving module is configured to receive an activation result sent by the
target wearable device, wherein the activation result is to indicate that the target wearable
device has activated the target payment token loaded into the target personalized data to the
activated state.
[00272] The eighth sending module is configured to send the activation result to the target
server.
[00273] In some embodiments of the present disclosure, the information processing apparatus
1100 may further include a ninth sending module and a second obtaining module.
[00274] The ninth sending module is configured to send a plurality of sets of personalized data to the target wearable device, wherein each of the sets of the personalized data corresponds to a payment card type.
[00275] The second obtaining module is configured to obtain a target payment card type of the target payment card account number corresponding to the target payment token.
[00276] In some embodiments, the seventh sending module may be specifically configured to send the target payment token and the activation instruction corresponding to the target payment card type to the target wearable device.
[00277] In some embodiments, the target personalized data is personalized data corresponding to the target payment card type.
[00278] It should be noted that the information processing apparatus 1100 shown in Fig. 11 may execute the various steps in the method embodiments shown in Fig. 6 and realize the various processes and effects in the method embodiments shown in Fig.6, which will not be repeated here.
[00279] Fig.12 is a schematic diagram of a hardware structure of an embodiment of an information processing device according to a third aspect of the present disclosure.
[00280] The information processing device may include a processor 1201 and a memory 1202 on which computer program instructions are stored.
[00281] In particular, the above-mentioned processor 1201 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured as one or more integrated circuits implementing the embodiments of the present disclosure.
[00282] The memory 1202 may include a mass storage for data or instructions. By way of example and not limitation, the memory 1202 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of the above. For example, memory 1202 may include removable or non-removable (or fixed) media. For example, the memory 1202 may be inside or outside the information processing device. In particular embodiments, the memory 1202 is a non-volatile solid memory. In particular embodiments, the memory 1202 includes a read only memory (ROM). For example, the ROM may be a mask programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM) or a flash memory or a combination of two or more of the above.
[00283] The processor 1201 reads and executes the computer program instructions stored in the memory 1202 to implement any one of the information processing methods in the foregoing
embodiments.
[00284] In one example, the information processing device may further include a communication interface 1203 and a bus 1210. As shown in Fig. 12, the processor 1201, the
memory 1202, and the communication interface 1203 connect and communicate with one
another via the bus 1210.
[00285] The communication interface 1203 is mainly configured to implement communication among the modules, apparatuses, units and/or devices in the embodiments of the present
disclosure.
[00286] The bus 1210 includes hardware or software or both, which may couple the
components of the information processing device with one another. By way of example and
not limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus,
an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper
Transport (HT) interconnect, an Industry Standard Architecture (ISA) ) bus, an InfiniBand
Interconnect, a Low Pin Count (LPC) bus, a Memory Bus, a Microchannel Architecture (MCA)
bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial
Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association
Local (VLB) bus or other suitable bus or a combination of two or more of the above. For
example, the bus 1210 may include one or more buses. Although the embodiments of the
present application describe and illustrate the particular buses, the present application may
include any suitable bus or interconnect.
[00287] The information processing device may execute the information processing method in
the embodiments of the present disclosure, so as to implement the information processing
method and apparatus described in conjunction with Fig. 5 to Fig. 11.
[00288] Further, in combination with the information processing methods in the foregoing
embodiments, the embodiments of the present disclosure may further provide a computer readable storage medium. Computer program instructions are stored on the computer-readable storage medium, and the computer program instructions, when executed by the processor, cause the processor to implement the information processing method in any one of the foregoing embodiments. Examples of the computer-readable storage medium shown include a non-transitory computer-readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), magnetic disk or CD and so on.
[00289] It is to be understood that the present disclosure is not limited to the specific configurations and processes described above and illustrated in the figures. For the sake of brevity, the detailed descriptions of well-known methods are omitted here. In the above described embodiments, many specific steps are described and shown as examples. However, the process of the method of the present disclosure is not limited to the specific steps described and shown, and a person skilled in the art may make various changes, modifications and additions, or a change of the order of steps after understanding the spirit of the present disclosure.
[00290] The functional blocks shown in the above described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, the functional blocks may be, for example, electronic circuits, application specific integrated circuits (ASICs), suitable firmware, plug-ins, function cards, and the like. When implemented in software, the elements of the present disclosure are programs or code segments used to perform the required tasks. The program or code segments may be stored on a machine readable medium or transmitted over a transmission medium or communication link by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that may store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, and the like. The code segments may be downloaded via a computer network such as the Internet, an intranet.
[00291] It should further be noted that the exemplary embodiments mentioned in the present disclosure describe some methods or systems based on a series of steps or devices. However, the present disclosure is not limited to the order of the above steps, and the steps may be performed in the order mentioned in the embodiments, or in an order different from the order in the embodiments, or several steps may be performed simultaneously.
[00292] The above are only particular implementations of the present disclosure. A person skilled in the art may clearly understand that, for the convenience and brevity of the description, for the specific working process of the above-described systems, modules and units, a reference may be made to the corresponding process in the foregoing method embodiments, which will not be repeated here. It should be understood that the protection scope of the present disclosure is not limited to this, and a person skilled in the art may easily conceive of various equivalent modifications or replacements within the technical scope disclosed in the present disclosure, and these modifications or replacements should all be considered as within the scope of protection of the present disclosure.
[00293] The reference to any prior art in this specification is not, and should not be taken as, an acknowledgement or any form of suggestion that such prior art forms part of the common general knowledge.
[00294] It will be understood that the terms "comprise" and "include" and any of their derivatives (e.g. comprises, comprising, includes, including) as used in this specification, and the claims that follow, is to be taken to be inclusive of features to which the term refers, and is not meant to exclude the presence of any additional features unless otherwise stated or implied.
Claims (18)
1. An information processing method, comprising:
receiving a state change request sent by a target electronic device;
parsing, in response to the state change request, the state change request to obtain state
change request information, wherein the state change request information comprises a target
payment token and a target payment state for a target wearable device, and the target wearable
device is a wearable device bound to the target electronic device and comprises a target secure
element having the target payment token stored therein; and
updating a target token state corresponding to the target payment token to the target
payment state, wherein when a transaction request corresponding to the target payment token
is received, whether to perform a transaction corresponding to the transaction request is
determined based on the target token state, and the transaction request is generated based on
the target payment token obtained from the target secure element,
wherein the method further comprises:
receiving the transaction request sent by a target acquiring device, wherein the transaction
request is generated based on the target payment token obtained by the target acquiring device
from the target secure element;
parsing, in response to the transaction request, the transaction request to obtain transaction
request information comprising the target payment token;
searching the target token state corresponding to the target payment token; and
refusing to perform the transaction corresponding to the transaction request under a
condition that the target token state is an abnormal state,
wherein after refusing to perform the transaction corresponding to the transaction request,
the method further comprises:
generating transaction feedback information corresponding to the transaction request
based on the target token state; and
sending the transaction feedback information to the target acquiring device.
2. The method according to claim 1, wherein the abnormal state comprises any one of a suspended state, a loss reporting state and an unbound state.
3. The method according to claim 1, wherein before receiving the state change request sent by the target electronic device, the method further comprises: receiving a token generating request sent by the target electronic device; parsing, in response to the token generating request, the token generating request to obtain token generating request information comprising a target payment card account number; generating the target payment token based on the target payment card account number; and storing the target payment card account number and the target payment token by associating them with each other.
4. The method according to claim 3, wherein after storing the target payment card account number and the target payment token by associating them with each other, the method further comprises: receiving an account number change request sent by the target electronic device; parsing, in response to the account number change request, the account number change request to obtain account number change request information comprising the target payment token and a to-be-changed-to payment card account number; and storing the to-be-changed-to payment card account number as a new target payment card account number.
5. The method according to claim 4, wherein after storing the target payment card account number and the target payment token by associating them with each other, the method further comprises: receiving a token change request sent by the target electronic device; parsing, in response to the token change request, the token change request to obtain token change request information comprising a to-be-changed-to payment card account number; generating a to-be-changed-to payment token based on the to-be-changed-to payment card account number; storing the to-be-changed-to payment card account number as a new target bank account number; and storing the to-be-changed-to payment token as a new target payment token.
6. The method according to claim 3 or 5, further comprising:
sending the target payment token to the target electronic device, so that the target
electronic device sends the target payment token and an activation instruction corresponding
to the target payment token to the target wearable device, wherein the activation instruction is
to cause the target wearable device to load the target payment token into target personalized
data corresponding to the target payment token and stored in the target secure element and to
activate the loaded target payment token to an activated state;
receiving an activation result sent by the target electronic device, wherein the activation
result is to indicate that the target wearable device has activated the target payment token loaded
into the target personalized data to the activated state; and
setting, in response to the activation result, the target token state corresponding to the
target payment token to the activated state.
7. An information processing method, comprising:
receiving a target payment state for a target wearable device input by a user, wherein the
target wearable device is in a bound state;
searching a target payment token corresponding to the target wearable device, wherein the
target payment token is a payment token stored in a target secure element of the target wearable
device;
generating a state change request based on the target payment token and the target
payment state; and
sending the state change request to a target server, wherein the state change request is to
update a target token state corresponding to the target payment token and stored in the target
server to the target payment state, and when a transaction request corresponding to the target
payment token is received by the target server, whether to perform a transaction corresponding
to the transaction request is determined based on the target token state, and the transaction request is generated based on the target payment token obtained from the target secure element, wherein the target server receives the transaction request sent by a target acquiring device, wherein the transaction request is generated based on the target payment token obtained by the target acquiring device from the target secure element; the target server parses, in response to the transaction request, the transaction request to obtain transaction request information comprising the target payment token; the target server searches the target token state corresponding to the target payment token; and the target server refuses to perform the transaction corresponding to the transaction request under a condition that the target token state is an abnormal state, wherein after refusing to perform the transaction corresponding to the transaction request, the target server: generates transaction feedback information corresponding to the transaction request based on the target token state; and sends the transaction feedback information to the target acquiring device.
8. The method according to claim 7, wherein the target payment state comprises any one
of a suspended state, a loss reporting state and an unbound state.
9. The method according to claim 7, wherein before receiving the target payment state for
the target wearable device input by the user, the method further comprises:
receiving a target payment card account number input by the user;
generating a token generating request based on the target payment card account number;
and
sending the token generating request to the target server, wherein the token generating
request is to cause the target server to generate the target payment token corresponding to the
target payment card account number.
10. The method according to claim 9, wherein after sending the token generating request
to the target server, the method further comprises: receiving a to-be-changed-to payment card account number input by the user; searching the target payment token corresponding to the target wearable device; generating an account number change request based on the target payment token and the to-be-changed-to payment card account number; and sending the account number change request to the target server, wherein the account number change request is to cause the target server to store the to-be-changed-to payment card account number as a new target payment card account number.
11. The method according to claim 10, wherein before searching the target payment token
corresponding to the target wearable device, the method further comprises:
obtaining a to-be-changed-to payment card type of the to-be-changed-to payment card
account number and a target payment card type of the target payment card account number,
wherein searching the target payment token corresponding to the target wearable device
comprises:
searching the target payment token corresponding to the target wearable device under a
condition that the to-be-changed-to payment card type is the same as the target payment card
type.
12. The method according to claim 11, wherein after obtaining the to-be-changed-to
payment card type of the to-be-changed-to payment card account number and the target
payment card type of the target payment card account number, the method further comprises:
generating a token change request based on the to-be-changed-to payment card account
number under a condition that the to-be-changed-to payment card type is different from the
target payment card type; and
sending the token change request to the target server, wherein the token change request is
to cause the target server to generate a to-be-changed-to payment token corresponding to the
to-be-changed-to payment card account number, as a new target payment token.
13. The method according to claim 9 or 12, further comprising:
receiving the target payment token sent by the target server; sending the target payment token and an activation instruction corresponding to the target payment token to the target wearable device, wherein the activation instruction is to cause the target wearable device to load the target payment token into target personalized data corresponding to the target payment token and stored in the target secure element and to activate the loaded target payment token to an activated state; receiving an activation result sent by the target wearable device, wherein the activation result is to indicate that the target wearable device has activated the target payment token loaded into the target personalized data to the activated state; and sending the activation result to the target server.
14. The method according to claim 13, wherein,
before receiving the target payment card account number input by the user, the method
further comprises: sending a plurality of sets of personalized data to the target wearable device,
wherein each of the sets of the personalized data corresponds to a payment card type,
before sending the target payment token and the activation instruction corresponding to
the target payment token to the target wearable device, the method further comprises: obtaining
a target payment card type of the target payment card account number corresponding to the
target payment token,
sending the target payment token and the activation instruction corresponding to the target
payment token to the target wearable device comprises: sending the target payment token and
the activation instruction corresponding to the target payment card type to the target wearable
device, and
the target personalized data is personalized data corresponding to the target payment card
type.
15. An information processing apparatus, comprising:
a first receiving module configured to receive a state change request sent by a target
electronic device;
a first parsing module configured to parse, in response to the state change request, the
state change request to obtain state change request information, wherein the state change request information comprises a target payment token and a target payment state for a target wearable device, and the target wearable device is a wearable device bound to the target electronic device and comprises a target secure element having the target payment token stored therein; and a first processing module configured to update a target token state corresponding to the target payment token to the target payment state, wherein when a transaction request corresponding to the target payment token is received, whether to perform a transaction corresponding to the transaction request is determined based on the target token state, and the transaction request is generated based on the target payment token obtained from the target secure element, wherein the information processing apparatus further comprises: a third receiving module configured to receive the transaction request sent by a target acquiring device, wherein the transaction request is generated based on the target payment token obtained by the target acquiring device from the target secure element; a second parsing module configured to parse, in response to the transaction request, the transaction request to obtain transaction request information comprising the target payment token; a second searching module configured to search the target token state corresponding to the target payment token; and a third processing module configured to refuse to perform the transaction corresponding to the transaction request under a condition that the target token state is an abnormal state, wherein the information processing apparatus further comprises: a fourth processing module configured to generate transaction feedback information corresponding to the transaction request based on the target token state; and a second sending module configured to send the transaction feedback information to the target acquiring device.
16. An information processing device, comprising:
a second receiving module configured to receive a target payment state for a target
wearable device input by a user, wherein the target wearable device is in a bound state; a first searching module configured to search a target payment token corresponding to the target wearable device, wherein the target payment token is a payment token stored in a target secure element of the target wearable device; a second processing module configured to generate a state change request based on the target payment token and the target payment state; a first sending module configured to send the state change request to a target server, wherein the state change request is to update a target token state corresponding to the target payment token and stored in the target server to the target payment state, and when a transaction request corresponding to the target payment token is received by the target server, whether to perform a transaction corresponding to the transaction request is determined based on the target token state, and the transaction request is generated based on the target payment token obtained from the target secure element, wherein the target server receives the transaction request sent by a target acquiring device, wherein the transaction request is generated based on the target payment token obtained by the target acquiring device from the target secure element; the target server parses, in response to the transaction request, the transaction request to obtain transaction request information comprising the target payment token; the target server searches the target token state corresponding to the target payment token; and the target server refuses to perform the transaction corresponding to the transaction request under a condition that the target token state is an abnormal state, wherein after refusing to perform the transaction corresponding to the transaction request, the target server: generates transaction feedback information corresponding to the transaction request based on the target token state; and sends the transaction feedback information to the target acquiring device.
17. An information processing device comprising: a processor and a memory having
computer program instructions stored thereon,
wherein the computer program instructions, when executed by the processor, cause the processor to implement the information processing method according to any one of claims 1
14.
18. A computer-readable storage medium having computer program instructions stored
thereon, wherein the computer program instructions, when executed by a processor, cause the
processor to implement the information processing method according to any one of claims 1
14.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010722517.7A CN111932244B (en) | 2020-07-24 | 2020-07-24 | Information processing method, device, equipment and medium |
| CN202010722517.7 | 2020-07-24 | ||
| PCT/CN2021/073115 WO2022016843A1 (en) | 2020-07-24 | 2021-01-21 | Information processing method and apparatus, device and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| AU2021311260A1 AU2021311260A1 (en) | 2022-04-28 |
| AU2021311260B2 true AU2021311260B2 (en) | 2023-11-16 |
Family
ID=73315479
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU2021311260A Active AU2021311260B2 (en) | 2020-07-24 | 2021-01-21 | Information processing method and apparatus, device and medium |
Country Status (5)
| Country | Link |
|---|---|
| JP (1) | JP7432738B2 (en) |
| CN (1) | CN111932244B (en) |
| AU (1) | AU2021311260B2 (en) |
| TW (1) | TWI797638B (en) |
| WO (1) | WO2022016843A1 (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111932244B (en) * | 2020-07-24 | 2023-10-20 | 中国银联股份有限公司 | Information processing method, device, equipment and medium |
| CN112581123B (en) * | 2020-12-08 | 2024-02-23 | 中国银联股份有限公司 | Card management method, user terminal, server, system and storage medium |
| CN112232805B (en) * | 2020-12-15 | 2021-03-02 | 中国银联股份有限公司 | Card management method, user terminal, server, system, and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150312038A1 (en) * | 2014-04-23 | 2015-10-29 | Karthikeyan Palanisamy | Token security on a communication device |
| US20190311109A1 (en) * | 2018-04-06 | 2019-10-10 | The Toronto-Dominion Bank | Systems for enabling tokenized wearable devices |
Family Cites Families (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1991926A (en) * | 2005-12-30 | 2007-07-04 | 中兴通讯股份有限公司 | RFID mobile phone small payment loss register handling system and realization method |
| KR101948285B1 (en) * | 2012-08-17 | 2019-02-14 | 에스케이플래닛 주식회사 | System and Method for managing Secure Application Module of payment service |
| KR102460459B1 (en) * | 2015-02-27 | 2022-10-28 | 삼성전자주식회사 | Method and apparatus for providing card service using electronic device |
| US20170011399A1 (en) * | 2015-07-09 | 2017-01-12 | Hrb Innovations, Inc. | Rule-based locking and unlocking of payment accounts |
| WO2017039241A1 (en) * | 2015-08-28 | 2017-03-09 | Samsung Electronics Co., Ltd. | Payment information processing method and apparatus of electronic device |
| US20170061423A1 (en) * | 2015-09-01 | 2017-03-02 | Bank Of America Corporation | Use of wearable as an account control system |
| CN107220828B (en) * | 2016-03-22 | 2020-09-08 | 阿里巴巴集团控股有限公司 | Method, system and device for payment authorization and payment through wearable device |
| KR101805813B1 (en) * | 2016-06-16 | 2017-12-07 | 주식회사 마인드웨어p스 | a integrated payment service assistance apparatus |
| CN106656969A (en) * | 2016-10-13 | 2017-05-10 | 上海众人网络安全技术有限公司 | Payment state management method and system thereof, and network payment system |
| CN108269084A (en) * | 2017-01-03 | 2018-07-10 | 阿里巴巴集团控股有限公司 | A kind of method and device for progress barcode scanning payment on the mobile apparatus |
| CN111325536B (en) * | 2017-06-02 | 2024-02-23 | 口碑(上海)信息技术有限公司 | Payment method and device |
| CN107480995A (en) * | 2017-07-05 | 2017-12-15 | 深圳市科迈爱康科技有限公司 | Method of payment, wearable device and computer-readable recording medium based on gait |
| CN107392722B (en) * | 2017-07-27 | 2020-10-20 | 福建中金在线信息科技有限公司 | Order processing method and device, electronic equipment and storage medium |
| JP6972471B2 (en) * | 2018-07-04 | 2021-11-24 | 株式会社日本総合研究所 | User terminal device |
| CN111932244B (en) * | 2020-07-24 | 2023-10-20 | 中国银联股份有限公司 | Information processing method, device, equipment and medium |
-
2020
- 2020-07-24 CN CN202010722517.7A patent/CN111932244B/en active Active
-
2021
- 2021-01-21 WO PCT/CN2021/073115 patent/WO2022016843A1/en active Application Filing
- 2021-01-21 JP JP2022543428A patent/JP7432738B2/en active Active
- 2021-01-21 AU AU2021311260A patent/AU2021311260B2/en active Active
- 2021-06-09 TW TW110121103A patent/TWI797638B/en active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150312038A1 (en) * | 2014-04-23 | 2015-10-29 | Karthikeyan Palanisamy | Token security on a communication device |
| US20190311109A1 (en) * | 2018-04-06 | 2019-10-10 | The Toronto-Dominion Bank | Systems for enabling tokenized wearable devices |
Also Published As
| Publication number | Publication date |
|---|---|
| TWI797638B (en) | 2023-04-01 |
| WO2022016843A1 (en) | 2022-01-27 |
| JP7432738B2 (en) | 2024-02-16 |
| AU2021311260A1 (en) | 2022-04-28 |
| TW202205170A (en) | 2022-02-01 |
| JP2023512922A (en) | 2023-03-30 |
| CN111932244B (en) | 2023-10-20 |
| CN111932244A (en) | 2020-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2021311260B2 (en) | Information processing method and apparatus, device and medium | |
| US10223096B2 (en) | Logging operating system updates of a secure element of an electronic device | |
| JP7454052B2 (en) | Data processing methods, apparatus, devices and media | |
| US20200074465A1 (en) | Verification and provisioning of mobile payment applications | |
| US12033132B2 (en) | Mid-range reader interactions | |
| US9826341B2 (en) | Device content provisioning system | |
| KR20130128924A (en) | Apparatus and method for charging a product in a near field communication device | |
| CN112308555A (en) | Remote transaction system, method and point-of-sale terminal | |
| EP2976739B1 (en) | A method and system for transferring data | |
| CN113632124B (en) | System, method, and computer-readable medium for exchanging transaction data | |
| CN109345213A (en) | Transfer account method, device and the equipment of digital cash | |
| CA2919323C (en) | System and method for generating payment credentials | |
| US20240144258A1 (en) | System, Method, and Computer Program Product for Secure Client Device and Consumer Authentication | |
| CN118195616A (en) | Service processing method and related device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FGA | Letters patent sealed or granted (standard patent) |