Payment method and related device

Abstract

The invention provides a payment method and a related device, and the method comprises the steps: when an electronic device is in a PICC (Proximity Intelligent Card) mode, for example, the electronic device is in the PICC mode in an unlocked state, the electronic device receives a first carrier wave sent by a collection device in a PCD (Proximity Coupled Device) mode through NFC (Near Field Communication), and the first carrier wave has a first coding feature; and after receiving the first carrier wave, the electronic equipment opens a PCD mode, carries out NFC signaling interaction with the collection equipment, and completes payment by using the first payment application and the collection equipment. Thus, the electronic device in the PICC mode can complete payment of the payment application through NFC interaction, payment in a mode required by a user can be completed without excessive operation of the user, and the efficiency of payment by using the electronic device by the user is improved.

Description

[0001] This application is a divisional application. The application number of the original application is 202411985445.X, and the original application date is December 28, 2024. The entire content of the original application is incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a payment method and related devices. Background Art

[0003] Mobile payment is a payment method used by consumers of goods or services to pay for goods or services through electronic devices. Users use their electronic devices to send payment instructions to merchants and other mobile payment service providers via the internet, generating monetary payments and transferring funds, thus achieving mobile payment.

[0004] Currently, when users purchase goods or services offline at brick-and-mortar merchants, they typically complete payment using a QR code within a target payment app. There are two ways to use QR code payment: Method 1: The user must connect their electronic device to an internet connection and use the scanning function within the target payment app to scan the merchant's payment QR code within the target payment app to obtain the merchant's payment account information. After the target payment app on the electronic device obtains the merchant's payment account information, it can open the payment page. The target payment app's service platform can then deduct the purchase amount from the user's payment account and transfer it to the merchant's payment account to complete the payment. Method 2: The user can open the payment page within the target payment app and have the merchant's payment device scan the QR code within the payment page to obtain the user's payment account information. The target payment app's service platform can then deduct the purchase amount from the user's payment account and transfer it to the merchant's payment account to complete the payment. Using these QR code payment methods, users must complete payment multiple times, making the payment process complex and inefficient for users using electronic devices. Summary of the Invention

[0005] The present application discloses a payment method and related devices, which enable users to use an electronic device to approach the card swiping area of ​​a payment device and complete payment of a payment application through near-field communication (NFC) interaction. Without excessive user operations, the payment method required by the user can be completed, thereby improving the efficiency of users using electronic devices to make payments.

[0006] In a first aspect, the present application provides an NFC system, including an electronic device and a payment receiving device, wherein the payment receiving device is configured to send a first carrier wave via NFC when in a proximity coupling device (PCD) mode, where the first carrier wave has a first coding feature; the electronic device is configured to receive the first carrier wave sent by the payment receiving device in PCD mode via NFC when in a proximity smart card (PICC) mode (PCD mode is not turned on at this time, for example, the electronic device is in PICC mode by default after the NFC function is turned on); the electronic device is configured to turn on PCD mode after receiving the first carrier wave sent by the payment receiving device via NFC, perform NFC signaling interaction with the payment receiving device, and complete payment using a first payment application and the payment receiving device.

[0007] In some examples, the first carrier is an NFC signal sent at the physical layer. In other examples, the first carrier is an NFC signal sent at the access layer.

[0008] In some examples, the first carrier wave is not modulated and does not indicate information. In other examples, the first carrier wave is modulated and can indicate information, such as instructing the electronic device to turn on the PCD mode.

[0009] In the above system, after the electronic device in PICC mode receives the first carrier sent by the payment device in PCD mode, it can turn on the PCD mode to realize the target payment process with the payment device, wherein the target payment process is the process in which the electronic device uses the payment application and the payment device to complete the payment, and the target payment process is not the process in which the electronic device uses the NFC simulated card and the payment device to complete the payment. Therefore, when the user uses the electronic device in PICC mode to approach the card swiping area of ​​the payment device, regardless of whether the electronic device is in an unlocked state (for example, the screen is off) or an unlocked state, the electronic device and the payment device can complete the payment of the payment application through NFC interaction (that is, complete the target payment process), instead of using the NFC simulated card to complete the payment, and there is no need for the user to manually operate the electronic device (for example, unlock the electronic device and then approach the payment device). In this way, the electronic device can complete the payment method required by the user (corresponding to the target payment process) without excessive user operation, thereby improving the efficiency of the user's payment using the electronic device.

[0010] In one possible implementation, the electronic device is specifically configured to, after receiving a first carrier sent by a payment receiving device via NFC, turn on the PCD mode, perform NFC signaling interaction at the access layer with the payment receiving device, receive NFC tag data sent by the payment receiving device, the NFC tag data including identifiers of one or more payment applications supported by the payment receiving device (including an identifier of the first payment application), then determine the first payment application from the one or more payment applications based on the NFC tag data, and complete the payment using the first payment application and the payment receiving device.

[0011] In the above system, after the electronic device in PICC mode receives the first carrier sent by the payment device in PCD mode, it can perform the target payment process with the payment device, wherein the electronic device can receive the NFC tag data of the payment device and select the first payment application supported by the payment device and the payment device to complete the payment based on the NFC tag data, rather than arbitrarily selecting a payment application to pay, thereby ensuring the normal implementation of the target payment process, with higher fault tolerance and better feasibility.

[0012] In one possible implementation, the first payment application is a host-based card emulation (HCE) application, not a wallet application.

[0013] In the above system, after the electronic device in PICC mode receives the first carrier sent by the payment device in PCD mode, it can perform a target payment process with the payment device, wherein the electronic device can use the first payment application as an HCE application and the payment device to complete the payment, instead of using the wallet application and the payment device to complete the payment according to the default payment method of the electronic device in PICC mode. There are many payment applications as HCE applications. In this way, the target payment process can be applied in a wider range of scenarios and is more in line with user usage.

[0014] In one possible implementation, the payment device is further used to switch from PCD mode to PICC mode after sending the first carrier via NFC in PCD mode, for example, switching to PICC mode in a time-sharing manner; the electronic device is further used to generate a radio frequency field when in PCD mode after the PCD mode is turned on as mentioned above; the electronic device is further used to send a first response (for example, indicating successful identification of the first carrier) to the payment device in PICC mode via NFC in PCD mode after the payment device switched from PCD mode to PICC mode enters the radio frequency field of the electronic device, and then switch from PCD mode to PICC mode; the payment device is further used to switch from PICC mode to PCD mode after receiving the first response sent by the electronic device via NFC, and generate a radio frequency field when in PCD mode; the electronic device is specifically used to perform NFC signaling interaction with the payment device switched from PICC mode to PCD mode after switching from PCD mode to PICC mode, and complete payment using the first payment application and the payment device.

[0015] In some examples, the first response is an NFC signal sent at the physical layer. In other examples, the first response is an NFC signal sent at the access layer.

[0016] In some examples, the first response is not modulated and does not indicate information. In other examples, the first response is modulated and can indicate information, such as indicating that the electronic device successfully identified the first carrier.

[0017] In the above system, after a payment device in PCD mode transmits a first carrier wave, it can switch from PCD mode to PICC mode. After receiving the first carrier wave transmitted by the payment device in PCD mode, the electronic device in PICC mode can switch to PCD mode and switch from PICC mode to PCD mode. The payment device in PICC mode and the electronic device in PCD mode then transmit a first response, allowing the payment device to determine, based on the first response, that the electronic device also supports the target payment process. Subsequently, the payment device and the electronic device can switch modes again and proceed with the target payment process, avoiding situations where the payment device assumes the electronic device does not support the target payment process, preventing the target payment process from proceeding normally. The payment device and the electronic device switch modes before transmitting the first response, avoiding continued NFC signaling exchanges related to NFC emulation cards in the previous "old mode." By switching modes after transmitting the first response and then proceeding with the target payment process, rather than directly proceeding with the target payment process in the current mode after transmitting the first response, the payment device and the electronic device require minimal changes to the NFC signaling and internal device logic, improving feasibility.

[0018] In one possible implementation, the payment device is further used to switch from PCD mode to PICC mode after sending the first carrier via NFC in PCD mode, for example, switching to PICC mode in a time-sharing manner; the electronic device is further used to generate a radio frequency field when in PCD mode after the PCD mode is turned on as mentioned above; the electronic device is specifically used to perform NFC signaling interaction with the payment device switched from PCD mode to PICC mode in PCD mode after the payment device switched from PCD mode to PICC mode enters the radio frequency field of the electronic device, and complete payment using the first payment application and the payment device.

[0019] In the above system, after the payment device in PCD mode transmits the first carrier wave, it can switch from PCD mode to PICC mode. After the electronic device in PICC mode receives the first carrier wave sent by the payment device in PCD mode, it can turn on PCD mode and switch from PICC mode to PCD mode. Then, the payment device in PICC mode and the electronic device in PCD mode can perform the target payment process. The payment device and the electronic device change modes before performing the target payment process, avoiding the continuation of NFC signaling interactions related to the NFC simulated card in the previous "old mode". Instead of directly performing the target payment process in the current mode after transmitting the first carrier wave (which requires modifying a large number of NFC signals and internal device logic), the payment device in PICC mode and the electronic device in PCD mode can use the existing logic for the target payment process. This method requires less modification to the NFC signals and internal device logic, and is more feasible.

[0020] In one possible implementation, when the electronic device completes payment using a first payment application and a payment receiving device, it is specifically used to: send a first payment command to the payment receiving device, wherein the first payment command carries an identifier of the first payment application and an identifier of a first payment account, the first payment account is a payment account corresponding to the first payment application and the electronic device, and the first payment command is used to request the payment receiving device to execute a payment process; the payment receiving device is further used to send payment information to the cloud server after receiving the first payment command sent by the electronic device, wherein the payment information includes the payment amount, the identifier of the first payment account and the identifier of the first payment account, the first payment account is a payment account corresponding to the first payment application and the payment device, and the payment information is used to request the cloud server to transfer the payment amount from the first payment account to the first payment account; the payment receiving device is also used to receive a first payment response sent by the cloud server, and then send a first payment response to the electronic device, wherein the first payment response carries a payment result.

[0021] In some examples, the electronic device may not be connected to the Internet when completing the payment using the first payment application and the payment device.

[0022] In the above system, when an electronic device completes payment using the first payment application and the payment receiving device, the payment receiving device and the cloud server can interact without the need for the electronic device to interact with the cloud service, and the electronic device does not need to be connected to the Internet. Therefore, the user does not need to manually turn on the Internet switch of the electronic device, further improving the efficiency of the user's payment using the electronic device.

[0023] In one possible implementation, the electronic device is specifically configured to receive a first carrier wave transmitted by a payment device in PCD mode via NFC while in an unlocked state and in PICC mode, and then enable PCD mode. For example, the electronic device is a mobile phone, tablet computer, or smart home device such as a smart screen.

[0024] In the above system, the user can place an unlocked electronic device close to the card swiping area of ​​the payment device and complete the payment of the payment application through NFC interaction. The user does not need to manually unlock the electronic device and then place it close to the card swiping area of ​​the payment device. In this way, the electronic device can complete the payment method required by the user without too much operation from the user, thereby improving the efficiency of the user's payment using the electronic device.

[0025] In one possible implementation, the electronic device is specifically configured to receive a first carrier wave transmitted by a payment device in PCD mode via NFC when in an unlocked or unlocked state and in PICC mode, and then enable PCD mode. The electronic device is a power-sensitive device, such as a wearable device such as a smart bracelet, smart watch, or smart glasses.

[0026] In the above system, the user can place the wearable device close to the card swiping area of ​​the payment device and complete the payment of the payment application through NFC interaction. The user does not need to manually turn on the PCD mode of the wearable device and then place it close to the card swiping area of ​​the payment device. In this way, the electronic device can complete the payment method required by the user without too much operation from the user, thereby improving the efficiency of the user's payment using the electronic device.

[0027] In one possible implementation, the electronic device is further configured to deactivate PCD mode and enter PICC mode after completing payment using the first payment application and the payment receiving device. For example, after a user places an unlocked electronic device near the card swipe area of ​​the payment receiving device, the electronic device can switch to an unlocked state to complete payment with the payment application through NFC interaction. After the payment is completed, the electronic device can automatically return to an unlocked state to reduce power consumption.

[0028] In the above system, after the electronic device turns on the PCD mode and the payment device completes the target payment process, the PCD mode can be automatically turned off instead of keeping the PCD mode on, which effectively reduces power consumption and improves device availability.

[0029] In one possible implementation, the payment device is used to send a first card search request to the electronic device that has switched from PCD mode to PICC mode via NFC after switching from PICC mode to PCD mode, wherein the first card search request is used to indicate that the payment device supports the first NFC protocol, and the first card search request is different from the first carrier; the electronic device is used to send a first card search response to the payment device via NFC after receiving the first card search request sent by the payment device via NFC, wherein the first card search response is used to indicate that the electronic device supports the first NFC protocol; the payment device is used to send an identifier of one or more payment applications supported by the payment device to the electronic device after receiving the first card search response sent by the electronic device via NFC; the electronic device is used to determine a first payment application from one or more payment applications, and complete payment using the first payment application and the payment device.

[0030] In the above system, after the payment device switches to PCD mode, it can send a first card search request to the electronic device switched to PICC mode. The first card search request is different from the first carrier. The first card search request is used to implement normal NFC signaling interaction at the access layer. Therefore, the electronic device can normally return the first card search response, thereby completing the target payment process with the payment device. In other words, the payment device in PCD mode automatically sends the first carrier or the first card search request in different scenarios to ensure the normal progress of the target payment process, eliminating the need for manual operation of the payment device and improving payment efficiency.

[0031] In one possible implementation, the carrier wave corresponding to the first card search request is modulated, and the first carrier wave is unmodulated. In this way, the electronic device can distinguish the first card search request from the first carrier wave without any analysis, further improving payment efficiency.

[0032] In one possible implementation, the electronic device is configured not to start the wallet application of the electronic device after receiving a first carrier sent by a payment device via NFC; the electronic device is configured not to start the wallet application of the electronic device after receiving a first card search request sent by a payment device via NFC.

[0033] In the above system, after the electronic device in PICC mode receives the first carrier wave, it will not use the wallet application and the payment device to complete the payment according to the electronic device's default payment method in PICC mode, and therefore will not start the wallet application. Furthermore, after the electronic device receives the first carrier wave and subsequently receives the first card search request in PICC mode, it will not use the wallet application and the payment device to complete the payment according to the electronic device's default payment method in PICC mode, and therefore will not start the wallet application. This ensures that the electronic device can complete the target payment process with the payment device, avoids unnecessary power consumption from starting and running the wallet application, and improves feasibility.

[0034] In one possible implementation, the first carrier includes N subcarriers, and the first coding feature of the first carrier includes one or more of the following: the amplitude of each subcarrier in the N subcarriers is a preset first amplitude, the duration of each subcarrier in the N subcarriers is a first duration, the time interval between two adjacent subcarriers in the N subcarriers is a preset first time interval, and N is a preset value, where N is a positive integer greater than 1.

[0035] In the above system, the first coding feature of the first carrier can be implemented in various ways and can be applied to various scenarios. For example, the first coding feature can be determined based on the type and features of the electronic device and the payment device, which is more feasible.

[0036] In the second aspect, the present application provides a payment method applied to an electronic device, the method comprising: when in PICC mode (PCD mode is not turned on at this time, for example, the electronic device is in PICC mode by default after the NFC function is turned on), receiving a first carrier sent by a payment receiving device in PCD mode via NFC, wherein the first carrier has a first coding feature; after receiving the first carrier sent by the payment receiving device via NFC, turning on the PCD mode, performing NFC signaling interaction with the payment receiving device, and using the first payment application and the payment receiving device to complete the payment.

[0037] In some examples, the first carrier is an NFC signal sent at the physical layer. In other examples, the first carrier is an NFC signal sent at the access layer.

[0038] In some examples, the first carrier wave is not modulated and does not indicate information. In other examples, the first carrier wave is modulated and can indicate information, such as instructing the electronic device to turn on the PCD mode.

[0039] In the above method, after the electronic device in PICC mode receives the first carrier sent by the payment device in PCD mode, it can turn on the PCD mode to realize the target payment process with the payment device, wherein the target payment process is the process in which the electronic device uses the payment application and the payment device to complete the payment, and the target payment process is not the process in which the electronic device uses the NFC simulated card and the payment device to complete the payment. Therefore, when the user uses the electronic device in PICC mode to approach the card swiping area of ​​the payment device, regardless of whether the electronic device is in an unlocked state (for example, the screen is off) or an unlocked state, the electronic device and the payment device can complete the payment of the payment application through NFC interaction (that is, complete the target payment process), instead of using the NFC simulated card to complete the payment, and there is no need for the user to manually operate the electronic device (for example, unlock the electronic device and then approach the payment device). In this way, the electronic device can complete the payment method required by the user (corresponding to the target payment process) without excessive user operation, thereby improving the efficiency of the user's payment using the electronic device.

[0040] In one possible implementation, when the electronic device and the payment device perform NFC signaling interaction and use the first payment application and the payment device to complete the payment, the following can be performed: the electronic device and the payment device perform NFC signaling interaction at the access layer; the electronic device receives NFC tag data sent by the payment device, the NFC tag data includes the identifiers of one or more payment applications supported by the payment device (including the identifier of the first payment application), and then determines the first payment application from the one or more payment applications based on the NFC tag data, and uses the first payment application and the payment device to complete the payment.

[0041] In the above method, after the electronic device in PICC mode receives the first carrier sent by the payment device in PCD mode, it can perform the target payment process with the payment device, wherein the electronic device can receive the NFC tag data of the payment device and select the first payment application supported by the payment device and the payment device to complete the payment based on the NFC tag data, rather than arbitrarily selecting a payment application to pay, thereby ensuring the normal implementation of the target payment process, with higher fault tolerance and better feasibility.

[0042] In a possible implementation, the first payment application is an HCE application, not a wallet application.

[0043] In the above method, after the electronic device in PICC mode receives the first carrier sent by the payment device in PCD mode, it can perform a target payment process with the payment device, wherein the electronic device can use the first payment application as an HCE application and the payment device to complete the payment, instead of using the wallet application and the payment device to complete the payment according to the default payment method of the electronic device in PICC mode. There are many payment applications as HCE applications. In this way, the target payment process can be applied in a wider range of scenarios and is more in line with user usage.

[0044] In one possible implementation, the method further includes: after the electronic device turns on PCD mode, it generates a radio frequency field while in PCD mode; after a payment device that switches from PCD mode to PICC mode after sending a first carrier enters the radio frequency field of the electronic device, it sends a first response (e.g., indicating successful identification of the first carrier) to the payment device in PICC mode via NFC in PCD mode, the first response being used for the payment device to switch from PICC mode to PCD mode after receiving the first response, and then switch from PCD mode to PICC mode. When the electronic device and the payment device perform NFC signaling interaction and use the first payment application and the payment device to complete the payment, the following can be performed: after switching from PCD mode to PICC mode, perform NFC signaling interaction with the payment device that switched from PICC mode to PCD mode, and use the first payment application and the payment device to complete the payment.

