Work data management method and device, equipment, storage medium and program product

Abstract

The invention discloses a working data management method and device, equipment, a storage medium and a program product. The method comprises the steps that a management node obtains a working data file; determining an execution object corresponding to the to-be-executed work item based on the work data file, and allocating a cloud desktop to the execution object; log data generated in the process that the execution objects execute the corresponding work items based on the cloud desktops are obtained, and a log data preview page is generated based on the corresponding relation between the cloud desktops corresponding to the execution objects and the log data. According to the embodiment of the invention, the execution object can be determined based on the to-be-executed work information by utilizing the management node, the cloud desktop is allocated to the execution object to clarify the association relationship among the execution object, the to-be-executed work item and the cloud desktop, and meanwhile, the preview page corresponding to the log data generated when the execution object executes the corresponding work on the cloud desktop is generated; the management of the whole working process is realized through the management node, so that the management efficiency of the working data is improved.

Description

Technical Field

[0001] The present application relates to the field of virtualization technology, and in particular to a method, device, equipment, storage medium and program product for managing work data. Background Art

[0002] At present, work tickets are written documents that record work content, working hours, staff and other information. They are usually issued by managers to staff, who then complete the corresponding work content based on the information recorded in the work tickets.

[0003] Specifically, the manager can allocate a virtual desktop to the staff based on the record information of the work ticket, so that the staff can use the virtual desktop to complete the corresponding work content. At the same time, the manager can supervise the work process of the staff.

[0004] However, the above-mentioned human supervision method is easy to consume a lot of time, resulting in low management efficiency of work tickets in the prior art. Therefore, the low management efficiency of work tickets has become a problem that needs to be solved. Summary of the invention

[0005] In view of the above-mentioned defects or deficiencies in the prior art, it is desired to provide a work data management method, apparatus, equipment, storage medium and program product. The work data management method can utilize a management node to determine an execution object based on the work information to be executed, and assign a cloud desktop to the execution object to clarify the association between the execution object, the work item to be executed and the cloud desktop, and at the same time generate a preview page corresponding to the log data generated when the execution object executes the corresponding work on the cloud desktop, so as to realize the management of the entire work process through the management node, thereby improving the management efficiency of the work data.

[0006] In a first aspect, the present invention provides a method for managing work data, which is applied to a cloud desktop management system, wherein the cloud desktop management system includes a management node and a background server, and the background server supports the operation of multiple cloud desktops, and the method includes: The management node obtains a work data file, which includes work information of the work item to be executed; Based on the work data file, determine the execution object corresponding to the work item to be executed, and assign a cloud desktop to the execution object; The log data generated in the process of executing the corresponding work item based on the cloud desktop by the execution object is obtained, and the log data preview page is generated based on the corresponding relationship between the cloud desktop corresponding to each execution object and the log data.

[0007] In a second aspect, the present invention provides a work data management device, which is applied to a cloud desktop management system, the cloud desktop management system includes a management node and a background server, the background server supports the operation of multiple cloud desktops, and the device includes: An acquisition module, used to enable the management node to acquire a work data file, where the work data file includes work information of the work item to be executed; An allocation module, used to determine the execution object corresponding to the work item to be executed based on the work data file, and allocate a cloud desktop to the execution object; The processing module is used to obtain the log data generated during the execution of the corresponding work item by the execution object based on the cloud desktop, and generate a log data preview page based on the corresponding relationship between the cloud desktop corresponding to each execution object and the log data.

[0008] In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method described in the first aspect is implemented.

[0009] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, characterized in that when the program is executed by a processor, the method described in the first aspect is implemented.

[0010] In a fifth aspect, a computer program product is provided. The computer program product includes instructions. When the instructions are executed, any method described in the first aspect is executed.

[0011] The work data management method, apparatus, device, storage medium and program product provided in the embodiments of the present application can, on the one hand, determine the execution object corresponding to the work information based on the work information of the work item to be executed through the management node and assign a cloud desktop to it, so as to clarify the association between the work item to be executed, the execution object and the cloud desktop, thereby supervising the work process of the execution object based on the association; on the other hand, the management node can obtain and record the log data generated by the execution object when the cloud desktop executes the corresponding work item, so as to generate a log data preview page that can characterize the correspondence between the execution object, the cloud desktop and the log data, thereby utilizing the management node to realize the management of the entire work process, thereby improving the management efficiency of work data. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings: Figure 1 A schematic diagram of the implementation environment architecture provided for the embodiments of the present application; Figure 2A flowchart of a method for managing work data provided in an embodiment of the present application; Figure 3 A schematic diagram of a module of a management node 10 provided in an embodiment of the present application; Figure 4 A schematic diagram of a log data preview page provided in an embodiment of the present application; Figure 5 A flowchart of another method for managing work data provided in an embodiment of the present application; Figure 6 A block diagram of a device for managing work data provided in an embodiment of the present application; Figure 7 A schematic diagram of the structure of a computer device provided in an embodiment of the present application; In the above picture: 10-management node; 20-cloud desktop resource pool; 30-user terminal; 101-work data file management unit; 1011-creation module; 1012-approval module; 1013-notification module; 1014-termination module; 1015-renewal module; 102-work data file cloud desktop management unit; 1021-information management module; 1022-creation module; 1023-allocation module; 1024-allocation time management module; 1025-recycling module; 1026-termination allocation module; 1027-cloud desktop renewal module; 103-log data audit unit; 1031-cloud desktop connection record module; 1032-cloud desktop terminal echo record module Block; 1033-cloud desktop video recording module; 104-log data preview unit; 1041-log data summary module; 1042-log data display module; 600-work data management device; 601-acquisition module; 602-allocation module; 603-processing module; 700-computer equipment; 701-central processing unit (CPU); 702-read-only memory (ROM); 703-random access memory (RAM); 704-bus; 705-input / output (I / O) interface; 706-input part; 707-output part; 708-storage part; 709-communication part; 710-drive; 711-removable medium. DETAILED DESCRIPTION

