Display method, electronic device and computer storage medium

Abstract

Provided in the present application are a display method, an electronic device and a computer storage medium. The method is applied to a first device. The method comprises: receiving a first near-field communication (NFC) signal sent by a second device; acquiring the state of the first device; on the basis of the state of the first device, determining whether to display a NFC card reading interface; when the first device is in a first state, displaying the NFC card reading interface; and, when the first device is in a second state, not displaying the NFC card reading interface, the first state being different from the second state, wherein the second state is related to the second device. When the first device is in the second state, the distance between the first device and the second device is less than or equal to a first distance, and the state of motion of the first device with respect to the second device is a static state. For example, the second state is a state in which the first device remains close to the second device. Therefore, whether to display the NFC card reading interface can be selected on the basis of device state sensing, so as to improve user experience and reduce device power consumption.

Description

Display method, electronic device, and computer storage medium

[0001] This application claims priority to the Chinese patent application with application number 202410183535.0 filed with the State Intellectual Property Office of China on February 19, 2024, and priority to the Chinese patent application with the invention name “Display method, electronic device and computer storage medium”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of computer technology, and in particular to a display method, an electronic device, and a computer storage medium. Background Art

[0003] Currently, vehicle center consoles can integrate near-field communication (NFC) card readers. When a mobile terminal (such as a mobile phone or wearable device) is placed on the vehicle's center console, the mobile terminal will pop up an NFC card reader interface. The vehicle can then authenticate the NFC car key activated on the mobile terminal through the NFC card reader area, enabling the vehicle to be controlled (such as starting) without a physical car key. However, when the mobile terminal remains in the vehicle's center console, the NFC card reader interface will frequently pop up, affecting the user experience and increasing power consumption. Summary of the Invention

[0004] The present application discloses a display method, an electronic device, and a computer storage medium, which can select whether to display an NFC card reader interface based on the state perception of the device, thereby improving the user experience and reducing the power consumption of the device.

[0005] In the first aspect, the present application provides a display method, which is applied to a first device, and the method includes: the first device (such as a mobile terminal with an integrated near-field communication NFC module, such as a mobile phone) receives a first near-field communication NFC signal sent by a second device (such as a vehicle, door, payment device, etc. with an integrated NFC card reading area); the first device obtains the status of the first device, and determines whether to display the NFC card reading interface based on the obtained status of the first device; when the first device is in the first state, the first interface (i.e., the NFC card reading interface) is displayed; when the first device is in the second state, the second interface is displayed, the first state and the second state are different, the first interface and the second interface are different (i.e., the second interface is not the NFC card reading interface), and the second state is related to the second device. It can be understood that the second state is a state of multiple NFC communication processes with the second device.

[0006] In some examples, when the first device is in the second state, the distance between the first device and the second device is less than or equal to the first distance (for example, the distance between the NFC card reading area of ​​the first device and the second device is less than or equal to the first distance), and the motion state of the first device relative to the second device is a stationary state. It can be understood that when the distance between the first device and the second device (such as the NFC card reading area) is very close and the first device and the second device remain relatively stationary, that is, when the first device remains close to the second device (such as the NFC card reading area), the first device is in the second state. Based on the characteristics of NFC, it can be obtained that when the distance between the first device and the second device is close, an NFC communication process (such as an NFC card reading process) will be triggered, and when the first device and the second device remain close to each other, the second device will send an NFC signal to the first device multiple times (for example, periodically) to trigger the NFC communication process. For example, when the first device is in the second state, at a first moment, the first device receives a first NFC signal sent by the second device (for waking up the NFC module of the first device), and at a second moment after the first moment, the first device will receive the first NFC signal sent by the second device again.

[0007] In the above method, after the first device receives the first NFC signal sent by the second device, it will first obtain its own status and determine whether to display the NFC card reader interface (displaying the NFC card reader interface can also be referred to as card pop-up) based on the obtained status. When the first device is in the second state, the NFC card reader interface will not be displayed, instead of displaying the NFC card reader interface as soon as the first NFC signal is received. Among them, when the first device is in the second state, it will believe that it is currently in a scenario where the first device remains close to the second device, rather than a "one-time card sticking" scenario. Taking into account the usage habits of most users, when the first device remains close to the second device (that is, when in the second state), users often do not want to perform multiple NFC card readings. Therefore, the first device does not display the NFC card reader interface when it is in the second state, which can avoid the situation where the NFC card reader interface frequently pops up due to the first device receiving the first NFC signal from the second device multiple times. This not only greatly improves the user experience, but also reduces unnecessary device power consumption.

[0008] In one possible implementation, the second state includes a state in which the first device is wirelessly charged by the second device, and the first device receives wireless charging input from the second device. For example, the NFC card reader area and the wireless charging area of ​​the second device are integrated.

[0009] In the above method, the first device can determine whether to display the NFC card reader interface according to whether it is currently in a wireless charging state. When the first device is in a state of wireless charging through the second device, especially when the NFC card reading area and the wireless charging area of ​​the second device are integrated together, the first device can assume that the current user's purpose of being close to the first device and the second device is to wirelessly charge the first device through the second device rather than to read the NFC card. Therefore, the first device will not display the NFC card reader interface. This can avoid the situation where the NFC card reader interface frequently pops up on the first device when the user is wirelessly charging the first device, and more accurately suppresses the situation of false card pop-ups caused by receiving the first NFC signal, greatly improving the user experience, and solving the problem of reduced charging efficiency of the first device caused by this situation.

[0010] In one possible implementation, the second state includes: the first device and the second device are connected via a first short-range communication method, and the motion posture of the first device is a stationary posture, wherein the first short-range communication method and the NFC communication method are different, for example, Bluetooth, ultra-wideband UWB, star flash or infrared.

[0011] It can be understood that the motion posture of the first device is different from the motion state of the first device relative to the second device. The motion posture of the first device is the posture of the first device itself moving in the space, such as rotation, translation, and stationary (i.e., remaining motionless), while the motion state of the first device relative to the second device represents whether the first device and the second device are relatively stationary or in relative motion.

[0012] In the above method, the second state includes that the first device and the second device are connected through the first short-range communication method. The first device can consider that the distance between the first device and the second device is relatively close, which can avoid the situation where the user of the first device performs NFC card reading at a distance from the second device. The second state also includes that the movement posture of the first device is a static posture. The first device can consider that the first device remains motionless, which can avoid the scenario where the user uses the first device to perform "one-time card sticking". Therefore, the first device does not display the NFC card reading interface when it is in the second state. In the scenario where the first device remains close to the second device, the false card pop-up caused by receiving the first NFC signal can be accurately suppressed, thereby effectively improving the user experience and reducing power consumption waste.

[0013] In one possible implementation, the second state includes: the first digital key of the first device is connected to the second device, and the motion posture of the first device is a static posture, wherein the short-range communication method and the NFC communication method corresponding to the first digital key are different, and the first digital key is, for example, a Bluetooth key, a UWB key, a star flash key or an infrared key.

[0014] In the above method, the second state includes the first digital key of the first device being connected to the second device. The first device can consider that the control of the second device through the first digital key has been achieved, and it can also be understood that the authentication of the first digital key by the second device (such as card reading) has been completed, so there is no need to perform the NFC card reading process. The second state also includes the movement posture of the first device being a static posture. The first device can consider that the first device remains motionless, which can avoid the scenario where the user uses the first device to perform a "one-time card sticking" operation. Therefore, the NFC card reading interface is not displayed when the first device is in the second state. In the scenario where the first device remains close to the second device, the false card ejection caused by receiving the first NFC signal can be more accurately suppressed, effectively improving the user experience and reducing power consumption waste.

