Screening method and device, screening system, user equipment and cloud server

Abstract

The embodiment of the application provides a screenshot method and device, comprising: in response to a screenshot triggering operation, generating a screenshot event and sending the screenshot event to a cloud server; acquiring a screenshot request sent by the cloud server according to the screenshot event; calling a screenshot tool according to the screenshot request to perform screenshot, and sending obtained screenshot content to the cloud server, so that the cloud server generates a screenshot result according to the screenshot content and a target cloud service application; and acquiring the screenshot result sent by the cloud server. In the case that the cloud side screenshot service is triggered and the cloud side screenshot process of the target cloud service application is intervened, the actual screenshot content is obtained according to the content processed by the user equipment on the desktop background, the screenshot content is consistent with the expectation of the user, so that the user can reach a non-perception experience whether the cloud service application is currently used or the local application is currently used.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a screenshot method, apparatus, system, user equipment, cloud server, and machine-readable medium. Background Technology

[0002] Cloud service applications are virtualized cloud-based applications. The cloud can bear the operating overhead of cloud service applications, and users can access and display the running window of cloud service applications through their devices, making the user end and the cloud a closely coordinated whole.

[0003] In related technologies, the implementation of screenshot functionality for cloud service applications specifically includes: the user device initiates a screenshot request through user operation, the cloud service application responds to the screenshot request, takes a screenshot in the cloud runtime environment to obtain the screenshot result, and then feeds the screenshot result back to the user device.

[0004] However, the inventors discovered through research that in the current solution, taking screenshots in the cloud environment results in a significant discrepancy between the screenshot results and expectations due to the differences between the cloud environment and the user's device environment, thus reducing the user experience. Summary of the Invention

[0005] This application provides a screenshot method to address the problem in related technologies where the screenshot result differs significantly from the expected result, thus reducing the user experience.

[0006] Accordingly, embodiments of this application also provide a screenshot device, a user device, a screenshot system, a cloud server, and a machine-readable medium to ensure the implementation and application of the above methods.

[0007] To address the aforementioned problems, this application discloses a screenshot method applied to a user device, comprising:

[0008] In response to a screenshot trigger operation, a screenshot event is generated and sent to the cloud server;

[0009] Obtain the screenshot request sent by the cloud server based on the screenshot event;

[0010] The screenshot tool is invoked to take a screenshot according to the screenshot request, and the obtained screenshot content is sent to the cloud server so that the cloud server can generate a screenshot result based on the screenshot content and the target cloud service application.

[0011] Obtain the screenshot result sent by the cloud server.

[0012] This application discloses a screenshot method applied to a cloud server, the method comprising:

[0013] Get screenshot events sent by the user's device;

[0014] Based on the screenshot event, a screenshot request is generated and sent to the user device;

[0015] Obtain the screenshot content captured by the user equipment based on the screenshot request;

[0016] Based on the screenshot content and the target cloud service application, a screenshot result is generated and sent to the user device.

[0017] Optionally, if the screenshot event is generated based on a screenshot trigger operation by the user device on a screenshot control displayed in the interface of the target cloud service application, then the step of generating a screenshot request and sending it to the user device according to the screenshot event includes:

[0018] Based on the screenshot event, the screenshot service interface is called to trigger the screenshot service of the cloud server;

[0019] The screenshot service of the cloud server is used to initiate a screenshot of the target cloud service application, generate a screenshot request, and send the screenshot request to the user device in accordance with the cloud service transmission protocol.

[0020] Optionally, the screenshot content is the content obtained by the user device in response to the screenshot operation on the screenshot interface, and the screenshot interface includes the interface of the target cloud service application displayed by the user device and the desktop background of the user device.

[0021] The step of generating a screenshot result based on the screenshot content and the target cloud service application includes:

[0022] The screenshot content is stored in a storage area associated with the screenshot service of the target cloud service application, and a screenshot result containing the access address of the screenshot content in the storage area is generated.

[0023] Optionally, the screenshot content is a full-screen image displayed on the user device;

[0024] The step of generating a screenshot result based on the screenshot content and the target cloud service application includes:

[0025] Use a screenshot tool to capture the full-screen display image and obtain the screenshot image;

[0026] The screenshot image is stored in a storage area associated with the screenshot service of the target cloud service application, and a screenshot result containing the access address of the screenshot image in the storage area is generated.

[0027] Optionally, the step of calling a screenshot tool to capture the full-screen display image and obtaining a screenshot image includes:

[0028] Replace the current display screen with the full-screen image;

[0029] The simulated screenshot cursor event sent by the user device is obtained. The simulated screenshot cursor event is a cursor event generated for the simulated screenshot interface displayed by the user device. The simulated screenshot interface displays the full-screen image.

[0030] Based on the simulated screenshot cursor event, a screenshot tool is invoked to capture a screenshot image from the full-screen display image shown on the cloud server.

[0031] Optionally, generating the screenshot result and sending it to the user device includes:

[0032] The screenshot result is sent to the user device through the target cloud service application according to the preset cloud service transmission protocol.

[0033] This application discloses a screenshot device applied to a user device, the device comprising:

[0034] The response module is used to respond to the screenshot trigger operation, generate a screenshot event, and send it to the cloud server.

[0035] The first acquisition module is used to acquire the screenshot request sent by the cloud server according to the screenshot event;

[0036] The screenshot module is used to call the screenshot tool to take a screenshot according to the screenshot request, and send the obtained screenshot content to the cloud server so that the cloud server can generate a screenshot result based on the screenshot content and the target cloud service application;

[0037] The second acquisition module is used to acquire the screenshot result sent by the cloud server.

[0038] This application discloses a screenshot device applied to a cloud server, the device comprising:

[0039] The third acquisition module is used to acquire screenshot events sent by the user's device;

[0040] The generation module is used to generate a screenshot request based on the screenshot event and send it to the user device;

[0041] The fourth acquisition module is used to acquire the screenshot content captured by the user equipment based on the screenshot request;

[0042] The sending module is used to generate a screenshot result based on the screenshot content and the target cloud service application, and send it to the user device.

[0043] This application discloses a screenshot system, including: a user device and a cloud server;

[0044] The user equipment is configured to: generate a screenshot event and send it to the cloud server in response to a screenshot trigger operation; obtain a screenshot request sent by the cloud server according to the screenshot event; call a screenshot tool to take a screenshot according to the screenshot request, and send the obtained screenshot content to the cloud server so that the cloud server can generate a screenshot result based on the screenshot content and the target cloud service application; and obtain the screenshot result sent by the cloud server.

[0045] The cloud server is used to: acquire screenshot events sent by user devices; generate screenshot requests based on the screenshot events and send them to the user devices; acquire screenshot content captured by the user devices based on the screenshot requests; and generate screenshot results based on the screenshot content and the target cloud service application and send them to the user devices.

[0046] This application also discloses a user equipment, including: a processor; and a memory storing executable code thereon, which, when executed, causes the processor to perform one or more methods as described in this application.

[0047] This application discloses a cloud server, including: a processor; and a memory storing executable code thereon, wherein when the executable code is executed, the processor performs one or more methods as described in this application embodiment.

[0048] This application also discloses one or more machine-readable media storing executable code thereon, which, when executed, causes a processor to perform one or more methods as described in this application.

[0049] Compared with related technologies, the embodiments of this application have the following advantages:

[0050] In this embodiment, even though the cloud-side screenshot service is triggered and the cloud-side screenshot process for the target cloud service application is initiated when the cloud-side operating environment and the user device-side operating environment have different styles, the actual screenshot content is processed based on the content of the screenshot taken by the user device of its own desktop environment. Therefore, the screenshot content is consistent with the user's expectations, so that the user can be unaware of whether they are currently using a cloud service application or a local application, thus improving the smoothness of the user's use of cloud service applications. Attached Figure Description

