Terminal state processing method and device, equipment and medium

Abstract

The invention relates to the technical field of data processing, can be applied to business scenes such as financial science and technology, medical health and the like, and discloses a terminal state processing method, device, equipment and medium. And collecting network use data and log data of the target terminal, and generating terminal state information in combination with processing and analysis. According to the method, screening is performed by combining the physical identifier of the terminal with the network priority, the key terminal is automatically marked, the network interaction data and the wireless log information are further acquired, and the terminal state information is generated through joint processing, so that the identification accuracy of the key terminal and the wireless network state analysis depth are improved, and the user experience is improved. And fine management and visual monitoring of important communication terminals are realized.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a terminal status processing method, device, equipment and storage medium. Background Art

[0002] Existing wireless network management technologies still lack the ability to precisely identify and differentiate critical terminal devices (especially those with high business value or service priority). Current systems generally employ a unified terminal access management mechanism, lacking strategies for independently tagging and classifying terminals with specific attributes or high-priority requirements. This makes it difficult to differentiate between critical devices in high-density deployments or complex network environments. This lack of identification directly impacts the accuracy and efficiency of subsequent information collection, network policy allocation, and fault analysis.

[0003] In the fintech sector, terminal devices often handle high-priority tasks such as transaction approval and sensitive data transmission. Failure to identify and manage these critical terminals can lead to instability in service during network congestion or signal interference, potentially leading to business interruptions and transaction failures. However, existing systems monitor only basic network parameters, failing to proactively identify these high-value terminals and lacking a policy configuration and hierarchical management mechanism based on their business importance.

[0004] In the healthcare sector, devices such as doctor workstations, surgical navigation systems, and remote imaging terminals require extremely stable and responsive network connections. Any network anomalies experienced by these devices can severely impact the continuity and safety of medical operations. However, current wireless network management systems manage these devices solely at the access status level and are unable to automatically determine their service criticality based on device attributes, making it difficult to provide timely, targeted diagnosis and alert processing.

[0005] Furthermore, existing technologies still have limitations in collecting and logging wireless network usage information. Most systems only display basic network connection status, such as signal strength or connection speed, and are unable to further explore the detailed behavior of terminals in wireless environments, such as the retransmission rate during data exchange, signal attenuation trends, and access point switching stability. This makes it difficult to identify early signs of network anomalies and support risk assessment based on behavioral patterns. Summary of the Invention

[0006] The main purpose of the present invention is to provide a terminal status processing method, device, equipment and storage medium, aiming to solve the technical problem that the existing technology cannot automatically identify and mark key terminals according to device identification and network priority, resulting in the inability to perform structured analysis and continuous monitoring of their wireless network status.

[0007] To achieve the above object, the present invention provides a terminal status processing method, comprising:

[0008] Receiving a terminal classification policy configuration, the classification policy configuration including device identification characteristics and network priority parameters;

[0009] Marking a terminal that meets the device identification feature and conforms to the network priority parameter as a target terminal;

[0010] Collecting wireless network usage information and wireless network log information of the target terminal;

[0011] The wireless network usage information and the wireless network log information are processed to generate terminal status information.

[0012] Furthermore, to achieve the above-mentioned object, the present invention provides a terminal status processing device, comprising:

[0013] A policy receiving module, configured to receive a terminal classification policy configuration, wherein the classification policy configuration includes a device identification feature and a network priority parameter;

[0014] a terminal identification module, configured to mark a terminal that meets the device identification characteristics and conforms to the network priority parameters as a target terminal;

[0015] An information collection module, configured to collect wireless network usage information and wireless network log information of the target terminal;

[0016] The status analysis module is used to process the wireless network usage information and the wireless network log information to generate terminal status information.

[0017] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a computer device, which includes a memory, a processor, and a terminal status processing program stored in the memory and executable on the processor. When the terminal status processing program is executed by the processor, the steps of the terminal status processing method described above are implemented.

[0018] Furthermore, to achieve the above-mentioned object, the present invention also provides a computer-readable storage medium, on which a terminal status processing program is stored. When the terminal status processing program is executed by a processor, the steps of the terminal status processing method described above are implemented.

[0019] Beneficial effects: The present invention relates to the field of data processing technology and can be applied to business scenarios such as financial technology and medical health. A terminal status processing method, apparatus, equipment and medium are disclosed, including: receiving a classification policy configuration including device identification characteristics and network priority parameters, marking terminals that meet the conditions as target terminals, collecting network usage data and log data of the target terminals, and generating terminal status information in combination with processing and analysis. The present invention automatically marks key terminals by combining the physical identification and network priority of the terminal for screening, and further collects network interaction data and wireless log information. Terminal status information is generated through joint processing, thereby improving the recognition accuracy of key terminals and the depth of wireless network status analysis, and realizing refined management and visual monitoring of important communication terminals. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:

[0021] Figure 1 A schematic diagram of an application environment of a terminal status processing method according to an embodiment of the present invention;

[0022] Figure 2 This is a flow chart of an embodiment of a terminal status processing method of the present invention;

[0023] Figure 3 This is a functional module diagram of a preferred embodiment of the terminal status processing device of the present invention;

[0024] Figure 4 A schematic diagram of the structure of a computer device according to an embodiment of the present invention;

[0025] Figure 5 FIG. 2 is another structural diagram of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0026] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0027] The terminal status processing method provided by the embodiment of the present invention can be applied in the following situations: Figure 1In an application environment, the user terminal communicates with the server terminal through the network. The server terminal can receive the classification policy configuration including the device identification characteristics and network priority parameters through the user terminal, mark the terminal that meets the conditions as the target terminal, collect the network usage data and log data of the target terminal, and generate terminal status information in combination with processing and analysis. The present invention combines the physical identification and network priority of the terminal for screening, automatically marks the key terminals, and further collects network interaction data and wireless log information, and generates terminal status information through joint processing, thereby improving the recognition accuracy of key terminals and the depth of wireless network status analysis, and realizing refined management and visual monitoring of important communication terminals. Among them, the user terminal can be but is not limited to various personal computers, laptops, smart phones, tablet computers and portable wearable devices. The server can be implemented with an independent server or a server cluster composed of multiple servers. The present invention is described in detail below through specific embodiments.

[0028] See also Figure 2 , Figure 2 This is a flow chart of an embodiment of a terminal status processing method provided by the present invention. It should be noted that although a logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0029] like Figure 2 As shown, the terminal status processing method proposed by the present invention includes the following steps:

[0030] S10, receiving a terminal classification policy configuration, wherein the classification policy configuration includes a device identification feature and a network priority parameter;

[0031] In this embodiment, the process of receiving the terminal classification policy configuration includes multiple associated operation links, the purpose of which is to achieve identification and classification of different terminals. The "device identification features" in the classification policy configuration are used to identify specific physical devices, which may include but are not limited to physical addresses (such as MAC addresses), device types (such as smartphones, terminal probes), and network access history information. These identification features can be derived from device access history records, terminal lists maintained in the network management platform, or manually entered identification rules.

[0032] The "Network Priority Parameter" describes the service level of network resources required by a terminal. It can cover dimensions such as bandwidth usage expectations, QoS level, roaming handover sensitivity, and log sampling frequency. This parameter reflects the importance of a device in the overall network and guides subsequent configurations such as data collection frequency and diagnostic depth.

[0033] Policy configurations can be issued from the management side or configured by operators on the policy control platform interface and saved in the database. Once the configuration is received by the system, it enters the policy parsing module. This module deconstructs the policy content, constructing a data structure containing device identification and priority fields, and forwards it to the terminal screening module to drive subsequent processes.

[0034] During implementation, the policy configuration interface is implemented through the collaboration of a front-end console and a back-end parameter processing module. The front-end interface supports entering device physical addresses and setting priority levels (such as high, medium, and low), and includes input validation logic to ensure address format validity. The back-end module receives policy requests from the front-end via a REST API and stores the policy data in the policy control database. When deployed in different network environments, the policy configuration module can also integrate with the user's existing device asset management system to automatically extract identification features, reducing the burden of manual data entry. For enterprise scenarios, a batch import function is also provided, allowing users to quickly configure policies for large numbers of devices by importing CSV or JSON format files. When processing priority parameters, the system uses a rule-based mapping mechanism to map user-defined bandwidth preferences (such as 10Mbps) to internally used priority levels (such as P1, P2, and P3) to standardize parameter standards. Furthermore, the policy supports version control, with each modification generating a change log to facilitate policy auditing and historical review.

[0035] Example: In the FinTech sector, the policy configuration module can be used to identify and mark key devices such as high-frequency trading terminals and financial system access nodes. By configuring these as high-priority target terminals, the system will perform more frequent data collection and more in-depth log analysis on them, thereby ensuring network continuity and transaction stability of the business system.

[0036] In the healthcare sector, this module can be used to prioritize critical devices within the operating room, such as wireless monitoring equipment and patient vital sign sensors. During operation, the system prioritizes the connection quality and signal path of these devices, ensuring that medical staff can promptly access device status and quickly respond to abnormalities, effectively improving safety and security in the medical environment.

