Equipment ledger management system, equipment and method based on NFC (Near Field Communication) module

Abstract

The invention discloses an equipment ledger management system, equipment and method based on an NFC module, and the system comprises an NFC data interaction module which triggers the near field communication between an NFC tag and a read-write terminal, and achieves the on-site reading and writing of equipment data; the standing book management core module integrates equipment information input, state updating, full life cycle recording and query statistics functions; the data synchronization module realizes real-time data interaction between a terminal and a server, and supports automatic synchronization after offline caching and network recovery; the authority management module allocates access authority based on roles and records an operation log; and the data encryption module encrypts the sensitive information and the transmission data. According to the equipment ledger management system and method, the equipment ledger data entry process can be effectively simplified, manual operation is reduced, the data collection efficiency is improved, full-period tracing and query of the ledger and real-time data updating can be achieved, and the application scene is wide.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of equipment account management, and in particular to an equipment account management system, equipment and method based on an NFC module. BACKGROUND

[0002] The equipment account is the core carrier of equipment management, and its data integrity and real-time directly affect the equipment maintenance efficiency, asset utilization rate and management decision-making scientificity. The traditional equipment account management mode mainly relies on manual input, paper records or simple two-dimensional code / bar code scanning assisted management, and has the following difficult-to-solve technical defects:

[0003] Low data collection efficiency and high error rate: in the traditional mode, the information of equipment warehousing, maintenance, circulation and the like needs to be manually input into the system, which is tedious and time-consuming, especially for the scenes of many and scattered field equipment and industrial equipment, the manual input cost is extremely high; at the same time, manual input is prone to problems such as number error, parameter omission and date deviation, and according to statistics, the data error rate of the traditional mode is generally more than 5%, which seriously affects the reliability of the account data.

[0004] Data synchronization has serious lag: the equipment status, fault information, maintenance records and other data collected by field personnel on site need to be recorded on paper or re-input into the system after returning to the office, which leads to a time difference of several hours to several days between the account data and the actual situation of the equipment, and the management personnel cannot grasp the equipment status in real time, which easily causes problems such as untimely maintenance and unreasonable resource scheduling.

[0005] Weak equipment identification and traceability: the traditional two-dimensional code / bar code is prone to be unable to be identified due to wear, dirt and obstruction, and only supports one-way data reading, and cannot update the dynamic information of the equipment; the manual checking of equipment numbers is inefficient, and the whole life cycle track of the equipment such as maintenance, circulation and scrap is stored in scattered form, which is difficult to integrate to form a complete file, and the traceability is difficult, and the traceability requirement of equipment management cannot be met.

[0006] Data security and lack of permission control: the existing account management system lacks a fine-grained permission control mechanism, and non-authorized personnel may modify the account data or leak sensitive information such as confidential equipment parameters; at the same time, there is no effective encryption measure in the process of data transmission and storage, and there is a risk of data leakage, especially for confidential equipment management, the security risk is prominent.

[0007] Insufficient system adaptability and expansibility: the traditional account management system is designed for a single scene, and it is difficult to adapt to the management needs of different types of equipment such as field, industrial and confidential; and the compatibility with the existing equipment management system is poor, the replacement cost is high, and data interconnection and sharing cannot be realized.

[0008] In existing technologies, NFC modules have been applied to scenarios such as access control and mobile payment. Some technologies attempt to use NFC for device identification, but only achieve a single authentication function, failing to deeply integrate with the entire process of device ledger management. For example, some solutions only store device numbers through NFC tags, requiring secondary queries of ledger information from other systems, and cannot achieve on-site data writing and automatic ledger updates. Some solutions lack full lifecycle record integration and access control mechanisms, failing to address the core pain points of traditional ledger management and struggling to meet the needs of intelligent and refined device management. Therefore, there is an urgent need for a system that deeply integrates NFC technology with the entire ledger management process, enabling automatic data collection, real-time synchronization, secure control, and full lifecycle traceability. Summary of the Invention

