Payment method and related apparatus

Abstract

Provided in the present application are a payment method and a related apparatus. The method comprises: when being in a proximity integrated circuit card (PICC) mode, for example, when being in the PICC mode in an unlocked state, an electronic device receives, by means of near field communication (NFC), a first carrier sent by a payment receiving device in a proximity coupling device (PCD) mode, the first carrier having a first encoding feature; and after receiving the first carrier, the electronic device turns on the PCD mode, performs NFC signaling interaction with the payment receiving device, and uses a first payment application to complete payment with the payment receiving device. In this way, the electronic device in the PICC mode can complete payment of the payment application by means of near field communication (NFC) interaction, and the payment in a manner required by a user can be completed without excessive operations of the user, thereby improving the efficiency of the user using the electronic device to perform payment.

Description

Payment methods and related devices

[0001] This application claims priority to Chinese Patent Application No. 202411985445.X, filed on December 28, 2024, entitled "Payment Method and Related Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to a payment method and related apparatus. Background Technology

[0003] Mobile payment is a payment method where consumers of goods or services pay for them by operating an electronic device. Users typically send payment instructions to merchants or other mobile payment service providers via the internet, resulting in monetary payment and fund transfer, thus realizing mobile payment.

[0004] Currently, when users purchase goods or services from physical merchants offline, they generally complete the payment via QR code in the target payment application. There are two main methods for QR code payment: Method 1: The user needs to keep their electronic device connected to the internet and use the scanning function in the target payment application to scan the merchant's QR code to obtain the merchant's payment account information. After obtaining the merchant's payment account information, the target payment application can launch a payment page. The service platform of the target payment application can deduct the purchase amount from the user's payment account and transfer the amount to the merchant's payment account to complete the payment. Method 2: The user can open the payment page in the target payment application and have the merchant's payment device scan the QR code on the payment page to obtain the user's payment account information. The service platform of the target payment application can then deduct the purchase amount from the user's payment account and transfer the amount to the merchant's payment account to complete the payment. These QR code payment methods require multiple steps to complete the payment, making the process cumbersome and inefficient for users using electronic devices for payments. Summary of the Invention

[0005] This application discloses a payment method and related device that allows users to use electronic devices to tap near the card reader of a payment device and complete the payment application through near field communication (NFC). This eliminates the need for excessive user intervention and improves the efficiency of users making payments using electronic devices.

[0006] In a first aspect, this application provides an NFC system, including an electronic device and a payment receiving device. The payment receiving device, when in proximity coupling device (PCD) mode, transmits a first carrier wave via NFC, the first carrier wave having a first encoding feature. The electronic device, when in proximity smart card (PICC) mode (where PCD mode is not enabled, for example, the electronic device defaults to PICC mode after enabling NFC), receives the first carrier wave transmitted by the payment receiving device in PCD mode via NFC. The electronic device, after receiving the first carrier wave transmitted by the payment receiving device via NFC, activates PCD mode, performs NFC signaling interaction with the payment receiving device, and completes payment using a first payment application and the payment receiving device.

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

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

[0009] In the aforementioned system, after receiving the first carrier wave from the PCD-mode receiving device, the PICC-mode electronic device can activate PCD mode to implement the target payment process with the receiving device. This target payment process involves the electronic device using a payment application to complete the payment; it is not the process of the electronic device using an NFC-enabled card. Therefore, when a user brings their PICC-mode electronic device close to the card reader of the receiving device, regardless of whether the electronic device is locked (e.g., screen off) or unlocked, the electronic device and the receiving device can complete the payment application's payment (i.e., complete the target payment process) through NFC interaction, instead of using an NFC-enabled card. This eliminates the need for manual user operation (e.g., unlocking the electronic device before bringing it close to the receiving device). In this way, the electronic device can complete the payment in the user's desired manner (corresponding to the target payment process) without requiring excessive user intervention, thus improving the efficiency of electronic payments.

[0010] In one possible implementation, the electronic device, specifically after receiving a first carrier wave sent by the receiving device via NFC, opens PCD mode, performs NFC signaling interaction with the receiving device at the access layer, receives NFC tag data sent by the receiving device, the NFC tag data including the identifiers of one or more payment applications supported by the receiving device (including the identifier of the first payment application), then determines the first payment application from the one or more payment applications based on the NFC tag data, and completes the payment using the first payment application and the receiving device.

[0011] In the above system, after receiving the first carrier wave sent by the PCD mode receiving device, the electronic device in PICC mode can initiate the target payment process with the receiving device. The electronic device can receive NFC tag data from the receiving device and select the first payment application supported by the receiving device and the receiving device to complete the payment based on the NFC tag data, instead of arbitrarily selecting a payment application to make the payment. This ensures the normal implementation of the target payment process, has a higher fault tolerance rate, 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 receiving the first carrier wave sent by the PCD mode receiving device, the electronic device in PICC mode can initiate a target payment process with the receiving device. In this process, the electronic device can use the first payment application as an HCE application and the receiving device to complete the payment, instead of using the wallet application as the default payment method of the electronic device in PICC mode. The payment applications that can be used as HCE applications are diverse, so the target payment process can be applied to a wider range of scenarios and is more in line with user usage.

[0014] In one possible implementation, the receiving device is further configured to switch from PCD mode to PICC mode, for example, time-sharing switching to PICC mode, after transmitting the first carrier via NFC in PCD mode; the electronic device is further configured to generate a radio frequency field while in PCD mode after the aforementioned PCD mode is activated; the electronic device is further configured to send a first response (e.g., indicating successful identification of the first carrier) to the receiving device in PICC mode via NFC in PCD mode after the receiving device, which has 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 receiving device is further configured 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 while in PCD mode; specifically, the electronic device is configured to perform NFC signaling interaction with the receiving device, which has switched from PICC mode to PCD mode, after switching from PCD mode to PICC mode, and complete the payment using a first payment application and the receiving 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 unmodulated and does not indicate any information. In other examples, the first response is modulated and can indicate information, such as indicating that the electronic device has successfully identified the first carrier.

[0017] In the aforementioned system, after the PCD-mode receiving device sends the first carrier wave, it can switch from PCD mode to PICC mode. Upon receiving the first carrier wave from the PCD-mode receiving device, the PICC-mode electronic device can activate PCD mode and switch from PICC mode to PCD mode. Then, the PICC-mode receiving device and the PCD-mode electronic device transmit the first response, allowing the receiving device to determine that the electronic device also supports the target payment process. Subsequently, the receiving device and electronic device can switch modes again and proceed with the target payment process, avoiding a situation where the receiving device mistakenly believes the electronic device does not support the target payment process, causing it to fail. Specifically, the receiving device and electronic device switch modes before transmitting the first response to avoid continuing NFC signaling interactions related to NFC card simulation in the previous "old mode." Transmitting the first response and then switching modes before proceeding with the target payment process, rather than directly proceeding in the current mode, requires less modification to the NFC signal and internal device logic, resulting in higher feasibility.

[0018] In one possible implementation, the receiving device is further configured to switch from PCD mode to PICC mode after transmitting the first carrier via NFC in PCD mode, for example, by time-sharing switching to PICC mode; the electronic device is further configured to generate a radio frequency field while in PCD mode after the aforementioned PCD mode is turned on; specifically, the electronic device is configured to perform NFC signaling interaction with the receiving device in PCD mode after the receiving device switches from PCD mode to PICC mode enters the radio frequency field of the electronic device, and complete the payment using the first payment application and the receiving device.

[0019] In the above system, after the PCD mode receiving device sends the first carrier wave, it can switch from PCD mode to PICC mode. Upon receiving the first carrier wave from the PCD mode receiving device, the PICC mode electronic device can activate PCD mode and switch from PICC mode to PCD mode. Then, the receiving device in PICC mode and the electronic device in PCD mode can proceed with the target payment process. This mode switch before proceeding avoids continuing NFC signaling interactions related to the NFC analog 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 would require significant modifications to NFC signals and internal device logic), the logic for the target payment process between the PICC mode receiving device and the PCD mode electronic device can utilize existing logic. This minimizes modifications to NFC signals and internal device logic, making it more feasible.

[0020] In one possible implementation, when the electronic device completes payment using a first payment application and a receiving device, it is specifically configured to: send a first payment command to the receiving device, wherein the first payment command carries the identifier of the first payment application and the identifier of a first payment account, the first payment account being the payment account corresponding to the electronic device in the first payment application, and the first payment command being used to request the receiving device to execute the payment collection process; the receiving device is further configured to, upon receiving the first payment command sent by the electronic device, send payment collection information to the cloud server, wherein the payment collection information includes the payment amount, the identifier of the first payment account, and the identifier of the first receiving account, the first receiving account being the receiving account corresponding to the receiving device in the first payment application, and the payment collection information being used to request the cloud server to transfer the payment amount from the first payment account to the first receiving account; the receiving device is further configured 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 the payment result.

[0021] In some examples, the electronic device may be offline when making a payment using a first payment application and a receiving device.

[0022] In the above system, when an electronic device completes a payment using the first payment application and the receiving device, the receiving device can interact with the cloud server without the need for the electronic device to interact with the cloud service. The electronic device does not need to be connected to the internet, so users do not need to manually turn on the network switch of the electronic device, which further improves the efficiency of users using electronic devices for payment.

[0023] In one possible implementation, the electronic device, specifically when in PICC mode in an unlocked state, receives a first carrier wave sent by a receiving device in PCD mode via NFC, and then activates PCD mode. For example, the electronic device could be a mobile phone, tablet, or a smart home device such as a smart screen.

[0024] In the aforementioned system, users can bring their locked electronic devices close to the card reader of the payment device and complete the payment application through NFC interaction. This eliminates the need for users to manually unlock the electronic devices before bringing them close to the card reader, thus allowing the electronic devices to complete the payment in the desired manner without much user intervention, thereby improving the efficiency of users making payments with electronic devices.

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

[0026] In the aforementioned system, users can bring their wearable devices close to the card-swiping area of ​​the payment device and complete the payment application through NFC interaction. Users do not need to manually turn on the PCD mode of the wearable device before bringing it close to the card-swiping area of ​​the payment device. In this way, the electronic device can complete the payment in the user's required manner without much user operation, thus improving the efficiency of users using electronic devices for payment.

[0027] In one possible implementation, the electronic device is further configured to disable PCD mode and enter PICC mode after completing payment using the first payment application and the receiving device. For example, when a user brings the locked electronic device close to the card reader area of ​​the receiving device, the electronic device can switch to an unlocked state and complete the payment via NFC interaction. After the payment is completed, the electronic device can automatically return to the locked state, reducing power consumption.

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

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

[0030] In the aforementioned system, after the payment device switches to PCD mode, it can send a first card search request to the electronic device that has switched to PICC mode. This first card search request differs from the first carrier wave; it's used to implement normal NFC signaling interaction at the access layer. Therefore, the electronic device can normally return a first card search response, thus completing the target payment process with the payment device. In other words, the payment device in PCD mode automatically sends either the first carrier wave or the first card search request in different scenarios to ensure the normal operation of the target payment process, eliminating the need for manual operation and resulting in higher payment efficiency.

[0031] In one possible implementation, the carrier corresponding to the first card search request is modulated, while the first carrier is unmodulated. This allows the electronic device to distinguish between the first card search request and the first carrier without parsing, further improving payment efficiency.

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

[0033] In the aforementioned system, after receiving the first carrier wave, the electronic device in PICC mode will not use the wallet application and the receiving device to complete the payment according to the default payment method in PICC mode. Therefore, the wallet application will not be launched. Furthermore, after receiving the first carrier wave, if the electronic device subsequently receives the first card search request in PICC mode, it will also not use the wallet application and the receiving device to complete the payment according to the default payment method in PICC mode, and therefore will not launch the wallet application. This ensures that the electronic device can complete the target payment process with the receiving device, while avoiding unnecessary power consumption from launching and running the wallet application, thus improving 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 of the N subcarriers is a preset first amplitude, the duration of each of 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 different scenarios. For example, the first coding feature can be determined according to the type and characteristics of electronic devices and payment devices, which makes it more feasible.

[0036] Secondly, this application provides a payment method applied to an electronic device. The method includes: when in PICC mode (PCD mode is not enabled at this time, for example, the electronic device is in PICC mode by default after NFC is enabled), receiving a first carrier wave sent by a receiving device in PCD mode via NFC, wherein the first carrier wave has a first encoding feature; after receiving the first carrier wave sent by the receiving device via NFC, enabling PCD mode, performing NFC signaling interaction with the receiving device, and completing the payment using a first payment application and the receiving device.

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

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

[0039] In the above method, after receiving the first carrier wave from the PCD mode receiving device, the PICC mode electronic device can activate PCD mode to implement the target payment process with the receiving device. This target payment process involves the electronic device using a payment application to complete the payment, not the electronic device using an NFC-enabled card. Therefore, when a user brings their PICC mode electronic device close to the receiving device's card-swiping area, regardless of whether the electronic device is locked (e.g., screen off) or unlocked, the electronic device and receiving device can complete the payment application's payment (i.e., complete the target payment process) via NFC interaction, instead of using an NFC-enabled card. This eliminates the need for manual user operation (e.g., unlocking the electronic device before bringing it close to the receiving device). This allows the electronic device to complete the desired payment method (corresponding to the target payment process) without excessive user intervention, improving the efficiency of electronic payments.

[0040] In one possible implementation, when the electronic device and the receiving device interact via NFC signaling and complete the payment using a first payment application and the receiving device, the following can be performed: the electronic device and the receiving device interact via NFC signaling at the access layer; the electronic device receives NFC tag data sent by the receiving device, the NFC tag data including the identifiers of one or more payment applications supported by the receiving device (including the identifier of the first payment application), and then determines the first payment application from among the one or more payment applications based on the NFC tag data, and completes the payment using the first payment application and the receiving device.

[0041] In the above method, after the PICC mode electronic device receives the first carrier wave sent by the PCD mode receiving device, it can perform the target payment process with the receiving device. The electronic device can receive the NFC tag data of the receiving device and select the first payment application supported by the receiving device and the receiving device to complete the payment based on the NFC tag data, instead of arbitrarily selecting a payment application to make the payment. This ensures the normal implementation of the target payment process, has a higher fault tolerance rate, and better feasibility.

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

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