[0015] In one possible implementation, after a first device receives a first NFC signal (e.g., signaling of the contactless card standard ISO14443-3 protocol) sent by a second device (e.g., a door or payment device), when in a first state, the first device can perform an NFC key authentication process with the second device (including the first device sending a second NFC signal to the second device), and the first device can display a first interface (i.e., an NFC card reader interface), the second NFC signal includes information about the first NFC key (e.g., a door key or payment key) of the first device, and the second NFC signal is used by the second device to authenticate the first NFC key. After the first device receives the first NFC signal sent by the second device, when in a second state, the first device will not perform an NFC key authentication process with the second device (i.e., the first device does not send the first device's NFC key information to the second device), and the first device can display a second interface (i.e., not displaying the NFC card reader interface).

[0016] In the above method, after the first device receives the first NFC signal sent by the second device, it will first obtain its own status and determine whether to display the NFC card reader interface and whether to perform the NFC key authentication process based on the obtained status. When the first device is in the second state, the NFC card reader interface will not be displayed, nor will the NFC key authentication process be performed. Instead of displaying the NFC card reader interface and sending the NFC key information as soon as the first NFC signal is received, the situation where the first device frequently pops up the NFC card reader interface and sends the NFC key information multiple times due to receiving the first NFC signal from the second device multiple times can be avoided, thereby effectively reducing unnecessary signal transmission and greatly reducing unnecessary device power consumption.

[0017] In one possible implementation, after the first device receives a first NFC signal (e.g., signaling of the contactless card standard ISO14443-3 protocol) sent by a second device (e.g., a vehicle), the method further includes: the first device receives a third NFC signal (e.g., signaling of the ISO14443-4 protocol) from the second device, the third NFC signal including a first identifier (e.g., an application identifier AID); the first device obtains the status of the first device, and based on the obtained status of the first device and whether the NFC key corresponding to the first identifier is activated (which can also be understood as the NFC key related to the second device), determines whether to display the NFC card reading interface and whether to perform the NFC key authentication process; when the first device is in the first state, and / or the second NFC key corresponding to the first identifier (e.g., a car key) has been activated, the first device can perform the NFC key authentication process with the second device. The process (including the first device sending a fourth NFC signal to the second device) is carried out, and the first device can display the first interface (i.e., the NFC card reader interface). The fourth NFC signal includes information of the third NFC key (e.g., a car key) of the first device. The fourth NFC signal is used by the second device to authenticate the third NFC key. When the first device has activated the second NFC key, the third NFC key is the second NFC key. When the first device has not activated the second NFC key, the third NFC is not the second NFC key (i.e., the third NFC key does not correspond to the first identifier). When the first device is in the second state and the NFC key corresponding to the first identifier is not activated, the first device will not perform the NFC key authentication process with the second device (i.e., the first device does not send the NFC key information of the first device to the second device), and the first device can display the second interface (i.e., the NFC card reader interface is not displayed).

[0018] In the above method, when the first device determines whether to display the NFC card reader interface and whether to perform the NFC key authentication process, it will not only make the judgment based on its own status, but also make the judgment based on whether the first device has activated the NFC key corresponding to the first identifier (provided by the second device) (that is, the NFC key related to the second device). This accurately suppresses the situation where the first device accidentally pops up the card and misauthenticates the NFC when the NFC key related to the second device is not activated, effectively improving the user experience and reducing power consumption waste.

[0019] In a second aspect, the present application provides an electronic device comprising a transceiver (including an NFC module), a processor, and a memory; the memory is used to store a computer program, and the processor calls the computer program so that the electronic device executes the display method provided in the first aspect and any one of the embodiments of the first aspect.

[0020] In a third aspect, the present application provides a computer storage medium storing a computer program. When the computer program is executed by a processor, it is used to execute the display method provided in the first aspect and any one of the embodiments of the first aspect.

[0021] In a fourth aspect, the present application provides a computer program product, which, when executed on a device, enables the device to execute the display method provided in the first aspect and any one of the embodiments of the first aspect.

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

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

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

[0025] FIG1 is a schematic diagram of the architecture of a communication system provided by the present application;

[0026] FIG2 is a schematic diagram of the architecture of another communication system provided by the present application;

[0027] FIG3 is a schematic diagram of the architecture of another communication system provided by the present application;

[0028] FIG4 is a schematic diagram of the hardware structure of an electronic device provided by the present application;

[0029] FIG5 is a schematic diagram of a software architecture of an electronic device provided by the present application;

[0030] FIG6 is a schematic flow chart of a display method provided by the present application;

[0031] FIG7 is a flow chart of another display method provided by the present application;

[0032] FIG8 is a flow chart of another display method provided by the present application;

[0033] FIG9 is a flow chart of another display method provided by the present application. DETAILED DESCRIPTION

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

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

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

[0037] FIG1 is a schematic diagram of the architecture of a communication system 10 provided in an embodiment of the present application.

[0038] As shown in Figure 1, the communication system 10 may include an electronic device 100 and an electronic device 200. The electronic device 100 and the electronic device 200 can communicate with each other via a wired or wireless method. The wired method includes, but is not limited to, a high-definition multimedia interface (HDMI), a universal serial bus (USB), a coaxial cable, an optical fiber, etc., and the wireless method includes, but is not limited to, Bluetooth, wireless fidelity (Wi-Fi), near field communication technology (NFC), ultra wide band (UWB), infrared, short-range wireless communication technology specified by the SparkLink Alliance (for example, SparkLink low energy (SLE), SparkLink basic (SLB)), etc.

[0039] In an embodiment of the present application, both the electronic device 100 and the electronic device 200 include an NFC module, which can implement an NFC communication process. For example, as shown in Figure 1, NFC signals can be transmitted between the electronic device 100 and the electronic device 200. Figure 1 takes the electronic device 100 as a mobile phone and the electronic device 200 as a vehicle as an example. The center console of the electronic device 200 can be integrated with an NFC card reading area. When the electronic device 100 is close to the NFC card reading area of ​​the electronic device 200, the electronic device 200 can send an NFC signal (for example, for waking up the NFC module of the electronic device 100) (which can be simply referred to as a wake-up signal) to the electronic device 100. After receiving the NFC signal, the electronic device 100 can display an NFC card reading interface, such as the user interface 310 shown in Figure 1. The electronic device 200 can also send an NFC signal (which may be referred to as an authentication request signal) to the electronic device 100 for detecting / authenticating the NFC key of the electronic device 100. Accordingly, the electronic device 100 can reply to the electronic device 200 with an NFC signal (which may be referred to as an authentication response signal) including information about the NFC key of the electronic device 100, so that the electronic device 200 can detect / authenticate the NFC key of the electronic device 100. When the authentication is passed, the function of the electronic device 200 can be controlled (such as starting) without a physical key. Among them, the user interface 310 may include a title "Car Key", indicating that the card reading interface of the NFC car key is currently triggered. The user interface 310 may include an icon 311 of the NFC card reading area, an icon 312 of this device, and prompt information 313 (including "Reading card" and "Please keep the phone close to the card").

[0040] FIG2 is a schematic diagram of the architecture of another communication system 10 provided in an embodiment of the present application.

[0041] As shown in FIG2 , the communication system 10 may include an electronic device 100 and an electronic device 200. For details, please refer to the description of the electronic device 100 and the electronic device 200 in FIG1 . The electronic device 100 shown in FIG2 may include a wallet application 101 and an NFC module 102. The electronic device 200 (vehicle) shown in FIG2 may include a center console 201. The center console 201 may include an NFC module 201A. The NFC module 201A corresponds to the NFC card reading area.

[0042] In one implementation, when the NFC card reading areas of the electronic device 100 and the electronic device 200 are close to each other and remain relatively stationary for a long time, for example, as shown in FIG1 , when the user in the driver's seat or the co-pilot seat keeps the electronic device 100 (mobile phone) placed on the center console of the electronic device 200 (vehicle), the electronic device 200 can periodically poll (i.e., periodically send a wake-up signal). Specifically, as shown in Figure 2, the electronic device 200 can periodically send a wake-up signal to the NFC module 102 of the electronic device 100 through the NFC module 201A. Each time the NFC module 102 receives the wake-up signal, it can report it to the wallet application 101 of the electronic device 100. Therefore, the wallet application 101 will frequently pop up and display the NFC card reading interface (for example, the user interface 310 shown in Figure 1). In addition, after sending the wake-up signal, the electronic device 200 can also send an authentication request signal to the NFC module 102 of the electronic device 100 through the NFC module 201A. The wallet application 101 can instruct the NFC module 102 to send an authentication response signal to the NFC module 201A based on the authentication request signal. Therefore, NFC signals related to the NFC key authentication process will also be frequently transmitted between the electronic devices 100 and 200, affecting the user experience and high power consumption. Understandably, when the user keeps the electronic device 100 placed on the electronic device 200, he or she may only want to authenticate the NFC key once, or may not want to authenticate the NFC key at all. For example, the center console of some vehicles integrates an NFC card reading area and a wireless charging area (for example, the NFC card reading area shown in Figure 1 also integrates a wireless charging area). When the user wants to use the electronic device 200 to charge the electronic device 100, the user will keep the electronic device 100 on the center console of the electronic device 200. At this time, the user may not want to authenticate the NFC key. Therefore, the frequent pop-up of the NFC card reading interface on the electronic device 100 will seriously affect the user experience, and the resulting power consumption problem will cause the charging efficiency of the electronic device 100 to be reduced.

[0043] In another implementation, the electronic device 200 has a preset duration after successfully authenticating the NFC key of the electronic device 100, which is generally about 1 or 2 minutes. During the inhibition period, the electronic device 200 will not send a wake-up signal to the electronic device 100. Therefore, during the inhibition period, the electronic device 100 will not pop up the NFC card reader interface, and no NFC signals related to the NFC key authentication process will be transmitted between the electronic devices 100 and 200. However, after the inhibition period ends, the electronic device 200 will send a wake-up signal, causing the electronic device 100 to pop up the NFC card reader interface again. This implementation still cannot effectively solve the technical problems existing in the above implementation. For example, it can only prevent the NFC card reader interface from popping up for a short period of time after the NFC key is authenticated, which can only reduce the frequency of the problem but cannot effectively solve the problems of poor user experience and high power consumption. For example, some electronic devices 100 do not have NFC keys activated and therefore cannot meet the authentication pass conditions to enter the inhibition period. That is, devices that have not activated NFC keys cannot benefit. For example, the manufacturer of the electronic device 200 needs to modify the electronic device 200, which is difficult to implement and has a long consumption cycle, and existing devices cannot benefit.

[0044] The embodiment of the present application provides a display method, which is applied to a communication system 10, and the communication system 10 includes an electronic device 100 and an electronic device 200. When a user brings the NFC card reading areas of the electronic device 100 and the electronic device 200 close to each other and keeps them relatively still, for example, when the electronic device 100 (mobile phone) shown in Figure 1 is placed on the NFC card reading area of ​​the center console of the electronic device 200 (vehicle), the electronic device 200 can send an NFC signal (such as a wake-up signal or an authentication request signal) to the electronic device 100. After the electronic device 100 receives the NFC signal of the electronic device 200, it can judge whether the NFC card reading interface is currently displayed based on the state perception of the electronic device 100, and optionally whether the electronic device 100 has activated the NFC key, and optionally whether to perform the NFC key authentication process. Compared with the above-mentioned short inhibition period, the embodiment of the present application can achieve a "permanent inhibition period" when the judgment result is no, which can avoid the problems of poor user experience and high device power consumption caused by the electronic device 100 repeatedly popping up the NFC card reading interface. Moreover, the capability of the above-mentioned display method is released with the electronic device 100 (for example, with the wallet application of the electronic device 100), and is supported even by the electronic device 100 with lower performance and without the NFC key activated. It does not depend on the modification of the electronic device 200 (such as a vehicle), and thus can cover more electronic devices 100 and electronic devices 200, and has a wider range of application scenarios.

[0045] Among them, the electronic device 100 activates the NFC key, which can also be referred to as the electronic device 100 registering the NFC key or the electronic device 100 including the NFC key, etc. It can be understood that the NFC key can control the corresponding device (one NFC key can correspond to at least one device), for example, the NFC car key 1 controls the start of vehicle 1, the NFC car key 2 controls the start of vehicle 2, the NFC door key 1 controls the opening of gate 1, and the NFC door key 2 controls the opening of gate 2. An NFC key can have an identification information (such as an application identifier (AID)), and different identification information corresponds to different NFC keys. Optionally, the identification information of multiple NFC keys can be the same.

[0046] The NFC card reader interface is the card reader interface of the NFC module of the electronic device 100, which may also be referred to as a verification interface or a usage interface, etc. The NFC key may also be referred to as an NFC card, etc.

[0047] FIG3 is a schematic diagram of the architecture of another communication system 10 provided in an embodiment of the present application.

[0048] As shown in Figure 3, the communication system 10 may include an electronic device 100 and an electronic device 200. For details, please refer to the description of the electronic device 100 and the electronic device 200 in Figure 1. The electronic device 100 shown in Figure 3 may include a wallet application 101, an NFC module 102, a wireless charging module 103, a Bluetooth module 104, a UWB module 105, a gyroscope sensor 106 and an authentication module 107. The electronic device 200 (vehicle) shown in Figure 3 may include a center console 201, a Bluetooth module 202 and a UWB module 203. The center console 201 may include an NFC module 201A (corresponding to the NFC card reading area) and a wireless charging module 201B. Among them:

[0049] The wallet application 101 of the electronic device 100 can be used to manage digital keys such as NFC keys, UWB keys, and Bluetooth keys of the electronic device 100. Any of these digital keys can be used to control other devices such as the electronic device 200. For example, an NFC / UWB / Bluetooth key of a car key can start a vehicle, and an NFC / UWB / Bluetooth key of a door key / access card can open a door. The wallet application 101 can also be used to call the authentication module 107 to determine whether to display an NFC card reader interface (such as the user interface 310 shown in Figure 1), and optionally determine whether to perform an NFC key authentication process.

[0050] The NFC module 102 of the electronic device 100 can be used to transmit NFC signals with the NFC module 201A of the electronic device 200 .

[0051] The wireless charging module 103 of the electronic device 100 can be used to wirelessly charge the wireless charging module 201B of the electronic device 200 (which can be referred to as being in a wireless charging state). In one embodiment, the electronic device 100 can serve as a charged device that receives a charging current, and the electronic device 200 can serve as a charging device that provides a charging current. For example, when the electronic device 100 is placed on the center console 201 of the electronic device 200, the electronic device 200 can send a charging current to the wireless charging module 103 of the electronic device 100 through the wireless charging module 201B, so that the electronic device 200 can charge the electronic device 100. In one embodiment, the wireless charging module 103 can report its own status (e.g., whether it is in a wireless charging state) to the authentication module 107.

[0052] The Bluetooth module 104 of the electronic device 100 can be used to establish a Bluetooth connection with the Bluetooth module 202 of the electronic device 200. For example, when the electronic device 100 activates the Bluetooth key and the electronic device 100 and the electronic device 200 are close to each other, the Bluetooth key of the electronic device 100 can establish a Bluetooth connection with the electronic device 200. Optionally, the first connection can be achieved by manual operation by the user. Alternatively, the Bluetooth key and the electronic device 200 that have established a Bluetooth connection can automatically establish a connection when the electronic device 100 and the electronic device 200 are close to each other. In one embodiment, the Bluetooth module 104 can report its own status (e.g., the connection status of the Bluetooth module 104 and / or the connection status of the Bluetooth key) to the authentication module 107.

[0053] The UWB module 105 of the electronic device 100 can be used to establish a UWB connection with the UWB module of the electronic device 200. For example, when the electronic device 100 activates the UWB key and the electronic devices 100 and 200 are close to each other, the UWB key of the electronic device 100 can establish a UWB connection with the electronic device 200. In one embodiment, the UWB module 105 can report its own status (e.g., the connection status of the UWB module 105 and / or the connection status of the UWB key) to the authentication module 107.

[0054] The gyroscope sensor 106 of the electronic device 100 can be used to determine the motion posture (also referred to as physical posture) of the electronic device 100. In one embodiment, the gyroscope sensor 106 can report detection information to the authentication module 107, so that the authentication module 107 determines the motion posture of the electronic device 100 based on the detection information.

[0055] The electronic device 100 can obtain the relative position of the electronic device 100 and the electronic device 200 through at least one module to determine whether the electronic device and the electronic device 200 remain relatively stationary, for example, by transmitting their respective positions through the Bluetooth module 104 and the electronic device 200 to determine the relative position of the electronic device 100 and the electronic device 200. Not limited to this, the relative position of the electronic device 100 and the electronic device 200 can also be obtained through other communication modules (such as UWB modules, NFC modules, etc.) and other sensors (such as proximity light sensors, gyroscope sensors, position sensors, etc.).

[0056] The authentication module 107 of the electronic device 100 can be used to obtain the status and / or detection information of at least one of the following modules: the wireless charging module 103, the Bluetooth module 104, the UWB module 105, and the gyroscope sensor 106. Based on the obtained status and / or detection information, and optionally whether the NFC key is enabled on the electronic device 100, the authentication module 107 can determine whether the NFC card reader interface is currently displayed, and optionally determine whether NFC key authentication with the electronic device 200 is currently required. The determination result of the authentication module 107 can be reported to the wallet application 101.

[0057] For example, when the NFC card reading areas of the electronic device 100 and the electronic device 200 are close to each other and remain relatively still for a long time, for example, as shown in FIG1 , when the user in the driver's seat or the co-pilot seat keeps the electronic device 100 (mobile phone) placed on the center console of the electronic device 200 (vehicle), the electronic device 200 can periodically poll. Specifically, as shown in FIG3 , the electronic device 200 can periodically send a wake-up signal to the NFC module 102 of the electronic device 100 through the NFC module 201A. Each time the NFC module 102 receives the wake-up signal, it can report it to the wallet application 101 of the electronic device 100. At this time, the wallet application 101 can call the authentication module 107. The authentication module 107 can determine whether the NFC card reading interface is currently displayed based on the status and / or detection information of at least one module obtained, and report the judgment result to the wallet application 101 so that the wallet application 101 displays the corresponding interface according to the judgment result. In addition, after sending the wake-up signal, the electronic device 200 can also send an authentication request signal to the NFC module 102 of the electronic device 100 through the NFC module 201A. The NFC module 102 will report the received authentication request signal to the wallet application 101. At this time, the wallet application 101 can call the authentication module 107. The authentication module 107 can determine whether it is currently necessary to authenticate the NFC key with the electronic device 200 and whether to display the NFC card reading interface based on the status and / or detection information of at least one module obtained, and whether the electronic device 100 has activated the NFC key, and report the judgment result to the wallet application 101 so that the wallet application 101 performs corresponding operations based on the judgment result. When the authentication module 107 determines to authenticate the NFC key with the electronic device 200, the wallet application 101 can instruct the NFC module 102 to send an authentication response signal to the NFC module 201A, so that the electronic device 200 authenticates the NFC key of the electronic device 100 according to the authentication response signal.

[0058] Understandably, if the NFC card reading areas of electronic devices 100 and 200 are close to each other and remain relatively still for an extended period of time, even if electronic device 200 is still periodically polling, electronic device 100 will independently determine whether to display the NFC card reading interface based on state perception. Therefore, the NFC card reading interface will not repeatedly pop up at the frequency of electronic device 200's polling, effectively improving the user experience. Furthermore, electronic device 100 can make accurate judgments based on the status and / or detection information of multiple modules, avoiding impacting the user experience of the NFC key in other scenarios and significantly improving the usability of the NFC key.

[0059] FIG3 illustrates an example in which the electronic device 100 and the electronic device 200 include a Bluetooth module and a UWB module. In a specific implementation, the electronic device 100 and / or the electronic device 200 may not include these communication modules. The electronic device 100 and / or the electronic device 200 may also include communication modules of other communication technologies, such as a star flash communication module, an infrared communication module, etc. The embodiment of the present application does not limit the number and type of communication modules included in the electronic device 100 and the electronic device 200. Accordingly, the electronic device 100 may also include a star flash key, an infrared key, etc. The embodiment of the present application does not limit the number and type of digital keys included in the electronic device 100.

[0060] Figure 3 illustrates an example in which the electronic device 100 includes a gyroscope sensor 106, and the motion posture of the electronic device 100 is determined by the detection information of the gyroscope sensor 106. In a specific implementation, other sensors may also be included, and the motion posture of the electronic device 100 may be determined by the detection information of other sensors, or the motion posture of the electronic device 100 may also be determined by an image captured by a camera. The embodiment of the present application does not limit the module in the electronic device 100 for determining the motion posture of the electronic device 100.

[0061] FIG3 illustrates an example in which the electronic device 100 and the electronic device 200 include a wireless charging module. In a specific implementation, the electronic device 100 and / or the electronic device 200 may also not include a wireless charging module.

[0062] Figure 3 takes the electronic device 200 as a vehicle, and the NFC module 201A and the wireless charging module 201B are integrated into the center console 201 as an example. In a specific implementation, the NFC module 201A and the wireless charging module 201B may also be integrated into other modules of the vehicle, or the electronic device 200 may also be in other forms. In this case, the NFC module 201A and the wireless charging module 201B may be integrated into the modules of the corresponding form of the electronic device 200, or the NFC module 201A and the wireless charging module 201B may not be integrated together. This embodiment of the present application is not limited to this.

[0063] The forms of the electronic device 100 and the electronic device 200 shown in Figures 1 to 3 are for example only. In specific implementations, they may also be in other forms. For specific examples, please refer to the description of the electronic device 100 and the electronic device 200 below. The embodiments of the present application are not limited to this.

[0064] Next, the electronic device 100 and the electronic device 200 involved in the embodiments of the present application are exemplarily introduced.

[0065] In the present application, the electronic device 100 / electronic device 200 can be a mobile phone, a tablet computer, a handheld computer, a desktop computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), as well as smart home devices such as smart TVs and smart cameras, wearable devices such as smart bracelets, smart watches, and smart glasses, extended reality (XR) devices such as augmented reality (AR), virtual reality (VR), and mixed reality (MR), vehicles, vehicle-mounted devices, or smart city devices. The embodiments of the present application do not impose any special restrictions on the specific types of electronic devices.

