Station management method and device, storage medium and computer program product

Abstract

The invention discloses a station management method and device, a storage medium and a computer program product, and relates to the field of enterprise resource management, and the method comprises the steps: obtaining first mapping relation data between a network port and an employee; initiating a station checking task, and determining binding relation data between the employees and the stations through the station checking task; calling employee state data, and generating corresponding relation data among the employees, the stations and the network ports based on the first mapping relation data, the binding relation data and the employee state data; and managing the stations according to the corresponding relation data and the employee state data. Through data integration and an automatic process, existing network infrastructure and management system data of an enterprise are directly reused, and hardware deployment and manual intervention cost are avoided, so that precise management of station resources is realized under the conditions of low cost and no hardware dependence.

Description

Technical Field

[0001] The present application relates to the field of enterprise resource management technology, and in particular to a workstation management method, device, storage medium, and computer program product. Background Art

[0002] In modern office environments, the dynamic allocation and management of workstation resources is key to improving space utilization. Currently, workstation management primarily relies on manual registration, the deployment of physical sensors at workstations to monitor usage in real time, and proactive employee operations to reserve and change workstations. However, the use of hardware sensors for monitoring requires significant hardware investment and management costs. Manual registration and proactive employee operations for reserving and changing workstations also lead to data lags, high labor costs, and the risk of human error, resulting in inaccurate data.

[0003] Therefore, how to achieve accurate management of workstation resources at low cost and without hardware dependence has become a technical problem that needs to be solved urgently in this application.

[0004] The above content is only used to assist in understanding the technical solution of this application and does not constitute an admission that the above content is prior art. Summary of the Invention

[0005] The main purpose of this application is to provide a workstation management method, device, storage medium and computer program product, aiming to solve the problem of accurate management of workstation resources under low cost and hardware-free conditions.

[0006] To achieve the above objectives, the present application proposes a workstation management method, which includes:

[0007] Obtain the first mapping relationship data between the network port and the employee;

[0008] Initiate a workstation inventory task, and determine the binding relationship data between the employee and the workstation through the workstation inventory task;

[0009] Calling employee status data, and generating corresponding relationship data between the employee, the workstation, and the network port based on the first mapping relationship data, the binding relationship data, and the employee status data;

[0010] The workstations are managed according to the corresponding relationship data and the employee status data.

[0011] In one embodiment, the step of obtaining first mapping relationship data between network ports and employees includes:

[0012] Obtaining second mapping relationship data between employee identity information, terminal MAC address, and terminal IP address from the enterprise intranet access control software;

[0013] capturing network traffic data in real time by using a network packet capture technology, and parsing third mapping relationship data between the network port and the terminal IP address based on the network traffic data;

[0014] The second mapping relationship data and the third mapping relationship data are matched and integrated with each other using the terminal IP address as the association key to generate the first mapping relationship data between the network port and the employee.

[0015] In one embodiment, the step of calling the employee status data and generating the corresponding relationship data between the employee, the workstation, and the network port based on the first mapping relationship data, the binding relationship data, and the employee status data includes:

[0016] Calling employee status data, and performing standardization processing on the first mapping relationship data, the binding relationship data, and the employee status data;

[0017] Associating the standardized first mapping relationship data, the binding relationship data, and the employee status data to generate initial corresponding relationship data between the employee, the workstation, and the network port;

[0018] Abnormal data in the initial correspondence data is eliminated through an abnormality detection mechanism to obtain correspondence data between the employee, the workstation, and the network port.

[0019] In one embodiment, the step of managing the workstation according to the correspondence data and the employee status data includes:

[0020] If the employee status data is on-the-job but not bound to a workstation, the associated workstation corresponding to the current network port used by the employee is queried according to the corresponding relationship data, and a workstation binding reminder is sent based on the associated workstation to update the corresponding relationship data.

[0021] In one embodiment, the step of managing the workstation according to the correspondence data and the employee status data includes:

[0022] If the employee status data indicates that the employee is on-the-job and has a bound workstation, query the network port information corresponding to the bound workstation according to the corresponding relationship data, and determine whether the network port information is consistent with the current network port used by the employee;

[0023] If the network port information is inconsistent with the current network port used by the employee, the current network port information used by the employee is queried according to the corresponding relationship data, and a workstation confirmation reminder is sent based on the current network port information to update the corresponding relationship data.

[0024] In one embodiment, the step of managing the workstation according to the correspondence data and the employee status data includes:

[0025] establishing an employee behavior pattern database based on the employee status data;

[0026] When the employee status data changes, a behavior pattern matching the current employee status is retrieved from the employee behavior pattern database, and the workstation is adjusted according to the behavior pattern and the corresponding relationship data.

[0027] In one embodiment, after the step of managing the workstation according to the correspondence data and the employee status data, the step further includes:

[0028] Monitoring the usage and network connection status of the workstation based on the corresponding relationship data, and establishing a workstation usage efficiency evaluation model based on the usage and the network connection status;

[0029] Identifying idle workstations or inefficiently used workstations using the workstation utilization efficiency evaluation model;

[0030] Initiate an automatic cleanup process for the idle workstations and generate a list of idle workstations;

[0031] The inefficiency reasons of the inefficiently used workstations are analyzed in combination with the employee status data and the employee behavior pattern database, and the workstations are adjusted according to the inefficiency reasons.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a workstation management device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the workstation management method as described above.

[0033] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium. A computer program is stored on the storage medium, and when the computer program is executed by the processor, the steps of the workstation management method described above are implemented.

[0034] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of the workstation management method described above are implemented.

[0035] One or more technical solutions proposed in this application have at least the following technical effects:

[0036] The system obtains first mapping data between network ports and employees; initiates a workstation inventory task, and uses the workstation inventory task to determine employee-workstation binding data; retrieves employee status data and, based on the first mapping data, the binding data, and the employee status data, generates correspondence data between employees, workstations, and network ports; and manages workstations based on the correspondence data and the employee status data. First, the system directly reuses the first mapping data, eliminating the need for additional hardware investment and relying solely on software-level data collection and processing. Second, the system triggers a workstation inventory task periodically or based on an event to determine employee-workstation binding data, replacing traditional workstation status monitoring methods that rely on physical sensors or manual registration. Furthermore, the system retrieves employee status data, combines the first mapping data with the binding data, generates employee-workstation-network port correspondence data, and performs differentiated operations based on the employee status data. Through software-driven data integration and automated processes, the system directly reuses existing enterprise network infrastructure and management system data, eliminating hardware deployment and manual intervention costs. This enables precise management of workstation resources at low cost and without hardware dependencies. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0038] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0039] Figure 1 A flowchart of the first embodiment of the workstation management method provided in this application;

[0040] Figure 2 A flow chart of a second embodiment of the workstation management method provided in this application;

[0041] Figure 3 A flowchart of a feasible implementation method of the third embodiment of the workstation management method provided in this application;

[0042] Figure 4 This is a schematic diagram of the module structure of the workstation management device according to an embodiment of the present application;

[0043] Figure 5 This is a schematic diagram of the equipment structure of the hardware operating environment involved in the workstation management method in the embodiment of the present application.

[0044] The purpose, features and advantages of this application will be further explained with reference to the accompanying drawings in conjunction with the embodiments. DETAILED DESCRIPTION

[0045] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.

[0046] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0047] The main solution of the embodiment of the present application is: obtaining the first mapping relationship data between the network port and the employee; initiating a workstation inventory task, and determining the binding relationship data between the employee and the workstation through the workstation inventory task; calling the employee status data, and generating the corresponding relationship data between the employee, the workstation, and the network port based on the first mapping relationship data, the binding relationship data, and the employee status data; and managing the workstation according to the corresponding relationship data and the employee status data.

[0048] In this embodiment, for ease of description, the following description is made with the workstation management system as the execution entity.

[0049] The embodiments of this application take into account that in modern office scenarios, the dynamic allocation and management of workstation resources is key to improving space utilization. Currently, workstation management relies primarily on manual registration, the deployment of physical sensors at workstations to monitor usage status in real time, and employees actively reserving and changing workstations. However, the use of hardware sensors for monitoring requires high hardware investment and management costs; manual registration and employees actively reserving and changing workstations are subject to data update lags, high labor costs, and the risk of human error, resulting in inaccurate data.

[0050] Therefore, the present application provides a solution that obtains first mapping relationship data between network ports and employees; initiates a workstation inventory task, and determines the binding relationship data between employees and workstations through the workstation inventory task; calls employee status data and generates corresponding relationship data between employees, workstations, and network ports based on the first mapping relationship data, the binding relationship data, and the employee status data; and manages workstations based on the corresponding relationship data and the employee status data. First, the first mapping relationship data is directly reused, eliminating the need for additional hardware investment and relying solely on data collection and processing at the software level. Second, the workstation inventory task is triggered periodically or by an event, and the binding relationship data between employees and workstations is determined through the workstation inventory task, replacing traditional workstation status monitoring methods that rely on physical sensors or manual registration. Furthermore, the employee status data is called, combined with the first mapping relationship data and the binding relationship data to generate employee-workstation-network port corresponding relationship data, and differentiated operations are performed based on the employee status data. Through software-driven data integration and automated processes, the enterprise's existing network infrastructure and management system data are directly reused, avoiding the costs of hardware deployment and manual intervention, thereby achieving precise management of workstation resources at low cost and without hardware dependence.

[0051] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, mobile phone, etc., or an electronic device capable of implementing the above functions, a workstation management system, etc. The following uses the workstation management system as an example to illustrate this embodiment and the following embodiments.

[0052] Based on this, the embodiment of the present application provides a workstation management method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the workstation management method of this application.

[0053] In this embodiment, the workstation management method includes steps S10 to S40:

[0054] Step S10, obtaining first mapping relationship data between network ports and employees;

[0055] First-level mapping data refers to a dataset directly linking network ports to employees, formed by integrating the binding relationships between employees and terminal devices within the enterprise, as well as the real-time connection relationships between network ports and IP addresses. This first-level mapping data provides the foundation for subsequent workstation binding and management. By dynamically tracking the network connection locations (network ports) of employee terminal devices, it achieves consistent mapping between workstations and employees' actual usage status, replacing traditional solutions that rely on hardware sensors or manual registration.

[0056] Specifically, in a feasible implementation method, the mapping relationship between network ports and employees can be obtained from the enterprise IT system through an API interface or database query, including but not limited to: extracting the associated data between employees and terminal devices from LDAP (Lightweight Directory Access Protocol, access and maintenance distributed directory service protocol); using SDN (Software-Defined Networking) controller to collect dynamic mapping of network ports and IP addresses.

[0057] For example, the currently assigned IP address 192.168.1.10 for employee A's (employee number 001) laptop (MAC: 00-1A-2B-3C-4D) is obtained through an API interface. Using SDN, the correspondence between each physical network port (e.g., switch port number) and the IP address of the currently connected terminal device is recorded: the device IP address connected to switch Port 1 is 192.168.1.10. Using the IP address as the association key, the two types of data are matched to form a first mapping relationship data similar to: network port identifier (e.g., Port 1) → employee identifier (employee number 001). The stored fields include: network port physical location, employee ID, MAC address, IP address, timestamp, etc.

[0058] Step S20: Initiate a workstation inventory task, and determine the binding relationship data between the employee and the workstation through the workstation inventory task;

