Nfc interaction method, intelligent terminal and storage medium

Abstract

The application provides an NFC interaction method, device and storage medium, S1: in response to a current scene, a target template is called to generate scene information, and the scene information is stored to an NFC tag; S2: in response to a reading instruction for the NFC tag, target information is pushed from the scene information and displayed. The application realizes dynamic scene adaptation, and different templates can be called based on a scene to perform dynamic data encapsulation and storage.

Description

Technical Field

[0001] This application relates to the field of NFC tag technology, specifically to an NFC interaction method, a smart terminal, and a storage medium. Background Technology

[0002] Near Field Communication (NFC) is widely used in various fields due to its advantages such as convenience, security, and low power consumption.

[0003] For existing NFC tags, users need to manually switch the data type activated by the tag via a mobile app.

[0004] In conceiving and implementing this application, the inventors discovered at least the following problems: users need to manually select the mode, and it cannot automatically adapt to the scenario; all data is stored in plaintext, and exposing complete information to any device poses a privacy risk.

[0005] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Summary of the Invention

[0006] To address the aforementioned technical issues, this application provides an NFC interaction method, a smart terminal, and a storage medium, which enables dynamic scene adaptation and dynamically encapsulates and stores data based on different templates called according to the scene, making the operation simple and convenient.

[0007] To address the aforementioned technical problems, this application provides an NFC interaction method, comprising: S1: In response to the current scene, call the target template to generate scene information and store it in the NFC tag; S2: In response to the reading command for the NFC tag, push the target information from the scene information for display.

[0008] Optionally, before step S1, the following steps are included: The current scene is obtained by multimodal data fusion, wherein the multimodal data includes at least one of scene beacons, device gyroscope attitude, and time information.

[0009] Optionally, step S1 includes: The target template is invoked to generate scene information, and the scene information is stored in the NFC tag through a hierarchical encryption storage strategy and a differential privacy mechanism.

[0010] Optionally, step S2 includes: In response to a read command for the NFC tag, obtain the device identifier of the reading device that reads the NFC tag; The device level of the reading device is obtained based on the device identifier; Based on the device level, select the corresponding target information from the scene information and push it to the reading device for display.

[0011] Optionally, after the step of obtaining the device level of the reading device based on the device identifier, the method further includes: If the reading device is detected as an illegal device, the circuit breaker mechanism is triggered, an exception log is recorded, and an alarm is pushed to the administrator.

[0012] Optionally, step S2 includes: In response to a read command for the NFC tag, the real-time location of the reading device for reading the NFC tag is obtained; Based on the real-time location, target information is selected from the scene information and pushed to the reading device.

[0013] Optionally, after step S2, the following steps are included: When the storage time of the scene information exceeds a preset time, the scene information or the encrypted data in the scene information is deleted from the NFC tag.

[0014] Optionally, after step S1, the following steps are included: The display information is obtained from the scene information stored in the NFC tag, and the display information is displayed through the NFC tag.

[0015] This application also provides a smart terminal, including: a memory and a processor, wherein the memory stores an NFC interaction program, and when the NFC interaction program is executed by the processor, it implements the steps of the method described above.

[0016] This application also provides a computer storage medium storing a computer program that, when executed by a processor, implements the steps of the method described above.

[0017] As described above, the NFC interaction method of this application, applied to a smart terminal, includes the following steps: S1: In response to the current scene, calling the target template to generate scene information and storing it in the NFC tag; S2: In response to a read command for the NFC tag, pushing target information from the scene information for display. Through the above technical solution, dynamic scene adaptation can be achieved, and dynamic data encapsulation can be performed according to the scene, thereby improving the user experience. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0019] Figure 1 A schematic diagram of the hardware structure of a smart terminal to implement the various embodiments of this application.

[0020] Figure 2 This is a communication network system architecture diagram provided for an embodiment of this application.

[0021] Figure 3 This is a flowchart illustrating the NFC interaction method according to the first embodiment.

[0022] Figure 4 This is a system architecture diagram of the NFC interaction method shown according to the first embodiment.

[0023] Figure 5 This is a business process diagram of the NFC interaction method shown according to the first embodiment.