[0066] It is understood that the structures illustrated in the embodiments of the present application do not constitute specific limitations on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0067] FIG4 is a schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of the present application.

[0068] As shown in Figure 4, the electronic device 100 may include a processor 110, an external memory interface 120, 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 receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

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

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

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

[0072] The charging management module 140 is used to receive charging input from the charger. The charger can be a wireless charger or a wired charger. In some wired charging implementations, the charging management module 140 can receive charging input from the wired charger through the USB interface 130. In some wireless charging implementations, the charging management module 140 can receive wireless charging input through the wireless charging coil of the electronic device 100, such as receiving wireless charging input from the electronic device 200. While the charging management module 140 charges the battery 142, it can also power the electronic device 100 through the power management module 141. In one implementation, the charging management module 140 can report to the processor 110 whether the electronic device 100 is in a wireless charging state, so that the processor 110 can determine whether to display the NFC card reader interface.

[0073] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In another embodiment, the power management module 141 can also be set in the processor 110. In another embodiment, the power management module 141 and the charging management module 140 can also be set in the same device.

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

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

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

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

[0078] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), UWB, star flash, etc., which are applied to the electronic device 100. 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 the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

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

[0080] In one embodiment, the wireless communication module 160 can report the status of the wireless communication connection between the electronic device 100 and the electronic device 200 to the processor 110, for example, whether the electronic device 100 and the electronic device 200 have established a wireless communication connection, the type of wireless communication connection established (such as Bluetooth, UWB, Star Flash), whether the digital key and the electronic device 200 have established a connection when the electronic device 100 has activated the digital key for wireless communication, etc., so that the processor 110 can determine whether to display the NFC card reading interface.