[0037] This embodiment uses a policy configuration structure to bind terminal identification features to usage levels, enabling the network management system to accurately identify target terminals based on policy and assign differentiated collection and analysis paths to them, thereby achieving refined management and optimized resource scheduling. This not only improves the accuracy of target terminal identification but also lays the foundation for subsequent log collection and status display, achieving a closed-loop process from policy input to terminal behavior perception.

[0038] S20, marking a terminal that meets the device identification feature and conforms to the network priority parameter as a target terminal;

[0039] In this embodiment, terminals that meet the device identification characteristics and network priority parameters are marked as target terminals, which involves two basic processes: one is the identification and matching between devices and policies, and the other is the status labeling and structured archiving of qualified terminals.

[0040] Device identification features are derived from the set of identification parameters established during policy configuration. These features include, but are not limited to, MAC address, terminal type, access zone identifier, or historical access behavior patterns. During real-time operation, the system retrieves terminal connection information from the access control system or wireless controller to extract the physical address and related dynamic attributes of currently online terminals. The identification module uses a data dictionary or hash index structure to perform matching calculations on connected terminals, screening out those devices that meet the device identification features.

[0041] Network priority parameters are used to determine a device's scheduling priority or monitoring depth within the current network. These parameters typically include conditions such as minimum connection rate thresholds, minimum bandwidth commitments, and roaming frequency tolerances. The system constructs a current state vector for each device, collecting real-time connection rate, access point handoff history, and traffic data from the network controller. This data is then compared against the priority parameters on a per-item basis.

[0042] The system marks a device as a target endpoint only if it meets both identification characteristics and priority parameters. This marking process assigns a unique target endpoint identification field to the device, which contains information such as a matching rule summary, physical address, priority level, and first marking time. This field is used to subsequently communicate contextual identity information between the acquisition, logging, and presentation modules, ensuring that each processing flow is centered around the same device.

[0043] Furthermore, to enable multi-module linkage, the system also binds the target terminal identification field to the monitoring policy in the log collection module. This binding relationship is reflected in the configuration of different policy items such as message sampling frequency, roaming detection period, and abnormal event backtracking window for different priority levels, thereby achieving layered awareness and scheduling optimization.

[0044] When marking a target terminal, the system first retrieves information about all currently online devices from the access device table. Using SQL matching statements or a cache-based real-time indexer, it identifies a candidate set of devices that meet the policy's device identification characteristics. For each candidate set, the system sequentially evaluates whether their current connection status meets the policy's network priority parameters, such as whether the current transmission rate exceeds the specified minimum connection rate and whether the device is located within the primary service access zone. For devices that meet these criteria, the system invokes the marking service interface to generate a target terminal identification field and writes it into the terminal mapping table. This field is constructed using a UUID or a combination of a physical address and a timestamp, ensuring uniqueness for multi-dimensional analysis and log tracking. If a target terminal has been previously marked in other policies, the system supports version logging and policy override flag updates. In the policy synchronization module, this identification field is automatically passed to the log collection module and the wireless data usage monitoring module. Each module dynamically adjusts resource allocation policies based on priority level. For example, for a target terminal with priority level P1, the system increases its log sampling frequency to twice the default standard and expands the retention window for abnormal events to 24 hours to support more comprehensive retrospective analysis.

[0045] Example: In the healthcare sector, this method can be used to automatically identify physiological monitoring terminals connected to a patient monitoring platform. By configuring device identification features (such as ICU device IDs or specific MAC addresses) and high-priority levels, the system can uniquely tag and prioritize critical medical devices. After tagging, the system adjusts its log sampling frequency and exception response window to ensure that any network anomalies during monitoring are quickly detected and reported to the medical platform.

[0046] In the fintech sector, this method can be applied to identify employee terminals or server connection nodes used to access core trading systems. By configuring high-priority network policy parameters and key device identification features, the system marks these terminals as target terminals and provides them with special treatment during subsequent log analysis and connection stability testing, ensuring the stability and continuity of the trading network is not affected by fluctuations.

[0047] This embodiment combines static device identification features with dynamic network priority parameters to achieve precise screening and efficient tagging of target terminals, effectively improving the system's ability to identify key terminals and respond to policies. This highly flexible approach allows for the coordinated application of dynamic parameter adjustments and hierarchical response strategies, enabling differentiated management of high-value terminals throughout their lifecycle. The terminal identification field generated during the tagging process serves as a unified data entry point, enabling each processing module within the system to maintain contextual consistency when targeting a specific device, improving overall processing efficiency and information tracking capabilities.

[0048] S30, collecting wireless network usage information and wireless network log information of the target terminal;

[0049] In this embodiment, collecting wireless network usage information of the target terminal involves extracting a set of dynamic parameters related to wireless link interaction behavior from multiple communication layers. This process is driven by a perception policy and aggregates information with the target terminal identification field as the core. First, in the network access control layer, the system configures a dedicated message capture policy to clarify the scope of the collection object. This policy does not rely on the traditional broadcast monitoring mechanism, but instead establishes a one-to-one mapping relationship between the target terminal identification field and the physical address feature, so that the capture logic has a clear direction when executed. The priority level serves as a scheduling factor of the policy, controlling the granularity of data message processing, such as whether to enable full message body extraction or only analyze the header field.

[0050] Interaction messages represent real-time communication between wireless access points and target terminals, including handshake requests, acknowledgement responses, and service transmission messages. When collecting messages, the system not only records the message type but also simultaneously extracts its contextual structure, such as the access point identifier, channel number, message duration, and retransmission flag. These data fields provide fine-grained input for subsequent modeling of wireless link stability and latency characteristics.

[0051] During the physical layer sensing process, the system periodically monitors the terminal's wireless signal quality parameters, including but not limited to the instantaneous signal strength index (RSSI), average transmission rate (Throughput), and packet loss ratio (Packet Loss Ratio). These parameters fluctuate significantly when the terminal is roaming, congested, or experiencing interference. The system continuously collects these parameters over a set dynamic time window to avoid misjudgments caused by short-term fluctuations.

[0052] A roaming handover event is a terminal's behavior when it switches from one wireless access point to another. The system detects handover triggers in real time and simultaneously records key fields, such as the handover timestamp, the IDs of the old and new access points, and the signal strength change rate. The signal strength change rate is the difference in RSSI before and after the handover divided by the handover response time. This rate quantifies whether the handover occurred under conditions of significant signal attenuation.

[0053] All collected wireless interaction data, signal quality parameters, and roaming trajectory data must be aligned based on a unified time base. This method uses a high-precision timestamp system based on a network timing protocol (such as NTP or IEEE 1588) to map data from different sources to the same time axis, forming a structured collection of wireless network usage information. This information is then archived in chronological order to facilitate subsequent correlation analysis and state inference.

[0054] In actual system deployment, the policy scheduler first loads a packet capture policy for each target terminal. This policy includes the terminal's physical address information and its priority level as recorded in the policy management table. The system intercepts target terminal traffic through bypass mirror ports or network probe nodes and writes it to a cache queue in real time. The cache structure uses a timestamp-ordered, bidirectionally linked list to support traffic replay and tracing analysis. The signal quality sensing unit in the acquisition module periodically calls the driver interface to request signal quality metrics from the wireless controller or terminal agent. The sampling period can be dynamically adjusted based on priority. For example, high-priority terminals are sampled once per second, while low-priority terminals are sampled once every ten seconds to avoid resource waste. During the acquisition process, the average and standard deviation of multiple sampling points are calculated to form a volatility indicator. The roaming detection unit in the system triggers detection logic based on access point handover notifications or RSSI mutations. It records the event time sequence and, combined with the terminal's location and movement trajectory data, generates a roaming path structure. This structure binds access point identifiers to timestamps, enabling two-dimensional spatial visualization. Ultimately, all collected information is aligned through the time synchronization module. Each type of data is calibrated to the millisecond level by a timestamp normalization module before storage, ensuring consistency during horizontal analysis. Structured data is stored in the usage information database table, using the target terminal identification field as the primary key for subsequent status analysis and decision-making models.

[0055] Example description: In the healthcare business field, it can be applied to the management of intelligent monitoring terminals in high-dependency wards of hospitals, such as for collecting wireless interaction behaviors of key equipment such as infusion pumps, ventilators, and vital signs collectors. The system identifies terminals with monitoring priority based on the set physical address characteristics, and after accessing the network, automatically enables a high-frequency message collection strategy, continuously monitoring the handshake response delay, business data throughput rate, and confirmation message retransmission rate. When patients are transferred between wards, these terminals roam and switch wireless access points. The system synchronously records their switching events and signal strength change rates to construct a complete communication trajectory map. If the signal fluctuation rate of a device continues to be higher than the stability threshold during multiple switching, the system can generate a data stability risk mark in real time, prompting network administrators to adjust access point deployment or guide medical equipment to reposition, to avoid data interruptions that interfere with patient status judgment.