[0024] Figure 6 This is a flowchart illustrating an intelligent meeting scenario as shown in an embodiment of this application.

[0025] Figure 7 This is a schematic diagram illustrating a retail product traceability process in an embodiment of this application.

[0026] Figure 8 This is a schematic diagram illustrating the structure of a retail product traceability system as shown in an embodiment of this application.

[0027] Figure 9 This is a schematic diagram of a health management process shown in an embodiment of this application.

[0028] The realization of the objectives, functional features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0029] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0030] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0031] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, may be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used in this application, may be interpreted as inclusive, or mean any one or any combination thereof. For example, "including at least one of the following: A, B, C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Similarly, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Exceptions to this definition only occur when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0032] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0033] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0034] It should be noted that step designations such as S1 and S2 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the protection scope of this application.

[0035] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0036] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0037] Smart terminals can be implemented in various forms. For example, the smart terminals described in this application may include smart terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminals such as digital TVs and desktop computers.

[0038] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to the embodiments of this application can also be applied to fixed-type terminals.

[0039] Please see Figure 1 This is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application. The mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that... Figure 1 The mobile terminal structure shown does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0040] The following is combined Figure 1 A detailed introduction to each component of the mobile terminal: The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, and a duplexer. Furthermore, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), and 5G, etc.

[0041] WiFi is a short-range wireless transmission technology. Mobile terminals, through the WiFi module 102, can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 1 WiFi module 102 is shown, but it is understood that it is not a necessary component of a mobile terminal and can be omitted as needed without changing the nature of the invention.

[0042] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, etc. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0043] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage media) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0044] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0045] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0046] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Optionally, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as touch screen, can collect touch operations on or near the user (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include two parts: a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to processor 110, and can receive and execute commands sent by processor 110. In addition, touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being specifically limited here.

[0047] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 based on the type of touch event. Although in Figure 1 In this embodiment, the touch panel 1071 and the display panel 1061 are two independent components to realize the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.

[0048] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more elements within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.

[0049] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0050] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of the mobile terminal. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.

[0051] The mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components. Preferably, the power supply 111 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0052] although Figure 1 As not shown, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0053] To facilitate understanding of the embodiments of this application, the communication network system on which the mobile terminal of this application is based is described below.

[0054] Please see Figure 2 , Figure 2 This application provides a communication network system architecture diagram. The communication network system is an LTE system based on the universal mobile communication technology. The LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and the operator's IP services 204, which are connected in sequence.

[0055] Optionally, UE201 can be the aforementioned terminal 100, which will not be described in detail here.

[0056] E-UTRAN202 includes eNodeB2021 and other eNodeB2022s. Optionally, eNodeB2021 can connect to other eNodeB2022s via backhaul (e.g., X2 interface). eNodeB2021 connects to EPC203 and can provide UE201 with access to EPC203.

[0057] EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gateway) 2034, a PGW (Packet Data Network Gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, etc. Optionally, MME2031 is the control node that handles signaling between UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as the Home Location Register (not shown in the figure) and stores user-specific information such as service characteristics and data rates. All user data can be sent through SGW2034. PGW2035 can provide UE 201 IP address allocation and other functions. PCRF2036 is the policy and charging control decision point for service data flow and IP bearer resources. It selects and provides available policy and charging control decisions for the policy and charging enforcement function unit (not shown in the figure).

[0058] IP services 204 may include the Internet, intranet, IMS (IP Multimedia Subsystem), or other IP services.

[0059] Although the above description uses the LTE system as an example, those skilled in the art should understand that this application is not only applicable to the LTE system, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems (such as 5G), etc., without limitation.

[0060] Based on the above-described mobile terminal hardware structure and communication network system, various embodiments of this application are proposed.

[0061] First Embodiment Please see Figure 3 and Figure 4 , Figure 3 This is a flowchart illustrating the NFC interaction method according to the first embodiment. Figure 4 This is a system architecture diagram of the NFC interaction method shown according to the first embodiment.

[0062] like Figure 3 As shown, an embodiment of this application provides an NFC interaction method that specifically includes the following steps: S1: In response to the current scene, call the target template to generate scene information and store it in the NFC tag.

[0063] like Figure 4 As shown, the current scenario is the scenario of a mobile device (or other handheld devices such as tablets and smartwatches). The target template is the template corresponding to the current scenario; different templates need to be selected for different scenarios. For example, if the mobile device recognizes a meeting room scenario, the business logic layer calls the meeting template (including the WiFi password and meeting agenda).

[0064] It should be noted that NFC tags include: sticker type (attached to the surface of product packaging, posters, etc.), card type (used for access control, employee cards), and key fob type (access control or payment).

[0065] Optionally, before step S1, the following steps are included: obtaining the current scene through multimodal data fusion, wherein the multimodal data includes at least one of scene beacon, device gyroscope attitude, and time information.

[0066] For example, the scene recognition processing logic can be: terminal device angle <30° → handheld operation mode; conference room beacon detected → activate conference template).