[0045] In some examples, the first response is an NFC signal sent at the physical layer. In other examples, the first response is an NFC signal sent at the access layer.

[0046] In some examples, the first response is not modulated and does not indicate information. In other examples, the first response is modulated and can indicate information, such as indicating that the electronic device successfully identified the first carrier.

[0047] In the above method, after receiving the first carrier wave transmitted by a payment device in PCD mode, the electronic device in PICC mode can turn on PCD mode and switch from PICC mode to PCD mode. The electronic device in PCD mode can then transmit a first response to the payment device that has switched from PCD mode to PICC mode, allowing the payment device to determine, based on the first response, that the electronic device also supports the target payment process. Subsequently, the payment device and the electronic device can switch modes again and proceed with the target payment process, avoiding a situation where the payment device assumes the electronic device does not support the target payment process, causing the target payment process to fail to proceed normally. The payment device and the electronic device switch modes before transmitting the first response, thus avoiding continuing NFC signaling interactions related to the NFC emulated card in the previous "old mode." By switching modes after transmitting the first response and then proceeding with the target payment process, rather than directly proceeding with the target payment process in the current mode after transmitting the first response, the payment device and the electronic device require minimal changes to the NFC signal and internal device logic, resulting in higher feasibility.

[0048] In one possible implementation, the above method also includes: after the electronic device turns on the PCD mode, it generates a radio frequency field when in PCD mode; when the electronic device and the payment device perform NFC signaling interaction, and use the first payment application and the payment device to complete the payment, it can be executed: after the payment device that switches from PCD mode to PICC mode after sending the first carrier enters the radio frequency field of the electronic device, it performs NFC signaling interaction in PCD mode with the payment device that switches from PCD mode to PICC mode, and uses the first payment application and the payment device to complete the payment.

[0049] In the above method, after the electronic device in PICC mode receives the first carrier sent by the payment device in PCD mode, it can turn on the PCD mode and change from PICC mode to PCD mode. Then, the electronic device in PCD mode can perform the target payment process with the payment device that has switched from PCD mode to PICC mode. The payment device and the electronic device change modes before performing the target payment process, avoiding continuing the NFC signaling interaction related to the NFC simulated card in the previous "old mode". The payment device and the electronic device do not directly perform the target payment process in the current mode after transmitting the first carrier (a large number of NFC signals and internal device logic need to be changed). The logic of the target payment process between the payment device in PICC mode and the electronic device in PCD mode can use the existing logic, so that the changes to the NFC signal and the internal device logic are relatively small, and the feasibility is higher.

[0050] In one possible implementation, when an electronic device completes a payment using a first payment application and a payment receiving device, it can execute: sending a first payment command to the payment receiving device, wherein the first payment command carries an identifier of the first payment application and an identifier of a first payment account, the first payment account is a payment account in the first payment application corresponding to the electronic device, the first payment command is used to request the payment receiving device to execute a payment process, the payment process is a process in which the payment receiving device requests the cloud server to transfer the payment amount from the first payment account to the first payment account, the first payment account is a payment account in the first payment application corresponding to the payment device; the above method also includes: the electronic device receives a first payment response sent by the payment receiving device, wherein the first payment response carries a payment result.

[0051] In some examples, the electronic device may not be connected to the Internet when completing the payment using the first payment application and the payment device.

[0052] In the above method, when the electronic device completes the payment using the first payment application and the payment receiving device, the payment receiving device and the cloud server can interact without the need for the electronic device to interact with the cloud service, and the electronic device does not need to be connected to the Internet. Therefore, the user does not need to manually turn on the Internet switch of the electronic device, further improving the efficiency of the user using the electronic device to make payments.

[0053] In one possible implementation, the electronic device can specifically receive a first carrier wave sent by a payment device in PCD mode via NFC while in an unlocked state and in PICC mode, and then turn on PCD mode. For example, the electronic device is a mobile phone, tablet computer, or smart home device such as a smart screen.

[0054] In the above method, the user can place an unlocked electronic device close to the card swiping area of ​​the payment device and complete the payment of the payment application through NFC interaction. The user does not need to manually unlock the electronic device and then place it close to the card swiping area of ​​the payment device. In this way, the electronic device can complete the payment method required by the user without too much operation from the user, thereby improving the efficiency of the user's payment using the electronic device.

[0055] In one possible implementation, the electronic device can specifically receive a first carrier wave sent by a payment device in PCD mode via NFC while in an unlocked or unlocked state and in PICC mode, and then turn on PCD mode. The electronic device is a power-sensitive device, such as a wearable device such as a smart bracelet, smart watch, or smart glasses.

[0056] In the above method, the user can place the wearable device close to the card swiping area of ​​the payment device and complete the payment of the payment application through NFC interaction. The user does not need to manually turn on the PCD mode of the wearable device and then place it close to the card swiping area of ​​the payment device. In this way, the electronic device can complete the payment method required by the user without too much operation from the user, thereby improving the efficiency of the user's payment using the electronic device.

[0057] In one possible implementation, the method further includes: after the electronic device completes payment using the first payment application and the payment receiving device, deactivating PCD mode and switching to PICC mode. For example, after a user places an unlocked electronic device near the card swipe area of ​​the payment receiving device, the electronic device can switch to an unlocked state to complete payment via NFC interaction with the payment application. After the payment is completed, the electronic device can automatically return to an unlocked state to reduce power consumption.

[0058] In the above method, after the electronic device turns on the PCD mode and the payment device completes the target payment process, the PCD mode can be automatically turned off instead of keeping the PCD mode on, which effectively reduces power consumption and improves device availability.

[0059] In one embodiment, after the electronic device switches from PCD mode to PICC mode, it performs NFC signaling interaction with the payment device that switches from PICC mode to PCD mode, and completes payment using the first payment application and the payment device, and can execute the following: after the electronic device switches from PCD mode to PICC mode, it receives a first card search request sent by the payment device that switches from PICC mode to PCD mode via NFC, wherein the first card search request is used to indicate that the payment device supports the first NFC protocol, and the first card search request is different from the first carrier; then it sends a first card search response to the payment device via NFC, wherein the first card search response is used to indicate that the electronic device supports the first NFC protocol; receives an identifier of one or more payment applications that the payment device supports for payment, sent by the payment device; determines a first payment application from one or more payment applications, and completes payment using the first payment application and the payment device.

[0060] In the above method, the electronic device switched to PICC mode can receive a first card search request sent by a payment device switched to PCD mode. The first card search request is different from the first carrier wave and is used to implement normal NFC signaling interaction at the access layer. Therefore, the electronic device can normally return the first card search response, thereby completing the target payment process with the payment device. In this way, the electronic device can perform corresponding operations based on the first carrier wave or the first card search request sent by the payment device in PCD mode in different scenarios, ensuring the normal progress of the target payment process and improving payment efficiency.

[0061] In one possible implementation, the carrier wave corresponding to the first card search request is modulated, and the first carrier wave is unmodulated. In this way, the electronic device can distinguish the first card search request from the first carrier wave without any analysis, further improving payment efficiency.

[0062] In one possible implementation, after the electronic device receives the first carrier sent by the payment device via NFC, the electronic device does not start the wallet application of the electronic device; after the electronic device receives the first card search request sent by the payment device via NFC, the electronic device does not start the wallet application of the electronic device.

[0063] In the above method, after the electronic device in PICC mode receives the first carrier wave, it will not use the wallet application and the payment device to complete the payment according to the electronic device's default payment method in PICC mode, and therefore will not start the wallet application. Furthermore, after the electronic device receives the first carrier wave and subsequently receives the first card search request in PICC mode, it will not use the wallet application and the payment device to complete the payment according to the electronic device's default payment method in PICC mode, and therefore will not start the wallet application. This ensures that the electronic device can complete the target payment process with the payment device, avoids unnecessary power consumption from starting and running the wallet application, and improves feasibility.

[0064] In one possible implementation, the first carrier includes N subcarriers, and the first coding feature of the first carrier includes one or more of the following: the amplitude of each subcarrier in the N subcarriers is a preset first amplitude, the duration of each subcarrier in the N subcarriers is a first duration, the time interval between two adjacent subcarriers in the N subcarriers is a preset first time interval, and N is a preset value, where N is a positive integer greater than 1.

[0065] In the above method, the first coding feature of the first carrier can be implemented in various ways and can be applied to various scenarios. For example, the first coding feature can be determined according to the type and characteristics of the electronic device and the payment device, which is more feasible.

[0066] In a third aspect, the present application provides an electronic device comprising a transceiver, a processor and a memory; the memory is used to store a computer program, the processor calls the computer program, and the electronic device executes the payment method provided in the second aspect and any one of the implementations of the second aspect.

[0067] In a fourth aspect, an embodiment of the present application provides a computer storage medium, including a computer program, which, when executed by a processor, is used to implement the payment method provided in the second aspect and any one of the implementations of the second aspect.

[0068] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when the computer program runs on a processor, is used to implement the payment method provided in the second aspect and any one of the implementations of the second aspect.

[0069] In the sixth aspect, the present application provides a chip system, including a processing circuit and an interface circuit, the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to run the code instructions to execute the payment method provided in the second aspect and any one of the implementation methods of the second aspect.

[0070] In a seventh aspect, the present application provides an electronic device, the electronic device including a method or apparatus for executing any aspect or embodiment of the present application. The electronic device is, for example, a chip.

[0071] It should be understood that the description of technical features, technical solutions, beneficial effects or similar language in this application does not imply that all features and advantages can be realized in any single implementation. On the contrary, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution or beneficial effect is included in at least one implementation. Therefore, the description of a technical feature, technical solution or beneficial effect in this application does not necessarily refer to the same implementation. Furthermore, the technical features, technical solutions and beneficial effects described in this application can also be combined in any appropriate manner. Those skilled in the art will understand that this application can be implemented without one or more specific technical features, technical solutions or beneficial effects of a specific implementation. In other implementations, additional technical features and beneficial effects can also be identified in specific implementations that do not embody all implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] The following is an introduction to the drawings used in this application.

[0073] Figure 1 This is a schematic diagram of the NFC working principle provided by this application;

[0074] Figure 2 This is a schematic diagram of the architecture of an NFC system provided by this application;

[0075] Figure 3 This is a schematic diagram of the architecture of an NFC protocol stack provided by this application;

[0076] Figure 4 This is a schematic diagram of the structure of an electronic device provided by this application;

[0077] Figure 5 This is a schematic diagram of the architecture of a payment system provided by this application;

[0078] Figures 6A-6EA schematic diagram illustrating how some electronic devices and payment devices complete payment through NFC interaction;

[0079] Figures 7A-7G Schematic diagrams showing some exemplary NFC pull-up payment user interfaces;

[0080] Figure 8 This is a flow chart of a payment method provided by this application;

[0081] Figure 9 This is a flowchart of another payment method provided by this application;

[0082] Figure 10 This is a schematic diagram of a payment device sending a first carrier provided by the present application;

[0083] Figure 11 This is a flowchart of the NFC signaling interaction process at the access layer provided by this application;

[0084] Figure 12 This is a flowchart of another NFC signaling interaction process at the access layer provided by this application;

[0085] Figure 13 This is a schematic diagram of the hardware structure of an electronic device provided by this application;

[0086] Figure 14-17 This is a schematic diagram of the structures of some communication devices provided in this application. DETAILED DESCRIPTION

[0087] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings. The terms used in the implementation methods of the embodiments of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application.

[0088] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0089] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of the technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

[0090] The following describes the working principle of the near field communication (NFC) technology in the embodiments of the present application.

[0091] Figure 1 This is a schematic diagram of the NFC working principle provided by an embodiment of the present application.

[0092] like Figure 1 As shown, the two parties communicating using NFC technology may include a proximity coupling device (PCD) and a proximity integrated circuit card (PICC). Among them, the PCD can implement contactless communication with the PICC in proximity. The PCD and the PICC may allow near-field communication at a specific data rate (e.g., 106 kilobits per second (kbps), 212kbps, 424kbps, or 848kbps)) and a specific frequency (e.g., 13.56 megahertz (MHz)). The communication between the PCD and the PICC may occur within a close distance between the PCD and the PICC, for example, a distance less than or equal to 10 cm.

[0093] The PCD can generate high-frequency alternating current to generate a radio frequency field of a specified frequency (for example, 13.56MHz) and send data to the PICC through the radio frequency field. When the PICC is close to the PCD, it can sense the radio frequency field emitted by the PCD. After entering the radio frequency field of the PCD, the PICC can obtain energy from the radio frequency field of the PCD through electromagnetic induction, and use the obtained energy to generate electricity to drive the circuit inside the PICC and analyze the data sent by the PCD through the radio frequency field, thereby realizing data transmission from the PCD to the PICC. The PICC can also send data to the PCD by load modulating the radio frequency field, thereby realizing data transmission from the PICC to the PCD.

[0094] The following describes the NFC system in the embodiments of the present application.

[0095] Figure 2 1 is a schematic diagram of the architecture of an NFC system 10 provided in an embodiment of the present application.

[0096] like Figure 2 As shown, the NFC system 10 may include an electronic device 100 and a payment device 200. The electronic device 100 may simulate itself as a PICC that complies with NFC standards using data from an NFC emulated card to implement PICC functionality. The electronic device 100 may activate one or more NFC emulated cards.

[0097] In some embodiments, the electronic device 100 can support both PICC mode and PCD mode. When in PCD mode, the electronic device 100 can function as a PCD to transmit a radio frequency field and communicate with the PICC via the radio frequency field. When in PICC mode, the electronic device 100 can function as a PICC to passively receive the radio frequency field transmitted by the PCD and communicate with the PCD via load modulation technology. In some examples, when in PICC mode, the electronic device 100 can simulate itself as a PICC that complies with NFC standards by using data information from an NFC emulated card.

[0098] In an embodiment of the present application, the electronic device 100 can be in PICC mode after the NFC function is turned on. In the case where the electronic device 100 supports both PICC mode and PCD mode, the electronic device 100 can also switch between PICC mode and PCD mode in a time-sharing manner after the NFC function is turned on. In some embodiments, in order to save power consumption, after the NFC function is turned on, if the electronic device 100 is in an unlocked state, the electronic device 100 can be in PICC mode by default. If the electronic device 100 is in an unlocked state, the electronic device 100 can be in PICC mode or PCD mode in a time-sharing manner. For example, the electronic device 100 is a mobile phone, tablet computer or other device as shown below, or a smart home device such as a smart large screen. In other embodiments, in order to save power consumption, after the NFC function is turned on, regardless of whether the electronic device 100 is in an unlocked state or an unlocked state, the electronic device 100 can be in PICC mode by default. The electronic device 100 can be a device that is sensitive to power consumption. For example, the electronic device 100 is a wearable device such as a smart bracelet, smart watch, smart glasses or the like as shown below.

[0099] In some embodiments, the payment device 200 can support both PCD and PICC modes. When in PCD mode, the payment device 200 can function as a PCD, transmitting radio frequency fields and communicating with a PICC via these fields. When in PICC mode, the payment device 200 can function as a PICC, passively receiving radio frequency fields transmitted by the PCD and communicating with the PCD via load modulation.

[0100] In an embodiment of the present application, if the payment device 200 supports both PCD mode and PICC mode, the payment device 200 can switch between PCD mode and PICC mode. In some embodiments, the NFC module of the payment device 200 can support both PCD mode and PICC mode, and the NFC module of the payment device 200 can switch between PCD mode and PICC mode. In some embodiments, the NFC module of the payment device 200 can operate in PCD mode. The payment device 200 may also include an NFC tag device, which can operate in PICC mode. The NFC tag device can be attached to the outer surface or inner surface of the card swiping area of ​​the payment device 200. Optionally, the NFC tag device can be connected to the processor of the payment device 200, or it can be disconnected from the processor of the payment device 200.

[0101] In the embodiment of the present application, the device type of the electronic device 100 can be any of a mobile phone, a tablet computer, a handheld computer, a desktop computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), as well as smart home devices such as smart large screens and smart speakers, wearable devices such as smart bracelets, smart watches, and smart glasses, extended reality (XR) devices such as augmented reality (AR), virtual reality (VR), and mixed reality (MR), in-vehicle devices or smart city devices, etc.

[0102] In the embodiment of the present application, the device type of the payment device 200 can be any one of a mobile phone, a tablet computer, a handheld computer, a desktop computer, a laptop computer, a super mobile personal computer, a netbook, a cellular phone, a personal digital assistant, as well as smart home devices such as smart large screens and smart speakers, wearable devices such as smart bracelets, smart watches, smart glasses, extended reality devices such as augmented reality, virtual reality, and mixed reality, vehicles, gates, smart door locks, card readers, point of sales (POS) machines, ticket purchasing and / or ticket verification terminals, bank service terminals, and ID card readers.

[0103] The following describes the NFC protocol stack in the embodiments of the present application.

[0104] Figure 3 This is a schematic diagram of the architecture of an NFC protocol stack provided in an embodiment of the present application.

[0105] like Figure 3 As shown, the NFC protocol stack may include a physical layer, a radio frequency layer, an access layer, a transport layer, and an application layer.

[0106] Among them, the physical layer can be used to implement the physical characteristics of NFC technology communication.

[0107] The radio frequency layer can be used to implement radio frequency specifications during NFC technology communication, such as data rate, frequency of radio frequency signals, etc.

[0108] The access layer can be used to implement polling and device discovery, service result notification, card conflict management, transmission protocol negotiation, timeout and retransmission mechanism, PICC / PCD mode switching, and integrated card selection.

[0109] The transport layer includes a high-speed data transmission protocol, through which data transmission between the PCD and the PICC at the application layer can be achieved.

[0110] The application layer can be used to implement one or more NFC services and one or more service management strategies. Among them, one or more NFC services may include codeless payment, electronic tickets, access control, digital ID card, full-scene touch, short-range data transmission, etc. One or more business management strategies may include any one or more of file management, card long activation, security management and service routing management. In some embodiments, the processing logic of the NFC service can be composed of the following: Figure 4 In some embodiments, the processing logic of the service management policy can be performed by the following Figure 4 The NFC basic service module is executed.

[0111] The structure of the electronic device 100 in the embodiment of the present application is introduced below.

[0112] Figure 4 1 is a schematic structural diagram of an electronic device 100 provided in an embodiment of the present application.