[0013] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It is also necessary to explain that, for ease of description, only the parts related to the invention are shown in the accompanying drawings.

[0014] It should be noted that, in the absence of conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments. In addition, the term "and / or" herein is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order of objects.

[0015] Figure 1 Schematic diagram of the implementation environment architecture of a work data management method provided in an embodiment of the present application. Figure 1 As shown, the implementation environment architecture can be a cloud desktop management system, which can specifically include: a management node 10, a cloud desktop resource pool 20 and multiple user terminals 30; wherein the cloud desktop resource pool 20 can include multiple cloud desktops and a background server that supports the operation of multiple cloud desktops.

[0016] In a specific implementation, the management node 10 can output a control instruction to the cloud desktop resource pool 20 in response to a cloud desktop request generated by the user terminal 30 or itself, so that the cloud desktop resource pool 20 controls the background server to support the operation of at least one cloud desktop in response to the control instruction, thereby providing cloud desktop services to at least one user terminal 30 to realize cloud desktop allocation to the user terminal 30.

[0017] Exemplarily, the management node 10 may generate a cloud desktop request according to the work information of the work item to be executed, so as to allocate a cloud desktop to the corresponding user terminal 30 based on the cloud desktop request; wherein the management node 10 may also be referred to as a cloud desktop work data management system.

[0018] Exemplarily, the multiple cloud desktops included in the cloud desktop resource pool 20 can have a one-to-one or one-to-many correspondence with multiple user terminals 30. Based on this, the cloud desktop resource pool 20 can directly control the background server to provide cloud desktop services to the corresponding user terminals 30 in response to the control instructions of the management node 10.

[0019] Optionally, the cloud desktop resource pool 20 may control the background server to sequentially provide cloud desktop services to the corresponding user terminals 30 (ie, sequentially allocate cloud desktops to the user terminals 30 ) in response to a control instruction of the management node 10 .

[0020] It should be noted that the cloud desktop can run on the user terminal 30. Based on this, the operation of the cloud desktop resource pool 20 responding to the control instruction to allocate the cloud desktop to the user terminal 30 can be that the cloud desktop resource pool 20 provides the cloud desktop deployed on the user terminal 30 with the support of the background server, so that the cloud desktop deployed on the user terminal 30 can be used normally. Optionally, the cloud desktop can also run on the background server.

[0021] Exemplarily, the user terminal 30 may be a terminal device in various application scenarios, such as a smart TV, a smart phone, a tablet computer, a TV, a laptop computer, a desktop computer, etc.

[0022] Currently, work tickets are written documents that record and indicate work information. They are usually issued by managers to workers, who then complete corresponding work content based on the information recorded in the work tickets.

[0023] Specifically, the recorded information of the work ticket may include work tasks, work start time, work end time, work location, staff list, equipment and tools involved in the work process, risk assessment results and necessary safety measures, etc.; for example, work tickets can be used in industrial production, construction, power maintenance and other fields to ensure production safety and improve work efficiency in these fields.

[0024] For example, a manager may allocate a virtual desktop to a worker based on the recorded information of the work ticket, so that the worker can use the virtual desktop to complete the corresponding work content. At the same time, the manager may supervise the work process of the worker using the virtual desktop.

[0025] Specifically, a large number of independent virtual desktops can be generated on a physical server through server virtualization technology, and the virtual desktops can be sent to user terminals based on a proprietary virtual desktop transmission protocol, so that the user terminals can log in to the virtual desktops through Ethernet.

[0026] However, before the above-mentioned cloud desktop is allocated, the work ticket record information needs to be approved by the work ticket management system, so that after the record information is approved, the virtual desktop system administrator will allocate the virtual desktop to the corresponding user terminal and manually supervise the specific operation content of the user terminal on the virtual desktop. This makes the supervision and management process of the work ticket more cumbersome and easy to consume a lot of time, resulting in low management efficiency of the work ticket. Therefore, the low management efficiency of the work ticket has become a problem that needs to be solved.

[0027] Based on this, an embodiment of the present application provides a work data management method, whose technical principle is: use the management node to first determine the execution object based on the work information to be executed, and then assign a cloud desktop to the execution object to clarify the association between the cloud desktop and the execution object, and at the same time record the log data generated by the execution object when executing the corresponding work on the cloud desktop and generate a preview page corresponding to the log data.

[0028] It should be noted that although the operations of the method of the present invention are described in a particular order in the drawings, this does not require or imply that the operations must be performed in this particular order or that all illustrated operations must be performed to achieve desired results.