[0044] In one possible implementation, the method further includes: after the electronic device activates PCD mode, it generates a radio frequency field while in PCD mode; after the receiving device switches from PCD mode to PICC mode after sending the first carrier, it enters the radio frequency field of the electronic device and sends a first response (e.g., indicating successful recognition of the first carrier) via NFC to the receiving device in PICC mode while in PCD mode. The first response is used for the receiving 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 receiving device perform NFC signaling interaction and complete payment using the first payment application and the receiving device, the following can be performed: after switching from PCD mode to PICC mode, NFC signaling interaction is performed with the receiving device that has switched from PICC mode to PCD mode, and payment is completed using the first payment application and the receiving device.

[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 unmodulated and does not indicate any information. In other examples, the first response is modulated and can indicate information, such as indicating that the electronic device has successfully identified the first carrier.

[0047] In the above method, after receiving the first carrier wave from the PCD mode receiving device, the PICC mode electronic device can switch to PCD mode and switch from PICC mode. Then, the PCD mode electronic device can transmit a first response with the receiving device that has switched from PCD to PICC mode. This allows the receiving device to determine that the electronic device also supports the target payment process. Subsequently, the receiving device and electronic device can switch modes again and proceed with the target payment process, avoiding a situation where the receiving device mistakenly believes the electronic device does not support the target payment process, causing it to fail. Specifically, the receiving device and electronic device switch modes before transmitting the first response to avoid continuing NFC signaling interactions related to the NFC card simulation in the previous "old mode." Transmitting the first response and then switching modes before proceeding with the target payment process, rather than directly proceeding in the current mode, requires less modification to the NFC signal and internal device logic, resulting in higher feasibility.

[0048] In one possible implementation, the above method further includes: after the electronic device activates PCD mode, it generates a radio frequency field while in PCD mode; when the electronic device and the receiving device perform NFC signaling interaction and complete the payment using the first payment application and the receiving device, the following can be performed: after the receiving device switches from PCD mode to PICC mode after sending the first carrier wave, it enters the radio frequency field of the electronic device, performs NFC signaling interaction with the receiving device that has switched from PCD mode to PICC mode in PCD mode, and completes the payment using the first payment application and the receiving device.

[0049] In the above method, after receiving the first carrier wave from the PCD mode receiving device, the PICC mode electronic device can switch to PCD mode and then switch from PICC mode to PCD mode. The PCD mode electronic device can then perform the target payment process with the receiving device that has switched from PCD to PICC mode. By switching modes before proceeding with the target payment process, the receiving device and electronic device avoid continuing NFC signaling interactions related to the NFC analog card in the previous "old mode." The receiving device and electronic device do not directly perform the target payment process in the current mode after transmitting the first carrier wave (which would require significant modifications to NFC signals and internal device logic). The logic for the target payment process between the PICC mode receiving device and the PCD mode electronic device can utilize existing logic, resulting in less modification to NFC signals and internal device logic, and higher feasibility.

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

[0051] In some examples, the electronic device may be offline when making a payment using a first payment application and a receiving device.

[0052] In the above method, when the electronic device completes the payment using the first payment application and the receiving device, the receiving device can interact with the cloud server without the need for the electronic device to interact with the cloud service. The electronic device does not need to be connected to the network, so the user does not need to manually turn on the network switch of the electronic device, which further improves the efficiency of the user's payment using the electronic device.

[0053] In one possible implementation, the electronic device, while locked and in PICC mode, receives a first carrier wave via NFC from a payment device in PCD mode, and then activates PCD mode. Examples of such electronic devices include mobile phones, tablets, and smart home devices such as smart screens.

[0054] In the above method, users can bring their locked electronic devices close to the card reader of the payment device and complete the payment application through NFC interaction. Users do not need to manually unlock the electronic devices before bringing them close to the card reader of the payment device. In this way, the electronic devices can complete the payment in the way the user needs without much operation by the user, which improves the efficiency of users using electronic devices to make payments.

[0055] In one possible implementation, the electronic device, either in an unlocked state or in PICC mode, receives a first carrier wave sent by a payment device in PCD mode via NFC, and then activates PCD mode. The electronic device is a power-sensitive device, such as a smart bracelet, smartwatch, or smart glasses.

[0056] In the above method, users can bring their wearable device close to the card reader of the payment device and complete the payment application through NFC interaction. Users do not need to manually turn on the PCD mode of the wearable device and then bring it close to the card reader of the payment device. In this way, the electronic device can complete the payment in the way the user needs without much operation by the user, which improves the efficiency of users using electronic devices for payment.

[0057] In one possible implementation, the method further includes: after the electronic device completes payment using the first payment application and the receiving device, it disables the PCD mode and enters the PICC mode. For example, after a user brings the locked electronic device close to the card reader area of ​​the receiving device, the electronic device can switch to the unlocked state and complete the payment via NFC interaction. After the payment is completed, the electronic device can automatically return to the locked state, reducing power consumption.

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

[0059] In one implementation, when an electronic device switches from PCD mode to PICC mode and interacts with a receiving device that has switched from PICC mode to PCD mode via NFC signaling, and completes payment using a first payment application and the receiving device, it can perform the following: After switching from PCD mode to PICC mode, the electronic device receives a first card search request sent by the receiving device that has switched from PICC mode to PCD mode via NFC, wherein the first card search request is used to indicate that the receiving device supports a 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 receiving device via NFC, wherein the first card search response is used to indicate that the electronic device supports the first NFC protocol; receives the identifiers of one or more payment applications supported by the receiving device; determines the first payment application from the one or more payment applications, and completes payment using the first payment application and the receiving device.

[0060] In the above method, the electronic device switched to PICC mode can receive the first card search request sent by the receiving device switched to PCD mode. This first card search request differs from the first carrier wave; it is used to implement normal NFC signaling interaction at the access layer. Therefore, the electronic device can normally return a first card search response, thus completing the target payment process with the receiving 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 receiving device in PCD mode under different scenarios, ensuring the normal progress of the target payment process and achieving higher payment efficiency.

[0061] In one possible implementation, the carrier corresponding to the first card search request is modulated, while the first carrier is unmodulated. This allows the electronic device to distinguish between the first card search request and the first carrier without parsing, further improving payment efficiency.

[0062] In one possible implementation, the electronic device does not launch its wallet application after receiving the first carrier wave sent by the receiving device via NFC; the electronic device also does not launch its wallet application after receiving the first card search request sent by the receiving device via NFC.

[0063] In the above method, after receiving the first carrier wave, the electronic device in PICC mode will not use the wallet application and the receiving device to complete the payment according to the default payment method of the electronic device in PICC mode. Therefore, the wallet application will not be launched. Furthermore, after receiving the first carrier wave, if the electronic device subsequently receives the first card search request in PICC mode, it will not use the wallet application and the receiving device to complete the payment according to the default payment method of the electronic device in PICC mode. Therefore, the wallet application will not be launched. In this way, the electronic device can complete the target payment process with the receiving device, and the unnecessary power consumption of launching and running the wallet application is avoided, making it more feasible.

[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 of the N subcarriers is a preset first amplitude, the duration of each of 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 methods, the first coding feature of the first carrier can be implemented in various ways and can be applied to various different scenarios. For example, the first coding feature can be determined according to the type and characteristics of electronic devices and payment devices, which makes it more feasible.

[0066] Thirdly, this application provides an electronic device, including a transceiver, a processor, and a memory; the memory is used to store a computer program, and the processor calls the computer program to enable the electronic device to execute the payment method provided by the second aspect and any implementation thereof.

[0067] Fourthly, embodiments of this application provide 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 implementation thereof.

[0068] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when run on a processor, is used to implement the payment method provided by the second aspect and any implementation thereof.

[0069] Sixthly, this 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. The processing circuit is used to execute the code instructions to perform the payment method provided in the second aspect and any implementation thereof.

[0070] In a seventh aspect, this application provides an electronic device that includes the methods or apparatus described in any aspect or embodiment of this application. The electronic device is, for example, a chip.

[0071] It should be understood that the descriptions of technical features, technical solutions, beneficial effects, or similar language in this application do not imply that all features and advantages can be achieved in any single implementation. Rather, 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 descriptions of technical features, technical solutions, or beneficial effects in this application do not necessarily refer to the same implementation. Furthermore, the technical features, technical solutions, and beneficial effects described in this application can be combined in any suitable 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 particular implementation. In other implementations, additional technical features and beneficial effects may be identified in specific implementations that do not embody all implementations. Attached Figure Description

[0072] The following describes the accompanying drawings used in this application.

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

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

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

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

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

[0078] Figures 6A-6E illustrate schematic diagrams of some electronic devices and payment devices completing payments through NFC interaction;

[0079] Figures 7A-7G exemplarily illustrate some user interface diagrams for NFC pull-to-pay;

[0080] Figure 8 is a flowchart illustrating a payment method provided in this application;

[0081] Figure 9 is a flowchart illustrating another payment method provided in this application;

[0082] Figure 10 is a schematic diagram of a payment receiving device transmitting a first carrier wave according to this application;

[0083] Figure 11 is a flowchart illustrating an NFC signaling interaction process at the access layer provided in this application;

[0084] Figure 12 is a flowchart illustrating another NFC signaling interaction process for the access layer provided in this application;

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

[0086] Figures 14-17 are schematic diagrams of the structures of some communication devices provided in this application. Detailed Implementation

[0087] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings. The terminology used in the implementation section of this application is only for explaining specific embodiments of this application and is not intended to limit this application.

[0088] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0089] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0090] The working principle of the near field communication (NFC) technology in the embodiments of this application is described below.

[0091] Figure 1 is a schematic diagram of the working principle of NFC provided in an embodiment of this application.

[0092] As shown in Figure 1, the two parties communicating using NFC technology can include a proximity coupling device (PCD) and a proximity integrated circuit card (PICC). The PCD can achieve contactless communication with the PICC in close proximity. The PCD and PICC can allow near-field communication at specific data rates (e.g., 106 kilobits per second, 212 kbps, 424 kbps, or 848 kbps) and specific frequencies (e.g., 13.56 mega hertz, MHz). Communication between the PCD and PICC can occur at close range, for example, a distance of less than or equal to 10 centimeters.

[0093] The PCD (Polymer Capacitor) can generate high-frequency alternating current to produce a radio frequency (RF) field of a specified frequency (e.g., 13.56 MHz), and transmit data to the PICC (Peripherally Input Cell) via this RF field. When the PICC is near the PCD, it can sense the RF field emitted by the PCD. Upon entering the PCD's RF field, the PICC can obtain energy from the PCD's RF field through electromagnetic induction, and use this energy to generate electricity to drive the internal circuitry of the PICC, thus enabling data transmission from the PCD to the PICC. Alternatively, the PICC can also transmit data to the PCD by modulating the RF field with a load, achieving data transmission from the PICC to the PCD.

[0094] The NFC system in the embodiments of this application is described below.

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

[0096] As shown in Figure 2, the NFC system 10 may include an electronic device 100 and a payment device 200. The electronic device 100 can simulate itself as a PICC compliant with NFC standards using data from an NFC emulation card, thereby implementing PICC functionality. The electronic device 100 can activate one or more NFC emulation 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 act as a PCD transmitter, using the radio frequency field to communicate with the PICC. When in PICC mode, the electronic device 100 can act as a PICC passive receiver of the radio frequency field transmitted by the PCD, communicating with the PCD through load modulation technology. In some examples, when in PICC mode, the electronic device 100 can simulate itself as a PICC conforming to NFC standards using data information from an NFC emulation card.

[0098] In this embodiment, the electronic device 100 can be in PICC mode after enabling NFC. If the electronic device 100 supports both PICC and PCD modes, it can also switch between PICC and PCD modes in a time-sharing manner after enabling NFC. In some embodiments, to save power, after enabling NFC, if the electronic device 100 is in an unlocked state, it can default to PICC mode; if it is in an unlocked state, it can switch between PICC and PCD modes in a time-sharing manner. For example, the electronic device 100 may be a mobile phone, tablet computer, or other smart home device as described below. In other embodiments, to save power, after enabling NFC, the electronic device 100 can default to PICC mode regardless of whether it is in an unlocked or unlocked state. The electronic device 100 may be a power-sensitive device, such as a smart bracelet, smartwatch, or smart glasses as described below.

[0099] In some embodiments, the payment device 200 can support both PCD mode and PICC mode. When in PCD mode, the payment device 200 can act as a PCD transmitter, communicating with the PICC via the radio frequency field. When in PICC mode, the payment device 200 can act as a PICC passive receiver of the radio frequency field transmitted by the PCD, communicating with the PCD via load modulation technology.

[0100] In this embodiment, when the payment receiving device 200 supports both PCD and PICC modes, it can switch between these modes. In some embodiments, the NFC module of the payment receiving device 200 can support both PCD and PICC modes, and can switch between them. In some embodiments, the NFC module of the payment receiving device 200 can operate in PCD mode. The payment receiving 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 or inner surface of the card-swiping area on the payment receiving device 200. Optionally, the NFC tag device can be connected to the processor of the payment receiving device 200, or it can be unconnected to the processor.

[0101] In this embodiment of the application, the device type of electronic device 100 can be any of the following: mobile phone, tablet computer, handheld computer, desktop computer, laptop computer, ultra-mobile personal computer (UMPC), netbook, cellular phone, personal digital assistant (PDA), as well as smart home devices such as smart screens and smart speakers, wearable devices such as smart bracelets, smartwatches, 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.

[0102] In this embodiment, the type of the receiving device 200 can be any of the following: mobile phone, tablet computer, handheld computer, desktop computer, laptop computer, super mobile personal computer, netbook, cellular phone, personal digital assistant, as well as smart home devices such as smart screens and smart speakers, wearable devices such as smart bracelets, smartwatches, and smart glasses, extended reality devices such as augmented reality, virtual reality, and mixed reality, vehicles, gates, smart locks, card readers, point of sale (POS) machines, ticket purchase and / or ticket verification terminals, bank service terminals, and document card readers.