[0056] In the fintech business sector, it is suitable for managing terminals with high communication requirements, such as risk control analysis terminals, high-speed market information receiving equipment, and high-frequency trading scheduling hosts in securities companies or large banks. In the financial trading hall environment, due to the large differences in business loads between devices, the system identifies such terminals as highly sensitive nodes through device identification characteristics and priority parameters, and configures a high-granularity data capture strategy to continuously collect their handshake quality, request-response consistency, and connection stability. When the network experiences problems such as instantaneous packet loss, abnormal roaming, or fluctuating channel interference, the system uses the time alignment parameters and trajectory change data recorded in its wireless network usage information to assist in determining whether the cause is an access point configuration defect, channel collision, or malicious interference. In addition, the system can also use the collected historical data to construct a wireless quality heat map during periods of concentrated business trading, providing strategy optimization input to the IT support team and improving the stability and early warning capabilities of the trading system.

[0057] Through a message collection strategy and signal quality monitoring mechanism based on identifier field binding, this system achieves in-depth, continuous, and multi-dimensional awareness of the target terminal's wireless behavior, addressing the limited granularity and lack of temporal and spatial consistency in key terminal data collection in existing systems. Collection goes beyond static metrics to encompass connection dynamics, link quality fluctuations, and spatial behavior changes, enabling the system to accurately restore the terminal's network usage scenarios and quality status in subsequent analysis. Furthermore, a network timing protocol unifies the timing of multi-source data, laying the foundation for subsequent behavior modeling and trend prediction.

[0058] To collect wireless network log information from the target terminal, it is necessary to establish a data acquisition path that is consistent with the target terminal's identification field, ensuring that the collected data objects are completely consistent with the terminal screening results generated in the previous step. Setting a log capture strategy is a key technical foundation for this step. This strategy should include the ability to bind event type parameters, allowing the system to dynamically determine the type of logs to be collected and the sampling granularity based on the terminal's level or purpose. Event type parameters should include at least three key log sources: authentication events, address allocation events, and connection status events.

[0059] Authentication event logs usually originate from the access control layer of wireless networks. They primarily record authentication protocol versions (such as 802.1X, WPA2-Enterprise, etc.) and their authentication result status (e.g., success, failure, timeout, etc.). This information is extremely valuable in locating the cause of access failure or abnormal retry behavior. Address allocation event logs focus on the status data of the terminal in the process of obtaining an IP address, including the set value of the address lease, the reason code for address pool allocation failure, etc., which can be used to identify problems such as address conflicts and allocation saturation. Connection status event logs primarily carry key indicators such as the roaming behavior of the terminal between multiple access points, connection delay fluctuations, and signal strength changes. They are the core data basis for analyzing the stability of roaming strategies and the continuity of experience.

[0060] During the log extraction process, to ensure temporal consistency across log data, all log entries should be timestamped using a unified network timing protocol. Furthermore, by pairing the signal strength change rate before and after access point switching with roaming events in the log, a connection status trajectory with temporal semantics can be constructed. All parsed log content should be stored in a structured manner, organized into three structural units: authentication record entries, address allocation records, and connection status trajectories. These should then be integrated into a unified wireless network log information collection to ensure complete data support for subsequent state recognition algorithms.

[0061] In actual deployments, log capture policy settings can be issued from the policy configuration platform to the access controller (AC) or log agent module. For high-priority target terminals, this policy increases the granularity of log event capture and enables more frequent polling cycles. Authentication event logs can be collected by monitoring RADIUS or EAP authentication channels, with protocol fields extracted by device firmware logs or middleware parsers. Address allocation logs can be obtained by interfacing with DHCP server logs, identifying lease configurations and failure codes based on the terminal's MAC address and allocation request context. Connection status logs are typically maintained by the AC or wireless controller, recording terminal RSSI values, access point IDs, and handover times. SNMP or NetFlow protocols can be used to extract data flow information for enhanced processing, if necessary. To ensure time consistency, all logs must be synchronized with unified timestamps provided by a synchronized NTP service during the collection phase, or aligned using controller timestamps. During the structured organization phase, the three types of event logs are used to establish a terminal-oriented data structure and map it to the target terminal ID field. This allows each log entry to be indexed by the terminal, enabling subsequent query, comparison, and tracking operations.

[0062] Example: In the healthcare sector, this can be applied to mobile devices in critical areas like emergency rooms or operating rooms, such as mobile ultrasound machines and electronic medical record terminals. The system collects logs to accurately record these devices' access control authentication, whether there are delays or failures in IP allocation, and whether they frequently switch access points while on the move. For example, if an ECG monitoring terminal frequently disconnects, the administrator can use the collected authentication failure logs to identify the issue as credential failure rather than a weak signal, avoiding the misjudgment of an improper access point configuration and shortening troubleshooting time.

[0063] In the fintech sector, this system is applicable to trading terminals and risk control equipment located in business halls and trading counters. The system collects terminal authentication logs and identifies repeated authentication timeouts, identifying potential network congestion. An increased rate of address allocation failures can be used to initially determine insufficient DHCP pool capacity. If connection status logs indicate frequent terminal access point switching and significant signal strength fluctuations, the system can further analyze potential interference or physical obstructions. This log collection mechanism significantly enhances the security and service continuity of financial terminals.

[0064] This embodiment establishes a log collection mechanism tied to the target terminal, achieving complete recording of the wireless authentication process, address allocation status, and roaming behavior, providing an interpretable process foundation for subsequent terminal status analysis. In particular, when connection anomalies or roaming interruptions occur, the system can accurately restore network behavior trajectories based on structured log information and quickly locate the root cause. Leveraging a timestamp alignment mechanism, it also supports multi-source log fusion and trend analysis, significantly enhancing network visualization and self-healing capabilities.

[0065] S40: Process the wireless network usage information and the wireless network log information to generate terminal status information.

[0066] In this embodiment, wireless network usage information and wireless network log information are processed collaboratively. The core goal is to achieve the fusion of these two heterogeneous data sources in terms of time and behavioral semantics. Through indicator extraction and status classification, terminal status results are generated for refined management. Wireless network usage information primarily includes dynamic operational indicators such as the terminal's real-time signal quality, roaming behavior, and interactive message characteristics, and exhibits strong temporal and volatile characteristics. Wireless network log information, on the other hand, primarily focuses on authentication status, address allocation processes, and connection trajectories, and describes structured events related to the terminal's interaction with the network environment. To fuse these two types of data, it is first necessary to establish a time-aligned association based on a unified timestamp to form a continuous data structure for terminal behavior.

[0067] After constructing a time-aligned dataset, network quality characteristic parameters are extracted using a sliding window or event-driven mechanism. These parameters typically include the signal strength fluctuation rate, which measures the stability of the terminal's channel and can be calculated as the ratio of the standard deviation of the signal strength to the average over a certain period of time; the message retransmission rate, which reflects link congestion or bit errors and is calculated as the ratio of retransmitted messages to total transmitted messages per unit time; and the roaming path stability index, which assesses the regularity and continuity of a terminal's handoff behavior between different access points. This metric can be constructed by calculating the inverse ratio between the number of handoffs and the signal change rate before and after each handoff. These parameters form the basis for a multi-dimensional expression of network behavior quality.

[0068] After these parameters are input into the state determination model, a state label is output based on pre-set state classification rules. Classification rules can be implemented based on fixed threshold policies or a simple rule engine, categorizing terminal states into three categories: normal, warning, and fault. This state label is bound to the connection state trajectory, ensuring that connection activity in each time period has corresponding state semantics. The final output is a state-labeled terminal behavior trajectory. This trajectory not only exhibits temporal continuity but also embeds quality awareness, making it suitable for root cause location and trend monitoring.

[0069] To ensure data availability and subsequent queryability, the processing results are associated with the target terminal identification field to form a terminal status information structure. This information structure includes the target terminal identification, behavior trajectory for each time period, status level, and related indicator values. It needs to be written into the database index structure or stored in a dedicated status information module for subsequent visualization or policy engine call.

[0070] During deployment, structured wireless network usage information and wireless network log information are first loaded into a memory cache through a data linkage mechanism. Primary key indexes are aligned according to the unified network timing protocol timestamp. Terminal time series behavior units can be formed through data frame alignment or time period aggregation. The feature extraction module can be executed on edge nodes using a scripted processing approach, such as a Python data analysis component running locally on the AC controller. Pandas is used for windowed aggregation statistics of basic metrics such as volatility and retransmission rate. Roaming stability requires analysis combining multiple connection status traces with signal strength curves, potentially requiring the use of dedicated network behavior modeling functions. The status classification engine can be deployed as an embedded rule-matching module, supporting configuration-based updates to classification thresholds. For example, medical networks may have tighter thresholds, while financial networks may prioritize recovery rates after fluctuations. Classification results are returned in a JSON structure and bound to the original trajectory data to form the final state-labeled behavior trajectory. The terminal status information storage strategy supports organization by terminal partition and by status level index, ensuring rapid location of abnormal terminals or hotspots despite increasing data volumes. The database structure needs to reserve status trend fields for subsequent trend prediction or self-healing strategy matching.

[0071] Example: In healthcare scenarios, this system can be applied to critical equipment such as mobile nursing carts and bedside monitors. For example, for a continuously moving cart terminal within a ward, the system, after processing its wireless network usage information, discovered that the signal fluctuation rate was consistently greater than 0.6, and the connection status trace exhibited frequent disconnections. Combined with the authentication failure and address reallocation records in the log, the system ultimately determined a fault condition and generated a complete abnormal behavior trace. Based on this trace, the nursing management platform can dispatch technicians to optimize network configurations or activate alternative equipment to ensure uninterrupted medical care.