[0059] Automatically initiate workstation resource inventory tasks based on preset cycles or trigger events; the workstation management system extracts the binding records between current employees and workstations (such as workstation numbers and binding time), generates employee→workstation binding relationship data, and cleans redundant or invalid binding records through logical verification (workstation number validity, employee status).

[0060] It should be noted that the trigger conditions for initiating a workstation inventory task include: network topology change events such as the addition of new switch ports, changes in the connection status of employee terminal devices such as IP address reallocation, or preset resource utilization thresholds that trigger capacity expansion inventory when the workstation occupancy rate exceeds 90%.

[0061] Step S30: calling employee status data, and generating corresponding relationship data between the employee, the workstation, and the network port based on the first mapping relationship data, the binding relationship data, and the employee status data;

[0062] Employee status data (e.g., hired, employed, or resigned) from the human resources management system is retrieved. The first mapping relationship data (network port → employee) is associated with the binding relationship data (employee → workstation), generating the corresponding relationship data for employee → workstation → network port. This corresponding relationship data is dynamically updated based on employee status: if the employee status is "hired," a free workstation is automatically assigned and a binding is established; if the employee status is "resigned," the previously bound workstation is released and marked as available.

[0063] Furthermore, when generating corresponding relationship data, the following rules are introduced: if the same network port is associated with multiple employees, the last active terminal device is matched first; if the employee is not bound to a workstation, the preset default workstation area is assigned according to his department or role.

[0064] Step S40: managing the workstations according to the corresponding relationship data and the employee status data.

[0065] Workstation management includes: matching an employee's currently used network port with their assigned workstation in real time; automatically triggering a workstation change process and updating the corresponding data if a mismatch is detected between the network port used by the employee and the assigned workstation (e.g., when the employee changes workstations); recovering workstations released by departing employees and reallocating them to other employees; or, sending workstation binding / change notifications to employees via corporate communication tools; and automatically releasing abnormal status (e.g., workstations that have been unused for an extended period) and generating management reports.

[0066] This embodiment provides a workstation management method that obtains first mapping relationship data between network ports and employees; initiates a workstation inventory task, and determines employee-workstation binding relationship data through the workstation inventory task; retrieves employee status data and generates corresponding relationship data between employees, workstations, and network ports based on the first mapping relationship data, the binding relationship data, and the employee status data; and manages workstations based on the corresponding relationship data and the employee status data. First, the first mapping relationship data is directly reused, eliminating the need for additional hardware investment and relying solely on software-level data collection and processing. Second, the workstation inventory task is triggered periodically or by an event, and the binding relationship data between employees and workstations is determined through the workstation inventory task, replacing traditional workstation status monitoring methods that rely on physical sensors or manual registration. Furthermore, the employee status data is retrieved, combined with the first mapping relationship data and the binding relationship data to generate employee-workstation-network port corresponding relationship data, and differentiated operations are performed based on the employee status data. Through software-driven data integration and automated processes, the existing enterprise network infrastructure and management system data are directly reused, avoiding hardware deployment and manual intervention costs, thereby achieving precise management of workstation resources at low cost and without hardware dependence.

[0067] In a feasible implementation, step S10 may include steps S11 to S14:

[0068] Step S11, obtaining second mapping relationship data between employee identity information, terminal MAC address, and terminal IP address from the enterprise intranet access control software;

[0069] Through the API of the enterprise intranet access control software (such as Active Directory or LDAP directory services), employee identity information (employee number, name), terminal device MAC address, and dynamically assigned IP address are extracted to form a second mapping relationship dataset: employee → MAC → IP address. For example, if employee A (employee number 001)'s laptop (MAC: 00-1A-2B-3C-4D) currently has an IP address of 192.168.1.10, the record {employee number 001, 00-1A-2B-3C-4D, 192.168.1.10} is generated.

[0070] It should be noted that the second mapping relationship data can be obtained from a variety of sources, including but not limited to: an enterprise identity management system and a terminal device management platform.

[0071] Step S12, capturing network traffic data in real time by using a network packet capture technology, and parsing third mapping relationship data between the network port and the terminal IP address based on the network traffic data;

[0072] Use standard network protocols to capture network traffic data in real time, parse the switch or router port configuration information, and record the third-party mapping relationship data from network port to IP address. For example, if the device IP address connected to switch Port 1 is 192.168.1.10, the record {Port1,192.168.1.10} will be generated.

[0073] It should be noted that the data update frequency can be dynamically adjusted based on network load (e.g., once per second during peak hours and once every five seconds during off-peak hours). Network packet capture technology can adapt to the proprietary protocols of different network equipment manufacturers and achieve a unified data format through standardized middleware.

[0074] Step S13: using the terminal IP address as an association key, matching and integrating the second mapping relationship data with the third mapping relationship data to generate first mapping relationship data between the network port and the employee;

[0075] Using the IP address as the association key, the second mapping relationship data (employee → MAC → IP) is matched with the third mapping relationship data (network port → IP). If the IP address uniquely matches (e.g., 192.168.1.10 exists in both the second and third data sets), the first mapping relationship data (network port → employee) {Port1, employee number 001} is generated. If there is an IP address conflict (e.g., multiple devices share the same IP address), an exception alarm is triggered and the conflict record is temporarily saved for administrators to resolve. Invalid IP addresses (unassigned or reserved addresses) are automatically eliminated during the data integration process.

[0076] Furthermore, priority rules are introduced for IP conflict scenarios: based on the last active timestamp of the terminal device, the record of the most recently connected device is retained; if the conflict persists for a timeout, the old binding is automatically released and the administrator is notified.