[0009] To address the aforementioned technical issues, this invention proposes an equipment ledger management system and method based on an NFC module. This system and method can effectively simplify the equipment ledger data entry process, reduce manual operations, improve data collection efficiency, and enable full-cycle traceability and querying of the ledger, with real-time data updates and wide applicability.

[0010] An NFC-based device ledger management system includes an NFC data interaction module, a ledger management core module, a data synchronization module, an access control module, and a data encryption module. The NFC data interaction module triggers near-field communication between NFC tags and a reader / writer terminal, enabling on-site reading and writing of device data. The ledger management core module integrates device information entry, status updates, full lifecycle recording, and query statistics functions. The data synchronization module enables real-time data interaction between the terminal and the server, supporting offline caching and automatic synchronization after network recovery. The access control module assigns access permissions based on roles and records operation logs. The data encryption module encrypts sensitive information and transmitted data.

[0011] As a preferred embodiment of the above technical solution, the core module for ledger management includes:

[0012] The information entry submodule automatically fills the ledger with static information read from NFC tags by an NFC reader / writer terminal, eliminating the need for manual entry of core data.

[0013] The status update submodule has preset status options including "in use", "under repair", "idle", "scrapped" and "in transfer", and supports one-click update of the terminal and real-time synchronization to the server.

[0014] The full lifecycle recording submodule integrates equipment maintenance records, circulation records, scrapping records, and operation logs to form a timeline-style lifecycle archive, and supports uploading attachments including maintenance vouchers and transfer documents.

[0015] The query and statistics submodule supports queries based on keyword combinations including equipment UID, model, user department, status, and time, and generates statistical reports including equipment distribution, maintenance frequency, and scrap rate.

[0016] As a preferred embodiment of the above technical solution, the data synchronization module uses the WebSocket protocol to achieve real-time communication, caches data through an SQLite database in offline mode, and avoids duplicate data uploads by using an incremental synchronization algorithm based on operation timestamps after the network is restored.

[0017] As a preferred embodiment of the above technical solution, the permission management module is based on the RBAC role-based access control model, with three preset roles: administrator, operator, and viewer. Administrators have full permissions, operators have data read and write permissions, and viewers only have query permissions. All operations are logged with information such as the operator, operation time, and operation content.

[0018] As a preferred embodiment of the above technical solution, the data encryption module adopts the AES-256 encryption algorithm to encrypt sensitive information in the NFC tag and the data transmitted between the terminal and the server. The key is managed uniformly by the server, and the terminal obtains the key after passing security authentication.

[0019] An NFC-based device ledger management device includes an NFC tag attached to the device to be managed, an NFC reader / writer terminal with network communication capabilities, and a server for data storage and service operation.

[0020] As a preferred embodiment of the above technical solution, the NFC tag adopts an IP68-level waterproof and dustproof industrial package, with a built-in unmodifiable unique identifier (UID). The storage area is divided into a static information area and a dynamic snapshot area. The static information area stores the device model, serial number, rated parameters, and manufacturer information, while the dynamic snapshot area can be repeatedly written with dynamic data including the current status of the device, the user, and the most recent maintenance records.

[0021] As a preferred embodiment of the above technical solution, the NFC reader / writer terminal is a smartphone, tablet, or industrial-grade dedicated reader / writer with an integrated NFC module, supports 4G / 5G / Wi-Fi network communication, has offline data caching capability, communication distance ≤10cm, and data reading response speed ≤0.5 seconds.

[0022] As a preferred embodiment of the above technical solution, the server is deployed in the cloud or locally, configured with a high-concurrency data processing unit and a dual backup mechanism, including daily scheduled backup and off-site backup. The data layer uses a MySQL relational database to store structured data, supporting data indexing and fast querying.

[0023] A device ledger management method based on an NFC module, the specific process of which is as follows:

[0024] Step 1: Device entry and NFC tag binding:

[0025] When equipment is put into storage, the manager operates the NFC reader / writer terminal and first initiates tag communication through the terminal's NFC data interaction module to verify the NFC tag's access password.

[0026] After successful verification, the device's static basic information is written into the static information area of ​​the NFC tag, and the information is simultaneously synchronized to the server via 4G / 5G / Wi-Fi network;