[0051] Figure 1 This is a system architecture diagram of a screenshot method according to an embodiment of this application;

[0052] Figure 2 This is an interactive diagram of one screenshot implementation of an embodiment of this application;

[0053] Figure 3 This is an interactive diagram of another screenshot implementation of the present application;

[0054] Figure 4 This is a schematic diagram illustrating an implementation scenario of a video platform cloud service application according to an embodiment of this application;

[0055] Figure 5 This is a schematic diagram illustrating an implementation scenario of an e-commerce cloud service application according to an embodiment of this application;

[0056] Figure 6 This is a schematic diagram illustrating an implementation scenario of a logistics cloud service application according to an embodiment of this application;

[0057] Figure 7 This is a flowchart illustrating the steps of a screenshot method according to an embodiment of this application;

[0058] Figure 8 This is a flowchart illustrating the steps of another screenshot method according to an embodiment of this application;

[0059] Figure 9 This is a flowchart illustrating the specific steps of a screenshot method according to an embodiment of this application;

[0060] Figure 10 This is a flowchart illustrating the specific steps of another screenshot method according to an embodiment of this application;

[0061] Figure 11 This is a block diagram of a screenshot device according to an embodiment of this application;

[0062] Figure 12 This is a block diagram of another screenshot device according to an embodiment of this application;

[0063] Figure 13 This is a block diagram of a screenshot system according to an embodiment of this application;

[0064] Figure 14 This is a schematic diagram of the structure of a device provided in an embodiment of this application. Detailed Implementation

[0065] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0066] To enable those skilled in the art to better understand this application, the concepts involved in this application are explained below:

[0067] Cloud server: refers to a computing unit deployed in the cloud. User devices can access cloud service applications running on the cloud server to obtain the services provided by the cloud service applications. Cloud server deployment is simple and efficient, secure and reliable, and its processing capacity can be scalable. Cloud server management is simpler and more efficient than physical server management. Users do not need to purchase expensive hardware in advance to obtain services by accessing the cloud server.

[0068] Cloud service applications: These are applications that enable interaction between user devices and the cloud. Cloud service applications can pass their running windows to the user device for display. User interactions on the user device can be synchronized to the cloud for the cloud service application to respond to. The operating overhead of cloud service applications is in the cloud, which reduces the overhead on the user device and makes the user unaware of cloud access. That is, it achieves a seamless experience, making it impossible for the user to distinguish whether they are using a cloud service application or a local application.

[0069] Screenshot trigger operation: The operation performed by the user on the running window of the cloud service application displayed on the user's device to trigger the screenshot service. The screenshot trigger operation can be the user clicking the screenshot control with the cursor, or the user triggering the physical button of the screenshot function.

[0070] Screenshot event: This can inform the cloud server of the event information that the user's device has triggered the screenshot service. It can include cursor operation information of clicking the screenshot control or trigger operation information of the physical button of the screenshot function.

[0071] Screenshot content: The image captured by the specific screenshot operation.

[0072] Screenshot result: The screenshot result generated after binding the screenshot content with the cloud service application. The user device can obtain the screenshot content provided by the cloud service application through the screenshot result.

[0073] Screenshot tool: A software tool used to provide screenshot services. Screenshot tools can run on user devices and cloud servers.

[0074] Screenshot service: This service is used to implement screenshot confirmation triggering, screenshot tool invocation, screenshot content acquisition, and content injection.

[0075] Cloud service transmission protocol: Provides the protocol content for information exchange between the user device side and the cloud server side.

[0076] The screenshot method in this application embodiment can be specifically applied to screenshot scenarios during the use of cloud service applications running in the cloud by user devices. In a related technical process, the cloud service application responds to a screenshot request initiated by the user device, takes a screenshot in the cloud runtime environment to obtain the screenshot result, and feeds the screenshot result back to the user device. However, due to the difference between the runtime environment of the cloud and the runtime environment of the user device, the screenshot result may differ significantly from the expectation. For example, if the wallpaper of the cloud runtime environment is a default black background, while the wallpaper of the user device runtime environment is a user-customized landscape photo, the above screenshot method will result in the user obtaining a screenshot of a black wallpaper, which contradicts the user's expectation (to obtain a screenshot containing a custom landscape wallpaper). This causes the user to perceive the use of the cloud service application differently from local applications, thus reducing the user experience of the cloud service application.

[0077] To address the aforementioned issues, this embodiment of the application allows a user device to generate a screenshot event based on a screenshot trigger operation while using a target cloud service application. This event is then sent to a cloud server, which triggers a screenshot service for the target cloud service application. Instead of performing a screenshot on the cloud desktop, the cloud server generates a screenshot request and sends it to the user device. The user device then activates its own screenshot service, uses a screenshot tool to take a screenshot on its desktop, and sends the screenshot to the cloud server. The cloud server, based on its screenshot service, binds the screenshot to the target cloud service application and simultaneously generates a screenshot result for retrieving the screenshot, which is sent to the user device. The user device can then retrieve the screenshot content using this result when needed. Thus, even when the cloud and user device operating environments differ, the screenshot on the user device side still yields the same result as the user expects, providing a seamless user experience regardless of whether they are using a cloud service application or a local application.

[0078] Reference Figure 1 This document illustrates a system architecture diagram of a screenshot method provided in an embodiment of this application, including a cloud server and a user device. The cloud server runs a target cloud service application, a cloud-side screenshot service, and a cloud-side screenshot tool. The cloud server also includes a screenshot detection module and a content injection module, which can be software functional modules included in the target cloud service application, respectively. The user device can receive and display the running window of the target cloud service application transmitted through the cloud server. The user device runs a client-side screenshot service and a client-side screenshot tool. The cloud server and the user device can interact via a cloud service transmission protocol. The cloud service transmission protocol can specifically define the transmission methods and data formats for messages, events, and information.

[0079] In the embodiments of this application, reference is made to Figure 1 The implementation environment of cloud service applications specifically refers to the cloud service applications running on cloud servers, which bear the operating overhead of the cloud service applications. In order for users to use cloud service applications, the cloud server can pass the running window of the cloud service application to the user's device for display. The interactive operations performed by the user in the running window on the user's device can be fed back to the cloud server for the cloud service application to respond, thereby achieving the goal of users using cloud service applications without being aware of them.

[0080] Specifically, this application provides two methods for taking screenshots:

[0081] In one implementation of screenshotting, refer to Figure 2 This diagram illustrates an interactive implementation of a screenshot method provided in this application. When a screenshot operation is required during the running of a target cloud service application, step S11 can be executed: the user can perform a screenshot trigger operation on the user device (e.g., click the "Screenshot" button in the running window of the target cloud service application). The user device responds to the screenshot trigger operation, generates a screenshot event, and sends it to the cloud service application on the cloud server. The screenshot detection module of the cloud service application can determine that a screenshot operation targeting the target cloud service application is currently being performed based on the screenshot event. At this time, the screenshot detection module can execute step S12 to further call the cloud-side screenshot service. The cloud-side screenshot service executes step S13 to intervene in the application screenshot and generate a screenshot request, which is sent to the end-side screenshot service of the user device. The client-side screenshot service can execute S14 upon receiving a screenshot request, invoking the client-side screenshot tool to enter screenshot mode. At this time, the cloud service application's window on the user's device will enter the screenshot interface. The user can then execute S15 to input screenshot operations, which the client-side screenshot service will then execute S16 to obtain the screenshot content based on the screenshot operations and send the screenshot content to the cloud server's cloud-side screenshot service. The cloud-side screenshot service can then execute S17 to bind the screenshot content with the target cloud service application (implemented by the content injection module), generating the screenshot result. The screenshot result can then be sent to the user's device, and the user can retrieve the screenshot content based on the result when needed.