[0067] like Figure 4 As shown, this application mainly utilizes a mobile device for dynamic scene recognition and data encapsulation. It should be noted that the mobile device and the receiving device can be the same device. If the mobile device also has NFC read / write capabilities, it can simultaneously serve as both the data encapsulation source (user side) and the receiving device (reader).

[0068] Context-aware engine (mobile) Functional Architecture: Based on the three-layer architecture design concept of the intelligent NFC all-in-one card system, this engine is the core module of the business logic layer, realizing scenario judgment by integrating multimodal data. Data sources: mobile phone gyroscope (attitude angle), Bluetooth beacon (spatial positioning), and system calendar (time context).

[0069] Processing logic: A hierarchical decision tree is adopted (e.g., angle <30° → handheld operation mode; conference room beacon detected → activate conference template), which is similar to the decision mechanism of the elevator controller in the all-in-one card system, but expands the dynamic scene adaptation capability.

[0070] Dynamic encapsulation engine (mobile version) Technical Implementation: Heterogeneous data is transformed into the standardized ASTER format through data access layer encapsulation technology. json { "header": {"Scene Type": "Meeting Room", "Validity Period": "2025-03-21 18:00"}, "payload": { "wifi": {"ssid": "ENC(AES256_Office)", "password": "****"}, vcard: {"Name": "Zhang San", "Phone Number": "138****5678"} } } By dynamically allocating storage space instead of fixed partitions, old data can be dynamically overwritten according to scenario needs, freeing up space for new data (such as releasing space after touching the office access control in the morning, and then touching the meeting room access control or touching product tags after get off work). The space can be reused, improving data utilization.

[0071] Optionally, step S1 includes: calling the target template to generate scene information, and storing the scene information in the NFC tag through a hierarchical encryption storage strategy and a differential privacy mechanism.

[0072] Differential privacy mechanisms involve applying different levels of encryption to different data types. For example, sensitive information is encrypted using AES256 (company Wi-Fi password); semi-public information is encrypted using dynamic de-identification (phone number 138****5678); and temporary data is encrypted using a one-time key (dynamically generated Bluetooth pairing code).

[0073] Specifically, differential privacy mechanisms can also enable tiered data exposure in resource-constrained NFC tags.

[0074] Specifically, by dynamically allocating storage space instead of the fixed partitions of NFC tags, each data storage partition can be automatically allocated according to demand (e.g., if data a requires 10 bytes and data b requires 5 bytes, then a data partition of 10-15 bytes is allocated to a and a data partition of 5-10 bytes is allocated to b; if data b only requires 3 bytes, then a data partition of 3-5 bytes is allocated to b), which allows for flexible data storage and avoids wasting storage space.

[0075] Specifically, before reading, writing, and storing data in the NFC tag, all heterogeneous data is converted into the standardized ASTER format and then stored in the NFC tag.

[0076] Specifically, this solution uses virtualized storage to dynamically allocate scene information on demand when storing it in NFC tags, thereby improving data utilization.

[0077] Technical Analysis of Virtualization Compression and Storage Utilization in This Application In traditional solutions, NFC tag storage is pre-divided into fixed partitions (such as WiFi, business card, and Bluetooth zones), with each partition storing only a single type of data. This design leads to: wasted space: even if some partitions are not used in the current scenario, they still occupy a fixed amount of capacity. Poor flexibility: the data capacity cannot be dynamically adjusted according to the scenario (e.g., it cannot be expanded when promotional information is too long).