[0072] In FinTech scenarios, this system is suitable for monitoring the status of ATMs and mobile payment terminals. During the holiday season, the system processed network data and discovered that device message retransmission rates at multiple transaction counters continued to rise, leading to a decrease in roaming path stability. The system ultimately displayed a yellow warning status, prompting the backend to adjust access point power or load balancing policies to ensure transaction continuity. This automated processing and classification mechanism improves network stability and service continuity in financial institutions.

[0073] This embodiment integrates wireless network usage information with wireless network log information to achieve a cross-source, multi-dimensional, and time-consistent terminal status analysis system, supporting high-frequency quality perception and fault identification. Feature parameter construction provides a rich information source for status classification, and the configuration of classification rules enables the system to adapt to environmental conditions. The resulting status information contains complete behavioral context and spatiotemporal logic, providing reliable data support for subsequent display, alarm, scheduling, and other functions.

[0074] The present invention relates to the field of data processing technology and can be applied to business scenarios such as financial technology and medical health. A terminal status processing method, apparatus, equipment, and medium are disclosed, including: receiving a classification policy configuration including device identification characteristics and network priority parameters, marking terminals that meet the conditions as target terminals, collecting network usage data and log data of the target terminals, and generating terminal status information through combined processing and analysis. The present invention automatically marks key terminals by combining the physical identification and network priority of the terminal for screening, and further collects network interaction data and wireless log information. Terminal status information is generated through joint processing, thereby improving the recognition accuracy of key terminals and the depth of wireless network status analysis, and realizing refined management and visual monitoring of important communication terminals.

[0075] In one embodiment, the above step S10 includes:

[0076] S101, configuring a device identification feature input control and a network priority parameter setting control;

[0077] S102, obtaining a physical address character string submitted by the user through the device identification feature input control;

[0078] S103, capturing the bandwidth allocation weight value set by the user through the network priority parameter setting control;

[0079] S104, converting the physical address character string into a standardized device identification feature format;

[0080] S105, matching the bandwidth allocation weight value with a preset parameter mapping table to generate a network priority parameter including a parameter level;

[0081] S106: Generate a policy configuration instruction based on the device identification feature and the network priority parameter.

[0082] In this embodiment, the key to receiving the terminal classification policy configuration is to provide a user-operable interactive method for inputting key identification information for identifying the device and the importance parameters of network use. The "device identification feature" refers to the terminal device identity information with network uniqueness, which is usually based on the physical address (such as MAC address), and may also include combination fields such as device fingerprint, manufacturer ID, terminal model, etc. This type of information is used to accurately calibrate the network identity of a terminal at the physical layer and link layer. The "network priority parameter" is an abstract representation of the service sensitivity or resource scheduling weight of the terminal in the entire network. It can be expressed through parameter dimensions such as bandwidth requirements, service level, and real-time requirements, and must have certain quantification and grading capabilities for the policy engine to identify.

[0083] The purpose of configuring the device identification feature input control is to provide an interface module for users to accurately submit device identity information. This control can be a text box based on the web front end or a table interface for batch import. The "physical address string" it obtains should include complete format verification and conflict detection capabilities to prevent policy delivery failures due to format errors. The network priority parameter setting control is used to guide users in setting the terminal's network service level. It is usually represented by graphical interface components such as a weight slider, level drop-down box, or numeric input box. The captured "bandwidth allocation weight value" is used to express the terminal's expected share of network bandwidth or service priority measurement value.

[0084] In order to ensure configuration consistency and system compatibility, the physical address string entered by the user needs to be uniformly converted into a standardized device identification feature format. This format can be based on the MAC address specification of the IEEE 802.1 standard and encrypted, normalized, or a checksum suffix can be added in combination with the platform identification requirements to support subsequent automatic identification and tracking. After obtaining the network priority value, it needs to be matched with the preset parameter mapping table, which is a relationship table between predefined weight levels and network scheduling policies. For example, level 1 represents basic services, and level 5 represents real-time security services. Through the matching operation, the user-entered value is archived into a network priority parameter structure that can be recognized by the policy engine, which not only includes the level, but also encapsulates additional scheduling cycles, minimum bandwidth guarantee parameters and other complex information.

[0085] The final system generates policy configuration instructions based on device identification characteristics and network priority parameters. This instruction is a structured control instruction for the network control module, which contains the target terminal identification field and the network scheduling policy field. It can drive subsequent terminal identification, monitoring, resource allocation and other processes to ensure that the network policy of key equipment is independently issued and the exclusive management path is established.

[0086] During implementation, a policy configuration interface can be deployed on the centralized management platform. This interface connects to the backend policy configuration API via a front-end JavaScript component. The device identification feature input control supports both single-device input and batch upload modes. The backend processes the user-submitted physical address string using regular expressions and uniqueness verification logic. After validating the string, a format conversion function is called to generate a standardized identification structure. This structure can include fields such as the full MAC address, device alias, and signaling identifier, allowing for subsequent sharing with log analysis and alarm identification modules. The network priority parameter setting control can be bound to a slider control. Users can drag the slider to set a weighting level from 1 to 10. Upon receiving this value, the platform backend queries the parameter mapping table. The resulting structure contains the priority level, recommended scheduling strategy, and alarm sensitivity level. The configuration engine then constructs the policy configuration directive. This directive is encoded in JSON or YAML and transmitted to the controller via the API or written to the policy database for centralized distribution. This mechanism also supports the definition of policy templates. Administrators can pre-create configuration templates for multiple device types based on service types and distribute them to a large number of end devices with a single click, significantly improving the efficiency and consistency of policy distribution.

[0087] This embodiment establishes a dual-dimensional policy configuration system based on device identification features and network priority parameters, enabling accurate identification and policy-aware scheduling of key terminals, providing a structured data entry for subsequent wireless network information collection, log analysis, and status assessment. Standardized processing and a policy mapping table mechanism ensure that diverse user input can be uniformly identified and parsed by the platform, enhancing the robustness of terminal classification policies. The resulting policy configuration instructions enable on-demand allocation of network resources and controllable guidance of terminal behavior, laying the foundation for differentiated terminal management based on identity and service value.

[0088] In one embodiment, the above step S20 includes:

[0089] S201, verifying whether the physical address feature of the terminal device matches the address whitelist in the device identification feature, and if so, adding the terminal device to a candidate device set;

[0090] S202, detecting whether the current connection rate of each terminal device in the candidate device set reaches the minimum connection rate threshold in the network priority parameter, and if so, marking the terminal device as a target terminal;

[0091] S203, creating a target terminal identification field for each target terminal in the device management database;

[0092] S204: Bind the target terminal identification field to the monitoring policy of the log analysis module.

[0093] In this embodiment, the core of marking the target terminal is to build a screening mechanism determined by static identification matching and dynamic performance evaluation to ensure that the selected terminal has both a clear device identity and meets the business carrying requirements of actual operating capabilities. The address whitelist in the device identification feature is a standardized terminal identity set generated by the policy configuration step, which contains legally authorized physical addresses and their corresponding attributes. The physical address characteristics of the terminal device are usually obtained in real time through the access control module, network authentication service or data acquisition interface. The logic of the verification operation is based on the address whitelist to determine whether a terminal has the identity legitimacy to be included in the high-priority management system. If it matches, a candidate device set is formed and enters the next stage of screening.

[0094] The connection rate is an important dynamic indicator that reflects the real-time network capabilities of a device. The current connection rate is typically monitored by access points, terminal network cards, or network controllers, and represents the data transmission capacity per unit time. The minimum connection rate threshold preset in the network priority parameters is the basic service quality threshold set in the policy configuration. Checking whether this rate reaches the threshold ensures that even if the identification is legitimate, if the device's connection status is unstable or the physical environment lacks service assurance capabilities, it will not be selected as a target terminal. This detection process typically involves continuous sampling and evaluation to avoid screening errors caused by instantaneous network fluctuations. Devices that meet the conditions will be officially marked as target terminals.

[0095] The target terminal identification field is the management identifier assigned to the selected terminal at the database layer, which includes two key fields: device identity and policy level. The physical address feature is used to index the terminal entity, and the priority level is used to mark its service assurance level and policy call path. This identification field is not only stored in the device management database, but also bound to the log analysis module through the indexing mechanism to form a key entry field in the log processing flow. The monitoring policy configuration of the log analysis module includes two core parameters: message sampling frequency and roaming detection period. The former defines the sampling accuracy of the system for the terminal's interactive data packets during the monitoring process, and the latter determines the time period for the system to detect the connection switching behavior of the terminal. Both must be consistent with the corresponding relationship of the network priority parameters to achieve a technical closed loop from policy configuration to behavior collection.