[0077] Furthermore, the generated first mapping relationship data is written into a terminal device management data warehouse. The terminal device management data warehouse may be a relational database such as MySQL or a distributed storage system such as Hadoop. The storage fields of the first mapping relationship data may include: network port identifier, employee ID, MAC address, IP address, and timestamp. A real-time data access interface is provided via a RESTful API or a message queue Kafka. The first mapping relationship data can be retrieved from the terminal device management data warehouse by accessing the real-time data interface.

[0078] Based on the first embodiment of the present application, the second embodiment of the present application is proposed. In the second embodiment of the present application, the same or similar contents as those of the above-mentioned first embodiment can be referred to the above introduction and will not be repeated hereafter.

[0079] On this basis, please refer to Figure 2 , Figure 2 A flow chart of the second embodiment of the workstation management method provided in this application.

[0080] In this embodiment, the step S30 of calling the employee status data and generating the corresponding relationship data between the employee, the workstation, and the network port based on the first mapping relationship data, the binding relationship data, and the employee status data may include steps S31 to S33:

[0081] Step S31: calling employee status data and performing standardization processing on the first mapping relationship data, the binding relationship data, and the employee status data;

[0082] Call the employee status data (such as joining, employment, and resignation) of the human resources management system, and standardize the following three types of data: First, mapping relationship data: unify the network port identification format, such as standardizing "Port1" to "SwitchA-Port1", and clean up invalid records including unregistered employee IDs or abandoned network ports; binding relationship data: convert the workstation number format, for example, map "workstation A-101" to "ZoneA-101", and eliminate expired binding records including the binding of resigned employees' workstations; employee status data: unify the status labels into preset enumeration values, such as 0 for joining, 1 for employment, and 2 for resignation.

[0083] It should be noted that standardization processing can adapt to different data formats including XML, JSON, and CSV, and achieve format conversion through a universal parser; cleaning rules support custom configuration, such as validating the workstation number format through regular expressions.

[0084] Step S32, associating the standardized first mapping relationship data, the binding relationship data, and the employee status data to generate initial corresponding relationship data between the employee, the workstation, and the network port;

[0085] With employee ID as the primary key, the three standardized data types are associated: the first mapping relationship data (network port → employee) is combined with the binding relationship data (employee → workstation) to generate a preliminary employee → workstation → network port mapping table, i.e., the initial corresponding relationship data; the validity of the mapping table records is dynamically marked according to the employee status data, for example, the records of employees who have left the company are marked as "to be released".

[0086] Furthermore, in addition to employee IDs, department IDs or role tags can be introduced as auxiliary association keys, for example, assigning adjacent workstations to employees in the same department; and support the coexistence of multiple versions of data, such as retaining historical binding records for auditing.

[0087] Step S33: Abnormal data in the initial correspondence data is eliminated through an abnormality detection mechanism to obtain correspondence data between the employee, the workstation, and the network port.

[0088] The following anomaly detection mechanism is used to remove abnormal data from the initial correspondence data and obtain the correspondence data between employees, workstations, and network ports:

[0089] If multiple active employees are associated with the same network port, for example, if network port SwitchA-Port1 is bound to both employees A and B, the last active record is retained and the remaining records are marked as conflicts. If the workstation ID does not exist in the workstation management system, an alarm is triggered and the corresponding record is removed. If the employee status is "Resigned" but still has a valid workstation bound to it, the workstation is automatically released and the data is updated.

[0090] Furthermore, conflict thresholds or alarm levels can be defined in configuration files to enable dynamic loading of anomaly detection rules; alternatively, anomaly detection models can be trained based on historical data, introducing deep learning mechanisms to identify potential data contradictions.

[0091] Specifically, in a feasible implementation of this embodiment, step S30 may include steps S301 to S302:

[0092] Step S301: calling employee status data and adding timestamps to the first mapping relationship data, the binding relationship data, and the employee status data respectively;

[0093] Employee status (joining, current, and leaving) is obtained in real time from the human resources management system, with each record appended with a status update timestamp. The real-time binding relationship between network ports and employees is extracted from the terminal device management data warehouse, with each record appended with a network port connection timestamp. Current workstation binding records are obtained from the workstation management system, with each record appended with a binding operation timestamp. Timestamps are used to clarify data timeliness, avoid data conflicts caused by asynchronous updates, and identify delayed or expired data based on timestamps.

[0094] If there are multiple timestamps for the same data source (for example, the network port connection time is inconsistent with the IP allocation time), the latest timestamp shall prevail. An alarm shall be triggered for data whose time deviation exceeds a threshold (such as 5 minutes). For example, if the network port connection time is inconsistent with the workstation binding time, it shall be marked as "pending manual verification".

[0095] Step S302 : defining node types and node relationships in a graph database according to the timestamps, and generating the corresponding relationship data based on the node types and node relationships.

[0096] Node types include: employee nodes, with attributes such as employee ID, name, status, and status update timestamp; workstation nodes, with attributes such as workstation number, region, and binding operation timestamp; and network port nodes, with attributes such as network port ID, switch IP address, and connection timestamp. Node relationships include: employee → workstation, with attributes such as binding start and end time; and workstation → network port, with attributes such as connection start and end time. Node types and relationships are dynamically written into the graph database to visualize corresponding relationship data.

[0097] In this embodiment, through standardization processing, the data formats of different sources are unified, avoiding matching errors caused by data format confusion; multi-source data are associated with employee ID as the primary key to generate initial corresponding relationship data, integrate scattered system information, and form a complete "employee-workstation-network port" mapping relationship; introduce an anomaly detection mechanism to automatically identify and eliminate abnormal data through preset rules (such as network port conflicts, invalid workstations, and inconsistent status), thereby improving the real-time and credibility of the data and ensuring that the corresponding relationship data finally output can be directly used for automated management.

[0098] Based on the first embodiment and / or the second embodiment of the present application, the third embodiment of the present application is proposed. In the third embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction and will not be repeated hereafter.