[0029] The present application embodiment provides a method for managing work data, which can be applied to Figure 1 The cloud desktop management system shown in Figure 2 is a flowchart of a method for managing work data provided by an embodiment of the present application, such as Figure 2 As shown, the method specifically comprises the following steps: Step 201: The management node 10 obtains a work data file, where the work data file includes work information of a work item to be executed.

[0030] In one possible implementation, the management node 10 may obtain a work data file created by a management object or an execution object, wherein the management object may be a person responsible for managing the work data file, the execution object may be a person who executes the work data file, and the work data file may correspond to the content of a work ticket.

[0031] Exemplarily, a work data file may include work information of at least one work item to be executed, wherein the work information may include execution team information, execution personnel information, execution processing time, execution content information, execution environment configuration requirements, etc., without specific limitations here.

[0032] For example, Figure 3 is a module diagram of the management node 10 provided in an embodiment of the present application, such as Figure 3 As shown, the management node 10 may include a work data file management unit 101, and the work data file management unit 101 may be used for application, approval, issuance, renewal and termination of work data files.

[0033] Specifically, the work data file management unit 101 may include a creation and preparation module 1011 to implement the creation of the work data file in the creation and preparation module 1011 .

[0034] For example, the management object or the execution object may establish a communication connection with the management node 10 through the user terminal 30 to create a working data file in the creation and preparation module 1011 of the management node 10 .

[0035] Step 202: Determine the execution object corresponding to the work item to be executed based on the work data file, and allocate a cloud desktop to the execution object; wherein the cloud desktop is deployed on the execution object.

[0036] In a possible implementation, the management node 10 may determine, based on the work data file, execution objects corresponding to each to-be-executed work item in the work data file; wherein one to-be-executed work item may correspond to one execution object or multiple execution objects.

[0037] Exemplarily, the execution object corresponding to the work item to be executed can be determined according to the specific work information of the work item to be executed. For example, the corresponding team or person can be determined as the execution object according to the execution team information or execution personnel information recorded in the work information.

[0038] In a possible implementation, before determining the execution object corresponding to the to-be-executed work item, a risk assessment may be performed on each to-be-executed work item in the work data file to determine the execution status of the to-be-executed work item (ie, whether to execute the to-be-executed work item).

[0039] Exemplarily, whether to execute the work item to be executed may be determined based on the risk level of the work information of the work item to be executed, so that when it is determined that the work item to be executed is executed, the execution object corresponding to the work item to be executed is determined.

[0040] It should be noted that, when the work data file contains multiple work items to be executed, the risk levels of the work information of the work items to be executed can be determined one by one.

[0041] For example, Figure 3 As shown, the work data file management unit 101 may also include an approval module 1012. Specifically, the management object may determine the risk level of the work information of the to-be-executed work item recorded by the creation preparation module 1011 through the approval module 1012, and record the risk assessment content related to the work information.

[0042] It should be noted that when the management object determines the execution status of the work item to be executed (ie, performs risk assessment on the work item to be executed), the approval module 1012 can record the relevant information of the management object to determine the approval object of the work item to be executed.

[0043] For example, when it is determined to execute the to-be-executed work item, the approval module 1012 may update the status of the corresponding to-be-executed work item to approved.

[0044] Exemplarily, when a work data file is created by a management object in the creation module 1011, the management object can directly determine the risk level of the work information of the work item to be executed in the work data file, and record the risk assessment content related to the work information. At this time, the status of the work item to be executed can be directly updated to approved.

[0045] Exemplarily, when it is determined not to execute the work data file based on the risk level of the work information of the work item to be executed, the work information of the work item to be executed may be modified until the risk level of the work information meets the execution requirement.

[0046] For example, the management object can modify the work information of the work item to be executed to modify the work information to meet the execution requirements; the management object can also update the status of the work item to be executed to failed approval through the approval module 1012, and send the status to the creation object of the work item to be executed, so that the creation object can modify the work information of the work item to be executed.

[0047] It should be noted that when the creation object modifies the work information of the work item to be executed, the modified work information can be stored in the creation planning module 1011, so that the management object can re-determine the risk level of the modified work information through the approval module 1012, and this cycle can be repeated until the risk level of the work information meets the execution requirements.

[0048] In a possible implementation, when it is determined that the work item to be executed meets the execution requirement (that is, the work data file can be executed), a cloud desktop can be allocated to the execution object corresponding to the work item to be executed.

[0049] Exemplarily, when it is determined that the work item to be executed meets the execution requirement, the management node 10 may send the work information of the work item to be executed to the corresponding execution object based on the determined execution object, so as to establish an association relationship between the execution object and the work item to be executed.

[0050] Specifically, Figure 3 As shown, the work data file management unit 101 may further include a notification module 1013, so as to use the notification module 1013 to send work information to the execution object.

[0051] For example, the notification module 1013 can notify the execution object of the work information of the work item to be executed by sending text messages or emails; among them, the notification of text messages or emails can be realized by integrating third-party text message libraries, mailbox libraries, etc., and no specific restrictions are made here.

[0052] Exemplarily, the management node 10 may simultaneously determine the cloud desktop information based on the execution environment configuration requirements of the work item to be executed, so as to allocate the cloud desktop to the corresponding execution object, thereby establishing an association relationship between the work item to be executed, the cloud desktop, and the execution object.