[0113] like Figure 4As shown, the electronic device 100 may include a processor 101 and an NFC module 102, and the processor 101 may be connected to the NFC module 102. One or more applications (APPs) may be running in the processor 101. In some examples, the one or more applications may include a wallet application, one or more host-based card emulation (HCE) applications, a subscriber identity module (SIM) card application, etc. The one or more HCE applications include one or more payment applications, and any one of the one or more HCE applications may be a payment application or may not be a payment application.

[0114] In some embodiments, as Figure 4 As shown, the electronic device 100 may further include a secure element (SE) 103 and / or a SIM card 104. The processor 101 may be connected to the NFC module 102, SE 103, and SIM card 104 respectively, and the NFC module 102 may also be connected to the SE 103 and SIM card 104.

[0115] In some embodiments, as Figure 4 As shown, the processor 101 may also include an NFC basic service module. The NFC basic service module can be used to provide common management functions for one or more NFC services. Among them, the common management functions may include file management, card long-term activation, security management, service routing management, etc.

[0116] In some embodiments, the NFC module 102 can be used to implement NFC technology communication between the electronic device 100 and the payment device 200.

[0117] In some embodiments, the NFC module 102 may include an NFC controller ( Figure 4 Not shown), NFC transceiver ( Figure 4 Not shown) and NFC memory ( Figure 4 (not shown), wherein the NFC controller can be connected to the processor 101, and the NFC controller can also be connected to the NFC transceiver and the NFC memory respectively.

[0118] The NFC controller in the NFC module 102 can be used to modulate and demodulate contactless communication signals, control the input and output of data in the NFC memory, and interact with the processor 101. The NFC transceiver in the NFC module 102 can be used to transmit and receive NFC signals (e.g., 13.56 MHz radio frequency signals). In some embodiments, the NFC transceiver may include an EMC filter circuit, a matching circuit, a receiving circuit, and an NFC antenna. The NFC antenna may be a loop antenna to implement the proximity-based contactless communication capabilities of the NFC module 102. The NFC memory in the NFC module 102 can be used to store data sent by the NFC module 102 to the payment device 200, as well as data received from the payment device 200.

[0119] In some embodiments, the NFC memory can be a memory that can be shared by the NFC module 102 and other modules in the electronic device 100. For example, some data in the NFC memory can be called by the NFC controller, while other data can be called by the SE 103. In other embodiments, the NFC memory can also be a collection of multiple memories. For example, the NFC controller can include a first memory among the multiple memories. The first memory can be used to store instructions or data used or recycled by the NFC controller. If the NFC controller needs to use the instruction or data again, it can be directly called from the first memory, thus reducing the waiting time of the NFC controller. The SE 103 can include a second memory among the multiple memories. The second memory can be used to store card information of an NFC simulated card based on a secure element (SE). In this way, if the SE 103 needs to read the card information of the NFC simulated card, the card information of the NFC simulated card can be read from the second memory in the SE 103. The SIM card 104 may include a third memory among the multiple memories, and the third memory may be used to store card information of an NFC simulated card based on the SIM card, etc. In this way, if the SIM card 104 needs to read the card information of the NFC simulated card, the card information of the NFC simulated card may be read from the third memory in the SIM card 104.

[0120] In some embodiments, the NFC memory can also be used to store routing information. In some embodiments, the routing information can be controlled or managed by the NFC controller, and the routing information can include a routing table, which is composed of a list of routing rules. Each routing rule includes an applet identifier (AID) and a corresponding destination. The AID is the identifier of the applet used to implement the business logic of the NFC simulated card, and the destination corresponding to the AID is the place where the applet of the AID runs (i.e., the hardware device or software module corresponding to the NFC simulated card of the AID). The destination can be an HCE application (such as a payment application) in the processor 101, or the destination can be the SE103 or SIM card 104 connected to the NFC module 102.

[0121] In the embodiment of the present application, the electronic device 100 can activate one or more NFC simulated cards in the application according to the user's input, thereby enabling the electronic device 100 to support one or more NFC services. The service processing logic of the NFC simulated card in the electronic device 100 is specifically implemented by an applet, which can be stored and run in the hardware device or software module corresponding to the NFC simulated card (such as HCE application, SE 103, SIM card 104, etc.).

[0122] In the embodiment of the present application, the card emulation mode of the NFC emulation card of the electronic device 100 may include a hardware-based virtual card mode and a software-based HCE mode.

[0123] In hardware-based virtual card mode, the electronic device 100 can provide the operating environment of the applet corresponding to the NFC simulated card and the storage and processing of the business data of the NFC simulated card through SE103 or SIM card 104. As the front end of contactless communication, the NFC module 102 forwards the NFC command received from the external payment device 200 to SE103 or SIM card 104. The applet in SE103 or SIM card 104 processes the NFC command and generates response data for the payment device 200. SE103 or SIM card 104 can send the response data to the NFC module 102, and the NFC module 102 can send the response data to the external payment device 200. In some examples, the user can activate one or more NFC simulated cards in the wallet application. The wallet application can write the applets of one or more NFC simulated cards and card data to SE103, and SE103 can run the one or more NFC simulated card applets. In some examples, the user can activate one or more NFC simulated cards in the SIM card application, the SIM card application can write one or more NFC simulated card applets and card data into the SIM card 104 for storage, and the SIM card 104 can run one or more NFC simulated card applets.

[0124] In software-based HCE mode, the HCE application in processor 101 provides an operating environment for the applet corresponding to the NFC emulated card, as well as storage and processing of NFC emulated card business data. NFC module 102, acting as the front end for contactless communication, forwards NFC commands received from an external payment device 200 to the HCE application in processor 101. The HCE application can process the NFC commands through an applet running within the HCE application or a cloud server, and generate response data for the PCD. The HCE application can then send the response data to NFC module 102, which in turn can send the response data to the external payment device 200. In some examples, a user can activate one or more NFC emulated cards in the HCE application, which can then run one or more NFC emulated card applets. The HCE application can then store the card data of the NFC emulated cards in the local storage of the electronic device 100 or on a cloud server.

[0125] For example, in the above-mentioned card emulation scenario, the electronic device 100 may be installed with native applications related to NFC, and the user may also download and install third-party applications in the electronic device 100 through the application store. Generally speaking, the native application can adopt a hardware-based virtual card solution, while the third-party application can adopt an HCE solution. The native application can be a wallet application, a SIM card application, etc., and the third-party application can be a payment application, a social application, a banking application, etc. The above examples are only used to explain the embodiments of the present application and should not constitute a limitation.

[0126] In some embodiments, the SE 103 and the NFC module 102 may be two independent chips. In other embodiments, the SE 103 and the NFC module 102 may be packaged in one chip.

[0127] Currently, when a user uses the electronic device 100 to purchase goods or services at a brick-and-mortar merchant offline, payment is typically completed using a QR code within a payment application. For example, the user opens the scanning function within the payment application to scan the merchant's payment QR code within the payment application to obtain the merchant's payment account information, or the user opens the payment page within the payment application and has the merchant's payment device scan the QR code within the payment page to obtain the user's payment account information. The QR code payment method requires the user to perform multiple operations to complete the payment, which is inefficient for users to make payments using the electronic device 100.

[0128] To improve the efficiency of payment using electronic device 100, the user can place electronic device 100 close to the card swiping area of ​​payment receiving device 200, and the electronic device 100 and payment receiving device 200 can complete the payment through NFC interaction. The following example illustrates the process of completing the payment through NFC interaction between electronic device 100 and payment receiving device 200.

[0129] Figure 5 2 is a schematic diagram of the architecture of a payment system 20 provided in an embodiment of the present application.

[0130] like Figure 5 As shown, the payment system 20 may include an electronic device 100, a payment device 200 and a cloud server 300. The electronic device 100 may include a processor 101 and an NFC module 102. The processor 101 may include a payment application and an NFC basic service module. Figure 4 The structural description shown is similar and will not be repeated here.

[0131] like Figure 5As shown, the electronic device 100 can be in PCD mode, and the payment device 200 can be in PICC mode. When the electronic device 100 and the payment device 200 are close to each other, the electronic device 100 can function as a PCD to perform NFC interaction with the payment device 200 functioning as a PICC.

[0132] like Figure 5 As shown, the electronic device 100 can communicate with the cloud server 300 via a wired or wireless method. The payment device 200 can also communicate with the cloud server 300 via a wired or wireless method. Wired methods include, for example, high-definition multimedia interface (HDMI), universal serial bus (USB), coaxial cable, optical fiber, digital subscriber line (DSL), etc. Wireless methods include, for example, Bluetooth, wireless fidelity (Wi-Fi), sidelink, NFC, ultra-wide band (UWB), infrared, etc.

[0133] In some embodiments, the cloud server 300 may include a server for a payment application in the electronic device 100 , and the server for the payment application may be used to provide payment-related services for the payment application.

[0134] Below through Figure 5 The following example illustrates a process in which the electronic device 100 and the payment device 200 complete payment through NFC interaction.

[0135] like Figure 5 In step 1 shown, the electronic device 100 obtains NFC tag data from the payment device 200. The electronic device 100 is in PCD mode and interacts with the payment device 200 in PICC mode via NFC module 102 to obtain the NFC tag data from the payment device 200. In some examples, the NFC tag data from the payment device 200 may include identifiers of one or more payment applications supported by the payment device 200. In some examples, the NFC tag data from the payment device 200 may include information about a first order to be paid, such as the identifier of the first order, optionally the payment account information of one or more payment applications, and optionally the payment amount of the first order.

[0136] like Figure 5In step 2 shown, in the electronic device 100, the NFC module 102 sends the NFC tag data of the payment device 200 to the NFC basic service module in the processor 101. The NFC module 102 can read the content of the NFC tag data of the payment device 200 and notify the NFC basic service module in the processor 101 of the read content.

[0137] like Figure 5 In step 3 shown, in the processor 101 of the electronic device 100, the NFC basic service module launches the target payment application, for example, by launching the target payment application through a data distribution service. The NFC basic service module can determine the target payment application from one or more HCE applications (including one or more payment applications) based on the NFC tag data of the payment device 200, and launch the target payment application. In some examples, the NFC tag data of the payment device 200 includes the identifiers of one or more payment applications that the payment device 200 supports payment. If the identifier of the payment application included in the NFC tag data of the payment device 200 is the identifier of the target payment application installed on the electronic device 100, the electronic device 100 can launch the target payment application. If the identifier of the payment application included in the NFC tag data of the payment device 200 is different from the identifier of the payment application installed on the electronic device 100 (which can be understood as the target payment application is not included in the applications installed by the electronic device 100), the electronic device 100 can output an installation prompt for the target payment application, and then launch the target payment application in response to the user input to install the target payment application. Launching the payment application may include launching the payment application and running the payment application in the background, or launching the payment application may include launching the payment application and running the payment application in the foreground (the user interface of the payment application will be displayed at this time).

[0138] like Figure 5In step 4 shown, the target payment application in the electronic device 100 queries the cloud server 300 for payment preferential information and displays the payment interface. Among them, the electronic device 100 can communicate with the cloud server 300 via wired or wireless means to enable the target payment application to query the cloud server 300 for payment preferential information. The payment preferential information may include payment preferential information for all users, and may also include payment preferential information for users of the electronic device 100. The payment preferential information may include payment preferential information of the target payment application, and optionally other payment preferential information. Optionally, the target payment application in the electronic device 100 may display the queried payment preferential information on the payment interface. In some examples, the NFC tag data of the payment device 200 may include information about the first order to be paid, and the payment application in the electronic device 100 may display information about the first order on the payment interface, such as the target payment application's collection account information (i.e., information about the target collection account), and optionally, the payment amount of the first order. It is understandable that the target payment application can query the cloud server 300 for payment preferential information only when the electronic device 100 and the cloud server 300 communicate via wired or wireless means. Therefore, the electronic device 100 needs to be connected to the Internet to execute the payment preferential information. Figure 5 Step 4 shown.

[0139] Not limited to Figure 5 As shown in step 4, in other embodiments, the target payment application in the electronic device 100 may not query the cloud server 300 for payment discount information, for example, the target payment application may not query the payment discount information when the electronic device 100 is not connected to the Internet.

[0140] like Figure 5 In step 5 shown, the electronic device 100 sends a payment command to the payment device 200 via short-range communication technology, carrying the identifier of the target payment account. The short-range communication technology may include, but is not limited to, any one or more of NFC, Bluetooth, Wi-Fi, and UWB. The target payment account may be the payment account corresponding to the target payment application in the electronic device 100. In some examples, when the electronic device 100 displays the payment interface, it receives the user's input for payment of the first order, and in response to the input, sends a payment command to the payment device 200 via short-range communication technology. Optionally, the payment command may also carry the identifier of the target payment application. Optionally, the payment command may also carry the payment amount and / or payment remarks, etc.

[0141] like Figure 5In step 6, the payment device 200 sends payment information to the cloud server 300 via a wired or wireless method to execute the payment process. The payment information may include the payment amount (i.e., the amount paid by the user to the payment device 200 via the electronic device 100, i.e., the payment amount for the first order), the identifier of the target payment account (i.e., the payment account of the target payment application supported by the payment device 200), and the identifier of the target payment account (i.e., the payment account of the target payment application on the electronic device 100). The cloud server 300 (e.g., the server of the target payment application) may execute the payment process based on the payment information, deducting the payment amount from the balance of the target payment account and adding the payment amount to the balance of the target payment account. In some examples, if the cloud server 300 successfully transfers the payment amount from the balance of the target payment account to the target payment account, it may send a payment completion notification to the payment device 200 used by the merchant. Upon receiving the payment completion notification, the payment device 200 may output a payment completion prompt, which serves to inform the merchant that the payment amount has been successfully collected. The payment completion notification can be a text prompt, an audio prompt, an image prompt, a mechanical vibration prompt, an indicator light prompt, etc. In other examples, if the cloud server 300 fails to transfer the payment amount from the balance of the target payment account to the target payment account, it can send a payment failure notification to the merchant's payment device 200. After receiving the payment failure notification, the payment device 200 can output a payment failure notification, which can be used to inform the merchant of the payment failure. This payment failure notification can be a text prompt, an audio prompt, an image prompt, a mechanical vibration prompt, an indicator light prompt, etc.

[0142] like Figure 5 In step 7 shown, the payment collection device 200 sends a payment response to the electronic device 100 via short-range communication technology, carrying the payment result. The short-range communication technology may include, but is not limited to, any one or more of NFC, Bluetooth, Wi-Fi, and UWB. The payment result carried in the payment response is the payment result of the first order. After the payment collection device 200 receives the payment completion notification / payment failure notification sent by the cloud server 300, it can send a payment response to the electronic device 100. If the payment collection device 200 receives the payment completion notification, the payment result carried in the payment response indicates a successful payment. If the payment collection device 200 receives the payment failure notification, the payment result carried in the payment response indicates a failed payment.

[0143] Not limited to Figure 5 In step 7 shown, in other embodiments, the cloud server 300 may also send a payment completion notification / payment failure notification to the electronic device 100, and the electronic device 100 may output a corresponding payment completion prompt / payment failure prompt based on the payment completion notification / payment failure notification.

[0144] Not limited to Figure 5 In other embodiments, the payment device 200 may send a payment command to the electronic device 100 via short-range communication technology, but in this case, the payment command carries the identifier of the target payment account. The electronic device 100 may then send payment information to the cloud server 300 via wired or wireless communication to execute the payment process. The payment information includes the payment amount, the identifier of the target payment account, and the identifier of the target payment account. The cloud server 300 may execute the payment process based on the payment information, deducting the payment amount from the balance of the target payment account and adding the payment amount to the balance of the target payment account. In some examples, if the cloud server 300 successfully transfers the payment amount from the balance of the target payment account to the target payment account, it may send a payment completion notification to the electronic device 100. Upon receiving the payment completion notification, the electronic device 100 may output a payment completion prompt (e.g., display a payment completion interface) to inform the user that the payment is complete. In other examples, if the cloud server fails to transfer the payment amount from the balance of the target payment account to the target payment account, it may send a payment failure notification to the electronic device 100. After receiving the payment failure notification, the electronic device 100 can output a payment failure prompt (for example, displaying a payment failure interface), which is used to prompt the user that the payment has failed. After the electronic device 100 receives the payment completion notification / payment failure notification sent by the cloud server 300, it can send a payment response to the payment device 200 through short-range communication technology. The payment result carried by the payment response corresponds to the payment completion notification / payment failure notification. Not limited to the above example, in other examples, the cloud server 300 can also send a payment completion notification / payment failure notification to the payment device 200, and the payment device 200 can output a corresponding payment completion prompt / payment failure prompt based on the payment completion notification / payment failure notification.

[0145] The following examples illustrate some implementation scenarios of payment completed by the electronic device 100 and the payment device 200 through NFC interaction.

[0146] Figures 6A-6C The following is a schematic diagram showing an example of an electronic device 100 and a payment device 200 completing a payment through NFC interaction. Figure 6A 、 Figure 6D and Figure 6E The following is a schematic diagram showing another electronic device 100 and a payment device 200 completing payment through NFC interaction.

[0147] like Figure 6AAs shown, the payment device 200 may include a card swipe area, for example, an NFC module may be included below the card swipe area. When a physical NFC tag device or an electronic device 100 in PICC mode is brought close to the card swipe area of ​​the payment device 200, the physical NFC tag device or the electronic device 100 in PICC mode may perform NFC interaction with the payment device 200.

[0148] like Figure 6B As shown, the electronic device 100 is in a state where the screen is on and unlocked. The electronic device 100 displays a desktop 610 as an example. The desktop 610 may include icons of one or more applications, such as icons of clock applications, settings applications, recorder applications, wallet applications, and payment applications. The electronic device 100 supports both PICC mode and PCD mode. The electronic device 100 can be in PICC mode or PCD mode at different times when the screen is on and unlocked. The electronic device 100 is in PICC mode by default when it is not unlocked. The user can place the electronic device 100 close to the card swiping area of ​​the payment device 200. The electronic device 100 can perform NFC signaling interaction with the payment device 200 in PCD mode and PICC mode. The electronic device 100 can obtain the NFC tag data of the payment device 200 from the payment device 200, and pull up the payment application of the electronic device 100 according to the NFC tag data of the payment device 200. The electronic device 100 can complete the payment with the payment device 200 through the payment application. For the specific implementation process, please refer to Figure 5 Example payment process.

[0149] like Figure 6C As shown, after the electronic device 100 pulls up the payment application, it can display a user interface 620 of the payment in progress. Among them, the user interface 620 is the user interface of the payment application, which can include an icon 611 of the payment application and a payment prompt message 612 (for example, "paying").

[0150] pass Figures 6A-6C As can be seen from the implementation scenario shown, the electronic device 100 can only perform NFC signaling interaction with the payment device 200 in PICC mode in PCD mode (including the electronic device 100 reading the NFC tag data of the payment device 200), thereby launching the payment application corresponding to the NFC tag data and completing the payment with the payment device 200. If the electronic device 100 is in an unlocked state (for example, a locked screen state or an off-screen state), the user also needs to manually unlock the electronic device 100, for example, by pressing the power button and manually entering the lock screen password or touching the fingerprint recognition area with a finger, and then bringing the electronic device 100 in the unlocked state with the bright screen close to the card swiping area of ​​the payment device 200. The user operation is cumbersome and the user's payment efficiency using the electronic device is low.

[0151] like Figure 6D As shown, the electronic device 100 is in a screen-off and unlocked state, so the electronic device 100 is in PICC mode by default. The user can place the electronic device 100 close to the card swiping area of ​​the payment device 200. The electronic device 100 can perform NFC signaling interaction with the payment device 200 in PCD mode in PICC mode, and pull up the NFC simulated card in the electronic device 100 and the payment device 200 to complete the card swiping service. Among them, in order to ensure security and the user experience of fast card swiping, after the electronic device 100 receives the NFC signal sent by the payment device 200 in PCD mode in PICC mode, it will start the wallet application and forward the NFC signal to SE103. The Applet in SE103 implements the business processing logic of the NFC simulated card of the wallet application. Therefore, the electronic device 100 in PICC mode can use the NFC simulated card in the wallet application to perform NFC signaling interaction with the payment device 200 in PCD mode, and complete the card swiping service of the transaction payment of the NFC simulated card.

[0152] like Figure 6E As shown, when the electronic device 100 in PICC mode and the payment device 200 in PCD mode perform NFC signaling interaction, the electronic device 100 can display an NFC simulated card swiping interface 630. The swiping interface 630 is the user interface of the wallet application and can include an icon 631 of an NFC simulated card (using a transit card as an example) in the wallet application and a fingerprint icon 632. The fingerprint icon 632 can be used to verify the user's fingerprint information. For example, if the user's fingerprint information is verified successfully, the NFC simulated card in the wallet application can be used to perform a card swiping service for transaction payment.

[0153] pass Figure 6A 、 Figure 6D and Figure 6E As can be seen from the implementation scenario shown, when the electronic device 100 is in an unlocked state, it can only perform NFC signaling interaction with the payment device 200 in PCD mode in PICC mode, thereby pulling up the NFC simulated card in the wallet application or other applications, and performing the card swiping service of the transaction payment of the NFC simulated card with the payment device 200, without reading the NFC tag data of the payment device 200 and pulling up the corresponding payment application. If the user wants to use the payment application of the electronic device 100 to complete the payment with the payment device 200, it is necessary to manually unlock the electronic device 100, and then bring the electronic device 100 with the screen on and unlocked close to the card swiping area of ​​the payment device 200, so that the electronic device 100 can read the NFC tag data of the payment device 200 and pull up the corresponding payment application, for example Figures 6A-6C The implementation scenario shown is cumbersome for users to operate and inefficient for users to pay using electronic devices.

[0154] An embodiment of the present application provides a payment method, in which the electronic device 100 can be in PICC mode, for example, in PICC mode by default, or in PICC mode on a time-sharing basis. The electronic device 100 in PICC mode can be close to the card swiping area of ​​the payment device 200, and receive the first carrier sent by the payment device 200 in PCD mode. After the electronic device 100 receives the first carrier with the first coding feature, it can determine to perform a target payment process with the payment device 200, wherein the target payment process is a process in which the electronic device 100 obtains the NFC tag data of the payment device 200 and uses the target payment application corresponding to the NFC tag data and the payment device 200 to make payment, and the target payment process is not a process in which the electronic device 100 uses an NFC simulated card and the payment device 200 to make payment. Therefore, after the electronic device 100 receives the first carrier, it can perform NFC signaling interaction with the payment device 200 in PCD mode or PICC mode, and obtain the NFC tag data of the payment device 200. The electronic device 100 can determine and start the target payment application based on the NFC tag data of the payment device 200, and use the target payment application to complete the payment with the payment device 200, that is, to realize the target payment process between the electronic device 100 and the payment device 200. Therefore, no matter whether the electronic device 100 is in an unlocked state or an unlocked state, the user can place the electronic device 100 close to the card swiping area of ​​the payment device 200, and use the payment application of the electronic device 100 to complete the payment with the payment device 200, and there will be no problem. Figure 6A 、 Figure 6D and Figure 6E In the case of using the wallet application to simulate an NFC card for transaction payment, there is no need to manually unlock the electronic device 100 and then place the unlocked electronic device 100 with the screen on close to the card swiping area of ​​the payment device 200. In this way, the electronic device 100 can complete the payment method required by the user (i.e., payment using the payment application) without requiring excessive user operations, thereby improving the efficiency of the user's payment using the electronic device 100.

[0155] In some embodiments, the payment application of the electronic device 100 is an HCE application.

[0156] It is understandable that after the payment device 200 transmits the first carrier wave to the electronic device 100, it can switch from PCD mode to PICC mode. After the electronic device 100 receives the first carrier wave transmitted by the payment device 200, it can switch from PICC mode to PCD mode. In this way, the electronic device 100 and the payment device 200 can conduct "new NFC signaling interaction" in the "new mode" and avoid continuing NFC signaling interaction related to NFC simulated cards in the "old mode". This ensures that the electronic device 100 and the payment device 200 complete the target payment process and meet the user's NFC payment needs. In addition, since the electronic device 100 and the payment device 200 conduct the target payment process after the mode change, rather than directly conducting the target payment process in the "old mode", the changes to the NFC signal and internal device logic are relatively small, and the feasibility is improved.

[0157] It can be understood that after the electronic device 100 receives the first carrier sent by the payment device 200, it determines to perform the target payment process with the payment device 200. The target payment process is not a process in which the electronic device 100 uses an NFC simulated card and the payment device 200 to make payment. Therefore, the electronic device 100 does not need to start the wallet application after receiving the first carrier.

[0158] The following is an illustrative introduction to the application scenarios of NFC pull-up payment and the user interface in the application scenarios in the embodiments of the present application.

[0159] Figures 7A-7G Some NFC pull-up payment user interface diagrams are shown as examples.

[0160] like Figure 7A As shown, the electronic device 100 is in the state of screen off and unlocked, so the electronic device 100 is in PICC mode by default. The user can place the electronic device 100 close to the card swiping area of ​​the payment device 200, and the electronic device 100 can perform NFC signaling interaction with the payment device 200 in PCD mode in PICC mode. For an example of the payment device 200, see Figure 6A .

[0161] like Figure 7BAs shown, after the electronic device 100 in PICC mode interacts with the payment device 200 in PCD mode through NFC signaling, for example, after the electronic device 100 receives the first carrier wave transmitted by the payment device 200, the electronic device 100 may display a lock screen interface 710. The lock screen interface 710 may include a lock mark 711, time information, date information, etc. The lock mark 711 is used to remind the user that the electronic device 100 is in a locked state (i.e., unlocked state). The lock screen interface 710 may also display a payment prompt window 712, for example, the payment prompt window 712 is displayed floating on the lock screen interface 710. The payment prompt window 712 may include NFC payment prompt information 712A (e.g., "Tap to pay"), payment discount information 712B (e.g., "Earn double points for this payment"), a payment control 712C, and a prompt information 712D corresponding to the payment control 712C (e.g., "Click the button to pay"). The payment prompt window 712 is used to prompt the user to make an NFC payment. For example, the payment discount information 712B may be obtained by the electronic device 100 from the cloud server 300 .

[0162] In some embodiments, the electronic device 100 may receive a signal acting on Figure 7B The user input of the payment control 712C in the payment prompt window 712 shown (for example, the user input is a touch operation, and the touch operation is, for example, a click operation), in response to the user input, the electronic device 100 can authenticate the user, and take face authentication as an example for explanation, for example, the electronic device 100 can capture the user's face image through the camera, and determine whether the user's face image matches the stored face image of the legitimate user, if they match, the face authentication passes, and if they do not match, the face authentication fails. When the face authentication passes, the electronic device 100 can switch from a locked state (i.e., an unlocked state) to an unlocked state (i.e., an unlocked state), for example, displaying in the unlocked state Figure 7C User interface 720 is shown.

[0163] like Figure 7CAs shown, after electronic device 100 interacts with payment device 200 through NFC signaling, it can obtain the NFC tag data of payment device 200. Based on the NFC tag data of payment device 200, electronic device 100 can determine a target payment application from one or more payment applications on electronic device 100 for payment and display a user interface 720 indicating payment in progress. In some examples, user interface 720 is the user interface of the target payment application. User interface 720 may include an identifier 721 of the target payment application, a payment prompt 722 (e.g., "Tap to pay"), and a payment window 723. The payment window 723 in user interface 720 may include a prompt 723A (e.g., "Paying in progress"), which is used to inform the user that electronic device 100 is in the process of making a payment. Optionally, payment window 723 may also include the name 723B of the target payment account (e.g., "K-Store").

[0164] like Figure 7D As shown, the electronic device 100 can communicate with the payment device 200 through short-range communication technology, thereby completing the payment with the payment device 200 using the target payment application. After the electronic device 100 completes the payment with the payment device 200, it can display a user interface 730 indicating that the payment is complete. In some examples, the user interface 730 is a user interface of the target payment application. The user interface 730 may include an identifier 721 of the target payment application, a payment prompt 722, and a payment window 723. The payment window 723 in the user interface 730 may include a payment success prompt 731, a payment amount 732 (e.g., "50 yuan"), the name of the target payment account 733 (e.g., "K-Store"), and a completion control 734. Among them, the payment success prompt 731 is used to prompt the user that the electronic device 100 has successfully paid. Not limited to Figure 7D The payment success prompt 731 shown, in a specific implementation, the payment success prompt can be one or more of a text prompt, an image prompt, an audio prompt, a vibration prompt, etc. The completion control 734 is used to trigger the electronic device 100 to close the payment completion user interface 730, for example, returning to the off-screen unlocked state, or returning to the lock screen interface, etc.

[0165] It is understandable that the electronic device 100 can display Figure 7B Before the lock screen interface 710 is displayed, the electronic device 100 interacts with the payment device 200 through NFC signaling and receives the NFC tag data sent by the payment device 200. Subsequently, the electronic device 100 can communicate with the payment device 200 through short-range communication technology. Figure 7B When the lock screen interface 710 is displayed, the user can pick up the electronic device 100 and move it away from the payment device 200. The user does not need to keep the electronic device 100 close to the payment device 200, which is more convenient for the user.

[0166] Not limited to the above embodiments, in other embodiments, if the electronic device 100 fails the facial authentication of the user, it may remain locked and the target payment application will not be started for payment. At this time, the electronic device 100 may output an authentication failure prompt, which is used to prompt the user that the authentication of the electronic device 100 has failed.

[0167] Not limited to the above embodiments, in other embodiments, if the payment between the electronic device 100 and the payment device 200 fails, the electronic device 100 may output a payment failure prompt, which is used to prompt the user that the payment of the electronic device 100 has failed.

[0168] The face authentication shown in the above embodiment is not limited. In other embodiments, the identity authentication performed when unlocking the state may also be fingerprint authentication, password authentication, iris authentication, voice authentication, palm print authentication, pattern authentication, gesture authentication, etc. The embodiment of the present application does not limit the specific method of identity authentication. For example, Figure 7E As shown, the identity authentication is password authentication or fingerprint authentication, so the electronic device 100 can respond to the Figure 7B The user input of the payment control 712C in the payment prompt window 712 shown displays the user interface 740 for identity authentication. When the electronic device 100 displays the user interface 740, it is still in a locked state. The user interface 740 may include a prompt message 741 (for example, "Please use a fingerprint or password to unlock"), a password input box 742, a password input keyboard 743, and a fingerprint recognition icon 744. Among them, when the user uses a password to unlock the electronic device 100, the password input keyboard 743 can be used to receive the user's input, and the lock screen password is entered in the password input box 742 according to the user's input. The electronic device 100 can verify the lock screen password entered by the user. When the user uses a fingerprint to unlock the electronic device 100, the fingerprint recognition icon 744 can be used to receive the user's touch operation, and the electronic device 100 collects the fingerprint of the user's finger that touches the fingerprint recognition icon 744, and the electronic device 100 can verify the collected user fingerprint. When the lock screen password verification or fingerprint verification is passed, the electronic device 100 switches from the locked state (i.e., unlocked state) to the unlocked state (i.e., unlocked state), and can use the target payment application and the payment device 200 to complete the payment, such as displaying Figure 7C User interface 720 showing payment in progress.

[0169] In some embodiments, after the electronic device 100 performs NFC signaling interaction with the payment receiving device 200, the electronic device 100 can determine the target payment application from one or more payment applications of the electronic device 100 to make payment, wherein the electronic device 100 can receive the payment amount from the payment receiving device 200, so the electronic device 100 can display Figure 7C As shown in the user interface 720 of payment in progress, the electronic device 100 can complete the payment of the payment amount with the payment device 200 without the user having to manually input the payment amount.

[0170] Not limited to this, in other embodiments, the user may also input the payment amount on the electronic device 100. Figure 7F As shown, after the electronic device 100 interacts with the payment device 200 through NFC signaling, it can determine the target payment application from one or more payment applications of the electronic device 100 for payment, and can display a user interface 750 for payment. In some examples, the user interface 750 is the user interface of the target payment application. The user interface 750 may include an identifier 721 of the target payment application, a payment prompt 722, and a payment window 723. The payment window 723 in the user interface 750 may include the name 751 of the target payment account (e.g., "K-Store"), a payment amount input box 752, a note input box 753, a numeric keypad 754, and a payment confirmation control 755. Among them, the numeric keypad 754 can be used to receive user input, and the payment amount (e.g., "50 yuan") can be entered in the payment amount input box 752 based on the user input. The note input box 753 can be used to display payment note information entered by the user. After the electronic device 100 receives the payment amount entered by the user in the payment amount input box 752, it can receive user input acting on the payment confirmation control 755 (for example, the user input is a touch operation, and the touch operation is, for example, a click operation). In response to the user input, the user interface 720 of payment in progress can be displayed, and the electronic device 100 can complete the payment of the payment amount entered by the above user with the payment receiving device 200.

[0171] Optionally, the electronic device 100 may respond to Figure 7B The user inputs the payment control 712C in the payment prompt window 712 shown in FIG. 7 , and performs identity authentication on the user, such as displaying Figure 7E The user interface 740 of the identity authentication is shown. If the identity authentication is passed, the electronic device 100 determines the target payment application to perform the payment application and displays Figure 7F Payment user interface 750 is shown.

[0172] In some embodiments, after the electronic device 100 interacts with the payment device 200 through NFC signaling, it can determine the target payment application from one or more payment applications of the electronic device 100 to make the payment. The target payment application of the electronic device 100 can complete the payment directly with the payment device 200 without performing payment verification on the user. For example, after the electronic device 100 receives the payment amount sent by the payment device 200, it displays Figure 7C The user interface 720 of the payment is shown, or the electronic device 100 is in Figure 7F The user interface 750 shown in FIG. 7 displays the payment amount after receiving the payment amount input by the user. Figure 7C User interface 720 showing payment in progress.

[0173] Not limited to this, in other embodiments, the target payment application of the electronic device 100 can perform payment verification on the user. Figure 7G As shown, after the electronic device 100 performs NFC signaling interaction with the payment device 200, it can determine the target payment application from one or more payment applications of the electronic device 100 to make payment, and can display the user interface 760 for payment verification after determining the payment amount. The user interface 760 may include an identifier 721 of the target payment application, a payment prompt 722, and a payment window 723. The payment window 723 in the user interface 760 may include the name 761 of the target payment account (for example, "K-Store"), the payment amount 762 (for example, "50 yuan"), a password input box 763, and a password input keyboard 764. Among them, the password input keyboard 764 can be used to receive user input, and enter the payment password in the password input box 763 according to the user input. The target payment application in the electronic device 100 can verify the payment password, and it can be displayed after the verification is passed. Figure 7C The user interface 720 of the payment process shown may output a verification failure prompt when the verification fails. The verification failure prompt is used to prompt the user that the payment password verification has failed.

[0174] Figure 7G The payment verification (i.e., password verification) shown is only for example. In other examples, payment verification can also be fingerprint verification, password verification, iris verification, voice verification, palm print verification, pattern verification, gesture verification, etc. The embodiments of this application do not limit the specific method of payment verification.

[0175] For example, the target payment application of electronic device 100 may determine whether to perform payment verification based on the target payment account logged in by the user in the target payment application. If the target payment account is set up for password-free payment and the payment amount does not exceed the password-free payment limit, the target payment application may not perform payment verification. If the target payment account is not set up for password-free payment or the payment amount exceeds the password-free payment limit, the target payment application may perform payment verification.

[0176] Not limited to the above embodiments, in other embodiments, from the time when the electronic device 100 in PICC mode is brought close to the card swiping area of ​​the payment device 200 to the time when the electronic device 100 uses the target payment application and the payment device 200 to complete the payment, the electronic device 100 can remain unlocked, for example, the screen remains off and unlocked, that is, the electronic device 100 can use the target payment application and the payment device 200 to complete the payment in the unlocked state without unlocking. In some examples, if the target payment account logged in by the user in the target payment application is set for password-free payment and the payment amount does not exceed the password-free payment limit, the electronic device 100 can use the target payment application and the payment device 200 to complete the payment in the unlocked state.

[0177] Not limited to the above embodiments, in other embodiments, the electronic device 100 can also be placed close to the card swiping area of ​​the payment device 200 when the screen is on and unlocked. The electronic device 100 can perform NFC signaling interaction with the payment device 200 in PCD mode in PICC mode, or the electronic device 100 can also perform NFC signaling interaction with the payment device 200 in PICC mode in PCD mode.

[0178] Not limited to the above embodiments, in other embodiments, the electronic device 100 may not perform identity authentication on the user. After the electronic device 100 determines the target payment application, it can launch the target payment application to make payment even without identity authentication, further reducing user operations and improving the efficiency of the user's payment using the electronic device 100.

[0179] It is understandable that based on the application scenario of the above example, the electronic device 100 can be placed close to the payment device 200 without displaying any NFC simulated card swiping interface, such as when the screen is off, locked, or the desktop is displayed, thereby entering the radio frequency field of the payment device 200. The electronic device 100 can interact with the payment device 200 through NFC signaling and select a target payment application. The electronic device 100 can use the target payment application to complete the payment with the payment device 200. In this way, the electronic device 100 can complete the payment without requiring excessive user operation, thereby improving the efficiency of the user's payment using the electronic device 100.

[0180] Next, the payment method provided in the embodiment of the present application is introduced.

[0181] Figure 8 This is a flow chart of a payment method provided in an embodiment of the present application.

[0182] like Figure 8 As shown, the payment method can be applied to an NFC system including an electronic device 100 and a payment device 200, for example, the NFC system is Figure 2 The NFC system 10 shown, for example, the electronic device 100 is Figure 4 The electronic device 100 shown, for example, the electronic device 100 and the payment device 200 are Figure 5 The electronic device 100 and the payment device 200 in the payment system 20 are shown. The electronic device 100 can support both PICC mode and PCD mode. The payment device 200 can support both PCD mode and PICC mode.

[0183] Figure 8 The payment methods shown may include but are not limited to the following steps:

[0184] S101: The payment device 200 is in PCD mode.

[0185] In some embodiments, the NFC module of the payment device 200 can support both PCD mode and PICC mode, and the NFC module of the payment device 200 can switch between PCD mode and PICC mode. In some examples, in S101, the NFC module of the payment device 200 can switch to PCD mode.

[0186] In other embodiments, the NFC module of the payment device 200 may only operate in PCD mode. The payment device 200 may also include an NFC tag device, which may operate in PICC mode. Therefore, in S101, the NFC module of the payment device 200 operates in PCD mode.

[0187] S102: The electronic device 100 is in PICC mode.

[0188] In some embodiments, after the electronic device 100 turns on the NFC function, the electronic device 100 can be in the PICC mode by default when it is in the unlocked state, or it can be in the PICC mode or PCD mode in a time-sharing manner when it is in the unlocked state (i.e., it can switch between the PICC mode and the PCD mode). For example, the electronic device 100 is a device such as a mobile phone. Therefore, in S102, the electronic device 100 can be in the PICC mode by default when it is in the unlocked state, or the electronic device 100 can be in the PICC mode in a time-sharing manner when it is in the unlocked state.

[0189] In some embodiments, after the NFC function is enabled, the electronic device 100 may be in PICC mode by default. For example, the electronic device 100 may be in PICC mode by default in both the unlocked and unlocked states. For example, the electronic device 100 may be a wearable device such as a smartwatch. Therefore, in S102, the electronic device 100 may be in PICC mode by default.

[0190] In some examples, the unlocked state includes a screen-off state or a screen-lit locked state, etc. In the screen-off state, the electronic device 100 can completely turn off the display screen, that is, the screen-off state includes the screen-off state, or the electronic device 100 can display content in a partial area of ​​the display screen using an always on display (AOD) technology in the screen-off state, that is, the screen-off state includes the AOD state.

[0191] S103 : The electronic device 100 enters the radio frequency field of the payment device 200 .

[0192] In some embodiments, the user can hold the electronic device 100 and move the NFC module on the electronic device 100 close to the card swiping area of ​​the payment device 200, thereby allowing the electronic device 100 to enter the radio frequency field of the payment device 200. Alternatively, the user can also hold the payment device 200 and move the card swiping area of ​​the payment device 200 close to the location of the NFC module on the electronic device 100, thereby allowing the electronic device 100 to enter the radio frequency field of the payment device 200.

[0193] S104: The payment device 200 sends a first carrier wave to the electronic device 100, where the first carrier wave has a first coding feature.

[0194] In some embodiments, when the payment device 200 is in PCD mode, it can transmit a first carrier wave, for example, by broadcasting the first carrier wave. When the electronic device 100 in PICC mode enters the radio frequency field of the payment device 200, it can receive the first carrier wave transmitted by the payment device 200 in PCD mode. The first carrier wave can be understood as a special detection signal transmitted by the payment device 200 in PCD mode.

[0195] In some embodiments, the first carrier may be transmitted at a physical layer, and the first carrier may have a first coding characteristic of the physical layer.

[0196] In some embodiments, the payment device 200 can send a first carrier when it is in PCD mode. In other embodiments, the payment device 200 can also send multiple first carriers in chronological order when it is in PCD mode. The time interval between two adjacent first carriers in the multiple first carriers can be a fixed value, that is, the payment device 200 can send the first carrier periodically. Alternatively, the time interval between two adjacent first carriers in the multiple first carriers is not a fixed value. For example, the payment device 200 sends three first carriers in chronological order from early to late, the time interval between the first first carrier and the second first carrier is duration 1, the time interval between the second first carrier and the third first carrier is duration 2, and duration 1 is different from duration 2.

[0197] In some embodiments, the first carrier includes N subcarriers, where N is a positive integer greater than 1. The coding characteristics of the first carrier are determined based on one or more of the following: the amplitude of the subcarrier, the duration of the subcarrier, the time interval between two adjacent subcarriers, and the value of N. The first coding characteristics of the first carrier include one or more of the following: the amplitude of each subcarrier in the N subcarriers is a first amplitude, the duration of each subcarrier in the N subcarriers is a first duration, the time interval between any two adjacent subcarriers in the N subcarriers is a first time interval, and N is a preset N1 (N1 is a positive integer greater than 1).

[0198] Not limited to the first coding feature shown in the above embodiment, in other embodiments, the amplitudes of different subcarriers among the N subcarriers may also be different. For example, the first coding feature includes: the amplitudes of some subcarriers among the N subcarriers are the second amplitude, and the amplitudes of other subcarriers are the third amplitude. In other embodiments, the durations of different subcarriers among the N subcarriers may also be different. For example, the first coding feature includes: the duration of some subcarriers among the N subcarriers is duration 3, and the duration of other subcarriers is duration 4. In other embodiments, the time intervals between different adjacent subcarriers among the N subcarriers may also be different. For example, the first coding feature includes: the time interval between some adjacent subcarriers among the N subcarriers is the second time interval, and the time interval between other adjacent subcarriers is the third time interval. The embodiments of the present application do not limit the specific content of the first coding feature.

[0199] Not limited to the above embodiments, in other embodiments, the coding characteristics of the first carrier can also be determined based on other characteristics of the subcarrier. The embodiments of the present application do not limit the specific parameters used to determine the coding characteristics.

[0200] The example of the first carrier wave sent by the payment device 200 can be found in the following Figure 10 .

[0201] In some embodiments, after the electronic device 100 receives the first carrier wave with the first coding feature sent by the payment device 200, it can be determined that the payment device 200 supports the target payment process, and thus can determine to perform the target payment process with the payment device 200. The target payment process may include: the electronic device 100 obtains the NFC tag data of the payment device 200, and uses the target payment application corresponding to the NFC tag data and the payment device 200 to complete the payment. An example of the target payment process can be found in Figure 8 S113-S117 and Figure 9 It can be understood that the purpose of the payment device 200 sending the first carrier is to perform a target payment process with the opposite device (ie, the device that receives and recognizes the first carrier).

[0202] S105: The electronic device 100 does not start the wallet application after receiving the first carrier.

[0203] S106: After receiving the first carrier, the electronic device 100 is in the PCD mode.

[0204] In the current NFC communication process, the electronic device 100 in PICC mode can receive a first card search request sent by the PCD device after entering the radio frequency field of the PCD device, and start the wallet application after receiving the first card search request, thereby facilitating the subsequent use of the NFC simulated card in the wallet application for NFC communication, and displaying the card swiping interface of the NFC simulated card in the wallet application to provide a user experience of fast card swiping.

[0205] The first card search request may be used to indicate that the PCD device supports the first NFC protocol. In some examples, if the first NFC protocol is a Type A NFC protocol, the first card search request may be a Type A request command (REQA). In some examples, if the first NFC protocol is a Type B NFC protocol, the first card search request may be a Type B request command (REQB). In some examples, if the first NFC protocol is a Type F NFC protocol, the first card search request may be an extended detection request (SENSF_REQ).

[0206] However, in the embodiment of the present application, the payment device 200 in PCD mode will not send the first card search request, but will send the first carrier. After the electronic device 100 receives the first carrier, it can identify that the first carrier has the first coding feature. The electronic device 100 can determine the target payment process with the payment device 200 based on the first carrier, rather than performing the NFC simulated card swiping business in the electronic device 100 with the payment device 200. Therefore, the electronic device 100 will not start the wallet application, avoid displaying the NFC simulated card swiping interface in the wallet application, and the electronic device 100 will change from being in PICC mode to being in PCD mode, so as to perform "new NFC signaling interaction" with the payment device 200 in the "new mode" (PCD mode), and avoid continuing to perform NFC signaling interaction related to the NFC simulated card with the payment device 200 in the "old mode" (PICC mode).

[0207] The first card search request and the first carrier are different. In some embodiments, the first card search request may be an NFC signal sent at the access layer, and the first carrier may be an NFC signal sent at the physical layer. In some embodiments, the first card search request may be a modulated signal, indicating that the PCD device sending the first card search request supports the first NFC protocol. The first carrier may be an unmodulated signal, indicating no information. In some examples, the first card search request may include multiple bit fields, while the first carrier does not include a bit field. When sending the first card search request, the PCD device may first generate multiple bit fields, modulate these multiple bit fields into a corresponding carrier, and then transmit the carrier. After receiving the modulated carrier sent by the PCD device, the PICC device may demodulate and obtain the multiple bit fields, thereby identifying the multiple bit fields. When transmitting the first carrier, the PCD device may directly generate and transmit the first carrier at the physical layer. Upon receiving the first carrier sent by the PCD device, the PICC device does not need to demodulate the first carrier, but instead directly identifies the coding characteristics of the first carrier.

[0208] The description of the first carrier shown in the embodiment of the present application is for example only. In other examples, the first carrier may also be an NFC signal sent at the access layer. In other examples, the first carrier may also be a modulated signal. In other examples, the first carrier may also indicate information, such as indicating that the electronic device 100 is in PCD mode (such as instructing the electronic device 100 to turn on PCD mode). In other examples, the first coding feature of the first carrier may also be other features, such as the field included in the first carrier has the first coding feature. The embodiment of the present application does not limit the specific form and content of the first carrier.

[0209] In some embodiments, the electronic device 100 may be in the PICC mode by default when it is not unlocked in S102, or the electronic device 100 may be in the PICC mode by default after the NFC function is enabled in S102. Therefore, in S106, the electronic device 100 may enable the PCD mode after receiving the first carrier wave having the first coding feature, and the electronic device 100 may subsequently switch between the PICC mode and the PCD mode regardless of whether it is in the unlocked state.

[0210] In some embodiments, the electronic device 100 may be in the unlocked state and in the PICC mode in a time-sharing manner in S102. Therefore, in S106, after receiving the first carrier with the first coding feature, the electronic device 100 may be in the PCD mode in a time-sharing manner.

[0211] S107: After sending the first carrier, the payment device 200 switches from the PCD mode to the PICC mode.

[0212] In some embodiments, the payment device 200 can be in PCD mode or PICC mode in a time-sharing manner. When in PCD mode, the payment device 200 can transmit one or N first carrier waves and then switch to PICC mode in a time-sharing manner. Optionally, if the payment device 200 switches to PICC mode in a time-sharing manner and does not receive a valid NFC signal (e.g., the first response, first card search request, or Probe frame described below) within a preset time period, it can switch to PCD mode in a time-sharing manner and continue to transmit the first carrier wave.

[0213] In some embodiments, the NFC module of the payment device 200 may support both PCD mode and PICC mode. Therefore, in S107 , the NFC module of the payment device 200 may switch from PCD mode to PICC mode.

[0214] In other embodiments, the NFC module of the payment device 200 may only operate in PCD mode. The payment device 200 may also include an NFC tag device, which may operate in PICC mode. Therefore, in S107, the NFC tag device on the payment device 200 may operate in PICC mode.

[0215] It can be understood that in order to carry out the target payment process with the counterpart device (i.e., the device that receives and identifies the first carrier), the payment device 200 can switch from PCD mode to PICC mode after sending the first carrier, so as to perform "new NFC signaling interaction" with the electronic device 100 in the "new mode" (PICC mode), and avoid continuing to perform NFC signaling interaction related to the NFC simulated card with the electronic device 100 in PICC mode in the "old mode" (PCD mode).

[0216] S108 : The payment device 200 enters the radio frequency field of the electronic device 100 .

[0217] In some embodiments, electronic device 100 is in PCD mode at S106. While in PCD mode, electronic device 100 can generate a radio frequency field. Payment device 200 switches to PICC mode at S107. Because the user has already positioned the NFC module on electronic device 100 and the card swipe area of ​​payment device 200 close to each other at S103, after electronic device 100 is in PCD mode and payment device 200 switches to PICC mode, payment device 200 is within the radio frequency field of electronic device 100.

[0218] S109: The electronic device 100 sends a first response to the payment device 200, indicating that the first carrier is successfully identified.

[0219] In some embodiments, the electronic device 100 in the PCD mode may send a first response to the payment terminal 200 in the PICC mode, where the first response indicates successful identification of the first carrier.

[0220] In some embodiments, the first response is an NFC signal sent at the access layer. In some embodiments, the first response is a modulated signal, and the first response may indicate successful identification of the first carrier. Without limitation, in other embodiments, the first response may also be a second carrier, and the second carrier may have a second coding feature, and the description of the second coding feature is similar to the description of the first coding feature. Optionally, the second carrier may be an unmodulated signal. Optionally, the second carrier may be an NFC signal sent at the physical layer, and the second carrier may not indicate information. The embodiments of the present application do not limit the form and content of the second carrier.

[0221] In some embodiments, after receiving the first response sent by the electronic device 100, the payment device 200 may determine that the electronic device 100 supports the target payment process, and thus may determine to perform the target payment process with the electronic device 100.

[0222] Understandably, after the electronic device 100 switches from PICC mode to PCD mode and the payment device 200 switches from PCD mode to PICC mode, the electronic device 100 can send a first response to the payment device 200 indicating successful identification of the first carrier, rather than sending the first response to the payment device 200 in the "old mode" (PICC mode). This avoids the need to continue NFC signaling interactions related to the NFC emulated card with the payment device 200 in the "old mode" (PICC mode) in order to send the first response. Furthermore, by transmitting the first response after the electronic device 100 and the payment device 200 change modes, rather than directly in the "old mode" (PICC mode), the changes to the NFC signal and internal device logic are minimal, improving feasibility.

[0223] Among them, S101-S109 implements the handshake negotiation between the electronic device 100 and the payment device 200. After the handshake negotiation is successful (i.e., after S109), the electronic device 100 can determine to perform the target payment process with the payment device 200, and the payment device 200 can also determine to perform the target payment process with the electronic device 100. Therefore, both the electronic device 100 and the payment device 200 can switch modes to perform "new NFC signaling interaction" (including NFC signaling interaction at the access layer) under the "new mode", thereby completing the target payment process. For specific implementation, please refer to S110-S117. It can be understood that the electronic device 100 and the payment device 200 perform the target payment process after changing the mode, rather than directly performing the target payment process in the "old mode" after transmitting the first response. This requires less change to the NFC signal and the internal logic of the device, and is more feasible.

[0224] S110: After sending the first response, the electronic device 100 switches from the PCD mode to the PICC mode.

[0225] In some embodiments, the electronic device 100 may enable PCD mode in S106, so after S106, the electronic device 100 may switch between PICC mode and PCD mode. In S110, after sending the first response, the electronic device 100 switches from PCD mode to PICC mode to perform a "new NFC signaling interaction" (including NFC signaling interaction at the access layer) with the payment device 200 in the "new mode" (PICC mode), thereby completing the target payment process. For specific implementation, see S112-S117.

[0226] In some embodiments, the electronic device 100 may be in the PCD mode in a time-sharing manner in S106. In S110, after sending the first response, the electronic device 100 may be in the PICC mode in a time-sharing manner.

[0227] S111: After receiving the first response, the payment device 200 switches from the PICC mode to the PCD mode.

[0228] In some embodiments, the NFC module of the payment device 200 may support both the PCD mode and the PICC mode. Therefore, in S111 , the NFC module of the payment device 200 may switch from the PICC mode to the PCD mode.

[0229] It can be understood that after receiving the first response, the payment device 200 can switch from PICC mode to PCD mode to perform "new NFC signaling interaction" (including NFC signaling interaction at the access layer) with the electronic device 100 in the "new mode" (PCD mode), thereby completing the target payment process. For specific implementation, please refer to S112-S117.

[0230] In other embodiments, the NFC module of the payment device 200 may only operate in PCD mode. The payment device 200 may also include an NFC tag device, which may operate in PICC mode. Therefore, in S111, the NFC module of the payment device 200 operates in PCD mode.

[0231] S112 : The electronic device 100 enters the radio frequency field of the payment device 200 .

[0232] In some embodiments, the payment device 200 switches to PCD mode in S111. While in PCD mode, the payment device 200 can generate a radio frequency field. The electronic device 100 switches to PICC mode in S110. Because the user has brought the NFC module on the electronic device 100 and the card swipe area of ​​the payment device 200 into close proximity in S103, after the payment device 200 switches to PCD mode and the electronic device 100 switches to PICC mode, the electronic device 100 is within the radio frequency field of the payment device 200.

[0233] S113: The payment device 200 interacts with the electronic device 100 via NFC signaling at the access layer.

[0234] In some embodiments, the payment device 200 in PCD mode performs NFC signaling interaction at the access layer with the electronic device 100 in PICC mode. Figure 11 and Figure 12 After the payment device 200 in PCD mode and the electronic device 100 in PICC mode complete the NFC signaling interaction at the access layer, they can perform NFC signaling interaction at the application layer, that is, execute S114-S117 to complete the payment.

[0235] S114: The payment receiving device 200 sends the NFC tag data of the payment receiving device 200 (including the identifiers of one or more payment applications supported by the payment receiving device 200 and the information of the first order) to the electronic device 100.

[0236] In some embodiments, the payment device 200 in PCD mode can send NFC tag data of the payment device 200 to the electronic device 100 in PICC mode. The NFC tag data includes the identifiers of one or more payment applications supported by the payment device 200. The NFC tag data includes information about the first order currently being paid. The information about the first order may include, for example, one or more of the following: the identifier of the first order, the payment amount of the first order, and the payment account information of the first order. The payment account information of the first order may include the payment account information of the one or more payment applications mentioned above. The payment account information may include, for example, one or more of the following: the name of the payment account, the profile picture of the payment account, the introduction information of the payment account, the identifier of the payment account, etc.

[0237] S115 : The electronic device 100 determines a target payment application from the one or more payment applications supported by the payment receiving device 200 based on the identifiers of the one or more payment applications supported by the payment receiving device 200 .

[0238] S116: The electronic device 100 starts the target payment application and displays the payment interface of the first order through the target payment application.

[0239] In some embodiments, the NFC tag data includes an identifier of a payment application supported by the payment receiving device 200. The electronic device 100 may determine the payment application included in the NFC tag data as the target payment application. A specific example is shown below:

[0240] Case 1.1: If the applications installed on the electronic device 100 include a target payment application, the electronic device 100 may start the target payment application.

[0241] Case 1.2: If the target payment application is not included in the applications installed on the electronic device 100, the electronic device 100 may not execute subsequent steps, and the electronic device 100 may output an installation prompt, which is used to prompt the user to install the target payment application on the electronic device 100 for payment.

[0242] In other embodiments, the NFC tag data includes identifiers of multiple payment applications supported by the payment device 200. Specific examples are as follows:

[0243] In case 2.1, if only one payment application among the applications installed on electronic device 100 is among the multiple payment applications supported by payment receiving device 200, electronic device 100 may determine the payment application installed on electronic device 100 as the target payment application and launch the target payment application. For example, if the NFC tag data includes the identifiers of payment application A1 and payment application A2, and electronic device 100 has payment application A1 installed but not payment application A2, electronic device 100 may determine payment application A1 as the target payment application.

[0244] Case 2.2, among the applications installed on the electronic device 100, there are multiple payment applications (which may be referred to as candidate payment applications) that belong to the multiple payment applications supported by the above-mentioned payment device 200, then the electronic device 100 can determine whether the multiple candidate payment applications include the default payment application set by the user. If the multiple candidate payment applications include the default payment application set by the user, the electronic device 100 can determine the default payment application as the target payment application and start the target payment application. If the multiple candidate payment applications do not include the default payment application set by the user, the electronic device 100 can select a candidate payment application from the multiple candidate payment applications according to preset rules (such as random selection) to determine it as the target payment application, and start the target payment application.

[0245] For example, the NFC tag data includes the identifier of payment application A1 and the identifier of payment application A2. The electronic device 100 has installed payment application A1, payment application A2 and payment application A3. If the default payment application set by the user is payment application A1, the electronic device 100 can start payment application A1 for payment. If the default payment application set by the user is payment application A3, the electronic device 100 can start payment application A1 or payment application A2 for payment.

[0246] Not limited to the preset rules of the above examples, in other examples, the preset rules may also be to determine the candidate payment applications that the user has used in the past as the target payment application. For example, if the multiple candidate payment applications do not include the default payment application set by the user, the electronic device 100 can select the candidate payment application used by the user during the last payment from these multiple candidate payment applications as the target payment application, and start the target payment application. In other examples, the preset rules may also be to determine the candidate payment application that the user has used the most times for payment within a specified time period as the target payment application. The embodiments of the present application do not limit the specific content of the preset rules.

[0247] In some embodiments, the electronic device 100 can display the payment interface of the first order through the target payment application based on the information of the first order included in the NFC tag data. The payment interface of the first order may include the information of the first order, such as the payment account information of the target payment application, the payment amount of the first order, etc. An example of the payment interface of the first order can be found in Figure 7C The user interface 720 shown, Figure 7F The user interface 750 shown, Figure 7G User interface 760 is shown.

[0248] In some embodiments, the electronic device 100 may display payment prompt information before displaying the payment interface of the first order through the target payment application. For specific examples, see Figure 7B The payment prompt window 712 is shown. Optionally, the electronic device 100 may display the payment prompt information before determining and launching the target payment application. Optionally, the electronic device 100 may display the payment prompt information after receiving the first carrier. Optionally, the electronic device 100 is in an unlocked state in S102, and the electronic device 100 may display the payment prompt information while in the unlocked state.

[0249] In some embodiments, the electronic device 100 is in an unlocked state in S102. Before the electronic device displays the payment interface of the first order through the target payment application, the electronic device can authenticate the user, for example, in response to the user's input of the payment prompt information (for triggering payment), authenticate the user, wherein the input is, for example, Figure 7B The user input of the payment control 712C in the payment prompt window 712 is shown. Figures 7A-7G For an explanation of identity authentication, see the user interface example of identity authentication. Figure 7E User interface 740 is shown. If the identity authentication is successful, the electronic device 100 switches from an unlocked state to an unlocked state, and in the unlocked state, the payment interface for the first order is displayed through the target payment application. If the identity authentication is unsuccessful, the electronic device 100 remains unlocked, and the target payment application is not launched, nor is the payment interface for the first order displayed through the target payment application.

[0250] In some embodiments, the electronic device 100 can communicate with the cloud server 300 via a wired or wireless manner, thereby obtaining payment preferential information of the payment application from the cloud server 300. The payment preferential information may include payment preferential information for all users, and may also include payment preferential information for users of the electronic device 100. The payment preferential information may include payment preferential information of the target payment application, and may also include payment preferential information of other payment applications, etc. The electronic device 100 may display the obtained payment preferential information. In some examples, the electronic device 100 may display the payment preferential information on the payment interface of the first order. In other examples, the electronic device 100 may also display the payment preferential information before displaying the payment interface of the first order, for example, displaying the payment preferential information when displaying the above-mentioned payment prompt information. For specific examples, please refer to Figure 7B Payment prompt window 712 is shown.

[0251] In some embodiments, when the electronic device 100 displays the payment interface for the first order, it can receive the user's input for payment of the first order. In response to the user input, the electronic device 100 can perform the payment process for the first order with the payment device 200. Optionally, in response to the user input, the electronic device 100 can perform payment verification on the user. For instructions on payment verification, please refer to Figures 7A-7G For instructions on payment verification, see the payment verification user interface example. Figure 7G User interface 760 is shown. If the payment verification is successful, the electronic device 100 can perform the payment process of the first order with the payment device 200. If the payment verification is unsuccessful, the payment process of the first order may not be performed.

[0252] S117: The payment device 200 and the electronic device 100 perform the payment process for the first order.

[0253] In some embodiments, the payment device 200 in PCD mode and the electronic device 100 in PICC mode can perform the payment process of the first order through NFC signaling interaction. Implementation examples in different situations are shown below.

[0254] In scenario 3.1, the payment device 200 may send payment information to the cloud server 300 (e.g., the server of the target payment application) to execute the payment process, thereby completing the payment process between the payment device 200 and the electronic device 100. The payment process in scenario 3.1 may include, but is not limited to, the following steps:

[0255] In step 1 of situation 3.1, after receiving the NFC tag data sent by the payment device 200, the electronic device 100 can send a first payment command to the payment device 200. The first payment command carries the identifier of the target payment application and the identifier of the target payment account. The optional first payment command can also carry one or more of the payment voucher of the first order (used to prove that the user has paid the first order), the payment amount of the first order, and the payment note information. Optionally, the first payment command is used to request the payment device 200 to execute the payment process. In some examples, different payment applications correspond to different payment accounts. After the electronic device 100 determines the target payment application, it can determine the identifier of the target payment account corresponding to the target payment application.

[0256] In step 2 of scenario 3.1, after receiving the first payment command sent by electronic device 100, payment device 200 may send payment information to cloud server 300 (e.g., the server of the target payment application) to execute the payment process. The payment information may include the payment amount of the first order, the identifier of the target payment account, the identifier of the target payment account, and optionally, the payment voucher for the first order.

[0257] In step 3 of scenario 3.1, cloud server 300 may, based on the payment information, deduct the payment amount from the balance of the target payment account and add the payment amount to the balance of the target payment receiving account. If cloud server 300 successfully transfers the payment amount from the balance of the target payment account to the target payment receiving account, it may send a payment completion notification to the merchant's payment receiving device 200. If the cloud server fails to transfer the payment amount from the balance of the target payment account to the target payment receiving account, it may send a payment failure notification to the merchant's payment receiving device 200. In some embodiments, if payment receiving device 200 receives the payment completion notification from cloud server 300, it may output a payment completion prompt to notify the merchant that the payment amount has been successfully collected. If payment receiving device 200 receives a payment failure notification from cloud server 300, it may output a payment failure prompt to notify the merchant that the payment has failed. The payment completion prompt / payment failure prompt may be a text prompt, an audio prompt, an image prompt, a mechanical vibration prompt, an indicator light prompt, or the like.

[0258] In some embodiments, after receiving the payment information, the cloud server 300 may send a deduction notification to the electronic device 100. After receiving the deduction notification, the electronic device 100 may perform payment verification on the user. If the electronic device 100 successfully verifies the user's payment, it may send a verification success notification to the cloud server 300. Upon receiving the verification success notification, the cloud server 300 deducts the payment amount from the balance of the target payment account and adds the payment amount to the balance of the target receiving account. Otherwise, the payment amount is not transferred from the balance of the target payment account to the target receiving account.

[0259] In step 4 of situation 3.1, if the payment device 200 receives the payment completion notification sent by the cloud server 300, it can send a first payment response to the electronic device 100. The first payment response carries a first payment result, and the first payment result is used to indicate that the payment is successful. After receiving the first payment response carrying the first payment result, the electronic device 100 can output a payment completion prompt. The payment completion prompt can be used to indicate that the payment is successful. For example, the electronic device 100 can display Figure 7D User interface 730 is shown. If payment device 200 receives a payment failure notification from cloud server 300, it can send a first payment response to electronic device 100. This first payment response carries a second payment result, which indicates a payment failure. After receiving the first payment response carrying the second payment result, electronic device 100 can output a payment failure prompt, which can be used to indicate the payment failure.

[0260] In some embodiments, the cloud server 300 may also send a payment completion notification to the electronic device 100, and upon receiving the payment completion notification, the electronic device 100 may output a payment completion prompt. Alternatively, the cloud server 300 may send a payment failure notification to the electronic device 100, and upon receiving the payment failure notification, the electronic device 100 may output a payment failure prompt. Optionally, step 4 of scenario 3.1 is optional.

[0261] In case 3.1, the payment amount of the first order is confirmed as follows:

[0262] In one possible implementation, the payment amount can be determined by payment receiving device 200. Payment receiving device 200 can receive the payment amount entered by the merchant, or payment receiving device 200 can independently determine the payment amount based on the price information of the goods purchased by the user. Optionally, payment receiving device 200 can send the payment amount to electronic device 100, for example, by including the payment amount in the NFC tag data shown in S114.

[0263] In another possible implementation, the payment amount can be determined by the electronic device 100, so the electronic device 100 does not need to receive the payment amount sent by the payment device 200. The electronic device 100 can receive the payment amount input by the user after starting the target payment application, for example, when displaying Figure 7F The user interface 750 shown is for receiving the payment amount input by the user. Optionally, the electronic device 100 can send the payment amount to the payment receiving device 200, for example, by including the payment amount in the first payment command shown in step 2 of scenario 3.1.

[0264] In scenario 3.2, the electronic device 100 may send payment information to the cloud server 300 (e.g., the server of the target payment application) to execute the payment process, thereby completing the payment process between the payment receiving device 200 and the electronic device 100. The payment process in scenario 3.2 may include, but is not limited to, the following steps:

[0265] In step 1 of scenario 3.2, after receiving the NFC tag data sent by the payment device 200, the electronic device 100 can send payment information to the cloud server 300 (e.g., the server of the target payment application) to execute the payment process. The payment information may include the payment amount of the first order, the identifier of the target payment account, the identifier of the target payment account, and optionally, the payment voucher for the first order.

[0266] In step 2 of case 3.2, the cloud server 300 may deduct the payment amount from the balance of the target payment account based on the payment information, and increase the payment amount in the balance of the target payment account. If the cloud server 300 successfully transfers the payment amount from the balance of the target payment account to the target payment account, a payment completion notification may be sent to the electronic device 100. If the cloud server fails to transfer the payment amount from the balance of the target payment account to the target payment account, a payment failure notification may be sent to the electronic device 100. In some embodiments, if the electronic device 100 receives the payment completion notification sent by the cloud server 300, a payment completion prompt may be output, which may be used to prompt that the payment is successful. For example, the electronic device 100 may display Figure 7D The user interface 730 shown. If the electronic device 100 receives the payment failure notification sent by the cloud server 300, it can output a payment failure prompt, which can be used to prompt the payment failure.

[0267] In some embodiments, after receiving the payment information, the cloud server 300 may send a deduction notification to the electronic device 100. After receiving the deduction notification, the electronic device 100 may perform payment verification on the user. If the electronic device 100 successfully verifies the user's payment, it may send a verification success notification to the cloud server 300. Upon receiving the verification success notification, the cloud server 300 deducts the payment amount from the balance of the target payment account and adds the payment amount to the balance of the target receiving account. Otherwise, the payment amount is not transferred from the balance of the target payment account to the target receiving account.

[0268] In step 3 of scenario 3.2, if the electronic device 100 receives a payment completion notification from the cloud server 300, it may send a second payment response to the payment device 200. This second payment response carries a third payment result, indicating successful payment. Upon receiving the second payment response carrying the third payment result, the payment device 200 may output a payment completion notification, notifying the merchant that the payment amount has been successfully collected. If the electronic device 100 receives a payment failure notification from the cloud server 300, it may send a second payment response to the payment device 200. This second payment response carries a fourth payment result, indicating a payment failure. Upon receiving the second payment response carrying the fourth payment result, the payment device 200 may output a payment failure notification, notifying the merchant of the payment failure. The payment completion / failure notification may include text, audio, image, mechanical vibration, or indicator light.

[0269] In some embodiments, the cloud server 300 may also send a payment completion notification to the payment receiving device 200. Upon receiving the payment completion notification, the payment receiving device 200 may output a payment completion prompt. Alternatively, the cloud server 300 may send a payment failure notification to the payment receiving device 200. Upon receiving the payment failure notification, the payment receiving device 200 may output a payment failure prompt. Optionally, step 3 of scenario 3.2 is optional.

[0270] Among them, in case 3.2, the payment amount of the first order is confirmed as follows:

[0271] In one possible implementation, the payment amount can be determined by payment device 200. Payment device 200 can receive the payment amount entered by the merchant, or it can independently determine the payment amount based on the price information of the goods purchased by the user. Payment device 200 can send the payment amount to electronic device 100 before step 1 of scenario 3.2, for example, by including the payment amount in the NFC tag data shown in S114.

[0272] In another possible implementation, the payment amount can be determined by the electronic device 100, so the electronic device 100 does not need to receive the payment amount sent by the payment device 200. The electronic device 100 can receive the payment amount input by the user after starting the target payment application, for example, when displaying Figure 7F The user interface 750 shown is for receiving the payment amount input by the user. Optionally, the electronic device 100 can send the payment amount to the payment receiving device 200, for example, by carrying the payment amount in the second payment response shown in step 3 of scenario 3.2.

[0273] Not limited to Figure 8 In the embodiment shown in S117 of FIG. 1 , in other embodiments, the payment device 200 and the electronic device 100 may also perform the payment process of the first order through other wireless communication technologies other than NFC. For example, other wireless communication technologies other than NFC include but are not limited to one or more of Bluetooth, Wi-Fi, UWB, etc. Therefore, after the electronic device 100 receives the NFC tag data sent by the payment device 200, for example, the electronic device 100 displays Figure 7B When the user interface 710 is displayed, or when the electronic device 100 authenticates the user, or when the electronic device 100 displays the user interface of the target payment application, the user can pick up the electronic device 100 and move it away from the payment device 200. In this way, the electronic device 100 does not need to be kept close to the payment device 200, and when the user needs to enter identity authentication information or payment verification information on the electronic device 100, the electronic device 100 can be brought back to the user, thereby improving the security of the user's payment.

[0274] Figure 9 This is a flow chart of another payment method provided in an embodiment of the present application.

[0275] like Figure 9 As shown, the payment method can be applied to an NFC system including an electronic device 100 and a payment device 200, for example, the NFC system is Figure 2 The NFC system 10 shown, for example, the electronic device 100 is Figure 4 The electronic device 100 shown, for example, the electronic device 100 and the payment device 200 are Figure 5 The electronic device 100 and the payment device 200 in the payment system 20 are shown. The electronic device 100 can support both PICC mode and PCD mode. The payment device 200 can support both PCD mode and PICC mode.

[0276] Figure 9 The payment methods shown may include but are not limited to the following steps:

[0277] S201: The payment device 200 is in PCD mode.

[0278] S202: The electronic device 100 is in PICC mode.

[0279] S203 : The electronic device 100 enters the radio frequency field of the payment device 200 .

[0280] S204: The payment device 200 sends a first carrier wave to the electronic device 100, where the first carrier wave has a first coding feature.

[0281] S205: The electronic device 100 does not start the wallet application after receiving the first carrier.

[0282] S206: The electronic device 100 is in the PCD mode after receiving the first carrier.

[0283] S207: After sending the first carrier, the payment device 200 switches from the PCD mode to the PICC mode.

[0284] S208 : The payment device 200 enters the radio frequency field of the electronic device 100 .

[0285] Figure 9 S201-S208 and Figure 8 Similar to S101-S108, see Figure 8 The description of S101-S108 will not be repeated here.

[0286] in, Figure 9 After S201-S204, the electronic device 100 can determine to perform the target payment process with the payment receiving device 200, and the payment receiving device 200 can determine to perform the target payment process with the electronic device 100 that receives the first carrier by default. Therefore, the electronic device 100 can change from being in PICC mode to being in PCD mode (i.e., executing Figure 9 The payment device 200 can switch from PCD mode to PICC mode (i.e., execute S206). Figure 9 S207) to perform "new NFC signaling interaction" (including NFC signaling interaction at the access layer) under the "new mode" to complete the target payment process. For specific implementation, please refer to Figure 9 It can be understood that the electronic device 100 and the payment device 200 perform the target payment process after changing the mode, rather than directly performing the target payment process in the "old mode" after transmitting the first carrier. This requires less change to the NFC signal and the internal logic of the device, and is more feasible.

[0287] S209: The payment device 200 interacts with the electronic device 100 via NFC signaling at the access layer.

[0288] In some embodiments, the electronic device 100 in PCD mode and the payment device 200 in PICC mode perform NFC signaling interaction at the access layer. An example of NFC signaling interaction at the access layer can be found below. Figure 11 and Figure 12 After the electronic device 100 in PCD mode and the payment device 200 in PICC mode complete the NFC signaling interaction at the access layer, they can perform NFC signaling interaction at the application layer, that is, execute S210-S213 to complete the payment.

[0289] S210 : The payment receiving device 200 sends the NFC tag data of the payment receiving device 200 (including the identifiers of one or more payment applications supported by the payment receiving device 200 and the information of the first order) to the electronic device 100 .

[0290] In some embodiments, the payment device 200 in PICC mode can transmit NFC tag data of the payment device 200 to the electronic device 100 in PCD mode. In some examples, the electronic device 100 in PCD mode can transmit a read tag command to the payment device 200 in PICC mode. The read tag command can be used to request the NFC tag data of the payment device 200 in PICC mode. After receiving the read tag command, the payment device 200 in PICC mode can transmit the NFC tag data of the payment device 200 to the electronic device 100 in PCD mode.

[0291] The NFC tag data includes the identifiers of one or more payment applications supported by the payment device 200. The NFC tag data includes information about the first order currently being paid. The first order information may include, for example, one or more of the following: the identifier of the first order, the payment amount of the first order, and the payment account information for the first order. The payment account information for the first order may include the payment account information of the one or more payment applications. The payment account information may include, for example, one or more of the following: the name of the payment account, the profile picture of the payment account, the introduction information of the payment account, the identifier of the payment account, etc.

[0292] S211 : The electronic device 100 determines a target payment application from the one or more payment applications supported by the payment receiving device 200 based on the identifiers of the one or more payment applications supported by the payment receiving device 200 .

[0293] S212: The electronic device 100 starts the target payment application and displays the payment interface of the first order through the target payment application.

[0294] Figure 9 S211-S212 and Figure 8 Similar to S115-S116, see Figure 8The description of S115-S116 will not be repeated here.

[0295] S213: The payment device 200 and the electronic device 100 perform the payment process for the first order.

[0296] In some embodiments, the electronic device 100 in PCD mode and the payment device 200 in PICC mode can interact through NFC signaling to perform the payment process of the first order, which is specifically implemented as follows: Figure 8 The implementation of S117 is similar, see Figure 8 The description of S117 is omitted here. Not limited to the above embodiment, in other embodiments, Figure 8 S117 and Figure 9 S213 may also not require interaction between the payment device 200 and the electronic device 100, and the electronic device 100 and / or the payment device 200 may also directly interact with the cloud server 300 for payment of the first order.

[0297] S214: The electronic device 100 turns off the PCD mode and enters the PICC mode.

[0298] In some embodiments, the electronic device 100 is in PICC mode by default when it is unlocked in S202, or the electronic device 100 is in PICC mode by default after the NFC function is enabled in S202. After receiving the first carrier wave having the first coding characteristic in S206, the electronic device 100 may enable PCD mode. Therefore, after S213, the electronic device 100 may disable PCD mode and enter PICC mode.

[0299] In some embodiments, step S214 is optional. In step S202, electronic device 100 is in PICC mode in a time-sharing manner while in the unlocked state. In step S206, electronic device 100 is in PCD mode in a time-sharing manner after receiving the first carrier wave having the first coding characteristic. Therefore, after step S213, electronic device 100 can be in either PICC mode or PCD mode in a time-sharing manner without disabling PCD mode.

[0300] Through the payment method provided in the embodiment of the present application, the electronic device 100 in PICC mode, whether in an unlocked state (e.g., screen-off state or screen-on state) or an unlocked state (e.g., screen-on state), when close to the payment device 200, if it receives the first carrier sent by the payment device 200, it can subsequently select the target payment application through NFC signaling interaction, and then the electronic device 100 can use the target payment application and the payment device 200 to complete the payment, that is, complete the target payment process. Therefore, through the special first carrier, the problem that only the electronic device 100 in the unlocked state with the screen on can use the payment application and the payment device 200 to complete the payment is solved. The electronic device 100 can complete the payment without excessive user operations, thereby improving the efficiency of the user's payment using the electronic device 100.

[0301] Moreover, when the payment device 200 and the electronic device 100 perform the payment process of the first order, the payment device 200 and the cloud server 300 can interact, or the electronic device 100 and the cloud server 300 can interact. That is to say, as long as one of the payment device 200 and the electronic device 100 is connected to the Internet, the payment can be completed. The payment device 200 is generally connected to the Internet, so the electronic device 100 does not need to be connected to the Internet to complete the payment. The user does not need to manually turn on the Internet function of the electronic device 100, which further improves the efficiency of the user's payment using the electronic device 100.

[0302] Not limited to the above embodiment, in other embodiments, when the user brings the electronic device 100 and the payment device 200 close to each other, the electronic device 100 is in PCD mode and the payment device 200 is in PICC mode. Therefore, the payment device 200 in PICC mode enters the radio frequency field of the electronic device 100 in PCD mode. The specific implementation process and Figure 9 S208-S213 shown are similar, see Figure 9 The description of S208-S213 shown is omitted here. In this way, even if the electronic device 100 is a "non-upgraded device" that cannot recognize the first carrier, it can still use the payment application and the payment device 200 to complete the payment normally in the unlocked state with the screen on. Therefore, the payment method provided in the embodiment of the present application is forward compatible with "non-upgraded devices" and has a wide range of application scenarios.

[0303] The following is an exemplary introduction to the first carrier wave sent by the payment device 200.

[0304] Figure 10 This is a schematic diagram of a payment device 200 sending a first carrier provided by an embodiment of the present application.

[0305] like Figure 10As shown, the payment device 200 can transmit multiple first carriers, which can include the first first carrier, the second first carrier, the third first carrier, and so on in order of transmission time from earliest to latest. Each of the multiple first carriers includes N1 subcarriers, which can include subcarrier 1, subcarrier 2, ..., subcarrier N1 in order of transmission time from earliest to latest. The amplitude of each subcarrier in the N1 subcarriers is a first amplitude (not shown). The duration of each subcarrier in the N1 subcarriers is a first duration T1. The time interval between any two adjacent subcarriers in the N1 subcarriers is a first time interval T2, for example, the time interval between subcarrier 1 and subcarrier 2 is a first time interval. The duration of each first carrier in the multiple first carriers is a second time interval T3, T3 = T1 x N1 + T2 x (N1-1). The time interval between the first first carrier and the second first carrier is time interval 1, and the time interval between the second first carrier and the third first carrier is time interval 2. Time interval 1 and time interval 2 may be equal or different.

[0306] In some examples, the duration of each subcarrier in the first carrier (i.e., the first duration T1) is 25 microseconds (μs), the time interval between any two adjacent subcarriers in the first carrier (i.e., the first time interval T2) is 10 milliseconds (ms), and the number of subcarriers in the first carrier (i.e., N1) is 2. Then, the duration of the first carrier (i.e., the second duration T3) is T2 = T1 x N1 + T2 x (N1-1) = 10.05 ms. The embodiments of the present application do not limit the specific values ​​of T1, T2, N1, and T3.

[0307] The following is an exemplary description of the process of NFC signaling interaction between the payment device 200 and the electronic device 100 at the access layer.

[0308] Figure 11 This is a flow chart of an NFC signaling interaction process at the access layer provided in an embodiment of the present application.

[0309] like Figure 11 As shown, the NFC signaling interaction process can be applied to an NFC system including a PCD device and a PICC device. In some examples, the PCD device is a payment device 200 in PCD mode, and the PICC device is an electronic device 100 in PICC mode. Figure 11 The process shown can be Figure 8 In other examples, the PCD device is an electronic device 100 in PCD mode, and the PICC device is a payment device 200 in PICC mode. Figure 11The process shown can be Figure 9 The implementation process of S209.

[0310] Figure 11 The NFC signaling interaction process shown may include but is not limited to the following steps:

[0311] S300: The PICC device enters the radio frequency field of the PCD device.

[0312] S301: The PCD device sends a first card search request to the PICC device.

[0313] In some embodiments, the PCD device can broadcast a first card search request via a radio frequency field. When the PICC device enters the radio frequency field of the PCD device, the PICC device can receive the first card search request broadcast by the PCD device. The PCD device can periodically send the first card search request, which can be used to indicate that the PCD device supports the first NFC protocol. In some examples, if the first NFC protocol is a Class A NFC protocol, the first card search request can be REQA. In some examples, if the first NFC protocol is a Class B NFC protocol, the first card search request can be REQB. In some examples, if the first NFC protocol is a Class F NFC protocol, the first card search request can be SENSF_REQ.

[0314] In some embodiments, the PICC device is an electronic device 100 in PICC mode, and the PCD device is a payment device 200 in PCD mode. After receiving the first card search request sent by the payment device 200 in PCD mode, the electronic device 100 in PICC mode can determine not to start the wallet application because it has previously received the first carrier with the first coding feature. It then selects an application to start during subsequent NFC signaling interaction at the application layer. For example, after receiving NFC tag data sent by the payment device 200, it starts the target payment application, ensuring that the electronic device 100 uses the target payment application to complete the payment with the payment device 200, thereby meeting the user's usage requirements for NFC payment.

[0315] S302: The PICC device sends a first card search response to the PCD device.

[0316] In some embodiments, the first card search response may be used to indicate that the PICC device supports the first NFC protocol supported by the PCD device. If the PICC device does not support the first NFC protocol indicated by the first card search request, the PICC device may not send the first card search response to the PCD device.

[0317] In some examples, the first NFC protocol is a Type A NFC protocol, the first card search request may be REQA, and the first card search response may be an answer to request type A (ATQA).

[0318] In some examples, the first NFC protocol is a Type B NFC protocol, the first card search request may be REQB, and the first card search response may be an answer to request type B (ATQB).

[0319] In some examples, the first NFC protocol is a Type F NFC protocol, the first card search request may be SENSF_REQ, and the first card search response may be a sense response (SENSF_RES).

[0320] S303: The PCD device sends an anti-collision command to the PICC device.

[0321] S304: The PICC device sends an anti-collision response to the PCD device.

[0322] In some embodiments, since multiple PICC devices (for example, NFC tag cards including multiple entities or devices in PICC mode) may exist simultaneously in the radio frequency field of the PCD device, if multiple PICC devices perform NFC signaling interaction with the PCD device, the NFC commands or NFC responses sent by these multiple PICC devices will collide, causing the PCD device to be unable to correctly parse the NFC command or NFC response. Therefore, the PCD device only performs NFC signaling interaction with one PICC device. Therefore, the PCD device can select a PICC device to perform NFC interaction with the PCD device by sending an anti-collision command. The anti-collision command can be used to select a target PICC device to perform NFC signaling interaction with the PCD device. After receiving the anti-collision command, multiple PICC devices can send an anti-collision response to the PCD device. The anti-collision response sent by the PICC device will carry the feedback result of the PICC device to the anti-collision command. After receiving one or more anti-collision responses, the PCD device can determine the target PICC device (i.e. Figure 11 PICC device shown) to perform NFC signaling interaction.

[0323] In some embodiments, S303 and S304 are optional steps. Figure 11The first card search response of a PICC device shown in FIG. 1 is received, but no card search response is received from other PICC devices. Then the PCD device and Figure 11 The PICC device shown may not execute S303 and S304 but may execute S305 and S306.

[0324] S305: The PCD device sends a select command to the PICC device.

[0325] S306: The PICC device sends a select acknowledge (SAK) command to the PCD device.

[0326] In some embodiments, the PCD device may determine the selected Figure 11 The PICC device shown in FIG. 1 can therefore send a selection command to the PICC device. After receiving the selection command, the PICC device can send a SAK command to the PCD device.

[0327] In some embodiments, the SAK command may indicate whether the application layer NFC protocol is supported. If the SAK command indicates that the application layer NFC protocol is supported, the PCD device may perform application layer NFC signaling interaction with the PICC device. If the SAK command indicates that the application layer NFC protocol is not supported, the PCD device may not perform application layer NFC signaling interaction with the PICC device.

[0328] In some embodiments, the PICC device is the electronic device 100 in PICC mode, and the PCD device is the payment device 200 in PCD mode. After receiving the selection command sent by the payment device 200, the electronic device 100, having previously received the first carrier wave having the first coding characteristic, can send a SAK command to the payment device 200 indicating support for the application layer NFC protocol, thereby enabling application layer NFC signaling interaction with the payment device 200, thereby launching the target payment application after receiving the NFC tag data sent by the payment device 200.

[0329] Figure 12 This is a flow chart of another NFC signaling interaction process at the access layer provided in an embodiment of the present application.

[0330] like Figure 12 As shown, the NFC signaling interaction process can be applied to an NFC system including a PCD device and a PICC device. In some examples, the PCD device is a payment device 200 in PCD mode, and the PICC device is an electronic device 100 in PICC mode. Figure 12 The process shown can be Figure 8In other examples, the PCD device is an electronic device 100 in PCD mode, and the PICC device is a payment device 200 in PICC mode. Figure 12 The process shown can be Figure 9 The implementation process of S209.

[0331] Figure 12 The NFC signaling interaction process shown may include but is not limited to the following steps:

[0332] S400: The PICC device enters the radio frequency field of the PCD device.

[0333] S401: The PCD device sends a probe frame to the PICC device.

[0334] In some embodiments, the PCD device can broadcast a Probe frame via a radio frequency field. When the PICC device enters the radio frequency field of the PCD device, the PICC device can receive the Probe frame broadcast by the PCD device. The PCD device can periodically send the Probe frame to indicate that the PCD device supports the second NFC protocol.

[0335] In some embodiments, the PICC device is an electronic device 100 in PICC mode, and the PCD device is a payment device 200 in PCD mode. Upon receiving a Probe frame sent by the payment device 200 in PCD mode, the electronic device 100 in PICC mode may not launch a wallet application, and may select an application to launch during subsequent NFC signaling interactions at the application layer, such as launching a target payment application after receiving NFC tag data sent by the payment device 200. For example, upon receiving a Probe frame sent by the payment device 200, the electronic device 100 may determine not to launch the wallet application because it has previously received a first carrier wave having a first coding characteristic.

[0336] S402: The PICC device sends a Probe ACK frame to the PCD device.

[0337] In some embodiments, the Probe ACK frame can be used to indicate that the PICC device supports the second NFC protocol corresponding to the Probe frame. If the PICC device does not support the second NFC protocol corresponding to the Probe frame, the PICC device will not send the Probe ACK frame to the PCD device.

[0338] S403: The PCD device sends a Notify frame (carrying device feature information of the PCD device) to the PICC device.

[0339] In some embodiments, the PCD device may notify the PICC device of the device feature information of the PCD device through a Notify frame, thereby indicating the service intention of the PCD device to the PICC device.

[0340] In some embodiments, the device feature information may include any one or more of a service identifier (SID), a device organization unique identifier (OUI) (also known as an NFC device organization unique identifier (ND_OUI)), and a device group identifier (GID) (also known as an NFC device group identifier (ND_GID)).

[0341] Among them, the service identifier (SID) can be used to indicate the type of NFC service supported by the PCD device based on the NFC function. NFC services include one or more of access control, keys, transportation, banking, digital currency, digital certificates, codeless payment, electronic tickets, wireless charging, touch and pay, multi-function cards, etc.

[0342] The Organizational Identifier (OUI) of a device can be used to identify the manufacturer that provides NFC services using a PCD device. For example, the manufacturer that provides NFC services may include one or more smart door lock manufacturers, one or more property management companies, one or more auto parts manufacturers, one or more transportation card management departments, etc.

[0343] The device group identifier (GID) can be used to indicate the group to which the NFC service provided by the PCD belongs. The device group identifier can be assigned based on the purpose and location of the payment device 200. Different NFC services can be divided into different groups.

[0344] S404: The PICC device sends a Notify ACK frame to the PCD device.

[0345] In some embodiments, after receiving the Notify frame, the PICC device may reply a Notify ACK frame to the PCD device to inform the PCD device that the Notify frame has been received.

[0346] In some embodiments, the PICC device is the electronic device 100 in PICC mode, and the PCD device is the payment device 200 in PCD mode. After receiving the Notify frame, the electronic device 100 can perform an action corresponding to the device feature information of the payment device 200 according to the device feature information of the payment device 200 carried in the Notify frame, such as a codeless payment prompt. For an example of a codeless payment prompt, see Figure 7B Payment prompt window 712 is shown.

[0347] S405: The PCD device sends a parameter negotiation (Param Negotiation) command to the PICC device.

[0348] S406: The PICC device sends a parameter negotiation response (Param Negotiation Response) to the PCD device.

[0349] In some embodiments, the PCD and PICC devices can negotiate communication parameters using parameter negotiation commands and parameter negotiation responses. The negotiated communication parameters can be used to implement subsequent communication processes, such as NFC signaling interactions at the application layer. The communication parameters may include any one or more of the maximum transmission rate and maximum data transmission length during data transmission.

[0350] In some embodiments, S405 and S406 are optional steps. After receiving the Notify ACK frame, the PCD device does not send a parameter negotiation command to the PICC device, that is, does not execute S405 and S406. Then, the PCD device and the PICC device can perform subsequent communication processes using default communication parameters.

[0351] In the above embodiment, when the electronic device 100 in PICC mode approaches the payment device 200 in PCD mode, the payment device 200 in PCD mode can send a first carrier to the electronic device 100 in PICC mode, and the electronic device 100 can successfully identify the first carrier and complete the target payment process with the payment device 200.

[0352] It can be understood that when the electronic device 100 in PCD mode is close to the payment device 200 in PICC mode, the electronic device 100 in PCD mode can perform NFC signaling interaction at the access layer with the payment device 200 in PICC mode, and the electronic device 100 can read the NFC tag data of the payment device 200 and use the target payment application and the payment device 200 to complete the payment, that is, to realize the target payment process. For a specific process example, please refer to Figure 9 For specific scenario examples, see S209-S213. Figures 6A-6C .

[0353] The above embodiments are described using the electronic device 100 that supports identification of the first carrier as an example. In other embodiments, there may also be an electronic device 400 that does not support identification of the first carrier. When the electronic device 400 in PICC mode is close to the payment device 200 in PCD mode, the payment device 200 in PCD mode can send the first carrier to the electronic device 400 in PICC mode. The electronic device 400 cannot successfully identify the first carrier, so it will not start the wallet application or perform any other processing. When the electronic device 400 in PCD mode is close to the payment device 200 in PICC mode, the electronic device 400 in PCD mode can perform NFC signaling interaction at the access layer with the payment device 200 in PICC mode. The electronic device 400 can read the NFC tag data of the payment device 200 and use the target payment application and the payment device 200 to complete the payment, that is, realize the target payment process.

[0354] Another structure of the electronic device 100 provided in an embodiment of the present application is introduced below.

[0355] Figure 13 Schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of the present application.

[0356] It should be understood that the electronic device 100 illustrated in the embodiment of the present application is merely an example, and the electronic device 100 may have more or fewer components than those illustrated in the embodiment of the present application, may combine two or more components, or may have a different component configuration. The various components shown in the figure may be implemented in hardware, including one or more signal processing and / or application-specific integrated circuits, software, or a combination of hardware and software.

[0357] like Figure 13As shown, the electronic device 100 may include a processor 110, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a microphone 170B, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a humidity sensor 180I, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a heart rate sensor 180M, an electrocardiogram sensor 180N, etc.

[0358] The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (AP), a micro-controller unit (MCU), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU), etc. Among them, different processing units can be independent devices or integrated into one or more processors. For example, the application processor may include a graphics processor and a digital signal processor, and the micro-controller unit may include a graphics processor.