[0081] Electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

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

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

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

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

[0086] In one embodiment, the camera 193 can send the captured image to the processor 110, and the processor 110 can obtain the relative position of the electronic device 100 and the electronic device 200, the relative motion state of the electronic device 100 and the electronic device 200, the motion posture of the electronic device 100 and other states of the electronic device 100 based on the captured image, and determine whether to display the NFC card reading interface based on the acquired state.

[0087] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0088] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the internal memory 121 and / or instructions stored in a memory provided in the processor.

[0089] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

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

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

[0092] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the user can place the receiver 170B close to the ear to hear the voice.

[0093] Microphone 170C, also known as a "microphone" or "speaker," converts sound signals into electrical signals. When making a call or sending a voice message, a user can place their mouth close to microphone 170C and speak, inputting the sound signal into microphone 170C. Electronic device 100 may be equipped with at least one microphone 170C.

[0094] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. 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 location of the touch based on the detection signal from pressure sensor 180A.

[0095] The gyroscope sensor 180B can be used to determine the motion posture of the electronic device 100. In one embodiment, the angular velocity of the electronic device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyroscope sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the electronic device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyroscope sensor 180B can also be used for navigation and somatosensory game scenes.

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

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

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

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

[0100] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 can use the proximity light sensor 180G to detect the relative position and relative motion state of the electronic device 100 and the electronic device 200.

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

[0102] The fingerprint sensor 180H is used to collect fingerprints.

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

[0104] The touch sensor 180K is also called a "touch-sensitive device." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In another embodiment, the touch sensor 180K can also be disposed on the surface of the electronic device 100, in a location different from that of the display screen 194.

[0105] The bone conduction sensor 180M can acquire vibration signals.

[0106] In one embodiment, the gyroscope sensor 180B and / or the acceleration sensor 180E can report detection information to the processor 110 so that the processor 110 can obtain the motion posture of the electronic device 100 and the relative motion state of the electronic device 100 and the electronic device 200, so as to be used by the processor 110 to determine whether to display the NFC card reading interface.

[0107] The buttons 190 include a power button, a volume button, and the like. The buttons 190 may be mechanical buttons or touch buttons. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100.

[0108] Motor 191 can generate vibration prompts.

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

[0110] The SIM card interface 195 is used to connect a SIM card.

[0111] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a microservice architecture, or a cloud architecture. For example, the software system with a layered architecture can be an Android system, a Harmony operating system (OS), or other software systems. The embodiment of the present application takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100.

[0112] FIG5 is a schematic diagram of a software architecture of an electronic device 100 provided in an embodiment of the present application.

[0113] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In one embodiment, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0114] The application layer can include a series of application packages.

[0115] As shown in Figure 5, the application package may include wallet, camera, music, settings, calls, navigation, Bluetooth, video, short messages, browser and other applications. The applications in this application can also be replaced by other software such as mini-programs and atomic services. The wallet application in the embodiment of this application can be used to manage at least one NFC key. Different NFC keys can be used to control different devices. Different NFC keys can also be used to control different functions of the same device. The embodiment of this application does not limit the functions of the NFC key. Not limited to this, the wallet application can also be used to manage digital keys such as Bluetooth keys, UWB keys, and Star Flash keys. Not limited to this, NFC keys can also be managed through other applications, such as the settings application.

[0116] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0117] As shown in FIG5 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, an authentication module, and the like.

[0118] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0119] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0120] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0121] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

[0122] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0123] The notification manager enables applications to display notification information in the status bar. This can be used to convey notification-type messages and can disappear automatically after a short period of time without user interaction. For example, the notification manager is used to notify the completion of downloads, message reminders, etc. The notification manager can also be used to display notifications in the form of icons or scrolling text in the top status bar of the system, such as notifications from applications running in the background, or notifications that appear on the screen in the form of dialog windows. For example, a text message can be displayed in the status bar, a notification sound can be emitted, the electronic device 100 can vibrate, an indicator light can flash, etc.

[0124] The authentication module is used to obtain the status of the electronic device 100, optionally whether the electronic device 100 has activated the NFC key, and determine whether to display the NFC card reader interface, and optionally determine whether to perform the NFC key authentication process with the electronic device 200.

[0125] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0126] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0127] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0128] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (e.g., OpenGL ES), and a 2D graphics engine (e.g., SGL).

[0129] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0130] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0131] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0132] A 2D graphics engine is a drawing engine for 2D drawings.

[0133] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0134] The following describes the workflow of the software and hardware of the electronic device 100 in conjunction with the NFC card reading scenario.

[0135] When the wireless communication module 160 receives a wake-up signal sent by the electronic device 200, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the wake-up signal into a raw input event (including the specific content of the wake-up signal, the timestamp of receiving the wake-up signal, and other information). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer and identifies the application corresponding to the input event (assuming it is a wallet application). The wallet application then calls the interface of the application framework layer, controls the display driver by calling the kernel layer, and displays the NFC card reading interface on the display screen 194.