[0096] In actual deployments, the system backend obtains the physical address information of all terminals in real time through the network access control module and compares it against a whitelist of device identification features. This comparison is accomplished using a hash index and rule-matching engine, enabling rapid identification in high-concurrency environments. Successfully matched devices are added to the candidate device set. Subsequently, the system accesses the access point controller or wireless controller interface to obtain the current connection rate of each candidate device. This rate is the average data transmission rate over the past few seconds and is updated periodically by the system. The system compares this rate with the threshold set in the network priority parameters. If the rate exceeds the threshold, the device is marked as a target terminal. A target terminal identification field is created or updated in the device management database for each terminal, and its physical address, identification time, priority level, and historical status are recorded in a standard format. The system also synchronizes this identification field with the monitoring configuration of the log analysis module. This module assigns different message sampling frequencies based on device priority level, for example, sampling every 1 second for high-priority devices and every 5 seconds for low-priority devices. The roaming detection period determines how often the system monitors access point change events, such as every 5 seconds for high-priority devices. Policy parameters can be dynamically adjusted through the policy synchronization engine and visualized in the management console.

[0097] This embodiment establishes a dual-dimensional screening mechanism based on device identity legitimacy and network status capabilities, effectively identifying and screening target terminals with high importance and network availability, establishing precise targets for subsequent network resource allocation, log collection, and behavior analysis. The structured design of the target terminal identification field enables the network management system to implement independent scheduling paths for critical devices while ensuring parameter inheritance and execution consistency between the policy and log analysis modules, thereby enhancing the overall network's ability to manage and protect high-value terminals.

[0098] In one embodiment, in step S30, collecting the wireless network usage information of the target terminal includes:

[0099] S301, setting a message capture strategy;

[0100] S302, intercepting interactive messages between the target terminal and the wireless access point according to the message capture strategy;

[0101] S303, collecting wireless signal quality parameters of the target terminal within a preset time window;

[0102] S304, recording roaming handover events of the target terminal between adjacent wireless access points, and generating roaming trajectory data including a handover timestamp, a target access point identifier, and a signal strength change rate;

[0103] S305: Synchronize and align the interaction message, signal quality parameter, and roaming trajectory data with a time reference based on a network timing protocol to generate a structured wireless network usage information set.

[0104] In this embodiment, the wireless network usage information of the target terminal is collected to obtain behavioral data from two dimensions: the network communication layer and the link quality layer, in order to establish a data foundation to support diagnosis and optimization analysis. Setting a message capture strategy is a prerequisite for this process. The physical address characteristics and priority levels contained in the message capture strategy are the core elements of the target terminal identification field generated in the previous stage. The physical address characteristics serve as a unique identifier for the device identity and are used to accurately identify the corresponding source and target in the message; the priority level is used to adjust the collection frequency and the scope of policy execution. For example, high-priority devices correspond to more frequent message interception and data collection windows.

[0105] Interaction messages directly convey wireless terminal network usage behavior. Handshake request messages are used to establish the initial connection state, service data messages carry service instructions and response payloads, and confirmation response messages provide feedback on the reliability of the communication link. Including these three types of messages in the collection scope fully covers the access initialization, service transmission, and response processes, improving the ability to restore network behavior.

[0106] Wireless signal quality parameters are link layer status indicators extracted from device communication behavior within a specified time window. The instantaneous signal strength value reflects the quality of the wireless channel at a given moment, the average transmission rate indicates the effective data transmission capacity per unit time, and the packet loss rate ratio measures data stability. These metrics require unified sampling and alignment in conjunction with a high-precision timing system.

[0107] A roaming handover event reflects the connection behavior of a terminal migrating from one access point to another. Recording this behavior requires capturing the handover timestamp, the target access point ID, and the rate of change in signal strength before and after the handover. This allows for assessing whether the handover was caused by signal degradation, a change in access policy, or an active device reselection. This information is crucial for analyzing roaming stability and regional coverage quality.

[0108] Finally, to ensure data consistency and relevance, collected interaction messages, signal quality parameters, and roaming trajectory data must be synchronized according to a time base based on a network timing protocol (such as NTP or PTP). This time base provides system-level timestamp specifications, ensuring that multi-source data has a unified time coordinate, enabling high-precision time series analysis. After time alignment, the relevant data is organized in a structured format, ultimately forming a collection of wireless network usage information, which provides input for subsequent state determination and behavior modeling.

[0109] In actual deployments, the system loads a packet capture policy through the wireless controller or edge probe node. This policy filters the target terminal's physical address and dynamically adjusts the collection window based on its priority level. For high-priority targets, the collection system uses a short trigger cycle and full frame retention, while for low-priority targets, it uses a longer sampling interval and partial header parsing. The system intercepts three types of interactive messages from the target terminal in the access switch or AP link. Handshake messages are identified based on DHCP and EAPOL signaling, service data packets are identified by port number and QoS tagging, and acknowledgment response messages are identified based on signaling confirmation or TCP ACK structures. Collected messages are stored in a high-speed cache, tagged with the device identification field, and then enter the data preprocessing process. To collect signal quality, the system initiates a scheduled scanning thread that reads the RSSI value between the terminal and the AP at regular intervals within a preset time window. Quality parameters are generated by combining rate negotiation results with packet loss statistics. Packet loss rate statistics are calculated by combining the reception confirmation rate and retransmission counts, all mapped to a unified timeline. Roaming trajectory collection is completed by the access controller. Whenever a terminal's access point changes, the system generates a roaming event record, including the average RSSI values ​​before and after the switch, the switch timestamp, and the access point identifier. This record is then standardized and time-aligned. After collection, the system precisely aligns all data with the timestamps generated by the network timing protocol. This process utilizes a built-in time synchronization module, generating two identifiers for each type of data: the event time and the collection time. Time offsets are calculated for correction. This ultimately creates a structured collection of wireless network usage information, including fields such as data type, source terminal identifier, timestamp, interaction type and content summary, signal parameter values, and roaming event fields. This information is then uniformly encoded and fed into the analysis module.

[0110] This embodiment completely collects all key interactions, signal states, and access switching behaviors of the target terminal in the wireless network, and combines it with the network timing protocol to achieve time series alignment. This can form a wireless network usage information set with behavioral chain integrity, time coordinate consistency, and fine-grained data content, providing a reliable data foundation for subsequent state modeling, anomaly detection, and policy optimization.

[0111] In one embodiment, in step S30, collecting the wireless network log information of the target terminal includes:

[0112] S306, setting a log capture strategy, wherein the log capture strategy includes a log event type parameter bound to a target terminal identification field;

[0113] S307, intercepting the wireless authentication event log, address allocation event log, and connection status event log of the target terminal according to the log event type parameter;

[0114] S308, parsing the protocol version identifier and authentication result status in the wireless authentication event log, and generating an authentication record entry including a network timing protocol timestamp;

[0115] S309, extracting the address lease parameter and the address allocation failure reason code from the address allocation event log to generate a structured address allocation record;

[0116] S310, correlating and analyzing the roaming handover events in the connection status event log with the signal strength change rates of adjacent access points to generate a connection status track with a time stamp;

[0117] S311: Integrate the authentication record entries, address allocation records, and connection status traces into a wireless network log information set.

[0118] In this embodiment, the purpose of collecting wireless network log information from the target terminal is to obtain a full-link behavior record of the device during network access, capturing event logs covering the entire process of connection establishment, address configuration, and connection status maintenance. The log capture policy is a prerequisite for the log collection process and contains a log event type parameter bound to the target terminal identification field. The log event type parameter is used to define the range of events that the system needs to intercept, including authentication events, address allocation events, and connection status events, ensuring that data collection has clear boundaries and structure.

[0119] Wireless authentication event logs typically record the authentication interactions that occur when a device accesses the network, including processes such as the EAP protocol, 802.1X interactions, or MAC authentication. The goal of parsing these logs is to extract the protocol version identifier, which can be used to identify the authentication mechanism (e.g., WPA2, WPA3), and the authentication result status, which indicates whether the authentication succeeded or failed. To enable cross-source alignment and behavioral modeling, the logs must be timestamped using a unified network timing protocol, such as the precise time generated by NTP or PTP.

[0120] The address allocation event log records the entire process of a terminal acquiring an address through DHCP or IPv6 SLAAC. Address lease parameters are extracted to infer the connection duration window and to identify allocation failure cause codes to locate allocation anomalies or address pool exhaustion. This processing generates a structured address allocation record, enabling subsequent analysis to reconstruct the device's IP layer behavior.

[0121] The connection status event log focuses on events that occur while a device maintains a connection, including roaming handovers, access point reselection, and packet loss recovery. The log extracts the time at which the terminal roams and the rate of change in signal strength at adjacent access points. Correlation analysis is performed to determine whether the handover is caused by signal degradation or policy adjustments. This analysis generates a time-stamped connection status track, recording the device's connection continuity and status fluctuations along the spatial path.

[0122] Authentication record entries, structured address allocation records, and connection status traces are all structured output items of independent event types. Finally, these three types of information must be integrated under the same terminal identification field dimension to generate a collection of wireless network log information. The integration process must ensure timestamp alignment, field standardization, and behavioral continuity, providing a unified data source for subsequent network status modeling and anomaly location.