[0103] The NFC protocol stack in the embodiments of this application is described below.

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

[0105] As shown in Figure 3, the NFC protocol stack can include the physical layer, radio frequency layer, access layer, transport layer and application layer.

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

[0107] The radio frequency (RF) layer can be used to implement RF specifications for NFC technology communication, such as data rate and RF signal frequency.

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

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

[0110] The application layer can be used to implement one or more NFC services and one or more service management policies. The one or more NFC services may include codeless payment, electronic tickets, access control, digital ID cards, all-scenario contactless payment, and short-range data transmission. The one or more service management policies may include any one or more of file management, card long-term activation, security management, and service routing management. In some embodiments, the processing logic of the NFC services can be executed by the applet shown in Figure 4. In some embodiments, the processing logic of the service management policies can be executed by the NFC basic service module shown in Figure 4.

[0111] The structure of the electronic device 100 in the embodiments of this application is described below.

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

[0113] As shown in Figure 4, the electronic device 100 may include a processor 101 and an NFC module 102, with the processor 101 connected to the NFC module 102. The processor 101 may run one or more applications (APPs). In some examples, these 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 may include one or more payment applications; any one of the HCE applications may or may not be a payment application.

[0114] In some embodiments, as shown in FIG4, 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, the SE 103, and the SIM card 104 respectively, and the NFC module 102 may also be connected to the SE 103 and the SIM card 104.

[0115] In some embodiments, as shown in FIG4, the processor 101 may further 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. These common management functions may include file management, card long-term activation, security management, service routing management, and other functions.

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

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

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

[0119] In some embodiments, the NFC memory can be a single memory shared by the NFC module 102 and other modules in the electronic device 100. For example, some data in the NFC memory can be accessed by the NFC controller, while other data can be accessed by the SE 103. In other embodiments, the NFC memory can be a collection of multiple memories. For example, the NFC controller may include a first memory among these multiple memories. The first memory can be used to store instructions or data that the NFC controller has used or reused. If the NFC controller needs to use the instruction or data again, it can directly access it from the first memory, thus reducing the waiting time of the NFC controller. The SE 103 may include a second memory among these multiple memories. The second memory can be used to store card information such as that of an NFC emulator based on a security component (SE). Thus, if the SE 103 needs to read the card information of an NFC emulator, it can read the card information of the NFC emulator from the second memory in the SE 103. The SIM card 104 may include a third memory among these multiple memories. The third memory can be used to store card information such as the NFC emulator card based on the SIM card. In this way, if the SIM card 104 needs to read the card information of the NFC emulator card, it can read the card information of the NFC emulator card 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, this routing information can be controlled or managed by the NFC controller, and can include a routing table consisting of a list of routing rules. Each routing rule contains 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 emulator card, and the destination is the location where the applet with that AID runs (i.e., the hardware device or software module corresponding to the NFC emulator card with that AID). The destination can be an HCE application (e.g., a payment application) in the processor 101, or it can be an SE 103 or a SIM card 104 connected to the NFC module 102.

[0121] In this embodiment, the electronic device 100 can activate one or more NFC emulator cards in an application based on user input, thereby enabling the electronic device 100 to support one or more NFC services. The business processing logic of the NFC emulator card in the electronic device 100 is specifically implemented by an applet, which can be stored and run in the corresponding hardware device or software module (e.g., HCE application, SE103, SIM card 104, etc.).

[0122] In this embodiment of the 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, electronic device 100 can provide the operating environment for the Applet corresponding to the NFC emulator card, as well as the storage and processing of the NFC emulator card's business data, through SE103 or SIM card 104. NFC module 102, acting as the front end of contactless communication, receives NFC commands from external payment device 200 and forwards them to SE103 or SIM card 104. The Applet in SE103 or SIM card 104 processes the NFC commands and generates response data for payment device 200. SE103 or SIM card 104 can then send the response data to NFC module 102, which in turn can send the response data to external payment device 200. In some examples, users can activate one or more NFC emulator cards in a wallet application. The wallet application can write the Applets and card data of one or more NFC emulator cards to SE103, which can then run the Applets of one or more NFC emulator cards. In some examples, a user can activate one or more NFC emulator cards in the SIM card application. The SIM card application can write the applets of one or more NFC emulator cards and the card data to the SIM card 104 for storage. The SIM card 104 can run one or more NFC emulator card applets.

[0124] In software-based HCE mode, the HCE application in processor 101 can provide the operating environment for the applet corresponding to the NFC emulator card, as well as the storage and processing of the NFC emulator card's business data. NFC module 102, as the front end of contactless communication, receives NFC commands from the external payment device 200 and forwards them to the HCE application in processor 101. The HCE application can process the NFC commands through the applet running within it or a cloud server, generating 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 emulator cards in the HCE application, which can run one or more NFC emulator card applets. The HCE application can also store the NFC emulator card data on the local memory of electronic device 100 or on a cloud server.

[0125] For example, in the card emulation scenario described above, the electronic device 100 can have a native NFC-related application installed, and users can also download and install third-party applications from an app store. Generally, the native application can use a hardware-based virtual card solution, while the third-party application can use 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 this application and should not be construed as limiting.

[0126] In some embodiments, SE103 and NFC module 102 may be two separate chips. In other embodiments, SE103 and NFC module 102 may be packaged within a single chip.

[0127] Currently, when users purchase goods or services from physical merchants using electronic devices, they typically complete the payment via QR code in a payment application. For example, the user scans the merchant's QR code within the payment application to obtain the merchant's payment account information, or the user opens the payment page and has the merchant's payment device scan the QR code to obtain the user's payment account information. QR code payments require multiple steps to complete, making the process inefficient.

[0128] To improve the efficiency of payment using electronic device 100, users can bring their electronic device 100 close to the card-swiping area of ​​payment device 200. Electronic device 100 and payment device 200 can then complete the payment via NFC interaction. The following example illustrates the process of electronic device 100 and payment device 200 completing a payment via NFC interaction.

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

[0130] As shown in Figure 5, the payment system 20 may include an electronic device 100, a payment receiving 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; the specific description is similar to that shown in Figure 4 and will not be repeated here.

[0131] As shown in Figure 5, the electronic device 100 can be in PCD mode and the receiving device 200 can be in PICC mode. When the electronic device 100 and the receiving device 200 are close together, the electronic device 100 can interact with the receiving device 200, which is in PICC mode, as PCD.

[0132] As shown in Figure 5, electronic device 100 can communicate with cloud server 300 via wired or wireless means. Payment device 200 can also communicate with cloud server 300 via wired or wireless means. Wired methods include, for example, High Definition Multimedia Interface (HDMI), Universal Serial Bus (USB), coaxial cable, fiber optic cable, and Digital Subscriber Line (DSL). Wireless methods include, for example, Bluetooth, Wi-Fi, sidelink, NFC, Ultra Wide Bandwidth (UWB), and infrared.

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

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

[0135] As shown in step 1 of Figure 5, electronic device 100 acquires NFC tag data from receiving device 200. Here, electronic device 100 is in PCD mode and interacts with receiving device 200 (which is in PICC mode) via NFC module 102 to acquire NFC tag data from receiving device 200. In some examples, the NFC tag data of receiving device 200 may include identifiers of one or more payment applications supported by receiving device 200. In some examples, the NFC tag data of receiving device 200 may include information about the first order to be paid, such as the identifier of the first order, optional receiving account information for one or more payment applications, and optional payment amount for the first order.

[0136] As shown in step 2 of Figure 5, 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. Specifically, 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] As shown in step 3 of Figure 5, in the processor 101 of the electronic device 100, the NFC basic service module launches the target payment application, for example, through a data distribution service. Specifically, 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 receiving device 200, and launch the target payment application. In some examples, the NFC tag data of the receiving device 200 includes the identifiers of one or more payment applications supported by the receiving device 200. If the identifier of the payment application included in the NFC tag data of the receiving 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 receiving 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 not being included in the applications installed on the electronic device 100), the electronic device 100 can output an installation prompt for the target payment application, launching the target payment application after the user inputs to install it. Launching the payment application can mean either starting the payment application and running it in the background, or starting the payment application and running it in the foreground (in which case the payment application's user interface will be displayed).

[0138] As shown in step 4 of Figure 5, the target payment application in electronic device 100 queries the cloud server 300 for payment discount information and displays the payment interface. Electronic device 100 can communicate with the cloud server 300 via wired or wireless means to enable the target payment application to query payment discount information. The payment discount information can include discounts for all users, or discounts for users of electronic device 100. The payment discount information can include discounts specific to the target payment application, and optionally, other discount information. Optionally, the target payment application in electronic device 100 can display the queried payment discount information on the payment interface. In some examples, the NFC tag data of the receiving device 200 can include information about the first order to be paid, and the payment application in electronic device 100 can display the information of the first order on the payment interface, such as the receiving account information of the target payment application (i.e., the target receiving account information), and optionally, the payment amount of the first order. Understandably, the target payment application can only query the payment discount information from the cloud server 300 when the electronic device 100 and the cloud server 300 communicate via wired or wireless means. Therefore, the electronic device 100 needs to perform step 4 as shown in Figure 5 when it is connected to the network.

[0139] Not limited to step 4 shown in Figure 5, in some 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 electronic device 100 may not query payment discount information when it is not connected to the Internet.

[0140] As shown in step 5 of Figure 5, electronic device 100 sends a payment command to receiving device 200 via short-range communication technology, carrying the identifier of the target payment account. The short-range communication technology can be any one or more of NFC, Bluetooth, Wi-Fi, and UWB. The target payment account can be the payment account corresponding to the target payment application in electronic device 100. In some examples, when electronic device 100 displays the payment interface, it receives user input for payment of the first order, and in response to this input, sends a payment command to receiving 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] As shown in step 6 of Figure 5, the payment receiving device 200 sends payment information to the cloud server 300 via wired or wireless means to execute the payment receiving process. The payment receiving information may include the payment amount (i.e., the amount paid by the user to the payment receiving device 200 through the electronic device 100, which is also the payment amount of the first order mentioned above), the identifier of the target payment receiving account (i.e., the payment receiving account of the target payment application supported by the payment receiving device 200), and the identifier of the target payment account (i.e., the payment account of the target payment application in the electronic device 100). The cloud server 300 (e.g., the server of the target payment application) can execute the payment receiving process based on the payment receiving information, wherein it can 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. 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 receiving account, it can send a payment completion notification to the payment receiving device 200 used by the merchant. After receiving the payment completion notification, the payment receiving device 200 can output a payment completion prompt, which is used to inform the merchant that the payment amount has been successfully received. The payment completion notification can be text-based, audio-based, image-based, mechanically vibrating, or an indicator light, etc. In other examples, if the cloud server 300 fails to transfer the payment amount from the target payment account's balance to the target receiving account, it can send a payment failure notification to the merchant's payment device 200. Upon receiving the payment failure notification, the payment device 200 can output a payment failure message, which can be used to inform the merchant of the payment failure. This payment failure message can be text-based, audio-based, image-based, mechanically vibrating, or an indicator light, etc.

[0142] As shown in step 7 of Figure 5, the payment receiving 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 can 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 receiving a payment completion notification / payment failure notification from the cloud server 300, the payment receiving device 200 can send a payment response to the electronic device 100. If the payment receiving device 200 receives a payment completion notification, the payment result carried in the payment response indicates successful payment; if the payment receiving device 200 receives a payment failure notification, the payment result carried in the payment response indicates payment failure.

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

[0144] Not limited to steps 5-7 shown in Figure 5, in other embodiments, the receiving 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 receiving account. Then, the electronic device 100 can send payment information to the cloud server 300 via wired or wireless means to execute the payment process. The payment information includes the payment amount, the identifier of the target receiving account, and the identifier of the target payment account. The cloud server 300 can execute the payment process based on the payment information, wherein it can deduct the payment amount from the balance of the target payment account and add the payment amount to the balance of the target receiving 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 receiving account, it can send a payment completion notification to the electronic device 100. After receiving the payment completion notification, the electronic device 100 can output a payment completion prompt (e.g., display a payment completion interface) to notify the user that the payment is complete. In other examples, if the cloud server fails to transfer the payment amount from the target payment account's balance to the target receiving account, it can send a payment failure notification to electronic device 100. Upon receiving the payment failure notification, electronic device 100 can output a payment failure message (e.g., display a payment failure interface) to inform the user of the payment failure. After receiving a payment completion notification / payment failure notification from cloud server 300, electronic device 100 can send a payment response to receiving device 200 via short-range communication technology. This payment response carries a payment result corresponding to the payment completion notification / payment failure notification. Not limited to the above examples, in other examples, cloud server 300 can also send a payment completion notification / payment failure notification to receiving device 200, and receiving device 200 can output a corresponding receiving completion message / receiving failure message based on the payment completion notification / payment failure notification.

[0145] The following examples illustrate some scenarios where electronic devices 100 and payment devices 200 complete payments through NFC interaction.

[0146] Figures 6A-6C exemplify a schematic diagram of an electronic device 100 and a payment receiving device 200 completing a payment through NFC interaction. Figures 6A, 6D, and 6E exemplify another schematic diagram of an electronic device 100 and a payment receiving device 200 completing a payment through NFC interaction.

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

[0148] As shown in Figure 6B, the electronic device 100 is in a screen-on and unlocked state. Taking the desktop 610 displayed on the electronic device 100 as an example, the desktop 610 can include icons for one or more applications, such as clock, settings, voice recorder, wallet, and payment applications. The electronic device 100 supports both PICC and PCD modes. In the screen-on and unlocked state, the electronic device 100 can be in either PICC or PCD mode at different times. In the locked state, the electronic device 100 is in PICC mode by default. The user can bring the electronic device 100 close to the card-swiping area of ​​the payment device 200. The electronic device 100 can interact with the payment device 200 in PCD mode and PICC mode via NFC signaling. Specifically, the electronic device 100 can obtain the NFC tag data of the payment device 200 and launch its payment application based on this data. The electronic device 100 can then complete the payment through the payment application. The specific implementation process can be seen in the payment process illustrated in Figure 5.

