CN117742864A

CN117742864A - Safe desktop screen capturing method, device, equipment and medium for remote control

Info

Publication number: CN117742864A
Application number: CN202311766581.5A
Authority: CN
Inventors: 谷金波; 马莉莉; 王秀青
Original assignee: Shenzhen Honghe Innovation Information Technology Co Ltd
Current assignee: Shenzhen Honghe Innovation Information Technology Co Ltd
Priority date: 2023-12-20
Filing date: 2023-12-20
Publication date: 2024-03-22

Abstract

The application is applicable to the technical field of computer remote control, and provides a safe desktop screen capturing method, device, equipment and medium for remote control, comprising the following steps: loading a first process and a second process in the equipment end; the first process has a SYSTEM right, and the second process does not have a SYSTEM right; establishing a communication connection and a data transmission channel between the first process and the second process; in response to detecting that the equipment end is in a secure desktop, performing screen capturing operation on the equipment end based on the first process to obtain desktop screen capturing data; the second process obtains the desktop screen capturing data through the communication connection and the data transmission channel; processing the desktop screen capturing data to generate encoded data; and transmitting the encoded data to the control terminal; the remote control method and the remote control device can realize remote control under the safety desktop of the windows system.

Description

Safe desktop screen capturing method, device, equipment and medium for remote control

Technical Field

The application belongs to the technical field of computer remote control, and particularly relates to a safe desktop screen capturing method, device, equipment and medium for remote control.

Background

Remote control is a function often used in the routine maintenance of computers. The computer at the controlled end needs to intercept the display content of the local desktop and then transmit the codes to the computer executing the remote maintenance task. The windows system' local desktop is affiliated with a window workstation, which has three types: secure desktops, default desktops (i.e., default desktops), and screen saver desktops. To ensure system security, windows operating systems may switch to a secure desktop when user login or privilege authentication is performed, and conventional applications associated with the default desktop cannot screen the secure desktop due to security restrictions of the windows system. Also, most open-source remote control utilities such as VNCs (Virtual Network Console, virtual network consoles) do not support access to secure desktops. This may affect smooth implementation of the remote control and may cause the remote control to be interrupted.

For example, for an installation/uninstallation software operation scenario, when the control end remotely installs software on the computer, under the influence of a policy of a windows system user account control (User Account Control, UAC), a prompt that needs to be allowed by a system login user can be popped up on the secure desktop. If the remote control method does not support the control scene under the safe desktop, the control end can be blacked out, so that the remote control operation cannot be continued. If the computer needs to be restarted in the maintenance process, the user login operation is triggered, so that the remote control operation cannot be continued.

Therefore, how to implement remote control under a secure desktop based on windows system is a problem facing the present day.

Disclosure of Invention

The embodiment of the application provides a method, a device, equipment and a medium for remotely controlling a safe desktop screen capture, which can solve the problem that remote control under a safe desktop of a windows system cannot be realized at present.

In a first aspect, an embodiment of the present application provides a secure desktop screen capturing method for remote control, where the secure desktop screen capturing method is used for a control end to remotely control a device end, and includes:

loading a first process and a second process in the equipment end; the first process has a SYSTEM right, and the second process does not have a SYSTEM right;

establishing a communication connection and a data transmission channel between the first process and the second process;

in response to detecting that the equipment end is in a secure desktop, performing screen capturing operation on the equipment end based on the first process to obtain desktop screen capturing data;

the second process obtains the desktop screen capturing data through the communication connection and the data transmission channel;

processing the desktop screen capturing data to generate encoded data; and

and sending the encoded data to the control end.

In a possible implementation manner of the first aspect, before the processing the desktop screen capture data to generate encoded data, the method further includes:

and responding to the detection that the equipment end is not in the secure desktop, and executing screen capturing operation on the equipment end based on the second process to obtain desktop screen capturing data.