[0136] Based on the above embodiments, the display method provided by the embodiments of the present application is described. The method can be applied to the communication system 10 shown in Figure 1. The method can be applied to the communication system 10 shown in Figure 3. The method can be applied to the electronic device 100 shown in Figure 4. The method can be applied to the electronic device 100 shown in Figure 5.

[0137] The following embodiments are illustrated by taking the gyroscope sensor 106 as an example to detect the physical posture of the electronic device 100. The following embodiments are illustrated by taking the electronic device 100 as an example to include a Bluetooth module / UWB module and to establish a Bluetooth / UWB connection with other devices (such as the electronic device 200).

[0138] FIG6 is a flow chart of a display method provided by an embodiment of the present application. The method may include but is not limited to the following steps:

[0139] S101: When the user brings the electronic device 100 and the electronic device 200 close to each other, the electronic device 100 and the electronic device 200 may establish a Bluetooth / UWB connection. Optionally, the Bluetooth module 104 / UWB module 105 of the electronic device 100 and the Bluetooth module 202 / UWB module 203 of the electronic device 200 establish a Bluetooth / UWB connection.

[0140] In one embodiment, S101 is an optional step. In one embodiment, if the electronic device 100 has activated the Bluetooth / UWB key corresponding to the electronic device 200, if the user brings the electronic device 100 and the electronic device 200 close together, the electronic device 100 can establish a Bluetooth / UWB connection with the electronic device 200 through the Bluetooth / UWB key.

[0141] S102: When the user places the electronic device 100 on the NFC card reading area of ​​the electronic device 200, the NFC module 201A of the electronic device 200 may be enabled to transmit NFC signals.

[0142] S103 : The NFC module 201A of the electronic device 200 sends an NFC signal 1 to the NFC module 102 of the electronic device 100 .

[0143] In one embodiment, the NFC signal 1 may be signaling of the contactless card standard ISO / IEC 14443-3 protocol. In some examples, the NFC signal 1 is a request signal (request A, REQA) or a wakeup signal (wakeup A, WUPA). The NFC signal 1 may be used to request the NFC card type of the electronic device 100. The NFC card type is distinguished by the way the NFC card (the electronic device 100 in the embodiment of the present application) sends a signal to the card reader (the electronic device 100 in the embodiment of the present application), and may be divided into type A (type A) and type B (type B). A type A card may send a signal via a 13.65 megahertz (MHz) carrier, with Miller coding and 100% amplitude shift keying (ASK) as the encoding method. A type B card may send a signal via a 13.65 MHz carrier, with non-return to zero (NRA) as the encoding method and 10% ASK as the carrier amplitude modulation method. Not limited to the above examples, in a specific implementation, there may be other NFC card types, such as a felica type, which may also be referred to as type F.

[0144] In one embodiment, the NFC module 102 of the electronic device 100 may wake up after receiving the NFC signal 1 to transmit the NFC signal.

[0145] S104 : In response to the NFC signal 1 , the NFC module 102 of the electronic device 100 sends an NFC signal 2 to the NFC module 201A of the electronic device 200 .

[0146] In one embodiment, the NFC signal 2 may include that the NFC key of the electronic device 100 is a virtual key or a physical key. The electronic device 100 in the embodiment of the present application is, for example, a mobile terminal such as a mobile phone or a wearable device. Therefore, the NFC key included in the electronic device 100 is a virtual key. However, this is not limited to this. In another embodiment, the electronic device 100 may also include a physical NFC key, or the electronic device 100 is a physical NFC key.

[0147] In one implementation, the NFC signal 2 may be signaling of the ISO / IEC 14443-3 protocol. In some examples, the NFC signal 2 is an answer to request A (ATQA) signal of the NFC signal 1 .

[0148] S105: After receiving the NFC signal 1, the NFC module 102 of the electronic device 100 sends a corresponding notification to the wallet application 101. For example, the NFC module 102 may broadcast a notification of receiving the NFC signal 1 to the application of the electronic device 100.

[0149] S106 : The wallet application 101 of the electronic device 100 obtains the connection status of the electronic device 100 from the Bluetooth module 104 / UWB module 105 .

[0150] In one embodiment, the connection status of the electronic device 100 may include whether a Bluetooth / UWB connection is established with the electronic device 200. Optionally, when the electronic device 100 has activated the Bluetooth / UWB key corresponding to the electronic device 200, the connection status of the electronic device 100 may include whether a Bluetooth / UWB connection is established with the electronic device 200 via the Bluetooth / UWB key corresponding to the electronic device 200. It is understandable that since short-range communication connections such as Bluetooth / UWB connections can only be successfully established when the distance between the electronic device 100 and the electronic device 200 is relatively close, the establishment of a Bluetooth / UWB connection between the electronic device 100 and the electronic device 200 indicates that the electronic device 100 is near the electronic device 200.

[0151] S107 : The wallet application 101 of the electronic device 100 obtains the motion posture of the electronic device 100 from the gyro sensor 106 .

[0152] In one embodiment, when it is obtained in S106 that the electronic device 100 has established a Bluetooth / UWB connection with the electronic device 200, the wallet application 101 can further obtain the motion posture of the electronic device 100 (i.e., execute S107) to determine whether the electronic device 100 is in a static posture. It can be understood that NFC is a short-range communication method. In order for the electronic device 100 and the electronic device 200 to transmit NFC signals, the distance between the two devices needs to be relatively close. When the connection status of the electronic device 100 is that the Bluetooth / UWB connection has been established with the electronic device 200, it indicates that the electronic device 100 is near the electronic device 200 and meets the basic conditions for transmitting NFC signals. In this case, executing S107 again can avoid the power consumption waste caused by meaninglessly executing other judgments (S107) when the electronic device 100 and the electronic device 200 are far apart.

[0153] S108: The wallet application 101 of the electronic device 100 determines whether to display the NFC card reading interface according to the motion posture and connection status of the electronic device 100.

[0154] S109: When the electronic device 100 is in a stationary position and has established a Bluetooth / UWB connection with the electronic device 200, the wallet application 101 of the electronic device 100 does not display the NFC card reading interface, otherwise it displays the NFC card reading interface.

[0155] In one embodiment, when the electronic device 100 is in a stationary posture and a Bluetooth / UWB connection is established with the electronic device 200 (which can be considered to be in a specific scenario), the electronic device 100 may not display the NFC card reader interface, for example, keeping the original display interface unchanged. The above-mentioned specific scenario can exclude the scenario where the user uses the NFC key, for example, exclude the scenario where the user uses other digital keys at a distance from the electronic device 200 (in this scenario, it is impossible to establish a connection with the electronic device 200 using a near-field communication method such as Bluetooth / UWB), and for example, exclude the scenario where the user uses an NFC bus card for "one-time card authentication" such as boarding a bus near the electronic device 200 (in this scenario, the electronic device 100 will not be in a stationary posture). Therefore, the mis-popping of the card in the specific scenario of receiving the NFC signal 1 can be accurately suppressed.

[0156] In another embodiment, when the electronic device 100 is not in a static posture (i.e., in motion), and / or no Bluetooth / UWB connection is established with the electronic device 200, it can be considered that it is not in the above-mentioned specific scenario, and the user may use the NFC key. In this case, the electronic device 100 can display the NFC card reader interface, so as to avoid affecting the normal card usage experience of digital keys such as access control. In some examples, when the electronic device 100 displays the NFC card reader interface, the NFC key of the electronic device 100 can be displayed in the NFC card reader interface. It can be understood that the electronic device 100 sets the NFC key on the top layer of multiple cards / multiple digital keys, and the electronic device 100 can set the displayed NFC key information to an accessible / readable state for other devices to read and authenticate the NFC key.

[0157] S110 : The NFC module 201A of the electronic device 200 determines to initiate authentication of the NFC key according to the NFC signal 2 .

[0158] In one embodiment, after receiving the NFC signal 2 in response to the NFC signal 1 , the NFC module 201A determines to initiate authentication of the NFC key, and thus executes S111 .

[0159] In one embodiment, when the NFC signal 2 includes an indication that the NFC key of the electronic device 100 is a virtual key, the NFC module 201A determines to initiate authentication of the NFC key, and thus executes S111 .

[0160] S111 : The NFC module 201A of the electronic device 200 sends an NFC signal 3 (including AID1 ) to the NFC module 102 of the electronic device 100 .

[0161] In one embodiment, the NFC signal 3 may be a signaling of the ISO / IEC 14443-4 protocol, used to request detection / authentication of the NFC key of the electronic device 100 .

[0162] In one embodiment, AID1 is the identifier of the NFC key corresponding to the electronic device 200. The electronic device 200 can send an NFC signal 3 including AID1 to the electronic device 100 to request detection / authentication of the NFC key corresponding to AID1 in the electronic device 100.

[0163] S112 : After receiving the NFC signal 3 , the NFC module 102 of the electronic device 100 sends a corresponding notification to the wallet application 101 . For example, the NFC module 102 may broadcast a notification of receiving the NFC signal 3 to the application of the electronic device 100 .