[0359] In some embodiments, electronic device 100 (e.g., a wearable device) implements display functionality through a GPU, display screen 194, application processor, microcontroller unit, and the like. A GPU is a microprocessor for image processing that interfaces with display screen 194, application processor, and microcontroller unit. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0360] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0361] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0362] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0363] The internal memory 121 may include one or more random access memories (RAMs) and one or more non-volatile memories (NVMs). The RAM can be directly read and written by the processor 110 and can be used to store executable programs (e.g., machine instructions) of the operating system or other running programs, as well as user and application data. The NVM can also store executable programs and user and application data, and can be pre-loaded into the RAM for direct reading and writing by the processor 110.

[0364] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also provide power to the electronic device 100 via the power management module 141.

[0365] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 and provides power to the processor 110, the internal memory 121, the display 194, the wireless communication module 160, the sensor module 180, and the like. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be provided in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be provided in the same device.

[0366] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0367] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0368] The mobile communication module 150 can provide wireless communication solutions for the electronic device 100, including second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), and sixth generation (6G). The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signals modulated by the modem processor and convert them into electromagnetic waves for radiation via the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be located in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be located in the same device as at least some of the modules of the processor 110.

[0369] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor or micro control unit. The application processor or micro control unit outputs a sound signal through an audio device (not limited to a speaker 170A, a microphone 170B, etc.) or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be provided in the same device as the mobile communication module 150 or other functional modules.