[0027] The information entry submodule of the server-side ledger management core module automatically receives data, generates ledger entries with unique UIDs, and completes the binding of "device-NFC tag-ledger". At this time, the ledger status is initialized to "idle", and the operation log synchronously records the administrator's identity and binding time.

[0028] Step 2, On-site data collection and two-way interaction:

[0029] When field staff or operators need to update information at the equipment site, they do not need to align the tag; they only need to bring the NFC reader / writer terminal close to the equipment, and the terminal will automatically trigger the NFC data interaction module.

[0030] Data reading: Quickly reads the UID and dynamic snapshot data from the tag. The terminal automatically links to the server ledger through the data synchronization module to display the current status of the device, the user, and historical maintenance records, avoiding manual verification of the serial number.

[0031] Data writing: If it is necessary to update the device status or enter maintenance records, the operator selects preset options or enters information through the terminal interface. The data is first cached locally on the terminal and then synchronously written to the dynamic snapshot area of ​​the NFC tag and the server.

[0032] Before writing, the terminal automatically verifies the operator's permissions through the permission management module to prevent unauthorized modification;

[0033] Step 3: Real-time data synchronization and automatic ledger updates:

[0034] If the terminal is connected to the network, the data synchronization module transmits the dynamic data collected on-site to the server in real time via the WebSocket protocol;

[0035] The status update submodule of the server-side ledger management core module automatically receives data and updates the "equipment status", "user" and "maintenance record" fields in the ledger. At the same time, the full lifecycle recording submodule integrates this operation into the equipment lifecycle archive according to the timestamp.

[0036] If the terminal is offline, the data is temporarily stored locally on the terminal. After the network is restored, the data synchronization module uses an incremental synchronization algorithm based on the operation timestamp to upload only the new data that has not been synchronized to the server, avoiding duplicate uploads and data conflicts, and ensuring that the ledger data is consistent with the actual situation of the equipment.

[0037] Step 4: Permission Verification and Data Security Control

[0038] Permission verification: Before the terminal performs an operation, the permission management module verifies the user's role using the RBAC model; when the server receives data, it performs a secondary verification of the operation permissions and the terminal's legitimacy to prevent unauthorized terminals from uploading data.

[0039] Data encryption: During data transmission, the data encryption module uses the AES-256 algorithm to encrypt sensitive information, and the key is dynamically allocated by the server; sensitive data stored in the NFC tag is also encrypted, and only authorized terminals can decrypt and read it to prevent data leakage;

[0040] Step 5: Query, traceability, and statistical analysis:

[0041] Terminal query: Scan tags with an NFC reader / writer to view the device's entire lifecycle record in real time; Backend query: Log in to the server's front-end management interface and use the query and statistics sub-module of the ledger management core module to query by combination of keywords such as UID, department, and status. The system automatically generates statistical reports and supports exporting to Excel.

[0042] If it is necessary to trace the movement of a certain piece of equipment, all operation records from its entry into the warehouse to the present can be viewed through the timeline archive, which meets the management and auditing needs;

[0043] Step Six: Equipment Scrapping and Record Filing:

[0044] When equipment reaches the scrapping conditions, the administrator initiates a scrapping application through the server backend. After the approval process is completed, the full life cycle record submodule of the operation ledger management core module updates the equipment status to "scrapped" and enters the scrapping reason and disposal result.

[0045] At the same time, the dynamic snapshot area of ​​the NFC tag is updated to "discarded" status to prevent accidental operation; the server automatically archives the complete ledger file of the device to the historical database to retain traceability evidence and complete the closed loop of the device's full life cycle management.

[0046] The beneficial effects of this invention are as follows:

[0047] Simplify the equipment ledger data entry process, reduce manual operations, and improve data collection efficiency; achieve real-time synchronization between on-site equipment data and the back-end ledger, eliminate data lag issues, and support managers to monitor equipment status in real time; improve the stability and convenience of equipment identification, overcome the defects of QR codes / barcodes being easily worn, and support bidirectional data reading and writing; establish a full lifecycle ledger archive for equipment, enabling traceability and queryability of equipment information, and meeting management and auditing needs; add refined permission management and data encryption mechanisms to ensure the security and integrity of ledger data; improve system adaptability and scalability, and support multi-scenario equipment management and integration with existing systems. Attached Figure Description