[0149] As shown in Figure 6C, after the electronic device 100 launches the payment application, it can display a user interface 620 indicating that payment is in progress. The user interface 620 is the interface of the payment application and may include the payment application icon 611 and payment prompt information 612 (e.g., "Paying in Progress").

[0150] As shown in Figures 6A-6C, the electronic device 100 can only perform NFC signaling interaction (including the electronic device 100 reading the NFC tag data of the payment device 200) in PCD mode and PICC mode when the screen is on and unlocked. This allows the payment application corresponding to the NFC tag data to complete the payment with the payment device 200. If the electronic device 100 is not unlocked (e.g., locked or off), the user needs to manually unlock the electronic device 100, such as by pressing the power button and manually entering the lock screen password or touching the fingerprint recognition area. Then, the user needs to bring the unlocked electronic device 100 close to the card reader of the payment device 200. This operation is cumbersome and the efficiency of using electronic devices for payment is low.

[0151] As shown in Figure 6D, the electronic device 100 is in a screen-off and unlocked state, therefore, the electronic device 100 is in PICC mode by default. The user can bring the electronic device 100 close to the card-swiping area of ​​the receiving device 200. The electronic device 100 can interact with the receiving device 200 in PCD mode via NFC signaling in PICC mode, and pull the NFC-enabled emulated card in the electronic device 100 to complete the card swipe transaction with the receiving device 200. To ensure security and a fast user experience, after receiving the NFC signal from the receiving device 200 in PCD mode in PICC mode, the electronic device 100 will launch the wallet application and forward the NFC signal to SE103. The Applet in SE103 will then implement the NFC emulated card transaction processing logic of the wallet application. Therefore, the electronic device 100 in PICC mode can use the NFC-enabled emulated card in the wallet application to interact with the receiving device 200 in PCD mode via NFC signaling and complete the card swipe transaction payment using the NFC-enabled emulated card.

[0152] As shown in Figure 6E, when the PICC mode electronic device 100 and the PCD mode payment device 200 interact via NFC signaling, 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 may include an icon 631 for the NFC simulated card (using a transportation card as an example) and a fingerprint icon 632. The fingerprint icon 632 can be used to verify the user's fingerprint information, for example, to perform a transaction payment using the NFC simulated card in the wallet application if the user's fingerprint information is successfully verified.

[0153] As shown in Figures 6A, 6D, and 6E, when the electronic device 100 is locked, it can only interact with the receiving device 200 in PICC mode and PCD mode via NFC signaling. This allows it to activate the NFC-enabled emulated card in the wallet application or other applications and perform a transaction payment using that NFC-enabled emulated card with the receiving device 200. However, it cannot read the NFC tag data of the receiving device 200 or activate the corresponding payment application. If a user wants to use the payment application of the electronic device 100 to complete a payment with the receiving device 200, they need to manually unlock the electronic device 100 and then bring the unlocked, screen-on electronic device 100 close to the card-swiping area of ​​the receiving device 200 so that the electronic device 100 can read the NFC tag data of the receiving device 200 and activate the corresponding payment application, as shown in Figures 6A-6C. This cumbersome operation results in low efficiency for users paying with electronic devices.

[0154] This application provides a payment method in which an electronic device 100 can be in PICC mode, for example, in PICC mode by default or in PICC mode at specific times. In PICC mode, the electronic device 100 can be placed close to the card-swiping area of ​​the receiving device 200 and receive a first carrier wave sent by the receiving device 200 in PCD mode. After receiving the first carrier wave with a first encoding feature, the electronic device 100 can determine and initiate a target payment process with the receiving device 200. The target payment process is one in which the electronic device 100 obtains the NFC tag data of the receiving device 200 and uses the target payment application corresponding to the NFC tag data to perform payment with the receiving device 200. The target payment process is not one in which the electronic device 100 uses an NFC-enabled card to perform payment with the receiving device 200. Therefore, after receiving the first carrier wave, electronic device 100 can interact with receiving device 200 via NFC signaling in PCD or PICC mode, and obtain the NFC tag data of receiving device 200. Electronic device 100 can determine and launch the target payment application based on the NFC tag data of receiving device 200, and use the target payment application to complete the payment with receiving device 200, thus realizing the target payment process between electronic device 100 and receiving device 200. Therefore, regardless of whether electronic device 100 is in an unlocked or locked state, the user can bring electronic device 100 close to the card-swiping area of ​​receiving device 200 and use the payment application of electronic device 100 to complete the payment with receiving device 200. There will be no card-swiping transactions using the NFC simulated card of the wallet application as shown in Figures 6A, 6D, and 6E, and there is no need to manually unlock electronic device 100 and then bring the unlocked electronic device 100 with its screen on close to the card-swiping area of ​​receiving device 200. In this way, the electronic device 100 can complete the payment in the user's desired manner (i.e., using a payment application) without requiring much user intervention, thus improving the efficiency of the user's payment using the electronic device 100.

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

[0156] Understandably, after the receiving device 200 sends the first carrier wave to the electronic device 100, it can switch from PCD mode to PICC mode. Upon receiving the first carrier wave from the receiving device 200, the electronic device 100 can switch from PICC mode to PCD mode. This allows the electronic device 100 and the receiving device 200 to perform "new NFC signaling interaction" in the "new mode," avoiding the need for NFC signaling interaction related to NFC card simulation in the "old mode." This ensures that the electronic device 100 and the receiving device 200 complete the target payment process, meeting the user's needs for NFC payments. Furthermore, since the electronic device 100 and the receiving device 200 perform the target payment process after changing modes, rather than directly in the "old mode," the changes to the NFC signals and internal device logic are minimal, making it more feasible.

[0157] Understandably, after receiving the first carrier wave sent by the receiving device 200, the electronic device 100 determines to conduct a target payment process with the receiving device 200. The target payment process is not the process of the electronic device 100 using an NFC simulated card to make a payment with the receiving device 200. Therefore, the electronic device 100 may not launch the wallet application after receiving the first carrier wave.

[0158] The following provides an exemplary description of the application scenarios and user interfaces for NFC-based payment in this application.

[0159] Figures 7A-7G exemplarily illustrate some user interface diagrams for NFC pull-to-pay.

[0160] As shown in Figure 7A, the electronic device 100 is in a screen-off and unlocked state, therefore the electronic device 100 is in PICC mode by default. The user can bring 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 PICC mode and PCD mode. An example of the payment device 200 can be seen in Figure 6A.

[0161] As shown in Figure 7B, after the electronic device 100 interacts with the payment device 200 in PICC mode and PCD mode via NFC signaling, for example, after the electronic device 100 receives the first carrier wave sent by the payment device 200, the electronic device 100 can display a lock screen interface 710. The lock screen interface 710 may include a lock mark 711, time information, and date information, etc. The lock mark 711 is used to indicate to the user that the electronic device 100 is in a locked state (i.e., not unlocked). A payment prompt window 712 may also be displayed on the lock screen interface 710, for example, the payment prompt window 712 may be 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., "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, payment discount information 712B can be obtained by electronic device 100 from cloud server 300.

[0162] In some embodiments, the electronic device 100 can receive user input (e.g., a touch operation, such as a click operation) applied to the payment control 712C in the payment prompt window 712 shown in FIG. 7B. In response to the user input, the electronic device 100 can authenticate the user's identity. Taking facial authentication as an example, the electronic device 100 can capture the user's facial image through a camera and determine whether the user's facial image matches the stored facial images of legitimate users. If they match, the facial authentication is successful; otherwise, the facial authentication fails. When facial authentication is successful, the electronic device 100 can switch from a locked state (i.e., locked state) to an unlocked state (i.e., unlocked state), for example, displaying the user interface 720 shown in FIG. 7C in the unlocked state.

[0163] As shown in Figure 7C, after interacting with the receiving device 200 via NFC signaling, the electronic device 100 can obtain the NFC tag data of the receiving device 200. Based on the NFC tag data of the receiving device 200, the electronic device 100 can determine the target payment application from one or more payment applications within its own portfolio and perform the payment, displaying a user interface 720 indicating that the payment is in progress. In some examples, the user interface 720 is the user interface of the target payment application. The 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 the user interface 720 may include a prompt message 723A (e.g., "Paying"), which informs the user that the electronic device 100 is making a payment. Optionally, the payment window 723 may also include the name 723B of the target receiving account (e.g., "K-Store").

[0164] As shown in Figure 7D, electronic device 100 can communicate with payment device 200 via short-range communication technology, thereby completing payment using the target payment application. After completing payment with payment device 200, electronic device 100 can display a payment completion user interface 730. In some examples, user interface 730 is the user interface of the target payment application. User interface 730 may include the identifier 721 of the target payment application, payment prompt 722, and payment window 723. The payment window 723 in user interface 730 may include a payment success prompt 731, payment amount 732 (e.g., "50 yuan"), the name of the target receiving account 733 (e.g., "K-Store"), and completion control 734. The payment success prompt 731 is used to notify the user that electronic device 100 has successfully completed the payment. Not limited to the payment success prompt 731 shown in Figure 7D, in specific implementations, the payment success prompt may be one or more of the following: text prompt, image prompt, audio prompt, 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, to return to the screen-off and unlocked state, or to return to the lock screen display, etc.

[0165] Understandably, before displaying the lock screen interface 710 shown in Figure 7B, the electronic device 100 can interact with the payment device 200 via NFC signaling and receive NFC tag data sent by the payment device 200. Subsequently, the electronic device 100 can communicate with the payment device 200 via short-range communication technology. In this way, when the electronic device 100 displays the lock screen interface 710 shown in Figure 7B, the user can pick up the electronic device 100 and move it away from the payment device 200, instead of keeping the electronic device 100 close to the payment device 200, making it more convenient for the user.

[0166] Not limited to the above embodiments, in other embodiments, if the electronic device 100 fails to authenticate the user's face, it can remain locked and not launch the target payment application for payment. In this case, the electronic device 100 can output an authentication failure prompt to inform the user that the electronic device 100 has failed to authenticate.

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

[0168] Not limited to the face authentication shown in the above embodiments, in other embodiments, the identity authentication performed when unlocking can also be fingerprint authentication, password authentication, iris authentication, voice authentication, palm print authentication, pattern authentication, gesture authentication, etc. This application does not limit the specific method of identity authentication. For example, as shown in FIG7E, identity authentication is password authentication or fingerprint authentication. Therefore, the electronic device 100 can respond to user input acting on the payment control 712C in the payment prompt window 712 shown in FIG7B and display the identity authentication user interface 740. When the electronic device 100 displays the user interface 740, it is still in a locked state. The user interface 740 may include prompt information 741 (e.g., "Please use fingerprint or password to unlock"), a password input box 742, a password input keyboard 743, and a fingerprint recognition icon 744. When the user unlocks the electronic device 100 using a password, the password input keyboard 743 can be used to receive the user's input. Based on the user's input, the user enters the lock screen password in the password input box 742, and the electronic device 100 can verify the lock screen password entered by the user. When a user unlocks the electronic device 100 using their fingerprint, the fingerprint recognition icon 744 can be used to receive the user's touch operation. The electronic device 100 collects the fingerprint of the finger that touches the fingerprint recognition icon 744, and can verify the collected fingerprint. When the lock screen password verification or fingerprint verification is successful, the electronic device 100 switches from a locked state (i.e., locked state) to an unlocked state (i.e., unlocked state), and can complete the payment using the target payment application and the receiving device 200, for example, displaying the payment in progress user interface 720 as shown in Figure 7C.

[0169] In some embodiments, after the electronic device 100 interacts with the receiving device 200 via NFC signaling, it can identify a target payment application from one or more payment applications of the electronic device 100 to make a payment. The electronic device 100 can receive the payment amount from the receiving device 200, so the electronic device 100 can display the user interface 720 showing the payment in progress as shown in FIG7C. The electronic device 100 can complete the payment of the payment amount with the receiving device 200 without the user having to manually enter the payment amount.

[0170] Not limited to this, in other embodiments, the user can also input the payment amount on the electronic device 100. As shown in FIG7F, after the electronic device 100 interacts with the receiving device 200 via NFC signaling, it can determine the target payment application from one or more payment applications of the electronic device 100 to make the payment, and can display the payment user interface 750. In some examples, the user interface 750 is the user interface of the target payment application. The user interface 750 may include the identifier 721 of the target payment application, payment prompts 722, and payment window 723. The payment window 723 in the user interface 750 may include the name 751 of the target receiving account (e.g., "K-Store"), a payment amount input box 752, a remarks input box 753, a numeric keypad 754, and a payment confirmation control 755. The numeric keypad 754 can be used to receive user input, and the user can enter the payment amount (e.g., "50 yuan") in the payment amount input box 752 according to the user's input. The remarks input box 753 can be used to display payment remarks information entered by the user. After receiving the payment amount entered by the user in the payment amount input box 752, the electronic device 100 can receive user input (e.g., the user input is a touch operation, such as a click operation) applied to the payment confirmation control 755. In response to the user input, the user interface 720 showing the payment in progress can be displayed, and the electronic device 100 can complete the payment of the user-input amount with the receiving device 200.

[0171] Optionally, the electronic device 100 may authenticate the user in response to user input applied to the payment control 712C in the payment prompt window 712 shown in FIG. 7B, for example, by displaying the authentication user interface 740 shown in FIG. 7E. If the authentication is successful, the electronic device 100 determines the target payment application and performs the payment application, and displays the payment user interface 750 shown in FIG. 7F.

[0172] In some embodiments, after the electronic device 100 interacts with the receiving device 200 via 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 may not perform payment verification on the user and may directly complete the payment with the receiving device 200. For example, after the electronic device 100 receives the payment amount sent by the receiving device 200, it displays the user interface 720 in the payment process shown in FIG7C. Alternatively, after the electronic device 100 receives the payment amount entered by the user in the user interface 750 shown in FIG7F, it displays the user interface 720 in the payment process shown in FIG7C.