In a possible implementation manner of the first aspect, the communication connection is established between the first process and the second process by:

the first process creates a process communication service interface;

the second process establishes the communication connection with the first process based on the process communication service interface.

In a possible implementation manner of the first aspect, the data transmission channel is established between the first process and the second process by:

the first process creates a shared memory, and takes the shared memory as a data transmission channel; the shared memory is used for storing the desktop screen capturing data.

In a possible implementation manner of the first aspect, the creating, by the first process, a shared memory includes:

the first process creates a file mapping object based on a file mapping interface;

the first process creates the shared memory based on the file map object.

In a possible implementation manner of the first aspect, the performing, based on the first process, a screen capturing operation on the device side to obtain desktop screen capturing data includes:

and the first process creates a display device context based on a graphic device interface, and executes screen capturing operation on the device side based on the display device context to obtain the desktop screen capturing data.

In a possible implementation manner of the first aspect, the establishing a communication connection and a data transmission channel between the first process and the second process includes:

responding to the connection established between the equipment end and the control end, establishing a communication connection and a data transmission channel between the first process and the second process, and generating a screen capturing instruction;

the responding to the detection that the equipment end is in the safe desktop, executing screen capturing operation on the equipment end based on the first process, and obtaining desktop screen capturing data comprises the following steps:

and responding to the screen capturing instruction and detecting that the equipment end is in the safe desktop, and executing screen capturing operation on the equipment end based on the first process to obtain desktop screen capturing data.

In a second aspect, an embodiment of the present application provides a secure desktop screen capturing device for remote control, configured to enable a control end to remotely control an equipment end, where the device includes:

the process loading module loads a first process and a second process in the equipment end; the first process has a SYSTEM right, and the second process does not have a SYSTEM right;

the process interaction module establishes communication connection and a data transmission channel between the first process and the second process;

the secure desktop screen capturing module is used for responding to the fact that the equipment end is in the secure desktop, and performing screen capturing operation on the equipment end based on the first process to obtain desktop screen capturing data;

the desktop screen capturing data acquisition module is used for acquiring the desktop screen capturing data through the communication connection and the data transmission channel by the second process;

the desktop screen capturing data processing module is used for processing the desktop screen capturing data to generate encoded data; and

and the coded data transmitting module is used for transmitting the coded data to the control end.

In a third aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the secure desktop screen capture method for remote control according to any one of the first aspects when the computer program is executed by the processor.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program which, when executed by a processor, implements the secure desktop screen capture method for remote control of any one of the first aspects above.

In a fifth aspect, embodiments of the present application provide a computer program product, which when run on an electronic device, causes the electronic device to perform the secure desktop screen capture method for remote control of any one of the first aspects above.

Compared with the prior art, the embodiment of the application has the beneficial effects that:

in the embodiment of the invention, the first process with the SYSTEM authority is created and loaded in the equipment end, communication connection is established between the first process and the second process without the SYSTEM authority, and then screen capturing is realized based on the first process when the equipment end is detected to be at the safe desktop, so that smoothness of remote control of the control end can be ensured no matter the equipment end is at the default desktop or the safe desktop, difficulty of remote maintenance of a computer is reduced, and use experience of a user at the control end is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following description will briefly introduce the drawings that are needed in the embodiments or the description of the prior art, it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a method for remotely controlling a secure desktop screen capture according to an embodiment of the present application;

FIG. 2 is a flow chart of a secure desktop screen capture method for remote control according to another embodiment of the present application;

FIG. 3 is a flow chart of a secure desktop screen capture method for remote control according to another embodiment of the present application;

FIG. 4 is a flow chart of a secure desktop screen capture method for remote control according to another embodiment of the present application;

FIG. 5 is a schematic structural view of a security desktop screen capture device for remote control according to another embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to another embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".

In addition, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.

Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

The terms referred to in this application are explained first:

a window station (window station) is created by a login process of a windows system, and when an interactive window station is created, three desktops are generated by default, including: secure desktops (i.e., winlogo desktops), screen saver desktops, and default desktops (i.e., default desktops). The desktop associated at the time of creation of the interactive window station is the default desktop. For a secure desktop, after system creation, it is activated when the user logs in. Such as when using Ctrl + Alt + Del combination keys, or when popping up the UAC pop-up window (depending on the system settings), is a secure desktop. The default desktop is the desktop that the windows operating system user sees after logging in, and common application programs are displayed on this desktop. The screen saver desktop wakes up after the screen saver is enabled.

Since computers are in the process of remote control, they typically switch between different types of desktops, such as between a default desktop and a secure desktop. The content of the default desktop and the content of the safe desktop need to be intercepted in the remote control process, so that the smoothness of the remote control process can be ensured, and the process can not be interrupted. Conventional applications associated with the default desktop can screen capture the default desktop, but not the secure desktop. This results in the need to implement interception and transmission of secure desktop content for windows systems if it is desired to ensure that the entire process of remote control including secure desktop content transmission is not interrupted.

As shown in FIG. 1, one embodiment of the present application provides a secure desktop screen capture method for remote control. The method is used for the control end to remotely control the equipment end. The control end and the equipment end can be respectively a computer. In this embodiment, the method includes the steps of:

s110, loading the first process and the second process in the equipment end. The first process has a SYSTEM right (i.e., a SYSTEM right) and the second process does not have a SYSTEM right. Specifically, the first process and the second process are respectively created in the step, and the first process has the SYSTEM authority, so that the content of the secure desktop can be intercepted after the secure desktop is associated based on the first process. Since the second process does not have the SYSTEM rights, the second process cannot intercept the content of the secure desktop, but the second process may intercept the desktop content under the default desktop.

In specific implementation, the first process may be registered as a service, and the service is loaded and run when the device side computer is started, that is, the operating system is started. Thus, after the service is started, the first process can be started by the SYSTEM user, and the SYSTEM authority can be owned. Wherein the working environment of the first process is associated to the secure desktop and inherits the SYSTEM rights of the registered service. The second process may be started when the device is started, or may be started when the second process needs to be used, which is not limited in this application. By way of example and not limitation, the first process described above may also be a process having root user rights.

S120, establishing a communication connection and a data transmission channel between the first process and the second process. In specific implementation, after the connection between the equipment end and the control end is detected, the connection can be communication connection, that is, the control end needs to remotely control the equipment end, so that real-time desktop content transmission of the equipment end is needed. Although the form of the device-side desktop content displayed at the control side is in the form of real-time video pictures, the real-time video pictures are formed from pictures frame by frame. Therefore, desktop content of the device end needs to be continuously intercepted, and a video stream is formed based on the intercepted pictures, namely, the video stream is displayed in the control end.

And then the communication connection and the data transmission channel are established between the first process and the second process of the equipment side. The communication connection is used for transmitting instructions, feedback information and the like between the first process and the second process. The data transmission channel is used for transmitting data between the first process and the second process, namely, transmitting the desktop screen capturing data intercepted by the first process to the second process, or notifying the storage address of the intercepted desktop screen capturing data to the second process and the like.

S130, in response to detecting that the equipment end is in the secure desktop, performing screen capturing operation on the equipment end based on the first process, and obtaining desktop screen capturing data. The embodiment can monitor the change of the windows desktop (i.e. whether the secure desktop and the default desktop are switched) based on the service registered according to the first process and the input desktop detection API interface, so as to determine whether the device side is in the secure desktop. Regarding the screen capture operation of the first process on the secure desktop, in some alternative embodiments, the windows system may be utilized to create a display device context with its own graphics device interface (Graphics Device Interface, GDI), and then copy screen content on the secure desktop based on the display device context, that is, implement performing the screen capture operation on the secure desktop at the device end. In other embodiments, other screen capturing operation modes can be adopted by those skilled in the art based on the first process, which is not limited in this application.