[0078] Example: A 144-byte NTAG213 tag is divided into three fixed partitions: Partition 1 (WiFi password): 64 bytes (32 bytes actually used, 32 bytes wasted); Partition 2 (electronic business card): 48 bytes (24 bytes actually used, 24 bytes wasted); Partition 3 (Bluetooth pairing code): 32 bytes (unused, completely wasted). Actual utilization rate: only 56 / 144 ≈ 39%. The core principle of virtualized compression is to abstract the physical storage space of tags into a "virtual storage pool" through dynamic storage allocation and data lifecycle management, and to allocate and reuse space on demand to achieve efficient utilization.

[0079] Key technologies: Storage pooling: Dividing the physical storage space of tags into uniform, allocatable blocks (e.g., 16 bytes per block) instead of fixed partitions. Example: 144-byte tag → divided into 9 16-byte blocks.

[0080] Dynamic allocation algorithm: The number of blocks allocated is dynamically determined based on the data size, prioritizing the use of contiguous free blocks. Example: Writing a meeting WiFi password (32 bytes) → occupies 2 blocks (32 / 16=2). Writing a promotional link (48 bytes) → occupies 3 blocks (48 / 16=3).

[0081] Data overwrite mechanism: When data expires (such as when a meeting ends) or new data is written, the old data block is marked as erasable for subsequent reuse.

[0082] Break through traditional limitations through the following combination of technologies: 1. Allocate as needed, eliminating wasted fixed partitions. All blocks can be occupied by any data type, improving the utilization rate of NFC tag storage space and avoiding the permanent waste of fixed partitions.

[0083] Example: Meeting scenario: occupies 2 blocks (WiFi) + 1 block (agenda) → total 3 blocks (48 bytes); erase after meeting → release 3 blocks; retail scenario: occupies 4 blocks (promotional information).

[0084] 2. Data compression and compact packaging Metadata optimization: Use lightweight headers (such as the ASTER protocol) to reduce management overhead. Example: Traditional header occupies 8 bytes → optimized header occupies only 4 bytes. Differentiated encryption: Encrypt only sensitive fields, store non-sensitive data in plaintext, reducing encryption bloat. Example: Encrypt only WiFi password (16 bytes), store agenda in plaintext (16 bytes) → total 32 bytes. If fully encrypted → it may bloat to 40 bytes.

[0085] 3. Intelligent erasure and block reuse Automatic reclamation of expired data: Data is marked with an expiration date when written (e.g., "expires on 2025-03-25 18:00"), and the block is automatically released after expiration. Defragmentation: Free blocks are periodically merged (similar to disk defragmentation) to reduce storage fragmentation.

[0086] Optionally, after step S1, the steps include: obtaining display information from the scene information stored in the NFC tag, and displaying the display information via the NFC tag.

[0087] Specifically, the hardware components of an NFC tag may include: an NFC chip (stores data and supports reading and writing), an e-ink screen (a low-power display module), and a microcontroller (parses data and drives the screen). The e-ink screen can be used to display some scenario information. For example, a smart doorplate for a meeting room: Before the meeting: The phone detects the user entering the meeting room → the NFC tag displays "Preparing". During the meeting: Touching the tag, the phone writes agenda data → the screen displays "Meeting in Progress" + a countdown.