[0082] In the above Figure 2 In the screenshot process, although the cloud-side screenshot service is triggered and the cloud-side screenshot process of the target cloud service application is intervened, the actual screenshot action occurs in the desktop environment of the running window on the user's device. Thus, the screenshot content obtained is based on the user's device desktop background and the content obtained from the cloud-side window on the device side. This screenshot content is consistent with the user's expectation (to obtain screenshot content that includes the user's device desktop background), thereby enabling the user to achieve a seamless experience regardless of whether they are currently using a cloud service application or a local application.

[0083] In another implementation of the screenshot method, refer to Figure 3 This diagram illustrates an interactive representation of another screenshot implementation method provided in this application. When a screenshot operation is required during the operation of a target cloud service application, step S21 can be executed: the user can perform a screenshot trigger operation on the user device (e.g., click the "Screenshot" button in the running window of the target cloud service application). The user device responds to the screenshot trigger operation, generates a screenshot event, and sends it to the cloud service application on the cloud server. The screenshot detection module of the cloud service application can determine that a screenshot operation targeting the target cloud service application is currently being performed based on the screenshot event. At this time, the screenshot detection module can execute step S22 to further call the cloud-side screenshot service. The cloud-side screenshot service executes step S23 to intervene in the application screenshot and generate a screenshot request, which is sent to the end-side screenshot service on the user device. The end-side screenshot service can execute step S24 based on the screenshot request to call the end-side screenshot tool to capture the full-screen display image of the user device's desktop as the screenshot content and send the screenshot content to the cloud-side screenshot service on the cloud server. The cloud-side screenshot service can execute S25, replacing the cloud-side desktop background with a full-screen image of the user's device desktop, and then obtaining the screenshot content based on the user's screenshot operation. Afterwards, the cloud-side screenshot service can execute S26, binding the screenshot content with the target cloud service application (implemented by the content injection module) to generate the screenshot result. The screenshot result can then be sent to the user's device, and the user can retrieve the screenshot content based on the screenshot result when needed.

[0084] In the above Figure 3 In the screenshot process, although the cloud-side screenshot service is triggered and the cloud-side screenshot process of the target cloud service application is intervened, the full-screen display image of the user's device desktop captured by the user device can be sent to the cloud-side screenshot service. The cloud-side screenshot service can replace the cloud-side desktop background with this full-screen display image. Furthermore, the cloud-side screenshot can obtain the screenshot content based on the user's screenshot operation on the full-screen display image. The obtained screenshot content is based on the full-screen display image of the user device, and this screenshot content is consistent with the user's expectation (to obtain screenshot content including the user device's desktop background). Thus, the user can achieve a seamless experience of not being aware of whether they are currently using a cloud service application or a local application.

[0085] It should be noted that the screenshot method provided in this application embodiment can be used in several specific scenarios, as follows:

[0086] In one implementation, refer to Figure 4This illustration shows an implementation scenario of a video platform cloud service application provided in this application, including: a user device and a video platform cloud server. The video platform cloud server runs a video platform cloud service application. The user device can receive and display the running window of the video platform cloud service application transmitted by the video platform cloud server. Specifically, the user can watch the video content provided by the video platform cloud service application through the running window displayed on the user device. Since the video platform cloud service application runs on the cloud side, the system overhead of the user device is reduced. When the user needs to take a screenshot, it follows the above... Figure 2 or Figure 3 Taking screenshots in this way ensures that the screenshot content matches the user's expectations, thus providing a seamless experience for the user, making it clear whether they are currently using a cloud service application or a local application.

[0087] In another implementation, refer to Figure 5 This illustration shows an implementation scenario of an e-commerce cloud service application provided in this application, including: a user device and an e-commerce cloud server. The e-commerce cloud server runs an e-commerce cloud service application, and the user device can receive and display the running window of the e-commerce cloud service application transmitted by the e-commerce cloud server. Specifically, the user can browse and purchase goods through the running window displayed on the user device. Since the e-commerce cloud service application runs on the cloud side, the system overhead of the user device is reduced. When the user needs to take a screenshot, it follows the above... Figure 2 or Figure 3 Taking screenshots in this way ensures that the screenshot content matches the user's expectations, thus providing a seamless experience for the user, making it clear whether they are currently using a cloud service application or a local application.

[0088] In another implementation, refer to Figure 6 This illustration shows an implementation scenario of a logistics cloud service application provided in this application, including: a user device and a logistics cloud server. The logistics cloud server runs a logistics cloud service application, and the user device can receive and display the running window of the logistics cloud service application transmitted through the logistics cloud server. Specifically, when a user sends or signs for a package through the running window displayed on the user device, the system overhead of the user device is reduced because the logistics cloud service application runs on the cloud side. When the user needs to take a screenshot, it follows the above... Figure 2 or Figure 3 Taking screenshots in this way ensures that the screenshot content matches the user's expectations, thus providing a seamless experience for the user, making it clear whether they are currently using a cloud service application or a local application.

[0089] It should be noted that the process of obtaining screenshot events, screenshot requests, screenshot content, screenshot results, and other information, signals, or data used in the embodiments of this application is carried out in compliance with the relevant data protection laws and policies of the country where the location is located, and with the authorization granted by the owner of the corresponding device.

[0090] In this embodiment, even though the cloud-side screenshot service is triggered and the cloud-side screenshot process for the target cloud service application is initiated when the cloud-side operating environment and the user device-side operating environment have different styles, the actual screenshot content is processed based on the content of the screenshot taken by the user device of its own desktop environment. Therefore, the screenshot content is consistent with the user's expectations, so that the user can be unaware of whether they are currently using a cloud service application or a local application, thus improving the smoothness of the user's use of cloud service applications.

[0091] Reference Figure 7 It illustrates a flowchart of a screenshot method provided in an embodiment of this application, applied to a user device, the method including:

[0092] Step 101: In response to the screenshot trigger operation, generate a screenshot event and send it to the cloud server.

[0093] In this embodiment of the application, the implementation environment of the cloud service application specifically refers to the cloud service application running on a cloud server, so that the cloud server bears the operating overhead of the cloud service application. In order for users to use the cloud service application, the cloud server can pass through the running window of the cloud service application to the user device for display. The interactive operations performed by the user in the running window of the user device can be fed back to the cloud server for the cloud service application to respond, thereby achieving the purpose of the user using the cloud service application without being aware of it.

[0094] When taking a screenshot while using a cloud service application, the user can perform a screenshot trigger operation on the user device (such as clicking the "Screenshot" button in the running window of the target cloud service application). The user device responds to the screenshot trigger operation, generates a screenshot event, and sends it to the cloud service application on the cloud server. The screenshot event is used to inform the cloud service application that the user has triggered a screenshot.

[0095] Step 102: Obtain the screenshot request sent by the cloud server based on the screenshot event.

[0096] In this embodiment of the application, in order to avoid the problem of decreased user experience caused by screenshots obtained from cloud server desktop environments that differ significantly from user expectations, this embodiment of the application can specifically take a screenshot of the user device's own desktop environment to obtain screenshot content, so as to ensure that the screenshot content meets user expectations. Specifically, although the screenshot event triggers the cloud server's screenshot service and intervenes in the cloud-side screenshot process of the target cloud service application, the cloud server will send a screenshot request to the user device so that the user device can obtain its own desktop environment as the screenshot content.

[0097] Step 103: Call the screenshot tool to take a screenshot according to the screenshot request, and send the obtained screenshot content to the cloud server so that the cloud server can generate the screenshot result based on the screenshot content and the target cloud service application.

[0098] In this embodiment, the user device can call the screenshot tool of the user device according to the screenshot request to take a screenshot of the user device's desktop environment and obtain the screenshot content. The screenshot content can be sent to the cloud server, so that the cloud server can bind the screenshot content with the target cloud service application according to the screenshot content and generate the same screenshot result as the user expects.