[0099] In a feasible implementation of this embodiment, the employee status data includes the employee's on-the-job workstation bound to the employee, and the step S40 of managing the workstation according to the corresponding relationship data and the employee status data may include step A41:

[0100] Step A41: If the employee status data indicates that the employee is on-the-job but not bound to a workstation, the associated workstation corresponding to the current network port used by the employee is queried according to the corresponding relationship data, and a workstation binding reminder is sent based on the associated workstation to update the corresponding relationship data.

[0101] When an employee's status is "on duty but not bound to a workstation", the workstation management system queries the network port ID currently used by the employee from the corresponding relationship data, and determines whether the network port has been associated with other workstations by matching the network port ID with the workstation binding record.

[0102] For example, if the current network port has an associated workstation, a workstation confirmation request is sent to the employee, and the workstation is automatically bound or administrator intervention is triggered based on the feedback result of the workstation confirmation request. For example, if Port1 is bound to workstation ZoneA-101, a workstation confirmation request is sent to the employee through the enterprise communication tool (such as enterprise WeChat, email system), and the workstation confirmation request content includes: current network port identification, associated workstation information, confirmation or feedback options. Based on the employee's feedback result on the workstation confirmation request, the workstation is automatically bound or administrator intervention is triggered. Specifically, if the employee's feedback result is confirmed to be correct, the workstation is automatically bound to the employee and the corresponding relationship data is updated; if the employee's feedback result is incorrect, the administrator intervention process is triggered, and the administrator verifies the network port configuration or workstation allocation logic and re-executes the binding.

[0103] Correspondingly, if the current network port is not associated with a workstation, a workstation binding reminder is sent to the employee, and the corresponding relationship data is updated: If the current network port is not associated with a workstation, a workstation binding reminder is sent to the employee, including a list of available workstations and binding instructions. The corresponding relationship data is updated based on the employee's response to the workstation binding reminder. For example, if the employee selects workstation ZoneB-201, a binding relationship is automatically established and the corresponding relationship data is generated. If no response is received from the employee to the workstation binding reminder, the reminder is periodically resent until the binding is completed or a timeout is triggered.

[0104] It should be noted that the list of available workstations can recommend adjacent workstations based on the employee's department or project team, or dynamically allocate workstations based on workstation utilization rates, giving priority to workstations in areas with low utilization rates.

[0105] In this embodiment, if the employee status data indicates that the employee is currently employed and on-duty, but not bound to a workstation, the corresponding workstation is queried based on the corresponding relationship data. The system automatically determines the association between the network port and the workstation, significantly reducing the need for manual inspection and workstation assignment. An employee confirmation mechanism based on feedback from workstation confirmation requests, as well as proactive notifications to employees who are not bound to a workstation, prevents data confusion, avoids idle workstations or duplicate occupation, and improves the accuracy of workstation management.

[0106] In another feasible implementation of this embodiment, the employee status data includes employee resignation, and the step S40 of managing the workstation according to the correspondence data and the employee status data may include step S41:

[0107] Step S41: If the employee status is employee resignation, the workstation corresponding to the resigned employee is determined and released according to the corresponding relationship data.

[0108] Obtain employee status data from the human resources management system, identify the list of employees whose status is marked as "resigned", and query the workstation information currently bound to the resigned employee based on the corresponding relationship data (employee → workstation → network port).

[0109] If a valid binding record exists, such as if Employee A is bound to workstation ZoneA-101, the workstation release process is executed. This includes: unbinding Employee A from workstation ZoneA-101; marking workstation ZoneA-101 as "Available" and updating the workstation management system database; and clearing Employee A's associated records from the corresponding relationship data. If no binding record is found, such as if Employee A has never been bound to a workstation, the release process is skipped and a log is recorded.

[0110] Furthermore, after a workstation is released, the following operations are automatically performed: the available workstation is added to the pending allocation queue, with priority allocated to new employees or departments with urgent needs; a workstation release report is generated, including the release time, workstation number, and historical usage history, and pushed to the administrator. The workstation release process is integrated with the IT asset management system: terminal devices (such as computers) of departing employees are automatically recovered and their status updated; and if a workstation is equipped with specialized equipment (such as monitors and phones), a device inspection task is triggered to ensure that it can be reassigned.

[0111] In this implementation, real-time detection of the binding between employee resignation status and workstations prevents idle resources caused by manual omissions. Data associated with departing employees is cleared to prevent subsequent allocation conflicts. When an employee's status indicates resignation, the workstation release process is automatically triggered, avoiding issues such as resource recovery delays, data inconsistencies, and management loopholes caused by manual operations.

[0112] refer to Figure 3 , Figure 3 A flowchart of a feasible implementation of the third embodiment of the workstation management method provided in this application. In another feasible implementation of this embodiment, the step S40 of managing the workstations according to the correspondence data and the employee status data may include steps B41 to B42:

[0113] Step B41: If the employee status data indicates that the employee is on-the-job and has a bound workstation, query the network port information corresponding to the bound workstation based on the corresponding relationship data, and determine whether the network port information is consistent with the current network port used by the employee;

[0114] If the employee status data is on-the-job and bound to a workstation, then the corresponding relationship data is used to query whether the workstation bound to the employee has the corresponding network port information, and determine whether the network port information is consistent with the network port currently used by the employee. If they are consistent, the original binding relationship and corresponding relationship data are maintained.

[0115] Step B42: If the network port information is inconsistent with the current network port used by the employee, query the current network port information used by the employee according to the corresponding relationship data, send a workstation confirmation reminder based on the current network port information, and update the corresponding relationship data;