[0088] like Figure 4 and Figure 6As shown, after a mobile device (such as a user's phone) detects the meeting room Bluetooth beacon (such as a Huawei IdeaHub device), it automatically encapsulates the meeting WiFi password, electronic agenda, and participant business cards using the meeting room template; and displays the "Meeting in Progress" status on the e-ink screen. Other users can obtain the meeting room WiFi password and meeting agenda by touching the access control device with a reader to read the NFC tag.

[0089] The specific steps for determining whether a mobile device is in a meeting room setting through multimodal data fusion are as follows: 1. Bluetooth beacon detection: Equipment: A Bluetooth beacon (such as a Huawei IdeaHub device) is deployed in the conference room, continuously broadcasting a unique ID (e.g., B0:34:95:XX:XX:XX). Mobile Operation: The user's mobile phone Bluetooth module scans and identifies the beacon to confirm the physical location as the conference room.

[0090] 2. Gyroscope attitude verification: Data: The phone's gyroscope detected a tilt angle >25°, indicating that the user is holding the phone (not with the phone lying flat or in a pocket).

[0091] 3. System schedule matching: Data source: The "project meeting" time marked in the phone calendar is matched with the current time to enhance the credibility of the scenario.

[0092] 4. Multimodal decision-making: Logic: Only when all three conditions (Bluetooth beacon + gyroscope angle + schedule time) are met simultaneously is it determined that the user has indeed entered the meeting room.

[0093] S2: In response to a reading command for an NFC tag, push target information from scene information for display.

[0094] Specifically, the reading device (i.e. Figure 4 The receiving device can read data from NFC tags that store scene information through the NFC function, thereby obtaining the corresponding target information.

[0095] It should be noted that when the reading device reads data from the NFC tag, it can also perform scene recognition and then push the target information of the corresponding scene to the reading device. That is, the NFC tag can contain scene information for multiple scenes. After the reading terminal performs scene recognition, uploads the information to the server / cloud, and then pushes the target information of the corresponding scene to the reading device.

[0096] like Figure 9As shown, when a patient wears an NFC tag and a medical emergency scenario is detected, the tag automatically exposes anonymized medical records and emergency contacts. This allows any reading device to access these information from the NFC tag. Furthermore, if the reading device's trust level is L2 or higher, it can read the patient's complete medical records and emergency guidelines from the NFC tag. In hospital settings, the device level can remove unauthorized devices, allowing all reading devices to access the information in the NFC tag, but only pre-verified devices can obtain the complete information.

[0097] Optionally, step S2 includes: in response to a reading command for an NFC tag, obtaining the device identifier of the reading device for reading the NFC tag; obtaining the device level of the reading device based on the device identifier; selecting the corresponding target information from the scene information based on the device level, and pushing it to the reading device for display.

[0098] For example, when a user touches the access control device with their handheld device to read the NFC tag, the access control device can send the device fingerprint and device ID (e.g., MAC address + digital certificate) to the cloud. The cloud returns the device level based on the uploaded device identifier: L2 (meeting room authentication device) → decrypts the complete WiFi configuration, thereby automatically configuring the smart devices in the meeting room (such as smart screens and projectors) to connect to the network. After the participants enter the meeting room, their devices are connected to the network and can directly project or share files.

[0099] like Figure 5 As shown, when reading an NFC tag, the reader also needs to send its own device ID and other device identifiers to the recipient. After obtaining the device ID, it is uploaded to the cloud. Based on the device ID, the trust level (i.e., device level) of the device can be obtained. Data exposure is then tiered according to the trust level of the reader, with different levels of decryption sent based on the device level. For example, if the reader is at the highest level (L2), the complete data stored in the NFC tag is returned; if the reader is at level L1, de-identified data is returned to prevent all devices from obtaining the complete data, thereby improving data privacy protection.

[0100] Optionally, after obtaining the device level of the reading device based on the device identifier, the method further includes: if the reading device is detected to be an illegal device, triggering a circuit breaker mechanism, recording an exception log, and pushing an alarm to the administrator.

[0101] like Figure 5As shown, to further protect data privacy, unauthorized devices can be set in the device trust level. After obtaining the device ID and uploading it to the cloud, the cloud verifies the device ID to determine whether the reading device is a verified device (or an unauthorized device). If an unauthorized device is detected, a circuit breaker mechanism is triggered, clearing dynamically generated Bluetooth pairing codes and other information, recording an exception log, and pushing an alarm to the administrator.

[0102] Optionally, step S2 includes: in response to a reading command for an NFC tag, obtaining the real-time location of the reading device for reading the NFC tag; and selecting target information from scene information based on the real-time location and pushing it to the reading device.

[0103] like Figure 7 As shown, after the reading device touches the product tag, the location information of the reading device is obtained, and an AR experience link + blockchain hash value is dynamically generated. Localized promotional information is pushed through the AR experience link, allowing the reading device to access and view relevant promotional information, including discounts and coupons. Figure 8 As shown, the reading device can obtain the milk's origin, blockchain ID, and promotional information by scanning the milk label, which helps improve customer interaction.

[0104] Optionally, after step S2, the following steps are included: if the storage time of the scene information exceeds a preset time, deleting the scene information from the NFC tag or deleting the encrypted data in the scene information.

[0105] like Figure 6 In the meeting room scenario shown, after the meeting ends and the meeting time is detected, the e-ink display on the NFC tag can be updated to "idle" and the encrypted data of the scene information (such as Wi-Fi password, meeting agenda, etc.) stored therein can be erased.

[0106] This application achieves dynamic scene adaptation through the above methods, breaking through the limitations of manual switching and enabling intelligent data distribution based on environmental awareness; it achieves lightweight privacy protection, enabling hierarchical data exposure in resource-constrained NFC tags; and it optimizes NFC tag storage space by improving the storage efficiency of small tags through virtualization encapsulation technology.

[0107] This application also provides a smart terminal, which includes a memory and a processor. The memory stores an NFC interaction program, and when the NFC interaction program is executed by the processor, it implements the steps of the NFC interaction method in any of the above embodiments.

[0108] This application also provides a computer-readable storage medium storing an NFC interaction program, which, when executed by a processor, implements the steps of the NFC interaction method in any of the above embodiments.

[0109] In the embodiments of the smart terminal and computer-readable storage medium provided in this application, all the technical features of any of the above-described NFC interaction method embodiments may be included. The extended and explanatory content of the specification is basically the same as that of the embodiments of the above methods, and will not be repeated here.

[0110] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the methods described in the various possible implementations above.

[0111] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.

[0112] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0113] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0114] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0115] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0116] In this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions are generally described in detail only when they appear for the first time. When they appear again, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions that are not described in detail later can be referred to their previous relevant detailed descriptions.