[0123] During the initialization phase of log collection, the system loads a log capture policy based on the target terminal identification field. This policy pre-sets a whitelist of event types, instructing the system to only capture authentication events, address allocation events, and connection status events. This policy is loaded into the access controller, log agent node, or edge monitoring module. Authentication event logs are parsed by the protocol parser module, which supports mainstream authentication protocols such as EAP, RADIUS, and 802.1X. Authentication interaction packets are identified in the logs, and the protocol version field (such as 802.1X version number or EAP type) and final status field (such as success or failure) are extracted. The timestamp generated by the network timing module is appended to form an authentication record entry. Address allocation logs are processed by the DHCP interaction capture module, which extracts the "lease time" field as the address lease parameter and generates the allocation failure reason field by matching the error code field (such as DHCPNAK or timeout response). The collection process must be matched with the terminal interaction log to ensure that the allocation event coincides with the authentication behavior time window. The connection status log collection module monitors AP-side handover events, identifies the roaming start and target access points based on the terminal MAC address, and reads the average RSSI change rate between the two points. The analysis module calculates the handover time point and change rate indicators to generate connection status trajectory records. The record structure includes fields such as terminal identification, start and target AP identification, change rate, and time stamp. The three types of log data are uniformly entered into the log integration module, indexed and aggregated by terminal identification, event time, and event type to form a structured wireless network log information collection. The collection is stored in the structured log storage area or the streaming analysis engine to provide input for subsequent status identification, policy optimization, and alarm deduction.

[0124] This embodiment uses a log capture strategy based on the terminal identification field and focuses on three key events: authentication, address allocation, and connection status. This builds a complete log data chain, recording the entire process from access and link establishment, address configuration, to status maintenance. This not only ensures the consistency and continuity of data collection, but also enhances the analyzability and retrospective value of the logs through event parsing and time-stamping mechanisms. The integrated wireless network log information collection becomes the core support resource for diagnostic analysis and behavioral modeling, significantly improving the system's responsiveness in anomaly detection, connection stability assessment, and policy optimization.

[0125] In one embodiment, the above step S40 includes:

[0126] S401, performing time series correlation on the wireless signal quality parameters in the wireless network usage information and the authentication record entries in the wireless network log information to generate time-aligned correlation data;

[0127] S402, extracting network quality characteristic parameters from the associated data;

[0128] S403, classifying the network quality characteristic parameters according to a preset status determination strategy to generate hierarchical status identifiers including normal status, warning status, and fault status;

[0129] S404: Performing spatiotemporal association between the hierarchical status identifier and the connection status track in the wireless network log information to generate a terminal behavior track with a status mark;

[0130] S405: Associate and store the terminal behavior trace with the target terminal identification field corresponding to the target terminal to generate terminal status information.

[0131] In this embodiment, wireless network usage information and wireless network log information respectively record terminal operational indicators and connection event data. These two types of information come from different data sources and have a natural correspondence on the timeline. Therefore, time series correlation between these two types of information is key to identifying behavioral patterns. Wireless signal quality parameters include time-varying characteristics such as instantaneous RSSI, average rate, and packet loss ratio. These are collected in real time from packet capture or network card status. Authentication record entries represent session initiation information between the terminal and the network control plane, including the time of successful authentication and the protocol type.

[0132] The core of time series correlation lies in introducing a unified time base to synchronize data across the physical and control layers. This synchronization is typically achieved using the NTP / PTP protocol timing mechanism. Records from different sources are sorted and windowed using timestamps to generate a time-aligned, correlated data set. Each data point in this set consists of both physical quality parameters and control event fields, forming a multidimensional data structure.

[0133] The goal of extracting network quality characteristic parameters from this set is to form quantitative evaluation indicators. Signal strength fluctuation measures channel stability, calculated as the ratio of the instantaneous RSSI standard deviation to its mean. The packet retransmission rate, calculated by capturing the ratio of MAC layer retransmissions to the total number of packets sent, characterizes link reliability. The roaming path stability index, calculated by combining the number of access point switches per unit time with the RSSI attenuation gradient before and after the switch, reflects connection continuity.

[0134] The status determination strategy is a set of multidimensional classification rules based on these characteristic parameters, used to classify the terminal status within each time period into three categories: normal, warning, or faulty. The core of the strategy is typically based on threshold determination or a decision tree model. For example, a fluctuation rate exceeding 0.5 or a retransmission rate exceeding 15% is considered a fault.

[0135] Hierarchical state identification essentially labels the terminal state at each time slice. This identification is then matched with the time coordinates and access point spatial coordinates in the connection state trajectory to form a terminal behavior trajectory that is jointly expressed in time and space. This behavior trajectory is no longer just static data such as a spatial path or event list, but a dynamic description of the state evolution process, supporting visualization and behavior prediction analysis.

[0136] Ultimately, the terminal behavior trajectory, as a refined representation of the terminal's state, is bound to the target terminal's identification field, establishing a one-to-one correspondence in the state storage module to form terminal state information. This state information becomes the basis for subsequent optimization strategy recommendations, fault alarms, connection mode adjustments, and other operations.

[0137] During the processing phase, the system first calls the timing module to normalize the timestamps of the collected wireless signal quality parameters and authentication record entries. This process uses the unified NTP time of the master control server as the alignment reference. The local collection time of all data records is converted to UTC format and uniformly sorted. The time alignment algorithm uses a sliding time window mechanism to search for signal quality records corresponding to authentication records within a preset time tolerance (e.g., ±200ms), achieving one-to-one or one-to-many matching. After matching, a composite dataset containing the fields {timestamp, RSSI, TX rate, loss rate, auth_type, auth_status} is generated. The feature extraction module performs rolling statistics on this composite dataset, calculating the signal strength fluctuation rate, packet retransmission rate, and roaming stability index within each terminal's continuous sampling window. Each feature parameter is output as a structured field and appended to the data record. The status determination module classifies the data according to a policy library. The policy library can be configured with threshold rules by the administrator or trained by a machine learning model (such as random forest or naive Bayes). A sequence of status labels, such as [normal, warning, normal, faulty], is generated on the timeline of each terminal. Connection status traces are extracted from log information. Each trace contains a time series and an AP ID sequence. The ID sequence is indexed and matched against the trace by timestamp to generate a trace status extension table, which is used to construct behavior graphs and visualize state changes. Behavior trajectory data is stored in JSON or time-based graph format, indexed using the endpoint ID field as the primary key. The system writes this data to the status information database or uses it in the heatmap engine.

[0138] This embodiment integrates wireless network usage information with wireless network log information on a timeline and introduces multi-dimensional feature parameters for state modeling. This effectively restores the terminal's behavior in the network environment, accurately characterizing its connection stability and channel quality fluctuations. It also integrates contextual information and behavioral indicators, making terminal state information determinable, traceable, and interpretable. The resulting state information output supports not only real-time monitoring but also historical behavior attribution and pattern recognition, enhancing the management system's responsiveness in VIP terminal identification, assurance, and policy optimization.

[0139] In one embodiment, after the above step S40, the method further includes:

[0140] S501, parsing the terminal status information into a network quality score, a real-time connection status code, and a historical roaming path;

[0141] S502: Generate a signal quality heat map based on the network quality score, where the signal quality heat map is a signal strength distribution map covering physical locations;

[0142] S503, generating a connection state sequence diagram based on the real-time connection state code, wherein the connection state sequence diagram maps hierarchical state identifiers in time sequence;

[0143] S504: Generate a roaming path trajectory map based on the historical roaming path, and superimpose the path coordinates on the wireless access point topology map on the roaming path trajectory map;

[0144] S505, configuring a status alarm triggering strategy, wherein the status alarm triggering strategy includes a fault state duration detection strategy and an alarm level mapping relationship;

[0145] S506, according to the fault state duration detection strategy, when it is detected that the real-time connection status code is determined to be in a fault state within multiple consecutive detection cycles, triggering corresponding multi-level alarm prompts according to the alarm level mapping relationship;

[0146] S507: Update the duration interval corresponding to the fault state to the connection state timing diagram with a visual warning mark.

[0147] In this embodiment, terminal status information, as a structured data result, needs to be further parsed into multiple sub-items for display and monitoring, including network quality score, real-time connection status code, and historical roaming path. This parsing process is a process of data semantic reconstruction, that is, breaking down the comprehensive structure output by the evaluation model into indicator fields that can be recognized and rendered by the front-end visualization system. The network quality score refers to a normalized evaluation score generated based on network quality characteristic parameters, which can be set to 0 to 100 and is used to quickly reflect the terminal's comprehensive connection quality in the current cycle; the real-time connection status code is a classification number output in real time by the status determination logic, which is used to describe whether the terminal is in normal, warning, or fault status in a given cycle; the historical roaming path is reconstructed chronologically from the access point switching records in the terminal's behavior trajectory to describe its spatial movement process.

[0148] Using network quality scores to generate a signal quality heatmap maps terminal behavior results into a spatially perceptible signal environment map. This map uses the target physical area as a base, combines the scores of terminals at different locations, and performs interpolation calculations to output a signal strength distribution map. This heatmap can be used to identify weak signal areas or interference hotspots and assist in deploying optimization solutions.

[0149] Based on the real-time connection status code, a connection status time series chart is generated. This chart uses a timeline as its primary structure, visually annotating the terminal's connection status at each time slice. Common formats include color-coded time bars, status trend line charts, or continuous category bar charts. The key benefit of this chart is that it helps administrators quickly identify abnormal connection trends over a specific period of time and determine whether they represent persistent failures.