[0048] Figure 1 This is a flowchart of the equipment ledger management method of the present invention. Detailed Implementation

[0049] The technical solution of the present invention will be clearly and completely described below with reference to the accompanying drawings. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0050] An NFC-based device ledger management system includes an NFC data interaction module, a ledger management core module, a data synchronization module, an access control module, and a data encryption module. The NFC data interaction module triggers near-field communication between NFC tags and a reader / writer terminal, enabling on-site reading and writing of device data. The ledger management core module integrates device information entry, status updates, full lifecycle recording, and query statistics functions. The data synchronization module enables real-time data interaction between the terminal and the server, supporting offline caching and automatic synchronization after network recovery. The access control module assigns access permissions based on roles and records operation logs. The data encryption module encrypts sensitive information and transmitted data.

[0051] In this embodiment, the core module for ledger management includes:

[0052] The information entry submodule automatically fills the ledger with static information read from NFC tags by an NFC reader / writer terminal, eliminating the need for manual entry of core data.

[0053] The status update submodule has preset status options including "in use", "under repair", "idle", "scrapped" and "in transfer", and supports one-click update of the terminal and real-time synchronization to the server.

[0054] The full lifecycle recording submodule integrates equipment maintenance records, circulation records, scrapping records, and operation logs to form a timeline-style lifecycle archive, and supports uploading attachments including maintenance vouchers and transfer documents.

[0055] The query and statistics submodule supports queries based on keyword combinations including equipment UID, model, user department, status, and time, and generates statistical reports including equipment distribution, maintenance frequency, and scrap rate.

[0056] Specifically, the core module of ledger management is deployed on a server, and the backend service can be developed using the Spring Boot framework, while the frontend management interface can be developed using Vue.js.

[0057] In this embodiment, the data synchronization module uses the WebSocket protocol to achieve real-time communication. In offline mode, data is cached through an SQLite database. After the network is restored, an incremental synchronization algorithm based on the operation timestamp is used to avoid duplicate data uploads.

[0058] In this embodiment, the permission management module is based on the RBAC role-based access control model, with three preset roles: administrator, operator, and viewer. Administrators have full permissions, operators have data read and write permissions, and viewers only have query permissions. All operations are logged with information such as the operator, operation time, and operation content.

[0059] In this embodiment, the data encryption module uses the AES-256 encryption algorithm to encrypt sensitive information in the NFC tag and the data transmitted between the terminal and the server. The key is managed uniformly by the server, and the terminal obtains the key after passing security authentication.

[0060] Specifically, a MySQL 8.0 relational database is used to store all equipment ledger data, including: static data: equipment UID, model, serial number, rated parameters, manufacturer, production date, warehousing date, and user department; dynamic data: current equipment status, user, storage location, maintenance records, circulation records, and scrapping records; system data: user information, role permissions, operation logs, and key information; the database is configured with data indexes to ensure query efficiency; and it supports data backup and recovery, with automatic backup at 1 AM daily. Backup files are stored locally and remotely (such as on Alibaba Cloud OSS) to prevent data loss.

[0061] An NFC-based device ledger management device includes an NFC tag attached to the device to be managed, an NFC reader / writer terminal with network communication capabilities, and a server for data storage and service operation.

[0062] In this embodiment, the NFC tag adopts an IP68-level waterproof and dustproof industrial package, with a built-in unmodifiable unique identifier (UID). The storage area is divided into a static information area and a dynamic snapshot area. The static information area stores the device model, serial number, rated parameters, and manufacturer information. The dynamic snapshot area can be repeatedly written with dynamic data including the current status of the device, the user, and the most recent maintenance records.

[0063] Specifically, the NFC tag has a built-in NXP MIFARE Classic 1K chip.