[0099] For example, the wallpaper of the cloud operating environment is a default black background, while the wallpaper of the user's device operating environment is a user-defined landscape photo. The screenshot method of this application embodiment can take a screenshot based on the desktop environment of the user's device with the user's customized landscape photo wallpaper to obtain the screenshot content, which is the same as the user's expectation (to obtain screenshot content containing the customized landscape wallpaper).

[0100] Step 104: Obtain the screenshot result sent by the cloud server.

[0101] In this embodiment, the cloud server can bind screenshot content to a target cloud service application, thereby realizing the original process logic of the cloud-side screenshot service on the cloud server side (capturing a screenshot file for the target cloud service application). Specifically, the binding action can be to store the screenshot content in a storage area associated with the target cloud service application, completing the binding association between the screenshot content and the target cloud service application. Furthermore, the cloud server can generate a screenshot result including an access address for accessing the screenshot content and send it to the user device. When the user needs to obtain the screenshot content later, they can obtain the screenshot content according to the access address in the screenshot result.

[0102] Optionally, step 104 can be implemented by sending the screenshot to the cloud server according to the cloud service transmission protocol.

[0103] Specifically, cloud service transmission protocols can define the transmission methods and data formats for messages, events, and information. This allows cloud servers and user devices to interact with screenshot content via cloud service transmission protocols.

[0104] In summary, this embodiment of the application, even when the cloud-side screenshot service is triggered and the cloud-side screenshot process for the target cloud service application is intervened, the actual screenshot content is processed based on the content of the screenshot of the user's own desktop background. Therefore, the screenshot content is consistent with the user's expectations, so that the user can be unaware of whether they are currently using a cloud service application or a local application, thus improving the smoothness of the user's use of cloud service applications.

[0105] Reference Figure 8 It illustrates a flowchart of another screenshot method provided in an embodiment of this application, applied to a cloud server, the method including:

[0106] Step 201: Obtain the screenshot event sent by the user device.

[0107] In this embodiment of the application, the screenshot event is event information generated by the user device after the user performs the screenshot trigger operation. It is used to inform the cloud service application that the current user has triggered a screenshot, and the cloud server calls the cloud-side screenshot service to intervene in the screenshot process for the target cloud service application.

[0108] Step 202: Based on the screenshot event, generate a screenshot request and send it to the user device.

[0109] In this embodiment of the application, in order to avoid the problem of decreased user experience caused by screenshot results that differ greatly from user expectations due to the desktop environment of the cloud server, the cloud server can generate a screenshot request based on the screenshot event and send it to the user device to notify the user device to take a screenshot of its own desktop environment to obtain the screenshot content, so as to ensure that the screenshot content meets the user's expectations.

[0110] Step 203: Obtain the screenshot content captured by the user device based on the screenshot request.

[0111] In this step, since the screenshot is taken by the user's device based on its own desktop environment, the screenshot content can meet the user's expectations, avoiding the user's perception that there is a difference in the screenshot content, and achieving the goal of the user using cloud service applications without being aware of it.

[0112] Step 204: Generate screenshot results based on the screenshot content and the target cloud service application, and send them to the user's device.

[0113] In this embodiment, the cloud server can bind the screenshot content to the target cloud service application, thereby realizing the original process logic of the cloud-side screenshot service on the cloud server side (capturing a screenshot file for the target cloud service application). Specifically, the screenshot content can be stored in a storage area associated with the target cloud service application to complete the binding association between the screenshot content and the target cloud service application. Furthermore, the cloud server can generate a screenshot result including an access address for accessing the screenshot content and send it to the user device.

[0114] In summary, this embodiment of the application, even when the cloud-side screenshot service is triggered and the cloud-side screenshot process for the target cloud service application is intervened, the actual screenshot content is processed based on the content of the screenshot of the user's own desktop background. Therefore, the screenshot content is consistent with the user's expectations, so that the user can be unaware of whether they are currently using a cloud service application or a local application, thus improving the smoothness of the user's use of cloud service applications.

[0115] Reference Figure 9 It illustrates a flowchart of the specific steps of a screenshot method provided in an embodiment of this application, applied to a user device, the method including:

[0116] Step 301: In response to the screenshot trigger operation of the screenshot control displayed in the interface of the target cloud service application, generate a screenshot event through the screenshot service of the user device, and send the screenshot event to the cloud server according to the preset cloud service transmission protocol.

[0117] When a screenshot is required while running the target cloud service application, the user can perform a screenshot trigger operation on the user's device desktop, such as clicking the "Screenshot" button in the running window of the target cloud service application, or pressing the screenshot physical button on the user's device to trigger the screenshot operation. The user's device responds to the screenshot trigger operation, generates a screenshot event, and sends it to the cloud service application on the cloud server according to the preset cloud service transmission protocol.

[0118] Step 302: Obtain the screenshot request sent by the cloud server based on the screenshot event.

[0119] For details, please refer to step 102 above; it will not be repeated here.

[0120] Step 303: Call the screenshot tool to take a screenshot according to the screenshot request, and send the obtained screenshot content to the cloud server.

[0121] For details, please refer to step 103 above; it will not be repeated here.

[0122] Step 304: Obtain the screenshot result sent by the cloud server.

[0123] For details, please refer to step 104 above; it will not be repeated here.

[0124] Optionally, in one implementation, step 303 may specifically include:

[0125] Sub-step 3031: Call the screenshot tool to enter the screenshot interface according to the screenshot request. The screenshot interface includes the interface of the target cloud service application and the desktop background of the user's device.

[0126] Sub-step 3032: In response to the screenshot operation on the screenshot interface, obtain the screenshot content containing the interface and / or desktop background of the target cloud service application, and send it to the cloud server so that the cloud server can generate the screenshot result based on the screenshot content and the target cloud service application.