[0117] In this application, the descriptions of the various embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0118] The technical features of the present application can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.

[0119] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the methods of each embodiment of this application.

[0120] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, storage disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0121] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. An NFC interaction method, characterized in that, The method includes the following steps: S1: In response to the current scene, call the target template to generate scene information and store it in the NFC tag; S2: In response to the reading command for the NFC tag, push the target information from the scene information for display.

2. The method as described in claim 1, characterized in that, Before step S1, the following are included: The current scene is obtained by multimodal data fusion, wherein the multimodal data includes at least one of scene beacons, device gyroscope attitude, and time information.

3. The method as described in claim 1, characterized in that, Step S1 includes: The target template is invoked to generate scene information, and the scene information is stored in the NFC tag through a hierarchical encryption storage strategy and a differential privacy mechanism.

4. The method as described in claim 1, characterized in that, Step S2 includes: In response to a read command for the NFC tag, obtain the device identifier of the reading device that reads the NFC tag; The device level of the reading device is obtained based on the device identifier; Based on the device level, select the corresponding target information from the scene information and push it to the reading device for display.

5. The method as described in claim 4, characterized in that, After obtaining the device level of the reading device based on the device identifier, the method further includes: If the reading device is detected as an illegal device, the circuit breaker mechanism is triggered, an exception log is recorded, and an alarm is pushed to the administrator.

6. The method as described in claim 1, characterized in that, Step S2 includes: In response to a read command for the NFC tag, the real-time location of the reading device for reading the NFC tag is obtained; Based on the real-time location, target information is selected from the scene information and pushed to the reading device.

7. The method as described in claim 1, characterized in that, Following step S2, the following is included: When the storage time of the scene information exceeds a preset time, the scene information or the encrypted data in the scene information is deleted from the NFC tag.

8. The method as described in claim 1, characterized in that, Following step S1, the following is included: The display information is obtained from the scene information stored in the NFC tag, and the display information is displayed through the NFC tag.

9. A smart terminal, characterized in that, The smart terminal includes a memory and a processor, wherein the memory stores an NFC interaction program, and when the NFC interaction program is executed by the processor, it implements the steps of the NFC interaction method as described in any one of claims 1 to 8.

10. A readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the NFC interaction method as described in any one of claims 1 to 8.

Images