[0064] In this embodiment, the NFC reader / writer terminal is a smartphone, tablet, or industrial-grade dedicated reader / writer with an integrated NFC module, supports 4G / 5G / Wi-Fi network communication, has offline data caching capability, communication distance ≤10cm, and data reading response speed ≤0.5 seconds.

[0065] Specifically, the NFC reader / writer terminal supports Android 8.0 and above or iOS 13.0 and above.

[0066] In this embodiment, the server is deployed in the cloud or locally, configured with a high-concurrency data processing unit and a dual backup mechanism, including daily scheduled backup and off-site backup. The data layer uses a MySQL relational database to store structured data, supporting data indexing and fast querying.

[0067] Specifically, the server is deployed in the cloud (such as Alibaba Cloud ECS) or a local data center, and is configured with 8 cores, 16GB of memory, and 500GB of SSD storage.

[0068] like Figure 1 The device ledger management method based on an NFC module is shown below, with the specific process as follows:

[0069] Step 1: Device entry and NFC tag binding:

[0070] When equipment is put into storage, the manager operates the NFC reader / writer terminal and first initiates tag communication through the terminal's NFC data interaction module to verify the NFC tag's access password.

[0071] After successful verification, the device's static basic information is written into the static information area of ​​the NFC tag, and the information is simultaneously synchronized to the server via 4G / 5G / Wi-Fi network;

[0072] The information entry submodule of the server-side ledger management core module automatically receives data, generates ledger entries with unique UIDs, and completes the binding of "device-NFC tag-ledger". At this time, the ledger status is initialized to "idle", and the operation log synchronously records the administrator's identity and binding time.

[0073] Step 2, On-site data collection and two-way interaction:

[0074] When field staff or operators need to update information at the equipment site, they do not need to align the tag; they only need to bring the NFC reader / writer terminal close to the equipment, and the terminal will automatically trigger the NFC data interaction module.

[0075] Data reading: Quickly reads the UID and dynamic snapshot data from the tag. The terminal automatically links to the server ledger through the data synchronization module to display the current status of the device, the user, and historical maintenance records, avoiding manual verification of the serial number.

[0076] Data writing: If it is necessary to update the device status or enter maintenance records, the operator selects preset options or enters information through the terminal interface. The data is first cached locally on the terminal and then synchronously written to the dynamic snapshot area of ​​the NFC tag and the server.

[0077] Before writing, the terminal automatically verifies the operator's permissions through the permission management module to prevent unauthorized modification;

[0078] Step 3: Real-time data synchronization and automatic ledger updates:

[0079] If the terminal is connected to the network, the data synchronization module transmits the dynamic data collected on-site to the server in real time via the WebSocket protocol;

[0080] The status update submodule of the server-side ledger management core module automatically receives data and updates the "equipment status", "user" and "maintenance record" fields in the ledger. At the same time, the full lifecycle recording submodule integrates this operation into the equipment lifecycle archive according to the timestamp.

[0081] If the terminal is offline, the data is temporarily stored locally on the terminal. After the network is restored, the data synchronization module uses an incremental synchronization algorithm based on the operation timestamp to upload only the new data that has not been synchronized to the server, avoiding duplicate uploads and data conflicts, and ensuring that the ledger data is consistent with the actual situation of the equipment.

[0082] Step 4: Permission Verification and Data Security Control

[0083] Permission verification: Before the terminal performs an operation, the permission management module verifies the user's role using the RBAC model; when the server receives data, it performs a secondary verification of the operation permissions and the terminal's legitimacy to prevent unauthorized terminals from uploading data.

[0084] Data encryption: During data transmission, the data encryption module uses the AES-256 algorithm to encrypt sensitive information, and the key is dynamically allocated by the server; sensitive data stored in the NFC tag is also encrypted, and only authorized terminals can decrypt and read it to prevent data leakage;

[0085] Step 5: Query, traceability, and statistical analysis:

[0086] Terminal query: Scan tags with an NFC reader / writer to view the device's entire lifecycle record in real time; Backend query: Log in to the server's front-end management interface and use the query and statistics sub-module of the ledger management core module to query by combination of keywords such as UID, department, and status. The system automatically generates statistical reports and supports exporting to Excel.