[0127] In this embodiment of the application, for sub-steps 3031-3032, refer to Figure 2 In this screenshot interaction method, the embodiment of this application triggers a cloud-side screenshot service and intervenes in the cloud-side screenshot process of the target cloud service application. However, the actual screenshot action occurs in the desktop environment of the user device's endpoint running window. That is, based on the screenshot request sent by the cloud server, the user device can display a screenshot interface including the target cloud service application's interface (running window) and the user device's desktop background. Furthermore, the user can input screenshot operations in the screenshot interface. The screenshot operation is used to select a screenshot area in the screenshot interface and use the content within the screenshot area as the screenshot content. The screenshot content can be further sent to the cloud server so that the cloud server can import the screenshot content into the target cloud service application. In this implementation, the screenshot action occurs in the desktop environment of the user device's endpoint running window. The obtained screenshot content is based on the user device's desktop background and the endpoint cloud window. This screenshot content matches the user's expectation (to obtain screenshot content including the user device's desktop background), thus allowing the user to seamlessly distinguish between using a cloud service application and a local application.

[0128] Depending on the actual needs, the screenshot content captured by the user can be only the interface or desktop background of the target cloud service application, or it can include both the interface of the target cloud service application and the desktop background.

[0129] Optionally, sub-step 3032 can be implemented by obtaining the screenshot cursor event included in the screenshot operation, determining the screenshot area in the screenshot interface based on the screenshot cursor event, and sending the interface and / or desktop background of the target cloud service application within the screenshot area as the screenshot content to the cloud server.

[0130] In this embodiment, the screenshot operation can specifically be a user selecting an area using a screenshot cursor on the screenshot interface. This operation can be recorded as a screenshot cursor event (reflecting event information about the selection trajectory of the screenshot cursor). The user device's on-device screenshot service can then determine the screenshot area based on the screenshot cursor event and send the content of that area as the screenshot content to the cloud server. The movement of the screenshot cursor in the screenshot cursor event can be controlled by the user. The user can control the movement of the screenshot cursor through touch operations on the user device's display screen or by operating the physical buttons on the user device.

[0131] Optionally, in one implementation, step 303 may specifically include:

[0132] Sub-step 3033: Call the screenshot tool according to the screenshot request to obtain the full-screen display image of the user's device.

[0133] Sub-step 3034: Add the full-screen image to the screenshot content and send it to the cloud server, so that the cloud server can capture all or part of the full-screen image displayed on the cloud server in response to the screenshot operation information subsequently sent by the user device.

[0134] In this embodiment of the application, for sub-steps 3033-3034, refer to Figure 3 In this embodiment of the screenshot interaction method, the cloud-side screenshot service is triggered and the cloud-side screenshot process of the target cloud service application is intervened. However, the user device can capture the full-screen display image of the user device's desktop as the screenshot content and send the screenshot content to the cloud-side screenshot service of the cloud server so that the cloud-side screenshot service can replace the desktop background of the cloud side with the full-screen display image of the user device's desktop. Then, according to the user's screenshot operation sent by the user device, the screenshot content is obtained from the replaced desktop background.

[0135] Specifically, based on a screenshot request, the user device can invoke a screenshot tool through the on-device screenshot service to capture a full-screen image of the user device. This full-screen image is then added to the screenshot content and sent to the cloud server. The cloud-side screenshot service replaces the cloud-side desktop background with this full-screen image before performing the screenshot operation, thus capturing the screenshot content on the full-screen image. The resulting screenshot content is based on the user device's full-screen image, and this content matches the user's expectation (to obtain a screenshot including the user device's desktop background). This allows the user to seamlessly distinguish between using cloud service applications and local applications.

[0136] Alternatively, in another implementation, step 303 may specifically include:

[0137] Sub-step 3035: Call the screenshot tool to enter the screenshot interface according to the screenshot request. The screenshot interface includes the interface of the target cloud service application and the desktop background of the user's device.

[0138] Sub-step 3036: In response to the screenshot operation on the screenshot interface, obtain the screenshot area containing the interface and / or desktop background of the target cloud service application.

[0139] Sub-step 3037: In response to the screen recording operation of the screenshot area, record the screen content of the screenshot area for a preset duration and send it to the cloud server so that the cloud server can bind the screen recording content with the target cloud service application and generate the screenshot result.

[0140] In this embodiment of the application, regarding sub-steps 3035-3037, the screenshot method of this embodiment can also be specifically applied to screenshot and screen recording scenarios. In this scenario, the user device can first call the screenshot tool according to the screenshot request to enter the screenshot interface including the interface of the target cloud service application and the desktop background of the user device. Then, according to the screenshot operation input by the user on the screenshot interface, the screenshot area is selected from the screenshot interface. After the user selects the screenshot area, the user can trigger the screen recording control (click the screen recording button control in the interface, or press the screen recording physical button of the user device) so that the user device can perform the screen recording operation on the screenshot area. The screen recording content of a preset duration is recorded for the screenshot area (the end time of the screen recording can be determined by the user device responding to the time of the screenshot termination operation input by the user) and sent to the cloud server so that the cloud server can bind the screen recording content with the target cloud service application and generate the screenshot result. In this way, the purpose of further realizing the screen recording operation of the screenshot area on the basis of the screenshot is achieved, which improves the functionality of the cloud service application.

[0141] In summary, this embodiment of the application, even when the cloud-side screenshot service is triggered and the cloud-side screenshot process for the target cloud service application is intervened, the actual screenshot content is processed based on the content of the screenshot of the user's own desktop background. Therefore, the screenshot content is consistent with the user's expectations, so that the user can be unaware of whether they are currently using a cloud service application or a local application, thus improving the smoothness of the user's use of cloud service applications.

[0142] Reference Figure 10 It illustrates a flowchart of the specific steps of a screenshot method provided in an embodiment of this application, applied to a cloud server, the method including:

[0143] Step 401: Obtain the screenshot event sent by the user device.

[0144] For details of this step, please refer to step 201 above; it will not be repeated here.

[0145] Step 402: Based on the screenshot event, call the screenshot service interface to trigger the screenshot service of the cloud server.

[0146] Among them, the screenshot event is generated based on the screenshot trigger operation of the user device on the screenshot control displayed in the interface of the target cloud service application.

[0147] In this embodiment of the application, the cloud server's screenshot service (cloud-side screenshot service) can specifically determine the current screenshot operation targeting the target cloud service application based on the screenshot event, and then intervene in the screenshot process of the target cloud service application.

[0148] Step 403: Using the screenshot service of the cloud server, initiate a screenshot of the target cloud service application, generate a screenshot request, and send the screenshot request to the user device in accordance with the cloud service transmission protocol.

[0149] In this step, after intervening in the screenshot process of the target cloud service application, the cloud-side screenshot service can generate a screenshot request and send it to the user device according to the cloud service transmission protocol to notify the user device to take a screenshot and return the screenshot content. This ensures that although the cloud server triggers the cloud-side screenshot service and intervenes in the cloud-side screenshot process of the target cloud service application, the actual screenshot action occurs in the desktop environment of the running window on the user device. This makes the screenshot content consistent with the user's expectations, thus providing the user with a seamless experience of whether they are currently using a cloud service application or a local application.

[0150] Step 404: Obtain the screenshot content captured by the user device based on the screenshot request.

[0151] For details, please refer to step 203 above; it will not be repeated here.

[0152] Step 405: Based on the screenshot content and the target cloud service application, generate a screenshot result and send the screenshot result to the user device through the target cloud service application according to the preset cloud service transmission protocol.

[0153] For details, please refer to step 204 above; it will not be repeated here.

[0154] Optionally, in one implementation, the screenshot content is the content obtained by the user device in response to the screenshot operation on the screenshot interface. The screenshot interface includes the interface of the target cloud service application displayed on the user device and the desktop background of the user device. Step 405 may specifically include:

[0155] Sub-step 4051: Store the screenshot content in the storage area associated with the screenshot service of the target cloud service application, and generate a screenshot result containing the access address of the screenshot content in the storage area.

[0156] In this implementation method, you can refer to Figure 2 The screenshot implementation method involves the screenshot action occurring in the desktop environment of the user's device's running window. Thus, the screenshot content obtained by the cloud service application on the cloud server is based on the user's device's desktop background and the content captured in the cloud-side window. Based on this screenshot content, the cloud-side screenshot service needs to further bind this content to the target cloud service application, i.e., inject the screenshot content into the target cloud service application, thereby completing the closed-loop process of the cloud-side screenshot service. Specifically, binding the screenshot content to the target cloud service application can involve storing the screenshot content in a storage area associated with the screenshot service of the target cloud service application. This storage area can be a local storage area on the cloud server or another external storage area.

[0157] Finally, the cloud server can generate a screenshot result containing the access address of the screenshot content in the storage area and send it to the user's device. When the user needs to obtain the screenshot content later, they can obtain the screenshot content from the storage area through the access address in the screenshot result.

[0158] Alternatively, in another implementation, the screenshot content is a full-screen image displayed on the user device; step 405 may specifically include:

[0159] Sub-step 4052: Use a screenshot tool to capture the full-screen image and obtain the screenshot image.

[0160] Sub-step 4053: Store the screenshot image in the storage area associated with the screenshot service of the target cloud service application, and generate a screenshot result containing the access address of the screenshot image in the storage area.

[0161] For the implementation of sub-steps 4052-4053, please refer to... Figure 3 The screenshot implementation method involves the user device sending a full-screen image of its desktop to the cloud-side screenshot service. The cloud-side screenshot service can then replace the desktop background with this full-screen image and use a screenshot tool to capture the full-screen image. This results in a screenshot image that is based on the user device's full-screen image and matches the user's expectations (to obtain a screenshot that includes the user device's desktop background). This allows the user to seamlessly distinguish between using a cloud service application and a local application.

[0162] Specifically, the cloud server can bind the screenshot image to the target cloud service application by storing the screenshot image in a storage area associated with the screenshot service of the target cloud service application. This storage area can be a local storage area of ​​the cloud server or other external storage areas.

[0163] Finally, the cloud server can generate a screenshot result containing the access address of the screenshot image in the storage area and send it to the user's device. When the user needs to obtain the screenshot image later, they can obtain the screenshot image from the storage area through the access address in the screenshot result.

[0164] Optionally, sub-step 4052 may specifically include:

[0165] Sub-step A1: Replace the currently displayed screen with a full-screen image.

[0166] Sub-step A2: Obtain the simulated screenshot cursor event sent by the user device. The simulated screenshot cursor event is a cursor event generated for the simulated screenshot interface displayed on the user device. The simulated screenshot interface displays a full-screen image.

[0167] Sub-step A3: Based on the simulated screenshot cursor event, call the screenshot tool to capture a screenshot image from the full-screen display image shown on the cloud server.

[0168] For sub-steps A1-A3, during the process of the cloud server calling the screenshot tool to capture a screenshot of the full-screen display image, the cloud server can first replace its own current display screen with the full-screen display image, making the desktop background of the cloud server consistent with the desktop background of the user device. Then, the user device can display a simulated screenshot interface. The user inputs a simulated screenshot cursor event in the simulated screenshot interface. The simulated screenshot cursor event does not trigger a screenshot action on the user device side, but is sent to the cloud server. The cloud server can then call the screenshot tool based on the simulated screenshot cursor event to capture a screenshot image from the full-screen display image displayed by the cloud server, thereby obtaining a screenshot image consistent with the user's expectation (to obtain a screenshot image that includes the user device's desktop background).

[0169] In summary, this embodiment of the application, even when the cloud-side screenshot service is triggered and the cloud-side screenshot process for the target cloud service application is intervened, the actual screenshot content is processed based on the content of the screenshot taken by the user device of its own desktop environment. Therefore, the screenshot content is consistent with the user's expectations, so that the user can be unaware of whether they are currently using a cloud service application or a local application, thus improving the smoothness of the user's use of cloud service applications.

[0170] Reference Figure 11It shows a block diagram of a screenshot device provided in an embodiment of this application, applied to a user device, including:

[0171] The response module 501 is used to respond to the screenshot trigger operation, generate a screenshot event and send it to the cloud server;

[0172] The first acquisition module 502 is used to acquire the screenshot request sent by the cloud server based on the screenshot event;

[0173] The screenshot module 503 is used to call the screenshot tool to take a screenshot according to the screenshot request, and send the obtained screenshot content to the cloud server so that the cloud server can generate the screenshot result based on the screenshot content and the target cloud service application;

[0174] The second acquisition module 504 is used to acquire the screenshot results sent by the cloud server.

[0175] Optionally, the screenshot module 503 includes:

[0176] The first calling submodule is used to call the screenshot tool to enter the screenshot interface according to the screenshot request. The screenshot interface includes the interface of the target cloud service application and the desktop background of the user's device.

[0177] The first screenshot submodule is used to respond to the screenshot operation on the screenshot interface, obtain the screenshot content including the interface and / or desktop background of the target cloud service application, and send it to the cloud server so that the cloud server can generate the screenshot result based on the screenshot content and the target cloud service application.

[0178] Optionally, the first screenshot submodule includes:

[0179] The cursor unit is used to acquire the screenshot cursor event included in the screenshot operation, and to determine the screenshot area in the screenshot interface based on the screenshot cursor event;

[0180] The screenshot unit is used to send the screenshot area containing the interface and / or desktop background of the target cloud service application to the cloud server as the screenshot content.

[0181] Optionally, the screenshot module 503 includes:

[0182] The full-screen screenshot submodule is used to invoke the screenshot tool based on the screenshot request and obtain the full-screen display image of the user's device.

[0183] The screenshot sending submodule is used to add a full-screen image to the screenshot content and send it to the cloud server, so that the cloud server can capture all or part of the full-screen image displayed on the cloud server in response to the screenshot operation information subsequently sent by the user's device.

[0184] Optionally, the response module 501 includes:

[0185] The event generation submodule is used to respond to the screenshot trigger operation of the screenshot control displayed in the interface of the target cloud service application. It generates a screenshot event through the screenshot service of the user device and sends the screenshot event to the cloud server according to the preset cloud service transmission protocol.

[0186] Screenshot module 503 includes:

[0187] The first protocol sending submodule is used by the event generation submodule to send screenshots to the cloud server according to the cloud service transmission protocol.

[0188] Optionally, the screenshot module 503 includes:

[0189] The second submodule is used to call the screenshot tool to enter the screenshot interface based on the screenshot request. The screenshot interface includes the interface of the target cloud service application and the desktop background of the user's device.

[0190] The second screenshot submodule is used to respond to the screenshot operation on the screenshot interface and obtain the screenshot area containing the interface and / or desktop background of the target cloud service application.

[0191] The screen recording submodule is used to respond to screen recording operations on the screenshot area. It records screen content of a preset duration for the screenshot area and sends it to the cloud server, so that the cloud server can bind the screen recording content with the target cloud service application and generate a screenshot result.

[0192] In summary, this embodiment of the application, even when the cloud-side screenshot service is triggered and the cloud-side screenshot process for the target cloud service application is intervened, the actual screenshot content is processed based on the content of the screenshot of the user's own desktop background. Therefore, the screenshot content is consistent with the user's expectations, so that the user can be unaware of whether they are currently using a cloud service application or a local application, thus improving the smoothness of the user's use of cloud service applications.

[0193] Reference Figure 12 It illustrates a block diagram of another screenshot device provided in an embodiment of this application, applied to a cloud server, including:

[0194] The third acquisition module 601 is used to acquire screenshot events sent by the user device;

[0195] The generation module 602 is used to generate a screenshot request based on the screenshot event and send it to the user device;

[0196] The fourth acquisition module 603 is used to acquire the screenshot content captured by the user device based on the screenshot request;

[0197] The sending module 604 is used to generate a screenshot result based on the screenshot content and the target cloud service application and send it to the user device.

[0198] Optionally, the screenshot event is generated based on the screenshot trigger operation of the user device on the screenshot control displayed in the interface of the target cloud service application. The generation module 602 includes:

[0199] The third submodule is used to trigger the screenshot service of the cloud server by calling the screenshot service interface based on the screenshot event.

[0200] The startup submodule is used to initiate a screenshot of the target cloud service application through the screenshot service of the cloud server, generate a screenshot request, and send the screenshot request to the user device in accordance with the cloud service transmission protocol.

[0201] Optionally, the screenshot content is the content obtained by the user device in response to the screenshot operation on the screenshot interface, which includes the interface of the target cloud service application displayed on the user device and the desktop background of the user device.

[0202] Transmitting module 604 includes:

[0203] The first binding submodule is used to store the screenshot content to the storage area associated with the screenshot service of the target cloud service application, and generate a screenshot result containing the access address of the screenshot content in the storage area.

[0204] Optionally, the screenshot content is a full-screen image displayed on the user's device;

[0205] Transmitting module 604 includes:

[0206] The fourth submodule is used to call the screenshot tool to capture the full-screen image and obtain the screenshot image;

[0207] The second binding submodule is used to store the screenshot image to a storage area associated with the screenshot service of the target cloud service application, and generate a screenshot result containing the access address of the screenshot image in the storage area.

[0208] Optionally, the fourth calling submodule includes:

[0209] The Replace submodule is used to replace the currently displayed image with a full-screen image;

[0210] The simulation submodule is used to obtain the simulated screenshot cursor event sent by the user device. The simulated screenshot cursor event is a cursor event generated for the simulated screenshot interface displayed on the user device. The simulated screenshot interface displays a full-screen image.

[0211] The screenshot submodule is used to call the screenshot tool to capture a screenshot image from the full-screen display image displayed on the cloud server based on the simulated screenshot cursor event.

[0212] Optionally, the transmitting module 604 includes:

[0213] The second protocol sending submodule is used to send the screenshot results to the user device through the target cloud service application according to the preset cloud service transmission protocol.

[0214] In summary, this embodiment of the application, even when the cloud-side screenshot service is triggered and the cloud-side screenshot process for the target cloud service application is intervened, the actual screenshot content is processed based on the content of the screenshot of the user's own desktop background. Therefore, the screenshot content is consistent with the user's expectations, so that the user can be unaware of whether they are currently using a cloud service application or a local application, thus improving the smoothness of the user's use of cloud service applications.

[0215] Reference Figure 13 The diagram illustrates a block diagram of a screenshot system provided in an embodiment of this application, including: a user device 701 and a cloud server 702;

[0216] User equipment 701 is used to: respond to a screenshot trigger operation, generate a screenshot event and send it to the cloud server; obtain a screenshot request sent by the cloud server based on the screenshot event; call a screenshot tool to take a screenshot based on the screenshot request, and send the obtained screenshot content to the cloud server so that the cloud server can generate a screenshot result based on the screenshot content and the target cloud service application; and obtain the screenshot result sent by the cloud server.

[0217] The cloud server 702 is used to: acquire screenshot events sent by user devices; generate screenshot requests based on the screenshot events and send them to user devices; acquire screenshot content captured by user devices based on the screenshot requests; and generate screenshot results based on the screenshot content and the target cloud service application and send them to user devices.

[0218] In summary, this embodiment of the application, even when the cloud-side screenshot service is triggered and the cloud-side screenshot process for the target cloud service application is intervened, the actual screenshot content is processed based on the content of the screenshot of the user's own desktop background. Therefore, the screenshot content is consistent with the user's expectations, so that the user can be unaware of whether they are currently using a cloud service application or a local application, thus improving the smoothness of the user's use of cloud service applications.

[0219] This application also provides a non-volatile readable storage medium storing one or more modules (programs). When these modules are applied to a device, they enable the device to execute the instructions of the method steps on the user equipment side in this application.

[0220] This application also provides a user equipment, including a processor and a memory, wherein the memory stores executable code, and when the executable code is executed, the processor performs the aforementioned method steps on the user equipment side.

[0221] This application provides one or more machine-readable media storing instructions that, when executed by one or more processors, cause a user equipment to perform one or more of the methods described in the above embodiments. In this application, the user equipment includes various types of terminal devices.

[0222] This application also provides a non-volatile readable storage medium storing one or more modules. When these modules are applied to a device, they enable the device to execute instructions for the method steps on the server side in this application.

[0223] This application also provides a cloud server, including a processor and a memory, wherein the memory stores executable code, and when the executable code is executed, the processor performs the aforementioned method steps on the cloud server side.

[0224] This application provides one or more machine-readable media storing instructions that, when executed by one or more processors, cause a cloud server to perform one or more of the methods described in the above embodiments.

[0225] The embodiments of this disclosure can be implemented as an apparatus with any suitable hardware, firmware, software, or any combination thereof configured as desired, including user equipment, cloud servers, etc. Figure 14 An exemplary apparatus 1000 is schematically shown that can be used to implement the various embodiments described in the embodiments of this application.

[0226] In one embodiment, Figure 14An exemplary device 1000 is shown, which includes one or more processors 1002, a control module (chipset) 1004 coupled to at least one of the processors 1002, a memory 1006 coupled to the control module 1004, a non-volatile memory (NVM) / storage device 1008 coupled to the control module 1004, one or more input / output devices 1010 coupled to the control module 1004, and a network interface 1012 coupled to the control module 1004.

[0227] Processor 1002 may include one or more single-core or multi-core processors, and processor 1002 may include any combination of general-purpose processors or special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In some embodiments, device 1000 can serve as a terminal device, server (cluster), or other device as described in the embodiments of this application.

[0228] In some embodiments, apparatus 1000 may include one or more computer-readable media (e.g., memory 1006 or non-volatile memory / storage device 1008) having instructions 1014 and one or more processors 1002 that are combined with the one or more computer-readable media and configured to execute instructions 1014 to implement modules and thereby perform the actions described in this disclosure.

[0229] In one embodiment, the control module 1004 may include any suitable interface controller to provide any suitable interface to at least one of the processors 1002 and / or any suitable device or component communicating with the control module 1004.

[0230] The control module 1004 may include a memory controller module to provide an interface to the memory 1006. The memory controller module may be a hardware module, a software module, and / or a firmware module.

[0231] Memory 1006 may be used, for example, to load and store data and / or instructions 1014 for device 1000. In one embodiment, memory 1006 may include any suitable volatile memory, such as suitable dynamic random access memory (DRAM). In some embodiments, memory 1006 may include dual data rate type quad synchronous dynamic random access memory (DDR4 SDRAM).

[0232] In one embodiment, the control module 1004 may include one or more input / output controllers to provide an interface to the non-volatile memory / storage device 1008 and (one or more) input / output devices 1010.

[0233] For example, non-volatile memory / storage device 1008 may be used to store data and / or instructions 1014. Non-volatile memory / storage device 1008 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable (one or more) non-volatile storage devices (e.g., one or more hard disk drives (HDDs), one or more compact disc (CD) drives, and / or one or more digital video disc (DVD) drives).

[0234] The non-volatile memory / storage device 1008 may include storage resources that are physically part of a device on which the device 1000 is mounted, or that can be accessed by the device without being part of the device. For example, the non-volatile memory / storage device 1008 may be accessed via a network via one or more input / output devices 1010.

[0235] One or more input / output devices 1010 may provide an interface for device 1000 to communicate with any other suitable device. Input / output devices 1010 may include communication components, audio components, sensor components, etc. Network interface 1012 may provide an interface for device 1000 to communicate via one or more networks. Device 1000 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and / or protocols, such as accessing wireless networks based on communication standards, such as Wireless Fidelity (WiFi) networks, Second Generation Mobile Networks (2G) networks, Third Generation Mobile Networks (3G) networks, Fourth Generation Mobile Networks (4G) networks, Fifth Generation Mobile Networks (5G) networks, etc., or combinations thereof.

[0236] In one embodiment, at least one of the processors 1002 may be logically packaged with one or more controllers (e.g., memory controller modules) of the control module 1004. In one embodiment, at least one of the processors 1002 may be logically packaged with one or more controllers of the control module 1004 to form a system-in-a-package (SiP). In one embodiment, at least one of the processors 1002 may be integrated with the logic of one or more controllers of the control module 1004 on the same die. In one embodiment, at least one of the processors 1002 may be integrated with the logic of one or more controllers of the control module 1004 on the same die to form a system-on-chip (SoC).

[0237] In various embodiments, device 1000 may be, but is not limited to, a server, desktop computing device, or mobile computing device (e.g., laptop computing device, handheld computing device, tablet computer, netbook, etc.). In various embodiments, device 1000 may have more or fewer components and / or different architectures. For example, in some embodiments, device 1000 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touchscreen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.

[0238] The detection device may use a main control chip as a processor or control module, and sensor data, position information, etc. may be stored in a memory or non-volatile memory / storage device. The sensor group may be used as an input / output device, and the communication interface may include a network interface.

[0239] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0240] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0241] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0242] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more blocks of a block diagram.