[0053] For example, Figure 3 As shown, the management node 10 may further include a work data file cloud desktop management unit 102 , so as to utilize the work data file cloud desktop management unit 102 to determine a cloud desktop corresponding to the work item to be executed.

[0054] Exemplarily, the work data file cloud desktop management unit 102 may include an information management module 1021 , a creation module 1022 , and an allocation module 1023 .

[0055] Specifically, the information management module 1021 can be used to record basic information such as the number, name, description information, pre-start number, recycling strategy, etc. of cloud desktops in the cloud desktop resource pool 20, wherein the description information of each cloud desktop can include the operating system, memory, CPU, disk and other information of each cloud desktop.

[0056] Specifically, the creation module 1022 can be used to create cloud desktops in the cloud desktop resource pool 20 and manage the status of each cloud desktop. For example, the creation module 1022 can create a corresponding number of cloud desktops with corresponding configuration information based on the number of cloud desktops recorded by the information management module 1021 and the description information of each cloud desktop, and maintain and manage the cloud desktop status to ensure that the background server in the cloud desktop resource pool 20 can provide operation support to the pre-started number of idle cloud desktops.

[0057] Specifically, the allocation module 1023 can be used to allocate cloud desktops. For example, the allocation module 1023 can send a control instruction to the cloud desktop resource pool 20 based on the execution time period information of the work item to be executed, before the execution time of the work item to be executed is reached, so that the cloud desktop resource pool 20 can control the background server to provide operation support to the cloud desktop in an idle state, and send cloud desktop related information to the execution object, thereby realizing the cloud desktop allocation to the execution object.

[0058] For example, Figure 3 As shown, the work data file cloud desktop management unit 102 may also include an allocation time management module 1024, which sends an allocation result to the allocation time management module 1024 after the allocation module 1023 allocates a cloud desktop to the execution object, so that the allocation time management module 1024 can create a cloud desktop allocation record and update the allocation time of each cloud desktop; wherein, the allocation time management module 1024 can record the allocation time of the cloud desktop based on the execution start time and execution end time of the work item to be executed.

[0059] Step 203, obtaining log data generated during the execution of the corresponding work item by the execution object based on the cloud desktop, and generating a log data preview page based on the corresponding relationship between the cloud desktop corresponding to each execution object and the log data.

[0060] In a possible implementation, after allocating a cloud desktop to the execution object, the management node 10 may obtain log data generated by the execution object when executing a corresponding work item based on the cloud desktop.

[0061] Exemplarily, the execution object may be the user terminal 30 . After the work data file cloud desktop management unit 102 completes the cloud desktop allocation, the executor of the work item to be executed may connect to the cloud desktop through the user terminal 30 .

[0062] Exemplarily, the log data may include all data information involved in the execution of the corresponding work item by the execution object, for example, may include command information, operation information, and connection information input by the execution object.

[0063] For example, Figure 3 As shown, the management node 10 may further include a log data audit unit 103 , so as to obtain log data generated by the execution object during the execution of the corresponding work item through the log data audit unit 103 .

[0064] Exemplarily, the log data audit unit 103 may include a cloud desktop connection recording module 1031 , a cloud desktop terminal echo recording module 1032 , a cloud desktop video recording module 1033 and an audit component 1034 .

[0065] Specifically, the cloud desktop connection recording module 1031 can be used to record the number of times the execution object connects to the cloud desktop and the duration of the connection to the cloud desktop; the cloud desktop terminal echo recording module 1032 can be used to record the input instructions of the execution object when accessing the cloud desktop and the instruction execution time; the cloud desktop video recording module 1033 can be used to record the specific operations of the execution object when accessing the cloud desktop.

[0066] Exemplarily, when the execution object is a user terminal 30, the audit component 1034 can be set on the user terminal 30 and the cloud desktop respectively.

[0067] Specifically, after the work data file cloud desktop management unit 102 assigns a cloud desktop to the user terminal 30, the audit component 1034 set in the user terminal 30 can obtain the connection information between the user terminal 30 and the cloud desktop, and report the obtained connection information to the above-mentioned cloud desktop connection recording module 1031 by regularly calling the API interface, so that the cloud desktop connection recording module 1031 stores the connection information in the database; wherein the connection information may include basic information of the user terminal 30 (for example, host name, MAC address, IP, etc.), login information of the user currently logged in to the user terminal 30, connection time of the cloud desktop, and description information of the cloud desktop, etc.

[0068] It should be noted that when the preset duration is exceeded, the connection information reported by the audit component 1034 to the cloud desktop connection recording module 1031 may be a disconnected state, which may indicate that the connection between the user terminal 30 and the cloud desktop is disconnected; wherein the preset duration may be the normal connection duration between the user terminal 30 and the cloud desktop.

[0069] Specifically, after determining the connection information between the user terminal 30 and the cloud desktop, the audit component 1034 set in the cloud desktop can obtain the command information entered in the cloud desktop, and report the obtained command information to the above-mentioned cloud desktop terminal echo recording module 1032 by regularly calling the API interface, so that the cloud desktop terminal echo recording module 1032 can store the command information in the database.

[0070] Specifically, after the instruction is input, the audit component 1034 set in the user terminal 30 can use the ffmpeg tool to record the specific operations on the cloud desktop, and upload the video slices to the above-mentioned cloud desktop video recording module 1033 through regular calls to the API interface, so that the cloud desktop video recording module 1033 can store the video slices in the database.