[0087] If it is necessary to trace the movement of a certain piece of equipment, all operation records from its entry into the warehouse to the present can be viewed through the timeline archive, which meets the management and auditing needs;

[0088] Step Six: Equipment Scrapping and Record Filing:

[0089] When equipment reaches the scrapping conditions, the administrator initiates a scrapping application through the server backend. After the approval process is completed, the full life cycle record submodule of the operation ledger management core module updates the equipment status to "scrapped" and enters the scrapping reason and disposal result.

[0090] At the same time, the dynamic snapshot area of ​​the NFC tag is updated to "discarded" status to prevent accidental operation; the server automatically archives the complete ledger file of the device to the historical database to retain traceability evidence and complete the closed loop of the device's full life cycle management.

[0091] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A device ledger management system based on an NFC module, characterized in that: It includes an NFC data interaction module, a ledger management core module, a data synchronization module, an access control module, and a data encryption module. The NFC data interaction module triggers near-field communication between the NFC tag and the reader / writer terminal to enable on-site reading and writing of device data. The ledger management core module integrates equipment information entry, status update, full lifecycle recording, and query statistics functions; the data synchronization module enables real-time data interaction between the terminal and the server, and supports offline caching and automatic synchronization after network recovery; the permission management module assigns access permissions based on roles and records operation logs; and the data encryption module encrypts sensitive information and transmitted data.

2. The device ledger management system based on an NFC module according to claim 1, characterized in that: The core module of the ledger management includes: The information entry submodule automatically fills the ledger with static information read from NFC tags by an NFC reader / writer terminal, eliminating the need for manual entry of core data. The status update submodule has preset status options including "in use", "under repair", "idle", "scrapped" and "in transfer", and supports one-click update of the terminal and real-time synchronization to the server; The full lifecycle recording submodule integrates equipment maintenance records, circulation records, scrapping records, and operation logs to form a timeline-style lifecycle archive, and supports uploading attachments including maintenance vouchers and transfer documents. The query and statistics submodule supports queries based on keyword combinations including equipment UID, model, user department, status, and time, and generates statistical reports including equipment distribution, maintenance frequency, and scrap rate.

3. The device ledger management system based on an NFC module according to claim 1, characterized in that: The data synchronization module uses the WebSocket protocol to achieve real-time communication. In offline mode, data is cached through an SQLite database. After the network is restored, an incremental synchronization algorithm based on the operation timestamp is used to avoid duplicate data uploads.

4. The device ledger management system based on an NFC module according to claim 1, characterized in that: The permission management module is based on the RBAC role-based access control model, with three preset roles: administrator, operator, and viewer. Administrators have full permissions, operators have data read and write permissions, and viewers only have query permissions. All operations are logged with information such as the operator, operation time, and operation content.

5. The device ledger management system based on an NFC module according to claim 1, characterized in that: The data encryption module uses the AES-256 encryption algorithm to encrypt sensitive information in the NFC tag and the data transmitted between the terminal and the server. The key is managed uniformly by the server, and the terminal obtains the key after passing security authentication.

6. A device ledger management device based on an NFC module, characterized in that: This includes NFC tags attached to the devices to be managed, NFC reader / writer terminals with network communication capabilities, and servers used for data storage and service operation.

7. The device ledger management device based on an NFC module according to claim 6, characterized in that: The NFC tag adopts an IP68-level waterproof and dustproof industrial package, with a built-in unmodifiable unique identifier (UID). The storage area is divided into a static information area and a dynamic snapshot area. The static information area stores the device model, serial number, rated parameters, and manufacturer information. The dynamic snapshot area can be repeatedly written with dynamic data including the current status of the device, the user, and the most recent maintenance records.

8. The device ledger management device based on an NFC module according to claim 6, characterized in that: The NFC reader / writer terminal is a smartphone, tablet, or industrial-grade dedicated reader / writer with an integrated NFC module. It supports 4G / 5G / Wi-Fi network communication, has offline data caching capabilities, a communication distance of ≤10cm, and a data reading response speed of ≤0.5 seconds.