[0116] If the network port bound to the workstation is inconsistent with the network port used by the employee, it is necessary to query the current network port information of the employee's network port PortA based on the corresponding relationship data, and further query the workstation A corresponding to the network port PortA used by the employee. A workstation confirmation reminder is sent to the employee through the enterprise communication tool, including the original workstation, the new workstation, and a confirmation option. The operation is performed based on the employee's feedback on the workstation confirmation reminder: If the employee confirms the change, the corresponding relationship data is updated, the network port PortB bound to the workstation is unbound from the employee, and the current network port PortA used by the employee and the corresponding workstation A are automatically bound; if the employee refuses the change, the administrator is triggered to verify the network port configuration or workstation allocation logic, and re-execute the verification after correction.

[0117] Correspondingly, if the current network port PortA used by the employee does not have a corresponding workstation A, a workstation binding reminder is sent to the employee, the bound workstation and network port PortB are unbound, and the network port information of network port A is added to the bound workstation.

[0118] In another feasible implementation of this embodiment, the step S40 of managing the workstation according to the correspondence data and the employee status data may include steps C41 to C42:

[0119] Step C41, establishing an employee behavior pattern database based on the employee status data;

[0120] First, collect workstation usage data, movement trajectory data, and device connection data. Among them, workstation usage data refers to the daily workstation usage time, frequency of use, and single usage duration of employees; movement trajectory data refers to the employee switching records across workstations / areas (such as the frequency of visits to conference rooms and collaboration areas); device connection data refers to the network connection time and active IP address of employee terminal devices (such as laptops).