[0173] Not limited to this, in other embodiments, the target payment application of electronic device 100 can verify the user's payment. As shown in FIG7G, after electronic device 100 interacts with receiving device 200 via NFC signaling, it can determine the target payment application from one or more payment applications of electronic device 100 to make the payment, and can display a payment verification user interface 760 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 user interface 760 may include the name 761 of the target receiving account (e.g., "K-Store"), the payment amount 762 (e.g., "50 yuan"), a password input box 763, and a password input keyboard 764. The password input keyboard 764 can be used to receive user input, and the user can enter the payment password in the password input box 763 according to the user's input. The target payment application in the electronic device 100 can verify the payment password. After successful verification, the user interface 720 showing the payment in progress as shown in Figure 7C can be displayed. If the verification fails, a verification failure message can be output to inform the user that the payment password verification has failed.

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

[0175] For example, the target payment application of electronic device 100 can 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 has set up 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 has not set up 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 moment the electronic device 100 in PICC mode approaches the card-swiping area of ​​the payment device 200, to the moment the electronic device 100 completes the payment using the target payment application and the payment device 200, the electronic device 100 can remain locked, for example, in a screen-off and unlocked state. That is, the electronic device 100 can complete the payment using the target payment application and the payment device 200 in a locked state without unlocking. In some examples, if the user has set up password-free payment for the target payment account logged in to the target payment application and the payment amount does not exceed the password-free payment limit, the electronic device 100 can complete the payment using the target payment application and the payment device 200 in a locked 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 need to authenticate the user. After the electronic device 100 determines the target payment application, it can launch the target payment application to make payment even without authentication, further reducing user operations and improving the efficiency of the user using the electronic device 100 to make payments.

[0179] Understandably, based on the application scenario described above, electronic device 100 can approach payment device 200 when the screen is off, locked, or displaying a desktop (without showing any NFC simulated card interface), thereby entering the radio frequency field of payment device 200. Electronic device 100 can then interact with payment device 200 via NFC signaling and select a target payment application. Electronic device 100 can then use the target payment application to complete the payment with payment device 200. In this way, electronic device 100 can complete the payment without requiring extensive user intervention, improving the efficiency of payment transactions using electronic device 100.

[0180] The payment method provided in the embodiments of this application will be introduced next.

[0181] Figure 8 is a flowchart illustrating a payment method provided in an embodiment of this application.

[0182] As shown in Figure 8, this payment method can be applied to an NFC system including an electronic device 100 and a receiving device 200. For example, the NFC system could be the NFC system 10 shown in Figure 2, the electronic device 100 could be the electronic device 100 shown in Figure 4, and the electronic device 100 and receiving device 200 could be the electronic device 100 and receiving device 200 in the payment system 20 shown in Figure 5. The electronic device 100 can support both PICC and PCD modes. The receiving device 200 can support both PCD and PICC modes.

[0183] The payment method shown in Figure 8 may include, but is not limited to, the following steps:

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

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

[0186] In other embodiments, the NFC module of the payment device 200 may operate only 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: Electronic device 100 is in PICC mode.

[0188] In some embodiments, after the electronic device 100 enables NFC, it can be in PICC mode by default when locked, or it can switch between PICC mode and PCD mode when unlocked (i.e., it can switch between PICC mode and PCD mode). For example, the electronic device 100 is a mobile phone or other similar device. Therefore, in S102, the electronic device 100 can be in PICC mode by default when locked, or it can be in PICC mode when unlocked.

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

[0190] In some examples, the locked state includes the screen-off state or the screen-on-lock state. Specifically, in the screen-off state, the electronic device 100 can completely turn off the display, meaning the screen-off state includes the screen-off state. Alternatively, the electronic device 100 can also display content on a portion of the display screen using always-on display (AOD) technology in the screen-off state, meaning the screen-off state includes the AOD state.

[0191] S103: Electronic device 100 enters the radio frequency field of receiving device 200.

[0192] In some embodiments, a user can hold the electronic device 100 and actively bring 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 actively hold the payment device 200 and bring the card-swiping area of ​​the payment device 200 close to 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 receiving device 200 sends a first carrier wave to the electronic device 100, the first carrier wave having a first coding feature.

[0194] In some embodiments, when the receiving 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 receiving device 200, it can receive the first carrier wave transmitted by the receiving device 200 in PCD mode. The first carrier wave can be understood as a special detection signal transmitted by the receiving device 200 in PCD mode.

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

[0196] In some embodiments, when the receiving device 200 is in PCD mode, it may transmit one first carrier. In other embodiments, when the receiving device 200 is in PCD mode, it may also transmit multiple first carriers in chronological order. The time interval between any two adjacent first carriers in the multiple first carriers may be a fixed value, meaning the receiving device 200 may transmit the first carriers periodically. Alternatively, the time interval between any two adjacent first carriers in the multiple first carriers may not be a fixed value. For example, the receiving device 200 may transmit three first carriers sequentially from morning to evening, with a time interval of duration 1 between the first and second first carriers, and a time interval of duration 2 between the second and third first carriers, where duration 1 and duration 2 are different.

[0197] In some embodiments, the first carrier includes N subcarriers, where N is a positive integer greater than 1. The coding features 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 features of the first carrier include one or more of the following: the amplitude of each of the N subcarriers is a first amplitude, the duration of each of the N subcarriers is a first duration, the time interval between any two adjacent subcarriers of 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 embodiments, in other embodiments, the amplitudes of different subcarriers among the N subcarriers may also be different. For example, the first coding feature includes: the amplitude of some subcarriers among the N subcarriers is a second amplitude, and the amplitude of other subcarriers is a third amplitude. In other embodiments, the duration 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 interval 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 a second time interval, and the time interval between other adjacent subcarriers is a third time interval. The embodiments of this application do not limit the specific content of the first coding feature.

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

[0200] An example of the first carrier wave sent by the receiving device 200 can be seen in Figure 10 below.

[0201] In some embodiments, after receiving a first carrier wave with a first encoded feature sent by the receiving device 200, the electronic device 100 can determine that the receiving device 200 supports the target payment process, and therefore can determine whether to conduct the target payment process with the receiving device 200. The target payment process may include: the electronic device 100 acquiring NFC tag data from the receiving device 200, and using the target payment application corresponding to the NFC tag data to complete the payment with the receiving device 200. Examples of the target payment process can be found in S113-S117 of Figure 8 and S209-S213 of Figure 9. It is understood that the purpose of the receiving device 200 sending the first carrier wave is to conduct the target payment process with the peer device (i.e., the device that receives and identifies the first carrier wave).

[0202] S105: Electronic device 100 does not launch the wallet application after receiving the first carrier wave.

[0203] S106: Electronic device 100 enters PCD mode after receiving the first carrier wave.

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

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

[0206] However, in this embodiment, the receiving device 200 in PCD mode does not send a first card search request, but instead sends a first carrier wave. After receiving the first carrier wave, the electronic device 100 can identify that the first carrier wave has a first encoding feature. The electronic device 100 can determine the target payment process with the receiving device 200 based on the first carrier wave, instead of conducting a card swiping transaction of the NFC simulated card in the electronic device 100. Therefore, the electronic device 100 will not launch the wallet application, avoiding displaying the NFC simulated card swiping interface in the wallet application. Furthermore, the electronic device 100 will change from PICC mode to PCD mode to conduct a "new NFC signaling interaction" with the receiving device 200 in the "new mode" (PCD mode), avoiding continuing NFC signaling interaction related to the NFC simulated card with the receiving device 200 in the "old mode" (PICC mode).

[0207] In this design, the first card search request and the first carrier are different. In some embodiments, the first card search request can be an NFC signal transmitted at the access layer, and the first carrier can be an NFC signal transmitted at the physical layer. In some embodiments, the first card search request can be a modulated signal, indicating that the PCD device sending the first card search request supports a first NFC protocol. The first carrier, on the other hand, can be an unmodulated signal and may not indicate any information. In some examples, the first card search request may include multiple bit fields, while the first carrier does not include any bit fields. When sending the first card search request, the PCD device can first generate multiple bit fields, modulate these bit fields into corresponding carriers, and then transmit the carrier. After receiving the modulated carrier transmitted by the PCD device, the PICC device can demodulate it and obtain the multiple bit fields, thereby identifying these multiple bit fields. When the PCD device transmits the first carrier, it can directly generate and transmit the first carrier at the physical layer. After receiving the first carrier transmitted by the PCD device, the PICC device does not need to demodulate it but directly identifies the encoded features of the first carrier.

[0208] The description of the first carrier shown in the embodiments of this application is for illustrative purposes only. In other examples, the first carrier may also be an NFC signal transmitted 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 (e.g., indicating that the electronic device 100 is in PCD mode). In other examples, the first coding feature of the first carrier may also be other features, such as the fields included in the first carrier having the first coding feature. The embodiments of this application do not limit the specific form and content of the first carrier.

[0209] In some embodiments, in S102, the electronic device 100 may be in PICC mode by default when it is locked, or the electronic device 100 may be in PICC mode by default after the NFC function is enabled. Therefore, in S106, after the electronic device 100 receives the first carrier wave with the first encoding feature, it can open the PCD mode, and subsequently the electronic device 100 can switch between PICC mode and PCD mode regardless of whether it is in a locked state.

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

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

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

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

[0214] In other embodiments, the NFC module of the payment device 200 may operate only 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] Understandably, in order to conduct the target payment process with the peer device (i.e., the device that receives and identifies the first carrier), the receiving device 200 can switch from PCD mode to PICC mode after sending the first carrier to conduct a "new NFC signaling interaction" with the electronic device 100 in the "new mode" (PICC mode), avoiding the need to continue NFC signaling interaction related to NFC analog cards with the electronic device 100 in the "old mode" (PCD mode).

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

[0217] In some embodiments, electronic device 100 is in PCD mode in S106, and electronic device 100 in PCD mode can generate a radio frequency field. Payment device 200 switches to PICC mode in S107. Since the user has already brought the NFC module on electronic device 100 and the card-swiping area of ​​payment device 200 close together in 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: Electronic device 100 sends a first response to receiving device 200, indicating that the first carrier has been successfully identified.

[0219] In some embodiments, an electronic device 100 in PCD mode may send a first response to a receiving device 200 in PICC mode, the first response indicating successful identification of a first carrier.

[0220] In some embodiments, the first response is an NFC signal transmitted at the access layer. In some embodiments, the first response is a modulated signal, which may indicate successful identification of a first carrier. Not limited thereto, in other embodiments, the first response may also be a second carrier, which may have a second coded feature, the description of which is similar to that of the first coded feature. Optionally, the second carrier may be an unmodulated signal. Optionally, the second carrier may be an NFC signal transmitted at the physical layer, and the second carrier may not indicate any information. This application does not limit the form and content of the second carrier.

[0221] In some embodiments, after receiving a first response from electronic device 100, payment device 200 can determine that electronic device 100 supports the target payment process, and therefore can determine to conduct the target payment process with electronic device 100.

[0222] Understandably, after electronic device 100 switches from PICC mode to PCD mode, and receiving device 200 switches from PCD mode to PICC mode, electronic device 100 can send a first response indicating successful recognition of the first carrier to receiving device 200, instead of sending the first response in the "old mode" (PICC mode). This avoids the need for continued NFC signaling interaction related to NFC card simulation with receiving device 200 in the "old mode" (PICC mode) just to send the first response. Furthermore, transmitting the first response after the mode switch, instead of directly in the "old mode" (PICC mode), requires less modification to the NFC signal and internal device logic, making it more feasible.

[0223] S101-S109 implements the handshake negotiation between electronic device 100 and receiving device 200. After the handshake negotiation is successful (i.e., after S109), electronic device 100 can determine to initiate the target payment process with receiving device 200, and receiving device 200 can also determine to initiate the target payment process with electronic device 100. Therefore, both electronic device 100 and receiving device 200 can switch modes to conduct "new NFC signaling interaction" (including NFC signaling interaction at the access layer) in the "new mode," thereby completing the target payment process. For specific implementation details, please refer to S110-S117. Understandably, electronic device 100 and receiving device 200 initiate the target payment process after changing modes, rather than directly in the "old mode" after transmitting the first response. This requires less modification to the NFC signal and the internal logic of the devices, making it more feasible.

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

[0225] In some embodiments, electronic device 100 can activate PCD mode in S106, so after S106, electronic device 100 can switch between PICC mode and PCD mode. In S110, after sending the first response, 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 receiving device 200 in the "new mode" (PICC mode), thereby completing the target payment process. For specific implementation details, please refer to S112-S117.

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

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

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

[0229] Understandably, after receiving the first response, the receiving device 200 can switch from PICC mode to PCD mode to conduct a "new NFC signaling interaction" (including NFC signaling interaction at the access layer) with the electronic device 100 in the "new mode" (PCD mode) to complete the target payment process. For details, please refer to S112-S117.

[0230] In other embodiments, the NFC module of the payment device 200 may operate only 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: Electronic device 100 enters the radio frequency field of receiving device 200.

[0232] In some embodiments, the receiving device 200 switches to PCD mode in S111, and the receiving device 200 in PCD mode can generate a radio frequency field. The electronic device 100 switches to PICC mode in S110. Since the user has brought the location of the NFC module on the electronic device 100 and the card swiping area of ​​the receiving device 200 close to each other in S103, after the receiving 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 receiving device 200.

[0233] S113: The payment device 200 and the electronic device 100 perform NFC signaling interaction at the access layer.

[0234] In some embodiments, the payment device 200 in PCD mode and the electronic device 100 in PICC mode perform NFC signaling interaction at the access layer. Examples of NFC signaling interaction at the access layer can be found in Figures 11 and 12 below. 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, i.e., execute S114-S117 to complete the payment.

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

[0236] In some embodiments, a payment receiving device 200 in PCD mode can send NFC tag data of the payment receiving device 200 to an electronic device 100 in PICC mode. The NFC tag data includes identifiers of one or more payment applications supported by the payment receiving device 200. The NFC tag data includes information about the first order of the current payment, which 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 may include 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 description of the payment account, and the identifier of the payment account.

[0237] S115: Electronic device 100 determines a target payment application from among one or more payment applications supported by payment receiving device 200, based on the identifier of one or more payment applications supported by payment receiving device 200.

[0238] S116: Electronic device 100 launches the target payment application and displays the payment interface for 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 device 200. The electronic device 100 can then identify the payment application included in the NFC tag data as the target payment application. Specific examples are shown below:

[0240] In case 1.1, if the electronic device 100 has a target payment application installed in its application, then the electronic device 100 can launch the target payment application.

