Cloud-based data processing methods and devices
By collaborating between the client and the cloud server, a cloud-based virtual mode is determined, a data channel is established, and an execution script is run. This solves the problem of low efficiency in reliable user data processing in existing technologies, and achieves secure and efficient data processing and improved stability.
Patent Information
- Application Number
- CN202611294703.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-25
- Publication Date
- 2026-11-17
AI Technical Summary
Existing cloud virtualization-based automated processing solutions struggle to meet the demands for efficient and secure data processing in diverse real-world application scenarios, particularly lacking effective solutions for the trusted processing of user data.
Through the collaborative cooperation between the client and the cloud server, data requests are submitted based on user authorization, the cloud virtual mode is determined, a data channel is established, message callbacks are registered, and scripts are run to simulate user operations, thereby achieving reliable data processing. Simulated data is collected and transmitted back through the cloud instance for rendering, display, and status response.
It enables secure and reliable processing of user data, improves data processing efficiency, expands the applicable scenarios for data processing, and enhances processing stability and availability through virtual mode switching.
Smart Images

Figure CN123123338A_ABST
Abstract
Description
Technical Field
[0001] This document relates to the field of cloud service technology, and in particular to a data processing method and apparatus based on cloud services. Background Technology
[0002] With the rapid development of cloud virtualization technology, cloud virtualization is increasingly widely used in various processing fields, resulting in various data processing capabilities based on virtualization technology. Cloud computing power carriers, represented by virtual machines deployed in the cloud, have been widely used in scenarios such as remote office and automated process processing. Although automated processing solutions based on cloud virtualization have made some progress in terms of coverage and execution efficiency, the diversification of needs in actual application scenarios has placed higher demands on the automated processing of cloud virtual machines. Summary of the Invention
[0003] This specification provides one or more embodiments of a cloud service-based data processing method applied to a client. The method includes: submitting a data request to a cloud server based on user authorization and receiving task information for a trusted data task returned by the cloud server; determining a cloud virtual mode for performing trusted data processing based on cloud configuration parameters and local parameters obtained by calling a cloud interface; establishing a data channel with a cloud instance by calling a cloud service component corresponding to the cloud virtual mode and registering message callbacks for receiving task execution status; performing simulated data collection and rendering based on the simulated data returned by the data channel, and executing page response actions corresponding to the returned task status messages.
[0004] This specification provides one or more embodiments of another cloud service-based data processing method applied to a cloud server. The method includes: creating a trusted data task based on a data request submitted by a client and returning task information; initializing the cloud task corresponding to the trusted data task; scheduling a corresponding cloud instance according to the client's determined cloud virtual mode and issuing an execution script for the cloud task to the cloud instance; initializing the virtual runtime environment of the cloud instance and simulating a user's data collection operation on the target system by running the execution script; transmitting the simulated data collected by the execution script back to the client through an established data channel, and transmitting task status messages based on the task execution status.
[0005] This specification provides one or more embodiments of a cloud service-based data processing device, running on a client side. The device includes: a data request submission module configured to submit a data request to a cloud server based on user authorization and receive task information for a trusted data task returned by the cloud server; a virtual mode determination module configured to determine a cloud virtual mode for performing trusted data processing based on cloud configuration parameters and local parameters obtained by calling a cloud interface; a data channel establishment module configured to establish a data channel with a cloud instance by calling a cloud service component corresponding to the cloud virtual mode and register for receiving message callbacks of task execution status; and a rendering response module configured to perform simulated rendering and display of the collected simulated data returned by the data channel and execute page response actions corresponding to the returned task status messages.
[0006] This specification provides one or more embodiments of another cloud service-based data processing apparatus, running on a cloud server. The apparatus includes: a task creation module configured to create a trusted data task based on a data request submitted by a client and return task information, and initialize the cloud task corresponding to the trusted data task; a cloud instance processing module configured to schedule a corresponding cloud instance according to a determined cloud virtual mode by the client, and issue an execution script for the cloud task to the cloud instance; an execution script running module configured to initialize the virtual runtime environment of the cloud instance and simulate a user's data collection operation on the target system by running the execution script; and a data feedback module configured to send the simulated data collected by the execution script back to the client through an established data channel, and send back task status messages based on the task execution status.
[0007] This specification provides one or more embodiments of a cloud service-based data processing device, including: a processor and a memory configured to store computer-executable instructions; when executed, the computer-executable instructions cause the processor to: submit a data request to a cloud server based on user authorization, and receive task information of a trusted data task returned by the cloud server; determine a cloud virtual mode for performing trusted data processing based on cloud configuration parameters and local parameters obtained by calling a cloud interface; establish a data channel with a cloud instance by calling a cloud service component corresponding to the cloud virtual mode, and register message callbacks for receiving task execution status; perform simulated data collection rendering and display based on the collected simulated data returned by the data channel, and execute page response actions corresponding to the returned task status messages.
[0008] This specification provides one or more embodiments of another cloud service-based data processing device, including: a processor and a memory configured to store computer-executable instructions; creating a trusted data task based on a data request submitted by a client and returning task information; initializing a cloud task corresponding to the trusted data task; scheduling a corresponding cloud instance according to a determined cloud virtual mode by the client and issuing an execution script for the cloud task to the cloud instance; initializing the virtual runtime environment of the cloud instance and simulating a user's data acquisition operation on a target system by running the execution script; transmitting the simulated acquisition data of the execution script back to the client through an established data channel, and transmitting task status messages based on the task execution status.
[0009] This specification provides one or more embodiments of a computer-readable storage medium for storing computer-executable instructions. When executed, these computer-executable instructions implement the following process: submitting a data request to a cloud server based on user authorization and receiving task information for a trusted data task returned by the cloud server; determining a cloud virtual mode for performing trusted data processing based on cloud configuration parameters and local parameters obtained by calling a cloud interface; establishing a data channel with a cloud instance by calling the cloud service component corresponding to the cloud virtual mode and registering message callbacks for receiving task execution status; performing simulated data collection rendering and display based on the simulated data returned by the data channel, and executing page response actions corresponding to the returned task status messages.
[0010] This specification provides one or more embodiments of another computer-readable storage medium for storing computer-executable instructions that, when executed, implement the following process: creating a trusted data task based on a data request submitted by a client and returning task information; initializing the cloud task corresponding to the trusted data task; scheduling a corresponding cloud instance according to the client's determined cloud virtual mode and issuing the execution script of the cloud task to the cloud instance; initializing the virtual runtime environment of the cloud instance and simulating a user's data collection operation on the target system by running the execution script; transmitting the simulated data collected by the execution script back to the client through an established data channel, and transmitting task status messages based on the task execution status. Attached Figure Description
[0011] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Figure 1A schematic diagram illustrating the implementation environment of a cloud service-based data processing method provided in one or more embodiments of this specification; Figure 2 A flowchart illustrating a cloud service-based data processing method provided in one or more embodiments of this specification; Figure 3 A flowchart illustrating a cloud-based data processing method for a trusted user data collection scenario, provided in one or more embodiments of this specification. Figure 4 A flowchart illustrating another cloud-based data processing method provided in one or more embodiments of this specification; Figure 5 A schematic diagram illustrating an embodiment of a cloud-based data processing apparatus provided in one or more embodiments of this specification; Figure 6 A schematic diagram of another embodiment of a cloud service-based data processing apparatus provided in one or more embodiments of this specification; Figure 7 A schematic diagram of the structure of a cloud service-based data processing device provided for one or more embodiments of this specification; Figure 8 This is a schematic diagram of another cloud-based data processing device provided in one or more embodiments of this specification. Detailed Implementation
[0012] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.
[0013] The cloud-based data processing method provided in one or more embodiments of this specification is applicable to the implementation environment of a trusted data processing system. (Refer to...) Figure 1 The implementation environment includes at least: Client 101 and cloud server 102; Among them, client 101 refers to the access point for users to process data. Specifically, client 101 can be the application or subroutine accessed by users to process data. Cloud server 102 refers to the processor that performs trusted processing of user data. Specifically, it schedules the corresponding cloud instance according to the cloud virtual mode and achieves trusted processing of user data by running automated execution scripts for trusted data processing in the cloud instance. Specifically, when the cloud virtual mode includes cloud phone mode and cloud desktop mode, cloud server 102 includes the cloud instance corresponding to cloud desktop mode, namely cloud desktop virtual machine 102-1, and the cloud instance corresponding to cloud phone mode, namely cloud phone instance 102-2. In this implementation environment, during the trusted processing of user data, client 101 first submits a data request to cloud server 102 based on user authorization. Cloud server 102 creates a trusted data task based on the data request submitted by client 101 and returns task information, as well as initializes the cloud task corresponding to the trusted data task. Correspondingly, client 101 receives the task information of the trusted data task returned by cloud server 102, and determines the cloud virtual mode used to perform trusted data processing based on the cloud configuration parameters and local parameters obtained by calling the cloud interface. Further, cloud server 102 schedules the corresponding cloud instance according to the determined cloud virtual mode by the client, sends the execution script of the cloud task to the cloud instance, initializes the virtual runtime environment of the cloud instance, and simulates the user's data collection operation on the target system by running the execution script. A data channel is established between the cloud service component corresponding to the cloud virtual mode and the cloud instance, and a message callback for receiving task execution status is registered. Based on this, the cloud server 102 sends the collected simulation data of the execution script back to the client 101 through the established data channel, and sends back task status messages based on the task execution status. Correspondingly, the client 101 performs collection simulation rendering and display based on the collected simulation data sent back through the data channel, and executes the page response action corresponding to the sent-back task status message. In this way, the client 101 and the cloud server 102 cooperate to achieve reliable processing of user data, ensure the security of user data during the data processing process, and improve data processing efficiency by running automated execution scripts on the cloud instance corresponding to the scheduled cloud virtual mode. At the same time, it also helps to expand the applicable scenarios of data processing.
[0014] This specification provides one or more embodiments of a cloud service-based data processing method, as follows: Reference Figure 2 The cloud service-based data processing method provided in this embodiment can be applied to a client. The method specifically includes steps S202 to S208.
[0015] Step S202: Submit a data request to the cloud server based on user authorization, and receive the task information of the trusted data task returned by the cloud server.
[0016] In this embodiment, during the trusted processing of user data, the user can submit data processing instructions through the client. Upon receiving the data processing instructions submitted by the user, the client can perform user authorization interaction and submit a data request to the cloud server after the user authorization interaction is completed.
[0017] The client can be an application or subroutine accessed by the user for data processing, such as an application for transaction payment or resource management, or a subroutine within an application. The user can access data processing and submit data processing instructions through the data processing entry point configured in the application or subroutine. For example, the user can submit data processing instructions through a service or page set up by a subroutine within a payment application for trusted processing of user data, or the user can submit data processing instructions through an HTML5 page in a browser for trusted processing of user data.
[0018] A data request refers to a processing request for trusted processing of user data. Specifically, a data request can be a processing request for trusted processing of user data in a specific scenario or service, such as trusted processing of user data in a user credit maintenance scenario, which can specifically be used to update user credit through trusted processing of user data. Correspondingly, in this case, the data processing entry point configured in the application or subroutine refers to the trusted data processing entry point for trusted processing of user data, which can specifically be the trusted data processing entry point for user data in a specific scenario or service.
[0019] In practice, to improve the efficiency of trusted user data processing, upon receiving a user-submitted data processing instruction, the client can verify the user's access by calling the cloud server's user verification interface. Correspondingly, the cloud server responds to the user verification interface call by verifying whether the user meets the access conditions for a specific scenario or service and returns the verification result to the client. If the access verification passes, user authorization is initiated, and a data request is submitted to the cloud server after authorization. If the access verification fails, an access failure notification is generated. Furthermore, to enhance user data security, upon receiving a user-submitted data processing instruction, the client can also perform user identity verification and submit a data request to the cloud server after successful verification.
[0020] In practical applications, when a user accesses data processing through the application or subroutine's data processing entry point, it may be the user's first time accessing data processing, or it may be that the user has already accessed data processing and is now accessing it to query the data processing results. In this case, before submitting a data request to the cloud server based on user authorization, the user's data task can be queried. If the user's data task is found, it indicates that the user's current access is to query the data processing results, and the user's task can be restored. If the user's data task is not found, a data request can be submitted to the cloud server based on user authorization.
[0021] In one optional implementation of this embodiment, before the data request operation based on user authorization is submitted to the cloud server, the following processing is performed: Based on the user's application identifier, the task query interface is called to check whether the user has a trusted data task in progress. If so, the corresponding task recovery strategy is executed according to the task status of the trusted data task in progress; if not, the next step is executed, that is, submitting a data application to the cloud server based on the user's authorization.
[0022] Specifically, the corresponding task recovery strategy is executed, including: if the task status is in the creation or running state, polling the task status based on the task identifier and redirecting to the corresponding cloud instance page; if the task status is in the completed state, redirecting to the task results page; otherwise, if the task status is in the closed or failed state, the task re-creation process is initiated, performing the operation of submitting a data request to the cloud server based on user authorization. Here, task status refers to the task status of the trusted data task created based on the data request previously submitted by the user. The task status of a trusted data task includes: creation, running, completed, closed, and / or failed; the progress status includes creation and / or running states.
[0023] In practice, after a user submits a data request to the cloud server based on the user's authorization, the cloud server creates a trusted data task based on the data request submitted by the client and returns task information to the client. Correspondingly, the client receives the task information of the trusted data task returned by the cloud server. Furthermore, in order to achieve fine-grained management of data processing, the cloud server synchronously creates a cloud task corresponding to the trusted data task based on the trusted data task, or initializes a cloud task corresponding to the trusted data task, and combines the cloud task and the trusted data task to perform cross-terminal synchronous management of the data processing process.
[0024] Optionally, the trusted data task and the cloud task employ a two-level state machine for state coordination and synchronization. The cloud task's state includes: initialization state, running state, completion state, failure state, and / or shutdown state; the running state includes script loading sub-state, account login sub-state, and / or data query sub-state; the trusted data task's state includes: creation state, running state, completion state, failure state, and / or shutdown state.
[0025] In the specific execution process, after the client submits a data request to the cloud server, the cloud server can generate a globally unique request number, create a trusted data task, and mark the task status of the trusted data task as "created." Simultaneously, it creates the corresponding cloud task and marks the task status of the cloud task as "initialized." Furthermore, the client can obtain dynamic configurations from the cloud server by calling a configuration interface. The cloud server responds to the interface call by reading the corresponding configuration items from the configuration center and returning them to the client. After receiving the dynamic configuration items returned by the cloud server, the client stores these items to provide a basis for subsequent processing. The dynamic configuration items include: a mode configuration list, grayscale configuration, collection reminder configuration, function switches, and / or a problem list.
[0026] The trusted data task described in this embodiment refers to a data processing task that performs data processing under at least one trusted dimension. The trusted dimensions include: a trusted identity dimension (user identity is trusted), a trusted data source and / or trusted data authenticity dimension, a trusted transmission dimension (data transmission process is trusted, such as end-to-end encrypted transmission), a trusted behavior dimension (data operation process or data processing process is trusted), and / or a trusted transfer dimension (data transfer is authorized by the user). Furthermore, a trusted data task can also be replaced by a data task, such as a data processing task performed in scenarios where trusted dimensions are not used for data processing.
[0027] Step S204: Based on the cloud configuration parameters and local parameters obtained by calling the cloud interface, determine the cloud virtual mode used to perform trusted data processing.
[0028] In practice, the client submits a data request to the cloud server based on user authorization. After receiving the task information of the trusted data task returned by the cloud server, the client determines the cloud virtual mode for performing trusted data processing based on the cloud configuration parameters and local parameters obtained by calling the cloud interface. Furthermore, after determining the cloud virtual mode for trusted data processing, the client can submit the cloud virtual mode to the cloud server. Correspondingly, after receiving the cloud virtual mode, the cloud server can process the cloud instance corresponding to the cloud virtual mode and distribute and execute the execution script. Specifically, the processing of the cloud instance corresponding to the cloud virtual mode and the distribution and execution of the execution script include: scheduling the corresponding cloud instance according to the determined cloud virtual mode by the client and issuing the execution script of the cloud task to the cloud instance; initializing the virtual runtime environment of the cloud instance; and simulating the user's data collection operation on the target system by running the execution script.
[0029] In the specific execution process, when determining the cloud virtual mode based on cloud configuration parameters and local parameters, the determination of the cloud virtual mode can be approached from multiple dimensions to improve the success rate and availability of trusted data processing based on the determined cloud virtual mode. Specifically, in one optional implementation of this embodiment, the cloud virtual mode for performing trusted data processing is determined based on the cloud configuration parameters and local parameters obtained by calling the cloud interface, including: Read the mode tag from the mode configuration list issued by the cloud server, read the grayscale policy parameters in the grayscale configuration, and / or read the connection timeout records stored locally; Check whether the detection mode label, grayscale strategy parameters and / or connection timeout records meet the preset conditions. If yes, determine the cloud virtual mode as cloud phone mode; otherwise, determine the cloud virtual mode as cloud desktop mode.
[0030] Among them, cloud virtual mode refers to a data processing mode that runs automated execution scripts and simulates user operations to complete data processing in a cloud virtualization instance; cloud desktop mode refers to a mode that provides a virtual machine remote desktop based on cloud desktop service, which can operate the target system through automated scripts and is suitable for PC and complex page scenarios; cloud phone mode refers to a mode that provides an Android virtual instance based on cloud phone service, such as an Android virtual instance (cloud phone) provided by cloud phone service, which users can remotely access and view in real time through a client.
[0031] The mode configuration list refers to the list of cloud virtual modes configured for the current client after the cloud server submits a data request. The mode configuration list includes cloud desktop mode and / or cloud phone mode; the gray-scale configuration refers to the configuration parameters configured for gray-scale users to adopt the cloud phone mode. If the gray-scale policy parameter is a preset flag parameter, it indicates that the current user has met the gray-scale rules for adopting the cloud phone mode and is allowed to use the cloud phone mode; otherwise, if the gray-scale policy parameter is not a preset flag parameter, the current user has not met the gray-scale rules for adopting the cloud phone mode and is not allowed to use the cloud phone mode; the connection timeout record refers to the locally stored record indicating whether a connection timeout has occurred. Accordingly, the preset conditions can be that the mode configuration list contains the cloud phone mode, the gray-scale policy parameter is the preset flag parameter and the connection timeout record is empty. That is, the cloud phone mode can be used if the mode configuration list contains the cloud phone mode, the current user hits the gray-scale rule of using the cloud phone mode, the cloud phone mode is allowed, and the connection timeout record in the local storage is empty. If any of the preset conditions are not met, the cloud desktop mode is used.
[0032] Furthermore, the preset conditions can also be set to other forms. For example, the preset conditions can also be set to include cloud phone mode in the mode configuration list and have no connection timeout records. Correspondingly, the implementation process of determining the cloud virtual mode used to perform trusted data processing based on the cloud configuration parameters and local parameters obtained by calling the cloud interface can also be replaced with other implementation methods. For example, determining the cloud virtual mode used to perform trusted data processing based on the cloud configuration parameters and local parameters obtained by calling the cloud interface includes: reading the mode label from the mode configuration list issued by the cloud server and reading the connection timeout records stored locally; checking whether the mode label and connection timeout records meet the preset conditions. If yes, the cloud virtual mode is determined to be cloud phone mode; if not, the cloud virtual mode is determined to be cloud desktop mode.
[0033] Step S206: Invoke the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, and register to receive message callbacks for task execution status.
[0034] After determining the cloud virtual mode for trusted data processing, the client can submit the cloud virtual mode to the cloud server. After receiving the cloud virtual mode, the cloud server can process the cloud instance corresponding to the cloud virtual mode and distribute and execute the execution script. On this basis, the client calls the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance and registers to receive message callbacks for task execution status.
[0035] As mentioned above, cloud virtual modes include cloud phone mode and cloud desktop mode. In the case where the cloud virtual mode used to perform trusted data processing is determined to be either cloud phone mode or cloud desktop mode, the following will specifically explain the process of establishing a data channel with the cloud instance and the message callback registration process in either cloud phone mode or cloud desktop mode.
[0036] (1) Cloud desktop mode In the process of establishing a data channel for a cloud instance in cloud desktop mode, one optional implementation of this embodiment involves calling the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, including: calling the connection interface of the cloud service component corresponding to the cloud desktop mode to establish a remote connection with the cloud desktop virtual machine.
[0037] In the specific execution process, after the client submits the determined cloud desktop mode to the cloud server, the cloud server schedules the corresponding cloud instance based on the client's determined cloud desktop mode. Specifically, it schedules the cloud desktop virtual machine and sends the execution script of the cloud task to the cloud desktop virtual machine, initializes the runtime environment of the cloud desktop virtual machine, and accordingly, the client calls the connection interface of the cloud service component corresponding to the cloud desktop mode to establish a remote connection with the cloud desktop virtual machine. For example, the client calls the connect() method of the SDK (Software Development Kit) corresponding to the cloud desktop mode, passes in the connection parameters, and establishes a remote connection with the cloud desktop Windows virtual machine.
[0038] Furthermore, in one optional implementation of the message callback registration process in cloud desktop mode, the registration includes registering message callbacks for receiving task execution status, such as connection success callbacks, connection interruption callbacks, and / or running message callbacks in cloud desktop mode. Optionally, the running message callback is used to receive login events, password input events, and / or general pop-up events returned by the execution script of the cloud task.
[0039] In addition, during the message callback registration process in cloud desktop mode, besides registering the connection success callback, connection interruption callback, and / or running message callback mentioned above, the detection method for peripheral devices (such as keyboards) can also be configured according to the operating system type. Alternatively, if a password storage instruction submitted by the user is detected, the encrypted password text returned by the cloud instance can be received and stored in local storage.
[0040] For example, the lifecycle callbacks in the client-side cloud desktop registration mode include: connection success callback (onConnected), connection interruption callback (onDisConnected), and runtime message callback (onRuntimeMsg). The connection success callback (onConnected) marks the connection as ready and updates the page display synchronously. The connection interruption callback (onDisConnected) receives interactive events such as login pop-ups, password input, and general pop-ups returned by the automated execution script, synchronously driving the client page to render the corresponding interactive components. Additionally, the client is configured with keyboard detection capabilities: on iOS, it listens for the `visualViewport.resize` event, and on Android, it listens for the `window.resize` event, adapting to the page layout offset after the keyboard pops up. It also detects password input events; if the user chooses to save their account and password, it receives the encrypted password text returned by the automated execution script and stores it in the local cache, which can be automatically filled in subsequent data collections to avoid repeated input by the user.
[0041] (2) Cloud phone mode In the process of establishing a data channel for a cloud instance in cloud phone mode, one optional implementation of this embodiment involves calling the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, including: calling the session creation interface of the cloud service component corresponding to the cloud phone mode to create a session and start the connection, and rendering the cloud phone instance screen through the embedded frame of the page.
[0042] In the specific execution process, after the client submits the determined cloud phone mode to the cloud server, the cloud server schedules the corresponding cloud instance based on the client's determined cloud phone mode. Specifically, it schedules the cloud phone Android virtual instance and sends the execution script of the cloud task to the cloud phone instance, initializing the runtime environment of the cloud phone instance. Correspondingly, the client calls the session creation interface of the cloud service component corresponding to the cloud phone mode to create a cloud phone session, passes in the task connection parameters, starts the connection, and renders the cloud phone Android instance screen through the page's embedded frame. For example, the client calls the createSession() method of the WebSDK corresponding to the cloud phone mode to create an application flow session, passes in the connection parameters, calls the start() method to start the connection, and renders the running screen of the cloud phone Android instance in the page's embedded frame.
[0043] Furthermore, in the process of registering task execution status monitoring in cloud phone mode, in an optional implementation of this embodiment, the registration for receiving message callbacks of task execution status includes: registering data channel monitoring and connection interruption monitoring in cloud phone mode, and starting a timeout detection timer to detect connection status.
[0044] Specifically, the data channel listener is used to receive login page display messages, login success messages, and execution completion messages returned by the automated execution script; the connection interruption listener is used to trigger exception handling and mode degradation logic; the timeout detection timer is used to detect the connection establishment timeout, and if no page message is received within the timeout period, the connection is determined to have failed and the mode degradation process is triggered.
[0045] For example, the core listening and detection mechanism in the client registration cloud phone mode is as follows: bind the default data channel listener of the virtual device proxy to receive core process messages such as login page display, login success, and execution end returned by the automated execution script, and update the collection progress and execution page flow simultaneously; register a connection disconnection listener (onDisConnected) to trigger exception handling and mode degradation logic when the connection is interrupted; at the same time, start a 30-second timeout detection timer. If no login page display message is received within 30 seconds, the connection is determined to have failed, and the subsequent mode degradation process is triggered.
[0046] Step S208: Perform collection simulation rendering and display based on the collection simulation data returned by the data channel, and execute the page response action corresponding to the returned task status message.
[0047] In practice, after determining the cloud virtual mode based on cloud configuration parameters and local parameters, the client calls the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance and registers to receive message callbacks for task execution status. Correspondingly, the cloud server processes the cloud instance corresponding to the cloud virtual mode and distributes and executes the execution script. On this basis, the cloud server sends back the collected simulation data of the execution script to the client through the established data channel and sends back task status messages based on the task execution status. Correspondingly, the client performs collection simulation rendering and display based on the collected simulation data sent back through the data channel and executes the page response actions corresponding to the returned task status messages.
[0048] In specific execution, in cloud desktop mode, the cloud desktop virtual machine can encode the cloud desktop stream data that simulates user data collection operations on the target system by executing scripts, and push the encoded cloud desktop stream data through the data channel. The cloud service component corresponding to cloud desktop mode receives the encoded cloud desktop stream data pushed by the cloud desktop virtual machine, decodes the cloud desktop stream data, and renders the cloud desktop screen on the client page. Similarly, in cloud phone mode, the cloud phone instance can encode the cloud phone stream data that simulates user data collection operations on the target system by executing scripts, and push the encoded cloud phone stream data through the data channel. The cloud service component corresponding to cloud phone mode receives the encoded cloud phone stream data pushed by the cloud phone instance, decodes the cloud phone stream data, and renders the cloud phone screen on the client page.
[0049] In this embodiment, in cloud desktop mode or cloud phone mode, the user's data collection operation on the target system is simulated by running an execution script. It should be noted that the user's trusted data collected by simulating the user's data collection operation on the target system can be used for trusted processing of user data, such as trusted storage and trusted transfer. For example, it can be used to update the user's credit limit. Specifically, in an optional implementation of this embodiment, trusted user data is generated based on the data collection results of the execution script, so as to update the user's credit limit based on the trusted data.
[0050] In this embodiment, the cloud instance corresponding to the cloud virtual mode updates the status of the cloud task to obtain the task execution status, and sends the task execution status back to the client. The client then executes the page response action corresponding to the returned task status message. Specifically, in one optional implementation of this embodiment, executing the page response action corresponding to the returned task status message includes: updating the task status of the trusted data task or executing the message response operation corresponding to the task status message based on the task status of the cloud task corresponding to the trusted data task carried in the task status message. Optionally, the trusted data task and the cloud task use a two-level state machine for state coordination and synchronization.
[0051] For example, if the received task status message is a login success message, the data collection progress of the trusted data task is updated in real time based on the account login sub-status of the cloud task carried in the login success message. If the received task status message is a data acquisition failure message or a connection interruption message, an error message will be displayed on the client page, and a reload control will be displayed to reload the data. If the received task status message is an interactive event message (login pop-up message or password input message), the client page renders the interactive component corresponding to the interactive event message for the user to interact with.
[0052] Furthermore, to improve user retention, when a user is detected to have actively exited the trusted processing of user data, a reminder can be displayed to retain the user, thereby improving the retention rate of users participating in trusted user data processing. Specifically, in one optional implementation of this embodiment, the page response action corresponding to the returned task status message includes: If a user submits a data collection exit operation, the operation is intercepted, and an API is called to perform pre-exit detection for data collection. If the detection passes, read the user's collection reminder time record and determine whether the collection reminder condition has been triggered based on the time record. If triggered, display a reminder pop-up window for collection exit operation; if not triggered, do nothing, or perform resource cleanup corresponding to the cloud virtual mode. If the test fails, no action is required, or you can perform resource cleanup corresponding to the cloud virtual mode.
[0053] The pre-collection exit check can specifically check whether the user meets the reminder preconditions. If yes, the check passes; otherwise, it fails. The reminder preconditions can be that the user does not have a currently active trusted data task and the data request submission channel is not a preset channel, or that the user has not created a trusted data task and the data request submission channel is a preset channel. The reminder condition can be that the time interval between the previous collection reminder time and the current time in the time record is greater than a preset time interval.
[0054] In the specific execution process, the pop-up reminder for exiting the data collection operation can be displayed based on the page dimension of the client page where the user submitted the exit operation. This improves the user experience. Specifically, in one optional implementation of this embodiment, the pop-up reminder for exiting the data collection operation includes: generating a pop-up theme text corresponding to the page dimension of the client page where the exit operation was submitted, and displaying the pop-up theme text on the client page. Optionally, the time records of client pages with different page dimensions are stored independently. The page dimensions include: the form page dimension, the cloud desktop page dimension displaying the cloud desktop screen, and / or the cloud phone page dimension displaying the cloud phone screen.
[0055] As described above, this embodiment provides two cloud virtual modes: cloud desktop mode and cloud phone mode. To enhance the fault tolerance of trusted processing of user data, the continuity and high availability of trusted processing can also be ensured by switching between cloud virtual modes, such as switching from cloud phone mode to cloud desktop mode. Specifically, in one optional implementation of this embodiment, after the operation of calling the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance is executed, it further includes: Detect the connection status and task execution status of the cloud instance in cloud phone mode, and detect whether the virtual mode degradation conditions are triggered. If so, write the connection timeout record to local storage and call the task shutdown interface to handle the task shutdown in cloud phone mode; Call the task creation interface to create a trusted data task in cloud desktop mode, and then redirect to the cloud desktop page in cloud desktop mode.
[0056] Optionally, the virtual mode downgrade conditions include at least one of the following: the connection status is connection timeout or connection interruption, and the task execution status is execution error; if the connection status is connection timeout, a timeout flag is generated and the timeout flag is sent back to the front page through the page lifecycle event, and the front page reads the timeout flag and determines the cloud virtual mode as cloud desktop mode.
[0057] Accordingly, when switching from cloud phone mode to cloud desktop mode, the cloud server responds to the client's API call to close the task and performs the cloud instance switching process from cloud phone mode to cloud desktop mode. Specifically, the cloud instance switching process from cloud phone mode to cloud desktop mode includes: destroying the cloud instance corresponding to cloud phone mode, scheduling the cloud instance corresponding to cloud desktop mode and issuing the execution script to downgrade from cloud phone mode to cloud desktop mode.
[0058] In practical applications, when a user logs out or the trusted processing of user data ends, resource cleanup corresponding to the cloud virtual mode can be performed to avoid resource occupation. Specifically, in one optional implementation of this embodiment, after performing collection simulation rendering and display based on the collected simulation data returned from the data channel, and executing the page response action corresponding to the returned task status message, the method further includes: responding to the page unload event or collection end event, performing resource cleanup corresponding to the cloud virtual mode. Specifically, resource cleanup corresponding to the cloud virtual mode includes: if it is a cloud desktop mode, disconnecting the remote connection with the cloud desktop virtual machine and deleting message callbacks; if it is a cloud phone mode, destroying the timeout timer and deleting the cloud phone session instance.
[0059] In summary, the cloud service-based data processing method provided in this embodiment, during the trusted processing of user data, involves submitting a data request to the cloud server based on user authorization and receiving task information for the trusted data task returned by the cloud server. Based on cloud configuration parameters and local parameters obtained by calling the cloud interface, a cloud virtual mode for executing trusted data processing is determined. A data channel is established between the cloud service component corresponding to the cloud virtual mode and the cloud instance, and a message callback for receiving task execution status is registered. The cloud server runs an execution script on the cloud instance corresponding to the cloud virtual mode to simulate user data collection operations on the target system and sends back simulated collection data. Based on the simulated collection data sent back through the data channel, a collection simulation rendering display is performed, and the page response action corresponding to the returned task status message is executed. This achieves trusted processing of user data through the cooperation of the client and the cloud server, ensuring user data security during the data processing process. Furthermore, data processing efficiency is improved by running automated execution scripts on the cloud instance corresponding to the scheduled cloud virtual mode, which also helps expand the applicable scenarios for data processing. In addition, the stability of data processing can be improved by switching between cloud virtual modes.
[0060] It should be noted that steps S202 to S208 provided in this embodiment can be executed by the client. It should also be noted that steps S202 to S208 executed by the client and steps S402 to S408 executed by the cloud server in the following embodiment can cooperate with each other during execution. Therefore, when reading this embodiment, please refer to the corresponding content of steps S402 to S408 provided in the following method embodiment. When reading the following method embodiment, please refer to the corresponding content of steps S202 to S208 provided in this embodiment.
[0061] The following example illustrates the application of a cloud service-based data processing method in a trusted user data collection scenario, combined with... Figure 3 The cloud service-based data processing method provided in this embodiment will be further explained below. Figure 3 A cloud-based data processing method for trusted user data collection scenarios includes the following steps.
[0062] Step S302: Obtain the processing request submitted by the user through the trusted data collection portal.
[0063] Step S304: Call the user verification interface on the cloud server to perform access verification for the user.
[0064] Step S306: If the access verification passes, call the task query interface to query whether the user has a trusted data task with a status. If present, execute the corresponding task recovery strategy based on the task status of the trusted data task in progress. If it does not exist, proceed to step S308; Step S308: Perform user identity verification and submit a data request to the cloud server after the identity verification is passed.
[0065] Step S312: Receive the task information of the data collection task returned by the cloud server.
[0066] Step S316: Based on the cloud configuration parameters and local parameters obtained by calling the cloud interface, determine the cloud virtual mode used to perform trusted data processing.
[0067] Step S318: Submit the confirmed cloud virtual mode to the cloud server.
[0068] Step S324: Invoke the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, and register to receive message callbacks for task execution status.
[0069] Step S328: Perform acquisition simulation rendering and display based on the acquisition simulation data returned from the data channel.
[0070] Step S332: Execute the page response action corresponding to the returned task status message.
[0071] It should be noted that any one or more steps in steps S302 to S308, S312, S316 to S318, S324, S328, and S332 can be combined with any one or more steps in steps S202 to S208 to form a new implementation method according to the needs of implementation and deployment. Furthermore, steps S302 to S308, S312, S316 to S318, S324, S328, and S332 can be combined with any one or more steps in steps S202 to S208 to form a new implementation method, depending on the actual deployment needs. 32. Select any one or more technical features and combine them with any one or more technical features provided in steps S202 to S208 to form a new implementation method; or, any one or more technical features in steps S302 to S308, S312, S316 to S318, S324, S328, and S332 can be replaced with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs, which will not be elaborated here.
[0072] Furthermore, it should be noted that steps S302 to S308, S312, S316 to S318, S324, S328, and S332 provided in this embodiment can be executed by the client. It should be noted that the client-executed steps S302 to S308, S312, S316 to S318, S324, S328, and S332 are different from steps S310, S314, and S332 executed by the cloud server in the following embodiment. Steps S320 to S322, S326, and S330 can cooperate with each other during execution. Therefore, when reading this embodiment, please refer to the corresponding content of steps S310, S314, S320 to S322, S326, and S330 provided in the following method embodiment. When reading the following method embodiment, please refer to the corresponding content of steps S302 to S308, S312, S316 to S318, S324, S328, and S332 provided in this embodiment.
[0073] One or more embodiments of another cloud service-based data processing method provided in this specification are as follows: Reference Figure 4The data processing method based on cloud services provided in this embodiment can be applied to cloud service terminals. The method specifically includes steps S402 to S408.
[0074] Step S402: Create a trusted data task based on the data request submitted by the client and return the task information, and initialize the cloud task corresponding to the trusted data task.
[0075] In this embodiment, during the trusted processing of user data, the user can submit data processing instructions through a client. Upon receiving the user's data processing instructions, the client can perform user authorization interaction and submit a data request to the cloud server after the user authorization interaction is completed. A data request refers to a processing request for trusted processing of user data. Specifically, a data request can be a processing request for trusted processing of user data in a specific scenario or service, such as trusted processing of user data in a user credit maintenance scenario, specifically, updating user credit through trusted processing of user data. Correspondingly, in this case, the data processing entry point configured in the application or subroutine refers to the trusted processing entry point for trusted processing of user data, specifically, it can be the trusted processing entry point for user data in a specific scenario or service.
[0076] In practice, to improve the efficiency of trusted user data processing, upon receiving a user-submitted data processing instruction, the client can verify the user's access by calling the cloud server's user verification interface. Correspondingly, the cloud server responds to the user verification interface call by verifying whether the user meets the access conditions for a specific scenario or service and returns the verification result to the client. If the access verification passes, user authorization is initiated, and a data request is submitted to the cloud server after authorization. If the access verification fails, an access failure notification is generated. Furthermore, to enhance user data security, upon receiving a user-submitted data processing instruction, the client can also perform user identity verification and submit a data request to the cloud server after successful verification.
[0077] In practical applications, when a user accesses data processing through the application or subroutine's data processing entry point, it may be the user's first time accessing data processing, or it may be that the user has already accessed data processing and is now accessing it to query the data processing results. In this case, before submitting a data request to the cloud server based on user authorization, the user's data task can be queried. If the user's data task is found, it indicates that the user's current access is to query the data processing results, and the user's task can be restored. If the user's data task is not found, a data request can be submitted to the cloud server based on user authorization.
[0078] In one optional implementation of this embodiment, before creating a trusted data task based on the data request submitted by the client and returning task information, the following processing is performed: In response to the client's interface call to the task query interface, the system queries whether the user has a trusted data task in progress based on the user's application identifier passed to the task query interface. If so, the system works with the client to execute the corresponding task recovery strategy according to the task status of the trusted data task in progress. If not, the system proceeds to the next step, that is, creating a trusted data task based on the data request submitted by the client and returning task information.
[0079] Specifically, in coordination with the client, the corresponding task recovery strategy is executed, including: if the task status is in the creation or running state, polling the task status based on the task identifier and redirecting to the corresponding cloud instance page; if the task status is in the completed state, redirecting to the task result page; otherwise, if the task status is in the closed or failed state, the task re-creation process is initiated, executing the operation of creating a trusted data task based on the data application submitted by the client and returning the task information.
[0080] In practice, after a user submits a data request to the cloud server based on the user's authorization, the cloud server creates a trusted data task based on the data request submitted by the client and returns task information to the client. Correspondingly, the client receives the task information of the trusted data task returned by the cloud server. Furthermore, in order to achieve fine-grained management of data processing, the cloud server synchronously creates a cloud task corresponding to the trusted data task based on the trusted data task, or initializes a cloud task corresponding to the trusted data task, and combines the cloud task and the trusted data task to perform cross-terminal synchronous management of the data processing process.
[0081] Optionally, the trusted data task and the cloud task employ a two-level state machine for state coordination and synchronization. The cloud task's state includes: initialization state, running state, completion state, failure state, and / or shutdown state; the running state includes script loading sub-state, account login sub-state, and / or data query sub-state; the trusted data task's state includes: creation state, running state, completion state, failure state, and / or shutdown state.
[0082] In the specific execution process, after the client submits a data request to the cloud server, the cloud server can generate a globally unique request number, create a trusted data task, and mark the task status of the trusted data task as "created." Simultaneously, it creates the corresponding cloud task and marks the task status of the cloud task as "initialized." Furthermore, the client can obtain dynamic configurations from the cloud server by calling a configuration interface. The cloud server responds to the interface call by reading the corresponding configuration items from the configuration center and returning them to the client. After receiving the dynamic configuration items returned by the cloud server, the client stores these items to provide a basis for subsequent processing. The dynamic configuration items include: a mode configuration list, grayscale configuration, collection reminder configuration, function switches, and / or a problem list.
[0083] The trusted data task described in this embodiment refers to a data processing task that performs data processing under at least one trusted dimension. The trusted dimensions include: a trusted identity dimension (user identity is trusted), a trusted data source and / or trusted data authenticity dimension, a trusted transmission dimension (data transmission process is trusted, such as end-to-end encrypted transmission), a trusted behavior dimension (data operation process or data processing process is trusted), and / or a trusted transfer dimension (data transfer is authorized by the user). Furthermore, a trusted data task can also be replaced by a data task, such as a data processing task performed in scenarios where trusted dimensions are not used for data processing.
[0084] Step S404: Based on the client's scheduling of the corresponding cloud instance for the determined cloud virtual mode, the execution script of the cloud task is sent to the cloud instance.
[0085] In practice, the client submits a data request to the cloud server based on user authorization and receives the task information of the trusted data task returned by the cloud server. Based on the cloud configuration parameters and local parameters obtained by calling the cloud interface, the client determines the cloud virtual mode for performing trusted data processing. In addition, after determining the cloud virtual mode for performing trusted data processing, the client can submit the cloud virtual mode to the cloud server. Accordingly, after receiving the cloud virtual mode, the cloud server schedules the corresponding cloud instance according to the cloud virtual mode determined by the client and sends the execution script of the cloud task to the cloud instance.
[0086] In the specific execution process, the determination of the cloud virtual mode can be based on multiple dimensions to improve the success rate and availability of reliable data processing based on the determined cloud virtual mode. Specifically, in one optional implementation of this embodiment, the cloud virtual mode is determined in the following way: whether the mode label in the mode configuration list, the grayscale strategy parameters in the grayscale configuration, and / or the connection timeout records stored locally meet the preset conditions. If yes, the cloud virtual mode is determined as cloud phone mode; if not, the cloud virtual mode is determined as cloud desktop mode.
[0087] Among them, cloud virtual mode refers to a data processing mode that runs automated execution scripts and simulates user operations to complete data processing in a cloud virtualization instance; cloud desktop mode refers to a mode that provides a virtual machine remote desktop based on cloud desktop service, which can operate the target system through automated scripts and is suitable for PC and complex page scenarios; cloud phone mode refers to a mode that provides an Android virtual instance based on cloud phone service, such as an Android virtual instance (cloud phone) provided by cloud phone service, which users can remotely access and view in real time through a client.
[0088] The mode configuration list refers to the list of cloud virtual modes configured for the current client after the cloud server submits a data request. The mode configuration list includes cloud desktop mode and / or cloud phone mode; the gray-scale configuration refers to the configuration parameters configured for gray-scale users to adopt the cloud phone mode. If the gray-scale policy parameter is a preset flag parameter, it indicates that the current user has met the gray-scale rules for adopting the cloud phone mode and is allowed to use the cloud phone mode; otherwise, if the gray-scale policy parameter is not a preset flag parameter, the current user has not met the gray-scale rules for adopting the cloud phone mode and is not allowed to use the cloud phone mode; the connection timeout record refers to the locally stored record indicating whether a connection timeout has occurred. Accordingly, the preset conditions can be that the mode configuration list contains the cloud phone mode, the gray-scale policy parameter is the preset flag parameter and the connection timeout record is empty. That is, the cloud phone mode can be used if the mode configuration list contains the cloud phone mode, the current user hits the gray-scale rule of using the cloud phone mode, the cloud phone mode is allowed, and the connection timeout record in the local storage is empty. If any of the preset conditions are not met, the cloud desktop mode is used.
[0089] In addition, the preset conditions can also be set to other forms. For example, the preset conditions can also be set to include cloud phone mode in the mode configuration list and the connection timeout record is empty. Correspondingly, the process of determining the cloud virtual mode can also be replaced with other implementation methods. For example, the cloud virtual mode can also be determined in the following way: check whether the mode label in the mode configuration list and the connection timeout record in the local storage meet the preset conditions. If yes, the cloud virtual mode is determined to be cloud phone mode; if no, the cloud virtual mode is determined to be cloud desktop mode.
[0090] Step S406: Initialize the virtual runtime environment of the cloud instance, and simulate the user's data collection operation on the target system by running the execution script.
[0091] The above process involves the client scheduling the corresponding cloud instance for the determined cloud virtual mode, sending the execution script of the cloud task to the cloud instance, initializing the virtual runtime environment of the cloud instance, and simulating the user's data collection operation on the target system by running the execution script. On this basis, the client calls the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance and registers to receive message callbacks for task execution status.
[0092] As mentioned above, cloud virtual mode includes cloud phone mode and cloud desktop mode. In the case that the cloud virtual mode used to perform trusted data processing is determined to be cloud phone mode or cloud desktop mode, the following will specifically explain the process of establishing a data channel between the client and the cloud instance in cloud phone mode or cloud desktop mode and the process of registering message callback.
[0093] During the process of establishing a data channel for a cloud instance in cloud desktop mode, the client establishes a data channel with the cloud instance by calling the cloud service component corresponding to the cloud virtual mode. Specifically, the client can call the connection interface of the cloud service component corresponding to the cloud desktop mode to establish a remote connection with the cloud desktop virtual machine.
[0094] In the specific execution process, after the client submits the determined cloud desktop mode to the cloud server, the cloud server schedules the corresponding cloud instance based on the client's determined cloud desktop mode. Specifically, it schedules the cloud desktop virtual machine and sends the execution script of the cloud task to the cloud desktop virtual machine, initializes the runtime environment of the cloud desktop virtual machine, and accordingly, the client calls the connection interface of the cloud service component corresponding to the cloud desktop mode to establish a remote connection with the cloud desktop virtual machine; for example, the client calls the connect() method of the SDK corresponding to the cloud desktop mode, passes in the connection parameters, and establishes a remote connection with the cloud desktop Windows virtual machine.
[0095] Furthermore, during the message callback registration process in cloud desktop mode, the client registers message callbacks for receiving task execution status. Specifically, it can register connection success callbacks, connection interruption callbacks, and / or run message callbacks in cloud desktop mode. Optionally, the run message callback is used to receive login events, password input events, and / or general pop-up events returned by the execution script of the cloud task.
[0096] In addition, during the message callback registration process in cloud desktop mode, besides registering the connection success callback, connection interruption callback, and / or running message callback mentioned above, the detection method for peripheral devices (such as keyboards) can also be configured according to the operating system type. Alternatively, if a password storage instruction submitted by the user is detected, the encrypted password text returned by the cloud instance can be received and stored in local storage.
[0097] For example, the lifecycle callbacks in the client-side cloud desktop registration mode include: connection success callback (onConnected), connection interruption callback (onDisConnected), and runtime message callback (onRuntimeMsg). The connection success callback (onConnected) marks the connection as ready and updates the page display synchronously. The connection interruption callback (onDisConnected) receives interactive events such as login pop-ups, password input, and general pop-ups returned by the automated execution script, synchronously driving the client page to render the corresponding interactive components. Additionally, the client is configured with keyboard detection capabilities: on iOS, it listens for the `visualViewport.resize` event, and on Android, it listens for the `window.resize` event, adapting to the page layout offset after the keyboard pops up. It also detects password input events; if the user chooses to save their account and password, it receives the encrypted password text returned by the automated execution script and stores it in the local cache, which can be automatically filled in subsequent data collections to avoid repeated input by the user.
[0098] In addition, during the process of establishing a data channel for a cloud instance in cloud phone mode, the client can establish a data channel with the cloud instance by calling the cloud service component corresponding to the cloud virtual mode. Specifically, the client can call the session creation interface of the cloud service component corresponding to the cloud phone mode to create a session and start the connection, and render the cloud phone instance screen through the embedded frame of the page.
[0099] In the specific execution process, after the client submits the determined cloud phone mode to the cloud server, the cloud server schedules the corresponding cloud instance based on the client's determined cloud phone mode. Specifically, it schedules the cloud phone Android virtual instance and sends the execution script of the cloud task to the cloud phone instance, initializing the runtime environment of the cloud phone instance. Correspondingly, the client calls the session creation interface of the cloud service component corresponding to the cloud phone mode to create a cloud phone session, passes in the task connection parameters, starts the connection, and renders the cloud phone Android instance screen through the page's embedded frame. For example, the client calls the createSession() method of the WebSDK corresponding to the cloud phone mode to create an application flow session, passes in the connection parameters, calls the start() method to start the connection, and renders the running screen of the cloud phone Android instance in the page's embedded frame.
[0100] Furthermore, in the process of registering task execution status monitoring in cloud phone mode, in an optional implementation of this embodiment, the registration for receiving message callbacks of task execution status includes: registering data channel monitoring and connection interruption monitoring in cloud phone mode, and starting a timeout detection timer to detect connection status.
[0101] Specifically, the data channel listener is used to receive login page display messages, login success messages, and execution completion messages returned by the automated execution script; the connection interruption listener is used to trigger exception handling and mode degradation logic; the timeout detection timer is used to detect the connection establishment timeout, and if no page message is received within the timeout period, the connection is determined to have failed and the mode degradation process is triggered.
[0102] For example, the core listening and detection mechanism in the client registration cloud phone mode is as follows: bind the default data channel listener of the virtual device proxy to receive core process messages such as login page display, login success, and execution end returned by the automated execution script, and update the collection progress and execution page flow simultaneously; register a connection disconnection listener (onDisConnected) to trigger exception handling and mode degradation logic when the connection is interrupted; at the same time, start a 30-second timeout detection timer. If no login page display message is received within 30 seconds, the connection is determined to have failed, and the subsequent mode degradation process is triggered.
[0103] Step S408: The collected simulation data of the execution script is sent back to the client through the established data channel, and the task status message is sent back based on the task execution status.
[0104] In practice, the cloud server schedules the corresponding cloud instance based on the client's determined cloud virtual mode and sends the execution script of the cloud task to the cloud instance. Correspondingly, after the client determines the cloud virtual mode based on the cloud configuration parameters and local parameters, it calls the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance and registers to receive message callbacks for task execution status. During this process, the cloud server initializes the virtual runtime environment of the cloud instance and simulates the user's data collection operation on the target system by executing the script. Afterward, the cloud server sends back the collected simulated data of the execution script to the client through the established data channel and sends back task status messages based on the task execution status.
[0105] In specific execution, in cloud desktop mode, the cloud desktop virtual machine can encode the cloud desktop stream data that simulates user data collection operations on the target system by executing scripts, and push the encoded cloud desktop stream data through the data channel. The cloud service component corresponding to cloud desktop mode receives the encoded cloud desktop stream data pushed by the cloud desktop virtual machine, decodes the cloud desktop stream data, and renders the cloud desktop screen on the client page. Similarly, in cloud phone mode, the cloud phone instance can encode the cloud phone stream data that simulates user data collection operations on the target system by executing scripts, and push the encoded cloud phone stream data through the data channel. The cloud service component corresponding to cloud phone mode receives the encoded cloud phone stream data pushed by the cloud phone instance, decodes the cloud phone stream data, and renders the cloud phone screen on the client page.
[0106] In this embodiment, in cloud desktop mode or cloud phone mode, the user's data collection operation on the target system is simulated by running an execution script. It should be noted that the user's trusted data collected by simulating the user's data collection operation on the target system can be used for trusted processing of user data, such as trusted storage and trusted transfer. For example, it can be used to update the user's credit limit. Specifically, in an optional implementation of this embodiment, trusted user data is generated based on the data collection results of the execution script, so as to update the user's credit limit based on the trusted data.
[0107] In this embodiment, the cloud instance corresponding to the cloud virtual mode updates the status of the cloud task to obtain the task execution status, and sends the task execution status back to the client. The client then executes the page response action corresponding to the returned task status message. Specifically, in one optional implementation of this embodiment, executing the page response action corresponding to the returned task status message includes: updating the task status of the trusted data task or executing the message response operation corresponding to the task status message based on the task status of the cloud task corresponding to the trusted data task carried in the task status message. Optionally, the trusted data task and the cloud task use a two-level state machine for state coordination and synchronization.
[0108] For example, if the received task status message is a login success message, the data collection progress of the trusted data task is updated in real time based on the account login sub-status of the cloud task carried in the login success message; if the received task status message is a collection failure message or a connection interruption message, an error message is displayed on the client page, and a reload control is displayed for reloading; if the received task status message is an interactive event message (login pop-up message or password input message), the client page renders the interactive component corresponding to the interactive event message for the user to interact with.
[0109] In addition, in order to improve user retention, when it is detected that a user has actively exited the trusted processing of user data, a reminder can be shown to the user to retain the user, thereby improving the retention rate of users participating in trusted processing of user data. Specifically, in an optional implementation of this embodiment, the task status message is returned based on the task execution status, including: responding to the interface call of the client when it detects and intercepts the user's submitted collection exit operation, and performing collection exit pre-detection. Accordingly, the client executes the page response actions corresponding to the returned task status message, including: if a user-submitted data collection exit operation is detected, the data collection exit operation is intercepted, and the interface is called to perform pre-exit detection; if the detection passes, the user's data collection reminder time record is read, and the data collection reminder condition is determined based on the time record; if triggered, a reminder pop-up for the data collection exit operation is displayed; if not triggered, no action is taken, or the corresponding resource cleanup in the cloud virtual mode is performed; if the detection fails, no action is taken, or the corresponding resource cleanup in the cloud virtual mode is performed.
[0110] The pre-collection exit check can specifically check whether the user meets the reminder preconditions. If yes, the check passes; otherwise, it fails. The reminder preconditions can be that the user does not have a currently active trusted data task and the data request submission channel is not a preset channel, or that the user has not created a trusted data task and the data request submission channel is a preset channel. The reminder condition can be that the time interval between the previous collection reminder time and the current time in the time record is greater than a preset time interval.
[0111] In the specific execution process, the pop-up reminder for exiting the data collection operation can be displayed based on the page dimension of the client page where the user submitted the exit operation. This improves the user experience. Specifically, in one optional implementation of this embodiment, the pop-up reminder for exiting the data collection operation includes: generating a pop-up theme text corresponding to the page dimension of the client page where the exit operation was submitted, and displaying the pop-up theme text on the client page. Optionally, the time records of client pages with different page dimensions are stored independently. The page dimensions include: the form page dimension, the cloud desktop page dimension displaying the cloud desktop screen, and / or the cloud phone page dimension displaying the cloud phone screen.
[0112] As described above, this embodiment provides two cloud virtual modes: cloud desktop mode and cloud phone mode. To enhance the fault tolerance of trusted processing of user data, the continuity and high availability of trusted processing can be ensured by switching between cloud virtual modes. For example, when switching from cloud phone mode to cloud desktop mode, specifically, after the client calls the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, it checks the connection status and task execution status of the cloud instance in cloud phone mode and checks whether the virtual mode degradation condition is triggered. If so, it writes a connection timeout record to local storage, calls the task shutdown interface to perform task shutdown processing in cloud phone mode, calls the task creation interface to create a trusted data task in cloud desktop mode, and jumps to the cloud desktop page in cloud desktop mode.
[0113] Optionally, the virtual mode downgrade conditions include at least one of the following: the connection status is connection timeout or connection interruption, and the task execution status is execution error; if the connection status is connection timeout, a timeout flag is generated and the timeout flag is sent back to the front page through the page lifecycle event, and the front page reads the timeout flag and determines the cloud virtual mode as cloud desktop mode.
[0114] Accordingly, when switching from cloud phone mode to cloud desktop mode, the cloud server responds to the client's API call to close the task and performs the cloud instance switching process from cloud phone mode to cloud desktop mode. Specifically, the cloud instance switching process from cloud phone mode to cloud desktop mode includes: destroying the cloud instance corresponding to cloud phone mode, scheduling the cloud instance corresponding to cloud desktop mode and issuing the execution script to downgrade from cloud phone mode to cloud desktop mode.
[0115] In practical applications, when a user logs out or the trusted processing of user data ends, resource cleanup corresponding to the cloud virtual mode can be performed to avoid resource consumption. Specifically, after the client performs simulated data collection and rendering based on the simulated data returned from the data channel and executes the page response action corresponding to the returned task status message, it responds to the page unload event or the data collection end event to perform resource cleanup corresponding to the cloud virtual mode. Specifically, resource cleanup corresponding to the cloud virtual mode includes: if it is a cloud desktop mode, disconnecting the remote connection with the cloud desktop virtual machine and deleting message callbacks; if it is a cloud phone mode, destroying the timeout timer and deleting the cloud phone session instance. Accordingly, the cloud server performs cloud instance release processing for the cloud virtual mode. Specifically, the cloud instance release processing for the cloud virtual mode includes: if it is cloud desktop mode, disconnecting the remote connection with the client and releasing the cloud desktop virtual machine; if it is cloud phone mode, disconnecting the remote connection with the client and releasing the cloud phone instance corresponding to the cloud phone mode scheduling.
[0116] The following example illustrates the application of a cloud service-based data processing method in a trusted user data collection scenario, combined with... Figure 3 The cloud service-based data processing method provided in this embodiment will be further explained below. Figure 3 A cloud-based data processing method for trusted user data collection scenarios includes the following steps.
[0117] Step S310: Create a data acquisition task based on the data request submitted by the client, and return task information to the client.
[0118] Step S314: Initialize the cloud task corresponding to the data acquisition task.
[0119] Step S320: Schedule the corresponding cloud instance according to the cloud virtual mode submitted by the client, and send the automated execution script of the cloud task to the cloud instance.
[0120] Step S322: Initialize the virtual runtime environment of the cloud instance and simulate the user's data collection operation on the target system by running an automated execution script.
[0121] Step S326: The collected simulation data of the automated execution script is sent back to the client through the established data channel.
[0122] Step S330: Send a task status message back to the client based on the task execution status.
[0123] It should be noted that any one or more of steps S310, S314, S320 to S322, S326, and S330 can be combined with any one or more of steps S402 to S408 to form a new implementation method according to the needs of implementation and deployment. Furthermore, any one of steps S310, S314, S320 to S322, S326, and S330 can be selected according to the actual deployment needs. One or more technical features may be combined with any one or more technical features provided in steps S402 to S408 to form a new implementation method; or, any one or more technical features in steps S310, S314, S320 to S322, S326, and S330 may be replaced with any one or more technical features provided in steps S402 to S408 to form a new implementation method according to the actual deployment needs, which will not be elaborated here.
[0124] This specification provides an embodiment of a cloud service-based data processing device as follows: In the above embodiments, a cloud service-based data processing method is provided, and correspondingly, a cloud service-based data processing device is also provided, which will be described below with reference to the accompanying drawings.
[0125] Reference Figure 5 This illustration shows a schematic diagram of an embodiment of a cloud service-based data processing device provided in this embodiment.
[0126] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.
[0127] This embodiment provides a cloud service-based data processing device that runs on a client side. The device includes: The data request submission module 502 is configured to submit a data request to the cloud server based on user authorization and receive task information of the trusted data task returned by the cloud server. The virtual mode determination module 504 is configured to determine the cloud virtual mode used to perform trusted data processing based on cloud configuration parameters and local parameters obtained by calling the cloud interface. The data channel establishment module 506 is configured to call the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, and register to receive message callbacks for task execution status; The rendering response module 508 is configured to perform simulated rendering and display of the collected data based on the collected simulation data returned by the data channel, and to execute the page response action corresponding to the returned task status message.
[0128] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more embodiments of this specification, the functions of each module or unit can be implemented in one or more software and / or hardware components, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.
[0129] Another embodiment of a cloud-based data processing device provided in this specification is as follows: In the above embodiments, another cloud service-based data processing method is provided, and correspondingly, another cloud service-based data processing device is also provided, which will be described below with reference to the accompanying drawings.
[0130] Reference Figure 6 This illustration shows a schematic diagram of an embodiment of a cloud service-based data processing device provided in this embodiment.
[0131] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.
[0132] This embodiment provides a cloud service-based data processing device that runs on a cloud server. The device includes: The task creation module 602 is configured to create a trusted data task based on a data request submitted by the client and return task information, and initialize the cloud task corresponding to the trusted data task. The cloud instance processing module 604 is configured to schedule the corresponding cloud instance according to the client for the determined cloud virtual mode, and send the execution script of the cloud task to the cloud instance; The script execution module 606 is configured to initialize the virtual runtime environment of the cloud instance and simulate the user's data collection operation in the target system by running the execution script; The data feedback module 608 is configured to send back the collected simulation data of the execution script to the client through the established data channel, and to send back task status messages based on the task execution status.
[0133] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more embodiments of this specification, the functions of each module or unit can be implemented in one or more software and / or hardware components, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.
[0134] This specification provides the following embodiment of a cloud-based data processing device: Corresponding to the cloud service-based data processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide a cloud service-based data processing device, which is used to execute the cloud service-based data processing method described above. Figure 7 This is a schematic diagram of the structure of a cloud service-based data processing device provided for one or more embodiments of this specification.
[0135] This embodiment provides a cloud service-based data processing device, including: like Figure 7As shown, device 700 mainly consists of a communication interface 702, a user interface 704, a processor 706, and a data storage 708. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 710. The communication interface 702 enables device 700 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, the communication interface 702 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, the communication interface 702 can be a wired interface such as Ethernet, Token Ring, or a USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or a wide-area wireless interface (e.g., WiMAX or LTE). Of course, the communication interface 702 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. The communication interface 702 may also include multiple physical communication interfaces, such as Wi-Fi, Bluetooth, and wide-area wireless interfaces. The user interface 704 includes receiving user input and providing output to the user. Therefore, user interface 704 may include input components such as a keypad, keyboard, touch panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with the touch panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. User interface 704 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, user interface 704 may include software, circuitry, or other forms of logic capable of transmitting and receiving data from external user input / output devices. Additionally or alternatively, device 700 may support remote access from other devices via communication interface 702 or another physical interface (not shown). User interface 704 may be configured to receive user input, the position and movement of which may be indicated by indicators or cursors described herein. User interface 704 may also be configured as a display device for rendering or displaying text fragments.
[0136] Processor 706 may include one or more general-purpose processors and / or special-purpose processors. Data storage 708 may include one or more volatile and / or non-volatile storage components, and may be integrated wholly or partially with processor 706. Data storage 708 may include removable and non-removable components.
[0137] Processor 706 is capable of executing program instructions 718 (e.g., compiled or uncompiled program logic and / or machine code) stored in data storage 708 to perform the various functions described herein. Data storage 708 may comprise a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 700, enable device 700 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 718 by processor 706 may result in processor 706 using data 712. For example, program instructions 718 may include an operating system 722 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 700 and one or more application programs 720 (e.g., a browser, social application, or game application). Similarly, data 712 may include operating system data 716 and application data 714. Operating system data 716 is primarily accessible to operating system 722, while application data 714 is primarily accessible to one or more application programs 720. Application data 714 may reside in a file system visible or hidden from the user of device 700. Application 720 can communicate with operating system 722 through one or more application programming interfaces (APIs). These APIs facilitate application 720 in reading and / or writing application data 714, transmitting or receiving information via communication interface 702, and receiving or displaying information on user interface 704. In some terms, application 720 may be simply referred to as "app". Furthermore, application 720 can be downloaded to device 700 through one or more online app stores or app markets. However, applications can also be installed on device 700 in other ways, such as through a web browser or a physical interface on device 700 (e.g., a USB port).
[0138] In one specific embodiment, the cloud-based data processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for use in the cloud-based data processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: Based on user authorization, the user submits a data request to the cloud server and receives task information for the trusted data task returned by the cloud server. Based on the cloud configuration parameters and local parameters obtained by calling the cloud interface, determine the cloud virtual mode used to perform trusted data processing; Invoke the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, and register to receive message callbacks for task execution status; The collected simulation data is collected and rendered based on the data channel, and the page response action corresponding to the returned task status message is executed.
[0139] Another embodiment of a cloud-based data processing device provided in this specification is as follows: Corresponding to the other cloud service-based data processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide another cloud service-based data processing device, which is used to execute the other cloud service-based data processing method provided above. Figure 8 This is a schematic diagram of another cloud-based data processing device provided in one or more embodiments of this specification.
[0140] This embodiment provides a cloud service-based data processing device, including: like Figure 8As shown, device 800 mainly consists of a communication interface 802, a user interface 804, a processor 806, and a data storage 808. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 810. The communication interface 802 enables device 800 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, the communication interface 802 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, the communication interface 802 can be a wired interface such as Ethernet, Token Ring, or a USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or a wide-area wireless interface (e.g., WiMAX or LTE). Of course, the communication interface 802 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. The communication interface 802 may also include multiple physical communication interfaces, such as Wi-Fi, Bluetooth, and wide-area wireless interfaces. The user interface 804 includes receiving user input and providing output to the user. Therefore, user interface 804 may include input components such as a keypad, keyboard, touch panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with the touch panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. User interface 804 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, user interface 804 may include software, circuitry, or other forms of logic capable of transmitting and receiving data to and from external user input / output devices. Additionally or alternatively, device 800 may support remote access from other devices via communication interface 802 or another physical interface (not shown). User interface 804 may be configured to receive user input, the position and movement of which may be indicated by indicators or cursors described herein. User interface 804 may also be configured as a display device for rendering or displaying text fragments.
[0141] Processor 806 may include one or more general-purpose processors and / or special-purpose processors. Data storage 808 may include one or more volatile and / or non-volatile storage components, and may be integrated wholly or partially with processor 806. Data storage 808 may include removable and non-removable components.
[0142] Processor 806 is capable of executing program instructions 818 (e.g., compiled or uncompiled program logic and / or machine code) stored in data storage 808 to perform the various functions described herein. Data storage 808 may comprise a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 800, enable device 800 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 818 by processor 806 may result in processor 806 using data 812. For example, program instructions 818 may include an operating system 822 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 800 and one or more application programs 820 (e.g., a browser, social application, or game application). Similarly, data 812 may include operating system data 816 and application data 814. Operating system data 816 is primarily accessible to operating system 822, while application data 814 is primarily accessible to one or more application programs 820. Application data 814 may reside in a file system visible or hidden from the user of device 800. Application 820 can communicate with operating system 822 through one or more application programming interfaces (APIs). These APIs facilitate application 820 in reading and / or writing application data 814, transmitting or receiving information via communication interface 802, and receiving or displaying information on user interface 804. In some terms, application 820 may be simply referred to as "app". Furthermore, application 820 can be downloaded to device 800 through one or more online application stores or app markets. However, applications can also be installed on device 800 in other ways, such as through a web browser or a physical interface on device 800 (e.g., a USB port).
[0143] In one specific embodiment, the cloud-based data processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for use in the cloud-based data processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: Based on the data request submitted by the client, a trusted data task is created and task information is returned, and the cloud task corresponding to the trusted data task is initialized. The client schedules the corresponding cloud instance for the determined cloud virtual mode and sends the execution script of the cloud task to the cloud instance; Initialize the virtual runtime environment of the cloud instance, and simulate the user's data collection operation on the target system by running the execution script; The system transmits the collected simulation data of the execution script back to the client through the established data channel, and transmits task status messages based on the task execution status.
[0144] This specification provides an embodiment of a computer-readable storage medium as follows: In accordance with the cloud service-based data processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.
[0145] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: Based on user authorization, the user submits a data request to the cloud server and receives task information for the trusted data task returned by the cloud server. Based on the cloud configuration parameters and local parameters obtained by calling the cloud interface, determine the cloud virtual mode used to perform trusted data processing; Invoke the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, and register to receive message callbacks for task execution status; The collected simulation data is collected and rendered based on the data channel, and the page response action corresponding to the returned task status message is executed.
[0146] It should be noted that the embodiments of a computer-readable storage medium described in this specification and the embodiments of a cloud service-based data processing method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.
[0147] Another embodiment of a computer-readable storage medium provided in this specification is as follows: Corresponding to the other cloud service-based data processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.
[0148] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: Based on the data request submitted by the client, a trusted data task is created and task information is returned, and the cloud task corresponding to the trusted data task is initialized. The client schedules the corresponding cloud instance for the determined cloud virtual mode and sends the execution script of the cloud task to the cloud instance; Initialize the virtual runtime environment of the cloud instance, and simulate the user's data collection operation on the target system by running the execution script; The system transmits the collected simulation data of the execution script back to the client through the established data channel, and transmits task status messages based on the task execution status.
[0149] It should be noted that the embodiments of another computer-readable storage medium described in this specification and the embodiments of a cloud service-based data processing method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.
[0150] This specification provides an example of a computer program product as follows: Corresponding to the cloud service-based data processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide a computer program product.
[0151] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps: Based on user authorization, the user submits a data request to the cloud server and receives task information for the trusted data task returned by the cloud server. Based on the cloud configuration parameters and local parameters obtained by calling the cloud interface, determine the cloud virtual mode used to perform trusted data processing; Invoke the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, and register to receive message callbacks for task execution status; The collected simulation data is collected and rendered based on the data channel, and the page response action corresponding to the returned task status message is executed.
[0152] It should be noted that the embodiments of a computer program product described in this specification and the embodiments of a cloud service-based data processing method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.
[0153] Another example of a computer program product provided in this specification is as follows: Corresponding to the other cloud service-based data processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide another computer program product.
[0154] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps: Based on the data request submitted by the client, a trusted data task is created and task information is returned, and the cloud task corresponding to the trusted data task is initialized. The client schedules the corresponding cloud instance for the determined cloud virtual mode and sends the execution script of the cloud task to the cloud instance; Initialize the virtual runtime environment of the cloud instance, and simulate the user's data collection operation on the target system by running the execution script; The system transmits the collected simulation data of the execution script back to the client through the established data channel, and transmits task status messages based on the task execution status.
[0155] It should be noted that the embodiments of another computer program product described in this specification and the embodiments of a cloud service-based data processing method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.
[0156] The various embodiments in this specification are described in a progressive manner. For the same or similar parts between the various embodiments, please refer to each other. Each embodiment focuses on describing the differences from other embodiments. For example, the device embodiment, equipment embodiment, and computer-readable storage medium embodiment are all similar to the method embodiment, so the description is relatively simple. For reading the relevant content of the device embodiment, equipment embodiment, and computer-readable storage medium embodiment, please refer to the description of the method embodiment.
[0157] While one or more embodiments of this specification provide method steps as described in the embodiments or flowcharts, it is understood that the order of steps listed in the embodiments or flowcharts is merely one possible execution order among many steps, and does not represent the only execution order. Therefore, when the claims involve method steps, any changes or adjustments to the order of such steps, or the parallelism between steps, are also within the scope of protection of the claims. This specification uses specific terms to describe embodiments of this specification. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "an embodiment," "one embodiment," or "an alternative embodiment" mentioned twice or more in different locations in this specification do not necessarily refer to the same embodiment. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.
[0158] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0159] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.
[0160] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.
[0161] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.
[0162] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.
[0163] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0164] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will 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 apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0165] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing 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, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0166] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0167] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0168] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0169] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer-readable storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage, or other magnetic storage devices, which can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient media, such as modulated data signals and carrier waves.
[0170] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus 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 apparatus. Without further limitation, an element defined by the phrase "comprising at least one…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0171] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.
[0172] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.
Claims
1. A cloud service-based data processing method, applied to a client, the method comprising: Based on user authorization, the user submits a data request to the cloud server and receives task information for the trusted data task returned by the cloud server. Based on the cloud configuration parameters and local parameters obtained by calling the cloud interface, determine the cloud virtual mode used to perform trusted data processing; Invoke the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, and register to receive message callbacks for task execution status; The collected simulation data is collected and rendered based on the data channel, and the page response action corresponding to the returned task status message is executed.
2. The data processing method based on cloud services according to claim 1, wherein determining the cloud virtual mode for performing trusted data processing based on cloud configuration parameters and local parameters obtained by calling the cloud interface includes: Read the grayscale policy parameters in the grayscale configuration from the mode label in the mode configuration list issued by the cloud server, and read the connection timeout records stored locally. The system checks whether the mode label, the grayscale strategy parameters, and the connection timeout record meet preset conditions. If yes, the cloud virtual mode is determined to be a cloud phone mode; otherwise, the cloud virtual mode is determined to be a cloud desktop mode.
3. The data processing method based on cloud services according to claim 1, further comprising, before the step of submitting a data request to the cloud service based on user authorization, the method includes: Based on the user's application identifier, the task query interface is called to query whether the user has a trusted data task in progress. If so, the corresponding task recovery strategy is executed according to the task status of the trusted data task in progress. If it does not exist, proceed to the next step; The execution of the corresponding task recovery strategy includes: if the task status is in the creation or running state, polling the task status based on the task identifier and redirecting to the corresponding cloud instance page; if the task status is in the completion state, redirecting to the task result page.
4. The data processing method based on cloud services according to claim 2, wherein the step of calling the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance includes: Call the connection interface of the cloud service component corresponding to the cloud desktop mode to establish a remote connection with the cloud desktop virtual machine; Alternatively, the session creation interface of the cloud service component corresponding to the cloud phone mode can be called to create a session and start the connection, and the cloud phone instance screen can be rendered through the embedded frame of the page.
5. The data processing method based on cloud services according to claim 2, wherein the registration for receiving message callbacks of task execution status includes: Register the connection success callback, connection interruption callback, and runtime message callback in the cloud desktop mode; The runtime message callback is used to receive login events, password input events, and general pop-up events returned by the execution script of the cloud task; Alternatively, register the data channel listener and connection interruption listener in the cloud phone mode, and start the timeout detection timer to check the connection status.
6. The data processing method based on cloud services according to claim 1, after the operation of calling the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance is executed, it further includes: The connection status and task execution status of the cloud instance in the cloud phone mode are detected, and it is also detected whether the virtual mode degradation condition is triggered. If so, write the connection timeout record to local storage and call the task shutdown interface to handle the task shutdown in cloud phone mode; Call the task creation interface to create a trusted data task in cloud desktop mode, and then redirect to the cloud desktop page in the cloud desktop mode.
7. The data processing method based on cloud services according to claim 6, wherein the virtual mode degradation condition includes at least one of the following: the connection status is connection timeout or connection interruption, and the task execution status is execution error; If the connection status is connection timeout, a timeout flag is generated and sent back to the front page through a page lifecycle event. After reading the timeout flag, the front page determines the cloud virtual mode as cloud desktop mode.
8. The data processing method based on cloud services according to claim 1, wherein the page response action corresponding to the task status message to be returned includes: Based on the task status of the cloud task corresponding to the trusted data task carried in the task status message, update the task status of the trusted data task, or execute the message response operation corresponding to the task status message. The trusted data task and the cloud task are synchronized and coordinated using a two-level state machine.
9. The data processing method based on cloud services according to claim 1 further includes: If a user-submitted exit action is detected, the exit action is intercepted, and an interface is called to perform pre-exit detection. If the detection passes, read the user's collection reminder time record, and determine whether the collection reminder condition is triggered based on the time record. If triggered, display a reminder pop-up window for the collection exit operation.
10. The data processing method based on cloud services according to claim 9, wherein the reminder pop-up window for exiting the data collection operation includes: Based on the page dimension of the client page that submitted the data collection exit operation, generate the pop-up theme text corresponding to the page dimension, and display the pop-up theme text on the client page through a pop-up window; The time records for client-side pages of different page dimensions are stored independently.
11. The data processing method based on cloud services according to claim 1, after the steps of performing collection simulation rendering and display based on the collection simulation data returned by the data channel, and executing the page response action corresponding to the returned task status message, further includes: In response to a page unload event or a data collection end event, perform resource cleanup corresponding to the cloud virtual mode; The resource cleanup corresponding to the cloud virtual mode includes: if it is a cloud desktop mode, disconnecting the remote connection with the cloud desktop virtual machine and deleting the message callback; if it is a cloud phone mode, destroying the timeout timer and deleting the cloud phone session instance.
12. A data processing method based on cloud services, applied to a cloud server, the method comprising: Based on the data request submitted by the client, a trusted data task is created and task information is returned, and the cloud task corresponding to the trusted data task is initialized. The client schedules the corresponding cloud instance for the determined cloud virtual mode and sends the execution script of the cloud task to the cloud instance; Initialize the virtual runtime environment of the cloud instance, and simulate the user's data collection operation on the target system by running the execution script; The system transmits the collected simulation data of the execution script back to the client through the established data channel, and transmits task status messages based on the task execution status.
13. The data processing method based on cloud services according to claim 12, wherein scheduling the corresponding cloud instance according to the client for the determined cloud virtual mode includes: In response to the client's call to the task shutdown interface, the cloud instance corresponding to the cloud phone mode is destroyed, the cloud instance corresponding to the cloud desktop mode is scheduled and the execution script is sent to downgrade from the cloud phone mode to the cloud desktop mode.
14. The cloud service-based data processing method according to claim 12, wherein the trusted data task and the cloud task are synchronized and coordinated using a two-level state machine; in, The task status of the cloud task includes: initialization status, running status, completion status, failure status, and closed status; the running status includes script loading sub-status, account login sub-status, and data query sub-status; The task status of the trusted data task includes: creation status, running status, completion status, failure status, and shutdown status.
15. The data processing method based on cloud services according to claim 12, further comprising: Based on the data collection results of the executed script, the user's trusted data is generated, and the user's credit limit is updated based on the trusted data.
16. A cloud-based data processing device, running on a client, the device comprising: The data request submission module is configured to submit data requests to the cloud server based on user authorization and receive task information of trusted data tasks returned by the cloud server. The virtual mode determination module is configured to determine the cloud virtual mode used to perform trusted data processing based on cloud configuration parameters and local parameters obtained by calling the cloud interface; The data channel establishment module is configured to call the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, and register to receive message callbacks for task execution status; The rendering response module is configured to perform simulated rendering and display of the collected data based on the simulated data returned by the data channel, and to execute the page response actions corresponding to the returned task status messages.
17. A cloud-based data processing device, operating on a cloud server, the device comprising: The task creation module is configured to create a trusted data task based on a data request submitted by the client and return task information, and initialize the cloud task corresponding to the trusted data task. The cloud instance processing module is configured to schedule the corresponding cloud instance according to the client for the determined cloud virtual mode, and send the execution script of the cloud task to the cloud instance; The execution script module is configured to initialize the virtual runtime environment of the cloud instance and simulate the user's data collection operation on the target system by running the execution script; The data feedback module is configured to send back the collected simulation data of the execution script to the client through the established data channel, and to send back task status messages based on the task execution status.
18. A cloud-based data processing device, comprising: The processor, and the memory configured to store computer-executable instructions; When the computer-executable instructions are executed, they cause the processor to: Based on user authorization, the user submits a data request to the cloud server and receives task information for the trusted data task returned by the cloud server. Based on the cloud configuration parameters and local parameters obtained by calling the cloud interface, determine the cloud virtual mode used to perform trusted data processing; Invoke the cloud service component corresponding to the cloud virtual mode to establish a data channel with the cloud instance, and register to receive message callbacks for task execution status; The collected simulation data is collected and rendered based on the data channel, and the page response action corresponding to the returned task status message is executed.
19. A cloud-based data processing device, comprising: The processor, and the memory configured to store computer-executable instructions; When the computer-executable instructions are executed, they cause the processor to: Based on the data request submitted by the client, a trusted data task is created and task information is returned, and the cloud task corresponding to the trusted data task is initialized. The client schedules the corresponding cloud instance for the determined cloud virtual mode and sends the execution script of the cloud task to the cloud instance; Initialize the virtual runtime environment of the cloud instance, and simulate the user's data collection operation on the target system by running the execution script; The system transmits the collected simulation data of the execution script back to the client through the established data channel, and transmits task status messages based on the task execution status.
20. A computer-readable storage medium for storing computer-executable instructions that, when executed, implement the steps of the method of claim 1 or 12.