[0121] After cleaning and standardizing the collected data and removing invalid records, we construct an employee behavior model. This model includes residence patterns (identifying employees' permanent workstations), mobility patterns (analyzing employees' cross-regional collaboration habits), and device usage patterns (counting the periods of network activity on employees' devices). The behavior data is stored in an employee behavior database, which includes fields such as the employee's anonymous identifier (hashed employee ID), residence location, movement trajectory tag, device activity period tag, and last update timestamp.

[0122] Step C42: When the employee status data changes, a behavior pattern matching the current employee status is retrieved from the employee behavior pattern database, and the workstation is adjusted according to the behavior pattern and the corresponding relationship data.

[0123] Changes in employee status data are not limited to employee resignations and new hires. They also include scenarios such as long-term remote work, transfers to new departments, and project team disbanding, all of which can affect an employee's use of their workstation. When an employee's status data changes, the system matches the current employee's behavior pattern from the behavior pattern database and adjusts the workstation based on the behavior pattern and corresponding relationship data. For example, if an employee's historical stay mode was "fixed workstation" but their current status is "remote work," their bound workstation is automatically released and marked as a "flexible workstation" for temporary use. If an employee transfers to a new department and their mobility patterns indicate frequent cross-regional collaboration, the system recommends an unoccupied workstation in the adjacent new department's workstation cluster and sends a binding suggestion.

[0124] In this embodiment, it is determined whether the bound workstation has corresponding network port information to ensure that each bound workstation is associated with valid network port information, thereby avoiding workstation allocation errors caused by missing data; new workstations are identified and change requests are sent, and the corresponding relationship data is automatically updated after employee confirmation to release the original workstation resources. When inconsistencies are found, the data is actively corrected to ensure that the workstations, network ports and employees' actual usage status are strictly synchronized, thereby solving the problems of inefficient manual operations, data lags and resource waste in traditional workstation management.

[0125] Based on the above embodiments of the present application, a fourth embodiment of the present application is proposed. In the fourth embodiment of the present application, the same or similar contents as those of the above embodiments can be referred to the above introduction and will not be repeated hereafter.

[0126] In this embodiment, the step S40 of managing the workstation according to the corresponding relationship data and the employee status data further includes steps S50 to S80:

[0127] Step S50: monitoring the usage and network connection status of the workstation based on the corresponding relationship data, and establishing a workstation usage efficiency evaluation model based on the usage and the network connection status;

[0128] Based on the aforementioned correspondence data (employee → workstation → network port), the following metrics are collected in real time: Workstation usage time: the actual daily time employees spend at their workstations (calculated by network port connection time); network connection activity: traffic data for the workstation's associated network port (e.g., bandwidth utilization, packet transmission frequency); device online rate: the continuous online time of the employee's terminal device (MAC address) at the workstation's network port. Supplementary data is obtained from the enterprise intranet monitoring system: port status of network devices (switch / router) (e.g., packet loss rate and latency of Port 1); and application usage logs of employee terminal devices (e.g., frequency of video conferencing and file transfers).

[0129] Analyze the data indicators collected above, assign evaluation indicator weights and determine scoring rules. For example, usage time accounts for 40%, network activity accounts for 30%, and device online rate accounts for 30%. The additional penalty item is that if the packet loss rate of the workstation-associated network port is >5% or the delay is >100ms, the efficiency score will be reduced by 20%.

[0130] Model training uses historical data to train a regression model to predict workstation efficiency scores; the model accuracy is verified by comparing actual workstation turnover rates with tests similar to the model output.

[0131] Step S60, identifying idle workstations or inefficiently used workstations using the workstation utilization efficiency evaluation model;

[0132] Identify idle or inefficient workstations using an evaluation model. For example, a workstation with a usage time of less than 2 hours per day for five consecutive days and a device online rate of less than 20% is considered idle based on the workstation efficiency evaluation model. Alternatively, a workstation with an efficiency score less than 60 and a network activity or device online rate below the department average is marked as inefficient. The underlying logic is to quickly identify problem workstations using pre-set rules and model scoring.

[0133] Step S70, initiating an automatic cleanup process for the idle workstations and generating an idle workstation list;

[0134] Automatically release idle workstations: Unbind employees, mark workstations as "allocatable," generate a list of idle workstations, and push it to the workstation management system and administrative department to support resource reallocation.

[0135] Step S80 , analyzing the inefficiency reasons of the inefficiently used workstations in combination with the employee status data and the employee behavior pattern database, and adjusting the workstations according to the inefficiency reasons.

[0136] Combined with employee status data and the employee behavior pattern database, the inefficiency of inefficiently used workstations is analyzed. If the inefficiency is due to poor network quality, historical repair records from the IT operations and maintenance system are linked to verify whether it is a device failure. If the cause is a usage pattern conflict, employee behavior pattern tags are retrieved to verify the rationality of the workstation layout. For inefficient workstations caused by network quality, backup network ports are assigned or switched to high-stability areas. IT operations and maintenance work orders are automatically generated to trigger network equipment maintenance. Chronically inefficient fixed workstations are converted to flexible workstations and included in the reservation system for short-term use. Priority rules for flexible workstations are set.

[0137] Specifically, in another feasible implementation of this embodiment, the step S40 of managing the workstation according to the correspondence data and the employee status data may further include:

[0138] A time series prediction model is trained based on historical workstation usage data, and a peak workstation demand is predicted according to the time series prediction model to obtain a prediction result; and a workstation allocation strategy is dynamically adjusted according to the prediction result.

[0139] For example, based on historical workstation usage data (such as usage time, department needs, and project cycles), a time series prediction model is trained to predict the peak workstation demand in the next week / month. The workstation allocation strategy is dynamically adjusted based on the prediction results: spare workstations are pre-allocated before the peak demand (such as temporarily converting conference rooms into workstations); employees from high-demand departments are automatically assigned to low-utilization areas to balance the space load.

[0140] In this embodiment, a workstation utilization efficiency evaluation model is established to improve the scientific nature of workstation resource allocation through multi-dimensional data analysis and model prediction; it is linked with IT operation and maintenance, energy consumption management and other systems to form a closed loop of resource management, and fully automated processes replace manual operations to achieve precise management of workstation resources at low cost and without hardware dependence.

[0141] For example, in order to help understand the implementation process of the workstation management method of the present application, the overall process is described in detail below, specifically:

[0142] Step 1: Obtain the relationship data between the network port and the employee from the terminal device management data warehouse and the workstation data bound to the employee from the workstation management. This is equivalent to obtaining the first mapping relationship data between the network port and the employee and the binding relationship data between the employee and the workstation. It is the basic operation for subsequently generating corresponding relationship data and performing workstation management. The network port information corresponding to the employee's bound workstation is used to initialize the workstation network port information of the workstation management system to prepare for the subsequent workstation management process.

[0143] Step 2: Combine the terminal device management data warehouse data, the employee and workstation data of the workstation management system, and the employee data of the human resources management system to obtain the correspondence between all employees->workstation->network ports. That is, based on the first mapping relationship data, binding relationship data, and employee status data, the correspondence data between employees, workstations, and network ports is generated. By integrating data from multiple parties, a complete correspondence is established to provide data support for accurate workstation management.

[0144] Step 3: Employee status is divided into vacation, resignation, employment and vacation, employment and not on vacation. If the employee status is employed, on duty, not on vacation, and bound to a workstation, obtain the network port PortA-101 corresponding to the bound workstation A-101 according to the corresponding relationship data, and determine whether the network port currently used by the employee is PortA-101. If the network port currently used by the employee is PortB-101, obtain the bound workstation B-101 of network port PortB-101 according to the corresponding relationship data, unbind workstation A-101 from the employee, bind workstation B-101 to the employee, and update the corresponding relationship data.

[0145] Correspondingly, if the corresponding bound workstation of network port PortB-101 is not found in the corresponding relationship data, it means that network port PortB-101 is not bound to a workstation. The network port PortA-101 corresponding to A-101 is unbound, and the network port PortB-101 is bound to the workstation A-101, and then the corresponding relationship data is updated.

[0146] Step 4: If the employee status is on-the-job, not on leave, and not bound to a workstation, query the current network port PortC-101 used by the employee according to the corresponding relationship data. If the workstation C-101 corresponding to the network port PortC-101 is found in the corresponding relationship data, send the workstation confirmation information and bind the workstation C-101 to the network port PortC-101.

[0147] Correspondingly, if the workstation corresponding to the network port PortC-101 cannot be found in the corresponding relationship data, a workstation binding reminder is sent to bind the network port PortC-101 to the workstation currently being used by the employee.

[0148] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the workstation management method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0149] This application also provides a workstation management device, please refer to Figure 4 , the workstation management device includes:

[0150] A first mapping relationship data acquisition module 10 is used to acquire first mapping relationship data between network ports and employees;

[0151] A binding relationship data determination module 20 is used to initiate a workstation inventory task and determine the binding relationship data between the employee and the workstation through the workstation inventory task;

[0152] a corresponding relationship data generating module 30, configured to call employee status data and generate corresponding relationship data between the employee, the workstation, and the network port based on the first mapping relationship data, the binding relationship data, and the employee status data;

[0153] The workstation management module 40 is configured to manage the workstations according to the corresponding relationship data and the employee status data.

[0154] The workstation management device provided in this application, employing the workstation management method of the aforementioned embodiment, can resolve the technical issues of workstation management. Compared to the prior art, the beneficial effects of the workstation management device provided in this application are the same as those of the workstation management method provided in the aforementioned embodiment. Other technical features of the workstation management device are the same as those disclosed in the aforementioned embodiment and are not further elaborated here.

[0155] The present application provides a workstation management device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the workstation management method in the above-mentioned embodiment one.