[0071] In a possible implementation, after the log data audit unit 103 obtains the log data generated by the execution object during the execution of the corresponding work item, a log data preview page can be generated based on the correspondence between the cloud desktops corresponding to each execution object and the log data.

[0072] Exemplarily, a log data preview page may be generated based on work information, approval information, execution object information, cloud desktop information, and log data of the to-be-executed work item corresponding to the work data file.

[0073] For example, Figure 3 As shown, the management node 10 may further include a log data preview unit 104 , and the log data preview unit 104 may specifically include a log data aggregation module 1041 and a log data display module 1042 .

[0074] Specifically, the log data aggregation module 1041 can be used to aggregate the work information, approval information, execution object information, cloud desktop allocation information of each work item to be executed in the work data file, and the log data generated when executing the work item to be executed.

[0075] Specifically, the log data display module 1042 can be used to display the information summarized and counted by the log data aggregation module 1041.

[0076] The work data management method provided in the embodiment of the present application can, on the one hand, determine the execution object corresponding to the work information based on the work information of the work item to be executed through the management node and assign a cloud desktop to it, so as to clarify the association between the work item to be executed, the execution object and the cloud desktop, and thus supervise the work process of the execution object based on the association; on the other hand, the management node can obtain and record the log data generated by the execution object when the cloud desktop executes the corresponding work item, so as to generate a log data preview page that can characterize the correspondence between the execution object, the cloud desktop and the log data, so as to use the management node to realize the management of the entire work process, thereby improving the management efficiency of work data.

[0077] In another embodiment of the present application, a method for stopping the use of a cloud desktop is also provided. Exemplarily, the "work information of the work item to be executed" mentioned above includes at least the processing time of the work item to be executed, and the method further includes: when the management node 10 detects that the use time of the target cloud desktop configured by the execution object corresponding to the work item to be executed reaches the processing time, the management node 10 sends a service termination instruction to the background server; the service termination instruction is used to instruct the background server to stop responding to the service request instruction of the target cloud desktop.

[0078] In the example of the present application, the usage time of the cloud desktop can be monitored by the management node 10, so that when the usage time of the cloud desktop reaches the processing time of the work item to be executed, the response to the business request instructions of the cloud desktop can be stopped in time, thereby achieving efficient management of the cloud desktop.

[0079] In one possible implementation, based on the execution start time and the execution processing time in the work information of the work item to be executed, when the management node 10 detects that the usage time of the target cloud desktop configured by the execution object corresponding to the work item to be executed reaches the processing time, a control instruction can be issued to the cloud desktop resource pool 20, so that the cloud desktop resource pool 20 controls the background server to stop providing operation support to the target cloud desktop (that is, the background server responds to the business termination instruction to stop responding to the business request instruction of the target cloud desktop).

[0080] For example, Figure 3As shown, the work data file cloud desktop management unit 102 may further include an allocation time management module 1024 and a recycling module 1025 .

[0081] Specifically, the allocation time management module 1024 can be used to record the allocation time of the target cloud desktop, so that when the allocation time (i.e., the usage time of the execution object for the target cloud desktop) reaches the execution processing time corresponding to the work information, a recovery notification is sent to the recovery module 1025, so that the recovery module 1025 can recover the permissions of the cloud desktop in response to the recovery notification.

[0082] It should be noted that the recovery module 1025 recovers permissions for the cloud desktop by sending a service termination instruction to the background server to control the background server to stop providing operation support to the target cloud desktop; wherein, the recovery module 1025 can recover permissions for the cloud desktop based on the recovery policy recorded by the information management module 1021.

[0083] In a possible implementation, the recycling strategy recorded by the information management module 1021 is mainly aimed at recycling the target cloud desktop and recycling the log data generated by the execution object based on the target cloud desktop.

[0084] Exemplarily, the recovery strategy may specifically include retaining log data recovery or erasing log data recovery; wherein, retaining log data recovery may be to recover permissions for the cloud desktop only (i.e., the log data is recovered together with the cloud desktop permissions); erasing log data recovery may be to restore the cloud desktop to its initial state and recover permissions for the cloud desktop (i.e., the log data is deleted and the cloud desktop permissions are recovered).

[0085] In a possible implementation, the retention or erasure of the log data may be determined based on the confidentiality level of the log data.

[0086] Exemplarily, the confidentiality level of the log data may be determined, and a management operation on the log data may be performed based on the confidentiality level; wherein the management operation includes recording the log data or deleting the log data.

[0087] It should be noted that when the management operation of log data is to record log data, the cloud desktop corresponding to the log data can retain the log data so that when the cloud desktop is assigned to the same execution object again, the execution object can continue to execute the work item to be executed based on the log data retained by the cloud desktop.

[0088] In another embodiment of the present application, another method for stopping the use of the cloud desktop is provided. Exemplarily, the method further includes: obtaining the risk level of the log data, when the risk level is greater than a preset threshold, the management node 10 sends a service termination instruction to the background server; the service termination instruction is used to instruct the background server to stop responding to the service request instruction of the target cloud desktop.

[0089] In an embodiment of the present application, the management node 10 can perform a risk assessment on the log data generated by the execution object, so as to terminate the cloud desktop service in a timely manner when there is a greater risk in the log data, thereby ensuring the safe use of the cloud desktop and making the risks in the entire workflow controllable.