[0370] The wireless communication module 160 can provide wireless communication solutions such as wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), wireless communication technologies specified by the SparkLink Alliance (for example, SparkLink low energy (SLE), SparkLink basic (SLB)), and intrabody communication (IBC) for application on the electronic device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0371] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with a network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, IR, star flash, and / or IBC technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0372] Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, electronic device 100 may include one or N display screens 194, where N is a positive integer greater than one.

[0373] The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

[0374] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and converted into a visible image. The ISP can also perform algorithmic optimization on image noise, brightness, and color. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0375] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0376] Digital signal processors are used to process digital signals.

[0377] Video codecs are used to compress or decompress digital video.

[0378] NPU is a neural-network (NN) computing processor.

[0379] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170 , the speaker 170A, the microphone 170B, and the processor 110 .

[0380] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0381] The speaker 170A, also called a "speaker", is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or listen to hands-free calls through the speaker 170A.

[0382] Microphone 170B, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170B to input the sound signal into the microphone 170B. The electronic device 100 can be provided with at least one microphone 170B. In other embodiments, the electronic device 100 can be provided with two microphones 170B, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170B to collect sound signals, reduce noise, identify the source of sound, realize directional recording function, etc.

[0383] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be located on display screen 194. There are many types of pressure sensors 180A, such as resistive, inductive, and capacitive. A capacitive pressure sensor can include at least two parallel plates made of conductive material. When force acts on pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the intensity of the pressure based on this change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the touch intensity based on pressure sensor 180A. Electronic device 100 can also calculate the touch location based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch location but with different touch intensities can correspond to different operation instructions. For example, when a touch operation with an intensity less than a first pressure threshold is applied to a short message application icon, a command to view short messages is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to a short message application icon, a command to create a new short message is executed.