[0164] S113 : The wallet application 101 of the electronic device 100 obtains the connection status of the electronic device 100 from the Bluetooth module 104 / UWB module 105 .

[0165] S114 : The wallet application 101 of the electronic device 100 obtains the motion posture of the electronic device 100 from the gyro sensor 106 .

[0166] The description of S113 and S114 can refer to the description of S106 and S107 above. The difference is that S106 and S107 are executed after the wallet application 101 receives the notification of NFC signal 1 entering the field, and S113 and S114 are executed after the wallet application 101 receives the notification of NFC signal 3 entering the field.

[0167] S115: The wallet application 101 of the electronic device 100 determines whether to display the NFC card reading interface and whether to perform the NFC key authentication process based on the movement posture, connection status, and whether the NFC key corresponding to AID1 of the electronic device 100 is activated (the judgment results can be seen in the following cases A and B).

[0168] S116: In situation A, when the electronic device 100 is in a stationary position, a Bluetooth / UWB connection is established with the electronic device 200, and the NFC key corresponding to AID1 is not activated, the wallet application 101 of the electronic device 100 does not display the NFC card reading interface and does not perform the NFC key authentication process.

[0169] In one embodiment, when the electronic device 100 is in a stationary posture and has established a Bluetooth / UWB connection with the electronic device 200, it can be considered to be in a specific scenario. The specific scenario can exclude the scenario where the user uses the NFC key. In the specific scenario, if the electronic device 100 has not activated the NFC key corresponding to AID1, the electronic device 100 may not display the NFC card reading interface, for example, keep the original display interface unchanged, and do not perform the NFC key authentication process with the electronic device 200, for example, do not execute S117 and S118 of the following situation B.

[0170] S117: In situation B, when the electronic device 100 satisfies at least one of the following conditions: not in a stationary position, not establishing a Bluetooth / UWB connection with the electronic device 200, and the NFC key corresponding to AID1 has been activated, the wallet application 101 of the electronic device 100 sends an NFC signal 4 to the NFC module 201A of the electronic device 200 through the NFC module 102.

[0171] In one embodiment, when the electronic device 100 satisfies at least one of the following conditions: it is not in a static posture (i.e., it is in motion), it has not established a Bluetooth / UWB connection with the electronic device 200, and the NFC key corresponding to AID1 (which may be referred to as NFC key 1) has been activated, it can be considered that it is not in a specific scenario and / or there is an NFC key 1 corresponding to the electronic device 200, and the user has the possibility of using the NFC key, then the electronic device 100 can perform the authentication process of the NFC key 1. In some examples, when the electronic device 100 has activated the NFC key 1 corresponding to AID1, the electronic device 100 can respond to the NFC signal 3 (including AID1) and send an NFC signal 4 to the electronic device 200, and the NFC signal 4 includes information about the NFC key 1 corresponding to AID1. In other examples, when the electronic device 100 has not activated the NFC key corresponding to AID1, the electronic device 100 may also send information about other NFC keys in the NFC signal 4. In other examples, when the electronic device 100 has not activated the NFC key corresponding to AID1, the electronic device 100 may not send the NFC key information in the NFC signal 4, for example, the NFC signal 4 indicates that the NFC key corresponding to AID1 has not been activated.

[0172] S118 : The NFC module 201A of the electronic device 200 authenticates the NFC key based on the NFC signal 4 .

[0173] S118 is an optional step. In one embodiment, when the NFC signal 4 includes information of an NFC key (e.g., NFC key 1), the NFC module 201A of the electronic device 200 can authenticate the NFC key according to the information of the NFC key after receiving the NFC signal 4. When the authentication is successful, the electronic device 100 can control the electronic device 200, such as starting the electronic device 200.

[0174] S119: In case B, when the electronic device 100 satisfies at least one of the following conditions: not in a static posture, not establishing a Bluetooth / UWB connection with the electronic device 200, and the NFC key corresponding to AID1 has been activated, the wallet application 101 of the electronic device 100 can display the NFC card reading interface.

[0175] In one embodiment, in situation B, it can be considered that the electronic device 100 is not in a specific scenario and / or there is an NFC key 1 corresponding to the electronic device 200, and the user may use the NFC key, then the electronic device 100 can display the NFC card reader interface. For instructions on how the electronic device 100 displays the NFC card reader interface, please refer to the instructions for displaying the NFC card reader interface in S109 above, wherein the NFC key displayed by the electronic device 100 on the NFC card reader interface may be the NFC key indicated by the NFC signal 4. For example, if the electronic device 100 has activated the NFC key 1 corresponding to AID1, the NFC key 1 can be displayed on the NFC card reader interface, and the electronic device 100 can set the information of the NFC key 1 to a readable state for other devices to read and authenticate the NFC key 1 (such as the instructions in S117 and S118).

[0176] FIG7 is a flow chart of another display method provided in an embodiment of the present application. The method may include but is not limited to the following steps:

[0177] S201: When the user places the electronic device 100 on the NFC card reading area of ​​the electronic device 200, the NFC module 201A of the electronic device 200 may be enabled to transmit NFC signals.

[0178] S202 : The NFC module 201A of the electronic device 200 sends an NFC signal 1 to the NFC module 102 of the electronic device 100 .

[0179] S203 : In response to the NFC signal 1 , the NFC module 102 of the electronic device 100 sends an NFC signal 2 to the NFC module 201A of the electronic device 200 .

[0180] S204 : After receiving the NFC signal 1 , the NFC module 102 of the electronic device 100 sends a corresponding notification to the wallet application 101 . For example, the NFC module 102 may broadcast a notification of receiving the NFC signal 1 to the application of the electronic device 100 .

[0181] S202-S204 are similar to S103-S105 in FIG6 , and for details, please refer to the description of S103-S105 in FIG6 .

[0182] S205 : The wallet application 101 of the electronic device 100 obtains from the wireless charging module 103 whether the electronic device 100 is in a wireless charging state.

[0183] In one embodiment, the wallet application 101 can specifically obtain whether the electronic device 100 is in the following wireless charging state: the electronic device 100 is a charged device receiving a charging current, and the electronic device 200 is a charging device providing a charging current, that is, the electronic device 200 is in a state of charging the electronic device 100.

[0184] S206: The wallet application 101 of the electronic device 100 determines whether to display the NFC card reading interface according to whether the electronic device 100 is in a wireless charging state.

[0185] S207: When the electronic device 100 is in the wireless charging state, the wallet application 101 of the electronic device 100 does not display the NFC card reading interface, otherwise it displays the NFC card reading interface.

[0186] In one embodiment, when the electronic device 100 is in a wireless charging state (for example, the wireless charging state described in S205), it can be considered to be in a specific scenario. The specific scenario can exclude scenarios where the user uses other keys, for example, scenarios where the user uses digital keys such as access cards and bus cards, and for example, scenarios where the user uses other digital keys at a distance from the electronic device 200 (in this scenario, the electronic device 200 cannot charge the electronic device 100). Therefore, the mis-ejection of the card in a specific scenario where the NFC signal 1 is received can be accurately suppressed.

[0187] In another embodiment, when the electronic device 100 is not in a wireless charging state (for example, the wireless charging state described in S205), it can be considered that it is not in the above-mentioned specific scenario, and the user may use the NFC key. The electronic device 100 can display the NFC card reading interface, so as to avoid affecting the normal card usage experience of digital keys such as access control.

[0188] S208 : The NFC module 201A of the electronic device 200 determines to initiate authentication of the NFC key according to the NFC signal 2 .

[0189] S209 : The NFC module 201A of the electronic device 200 sends an NFC signal 3 (including AID1 ) to the NFC module 102 of the electronic device 100 .

[0190] S210 : After receiving the NFC signal 3 , the NFC module 102 of the electronic device 100 sends a corresponding notification to the wallet application 101 . For example, the NFC module 102 may broadcast a notification of receiving the NFC signal 3 to the application of the electronic device 100 .

[0191] S208 - S210 are similar to S110 - S112 in FIG. 6 , and for details, please refer to the description of S110 - S112 .

[0192] S211 : The wallet application 101 of the electronic device 100 obtains from the wireless charging module 103 whether the electronic device 100 is in a wireless charging state.

[0193] The description of S211 can refer to the description of S205 above, the difference is that S205 is executed after the wallet application 101 receives the notification of NFC signal 1 entering the field, and S211 is executed after the wallet application 101 receives the notification of NFC signal 3 entering the field.

[0194] S212: The wallet application 101 of the electronic device 100 determines whether to display the NFC card reading interface and whether to perform the NFC key authentication process based on whether the electronic device 100 is in the wireless charging state and whether the NFC key corresponding to AID1 is activated (the judgment results can be seen in the following cases A and B).

[0195] S213: In case A, when the electronic device 100 is in wireless charging state and the NFC key corresponding to AID1 is not activated, the wallet application 101 of the electronic device 100 does not display the NFC card reading interface and does not perform the NFC key authentication process.

