Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
The embodiment of the specification provides a data processing system.
In this embodiment, the data processing system may include a first terminal. The first terminal may have a payment code generation function. The payment code can comprise a graphical code, a sound wave code and the like, and the graphical code can comprise a bar code, a two-dimensional code and the like. The first terminal may also have a short-range wireless communication function. The short-range wireless Communication may refer to Communication within a short distance, including but not limited to Bluetooth (Bluetooth), infrared (IrDA), wireless fidelity (WI-FI), Ultra Wide Band (Ultra Wide Band), violet peak (Zigbee), Near Field Communication (NFC), and the like. The first terminal can be a smart phone, a tablet electronic device, a portable computer, a Personal Digital Assistant (PDA), an intelligent wearable device and the like.
In this embodiment, the data processing system may further include a second terminal. The second terminal may have a payment code scanning function. The second terminal may also have a short-range wireless communication function. The second terminal may be a mobile device, such as a smart phone, a tablet electronic device, a portable computer, a Personal Digital Assistant (PDA), an in-vehicle device, a POS machine (e.g., a merchant POS machine, a public transit POS machine, etc.), or a smart wearable device. The second terminal may also be a desktop device, such as a server, an industrial personal computer (industrial control computer), a Personal Computer (PC), a kiosk, or a smart kiosk (kiosk) (e.g., subway kiosk, train ticket kiosk), etc. In one implementation of this embodiment, the second terminal may further have a speaker. The speaker may generate sound waves audible to a human.
In an implementation manner of this embodiment, the data processing system may further include a first server. The first server may be one server or a server cluster including a plurality of servers. The first server may be a server corresponding to the first terminal. For example, the first terminal may be a smart phone installed with a pay bank APP, and the first server may be a pay bank server.
In an implementation manner of this embodiment, the data set transmission system may further include a second server. The second server may be one server, or may be a server cluster including a plurality of servers. The second server may be a server corresponding to the second terminal. For example, the second terminal may be a public transportation POS, and the second server may be a server corresponding to the public transportation POS.
Please refer to fig. 1, fig. 2, fig. 5, fig. 6 and fig. 7. The embodiment of the specification provides a data processing method. The main body for implementing the data processing method may include a first terminal and a second terminal. To enable data transmission, the short-range wireless communication function of the first and second terminals may be in an on state. The data processing method may include the following steps.
Step S10: the first terminal generates a payment code.
In this embodiment, the payment code may include a graphical code, a sound wave code, and the like, and the graphical code may include a barcode, a two-dimensional code, and the like.
The payment code may include connection information. The connection information may include a connection identification of the first terminal. The connection identification may be used to establish a wireless communication connection. The connection identities may be the same or different depending on the wireless communication connection being established. For example, when establishing a wireless communication connection based on bluetooth technology, the connection identifier may be a physical address (MAC) of the first terminal. As another example, when establishing a wireless communication connection based on the wifi technology, the connection Identifier may be a Service Set Identifier (SSID) of the first terminal. Of course, when the wireless communication connection is established based on other technologies, the connection identifier may be other identifiers of the first terminal, which are not listed in sequence here.
The payment code may also include payment information. The payment information may include user identification information. The user identification information may be used to identify a user. The user identification information may be, for example, a user account, a code of a user account, or any other form of information from which a user account may be derived. The user account may be, for example, a pay account, a wechat account, a card number of a bus card, or a card number of a campus card. Of course, the payment information may also include other information, such as at least one of individual limits and time of failure. The single quota can be 10 yuan, 20 yuan or the like; the failure time may be, for example, 10: 30 points, 11: 15 points, or the like.
In this embodiment, the first terminal may generate the payment code after receiving the payment instruction.
The first terminal may have a payment key; the payment instruction may be generated upon detecting that the payment key is triggered. Where the payment key is triggered including, but not limited to, the payment key being pressed, clicked, double-clicked, swiped, pressed for more than a predetermined time, etc. The payment key may be a physical key, or a virtual key, etc., and the virtual key includes, but is not limited to, a button control, a graphic control, a text control, etc. Alternatively, the first terminal may be preset with a gesture operation. The gesture operation may include a touch trajectory on a display component (e.g., a touch-sensitive display). The first terminal may generate the payment instruction when recognizing the preset gesture operation. Alternatively, the first terminal may have a sensor. The sensor may be configured to sense a predetermined motion state, and may specifically include a gyroscope and/or an acceleration sensor. The first terminal may generate the payment instruction when sensing the preset motion state.
In this embodiment, the first terminal may obtain connection information and payment information; a payment code may be generated based on the obtained connection identification and payment information using a payment code generation algorithm.
According to the wireless communication connection type agreed by the first terminal and the second terminal in advance, the first terminal can obtain corresponding connection information. For example, when the pre-agreed wireless communication connection type is bluetooth, the first terminal may acquire its own physical address. As another example, when the predetermined wireless communication connection type is wireless fidelity, the first terminal may obtain a service set identifier of the first terminal.
The first terminal may obtain user identification information. For example, the first terminal may acquire a currently logged-in account or a historically logged-in account as the user identification information. As another example, the first terminal may obtain a card number of a bus card or a card number of a campus card as the user identification information. In an implementation manner of this embodiment, the first terminal may further obtain a single quota. Specifically, the first terminal may be preset with a single quota. The first terminal may obtain the preset single quota. Alternatively, the first server may have a single quota. The first terminal may send a data acquisition request to the first server. The first server may receive the data acquisition request, and may acquire and send the single quota to the first terminal. The first terminal may receive the single quota. In another implementation of this embodiment, the first terminal may further obtain an effective time of the payment code; the expiry time of the payment code may be calculated based on the current time and the validity time. The validity time of the payment code may come from the first terminal or the first server. Specifically, the first terminal may be preset with an effective time of the payment code. The first terminal may acquire the preset valid time. Alternatively, the first server may have a valid time for the payment code. The first terminal may send a data acquisition request to the first server. The first server may receive the data acquisition request, and may acquire and transmit the validity time to the first terminal. The first terminal may receive the validity time.
In this embodiment, the payment code generation algorithms may be the same or different depending on the generated payment code. For example, in generating the two-dimensional code, the payment code generation algorithm may be a Quick Response code (QRcode) algorithm. It will be appreciated by those skilled in the art that the fast reaction code algorithm herein is merely an example, and virtually any algorithm capable of generating a two-dimensional code may be applied herein. Of course, when generating other payment codes, the payment code generation algorithm may also be other algorithms, which are not listed in sequence here.
Step S12: the second terminal obtains the payment code.
In this embodiment, the user may perform a code swiping operation using the payment code generated by the first terminal. The second terminal may scan for the payment code. It should be understood by those skilled in the art that the second terminal may also obtain the payment code generated by the first terminal in other manners, which is not limited in this embodiment.
Step S14: the second terminal establishes wireless communication connection with the first terminal based on the connection identifier; and sending first prompt information to the first terminal based on the wireless communication connection.
In this embodiment, the second terminal may analyze the payment code to obtain the connection information and the payment information.
In this embodiment, the connection information may include a connection identifier of the first terminal. The first terminal may be regarded as a device requesting establishment of a wireless communication connection, and the second terminal may be understood as a device requested establishment of a wireless communication connection. The second terminal may establish a wireless communication connection with the first terminal based on the connection identification.
In this embodiment, the first prompt message may be used to prompt whether the payment is successful. Specifically, the first prompt message may include a prompt message that the payment is successful or a prompt message that the payment is failed. The prompt message of successful payment may include text, image, audio, video and any combination thereof. Further, the prompt message of successful payment may include the payment amount. The prompt message of payment failure may include text, image, audio, video and any combination thereof.
In this embodiment, after the second terminal analyzes the payment code, the second terminal may directly send a prompt message that the payment is successful to the first terminal. Or after the second terminal analyzes the payment code; the payment information can be verified; when the verification result is correct, prompt information of successful payment can be sent to the first terminal; and when the verification result is wrong, prompt information of payment failure can be sent to the first terminal.
For example, the payment information may include the time of failure. After the second terminal analyzes the payment code, the current time can be compared with the failure time; when the current time is less than or equal to the failure time, the verification result can be considered to be correct; and when the current time is greater than the failure time, the verification result can be considered as an error.
As another example, the payment information may include a single quota. After the second terminal analyzes the payment code, the payment amount can be determined; the payment amount may be compared to the single limit; when the payment amount is less than or equal to the single limit, the verification result can be considered to be correct; when the payment amount is larger than the single limit, the verification result can be considered as an error. The payment amount may be a preset default amount. Alternatively, the payment amount may be determined by the second terminal according to information input by the user. The information input by the user may include, for example, a destination station and the like. Still alternatively, the payment amount may be determined by the second terminal according to its current geographic location. For example, the second terminal may have a calculation rule. The second terminal can acquire the current geographic position of the second terminal; the payment amount may be calculated based on the obtained geographical location and the calculation rule.
Step S16: the first terminal receives the first prompt message based on wireless communication connection; and displaying the first prompt message.
In this embodiment, the first prompt message may include a prompt message that the payment is successful or a prompt message that the payment is unsuccessful. The first terminal can receive prompt information of successful payment or prompt information of failed payment; prompt information of successful payment or prompt information of failed payment can be displayed.
In one embodiment of this embodiment, the first server may have at least one digital signature data. The digital signature data can be obtained by carrying out signature based on a private key of an asymmetric encryption technology. The asymmetric encryption techniques include, but are not limited to, RSA algorithm, Elgamal algorithm, knapsack algorithm, ECC (elliptic Curve encryption algorithm), and the like. Each piece of digital signature data in the first server may correspond to a public key and a key identifier, the public key may be used to verify the digital signature data, and the key identifier may be used to identify the public key.
In this embodiment, the first terminal may obtain digital signature data and a key identifier corresponding to the digital signature data; a payment code may be generated based on the connection information, the payment information, the digital signature data, and the key identification.
The first server may issue at least one piece of digital signature data and a key identifier corresponding to the digital signature data to the first terminal. In this way, the first terminal may have a digital signature data set. The set of digital signature data may include at least one digital signature data, and each digital signature data may correspond to a key identification. In this way, the first terminal may obtain one piece of digital signature data and the key identifier corresponding to the digital signature data from the digital signature data set. Alternatively, the first terminal may send a data acquisition request to the first server. The first server may receive the data acquisition request; the digital signature data and the key identification corresponding to the digital signature data can be acquired and sent to the first terminal. The first terminal may receive the digital signature data and a key identifier corresponding to the digital signature data.
In this embodiment, the second terminal may obtain a payment code; the payment code can be analyzed to obtain connection information, payment information, digital signature data and a key identification; a public key of the key identification can be obtained as a target public key; the digital signature data may be verified using the target public key. Further, after the signature verification, the second terminal may send first prompt information to the first terminal. Specifically, after the signature verification is successful, the second terminal may send a prompt message that the payment is successful to the first terminal. After the signature verification fails, the second terminal may send a prompt message of payment failure to the first terminal.
The first server may issue a public key corresponding to at least one piece of digital signature data to the second terminal. In this way, the second terminal may have a set of public keys, which may include at least one public key. In this way, the second terminal may obtain, from the public key set, a public key corresponding to the key identifier as the target public key.
In one implementation of this embodiment, the second terminal may have a speaker. The second terminal may emit audible prompts using a speaker. Specifically, after the second terminal analyzes the payment code, the second terminal may directly use the speaker to send out a sound prompt message indicating that the payment is successful. Or after the second terminal analyzes the payment code; the payment information can be verified; when the verification result is correct, a speaker can be used for sending out sound prompt information of successful payment; when the verification result is error, a speaker can be used for sending out a sound prompt message of payment failure.
In one implementation of this embodiment, the second server may perform a deduction operation. In particular, the second terminal may determine a payment amount; the payment information and the payment amount may be sent to a second server. The second server may receive the payment information and the payment amount. The payment information may include a user identification, and the second server may then perform a deduction operation based on the user identification information and the payment amount. Alternatively, the first server may perform a deduction operation. Specifically, after receiving the payment information and the payment amount from the second terminal, the second server may send a deduction request to the first server, where the deduction request may carry the user identification information and the payment amount. The first server may receive the deduction request; a deduction operation may be performed based on the user identification information and the payment amount. Further, after executing the deduction operation, the first server may further send a second prompt message to the first terminal, where the second prompt message may include a prompt message that the deduction is successful. The first terminal may receive and display the second prompt message.
The second terminal may directly transmit payment information and a payment amount to the second server. Or, the second terminal may further send payment information and a payment amount to the second server after detecting the sending instruction. Wherein the transmission instruction may be automatically generated by the second terminal. For example, the second terminal may generate the transmission instruction at a preset timing. The preset time can be flexibly set according to actual needs, for example, 12 pm, 4 am, etc. As another example, the second terminal may further generate the sending instruction when detecting that its own network connection is available. Of course, the sending instruction may also be generated by a user active trigger. For example, the second terminal may have a send button, and the second terminal may in turn generate the send instruction upon detecting that the send button is triggered. Where the send button is triggered including, but not limited to, the send button being pressed, clicked, double-clicked, stroked, pressed for more than a predetermined time, etc. The sending key may be a physical key or a virtual key, and the like, and the virtual key includes, but is not limited to, a button control, a graphic control, a text control, and the like.
In this embodiment, the first terminal may generate a payment code; wherein, the payment code comprises connection information; the connection information includes a connection identifier of the first terminal. The second terminal may obtain the payment code; a wireless communication connection may be established with the first terminal based on the connection identification; first prompt information may be sent to the first terminal based on the wireless communication connection. The first terminal may receive the first prompt information based on the wireless communication connection; the first prompt may be presented. The first prompt message may be used to prompt whether the payment is successful. Therefore, through the first prompt message displayed by the first terminal, the user can conveniently judge whether the code swiping is successful or not, and the user experience is improved.
Please refer to fig. 3. The embodiment of the specification also provides another data processing method. The main body implementing the data processing method may include a first terminal. To enable data transmission, the short-range wireless communication function of the first terminal may be in an on state. The data processing method may include the following steps.
Step S20: a payment code is generated.
In this embodiment, the first terminal may generate the payment code after receiving the payment instruction.
Step S22: and under the condition that the wireless communication connection is established with the second terminal based on the connection identifier, receiving first prompt information sent by the second terminal based on the wireless communication connection.
In this embodiment, the first prompt message may be used to prompt whether the payment is successful. Specifically, the first prompt message may include a prompt message that the payment is successful or a prompt message that the payment is failed.
In this embodiment, the second terminal may obtain the payment code; the payment code can be analyzed to obtain connection information; a wireless communication connection can be established with the first terminal based on the connection identifier in the connection information; first prompt information may be sent to the first terminal based on the wireless communication connection. The first terminal may receive the first prompt message from the second terminal based on the wireless communication connection.
Step S24: and displaying the first prompt message.
In an implementation manner of this embodiment, the first terminal may obtain digital signature data and a key identifier corresponding to the digital signature data; a payment code may be generated based on the connection information, the payment information, the digital signature data, and the key identification.
In an implementation manner of this embodiment, the first terminal may receive a second prompt message sent by the first server; the second prompt may be presented. The second prompt message may include a prompt message that the deduction is successful.
In this embodiment, the first terminal may generate a payment code; under the condition that the wireless communication connection is established with the second terminal based on the connection identifier, first prompt information sent by the second terminal can be received based on the wireless communication connection; the first prompt may be presented. The first prompt message may be used to prompt whether the payment is successful. Therefore, through the first prompt message displayed by the first terminal, the user can conveniently judge whether the code swiping is successful or not, and the user experience is improved.
Please refer to fig. 4. The embodiment of the specification also provides another data processing method. The main body implementing the data processing method may include the second terminal. The short-range wireless communication function of the second terminal may be in an on state in order to enable data transmission. The data processing method may include the following steps.
Step S30: a payment code is obtained.
Step S32: and sending first prompt information to the first terminal based on the wireless communication connection under the condition of establishing the wireless communication connection with the first terminal based on the connection identifier.
In this embodiment, the first prompt message may be used to prompt whether the payment is successful. Specifically, the first prompt message may include a prompt message that the payment is successful or a prompt message that the payment is failed.
In this embodiment, the second terminal may analyze the payment code to obtain the connection information and the payment information. The connection information may include a connection identification of the first terminal. The first terminal may be regarded as a device requesting establishment of a wireless communication connection, and the second terminal may be understood as a device requested establishment of a wireless communication connection. The second terminal may establish a wireless communication connection with the first terminal based on the connection identification.
In this embodiment, after the second terminal analyzes the payment code, the second terminal may directly send a prompt message that the payment is successful to the first terminal. Or after the second terminal analyzes the payment code; the payment information can be verified; when the verification result is correct, prompt information of successful payment can be sent to the first terminal; and when the verification result is wrong, prompt information of payment failure can be sent to the first terminal.
In an implementation manner of this embodiment, the second terminal may obtain a payment code; the payment code can be analyzed to obtain connection information, payment information, digital signature data and a key identification; a public key of the key identification can be obtained as a target public key; the digital signature data may be verified using the target public key. Further, after the signature verification, the second terminal may send first prompt information to the first terminal. Specifically, after the signature verification is successful, the second terminal may send a prompt message that the payment is successful to the first terminal. After the signature verification fails, the second terminal may send a prompt message of payment failure to the first terminal.
In one implementation of this embodiment, the second terminal may have a speaker. The second terminal may emit audible prompts using a speaker.
In one implementation of this embodiment, the second terminal may determine a payment amount; the payment information and the payment amount may be sent to a second server. The second server may receive the payment information and the payment amount. The payment information may include user identification information, and the second server may perform a deduction operation based on the user identification information and the payment amount. Or, after receiving the payment information and the payment amount from the second terminal, the second server may further send a deduction request to the first server, where the deduction request may carry the user identification information and the payment amount. The first server may receive the deduction request; a deduction operation may be performed based on the user identification information and the payment amount.
In this embodiment, the second terminal may obtain the payment code; under the condition that wireless communication connection is established with a first terminal based on a connection identifier, first prompt information can be sent to the first terminal based on the wireless communication connection, so that the first terminal can display the first prompt information. The first prompt message may be used to prompt whether the payment is successful. Therefore, through the first prompt message displayed by the first terminal, the user can conveniently judge whether the code swiping is successful or not, and the user experience is improved.
Please refer to fig. 1, fig. 2, fig. 5, fig. 6 and fig. 7. An example of a scenario of an embodiment of the present specification is described below.
In this scenario embodiment, the data processing system may include a first terminal, a second terminal, a first server, and a second server. The first terminal may be a smartphone. The smart phone can be provided with a payment APP. The smart phone may have a bluetooth communication function, and the bluetooth communication function of the smart phone may be in an on state. The second terminal can be a public transportation POS machine. The bus POS machine can have a Bluetooth communication function, and the Bluetooth communication function of the bus POS machine can be in an open state. The public transit POS machine can also be provided with a loudspeaker. The first server may be a payroll server. The second server may be a server corresponding to the public transportation POS machine.
In this scenario embodiment, the payroll server may have at least one digital signature data. The digital signature data can be obtained by carrying out signature based on a private key of an asymmetric encryption technology. Each piece of digital signature data in the payment server may correspond to a public key and a key identifier, where the public key may be used to verify the digital signature data, and the key identifier may be used to identify the public key. The Payment treasure server can issue at least one piece of digital signature data and a key identification corresponding to the digital signature data to the smart phone. In this way, the smartphone may have a digital signature data set. The set of digital signature data may include at least one digital signature data, and each digital signature data may correspond to a key identification. The Payment server can also issue a public key corresponding to at least one piece of digital signature data to the public transportation POS machine. In this way, the public transit POS may have a set of public keys, which may include at least one public key.
In the scene embodiment, when a user needs to take a bus, the user can send a payment instruction to the smart phone. The smart phone can acquire connection information and payment information after receiving the payment instruction; acquiring digital signature data and a key identifier corresponding to the digital signature data from a digital signature data set; a payment code may be generated based on the connection information, the payment information, the acquired digital signature data, and the acquired key identification.
In the scene embodiment, the user can use the payment code to perform code swiping operation at the public transportation POS machine. The public transportation POS machine can obtain the payment code; the payment code may be parsed to obtain connection information, payment information, digital signature data, and a key identification.
The connection information may include a physical address of the smartphone. Therefore, the bus POS machine can establish Bluetooth communication connection with the smart phone by using the physical address in the connection information.
The public transport POS machine can also obtain a public key of the key identification from a public key set as a target public key; the digital signature data may be verified using the target public key. After the signature verification is successful, the bus POS machine can send prompt information of successful payment to the smart phone through the Bluetooth communication connection. Or after the signature verification fails, the public transportation POS machine can send prompt information of payment failure to the smart phone through the Bluetooth communication connection. The smart phone can receive prompt information of successful payment or prompt information of failed payment; prompt information of successful payment or prompt information of failed payment can be displayed. Therefore, the user can conveniently judge whether the code swiping is successful or not through the smart phone.
In addition, after the signature verification is successful, the bus POS machine can also determine the payment amount; the payment information and the payment amount may be sent to a second server. The second server may receive the payment information and the payment amount, and the payment information may include user identification information. The second server may then send a deduction request to the payer server, where the deduction request may carry the user identification information and the payment amount. The pay bank server may receive the deduction request; deduction operation can be carried out based on the user identification information and the payment amount; and sending a prompt message of successful deduction to the smart phone. The smart phone can receive and display the prompt message of successful deduction.
Please refer to fig. 8. The embodiment of the present specification provides a data processing apparatus, which includes a generating unit 40, a receiving unit 42, and a presenting unit 44.
A generating unit 40 for generating a payment code; wherein, the payment code comprises connection information; the connection information comprises a connection identifier of the first terminal;
a receiving unit 42, configured to receive, on a condition that a wireless communication connection is established with a second terminal based on the connection identifier, first prompt information sent by the second terminal based on the wireless communication connection; the first prompt message is used for prompting whether the payment is successful or not;
and the display unit 44 is used for displaying the first prompt message.
Please refer to fig. 9. The embodiment of the specification provides a terminal device which comprises a communication component, a display component and a processor.
In this embodiment, the communication component may be implemented in any suitable manner, for example, a wireless network card, a bluetooth module, an infrared transceiver module, an ultra-wideband communication module, a zigbee protocol communication module, and the like. The communication component may be used to establish a communication connection and perform data transmission.
In the present embodiment, the Display components include, but are not limited to, a Liquid Crystal Display (LCD) Display, a Cathode Ray Tube (CRT) Display, a Light Emitting Diode (LED) Display, and the like. The display component may be configured to present a first prompt.
In this embodiment, the processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth.
The processor may be operable to generate a payment code; wherein, the payment code comprises connection information; the connection information comprises a connection identifier of the first terminal; under the condition that wireless communication connection is established with a second terminal based on the connection identifier, receiving first prompt information sent by the second terminal based on the wireless communication connection; the first prompt message is used for prompting whether the payment is successful or not; and controlling the display component to display the first prompt message.
The specific functions of the terminal device, its communication component, display component and processor, which are disclosed in this embodiment, may be explained in contrast to the foregoing embodiments in this specification.
Please refer to fig. 10. A data processing apparatus includes an acquisition unit 50 and a transmission unit 52.
An acquisition unit 50 for acquiring a payment code; wherein, the payment code comprises connection information; the connection information comprises a connection identifier of the first terminal;
a sending unit 52, configured to send first prompt information to the first terminal based on the wireless communication connection under a condition that the wireless communication connection is established with the first terminal based on the connection identifier; the first prompt message is used for prompting whether the payment is successful or not.
Please refer to fig. 11. An embodiment of the present specification provides a terminal device, which includes a communication component and a processor.
In this embodiment, the communication component may be implemented in any suitable manner, for example, a wireless network card, a bluetooth module, an infrared transceiver module, an ultra-wideband communication module, a zigbee protocol communication module, and the like. The communication component may be used to establish a communication connection and perform data transmission.
In this embodiment, the processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth.
The processor may be configured to obtain a payment code; wherein, the payment code comprises connection information; the connection information comprises a connection identifier of the first terminal; under the condition that wireless communication connection is established with the first terminal based on the connection identifier, first prompt information is sent to the first terminal based on the wireless communication connection; the first prompt message is used for prompting whether the payment is successful or not.
In one implementation of this embodiment, the terminal device may further include a speaker that may generate sound waves audible to a human.
The specific functions of the terminal device, its communication components and processor implementation disclosed in this embodiment may be explained in contrast to the foregoing embodiments in this specification.
It should be noted that, in the present specification, each embodiment is described in a progressive manner, and the same or similar parts in each embodiment may be referred to each other, and each embodiment focuses on differences from other embodiments. Particularly, for the terminal device embodiment, since it is basically similar to the data processing method embodiment, the description is relatively simple, and for relevant points, reference may be made to partial description of the data processing method embodiment.
In addition, it is understood that one skilled in the art, after reading this specification document, may conceive of any combination of some or all of the embodiments listed in this specification without the need for inventive faculty, which combinations are also within the scope of the disclosure and protection of this specification.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate a dedicated integrated circuit chip 2. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardbyscript Description Language (vhr Description Language), and the like, which are currently used by Hardware compiler-software (Hardware Description Language-software). It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
From the above description of the embodiments, it is clear to those skilled in the art that the present specification can be implemented by software plus a necessary general hardware platform. Based on such understanding, the technical solutions of the present specification may be essentially or partially implemented in the form of software products, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The description is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
While the specification has been described with examples, those skilled in the art will appreciate that there are numerous variations and permutations of the specification that do not depart from the spirit of the specification, and it is intended that the appended claims include such variations and modifications that do not depart from the spirit of the specification.