[0241] In 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 perform the subsequent steps. 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 to make the payment.

[0242] In other embodiments, the NFC tag data includes identifiers of multiple payment applications supported by the payment device 200, as shown in the following examples:

[0243] Scenario 2.1: If only one payment application installed on electronic device 100 belongs to the multiple payment applications supported by the aforementioned payment receiving device 200, then electronic device 100 can identify this one payment application as the target payment application and launch it. 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, then electronic device 100 can identify payment application A1 as the target payment application.

[0244] In scenario 2.2, if the electronic device 100 has multiple payment applications (referred to as candidate payment applications) installed that are supported by the payment receiving device 200, the electronic device 100 can determine whether the candidate payment applications include the user-set default payment application. If the candidate payment applications include the user-set default payment application, the electronic device 100 can identify the default payment application as the target payment application and launch it. If the candidate payment applications do not include the user-set default payment application, the electronic device 100 can select one candidate payment application from the candidate payment applications according to preset rules (e.g., random selection) and identify it as the target payment application, then launch it.

[0245] For example, the NFC tag data includes the identifiers of payment application A1 and payment application A2. The electronic device 100 has payment application A1, payment application A2 and payment application A3 installed. If the user sets payment application A1 as the default payment application, the electronic device 100 can launch payment application A1 to make a payment. If the user sets payment application A3 as the default payment application, the electronic device 100 can launch payment application A1 or payment application A2 to make a payment.

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

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

[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. A specific example can be found in the payment prompt window 712 shown in Figure 7B. Optionally, the electronic device 100 may display payment prompt information before determining and launching the target payment application. Optionally, the electronic device 100 may display payment prompt information after receiving the first carrier wave. Optionally, if the electronic device 100 is in an unlocked state in S102, the electronic device 100 may display payment prompt information even while in an unlocked state.

[0249] In some embodiments, in S102, the electronic device 100 is in an unlocked state. Before displaying the payment interface for 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 aforementioned payment prompt information (used to trigger payment). This input can be, for example, user input acting on the payment control 712C in the payment prompt window 712 shown in FIG. 7B. An explanation of authentication can be found in FIG. 7A-7G, and an example of the user interface for authentication can be found in the user interface 740 shown in FIG. 7E. If authentication is successful, the electronic device 100 switches from an unlocked state to an unlocked state and displays the payment interface for the first order through the target payment application in the unlocked state. If authentication fails, the electronic device 100 remains in an unlocked state 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 wired or wireless means to obtain payment discount information of the payment application from the cloud server 300. The payment discount information may include payment discount information for all users, or payment discount information for the user of the electronic device 100. The payment discount information may include payment discount information for the target payment application, or payment discount information for other payment applications, etc. The electronic device 100 can display the obtained payment discount information. In some examples, the electronic device 100 can display the payment discount information on the payment interface of the first order. In other examples, the electronic device 100 can also display the payment discount information before displaying the payment interface of the first order, for example, displaying the payment discount information when displaying the aforementioned payment prompt information; a specific example can be seen in the payment prompt window 712 shown in Figure 7B.

[0251] In some embodiments, when the electronic device 100 displays the payment interface for the first order, it can receive user input indicating that the user intends to pay for the first order. In response to this user input, the electronic device 100 can initiate the payment process for the first order with the receiving device 200. Optionally, in response to the user input, the electronic device 100 can perform payment verification for the user. A description of payment verification can be found in Figures 7A-7G, and an example of the user interface for payment verification can be found in the user interface 760 shown in Figure 7G. If the payment verification passes, the electronic device 100 can initiate the payment process for the first order with the receiving device 200; if the payment verification fails, the payment process for the first order may not be executed.

[0252] S117: Payment process for the first order between the payment receiving device 200 and the electronic device 100.

[0253] In some embodiments, the payment device 200 in PCD mode and the electronic device 100 in PICC mode can interact via NFC signaling to complete the payment process for the first order. Examples of implementation under different circumstances are shown below.

[0254] In scenario 3.1, the receiving device 200 can 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 receiving device 200 and the electronic device 100. The payment process under scenario 3.1 may include, but is not limited to, the following steps;

[0255] In step 1 of scenario 3.1, after receiving the NFC tag data sent by the receiving device 200, the electronic device 100 can send a first payment command to the receiving device 200. The first payment command carries the identifier of the target payment application and the identifier of the target payment account. Optionally, the first payment command may also carry one or more of the following: payment voucher for the first order (used to prove that the user has paid for the first order), the payment amount of the first order, and payment remarks. Optionally, the first payment command is used to request the receiving device 200 to execute the payment collection process. In some examples, different payment applications correspond to different payment accounts. After the electronic device 100 identifies 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 can 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 receiving account, and the identifier of the target paying account, and optionally may also include the payment voucher for the first order.

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

[0258] In some embodiments, after receiving payment information, the cloud server 300 can send a deduction notification to the electronic device 100. Upon receiving the deduction notification, the electronic device 100 can verify the user's payment. If the electronic device 100 verifies the user's payment, it can 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, it does not transfer the payment amount from the balance of the target payment account to the target receiving account.

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

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

[0261] In case 3.1, the method for confirming the payment amount for the first order is as follows:

[0262] In one possible implementation, the payment amount can be determined by the payment receiving device 200. The payment receiving device 200 can receive a payment amount input by the merchant, or it can determine the payment amount itself based on the price information of the goods purchased by the user. Optionally, the payment receiving device 200 can send the payment amount to the electronic device 100, for example, by carrying 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, thus eliminating the need for the electronic device 100 to receive the payment amount sent by the receiving device 200. The electronic device 100 can receive the payment amount entered by the user after the target payment application is launched, for example, when the user interface 750 shown in FIG. 7F is displayed. Optionally, the electronic device 100 can send the payment amount to the receiving device 200, for example, by including the payment amount in the first payment command shown in step 2 of case 3.1.

[0264] In scenario 3.2, electronic device 100 can send payment information to cloud server 300 (e.g., the server of the target payment application) to execute the payment process, thereby completing the payment process between receiving device 200 and electronic device 100. The payment process under 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 receiving 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 receiving account, and the identifier of the target payment account, and optionally may also include the payment voucher for the first order.

[0266] In step 2 of scenario 3.2, the cloud server 300 can deduct the payment amount from the balance of the target payment account and add the payment amount to the balance of the target receiving account based on the payment information. If the cloud server 300 successfully transfers the payment amount from the balance of the target payment account to the target receiving account, it can send a payment completion notification 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 receiving account, it can send a payment failure notification to the electronic device 100. In some embodiments, if the electronic device 100 receives a payment completion notification from the cloud server 300, it can output a payment completion prompt, which can be used to indicate successful payment. For example, the electronic device 100 can display the user interface 730 shown in FIG7D. If the electronic device 100 receives a payment failure notification from the cloud server 300, it can output a payment failure prompt, which can be used to indicate payment failure.

[0267] In some embodiments, after receiving payment information, the cloud server 300 can send a deduction notification to the electronic device 100. Upon receiving the deduction notification, the electronic device 100 can verify the user's payment. If the electronic device 100 verifies the user's payment, it can 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, it does not transfer the payment amount from the balance of the target payment account to the target receiving account.

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

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

[0270] In case 3.2, the method for confirming the payment amount for the first order is as follows:

[0271] In one possible implementation, the payment amount can be determined by the receiving device 200. The receiving device 200 can receive a payment amount input by the merchant, or it can determine the payment amount itself based on the price information of the goods purchased by the user. The receiving device 200 can send the payment amount to the electronic device 100 before step 1 of situation 3.2, for example, by carrying 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, thus eliminating the need for the electronic device 100 to receive the payment amount sent by the receiving device 200. The electronic device 100 can receive the payment amount entered by the user after the target payment application is launched, for example, when the user interface 750 shown in Figure 7F is displayed. Optionally, the electronic device 100 can send the payment amount to the receiving device 200, for example, by including the payment amount in the second payment response shown in step 3 of case 3.2.

[0273] Not limited to the embodiment shown in S117 of Figure 8, in other embodiments, the receiving device 200 and the electronic device 100 can also conduct the payment process for the first order through wireless communication technologies other than NFC. These other wireless communication technologies include, but are not limited to, one or more of Bluetooth, Wi-Fi, and UWB. Therefore, after the electronic device 100 receives the NFC tag data sent by the receiving device 200, for example, when the electronic device 100 displays the lock screen interface 710 shown in Figure 7B, 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 receiving device 200. This avoids the electronic device 100 being constantly close to the receiving device 200, and when the user needs to enter authentication or payment verification information on the electronic device 100, the electronic device 100 can be brought back to the user, thus improving the security of the user's payment.

[0274] Figure 9 is a flowchart illustrating another payment method provided in an embodiment of this application.

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

[0276] The payment method shown in Figure 9 may include, but is not limited to, the following steps:

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

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

[0279] S203: Electronic device 100 enters the radio frequency field of receiving device 200.

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

[0281] S205: Electronic device 100 does not launch the wallet application after receiving the first carrier wave.

[0282] S206: Electronic device 100 enters PCD mode after receiving the first carrier wave.

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

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

[0285] S201-S208 in Figure 9 are similar to S101-S108 in Figure 8. Please refer to the description of S101-S108 in Figure 8. They will not be repeated here.

[0286] In Figure 9, after steps S201-S204, electronic device 100 can determine whether to initiate a target payment process with receiving device 200. Receiving device 200 can, by default, determine whether to initiate a target payment process with electronic device 100 that has received the first carrier wave. Therefore, electronic device 100 can change from PICC mode to PCD mode (i.e., execute S206 of Figure 9), and receiving device 200 can switch from PCD mode to PICC mode (i.e., execute S207 of Figure 9) to perform a "new NFC signaling interaction" (including NFC signaling interaction at the access layer) in the "new mode," thereby completing the target payment process. For specific implementation details, see steps S209-S213 of Figure 9. Understandably, electronic device 100 and receiving device 200 initiate the target payment process after changing modes, rather than directly in the "old mode" after transmitting the first carrier wave. This requires less modification to the NFC signal and the internal logic of the device, making it more feasible.

[0287] S209: The payment device 200 and the electronic device 100 perform NFC signaling interaction 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. Examples of NFC signaling interaction at the access layer can be found in Figures 11 and 12 below. 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, i.e., execute steps S210-S213 to complete the payment.

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

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

[0291] The NFC tag data includes identifiers of one or more payment applications supported by the payment device 200. The NFC tag data also includes information about the first order of the current payment, which may include one or more of the following: the identifier of the first order, the payment amount of the first order, and the payee account information of the first order. The payee account information may include payee account information from the aforementioned one or more payment applications. The payee account information may include one or more of the following: the name of the payee account, the payee account's profile picture, the payee account's descriptive information, and the payee account's identifier.

[0292] S211: Electronic device 100 determines a target payment application from among one or more payment applications supported by payment receiving device 200, based on the identifier of one or more payment applications supported by payment receiving device 200.

[0293] S212: Electronic device 100 launches the target payment application and displays the payment interface for the first order through the target payment application.

[0294] S211-S212 in Figure 9 are similar to S115-S116 in Figure 8. Please refer to the description of S115-S116 in Figure 8. They will not be repeated here.

[0295] S213: Payment process for the first order between the payment receiving device 200 and the electronic device 100.

[0296] In some embodiments, the electronic device 100 in PCD mode and the payment device 200 in PICC mode can interact via NFC signaling to complete the payment process for the first order. The specific implementation is similar to that of S117 in Figure 8, and can be found in the description of S117 in Figure 8, which will not be repeated here. Not limited to the above embodiments, in other embodiments, S117 in Figure 8 and S213 in Figure 9 may also be implemented without interaction between the payment device 200 and the electronic device 100. The electronic device 100 and / or the payment device 200 can directly interact with the cloud server 300 to complete the payment for the first order.

[0297] S214: Electronic device 100 is in PICC mode with PCD mode off.

[0298] In some embodiments, in S202, the electronic device 100 is in PICC mode by default when it is not unlocked, or in S202, the electronic device 100 is in PICC mode by default after the NFC function is enabled. In S206, the electronic device 100 can turn on PCD mode after receiving a first carrier wave with a first coded feature. Therefore, after S213, the electronic device 100 can turn off PCD mode and enter PICC mode.

[0299] In some embodiments, S214 is an optional step. In S202, the electronic device 100 is in PICC mode in a time-division multiplexing state while in an unlocked state. In S206, the electronic device 100 is in PCD mode in a time-division multiplexing state after receiving a first carrier with a first coding feature. Therefore, after S213, the electronic device 100 can be in either PICC mode or PCD mode in a time-division multiplexing state without having to turn off PCD mode.

[0300] The payment method provided in this application embodiment allows an electronic device 100 in PICC mode to select a target payment application via NFC signaling when it is near a payment receiving device 200, regardless of whether it is in an unlocked state (e.g., screen off or screen on) or an unlocked state (e.g., screen on). The electronic device 100 can then use the target payment application to complete the payment with the payment receiving device 200, thus completing the target payment process. Therefore, by using a special first carrier wave, the problem that only an electronic device 100 in an unlocked state with its screen on can complete the payment using a payment application and the payment receiving device 200 is solved. The electronic device 100 can complete the payment without much user intervention, improving the efficiency of payment using the electronic device 100.

[0301] Furthermore, during the payment process for the first order between the payment receiving device 200 and the electronic device 100, the payment receiving device 200 can interact with the cloud server 300, or the electronic device 100 can interact with the cloud server 300. In other words, as long as either the payment receiving device 200 or the electronic device 100 is connected to the internet, the payment can be completed. Since the payment receiving device 200 is usually connected to the internet, the electronic device 100 does not need to be connected to the internet to complete the payment. Users do not need to manually enable the internet access function of the electronic device 100, which further improves the efficiency of users using the electronic device 100 for payment.

[0302] Not limited to the above embodiments, 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 is similar to S208-S213 shown in Figure 9, and can be found in the description of S208-S213 in Figure 9, which will not be repeated here. In this way, even if the electronic device 100 is an "unupgraded device" that cannot recognize the first carrier, it can still complete the payment normally using the payment application and the payment device 200 in the screen-on and unlocked state. Therefore, the payment method provided by the embodiments of this application is backward compatible with "unupgraded devices" and has a wide range of application scenarios.

[0303] The following example illustrates the first carrier wave transmitted by the payment receiving device 200.

[0304] Figure 10 is a schematic diagram of a payment receiving device 200 transmitting a first carrier wave according to an embodiment of this application.

[0305] As shown in Figure 10, the receiving device 200 can transmit multiple first carriers, which can be sequentially named as the 1st first carrier, the 2nd first carrier, the 3rd first carrier, and so on, according to their transmission time from earliest to latest. Each of the multiple first carriers includes N1 subcarriers, which can be sequentially named as subcarrier 1, subcarrier 2, ..., subcarrier N1, according to their transmission time from earliest to latest. The amplitude of each of the N1 subcarriers is a first amplitude (not shown). The duration of each of the N1 subcarriers is a first duration T1. The time interval between any two adjacent 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 of the multiple first carriers is a second duration T3, where T3 = T1 × N1 + T2 × (N1 - 1). The time interval between the first and second carrier waves is called time interval 1, and the time interval between the second and third carrier waves is called time interval 2. Time interval 1 and time interval 2 can be equal or unequal.

[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 × N1 + T2 × (N1 - 1) = 10.05 ms. This application does not limit the specific values ​​of T1, T2, N1, and T3 in its embodiments.

[0307] The following example illustrates the process of NFC signaling interaction at the access layer between the payment device 200 and the electronic device 100.

[0308] Figure 11 is a flowchart illustrating an NFC signaling interaction process at the access layer provided in an embodiment of this application.

[0309] As shown in Figure 11, this NFC signaling interaction process can be applied to an NFC system that includes a PCD device and a PICC device. In some examples, the PCD device is a receiving device 200 in PCD mode and the PICC device is an electronic device 100 in PICC mode; in this case, the process shown in Figure 11 can be an implementation of S113 shown in Figure 8. In other examples, the PCD device is an electronic device 100 in PCD mode and the PICC device is a receiving device 200 in PICC mode; in this case, the process shown in Figure 11 can be an implementation of S209 in Figure 9.

[0310] The NFC signaling interaction process shown in Figure 11 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 the 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 a 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 a first NFC protocol. In some examples, the first NFC protocol is a Class A NFC protocol, and the first card search request can be REQA. In some examples, the first NFC protocol is a Class B NFC protocol, and the first card search request can be REQB. In some examples, the first NFC protocol is a Class F NFC protocol, and 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 receiving device 200 in PCD mode. After receiving a first card search request from the payment receiving device 200 in PCD mode, the electronic device 100 in PICC mode can determine not to launch the wallet application since it has already received a first carrier wave with the first encoding feature. The application to be launched will be selected during subsequent NFC signaling interactions at the application layer. For example, the target payment application can be launched after receiving NFC tag data from the payment receiving device 200, ensuring that the electronic device 100 uses the target payment application to complete the payment with the payment receiving device 200, thus meeting the user's needs for NFC payments.

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

[0316] In some embodiments, the first card search response can be used to indicate that the PICC device supports a 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, if the first NFC protocol is a Type A NFC protocol, then the first card search request can be REQA, and the first card search response can be an answer to request type A (ATQA).

[0318] In some examples, the first NFC protocol is a Type B NFC protocol, then the first card search request can be REQB, and the first card search response can be a Type B request response (ATQB).

[0319] In some examples, the first NFC protocol is the F-type NFC protocol, then the first card search request can be SENSF_REQ, and the first card search response can 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 anticollision response to the PCD device.

[0322] In some embodiments, since multiple PICC devices (e.g., NFC tags comprising multiple entities or devices in PICC mode) may exist simultaneously within the radio frequency field of the PCD device, if multiple PICC devices interact with the PCD device via NFC signaling, the NFC commands or responses sent by these multiple PICC devices will collide, causing the PCD device to be unable to correctly parse the NFC commands or responses. Therefore, the PCD device only interacts with one PICC device via NFC signaling. Thus, the PCD device can select one PICC device to interact with via NFC by sending an anti-collision command. This anti-collision command can be used to select a target PICC device to interact with via NFC signaling. After receiving the anti-collision command, multiple PICC devices may send anti-collision responses to the PCD device. The anti-collision responses sent by the PICC devices 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 to interact with the target PICC device (i.e., the PICC device shown in Figure 11) via NFC signaling based on the feedback result carried in one or more anti-collision responses.

[0323] In some embodiments, steps S303 and S304 are optional. If, after sending the first card search request, the PCD device only receives a first card search response from one PICC device as shown in FIG11, and does not receive card search responses from other PICC devices, then the PCD device and the PICC device shown in FIG11 may not execute steps S303 and S304, but instead execute steps 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 can determine to select the PICC device shown in FIG11, and therefore can send a selection command to the PICC device. After receiving the selection command, the PICC device can send an SAK command to the PCD device.

[0327] In some embodiments, the SAK command can indicate whether the application layer NFC protocol is supported. If the SAK command indicates support for the application layer NFC protocol, the PCD device can 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 can choose not to perform application layer NFC signaling interaction with the PICC device.

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

[0329] Figure 12 is a schematic diagram of another access layer NFC signaling interaction provided in an embodiment of this application.

[0330] As shown in Figure 12, this NFC signaling interaction process can be applied to an NFC system that includes 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; in this case, the process shown in Figure 12 can be an implementation of S113 shown in 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; in this case, the process shown in Figure 12 can be an implementation of S209 in Figure 9.

[0331] The NFC signaling interaction process shown in Figure 12 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 a 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 probe frames, which can be used to indicate that the PCD device supports a 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 receiving device 200 in PCD mode. After receiving a Probe frame from the payment receiving device 200 in PCD mode, the electronic device 100 in PICC mode may not launch the wallet application. The application can be selected for launch during subsequent application-layer NFC signaling interactions, for example, launching the target payment application after receiving NFC tag data from the payment receiving device 200. For instance, after receiving a Probe frame from the payment receiving device 200, the electronic device 100 can determine not to launch the wallet application because it has already received a first carrier wave with a first encoding feature.

[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 a Probe ACK frame to the PCD device.

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

[0339] In some embodiments, the PCD device can notify the PICC device of its device characteristics information via a Notify frame, thereby indicating the PCD device's business intent to the PICC device.

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

[0341] The Service Identifier (SID) can be used to indicate the type of NFC service supported by the PCD device on the basis of NFC functionality. NFC services include one or more of the following: access control, keys, transportation, banking, digital currency, digital certificates, codeless payment, electronic tickets, wireless charging, tap-to-pay, multi-function cards, etc.

[0342] The Device Organization Identifier (OUI) can be used to indicate the manufacturer providing NFC services using the PCD device. For example, manufacturers providing NFC services may include one or more smart lock manufacturers, one or more property management companies, one or more automotive parts manufacturers, one or more transportation card management departments, etc.

[0343] A Device Group Identifier (GID) can be used to indicate the group to which the NFC service provided by the PCD device belongs. The Device Group Identifier can be assigned based on the purpose and location of the receiving device 200. Different NFC services can be assigned to different groups.

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

[0345] In some embodiments, after receiving a Notify frame, the PICC device may reply with 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 an electronic device 100 in PICC mode, and the PCD device is a payment receiving device 200 in PCD mode. After receiving a Notify frame, the electronic device 100 can perform an action corresponding to the device characteristic information of the payment receiving device 200 carried in the Notify frame, such as a codeless payment prompt. An example of a codeless payment prompt can be found in the payment prompt window 712 shown in Figure 7B.

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

[0348] S406: The PICC device sends a parameter negotiation response to the PCD device.

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

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

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

[0352] Understandably, when the electronic device 100 in PCD mode approaches 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. The electronic device 100 can read the NFC tag data of the payment device 200 and complete the payment using the target payment application and the payment device 200, thus realizing the target payment process. For a specific process example, please refer to S209-S213 in Figure 9, and for specific scenario examples, please refer to Figures 6A-6C.

[0353] The above embodiments use an electronic device 100 that supports the identification of the first carrier as an example. In other embodiments, there may also be an electronic device 400 that does not support the identification of the first carrier. When the electronic device 400 in PICC mode approaches the receiving device 200 in PCD mode, the receiving 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, therefore it will not launch the wallet application or perform any other processing. When the electronic device 400 in PCD mode approaches the receiving device 200 in PICC mode, the electronic device 400 in PCD mode can perform NFC signaling interaction at the access layer with the receiving device 200 in PICC mode. The electronic device 400 can read the NFC tag data of the receiving device 200 and complete the payment using the target payment application and the receiving device 200, thus realizing the target payment process.

[0354] The following describes another structure of the electronic device 100 provided in the embodiments of this application.

[0355] Figure 13 is a schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application.

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

[0357] As shown in Figure 13, 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, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity 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, and an electrocardiogram sensor 180N, etc.

[0358] Processor 110 may include one or more processing units, such as: application processor (AP), microcontroller unit (MCU), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. The different processing units may 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 microcontroller unit may include a graphics processor.

[0359] In some embodiments, the electronic device 100 (e.g., a wearable device) implements display functions via a GPU, a display screen 194, an application processor, a microcontroller unit, etc. The GPU is a microprocessor for image processing, connected to the display screen 194, the application processor, and the microcontroller unit. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0360] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0361] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0362] In some embodiments, the processor 110 may include one or more interfaces. 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, etc.