[0090] In one possible implementation, when the execution object executes a work item to be executed based on a cloud desktop, the risk level of the log data generated by the execution object can be determined in real time, so that when the risk level of the log data is greater than a preset threshold, a control instruction is issued to the cloud desktop resource pool 20 through the management node 10, so that the cloud desktop resource pool 20 controls the background server to stop providing operation support to the target cloud desktop (that is, the background server responds to the business termination instruction to stop responding to the business request instruction of the target cloud desktop).

[0091] Exemplarily, the management object (eg, the person in charge of managing the work data file) may determine the risk level of the log data summarized and counted by the log data preview unit 104 to initiate a termination operation of the work data file when the risk level is greater than a preset threshold.

[0092] For example, Figure 3 As shown, the work data file management unit 101 may also include a termination module 1014. Specifically, when the management object determines that the risk level of the log data is greater than a preset threshold, the termination module 1014 may initiate an abnormal termination operation on the work item to be executed, and record relevant termination reasons and other information, and then the termination module 1014 may send a termination operation instruction of the work item to be executed to the termination allocation module 1026 of the work data file cloud desktop management unit 102 in response to the termination operation, so that the termination allocation module 1026 triggers the recovery module 1025 to perform a permission recovery operation on the target cloud desktop configured by the execution object corresponding to the work item to be executed, and updates the allocation end time of the target cloud desktop through the allocation time management module 1024.

[0093] It should be noted that the operation of the management node 10 sending the service termination instruction to the background server is similar to the operation of sending the service termination instruction in the previous embodiment, and will not be described in detail here.

[0094] In another embodiment of the present application, a method for extending the use of a cloud desktop is also provided. Exemplarily, the method further includes: when the management node 10 receives an application for extended use of a target cloud desktop configured by itself sent by the execution object, the management node 10 sends a business recovery instruction to the background server; the business recovery instruction is used to instruct the background server to continue to respond to the business request instruction of the target cloud desktop.

[0095] In one possible implementation, the execution object can initiate an extension of the usage time of the target cloud desktop that has a corresponding relationship with itself through the management node 10, so that the management node 10 sends a control instruction to the cloud desktop resource pool 20, so that the cloud desktop resource pool 20 controls the background server to resume the operation support provided to the target cloud desktop (that is, the background server responds to the business recovery instruction and continues to respond to the business request instruction of the target cloud desktop).

[0096] For example, Figure 3 As shown, the work data file management unit 101 may further include a renewal module 1015. Specifically, when the execution object needs to extend the use time of the target cloud desktop, the execution end time of the to-be-executed work item can be extended through the renewal module 1015 (i.e., the processing time of the to-be-executed work item is extended), and the renewal module 1015 records the renewal information; wherein the renewal information may include the reason for the extended use of the target cloud desktop and the extended use end time of the target cloud desktop, etc.

[0097] For example, when the execution object determines that the to-be-executed work item cannot be completed within the remaining usage time of the target cloud desktop, a request for extending the usage of the target cloud desktop can be initiated through the renewal module 1015 .

[0098] Exemplarily, the approval module 1012 can be used to approve the extended use request of the target cloud desktop initiated in the renewal module 1015. Specifically, after approval, the renewal module 1015 can send the extended use request to the cloud desktop renewal module 1027 of the work data file cloud desktop management unit 102, so that the cloud desktop renewal module 1027 sends the extended use end time of the target cloud desktop to the allocation time management module 1024, and the allocation time management module 1024 updates the use end time of the target cloud desktop to the extended use end time of the target cloud desktop, thereby completing the extended use application of the target cloud desktop.

[0099] Exemplarily, after the allocation time management module 1024 updates the use end time of the target cloud desktop, it can send a control instruction to the cloud desktop resource pool 20 so that the cloud desktop resource pool 20 controls the background server to continue to respond to the service request instruction of the target cloud desktop.

[0100] In another embodiment of the present application, the specific content of the log data preview page is also provided. For example, Figure 4 is a schematic diagram of a log data preview page provided in an embodiment of the present application, such as Figure 4 As shown, the log data preview page can be used to record all data information involved in the execution object during the execution of the corresponding work item.

[0101] Specifically, refer to Figure 4 The log data preview page may include the number, status, creation object, and creation time of the work item to be executed recorded by the creation and planning module 1011, the approval object, approval time, risk assessment result, and risk assessment content of the work item to be executed recorded by the approval module 1012, the execution team and execution object of the work item to be executed recorded by the notification module 1013, the abnormal termination time and termination reason of the work item to be executed recorded by the termination module 1014, the extension request information of the work item to be executed recorded by the renewal module 1015, the cloud desktop configuration information recorded by the information management module 1021, the cloud desktop allocation information recorded by the allocation module 1023, the execution start time and execution end time of the cloud desktop recorded by the time management module 1024, the number of times the execution object connects to the cloud desktop and the duration of the connection to the cloud desktop, the specific operations of the execution object when accessing the cloud desktop, and other information recorded by the log data audit unit 103.

[0102] In another embodiment of the present application, another method for managing work data is provided. Figure 5 is a flow chart of another method for managing work data provided by an embodiment of the present application, such as Figure 5 As shown, the method specifically comprises the following steps: Step 501a, the execution object creates a working data file.