And S140, the second process obtains the desktop screen capturing data through the communication connection and the data transmission channel. Specifically, after the first process acquires the desktop screen capturing data, a notification message is sent to the second process based on the communication connection. And the first process provides the desktop screen capture data to the second process based on the data transmission channel. That is, the communication connection described above is used for information interaction between the first process and the second process. The data transmission channel is used for data interaction between the first process and the second process.

In a specific implementation, after the desktop screen capturing data is generated for the first process, the desktop screen capturing data can be directly sent to the second process based on the data transmission channel. A shared memory can also be established, both the first process and the second process can access the shared memory, after the first process stores the data into the shared memory, the first process sends related notification information to the second process, and then the second process can directly take the data out of the shared memory. This saves bandwidth transmission resource consumption.

S150, processing the desktop screen capturing data to generate encoded data. That is, the desktop screen capturing data can be converted into a data format which can be identified by the coding module of the device side based on the second process, and then the coding module of the device side is controlled by the second process to code and compress the data so as to generate coded data. The specific working process of the encoding module can be realized by referring to the related technology, and the description of this embodiment is omitted. The processing of this step is completed in the equipment end. In other embodiments, the control body of the step may be other processes in the device side, which is not limited in this application.

And S160, transmitting the encoded data to a control terminal. The step is that the device side sends the encoded data to the control side, specifically, the encoded data may be sent to the control side based on the second process in the device side, or may be sent to the control side based on other conventional processes in the device side. The present application is not limited in this regard.

The embodiment sends the processed coded data to the control end based on the second process instead of directly sending the data based on the first process, so that on one hand, memory resources can be saved, and the problem of memory resource consumption caused by the fact that the first process occupies larger memory resources is avoided; on the other hand, the second process belongs to a conventional process of the equipment end, can be started as required, does not need to run all the time after the equipment end is started, can be closed when not needed, and can not be closed at any time; therefore, the second process can be turned off after the data transmission is completed, so that the memory resource is further saved.

In the embodiment of the application, a first process with a SYSTEM right is created and loaded in a device side, communication connection is established between the first process and a second process without the SYSTEM right, and then when the device side is detected to be in a safe desktop, screen capturing is realized based on the first process; in addition, when the equipment end is detected to be on a default desktop, screen capturing is realized based on a second process; therefore, the smoothness of remote control of the control end can be guaranteed under the condition that the equipment end is positioned on a default desktop or a safe desktop, the difficulty of remote maintenance of a computer is reduced, and the use experience of a user of the control end is improved.

The embodiment of the application realizes the remote desktop data transmission under the secure desktop of the equipment end, and can be suitable for use scenes such as user login, logout, software installation, driver installation, window computer restarting control and the like, thereby expanding the available range of a remote maintenance system and leading the applicability of remote control to be wider.

In another embodiment of the present application, another secure desktop screen capture method for remote control is also disclosed. As shown in fig. 2, the method further includes, based on the corresponding embodiment of fig. 1, between step S120 and step S130, the steps of:

s170, judging whether the equipment end is positioned on a safe desktop.

Between step S170 and step S150, further comprising the steps of:

and S180, responding to the fact that the equipment end is not in the safe desktop, and executing screen capturing operation on the equipment end based on a second process to obtain desktop screen capturing data.

In the embodiment, when the equipment end is detected to be in a safe desktop, screen capturing is realized based on a first process; in addition, when the equipment end is detected to be on a default desktop, screen capturing is realized based on a second process; therefore, the smoothness of remote control of the control end can be guaranteed under the condition that the equipment end is positioned on a default desktop or a safe desktop, the difficulty of remote maintenance of a computer is reduced, and the use experience of a user of the control end is improved.

In some alternative embodiments, based on the corresponding embodiments of fig. 1 or fig. 2, a communication connection is established between the first process and the second process as follows:

s121, the first process creates a process communication service interface.

And S122, the second process establishes the communication connection with the first process based on the process communication service interface.

In this embodiment, the process communication service interface is a windows PIPE (windows PIPE) function interface (such as a CreateNamedPipe application interface), and the PIPE interface created by the first process is set to be accessible by all users of the windows system. This allows a conventional program, including the second process, to communicate with the first process.

In some alternative embodiments, on the basis of any of the above embodiments, for example, as shown in fig. 3, taking an example on the basis of the corresponding embodiment of fig. 1, step S120 is replaced by step S123: and establishing communication connection between the first process and the second process, wherein the first process creates a shared memory, and the shared memory is used as a data transmission channel between the first process and the second process. The shared memory is used for storing the desktop screen capturing data. That is, the embodiment establishes a data transmission channel between the first process and the second process by the method corresponding to step S123 described above.

That is, both the first process and the second process may access the shared memory. The first process intercepts desktop contents under the secure desktop, and stores desktop screen capturing data in a shared memory after the desktop screen capturing data are obtained. The first process then sends relevant notification information to the second process, which may include the screen capture execution result and shared memory identification information. The shared memory identification information may be information such as a name or ID of the shared memory. The second process may fetch data from the shared memory according to the related notification information. This saves bandwidth transmission resources consumed and memory resources.

Optionally, the relevant notification information sent by the first process to the second process may be in JSON coding format, for example { Ret: the screen shot return value, desktop: name of shared memory }, by way of example and not limitation, may be 0 or-1, where 0 indicates that the screen shot was successful. -1 indicates a screen capture failure or that the system is not now under a secure desktop. The notification information is based on the transmission mode of the JSON coding format, so that the light weight of the remote control desktop content transmission is improved, the data transmission efficiency is improved, and the smoothness of the desktop data transmission, namely the remote control is improved.

By way of example, and not limitation, the content contained in the shared memory and the meaning explanation corresponding to each content can refer to the following table 1, and the application is not limited thereto.

TABLE 1

In some alternative embodiments, step S123 includes, based on the corresponding embodiment of fig. 3, steps of:

the first process creates a file map object based on the file map interface, and the first process creates the shared memory based on the file map object. The file mapping interface is a createFilemapping interface.

In some alternative embodiments, step S120 is replaced with step S124, as shown in fig. 4, based on the corresponding embodiment of fig. 1.

And establishing a communication connection and a data transmission channel between the first process and the second process in response to the connection establishment between the equipment end and the control end, and generating a screen capturing instruction.

Step S130 is replaced with step S131:

and responding to the screen capturing instruction and detecting that the equipment end is in the safe desktop, and executing screen capturing operation on the equipment end based on a first process to obtain desktop screen capturing data.

Specifically, the device side and the control side establish a connection, and the first process provides a process communication service interface which can be accessed by any conventional process in the device side, and then the second process accesses the process communication service interface, so that a communication connection can be established with the first process.

The screen capturing instruction may be generated by the device side or the control side, which is not limited in this application. If the screen capturing instruction is generated at the control end, the control end sends the screen capturing instruction to the equipment end, and the equipment end sends the screen capturing instruction to the first process and the second process respectively. In the process of remote control connection, the desktop content of the equipment end needs to be continuously transmitted in real time, so that the equipment end needs to continuously send screen capturing instructions to the first process and the second process.

Optionally, the screen capturing instruction may be generated using a JSON coding format, for example { Cmd: desktop, ver: "HH10" }, which is favorable for improving the light weight of remote control desktop content transmission, improving the data transmission efficiency, and improving the smoothness of desktop data transmission, that is, remote control.

It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.

The method and the device for processing the image data can be used for processing the image data, and the method and the device for processing the image data can be used for processing the image data.