[0196] In one embodiment, when the electronic device 100 is in a wireless charging state, it can be considered to be in a specific scenario, which can exclude scenarios where the user uses other keys. In the specific scenario, if the electronic device 100 has not activated the NFC key corresponding to AID1, the electronic device 100 may not display the NFC card reading interface, for example, keep the original display interface unchanged, and do not perform the NFC key authentication process with the electronic device 200, for example, do not execute S214 and S215 of the following situation B.

[0197] S214: In situation B, when the electronic device 100 is not in a wireless charging state and / or the NFC key corresponding to AID1 has been activated, the wallet application 101 of the electronic device 100 sends an NFC signal 4 to the NFC module 201A of the electronic device 200 through the NFC module 102.

[0198] In one embodiment, when the electronic device 100 is not in a wireless charging state and / or the NFC key corresponding to AID1 (referred to as NFC key 1) has been activated, it can be considered that it is not in a specific scenario and / or the NFC key 1 corresponding to the electronic device 200 is present, and the user may use the NFC key. In this case, the electronic device 100 can perform the authentication process of the NFC key 1. For a specific example, see the example of S117 in Figure 6.

[0199] S215 : The NFC module 201A of the electronic device 200 authenticates the NFC key according to the NFC signal 4 .

[0200] S215 is similar to S118 in FIG6 , and for details, please refer to the description of S118 in FIG6 .

[0201] S216: In case B, when the electronic device 100 is not in a wireless charging state and / or the NFC key corresponding to AID1 has been activated, the wallet application 101 of the electronic device 100 may display an NFC card reading interface.

[0202] S216 is similar to S119 in FIG. 6 , and for details, please refer to the description of S119 in FIG. 6 .

[0203] Without being limited to the embodiments shown in Figures 6 and 7, in other embodiments, the electronic device 200 may not send the NFC signal 3. In this case, the NFC signal 1 can be used to initiate NFC key authentication. A specific process example can be seen in Figure 8. Figure 8 illustrates an example in which the electronic device 100 determines whether to display the NFC card reader interface (corresponding to Figure 6) based on the motion posture and connection status of the electronic device 100. The electronic device 100 can also determine whether to display the NFC card reader interface (corresponding to Figure 7) based on whether it is in a wireless charging state. In this case, the process is similar to that of Figure 8 and will not be repeated here.

[0204] FIG8 is a flow chart of another display method provided in an embodiment of the present application. The method may include but is not limited to the following steps:

[0205] S301: When the user brings the electronic device 100 and the electronic device 200 close to each other, the electronic device 100 and the electronic device 200 may establish a Bluetooth / UWB connection. Optionally, the Bluetooth module 104 / UWB module 105 of the electronic device 100 and the Bluetooth module 202 / UWB module 203 of the electronic device 200 establish a Bluetooth / UWB connection.

[0206] In one embodiment, S301 is an optional step. S301 is similar to S101 in FIG6 , and for details, please refer to the description of S101 in FIG6 .

[0207] S302: When the user places the electronic device 100 on the NFC card reading area of ​​the electronic device 200, the NFC module 201A of the electronic device 200 may be enabled to transmit NFC signals.

[0208] S303 : The NFC module 201A of the electronic device 200 sends an NFC signal 5 to the NFC module 102 of the electronic device 100 .

[0209] S303 is similar to S103 in FIG. 6 , and for details, please refer to the description of S103 in FIG. 6 , wherein the NFC signal 5 in S303 corresponds to the NFC signal 1 in S103 .

[0210] S304 : The NFC module 102 of the electronic device 100 sends an NFC signal 6 to the NFC module 201A of the electronic device 200 in response to the NFC signal 5 .

[0211] S304 is similar to S104 in FIG. 6 , and for details, please refer to the description of S104 in FIG. 6 , wherein the NFC signal 6 in S304 corresponds to the NFC signal 2 in S104 .

[0212] S305 : After receiving the NFC signal 5 , the NFC module 102 of the electronic device 100 sends a corresponding notification to the wallet application 101 . For example, the NFC module 102 may broadcast a notification of receiving the NFC signal 5 to the application of the electronic device 100 .

[0213] S306 : The wallet application 101 of the electronic device 100 obtains the connection status of the electronic device 100 from the Bluetooth module 104 / UWB module 105 .

[0214] S307 : The wallet application 101 of the electronic device 100 obtains the motion posture of the electronic device 100 from the gyro sensor 106 .

[0215] S306-S307 are similar to S106-S107 in FIG6 , and for details, please refer to the description of S106-S107 in FIG6 .

[0216] S308: The wallet application 101 of the electronic device 100 determines whether to display the NFC card reading interface and whether to perform the NFC key authentication process based on the motion posture and connection status of the electronic device 100 (the judgment results can be seen in the following cases A and B).

[0217] S309: In case A, when the electronic device 100 is in a stationary position and has established a Bluetooth / UWB connection with the electronic device 200, the wallet application 101 of the electronic device 100 does not display the NFC card reading interface and does not perform the NFC key authentication process.

[0218] In one embodiment, when the electronic device 100 is in a stationary posture and has established a Bluetooth / UWB connection with the electronic device 200, it can be considered to be in a specific scenario, which can exclude the scenario where the user uses the NFC key. The electronic device 100 may not display the NFC card reader interface, for example, keep the original display interface unchanged, and not perform the NFC key authentication process with the electronic device 200, for example, not execute S310 and S311 of the following situation B.

[0219] S310: In situation B, when the electronic device 100 is not in a stationary posture and / or no Bluetooth / UWB connection is established with the electronic device 200, the wallet application 101 of the electronic device 100 sends an NFC signal 7 to the NFC module 201A of the electronic device 200 through the NFC module 102.

[0220] In one embodiment, when the electronic device 100 is not in a stationary state (i.e., in motion) and / or has not established a Bluetooth / UWB connection with the electronic device 200, it can be considered that it is not in a specific scenario and the user may use an NFC key, then the electronic device 100 can perform an NFC key authentication process. In some examples, the electronic device 100 can send an NFC signal 7 including NFC key information to the electronic device 200, wherein, in one case, the NFC key can be requested by the electronic device 200, for example, the NFC signal 5 includes an identifier of the NFC key (such as an AID) for the electronic device 100 to determine the NFC key and send the NFC key information to the electronic device 200. In another case, the NFC key can also be automatically identified by the electronic device 100, for example, the electronic device 100 obtains the NFC key based on the type of the electronic device 200. In other examples, when the electronic device 100 has not activated or has not obtained the NFC key corresponding to the electronic device 200, the electronic device 100 may not send the NFC key information in the NFC signal 7, for example, the NFC signal 7 indicates that the NFC key is not activated / has not been obtained.

[0221] S311 : The NFC module 201A of the electronic device 200 authenticates the NFC key based on the NFC signal 7 .

[0222] S311 is an optional step. S311 is similar to S118 in FIG6 , and for details, please refer to the description of S118 in FIG6 , wherein the NFC signal 7 in S311 corresponds to the NFC signal 4 in S118 .

[0223] S312: In case B, when the electronic device 100 is not in a static posture and / or no Bluetooth / UWB connection is established with the electronic device 200, the wallet application 101 of the electronic device 100 may display an NFC card reading interface.

[0224] In one embodiment, when the electronic device 100 is not in a stationary state (i.e., in motion) and / or has not established a Bluetooth / UWB connection with the electronic device 200, it can be considered that it is not in the above-mentioned specific scenario, and the user may use the NFC key, then the electronic device 100 can display the NFC card reader interface. For an explanation of the electronic device 100 displaying the NFC card reader interface, please refer to the explanation of displaying the NFC card reader interface in S109 of Figure 6, wherein the NFC key displayed by the electronic device 100 on the NFC card reader interface may be the NFC key indicated by the NFC signal 7.

[0225] 6 and 7 are car keys, and the electronic device 200 is a vehicle. The NFC key shown in FIG8 is a door key or a payment key (eg, an electronic bank card, an electronic bus card, etc.).

[0226] FIG9 is a flow chart of another display method provided by an embodiment of the present application. The method may include but is not limited to the following steps:

[0227] S401: A first device (ie, the electronic device 100 ) receives a first NFC signal sent by a second device (ie, the electronic device 200 ).

[0228] In one embodiment, the first NFC signal is NFC signal 1 in Figure 6 or Figure 7. In another embodiment, the first NFC signal is NFC signal 5 in Figure 8. For example, the first NFC signal is used to wake up the NFC module of the first device.

[0229] S402: The first device obtains the status of the first device.

[0230] In one embodiment, the first device can detect its own status by itself, for example, through a sensor module, camera, communication module, etc. of the first device. In another embodiment, the first device can also obtain the status of the first device from other devices (such as devices connected to the first device). The status of the first device includes, for example, but not limited to: whether wireless charging is performed with other devices, the motion posture of the first device (such as rotation, translation, and stationary), the relative position of the first device with other devices (which can represent the relative motion state with other devices), and the connection status with other devices.

[0231] In one implementation, the first device may determine whether to display the NFC card reading interface based on the acquired state of the first device. For details, see S403 and S404 below.

[0232] S403: When the first device is in the first state, the first device displays a first interface (NFC card reading interface).

[0233] S404: When the first device is in the second state, the first device displays a second interface (not an NFC card reading interface).