9. The device ledger management device based on an NFC module according to claim 6, characterized in that: The server is deployed in the cloud or locally, configured with a high-concurrency data processing unit and a dual backup mechanism, including daily scheduled backup and off-site backup. The data layer uses a MySQL relational database to store structured data, supporting data indexing and fast querying.

10. A device ledger management method based on an NFC module, characterized in that: The specific process is as follows: Step 1: Device entry and NFC tag binding: When equipment is put into storage, the manager operates the NFC reader / writer terminal and first initiates tag communication through the terminal's NFC data interaction module to verify the NFC tag's access password. After successful verification, the device's static basic information is written into the static information area of ​​the NFC tag, and the information is simultaneously synchronized to the server via 4G / 5G / Wi-Fi network; The information entry submodule of the server-side ledger management core module automatically receives data, generates ledger entries with unique UIDs, and completes the binding of "device-NFC tag-ledger". At this time, the ledger status is initialized to "idle", and the operation log synchronously records the administrator's identity and binding time. Step 2, On-site data collection and two-way interaction: When field staff or operators need to update information at the equipment site, they do not need to align the tag; they only need to bring the NFC reader / writer terminal close to the equipment, and the terminal will automatically trigger the NFC data interaction module. Data reading: Quickly reads the UID and dynamic snapshot data from the tag. The terminal automatically links to the server ledger through the data synchronization module to display the current status of the device, the user, and historical maintenance records, avoiding manual verification of the serial number. Data writing: If it is necessary to update the device status or enter maintenance records, the operator selects preset options or enters information through the terminal interface. The data is first cached locally on the terminal and then synchronously written to the dynamic snapshot area of ​​the NFC tag and the server. Before writing, the terminal automatically verifies the operator's permissions through the permission management module to prevent unauthorized modification; Step 3: Real-time data synchronization and automatic ledger updates: If the terminal is connected to the network, the data synchronization module transmits the dynamic data collected on-site to the server in real time via the WebSocket protocol; The status update submodule of the server-side ledger management core module automatically receives data and updates the "equipment status", "user" and "maintenance record" fields in the ledger. At the same time, the full lifecycle record submodule integrates this operation into the equipment lifecycle archive according to the timestamp. If the terminal is offline, the data is temporarily stored locally on the terminal. After the network is restored, the data synchronization module uses an incremental synchronization algorithm based on the operation timestamp to upload only the new data that has not been synchronized to the server, avoiding duplicate uploads and data conflicts, and ensuring that the ledger data is consistent with the actual situation of the equipment. Step 4: Permission Verification and Data Security Control Permission verification: Before the terminal performs an operation, the permission management module verifies the user's role using the RBAC model; when the server receives data, it performs a secondary verification of the operation permissions and the terminal's legitimacy to prevent unauthorized terminals from uploading data. Data encryption: During data transmission, the data encryption module uses the AES-256 algorithm to encrypt sensitive information, and the key is dynamically allocated by the server; sensitive data stored in the NFC tag is also encrypted, and only authorized terminals can decrypt and read it to prevent data leakage; Step 5: Query, traceability, and statistical analysis: Terminal query: Scan tags with an NFC reader / writer to view the device's entire lifecycle record in real time; Backend query: Log in to the server's front-end management interface and use the query and statistics sub-module of the ledger management core module to query by combination of keywords such as UID, department, and status. The system automatically generates statistical reports and supports exporting to Excel. If it is necessary to trace the movement of a certain piece of equipment, all operation records from its entry into the warehouse to the present can be viewed through the timeline archive, which meets the management and auditing needs; Step Six: Equipment Scrapping and Record Filing: When equipment reaches the scrapping conditions, the administrator initiates a scrapping application through the server backend. After the approval process is completed, the full lifecycle record submodule of the operation ledger management core module updates the equipment status to "scrapped" and enters the scrapping reason and disposal result. At the same time, the dynamic snapshot area of ​​the NFC tag is updated to "discarded" status to prevent accidental operation; the server automatically archives the complete ledger file of the device to the historical database to retain traceability evidence and complete the closed loop of the device's full life cycle management.

Images