Corresponding to the secure desktop screen capturing method described in the above embodiments, fig. 5 shows a block diagram of a secure desktop screen capturing device for remote control according to an embodiment of the present application, and for convenience of explanation, only a portion related to the embodiment of the present application is shown.

Referring to fig. 5, the apparatus includes:

the process loading module 51 loads the first process and the second process in the device side. The first process has a SYSTEM right and the second process does not have a SYSTEM right.

The process interaction module 52 establishes a communication connection and a data transmission channel between the first process and the second process.

The secure desktop screen capture module 53, in response to detecting that the device side is in the secure desktop, performs a screen capture operation on the device side based on the first process, and obtains desktop screen capture data.

The desktop screen capturing data obtaining module 54 obtains the desktop screen capturing data through the communication connection and the data transmission channel by the second process.

The desktop screen capture data processing module 55 processes the desktop screen capture data to generate encoded data.

And

The encoded data transmission module 56 transmits the encoded data to the control terminal.

In some alternative embodiments, on the basis of the corresponding embodiment of fig. 5, the apparatus further includes:

the judging module is used for judging whether the equipment end is positioned on the safe desktop or not.

And the unsafe desktop screen capturing module is used for responding to the fact that the equipment end is not in the safe desktop, and executing screen capturing operation on the equipment end based on a second process to obtain desktop screen capturing data.

In some alternative embodiments, the process interaction module 52 is further configured to create a process communication service interface, and the second process establishes the communication connection with the first process based on the process communication service interface.

In some alternative embodiments, the process interaction module 52 is further configured to create a shared memory, and use the shared memory as a data transmission channel between the first process and the second process. The shared memory is used for storing the desktop screen capturing data.

In some alternative embodiments, the process interaction module 52 creates a file map object based on the file map interface, and the first process creates the shared memory based on the file map object.

In some alternative embodiments, the process interaction module 52 establishes a communication connection and a data transmission channel between the first process and the second process in response to the device side and the control side establishing a connection, and generates the screen capturing instruction. The secure desktop screen capture module 53 performs a screen capture operation on the device side based on the first process in response to the screen capture instruction and detecting that the device side is in the secure desktop, and obtains the desktop screen capture data.

It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein again.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.

The embodiment of the application also provides an electronic device, as shown in fig. 6, the electronic device 60 includes: at least one processor 601, a memory 602 and a computer program 603 stored in the memory and executable on the at least one processor, which processor implements the steps of any of the various method embodiments described above when it executes the computer program.

Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, implements steps that may implement the various method embodiments described above.

Embodiments of the present application provide a computer program product which, when run on a mobile terminal, causes the mobile terminal to perform steps that may be performed in the various method embodiments described above.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a camera device/electronic apparatus, a recording medium, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other manners. For example, the apparatus/network device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. A secure desktop screen capturing method for remote control, which is used for a control end to remotely control a device end, the method comprising:

processing the desktop screen capturing data to generate encoded data; and

and sending the encoded data to the control end.

2. The secure desktop screen capture method of claim 1, wherein prior to said processing said desktop screen capture data to generate encoded data, said method further comprises:

3. The secure desktop screen capture method of claim 1 or 2, wherein the communication connection is established between the first process and the second process by:

the first process creates a process communication service interface;

4. The secure desktop screen capture method of claim 3, wherein the data transmission channel is established between the first process and the second process by:

5. The secure desktop screen capture method of claim 4, wherein the first process creates a shared memory comprising:

the first process creates the shared memory based on the file map object.

6. The method of claim 5, wherein the performing a screen capture operation on the device side based on the first process to obtain desktop screen capture data comprises:

7. The secure desktop screen capture method according to claim 1 or 2, wherein said establishing a communication connection and a data transmission channel between said first process and said second process comprises:

8. A secure desktop screen capture device for remote control, characterized in that it is configured to remotely control a device end by a control end, the device comprising:

9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 7 when the computer program is executed.

10. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method according to any one of claims 1 to 7.