[0363] Internal memory 121 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM). 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 read and write operations by the processor 110.

[0364] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via a USB interface 130. In some wireless charging embodiments, the charging management module 140 receives 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 supply power to the electronic device 100 via the power management module 141.

[0365] The power management module 141 connects 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 supplies power to the processor 110, internal memory 121, display screen 194, wireless communication module 160, and sensor module 180, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

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

[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 one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0368] The mobile communication module 150 can provide wireless communication solutions for applications on the electronic device 100, including second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G) mobile communication technologies. The mobile communication module 150 may include at least one filter, switch, power amplifier, low-noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0369] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates 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 processing by the baseband processor, the low-frequency baseband signal is transmitted to an application processor or microcontroller unit. The application processor or microcontroller unit outputs sound signals through an audio device (not limited to speaker 170A, microphone 170B, etc.) or displays images or videos through a display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and housed within the same device as the mobile communication module 150 or other functional modules.

[0370] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), Sparklink Alliance-specific wireless communication technologies (such as Sparklink Low Energy (SLE) and Sparklink Basic (SLB)), and intrabody communication (IBC). The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0371] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via 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, Starflash, and / or IBC technology, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0372] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may 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 miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0373] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0374] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, 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, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and color. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0375] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. 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, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0376] A digital signal processor is used to process digital signals.

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

[0378] NPU stands for Neural Network (NN) Computation Processor.

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

[0380] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

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

[0382] Microphone 170B, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170B, inputting the sound signal into microphone 170B. Electronic device 100 may have at least one microphone 170B. In some embodiments, electronic device 100 may have two microphones 170B, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic device 100 may also have three, four, or more microphones 170B, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, 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 disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the intensity of the touch operation based on pressure sensor 180A. Electronic device 100 can also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

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

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

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

[0387] The 180E accelerometer can detect the magnitude of acceleration of electronic device 100 in various directions (typically three axes). When electronic device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of electronic devices and applied to applications such as screen orientation switching and pedometers.

[0388] 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 photodetector.

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

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

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

[0393] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to processor 110 (such as an application processor or microcontroller unit) to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0394] The 180L ambient light sensor is used to detect ambient light intensity.

[0395] The 180M heart rate sensor can be used for heart rate detection. The 180N electrocardiogram (ECG) sensor can be used for ECG detection.

[0396] Buttons 190 include a power button, volume buttons, etc. Motor 191 can generate vibration feedback.

[0397] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate 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, i.e., an 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 description illustrates the method provided in the embodiments of this application. In order to facilitate better implementation of the above solutions in the embodiments of this application, the embodiments of this application also provide corresponding devices or equipment.

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

[0401] The communication device of the present application embodiment will now be described in detail with reference to Figures 14 to 17.

[0402] Referring to FIG14, which is a schematic diagram of a communication device 1400 provided in an embodiment of this application, the communication device 1400 can be the electronic device 100 in the above embodiments. In some embodiments, the communication device 1400 can be a chip / chip system, such as an NFC chip. As shown in FIG14, the communication device 1400 may include a transceiver unit 1410 and a processing unit 1420.

[0403] The transceiver unit 1410 shown in Figure 14 can be used to perform the NFC sending and NFC receiving functions performed by the electronic device 100 in the above embodiments of this application.

[0404] In some embodiments, the processing unit 1420 shown in FIG14 can be used to perform functional steps related to NFC protocol parsing and encapsulation, NFC service processing flow and display performed by the electronic device 100 in the above embodiments of this application.

[0405] It should be understood that the communication device 1400 in this design can perform the method steps executed by the electronic device 100 in the aforementioned embodiments, and for the sake of brevity, it will not be described again here.

[0406] Referring to FIG15, which is a schematic diagram of a communication device 1500 provided in an embodiment of this application, the communication device 1500 can be the payment receiving device 200 in the above embodiments. As shown in FIG15, the communication device 1500 may include a transceiver unit 1510 and a processing unit 1520.

[0407] The transceiver unit 1510 shown in Figure 15 can be used to perform the NFC sending and NFC receiving functions performed by the payment device 200 in the above embodiments of this application.

[0408] In some embodiments, the processing unit 1520 shown in FIG15 can be used to perform functional steps such as NFC protocol parsing and encapsulation and NFC service processing flow performed by the payment receiving device 200 in the above embodiments of this application.

[0409] It should be understood that the communication device 1500 in this design can perform the method steps executed by the payment device 200 in the aforementioned embodiment, and for the sake of brevity, it will not be described again here.

[0410] The above describes the electronic device 100 and the payment device 200 of the embodiments of this application. It should be understood that any product with the functions of the electronic device 100 described in FIG14 above, and any product with the functions of the payment device 200 described in FIG15 above, falls within the protection scope of the embodiments of this application.

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