[0156] Reference below Figure 5 , which shows a schematic diagram of the structure of a workstation management device suitable for implementing the embodiments of the present application. The workstation management device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The workstation management device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0157] like Figure 5As shown, the workstation management device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory 1002 or programs loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the workstation management device. The processing device 1001, the read-only memory 1002, and the random access memory 1004 are connected to each other via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the workstation management device to communicate with other devices wirelessly or wired to exchange data. Although the figure shows a workstation management device with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems can be implemented or provided instead.

[0158] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are performed.

[0159] The workstation management device provided in this application, employing the workstation management method of the aforementioned embodiment, can resolve the technical issues of workstation management. Compared to the prior art, the beneficial effects of the workstation management device provided in this application are the same as those of the workstation management method provided in the aforementioned embodiment. Other technical features of the workstation management device are the same as those disclosed in the aforementioned embodiment and are not further elaborated here.

[0160] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0161] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0162] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer program) stored thereon, and the computer-readable program instructions are used to execute the workstation management method in the above embodiment.

[0163] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0164] The computer-readable storage medium may be included in the workstation management device, or may exist independently without being assembled into the workstation management device.

[0165] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the workstation management device, the workstation management device: obtains the first mapping relationship data between the network port and the employee; initiates a workstation inventory task, and determines the binding relationship data between the employee and the workstation through the workstation inventory task; calls the employee status data, and generates the corresponding relationship data between the employee, the workstation, and the network port based on the first mapping relationship data, the binding relationship data, and the employee status data; and manages the workstation according to the corresponding relationship data and the employee status data.

[0166] Computer program code for performing the operations of the present application may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0167] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, program segment or a part of code, and the module, program segment or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.

[0168] The modules described in the embodiments of the present application may be implemented in software or hardware, wherein the name of a module does not necessarily limit the unit itself.

[0169] The computer-readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the aforementioned workstation management method, thereby resolving the technical issues surrounding workstation management. Compared to the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the workstation management method provided in the aforementioned embodiments, and are not further elaborated here.

[0170] The present application also provides a computer program product, comprising a computer program, which implements the steps of the above-mentioned workstation management method when executed by a processor.

[0171] The computer program product provided in this application can solve the technical problem of workstation management. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the workstation management method provided in the above embodiment, which will not be repeated here.

[0172] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A workstation management method, characterized in that: The workstation management method comprises: Obtain the first mapping relationship data between the network port and the employee; Initiate a workstation inventory task, and determine the binding relationship data between the employee and the workstation through the workstation inventory task; Calling employee status data, and generating corresponding relationship data between the employee, the workstation, and the network port based on the first mapping relationship data, the binding relationship data, and the employee status data; The workstations are managed according to the corresponding relationship data and the employee status data.

2. The workstation management method according to claim 1, wherein: The step of obtaining first mapping relationship data between network ports and employees includes: Obtaining second mapping relationship data between employee identity information, terminal MAC address, and terminal IP address from the enterprise intranet access control software; capturing network traffic data in real time by using a network packet capture technology, and parsing third mapping relationship data between the network port and the terminal IP address based on the network traffic data; The second mapping relationship data and the third mapping relationship data are matched and integrated with each other using the terminal IP address as the association key to generate the first mapping relationship data between the network port and the employee.

3. The workstation management method according to claim 1, wherein: The step of calling the employee status data and generating the corresponding relationship data between the employee, the workstation, and the network port based on the first mapping relationship data, the binding relationship data, and the employee status data includes: Calling employee status data, and performing standardization processing on the first mapping relationship data, the binding relationship data, and the employee status data; Associating the standardized first mapping relationship data, the binding relationship data, and the employee status data to generate initial corresponding relationship data between the employee, the workstation, and the network port; Abnormal data in the initial correspondence data is eliminated through an abnormality detection mechanism to obtain correspondence data between the employee, the workstation, and the network port.

4. The workstation management method according to claim 1, wherein: The step of managing the workstation according to the correspondence data and the employee status data includes: If the employee status data is on-the-job but not bound to a workstation, the associated workstation corresponding to the current network port used by the employee is queried according to the corresponding relationship data, and a workstation binding reminder is sent based on the associated workstation to update the corresponding relationship data.

5. The workstation management method according to claim 1, wherein: The step of managing the workstation according to the correspondence data and the employee status data includes: If the employee status data indicates that the employee is on-the-job and has a bound workstation, query the network port information corresponding to the bound workstation according to the corresponding relationship data, and determine whether the network port information is consistent with the current network port used by the employee; If the network port information is inconsistent with the current network port used by the employee, the current network port information used by the employee is queried according to the corresponding relationship data, and a workstation confirmation reminder is sent based on the current network port information to update the corresponding relationship data.

6. The workstation management method according to claim 1, wherein: The step of managing the workstation according to the correspondence data and the employee status data includes: establishing an employee behavior pattern database based on the employee status data; When the employee status data changes, a behavior pattern matching the current employee status is retrieved from the employee behavior pattern database, and the workstation is adjusted according to the behavior pattern and the corresponding relationship data.

7. The workstation management method according to claim 1, wherein: After the step of managing the workstation according to the corresponding relationship data and the employee status data, the following further comprises: Monitoring the usage and network connection status of the workstation based on the corresponding relationship data, and establishing a workstation usage efficiency evaluation model based on the usage and the network connection status; Identifying idle workstations or inefficiently used workstations using the workstation utilization efficiency evaluation model; Initiate an automatic cleanup process for the idle workstations and generate a list of idle workstations; The inefficiency reasons of the inefficiently used workstations are analyzed in combination with the employee status data and the employee behavior pattern database, and the workstations are adjusted according to the inefficiency reasons.

8. A workstation management device, characterized in that: The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the workstation management method according to any one of claims 1 to 7.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the workstation management method according to any one of claims 1 to 7 are implemented.

10. A computer program product, characterized in that The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the workstation management method according to any one of claims 1 to 7 are implemented.

Images