[0384] The gyroscope sensor 180B can be used to determine the motion of the electronic device 100. In some embodiments, the gyroscope sensor 180B can be used to determine the angular velocity of the electronic device 100 around three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization, navigation, and motion-sensing gaming scenarios.

[0385] The air pressure sensor 180C is used to measure air pressure.

[0386] The magnetic sensor 180D includes a Hall sensor.

[0387] Accelerometer 180E can detect the magnitude of acceleration of electronic device 100 in all directions (generally three axes). It can also detect the magnitude and direction of gravity when electronic device 100 is stationary. It can also be used to identify the electronic device's posture, enabling applications such as switching between landscape and portrait modes and pedometers.

[0388] The distance sensor 180F is used to measure distance.

[0389] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector.

[0390] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, etc.

[0391] The humidity sensor 180I is used to detect humidity.

[0392] The temperature sensor 180J is used to detect temperature.

[0393] The touch sensor 180K is also called a "touch device". The touch sensor 180K can be set on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can transmit the detected touch operation to the processor 110 (such as an application processor, a microcontroller unit) to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the electronic device 100, at a different location from the display screen 194.

[0394] The ambient light sensor 180L is used to sense the brightness of the ambient light.

[0395] The heart rate sensor 180M can be used for heart rate detection, and the electrocardiogram sensor 180N can be used for electrocardiogram detection.