[0412] Referring to Figure 16, Figure 16 is a schematic diagram of the structure of a communication device 1600 provided in an embodiment of this application. The communication device 1600 can be an electronic device 100, or a device therein. As shown in Figure 16, the communication device 1600 includes a processor 1601 and a transceiver 1602 internally connected and communicating with the processor 1601. The processor 1601 can be a general-purpose processor or a dedicated processor, etc. For example, it can be a central processing unit and / or an NFC controller, etc. The transceiver 1602 can be referred to as a transceiver unit, transceiver, or 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 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 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 (not shown in FIG. 16), such as an NFC antenna, wherein the NFC antenna may be a coil-type antenna. The antenna 1603 and / or the radio frequency unit may be located inside the communication device 1600 or may be separate from the communication device 1600, i.e., the antenna 1603 and / or the radio frequency unit may be remotely or distributedly deployed.

[0414] In some embodiments, the communication device 1600 may include one or more memories 1604, which may store instructions, which may be computer programs, that can be executed on the communication device 1600 to cause 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] The processor 1601, transceiver 1602, and memory 1604 shown in Figure 16 can 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 foregoing embodiments: the processor 1601 can be used to perform the functional steps related to NFC protocol parsing and encapsulation, NFC service processing flow and display performed by the electronic device 100 in the foregoing embodiments of this application and / or other processes used in the technology described in the embodiments of this application; the transceiver 1602 can be used to perform the functional steps related to NFC sending and NFC receiving performed by the electronic device 100 in the foregoing embodiments of this application and / or other processes used in the technology described herein.

[0417] In any of the above designs, the processor 1601 may include a transceiver for implementing receive and transmit 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 receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0418] In any of the above designs, the processor 1601 may store instructions, which may be computer programs. These computer programs, running on the processor 1601, cause the communication device 1600 to execute the method steps performed by the electronic device 100 in the above embodiments of this application. The computer program may be embedded in the processor 1601; in this case, the processor 1601 may be implemented in hardware.

[0419] In one implementation, the communication device 1600 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), 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 is not limited to that shown in FIG16. Communication device 1600 may be a standalone device or part of a larger device. For example, the communication device 1600 may be:

[0421] (1) A standalone integrated circuit IC, or chip, or chip system or subsystem; (2) A collection of one or more ICs, optionally including storage components for storing data or computer programs; (3) An ASIC, such as an NFC chip; (4) A module that can be embedded in other devices; (5) A receiver, terminal, smart terminal, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) Others, etc.

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

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

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

[0425] The processor 1701, transceiver 1702, and memory 1704 shown in Figure 17 can 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 foregoing embodiments: the processor 1701 can be used to perform the functional steps related to NFC protocol parsing and encapsulation, NFC service processing flow and / or other processes used in the technology described herein, performed by the payment device 200 in the foregoing embodiments of this application; the transceiver 1702 can be used to perform the functional steps related to NFC sending and NFC receiving performed by the payment device 200 in the foregoing embodiments of this application and / or other processes used in the technology described herein.

[0427] In any of the above designs, the processor 1701 may include a transceiver for implementing receive and transmit 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 receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

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

[0429] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps performed by the electronic device 100 in the above-described method embodiments.

[0430] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps performed by the payment device 200 in the above-described method embodiments.

[0431] This application also provides a computer program product, including a computing program, which, when run on a computer, enables the computer to perform the steps executed by the electronic device 100 in the above-described method embodiments.

[0432] This application also provides a computer program product, including a computing program, which, when run on a computer, enables the computer to perform the steps executed by the payment receiving device 200 in the above-described method embodiments.

[0433] This application also provides a chip system, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to perform the steps executed by the electronic device 100 in any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0434] This application also provides a chip system, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to perform the steps executed by the payment receiving device 200 in any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0435] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A near-field communication (NFC) system, characterized in that, This includes electronic devices and payment collection devices, among which, The receiving device is used to send a first carrier via NFC when in proximity coupling device (PCD) mode, wherein the first carrier has a first encoding feature; The electronic device is configured to receive the first carrier wave sent by the receiving device in the PCD mode via NFC when in the proximity smart card PICC mode. The electronic device is configured to, after receiving the first carrier wave sent by the receiving device via NFC, activate the PCD mode, perform NFC signaling interaction with the receiving device, and complete the payment using the first payment application and the receiving device.

2. The NFC system as described in claim 1, characterized in that, The electronic device is specifically configured to, after receiving the first carrier wave sent by the receiving device via NFC, perform NFC signaling interaction with the receiving device at the access layer, and then receive NFC tag data sent by the receiving device, wherein the NFC tag data includes the identifiers of one or more payment applications supported by the receiving device; The electronic device is specifically used to identify the first payment application from the one or more payment applications, and to complete the payment using the first payment application and the receiving device.

3. The NFC system as described in claim 1 or 2, characterized in that, The first payment application is a host-based card emulation HCE application.

4. The NFC system as described in any one of claims 1-3, characterized in that, The payment device is also used to switch from the PCD mode to the PICC mode after sending the first carrier via NFC in the PCD mode; The electronic device is further configured to generate a radio frequency field when the PCD mode is activated after the PCD mode is turned on. The electronic device is further configured to send a first response via NFC to the receiving device in the PICC mode in the PCD mode after the receiving device, which has switched from the PCD mode to the PICC mode, enters the radio frequency field of the electronic device, wherein the first response indicates successful identification of the first carrier. The electronic device is further configured to switch from the PCD mode to the PICC mode after sending the first response via NFC to the receiving device in the PICC mode in the PCD mode. The payment receiving device is further configured to switch from the PICC mode to the PCD mode after receiving the first response sent by the electronic device via NFC, and generate a radio frequency field when in the PCD mode; The electronic device is specifically used to perform NFC signaling interaction with the receiving device after switching from the PCD mode to the PICC mode, and to complete the payment using the first payment application and the receiving device.

5. The NFC system as described in any one of claims 1-3, characterized in that, The payment device is also used to switch from the PCD mode to the PICC mode after sending the first carrier via NFC in the PCD mode; The electronic device is further configured to generate a radio frequency field when the PCD mode is activated after the PCD mode is turned on. The electronic device is specifically used to perform NFC signaling interaction between the receiving device in the PCD mode and the receiving device in the PICC mode after the receiving device switches from the PCD mode to the PICC mode enters the radio frequency field of the electronic device, and to complete the payment using the first payment application and the receiving device.

6. The NFC system according to any one of claims 1-5, characterized in that, When the electronic device completes a payment using the first payment application and the receiving device, it is specifically used for: Send a first payment command to the payment receiving device, wherein the first payment command carries the identifier of the first payment application and the identifier of the first payment account, the first payment account being the payment account corresponding to the electronic device in the first payment application, and the first payment command being used to request the payment receiving device to execute the payment receiving process; The payment device is further configured to send payment information to the cloud server after receiving the first payment command sent by the electronic device. The payment information includes a payment amount, an identifier of the first payment account, and an identifier of the first payment account. The first payment account is the payment account corresponding to the payment device in the first payment application. 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 the first payment response to the electronic device, wherein the first payment response carries a payment result.

7. The NFC system according to any one of claims 1-6, characterized in that, Specifically, the electronic device is used to receive the first carrier wave sent by the receiving device in the PCD mode via NFC when it is in the PICC mode in an unlocked state.

8. The NFC system according to any one of claims 1-6, characterized in that, The electronic device is a wearable device; specifically, the electronic device is used to receive the first carrier wave sent by the receiving device in the PCD mode via NFC when it is in the PICC mode or in the unlocked state.

9. The NFC system according to any one of claims 1-8, characterized in that, The electronic device is also configured to, after completing the payment using the first payment application and the receiving device, close the PCD mode and enter the PICC mode.

10. The NFC system as described in claim 4, characterized in that, The payment receiving device is configured to send a first card search request via NFC to the electronic device that has switched from the PCD mode to the PICC mode after switching from the PICC mode to the PCD mode. The first card search request is used to indicate that the payment receiving device supports a first NFC protocol. The first card search request is different from the first carrier. The electronic device is configured 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 receiving device is configured to send an identifier of one or more payment applications supported by the payment receiving device to the electronic device after receiving the first card search response sent by the electronic device via NFC; The electronic device is configured to identify the first payment application from the one or more payment applications and complete the payment using the first payment application and the receiving device.

11. The NFC system as described in claim 10, characterized in that, The carrier corresponding to the first card search request is modulated, while the first carrier is unmodulated.

12. The NFC system as described in claim 10 or 11, characterized in that, The electronic device is configured not to launch its wallet application after receiving the first carrier wave sent by the receiving device via NFC. The electronic device is configured not to launch its wallet application after receiving the first card search request sent by the payment device via NFC.

13. The NFC system according to any one of claims 1-12, characterized in that, 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 of the N subcarriers is a preset first amplitude, the duration of each of 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, wherein N is a positive integer greater than 1.

14. A payment method applied to electronic devices, characterized in that, include: When in PICC mode, the first carrier wave transmitted by the receiving device in PCD mode is received via NFC, wherein the first carrier wave has a first encoding feature; After receiving the first carrier wave sent by the receiving device via NFC, the PCD mode is activated, NFC signaling interaction is performed with the receiving device, and the payment is completed using the first payment application and the receiving device.

15. The method as described in claim 14, characterized in that, The process of interacting with the receiving device via NFC signaling and completing the payment using the first payment application and the receiving device includes: It performs NFC signaling interaction at the access layer with the payment device; Receive NFC tag data sent by the payment device, wherein the NFC tag data includes identifiers of one or more payment applications supported by the payment 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 receiving device.

16. The method as described in claim 14 or 15, characterized in that, The first payment application is an HCE application.

17. The method according to any one of claims 14-16, characterized in that, The method further includes: After the PCD mode is turned on, a radio frequency field is generated while in the PCD mode; After the receiving device switches from the PCD mode to the PICC mode after sending the first carrier, it enters the radio frequency field of the electronic device and sends a first response via NFC to the receiving device in the PICC mode in the PCD mode. The first response indicates successful identification of the first carrier and is used by the receiving device to switch from the PICC mode to the PCD mode after receiving the first response. After sending a first response via NFC to the receiving device in PICC mode in PCD mode, the system switches from PCD mode to PICC mode. The process of interacting with the receiving device via NFC signaling and completing the payment using the first payment application and the receiving device includes: After switching from the PCD mode to the PICC mode, the system performs NFC signaling interaction with the receiving device that has switched from the PICC mode to the PCD mode, and completes the payment using the first payment application and the receiving device.

18. The method according to any one of claims 14-16, characterized in that, The method further includes: After the PCD mode is turned on, a radio frequency field is generated while in the PCD mode; The process of interacting with the receiving device via NFC signaling and completing the payment using the first payment application and the receiving device includes: After the receiving device switches from the PCD mode to the PICC mode after sending the first carrier, it enters the radio frequency field of the electronic device. In the PCD mode, the receiving device and the receiving device that switched from the PCD mode to the PICC mode perform NFC signaling interaction, and the payment is completed using the first payment application and the receiving device.

19. The method according to any one of claims 14-18, characterized in that, The process of completing the payment using the first payment application and the receiving device includes: A first payment command is sent to the receiving device, wherein the first payment command carries the identifier of the first payment application and the identifier of the first payment account, the first payment account being the payment account corresponding to the electronic device in the first payment application, and the first payment command is used to request the receiving device to execute a payment process, the payment process being the process by which the receiving device requests the cloud server to transfer the payment amount from the first payment account to the first receiving account, the first receiving account being the receiving account corresponding to the receiving device in the first payment application; The method further includes: Receive a first payment response sent by the payment receiving device, wherein the first payment response carries a payment result.

20. The method according to any one of claims 14-19, characterized in that, The step of receiving a first carrier wave transmitted by the receiving device in PCD mode via NFC when in PICC mode includes: When in the PICC mode while locked, the first carrier wave sent by the receiving device in the PCD mode is received via NFC.

21. The method according to any one of claims 14-19, characterized in that, The electronic device is a wearable device; the step of receiving the first carrier wave transmitted by the receiving device in PCD mode via NFC when in PICC mode includes: When in the PICC mode (either in an unlocked state or an unlocked state), the first carrier wave sent by the receiving device in the PCD mode is received via NFC.

22. The method according to any one of claims 14-21, characterized in that, The method further includes: After completing the payment using the first payment application and the receiving device, the PCD mode is turned off and the device enters the PICC mode.

23. The method as described in claim 17, characterized in that, After switching from PCD mode to PICC mode, the process involves NFC signaling interaction with the receiving device that has switched from PICC mode to PCD mode, and completing the payment using the first payment application and the receiving device, including: After switching from the PCD mode to the PICC mode, the first card search request sent by the receiving device that has switched from the PICC mode to the PCD mode is received via NFC. The first card search request is used to indicate that the receiving device supports the first NFC protocol. The first card search request is different from the first carrier. A first card search response is sent 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; Receive the identifiers of one or more payment applications supported by the payment device, sent by the payment 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 receiving device.

24. The method as described in claim 23, characterized in that, The carrier corresponding to the first card search request is modulated, while the first carrier is unmodulated.

25. The method as described in claim 23 or 24, characterized in that, After receiving the first carrier wave sent by the receiving device via NFC, the electronic device does not launch the wallet application of the electronic device; After receiving the first card search request sent by the receiving device via NFC, the electronic device does not launch the wallet application of the electronic device.

26. The method according to any one of claims 14-25, characterized in that, 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 of the N subcarriers is a preset first amplitude, the duration of each of 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, wherein N is a positive integer greater than 1.

27. An electronic device, characterized in that, The device includes a processor, a memory, and a transceiver, wherein the memory stores a computer program, and the processor invokes the computer program to perform the method as described in any one of claims 14-26.

28. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, is used to implement the method as described in any one of claims 14-26.

29. A computer program product, characterized in that, When the computer program product is run on a processor, it is used to implement the method as described in any one of claims 14-26.

30. A chip system, characterized in that, It includes a processing circuit and an interface circuit, the interface circuit being used to receive code instructions and transmit them to the processing circuit, the processing circuit being used to execute the code instructions to perform the method as described in any one of claims 14-26.

Images