[0103] Exemplarily, the execution object may create a work data file in the creation module 1011. Based on this, after the creation of the work data file is completed, step 502 may be executed; wherein the execution object may be an operator of the work data file.

[0104] Step 501b: The management object creates a working data file.

[0105] Exemplarily, the management object may create a work data file in the creation module 1011. Based on this, after the creation of the work data file is completed, step 504b may be executed; wherein the management object may be a manager of the work data file.

[0106] Step 502, determining whether the risk level of the work information of the work item to be executed in the work data file meets the execution requirements, when the risk level meets the execution requirements, executing step 503, otherwise executing step 501a.

[0107] Exemplarily, the risk level of the work information of the work item to be executed may be determined by the approval module 1012 .

[0108] Exemplarily, when the risk level does not meet the execution requirement, step 501a may be executed to modify the work information of the work item to be executed.

[0109] Step 503, determining whether the work item to be executed is a request for extended use of the cloud desktop, if so, executing step 504a, otherwise executing 504b.

[0110] Exemplarily, the renewal module 1015 may be used to determine whether the to-be-executed work item corresponds to a request for extended use of the cloud desktop.

[0111] Step 504a: Update the usage end time of the cloud desktop corresponding to the work item to be executed.

[0112] Exemplarily, the allocation time management module 1024 may update the end time of use of the cloud desktop corresponding to the work item to be executed.

[0113] Exemplarily, after the use end time of the cloud desktop is updated, step 506 may be directly executed.

[0114] Step 504b: determine the execution object corresponding to the work item to be executed.

[0115] Exemplarily, the execution object of the work item to be executed may be determined based on the work information of the work item to be executed.

[0116] Exemplarily, the notification module 1013 can be used to notify the execution object of the work information of the work item to be executed by sending text messages or emails; among them, the notification of text messages or emails can be implemented by integrating third-party text message libraries, mailbox libraries, etc., and no specific restrictions are made here.

[0117] Step 505: Allocate a cloud desktop to the execution object.

[0118] Exemplarily, the allocation module 1023 can send a control instruction to the cloud desktop resource pool 20 based on the execution time period information of the work item to be executed before the execution time of the work item to be executed is reached, so that the cloud desktop resource pool 20 can control the background server to provide operation support to the cloud desktop in an idle state, and send cloud desktop related information to the execution object, thereby realizing the cloud desktop allocation to the execution object.

[0119] Step 506: The execution object establishes a connection with the cloud desktop.

[0120] Step 507: Obtain log data generated during the execution of the corresponding work item by the execution object based on the cloud desktop.

[0121] Exemplarily, the connection information between the execution object and the cloud desktop can be obtained by the audit component 1034 set in the execution object, and the obtained connection information can be reported to the cloud desktop connection recording module 1031 by calling the API interface at a regular interval.

[0122] Exemplarily, the command information input in the cloud desktop can be obtained by the audit component 1034 set in the cloud desktop, and the obtained command information can be reported to the cloud desktop terminal echo recording module 1032 by calling the API interface at a regular interval.

[0123] Exemplarily, the audit component 1034 set in the execution object can use the ffmpeg tool to record the specific operations on the cloud desktop, and upload the video segments to the above-mentioned cloud desktop video recording module 1033 by calling the API interface at a regular interval.

[0124] Step 508 , determining whether the execution object initiates a request for extended use of the cloud desktop, if so, executing step 502 , otherwise executing step 509 .

[0125] Step 509: When the usage time of the cloud desktop configured by the execution object reaches the processing time of the work information of the work item to be executed, the cloud desktop usage permission is revoked.

[0126] Exemplarily, the allocation time management module 1024 can be used to record the allocation time of the cloud desktop, so that when the allocation time (i.e., the usage time of the execution object for the cloud desktop) reaches the execution processing time corresponding to the work information, a recovery notification is sent to the recovery module 1025, so that the recovery module 1025 can recover the permissions of the cloud desktop in response to the recovery notification.

[0127] Step 510: Generate a log data preview page based on the corresponding relationship between the cloud desktops corresponding to each execution object and the log data.

[0128] Exemplarily, the log data aggregation module 1041 can be used to aggregate and count the work information, approval information, execution object information, cloud desktop allocation information, and log data generated when executing the work items to be executed for each work item to be executed in the work data file.

[0129] Exemplarily, the log data display module 1042 may be used to display the information summarized and counted by the log data aggregation module 1041 .

[0130] Figure 6A block diagram of a work data management device provided in an embodiment of the present application. Figure 6 As shown, the work data management device 600 includes: an acquisition module 601, an allocation module 602 and a processing module 603, wherein: An acquisition module 601 is used to enable the management node to acquire a work data file, where the work data file includes work information of a work item to be executed; The allocation module 602 is used to determine the execution object corresponding to the work item to be executed based on the work data file, and allocate the cloud desktop to the execution object; wherein the cloud desktop is deployed on the execution object; The processing module 603 is used to obtain the log data generated when the execution object executes the corresponding work item based on the cloud desktop, and generate a log data preview page based on the corresponding relationship between the cloud desktop corresponding to each execution object and the log data.