[0396] The buttons 190 include a power button, a volume button, etc. The motor 191 can generate a vibration prompt.

[0397] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0398] The SIM card interface 195 is used to connect a SIM card. In some embodiments, the electronic device 100 uses an eSIM, or embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0399] The above content describes the method provided in the embodiment of the present application. In order to facilitate better implementation of the above scheme of the embodiment of the present application, the embodiment of the present application also provides corresponding devices or equipment.

[0400] In the embodiment of the present application, the electronic device 100 and the payment device 200 can be divided into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, other division methods may be used.

[0401] The following will be combined Figures 14 to 17 The communication device according to the embodiment of the present application is described in detail.

[0402] In the case of integrated units, see Figure 14 , Figure 14 1 is a schematic diagram of the structure of a communication device 1400 provided in an embodiment of the present application. The communication device 1400 may be the electronic device 100 in the above embodiment. In some embodiments, the communication device 1400 may be a chip / chip system, such as an NFC chip. Figure 14 As shown, the communication device 1400 may include a transceiver unit 1410 and a processing unit 1420 .

[0403] Figure 14 The transceiver unit 1410 shown can be used to execute the functional steps such as NFC sending and NFC receiving performed by the electronic device 100 in the above embodiments of the present application.

[0404] In some embodiments, Figure 14 The processing unit 1420 shown can be used to execute the functional steps such as NFC protocol parsing and packaging, NFC service processing flow and display performed by the electronic device 100 in the above embodiment of the present application.