[0150] Generating a roaming path trajectory map from historical roaming paths visualizes the terminal's access behavior in physical space. This map, superimposed on the wireless access point topology map, displays the sequence of AP nodes visited by the terminal and their chronological order. It can further annotate handover intensity changes or failure points, supporting roaming strategy optimization.

[0151] The status alarm triggering strategy is an exception management logic at the operation and maintenance level. Its core is to perform fault status detection based on the time series data of the connection status code. When the terminal status code is marked as "faulty" for multiple consecutive time periods (such as 5 consecutive minutes of failure), the system will trigger the corresponding prompt strategy based on the preset alarm level mapping relationship. The alarm level can be set to multiple levels, such as mild, moderate, and severe, and different levels correspond to different notification strategies, such as UI pop-up windows, email notifications, and automatic allocation of network resources.

[0152] Finally, the duration of the alarm triggering and the alarm level will be marked in the connection status timing diagram through graphic components (such as red segments on the timeline, warning icons, etc.).

[0153] In one specific implementation, the system first extracts fields from structured terminal status information through a backend parsing module to generate a network score, current status code, and roaming path sequence. The score is calculated using a weighted formula: Q = α·(1-volatility) + β·(1-retransmission rate) + γ·stability index, where α, β, and γ are configuration parameters. A signal quality heat map, based on the binding relationship between terminal and location information, uses the IDW interpolation algorithm to plot the score density distribution on a geographic boundary map. The front-end dynamically generates layers using WebGL or Canvas rendering. A connection status time series diagram is generated from a time series array of terminal status codes. Each time slice corresponds to a status level, and the front-end uses color coding, such as green (normal), orange (warning), and red (fault), to fill in the segments. The trajectory map construction process extracts access point node IDs and coordinates from the behavioral trajectory data, connects them chronologically into a path, and annotates the RSSI value changes at each point. If a handover is accompanied by a significant RSSI drop or occurs repeatedly within a short period of time, a warning symbol is added to the trajectory. The alarm triggering strategy sets a periodic window in the backend (for example, N consecutive fault states within 3 minutes). It then performs a sliding window check based on the status code sequence. When a rule is matched, the alarm level mapping table is searched and the response level is returned. Alarm graphical feedback is provided by overlaying interval markers on the sequence diagram and adding a warning prompt box to the terminal monitoring dashboard. The alarm content is synchronously written to the event database and bound to the terminal identification field for subsequent statistics.

[0154] To ensure data upload quality for multiple vital signs monitoring terminals in the ICU network management system of a tertiary hospital, the administrator entered the MAC address prefixes of these devices and assigned them high-priority bandwidth weights through the configuration interface, forming policy configuration instructions. These device characteristics were used to match online devices, and the system selected terminals that matched the address whitelist and had connection speeds above a preset threshold as target terminals. The system then collected network usage information for these target terminals, capturing their handshake messages and service data packets from the wireless controller in real time and measuring signal strength, packet loss ratio, and average speed over short periods. Furthermore, the roaming detection module recorded the time these devices switched wireless access points within the ward, the target AP ID, and the signal gradient, thereby building a collection of wireless network usage information. Based on this information, the system then activated the log analysis module, configured a log collection policy, and captured authentication, address allocation, and connection status logs generated by the target terminals. The system analyzed protocol versions and failure reasons, and further generated structured authentication records, address event records, and connection status traces. The system then time-aligned this usage information with the log information, extracted characteristic values ​​such as volatility, retransmission rate, and stability, and classified them into normal, warning, or fault states based on pre-set rules. During analysis, the system detected that the two devices experienced multiple rapid handoffs between 5:00 AM and 5:15 AM, resulting in a significant drop in their scores. This abnormal state was clearly marked in the connection status trace and written to the status information storage area using the target terminal identification field. The status information was then parsed and used to construct the display interface. The signal score was used to render a heat map overlaid on the ICU floor plan, clearly highlighting the problem hotspots. The time sequence diagram generated from the status code showed continuous red status during this period; the path diagram showed the terminal repeatedly switching between access points three times. Because the alarm policy was set to "three consecutive cycles of failure trigger a high-level alarm," the system triggered a notification, automatically overlaying a red highlight on the diagram, and notifying network maintenance personnel through the hospital's internal IM system to investigate the AP deployment blind spot. This process ensured stable communication for critical medical equipment.

[0155] In a securities firm's VIP trading area, to ensure stable operation of high-net-worth clients' trading terminals, the IT department configured a MAC address list for certain terminals through the policy interface and configured high-bandwidth priority parameters for them. Upon receiving the policy configuration, the system immediately matched online terminals on the network, identifying those with stable connection speeds and matching identification characteristics as target terminals. These terminals were automatically marked and a corresponding identification field was generated. The system then captured service packets and sampled signal quality for these target terminals. During a high-frequency trading morning session, the system detected such devices repeatedly switching between a specific access point and a backup AP. The captured interaction packets revealed a decreased handshake success rate. Roaming trajectory data showed a signal change rate exceeding 25%, which was recorded in the wireless usage data. Using the log collection policy, the system further captured authentication events and address allocation failures during this period, noting multiple DHCP rejection events. Time series alignment of usage information and log data was performed to extract feature values. A retransmission rate of 20% and a stability index less than 0.4 triggered a "failure" status. This status information is sent to the display module for processing. Terminals with a score of only 42 are displayed as dark red areas in the heat map, and the status code sequence diagram shows continuous red segments. The trajectory diagram shows that the terminal repeatedly switches between three APs, and the movement path is extremely complex. Since the policy configuration sets "two consecutive cycles of failures are judged as intermediate alarms", the system marks the abnormal period on the visual interface and pops up a graphic alarm notification, prompting the need to check the current AP bandwidth congestion or DFS channel interference problem. After viewing the diagram, the operation and maintenance personnel immediately switched the terminal access priority configuration and adjusted the AP to a static channel configuration through the access controller. The problem was alleviated within 30 minutes. The entire system realizes real-time monitoring, automatic diagnosis and precise intervention of high-value customer network behavior, greatly improving the service experience and network stability.

[0156] This embodiment parses terminal status information into structured data items for display and graphically represents network quality, connection continuity, and behavior paths. This allows the management system to intuitively reflect the evolution of the terminal's network status in time and space. Combined with a status alarm trigger mechanism, the system can proactively respond to long-term or continuous network issues and provide multi-level prompts, improving fault location efficiency and operational response capabilities.

[0157] In one embodiment, a terminal status processing device is provided, which corresponds one-to-one to the terminal status processing method in the above embodiment. Figure 3 , Figure 3 This is a functional module diagram of a preferred embodiment of the terminal status processing device of the present invention. It includes a policy receiving module 10, a terminal identification module 20, an information collection module 30, and a status analysis module 40. The functional modules are described in detail as follows:

[0158] A policy receiving module 10 is configured to receive a terminal classification policy configuration, wherein the classification policy configuration includes a device identification feature and a network priority parameter;

[0159] The terminal identification module 20 is used to mark a terminal that meets the device identification characteristics and meets the network priority parameters as a target terminal;

[0160] An information collection module 30 is configured to collect wireless network usage information and wireless network log information of the target terminal;

[0161] The status analysis module 40 is configured to process the wireless network usage information and the wireless network log information to generate terminal status information.

[0162] In one embodiment, the policy receiving module 10 is specifically configured to:

[0163] Configure the device identification feature input controls and network priority parameter setting controls;

[0164] Obtaining a physical address string submitted by the user through the device identification feature input control;

[0165] Capturing the bandwidth allocation weight value set by the user through the network priority parameter setting control;

[0166] Converting the physical address character string into a standardized device identification feature format;

[0167] Matching the bandwidth allocation weight value with a preset parameter mapping table to generate a network priority parameter including a parameter level;

[0168] A policy configuration instruction is generated based on the device identification characteristics and the network priority parameter.

[0169] In one embodiment, the terminal identification module 20 is specifically configured to:

[0170] Verify whether the physical address characteristics of the terminal device match the address whitelist in the device identification characteristics, and if so, add the terminal device to the candidate device set;

[0171] Detecting whether the current connection rate of each terminal device in the candidate device set reaches the minimum connection rate threshold in the network priority parameter, and when reaching the minimum connection rate threshold, marking the terminal device as a target terminal;

[0172] Creating a target terminal identification field for each target terminal in a device management database;

[0173] The target terminal identification field is bound to the monitoring strategy of the log analysis module.

[0174] In one embodiment, the information collection module 30 is specifically configured to:

[0175] Set up packet capture policies;

[0176] intercepting interaction messages between the target terminal and the wireless access point according to the message capture strategy;

[0177] Collect wireless signal quality parameters of the target terminal within a preset time window;

[0178] Record the roaming handover events of the target terminal between adjacent wireless access points and generate roaming trajectory data including the handover timestamp, target access point identifier, and signal strength change rate;

[0179] The interaction messages, signal quality parameters and roaming trajectory data are synchronized with a time reference based on a network timing protocol to generate a structured wireless network usage information set.

[0180] In one embodiment, the information collection module 30 is specifically configured to:

[0181] Setting a log capture strategy, wherein the log capture strategy includes a log event type parameter bound to a target terminal identification field;

[0182] intercepting the wireless authentication event log, address allocation event log, and connection status event log of the target terminal according to the log event type parameter;