[0131] Reference below Figure 7 , Figure 7 A schematic diagram of the structure of a computer device suitable for implementing the embodiments of the present application is shown. Figure 7 As shown, the computer device 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 702 or the program loaded from the storage part 708 to the random access memory (RAM) 703. In the random access memory (RAM) 703, various programs and data required for the operation instructions of the system are also stored. The central processing unit (CPU) 701, the read-only memory (ROM) 702 and the random access memory (RAM) 703 are connected to each other through a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0132] The following components are connected to the input / output (I / O) interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the input / output (I / O) interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed so that a computer program read therefrom is installed into the storage section 708 as needed.

[0133] In particular, according to an embodiment of the present application, the above reference flow chart Figure 2Any of the described processes may be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product including a computer program carried on a computer-readable medium, the computer program including a program code for executing the method shown in the flowchart. In such an embodiment, the computer program includes a 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 section 709, and / or installed from a removable medium 711. When the computer program is executed by a central processing unit (CPU) 701, the above-mentioned functions defined in the system of the present application are executed.

[0134] It should be noted that the computer-readable medium shown in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. 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 of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium that matches a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, device or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0135] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operating instructions of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the aforementioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, the boxes represented by two connections 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 with a dedicated hardware-based system that performs a specified function or operating instruction, or can be implemented with a combination of dedicated hardware and computer instructions.

[0136] The units or modules involved in the embodiments described in the present application may be implemented by software or by hardware. The described units or modules may also be provided in a processor, for example, may be described as: a processor including a semantic extraction unit, a weight allocation unit, and a determination unit. The names of these units or modules do not, in some cases, constitute limitations on the units or modules themselves.

[0137] As another aspect, the present application further provides a computer-readable storage medium, which may be included in the computer device described in the above embodiment, or may exist independently without being installed in the computer device. The above computer-readable storage medium stores one or more programs, and when the above programs are used by one or more processors to execute the method described in the present application. For example, it can be executed Figure 2 The steps of any of the methods shown.

[0138] The present application embodiment provides a computer program product, which includes instructions. When the instructions are executed, the method described in the present application embodiment is executed. For example, Figure 2 The steps of any of the methods shown.

[0139] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the aforementioned disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present application (but not limited to) by each other to form a technical solution.

Claims

1. A method for managing work data, applied to a cloud desktop management system, wherein the cloud desktop management system includes a management node and a background server, wherein the background server supports the operation of multiple cloud desktops, and is characterized in that: The method comprises: The management node obtains a work data file, wherein the work data file includes work information of a work item to be executed; Based on the work data file, determining the execution object corresponding to the to-be-executed work item, and assigning a cloud desktop to the execution object; The log data generated in the process of the execution object executing the corresponding work item based on the cloud desktop is obtained, and a log data preview page is generated based on the corresponding relationship between the cloud desktop corresponding to each of the execution objects and the log data.

2. The method for managing work data according to claim 1, characterized in that: The determining the execution object corresponding to the to-be-executed work item includes: Acquire the risk level of the work information of the to-be-executed work item, and determine whether to execute the work data file based on the risk level; In the case of determining to execute the work data file, determining the execution object corresponding to the to-be-executed work item.

3. The method for managing work data according to claim 2, characterized in that: The method further comprises: In a case where it is determined not to execute the work data file, the work information of the to-be-executed work item is modified until the risk level of the work information meets the execution requirement.

4. The method for managing work data according to claim 1, characterized in that: The work information of the to-be-executed work item at least includes the processing time of the to-be-executed work item, and the method further includes: When the management node detects that the usage time of the target cloud desktop configured by the execution object corresponding to the work item to be executed reaches the processing time, the management node sends a service termination instruction to the background server; the service termination instruction is used to instruct the background server to stop responding to the service request instruction of the target cloud desktop.

5. The method for managing work data according to claim 1, characterized in that: The method further comprises: The risk level of the log data is obtained. When the risk level is greater than a preset threshold, the management node sends a service termination instruction to the background server; the service termination instruction is used to instruct the background server to stop responding to the service request instruction of the target cloud desktop.

6. The method for managing work data according to any one of claims 4 to 5, characterized in that: The method further comprises: When the management node receives an application for extended use of the target cloud desktop configured by itself sent by the execution object, the management node sends a business recovery instruction to the background server; the business recovery instruction is used to instruct the background server to continue to respond to the business request instructions of the target cloud desktop.

7. The method for managing work data according to claim 1, characterized in that: After generating the log data preview page, the method further includes: Determining a confidentiality level of the log data; Based on the confidentiality level, a management operation on the log data is performed; the management operation includes recording the log data or deleting the data.

8. A work data management device, applied to a cloud desktop management system, the cloud desktop management system includes a management node and a background server, the background server supports the operation of multiple cloud desktops, characterized in that: The device comprises: An acquisition module, configured to enable the management node to acquire a work data file, wherein the work data file includes work information of a work item to be executed; An allocation module, configured to determine, based on the work data file, an execution object corresponding to the to-be-executed work item, and allocate a cloud desktop to the execution object; The processing module is used to obtain the log data generated in the process of the execution object executing the corresponding work item based on the cloud desktop, and generate a log data preview page based on the corresponding relationship between the cloud desktop corresponding to each execution object and the log data.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

11. A computer program product, characterized in that The computer program product comprises instructions, which, when executed, cause the method according to any one of claims 1 to 7 to be performed.

Images