[0243] These computer program instructions may also be loaded onto a computer or other programmable data processing terminal equipment to cause a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable terminal equipment, provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of a block diagram.

[0244] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.

[0245] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0246] The foregoing has provided a detailed description of the screenshot method, apparatus, user equipment, cloud server, screenshot system, and machine-readable medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A screenshot method, characterized in that, Applied to user equipment, the method includes: In response to a screenshot trigger operation, a screenshot event is generated and sent to the cloud server; Obtain the screenshot request sent by the cloud server based on the screenshot event; The screenshot tool is invoked according to the screenshot request to take a screenshot, and the obtained screenshot content is sent to the cloud server so that the cloud server can generate a screenshot result based on the screenshot content and the target cloud service application. The step of invoking the screenshot tool according to the screenshot request includes: performing a screenshot action in the desktop environment of the terminal running window in the target cloud service application; the screenshot content is based on the desktop background of the user device and the content obtained from the terminal running window; the cloud server generating the screenshot result based on the screenshot content and the target cloud service application includes: the cloud server binding the screenshot content with the target cloud service application to generate the screenshot result; the screenshot result includes an access address for accessing the screenshot content. Obtain the screenshot result sent by the cloud server.

2. The method according to claim 1, characterized in that, The step of calling the screenshot tool to take a screenshot according to the screenshot request and sending the obtained screenshot content to the cloud server includes: The screenshot request is used to invoke the screenshot tool to enter the screenshot interface, which includes the interface of the target cloud service application and the desktop background of the user device. In response to the screenshot operation on the screenshot interface, a screenshot of the interface of the target cloud service application and / or the desktop background is obtained and sent to the cloud server so that the cloud server can generate a screenshot result based on the screenshot content and the target cloud service application.