[0234] In one embodiment, the first state and the second state are different, and the first interface and the second interface are different. The second state is related to the second device. When the first device is in the second state, the distance between the first device and the second device is less than or equal to the first distance (for example, the distance between the NFC card reading area of ​​the first device and the second device is less than or equal to the first distance), and the movement state of the first device relative to the second device is a stationary state. The second state can be understood as a state in which the first device remains close to the second device (for example, the NFC card reading area of ​​the second device). In addition, the second state is a state in which the first device and the second device perform multiple NFC communication processes. When the first device is in the second state, the second device will send the first NFC signal to the first device multiple times (for example, periodically). If the first device does not execute the display method provided in this application, the first device will display the NFC card reading interface each time it receives the first NFC signal. If the first device executes the display method provided in this application, the first device will determine whether to display the NFC card reading interface each time it receives the first NFC signal.

[0235] Among them, the movement state of the first device relative to the second device is a stationary state, which means that the first device and the second device remain relatively stationary and do not move relative to each other. For example, the first device is a mobile phone, the second device is a vehicle, and the first device is placed flat on the NFC card reading area of ​​the second device. When the second device is in a driving state, although the first device will move synchronously with the movement of the second device (movement relative to the ground), the relative positions of the first device and the second device remain unchanged. The first device always remains flat on the NFC card reading area of ​​the first device and will not be flipped over or picked up.

[0236] In some examples, the second state includes: the first device and the second device are connected via a first short-range communication method (for example, the first digital key of the first device is connected to the second device), and the motion posture of the first device is a static posture, then the first state includes: the first device and the second device are not connected via the first short-range communication, and / or, the motion posture of the first device is not a static posture, the above-mentioned first short-range communication method is different from the NFC communication method, for example but not limited to Bluetooth, UWB, Star Flash, infrared, etc., the above-mentioned first digital key corresponds to the first short-range communication method, for example but not limited to Bluetooth key, UWB key, Star Flash key, infrared key and other digital keys. In this case, the description of S401-S404 can be found in S103-S109 of Figure 6 or S303-S312 of Figure 8. Among them, the motion posture of the first device is the posture of the first device itself moving in the space where it is located, for example, including rotation, translation, and static (i.e., remaining motionless).

[0237] It is understandable that, considering that there are certain errors when detecting the motion state of the first device relative to the second device (for example, through detection by a gyroscope sensor, an infrared module, etc.), and considering the actual application scenarios of the first and second devices, the motion state of the first device relative to the second device is a stationary state, which does not mean that the amplitude of the change in the relative position of the first and second devices is 0. The amplitude of the change in the relative position of the first and second devices is less than a certain range (for example, 1 mm) (for example, the first device translates within the NFC card reading area of ​​the second device) can be understood as the motion state of the first device relative to the second device being a stationary state, that is, the relative position of the first and second devices remains unchanged (which can also be referred to as remaining relatively stationary). Similarly, the motion posture of the first device being a stationary posture does not mean that the amplitude of the change in the position of the first device is 0. The amplitude of the change in the position of the first device is less than a certain range (for example, the first device translates within the NFC card reading area of ​​the second device) can be understood as the motion posture of the first device being a stationary posture, but when the motion posture of the first device is a stationary posture, the first device will not rotate or other movements.

[0238] In other examples, the second state includes: a state in which the first device is wirelessly charged by the second device (also referred to as a state in which the second device charges the first device), that is, a wireless charging state in which the first device acts as a charged device receiving a charging current / charging input, and the second device acts as a charging device providing a charging power source / charging input. Optionally, in this case, the NFC card reader area and the wireless charging area of ​​the electronic device 200 are integrated. In this case, the description of S401-S404 can be found in the description of S202-S207 of Figure 7.

[0239] In one embodiment, in S403, when the first device is in the first state, the first device may display the NFC card reader interface, and the first device may perform the authentication process of the first NFC key of the first device with the second device (for example, the first device sends a second NFC signal including information of the first NFC key to the second device for the second device to perform authentication). In S404, when the first device is in the second state, the first device may not display the NFC card reader interface, and the first device will not perform the authentication process of the NFC key with the second device (for example, the first device does not send information of the NFC key of the first device to the second device). At this time, the description of S403 can refer to the description of S310-S312 under Case B of Figure 8, and the description of S404 can refer to the description of S309 under Case A of Figure 8.

[0240] In another embodiment, after S401, for example, after S403 or S404, the method further includes: the first device receiving a third NFC signal (including the first identifier) ​​sent by the second device, and then obtaining the status of the first device; the first device may determine whether to display the NFC card reader interface and whether to perform the NFC key authentication process based on the status of the first device. When the first device is in the first state and / or has activated the second NFC key corresponding to the first identifier, the first device and the second device perform the NFC key authentication process (for example, the first device sends a fourth NFC signal including information about the third NFC key to the second device for the second device to authenticate), and the first device displays the NFC card reader interface, wherein the third NFC key is the second NFC key when the first device has activated the second NFC key corresponding to the first identifier, and does not correspond to the first identifier when the second NFC key is not activated. When the first device is in the second state and has not activated the NFC key corresponding to the first identifier, the first device does not perform the NFC key authentication process with the second device (for example, the first device does not send the first device's NFC key information to the second device), and the first device does not display the NFC card reader interface. At this time, the description of the first device being in the first state can be referred to S117-S119 in case B of FIG6 , and the description of the first device being in the second state can be referred to S116 in case A of FIG6 . Alternatively, the description of the first device being in the first state can be referred to S214-S216 in case B of FIG7 , and the description of the first device being in the second state can be referred to S213 in case A of FIG7 .

[0241] For the convenience of description, the embodiments of the present application are described in the order of Figures 6, 7, 8, and 9, and are not intended to limit execution to the above order. The embodiments of the present application do not limit the order of execution, execution time, number of executions, etc. of the above one or more steps. For example, in Figure 6, the order of S104 and S105 is not limited, the order of S106 and S107 is not limited, and the order of S117 and S119 is not limited.

[0242] For ease of description, the embodiments of the present application are described using the steps of Figures 6, 7, 8, and 9, and are not intended to limit the execution to all of the above steps. The embodiments of the present application may include some or all of the above steps. For example, in Figure 8, after the first device receives the second NFC signal sent by the second device, it may not obtain the status of the first device, but directly use the status obtained in S402.

[0243] The methods provided in the various embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, they may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a digital video disc (DWD), or a semiconductor medium (e.g., a solid state drive (SSD)). As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit the same. Although the present application has been described in detail with reference to the above embodiments, a person skilled in the art should understand that the technical solutions described in the above embodiments may be modified, or some of the technical features thereof may be replaced by equivalents. However, such modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A display method, characterized in that: Applied to a first device, the method includes: Receiving a first near field communication (NFC) signal sent by a second device; Obtaining a status of the first device; When the first device is in a first state, a first interface is displayed, where the first interface is an NFC card reading interface; When the first device is in a second state, a second interface is displayed, the first state and the second state are different, the first interface and the second interface are different, and the second state is related to the second device.

2. The method according to claim 1, wherein When the first device is in the second state, the distance between the first device and the second device is less than or equal to a first distance, and the motion state of the first device relative to the second device is a stationary state.

3. The method according to claim 2, wherein The second state includes: a state in which the first device is wirelessly charged by the second device; or The second state includes: the first device and the second device are connected via a first short-range communication method, and the motion posture of the first device is a static posture, wherein the first short-range communication method is different from the NFC communication method.

4. The method according to claim 3, wherein The second state includes: the first digital key of the first device is connected to the second device, the motion posture of the first device is a static posture, and the short-range communication mode and NFC communication mode corresponding to the first digital key are different.

5. The method according to any one of claims 1 to 4, characterized in that The step of displaying a first interface when the first device is in the first state includes: When the first device is in the first state, sending a second NFC signal to the second device and displaying the first interface, wherein the second NFC signal includes information about the first NFC key of the first device, and the second NFC signal is used by the second device to authenticate the first NFC key; The step of displaying a second interface when the first device is in the second state includes: When the first device is in the second state, the first device does not send the information of the NFC key of the first device to the second device, and displays the second interface.

6. The method according to any one of claims 1 to 4, characterized in that After receiving the first near field communication NFC signal sent by the second device, the method further includes: receiving a third NFC signal sent by the second device, where the third NFC signal includes the first identifier; Obtaining a status of the first device; When the first device is in the first state and / or the second NFC key corresponding to the first identifier has been activated, a fourth NFC signal is sent to the second device and the first interface is displayed, the fourth NFC signal including information of the third NFC key of the first device, the fourth NFC signal being used by the second device to authenticate the third NFC key, and the third NFC key being the second NFC key when the second NFC key has been activated by the first device; When the first device is in the second state and the NFC key corresponding to the first identifier is not activated, the first device does not send the NFC key information of the first device to the second device, and the first device displays the second interface.

7. The method according to claim 5, wherein The first NFC key is a door key or a payment key.

8. The method according to claim 6, wherein The second NFC key or the third NFC key is a car key.

9. The method according to claim 4, wherein The first digital key is a Bluetooth key, an ultra-wideband UWB key, a star flash key, or an infrared key.

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

11. A computer storage medium, characterized in that The computer storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images