[0183] Parsing the protocol version identifier and authentication result status in the wireless authentication event log to generate an authentication record entry including a network timing protocol timestamp;

[0184] Extracting the address lease parameter and the address allocation failure reason code from the address allocation event log to generate a structured address allocation record;

[0185] Correlate and analyze the roaming handover events in the connection status event log with the signal strength change rate of adjacent access points to generate a connection status track with a time stamp;

[0186] The authentication record entries, address allocation records and connection status traces are integrated into a wireless network log information set.

[0187] In one embodiment, the status analysis module 40 is specifically configured to:

[0188] Performing time series correlation on the wireless signal quality parameters in the wireless network usage information and the authentication record entries in the wireless network log information to generate time-aligned correlation data;

[0189] extracting network quality characteristic parameters from the associated data;

[0190] Classify the network quality characteristic parameters according to a preset status determination strategy to generate hierarchical status identification including normal status, warning status and fault status;

[0191] Performing spatiotemporal association between the hierarchical status identifier and the connection status track in the wireless network log information to generate a terminal behavior track with a status mark;

[0192] The terminal behavior track is associated with a target terminal identification field corresponding to the target terminal and stored to generate terminal status information.

[0193] In one embodiment, the status analysis module 40 is specifically configured to:

[0194] Parsing the terminal status information into a network quality score, a real-time connection status code, and a historical roaming path;

[0195] generating a signal quality heat map based on the network quality score, wherein the signal quality heat map is a signal strength distribution map covering physical locations;

[0196] generating a connection state sequence diagram based on the real-time connection state code, wherein the connection state sequence diagram maps hierarchical state identifiers in time series;

[0197] generating a roaming path trajectory map based on the historical roaming path, wherein the roaming path trajectory map overlays and displays path coordinates on the wireless access point topology map;

[0198] Configure a status alarm triggering strategy, wherein the status alarm triggering strategy includes a fault status duration detection strategy and an alarm level mapping relationship;

[0199] According to the fault state duration detection strategy, when it is detected that the real-time connection status code is determined to be in a fault state within multiple consecutive detection cycles, a corresponding multi-level alarm prompt is triggered according to the alarm level mapping relationship;

[0200] The duration interval corresponding to the fault state is updated to the connection state timing diagram with a visual warning mark.

[0201] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 4As shown. The computer device includes a processor, memory, network interface and database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external user terminal via a network connection. When the computer program is executed by the processor, it implements the functions or steps of a terminal status processing method service side.

[0202] In one embodiment, a computer device is provided. The computer device may be a user terminal, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, memory, network interface, display screen and input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements the functions or steps on the user side of a terminal status processing method.

[0203] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are performed:

[0204] Receiving a terminal classification policy configuration, the classification policy configuration including device identification characteristics and network priority parameters;

[0205] Marking a terminal that meets the device identification feature and conforms to the network priority parameter as a target terminal;

[0206] Collecting wireless network usage information and wireless network log information of the target terminal;

[0207] The wireless network usage information and the wireless network log information are processed to generate terminal status information.

[0208] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0209] Receiving a terminal classification policy configuration, the classification policy configuration including device identification characteristics and network priority parameters;

[0210] Marking a terminal that meets the device identification feature and conforms to the network priority parameter as a target terminal;

[0211] Collecting wireless network usage information and wireless network log information of the target terminal;

[0212] The wireless network usage information and the wireless network log information are processed to generate terminal status information.

[0213] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can be found in the relevant descriptions of the server side and the user side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0214] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0215] Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0216] It should be noted that if any software tools or components other than those of the Company appear in the embodiments of this application, they are merely for illustration and do not represent actual use. The above embodiments are intended only to illustrate the technical solutions of the present invention, not to limit them. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some of the technical features therein with equivalents. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the scope of protection of the present invention.

Claims

1. A terminal status processing method, characterized in that: The following steps are involved: Receiving a terminal classification policy configuration, the classification policy configuration including device identification characteristics and network priority parameters; Marking a terminal that meets the device identification feature and conforms to the network priority parameter as a target terminal; Collecting wireless network usage information and wireless network log information of the target terminal; The wireless network usage information and the wireless network log information are processed to generate terminal status information.

2. The terminal status processing method according to claim 1, wherein: Receive terminal classification policy configuration, the classification policy configuration including device identification characteristics and network priority parameters, including: Configure the device identification feature input controls and network priority parameter setting controls; Obtaining a physical address string submitted by the user through the device identification feature input control; Capturing the bandwidth allocation weight value set by the user through the network priority parameter setting control; Converting the physical address character string into a standardized device identification feature format; Matching the bandwidth allocation weight value with a preset parameter mapping table to generate a network priority parameter including a parameter level; A policy configuration instruction is generated based on the device identification characteristics and the network priority parameter.

3. The terminal status processing method according to claim 1, wherein: Marking a terminal that meets the device identification feature and the network priority parameter as a target terminal includes: Verify whether the physical address characteristics of the terminal device match the address whitelist in the device identification characteristics, and if so, add the terminal device to the candidate device set; Detecting whether the current connection rate of each terminal device in the candidate device set reaches the minimum connection rate threshold in the network priority parameter, and when reaching the minimum connection rate threshold, marking the terminal device as a target terminal; Creating a target terminal identification field for each target terminal in a device management database; The target terminal identification field is bound to the monitoring strategy of the log analysis module.

4. The terminal status processing method according to claim 1, wherein: Collecting wireless network usage information of the target terminal, including: Set up packet capture policies; intercepting interaction messages between the target terminal and the wireless access point according to the message capture strategy; Collect wireless signal quality parameters of the target terminal within a preset time window; Record the roaming handover events of the target terminal between adjacent wireless access points and generate roaming trajectory data including the handover timestamp, target access point identifier, and signal strength change rate; The interaction messages, signal quality parameters and roaming trajectory data are synchronized with a time reference based on a network timing protocol to generate a structured wireless network usage information set.

5. The terminal status processing method according to claim 1, wherein: Collecting wireless network log information of the target terminal includes: Setting a log capture strategy, wherein the log capture strategy includes a log event type parameter bound to a target terminal identification field; intercepting the wireless authentication event log, address allocation event log, and connection status event log of the target terminal according to the log event type parameter; Parsing the protocol version identifier and authentication result status in the wireless authentication event log to generate an authentication record entry including a network timing protocol timestamp; Extracting the address lease parameter and the address allocation failure reason code from the address allocation event log to generate a structured address allocation record; Correlate and analyze the roaming handover events in the connection status event log with the signal strength change rate of adjacent access points to generate a connection status track with a time stamp; The authentication record entries, address allocation records and connection status traces are integrated into a wireless network log information set.

6. The terminal status processing method according to claim 1, wherein: Processing the wireless network usage information and the wireless network log information to generate terminal status information includes: Performing time series correlation on the wireless signal quality parameters in the wireless network usage information and the authentication record entries in the wireless network log information to generate time-aligned correlation data; extracting network quality characteristic parameters from the associated data; Classify the network quality characteristic parameters according to a preset status determination strategy to generate hierarchical status identification including normal status, warning status and fault status; Performing spatiotemporal association between the hierarchical status identifier and the connection status track in the wireless network log information to generate a terminal behavior track with a status mark; The terminal behavior track is associated with a target terminal identification field corresponding to the target terminal and stored to generate terminal status information.

7. The terminal status processing method according to claim 1, wherein: After processing the wireless network usage information and the wireless network log information to generate terminal status information, the method further includes: Parsing the terminal status information into a network quality score, a real-time connection status code, and a historical roaming path; generating a signal quality heat map based on the network quality score, wherein the signal quality heat map is a signal strength distribution map covering physical locations; generating a connection state sequence diagram based on the real-time connection state code, wherein the connection state sequence diagram maps hierarchical state identifiers in time series; generating a roaming path trajectory map based on the historical roaming path, wherein the roaming path trajectory map overlays and displays path coordinates on the wireless access point topology map; Configure a status alarm triggering strategy, wherein the status alarm triggering strategy includes a fault status duration detection strategy and an alarm level mapping relationship; According to the fault state duration detection strategy, when it is detected that the real-time connection status code is determined to be in a fault state within multiple consecutive detection cycles, a corresponding multi-level alarm prompt is triggered according to the alarm level mapping relationship; The duration interval corresponding to the fault state is updated to the connection state timing diagram with a visual warning mark.

8. A terminal status processing device, characterized in that: The terminal status processing device includes: A policy receiving module, configured to receive a terminal classification policy configuration, wherein the classification policy configuration includes a device identification feature and a network priority parameter; a terminal identification module, configured to mark a terminal that meets the device identification characteristics and conforms to the network priority parameters as a target terminal; An information collection module, configured to collect wireless network usage information and wireless network log information of the target terminal; The status analysis module is used to process the wireless network usage information and the wireless network log information to generate terminal status information.

9. A computer device, characterized in that: The computer device includes a memory, a processor, and a terminal status processing program stored in the memory and executable on the processor. When the terminal status processing program is executed by the processor, the steps of the terminal status processing method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that The storage medium stores a terminal status processing program, which, when executed by a processor, implements the steps of the terminal status processing method according to any one of claims 1 to 7.

Images