3. The method according to claim 2, characterized in that, The step of obtaining screenshot content including the interface of the target cloud service application and / or the desktop background in response to the screenshot operation includes: Obtain the screenshot cursor event included in the screenshot operation, and determine the screenshot area in the screenshot interface based on the screenshot cursor event; The interface of the target cloud service application and / or the desktop background within the screenshot area are sent to the cloud server as the screenshot content.

4. The method according to claim 1, characterized in that, The step of calling the screenshot tool to take a screenshot according to the screenshot request and sending the obtained screenshot content to the cloud server includes: The screenshot tool is invoked based on the screenshot request to obtain the full-screen display image of the user device; The full-screen image is added to the screenshot content and sent to the cloud server, so that the cloud server can extract all or part of the full-screen image displayed by the cloud server in response to the screenshot operation information subsequently sent by the user device.

5. The method according to claim 1, characterized in that, The step of calling the screenshot tool to take a screenshot according to the screenshot request and sending the obtained screenshot content to the cloud server includes: The screenshot request is used to invoke the screenshot tool to enter the screenshot interface, which includes the interface of the target cloud service application and the desktop background of the user device. In response to the screenshot operation on the screenshot interface, a screenshot area containing the interface of the target cloud service application and / or the desktop background is obtained; In response to the screen recording operation of the screenshot area, screen recording content of a preset duration is recorded for the screenshot area and sent to the cloud server, so that the cloud server can bind the screen recording content with the target cloud service application and generate a screenshot result.