[0405] It should be understood that the communication device 1400 in this design can execute the method steps executed by the electronic device 100 in the aforementioned embodiment. For the sake of brevity, they will not be repeated here.

[0406] In the case of integrated units, see Figure 15 , Figure 15 1 is a schematic diagram of the structure of a communication device 1500 provided in an embodiment of the present application. The communication device 1500 may be the payment device 200 in the above embodiment. Figure 15 As shown, the communication device 1500 may include a transceiver unit 1510 and a processing unit 1520 .

[0407] Figure 15 The transceiver unit 1510 shown can be used to execute the functional steps such as NFC sending and NFC receiving performed by the payment device 200 in the above embodiment of the present application.

[0408] In some embodiments, Figure 15 The processing unit 1520 shown can be used to execute the functional steps such as NFC protocol parsing and packaging, NFC service processing flow, etc. performed by the payment device 200 in the above embodiment of the present application.

[0409] It should be understood that the communication device 1500 in this design can execute the method steps executed by the payment device 200 in the aforementioned embodiment. For the sake of brevity, they will not be repeated here.

[0410] The electronic device 100 and the payment device 200 of the embodiment of the present application are described above. It should be understood that any device having the above Figure 14Any product of any form having the functions of the electronic device 100 as described above Figure 15 Any product that has the functions of the payment device 200 falls within the protection scope of the embodiments of the present application.

[0411] As a possible product form, the electronic device 100 described in the embodiment of the present application can be implemented by a general bus architecture.

[0412] See also Figure 16 , Figure 16 1 is a schematic diagram of the structure of the communication device 1600 provided in an embodiment of the present application. The communication device 1600 may be the electronic device 100, or a device therein. Figure 16 As shown, the communication device 1600 includes a processor 1601 and a transceiver 1602 that is internally connected and communicates with the processor 1601. The processor 1601 can be a general-purpose processor or a dedicated processor. For example, it can be a central processing unit and / or an NFC controller. The transceiver 1602 can be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement transceiver functions. The transceiver 1602 can include a receiver and a transmitter. The receiver can be referred to as a receiver or a receiving circuit, etc., and is used to implement a receiving function, such as an NFC receiving function; the transmitter can be referred to as a transmitter or a transmitting circuit, etc., and is used to implement a transmitting function, such as an NFC transmitting function.

[0413] In some embodiments, the communication device 1600 may further include an antenna 1603 and / or a radio frequency unit ( Figure 16 (not shown), for example, an NFC antenna, where the NFC antenna can be a coil-type antenna. Antenna 1603 and / or the radio frequency unit can be located inside communication device 1600 or can be separated from communication device 1600, that is, antenna 1603 and / or the radio frequency unit can be remotely or distributedly deployed.

[0414] In some embodiments, the communication device 1600 may include one or more memories 1604, on which instructions may be stored. The instructions may be computer programs. The computer programs may be executed on the communication device 1600 to enable the communication device 1600 to perform the method steps described in the above embodiments of this application. Optionally, the memory 1604 may also store data. The communication device 1600 and the memory 1604 may be provided separately or integrated together.

[0415] Figure 16 The processor 1601 , transceiver 1602 , and memory 1604 shown may be connected via a communication bus.

[0416] In one design, the communication device 1600 can be used to perform the functions of the electronic device 100 in the aforementioned embodiment: the processor 1601 can be used to execute the functional steps such as NFC protocol parsing and encapsulation, NFC service processing flow and display performed by the electronic device 100 in the aforementioned embodiment of this application and / or other processes for the technology described in the embodiment of this application; the transceiver 1602 can be used to execute the functional steps such as NFC sending and NFC receiving performed by the electronic device 100 in the aforementioned embodiment of this application and / or other processes for the technology described herein.

[0417] In any of the above designs, processor 1601 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0418] In any of the above designs, the processor 1601 may store instructions, which may be computer programs. The computer programs run on the processor 1601, which may enable the communication device 1600 to perform the method steps performed by the electronic device 100 in the above embodiments of the present application. The computer program may be fixed in the processor 1601, in which case the processor 1601 may be implemented by hardware.

[0419] In one implementation, the communication device 1600 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0420] The scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited thereto. Figure 16 The communication device 1600 may be an independent device or may be part of a larger device. For example, the communication device 1600 may be:

[0421] (1) Independent integrated circuit IC, or chip, or chip system or subsystem; (2) A collection of one or more ICs, optionally, the IC collection may also include a storage component for storing data, computer programs; (3) ASIC, such as NFC chip; (4) Modules that can be embedded in other devices; (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.; (6) Others, etc.

[0422] As a possible product form, the payment device 200 described in the embodiment of the present application can be implemented by a general bus architecture.

[0423] See also Figure 17 , Figure 17 1 is a schematic diagram of the structure of the communication device 1700 provided in the embodiment of the present application. The communication device 1700 may be the payment device 200, or a device therein. Figure 17As shown, the communication device 1700 includes a processor 1701 and a transceiver 1702 internally connected to and communicating with the processor 1701. The processor 1701 is a general-purpose processor or a dedicated processor, for example, an NFC controller. The transceiver 1702 can be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing transceiver functions. The transceiver 1702 can include a receiver and a transmitter. The receiver can be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter can be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function. Optionally, the communication device 1700 can further include an antenna 1703 and / or a radio frequency unit (not shown). The antenna 1703 and / or the radio frequency unit can be located inside the communication device 1700, or can be separated from the communication device 1700, that is, the antenna 1703 and / or the radio frequency unit can be remotely or distributedly deployed.

[0424] In some embodiments, the communication device 1700 may include one or more memories 1704, on which instructions may be stored. The instructions may be computer programs. The computer programs may be executed on the communication device 1700 to enable the communication device 1700 to perform the method steps described in the above embodiments of this application. Optionally, the memories 1704 may also store data. The communication device 1700 and the memories 1704 may be provided separately or integrated together.

[0425] Figure 17 The processor 1701 , transceiver 1702 , and memory 1704 shown may be connected via a communication bus.

[0426] In one design, the communication device 1700 can be used to perform the functions of the payment device 200 in the aforementioned embodiment: the processor 1701 can be used to execute the functional steps of NFC protocol parsing and encapsulation, NFC service processing flow and / or other processes for the technology described herein performed by the payment device 200 in the aforementioned embodiment of this application; the transceiver 1702 can be used to execute the functional steps of NFC sending and NFC receiving performed by the payment device 200 in the aforementioned embodiment of this application and / or other processes for the technology described herein.

[0427] In any of the above designs, processor 1701 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0428] In any of the above designs, processor 1701 may store instructions, which may be computer programs. The computer programs, when executed on processor 1701, may cause communication device 1700 to execute the method steps performed by payment device 200 in the above method embodiments. The computer programs may be embedded in processor 1701, in which case processor 1701 may be implemented by hardware.

[0429] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it can implement the steps performed by the electronic device 100 in the above-mentioned various method embodiments.

[0430] The embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it can implement the steps performed by the payment device 200 in the above-mentioned various method embodiments.

[0431] An embodiment of the present application further provides a computer program product, including a computer program. When the computer program runs on a computer, the computer can implement the steps performed by the electronic device 100 in each of the above method embodiments.

[0432] The embodiment of the present application further provides a computer program product, including a computer program. When the computer program is executed on a computer, the computer can implement the steps performed by the payment device 200 in the above-mentioned various method embodiments.

[0433] The present application also provides a chip system, which includes a processing circuit and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processing circuit. The processing circuit is configured to execute the code instructions so that the chip system implements the steps performed by the electronic device 100 in any method embodiment of the present application. The chip system can be a single chip or a chip module composed of multiple chips.

[0434] The present application also provides a chip system, which includes a processing circuit and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processing circuit. The processing circuit is configured to execute the code instructions so that the chip system implements the steps performed by the payment device 200 in any of the method embodiments of the present application. The chip system can be a single chip or a chip module composed of multiple chips.

[0435] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A payment method, applied to an electronic device, characterized in that: include: When in PICC mode, receiving a first carrier wave sent by a payment device in PCD mode via NFC, wherein the first carrier wave has a first coding feature; After receiving the first carrier sent by the payment device through NFC, the PCD mode is turned on, NFC signaling interaction is performed with the payment device, and the payment is completed using the first payment application and the payment device.

2. The method according to claim 1, wherein The performing NFC signaling interaction with the payment receiving device and completing the payment using the first payment application and the payment receiving device includes: Performing NFC signaling interaction at the access layer with the payment device; Receiving NFC tag data sent by the payment receiving device, wherein the NFC tag data includes identifiers of one or more payment applications supported by the payment receiving device; The first payment application is determined from the one or more payment applications, and the payment is completed using the first payment application and the payment device.

3. The method according to claim 1 or 2, wherein: The first payment application is an HCE application.

4. The method according to any one of claims 1 to 3, wherein The method further comprises: After said turning on said PCD mode, generating a radio frequency field while in said PCD mode; sending a first response to the payment device in the PICC mode via NFC in the PCD mode, wherein the first response indicates successful identification of the first carrier, and the first response is used by the payment device to switch from the PICC mode to the PCD mode after receiving the first response; After sending a first response to the payment device in the PICC mode via NFC in the PCD mode, switching from the PCD mode to the PICC mode; The performing NFC signaling interaction with the payment receiving device and completing the payment using the first payment application and the payment receiving device includes: After switching from the PCD mode to the PICC mode, perform NFC signaling interaction with the payment device that has switched from the PICC mode to the PCD mode, and complete payment using the first payment application and the payment device.

5. The method according to any one of claims 1 to 3, wherein The method further comprises: After said turning on said PCD mode, generating a radio frequency field while in said PCD mode; The performing NFC signaling interaction with the payment receiving device and completing the payment using the first payment application and the payment receiving device includes: Perform NFC signaling interaction in the PCD mode with the payment device that has switched from the PCD mode to the PICC mode, and complete payment using the first payment application and the payment device.

6. The method according to any one of claims 1 to 5, wherein: The method of completing the payment using the first payment application and the payment receiving device includes: Sending a first payment command to the payment receiving device, wherein the first payment command carries an identifier of the first payment application and an identifier of a first payment account, the first payment account being a payment account in the first payment application corresponding to the electronic device, the first payment command being used to request the payment receiving device to execute a payment collection process, the payment collection process being a process in which the payment receiving device requests a cloud server to transfer a payment amount from the first payment account to a first payment receiving account, the first payment receiving account being a payment receiving account in the first payment application corresponding to the payment receiving device; The method further comprises: A first payment response sent by the payment receiving device is received, wherein the first payment response carries a payment result.

7. The method according to any one of claims 1 to 6, wherein: The receiving, through NFC, a first carrier wave sent by the payment device in the PCD mode when in the PICC mode includes: When in the PICC mode in an unlocked state, the first carrier wave sent by the payment device in the PCD mode is received through NFC.

8. The method according to any one of claims 1 to 6, wherein: The electronic device is a wearable device; and when in PICC mode, receiving a first carrier wave sent by the payment device in PCD mode via NFC includes: When in the PICC mode in an unlocked state or an unlocked state, the first carrier wave sent by the payment device in the PCD mode is received through NFC.

9. The method according to any one of claims 1 to 8, wherein The method further comprises: After completing payment using the first payment application and the payment device, the PCD mode is closed and the PICC mode is entered.

10. The method according to claim 4, wherein After switching from the PCD mode to the PICC mode, performing NFC signaling interaction with the payment device that has switched from the PICC mode to the PCD mode, and completing payment using the first payment application and the payment device, includes: After switching from the PCD mode to the PICC mode, receiving, via NFC, a first card search request sent by the payment device that has switched from the PICC mode to the PCD mode, wherein the first card search request is used to indicate that the payment device supports a first NFC protocol, and the first card search request is different from the first carrier; Sending a first card search response to the payment device via NFC, wherein the first card search response is used to indicate that the electronic device supports the first NFC protocol; receiving, from the payment receiving device, identifiers of one or more payment applications supported by the payment receiving device; The first payment application is determined from the one or more payment applications, and the payment is completed using the first payment application and the payment device.

11. The method according to claim 10, wherein The carrier corresponding to the first card-searching request is modulated, and the first carrier is unmodulated.

12. The method according to claim 10 or 11, wherein: After the electronic device receives the first carrier sent by the payment receiving device through NFC, the electronic device does not start the wallet application of the electronic device; After receiving the first card search request sent by the payment device through NFC, the electronic device does not start the wallet application of the electronic device.

13. The method according to any one of claims 1 to 12, wherein: The first carrier includes N subcarriers, and the first coding feature of the first carrier includes one or more of the following: the amplitude of each subcarrier in the N subcarriers is a preset first amplitude, the duration of each subcarrier in the N subcarriers is a preset first duration, the time interval between two adjacent subcarriers in the N subcarriers is a preset first time interval, and N is a preset value, where N is a positive integer greater than 1.

14. An electronic device, characterized in that: The method comprises a processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor calls the computer program to execute the method according to any one of claims 1 to 13.

15. A computer storage medium, characterized in that The computer storage medium stores a computer program, and when the computer program is executed by a processor, it is used to implement the method according to any one of claims 1 to 13.

16. A computer program product, characterized in that When the computer program product is run on a processor, it is used to implement the method according to any one of claims 1 to 13.

17. A chip system, characterized in that: The system comprises a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit the code instructions to the processing circuit, and the processing circuit is used to run the code instructions to execute the method according to any one of claims 1 to 13.

Images