6. The method according to any one of claims 1 to 5, characterized in that, The process of responding to a screenshot trigger operation, generating a screenshot event, and sending it to the cloud server includes: In response to a screenshot trigger operation of a screenshot control displayed in the interface of a target cloud service application, a screenshot event is generated through the screenshot service of the user device, and the screenshot event is sent to the cloud server according to a preset cloud service transmission protocol. Sending the obtained screenshot content to the cloud server includes: The screenshot content is sent to the cloud server according to the cloud service transmission protocol.

7. A screenshot method, characterized in that, Applied to cloud servers, the method includes: Get screenshot events sent by the user's device; Based on the screenshot event, a screenshot request is generated and sent to the user device; The screenshot content captured by the user device based on the screenshot request is obtained; wherein, the user device performs the screenshot action in the desktop environment of the terminal running window in the target cloud service application, and the screenshot content is obtained based on the desktop background of the user device and the terminal running window; Based on the screenshot content and the target cloud service application, a screenshot result is generated and sent to the user device; The step of generating a screenshot result and sending it to the user device based on the screenshot content and the target cloud service application includes: binding the screenshot content with the target cloud service application, generating the screenshot result and sending it to the user device, wherein the screenshot result includes an access address for accessing the screenshot content.

8. A screenshot device, characterized in that, Applied to user equipment, the device includes: The response module is used to respond to the screenshot trigger operation, generate a screenshot event, and send it to the cloud server. The first acquisition module is used to acquire the screenshot request sent by the cloud server according to the screenshot event; A screenshot module is used to invoke a screenshot tool to take a screenshot according to the screenshot request, and send the obtained screenshot content to the cloud server, so that the cloud server can generate a screenshot result based on the screenshot content and the target cloud service application; wherein, invoking the screenshot tool to take a screenshot according to the screenshot request includes: performing a screenshot action in the desktop environment of the terminal running window in the target cloud service application, the screenshot content is the content obtained based on the desktop background of the user device and the terminal running window, and the cloud server generating a screenshot result based on the screenshot content and the target cloud service application includes: the cloud server binding the screenshot content with the target cloud service application to generate the screenshot result; The second acquisition module is used to acquire the screenshot result sent by the cloud server, and the screenshot result includes an access address for accessing the screenshot content.

9. A screenshot device, characterized in that, The device, applied to a cloud server, includes: The third acquisition module is used to acquire screenshot events sent by the user's device; The generation module is used to generate a screenshot request based on the screenshot event and send it to the user device; The fourth acquisition module is used to acquire the screenshot content captured by the user device based on the screenshot request; wherein, the user device performs the screenshot action in the desktop environment of the terminal running window in the target cloud service application, and the screenshot content is the content obtained based on the desktop background of the user device and the terminal running window; The sending module is used to generate a screenshot result based on the screenshot content and the target cloud service application and send it to the user device; Specifically, the sending module is used to bind the screenshot content with the target cloud service application, generate the screenshot result, and send it to the user device. The screenshot result includes an access address for accessing the screenshot content.

10. A user equipment, characterized in that, include: processor; and A memory having executable code stored thereon, which, when executed, causes the processor to perform the method as described in any one of claims 1 to 6.

11. A cloud server, characterized in that, include: processor; and A memory having executable code stored thereon, which, when executed, causes the processor to perform the method as described in claim 7.

12. One or more machine-readable media having executable code stored thereon, which, when executed, causes a processor to perform the method as claimed in any one of claims 1 to 6.

13. One or more machine-readable media having executable code stored thereon, which, when executed, causes a processor to perform the method of claim 7.

14. A screenshot system, characterized in that, include: User equipment and cloud servers; The user equipment is used to: generate a screenshot event and send it to the cloud server in response to a screenshot trigger operation; Obtain the screenshot request sent by the cloud server based on the screenshot event; The screenshot tool is invoked according to the screenshot request to take a screenshot, and the obtained screenshot content is sent to the cloud server so that the cloud server can generate a screenshot result based on the screenshot content and the target cloud service application; wherein, the step of invoking the screenshot tool according to the screenshot request includes: performing a screenshot action in the desktop environment of the terminal running window in the target cloud service application, the screenshot content being the content obtained based on the desktop background of the user device and the terminal running window, obtaining the screenshot result sent by the cloud server, and the screenshot result including an access address for accessing the screenshot content; The cloud server is used to: acquire screenshot events sent by user devices; generate screenshot requests and send them to the user devices based on the screenshot events; acquire screenshot content captured by the user devices based on the screenshot requests; generate screenshot results and send them to the user devices based on the screenshot content and a target cloud service application; wherein, generating screenshot results and sending them to the user devices based on the screenshot content and the target cloud service application includes: binding the screenshot content with the target cloud service application, generating the screenshot results and sending them to the user devices.

Images