Communication method and device, electronic equipment, storage medium and program product

Abstract

The invention provides a communication method and apparatus, an electronic device, a storage medium and a program product. The method comprises the steps of configuring an access rule of a target application in a cloud device; when the user equipment accesses the target application, intercepting a page jump request and / or button click jump; and when at least one of a target page corresponding to the page jump request and a target identifier corresponding to the button is matched with the access rule, jumping to a rendering page of a target application corresponding to the cloud equipment for access. Compared with an existing mode that the user is forced to upgrade the local application or use is limited due to version incompatibility, the method and the device have the advantage that the user can access the latest function of the target application through the cloud rendering page under the condition that the user is not forced to upgrade the local application. In conclusion, according to the technical scheme provided by the invention, the user experience and satisfaction can be improved to the greatest extent while continuous iterative updating of the application is guaranteed, and powerful support is provided for long-term development of the application.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, apparatus, electronic device, storage medium, and program product. Background Technology

[0002] Currently, frequent application updates can cause user dissatisfaction, leading many users to remain on a certain version without upgrading. If a forced upgrade occurs, users are forced to either upgrade to the new version or choose not to, resulting in a forced exit. This negatively impacts user experience and application affinity, and may also cause some users to churn due to resistance to upgrades. It fails to balance application feature updates with user experience, making it difficult to achieve a balance between application iteration and user retention. Summary of the Invention

[0003] This disclosure provides a communication method, apparatus, electronic device, storage medium, and program product to address, to some extent, the difficulty in balancing application iteration and user retention.

[0004] According to one aspect of this disclosure, a communication method is provided, the method comprising: configuring access rules for a target application on a cloud device; when a user device accesses the target application, intercepting page redirection requests and / or button click redirections; when at least one of the target page corresponding to the page redirection request and the target identifier corresponding to the button matches the access rules, redirecting to the rendered page of the target application on the cloud device for access. Furthermore, according to one aspect of the method disclosed herein, configuring access rules for a target application on a cloud device includes: receiving the target application version number, target page, target identifier, and rendering page configured by a third-party developer; establishing a mapping relationship between the target application version number, target page, and / or target identifier and rendering page to form access rule entries; adding effective conditions to the access rule entries to obtain access rules; the effective conditions include at least one of the following: time range and user permissions.

[0005] Furthermore, according to one aspect of the method disclosed herein, when a user device accesses a target application, intercepting page jump requests and / or button click jumps includes: detecting the access environment; and when the access environment is a real environment, intercepting system page jumps and / or button click views.

[0006] Furthermore, according to one aspect of the method disclosed herein, when the target page corresponding to the page jump request and / or the target identifier corresponding to the button match the access rules respectively, the user device is redirected to the rendering page of the target application corresponding to the cloud device for access, including: determining the matching degree between the target page and / or the target identifier and the access rules respectively; when the matching degree meets the threshold, logging into the target application of the user device and the cloud device; establishing a transmission channel between the user device and the cloud device through the end-cloud collaboration module, and redirecting to the rendering page.

[0007] Furthermore, according to one aspect of the method of this disclosure, when the matching degree meets a threshold, logging into the target application of the user device and the cloud device includes: obtaining a first token of the user device and a single sign-on credential of the cloud device; obtaining a second token of the cloud device based on the credentials; and logging into the target application of the cloud device based on the first token and the second token.

[0008] Furthermore, according to one aspect of the method disclosed herein, a transmission channel between a user device and a cloud device is established through an end-to-cloud collaboration module to jump to a rendering page, including: transmitting the user device's parameters and a first token to the cloud device through the end-to-cloud collaboration module; performing second token authentication on the cloud device when the user device starts up; and when authentication is successful, rendering and sending the target application's audio, video, and / or business data to the user device through the cloud device.

[0009] Furthermore, according to one aspect of the method disclosed, the method further includes: when the target application within the cloud device is closed, sending a shutdown command to the user device through the end-to-cloud collaboration module, the shutdown command being used to instruct the closure of the rendered page on the user device.

[0010] Furthermore, according to one aspect of the method disclosed herein, the method further includes: the user equipment and the cloud device communicating synchronously via a data synchronization module; when the user equipment logs in for the first time, the user equipment's local data is fully or incrementally synchronized to the cloud device via the data synchronization module; when the cloud device logs in for the first time, the cloud device's data is fully or incrementally synchronized to the user equipment via the data synchronization module; when the user equipment or the cloud device detects a data update, the incremental data is determined by comparing the user equipment's local data and the cloud device's data, and the incremental data is synchronized via the data synchronization module. Furthermore, according to one aspect of the method disclosed herein, the method further includes: when a cloud device requests to obtain hardware data, sending a retrieval instruction carrying a hardware type identifier to a user device; obtaining the collected hardware data from the user device based on the retrieval instruction; and sending the hardware data to the cloud device.

[0011] According to another aspect of this disclosure, a communication apparatus is provided, comprising: a configuration unit for configuring access rules for a target application on a cloud device; an interception unit for intercepting page jump requests and / or button click jumps when a user device accesses the target application; and a jump unit for jumping to the rendered page of the target application on the cloud device for access when at least one of the target page corresponding to the page jump request and the target identifier corresponding to the button matches the access rules.

[0012] According to another aspect of this disclosure, an electronic device is provided, comprising: a memory for storing computer-readable instructions; and a processor for executing the computer-readable instructions, causing the electronic device to perform the method as described in any embodiment of one aspect.

[0013] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided for storing computer-readable instructions that, when executed by a processor, cause the processor to perform the method as described in any embodiment of one aspect.

[0014] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the method as described in any embodiment of one aspect.

[0015] This disclosure provides a communication method, apparatus, electronic device, storage medium, and program product. This disclosure configures access rules for a target application on a cloud device; when a user device accesses the target application, it intercepts page redirection requests and / or button clicks; when at least one of the target page corresponding to the page redirection request and the target identifier corresponding to the button matches the access rules, it redirects the user to the rendered page of the target application on the cloud device for access. Compared to existing models that force users to upgrade local applications or restrict usage due to version incompatibility, this disclosure allows users to access the latest features of a target application through a cloud-rendered page without forcing them to upgrade their local applications. This satisfies users' habits of using older versions while allowing them to experience new features on demand, avoiding user experience degradation and user churn caused by forced upgrades, thus achieving a balance between application feature iteration and user retention. In summary, the technical solution provided by this disclosure can maximize user experience and satisfaction while ensuring continuous application iteration and updates, providing strong support for the long-term development of applications.

[0016] It should be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further illustration of the claimed technology. Attached Figure Description

[0017] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of the embodiments thereof in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0018] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure; Figure 2 A flowchart illustrating a communication method provided in an embodiment of this disclosure; Figure 3 is a schematic diagram illustrating one configuration of access rules provided in this disclosure; Figure 4 is an interactive flowchart of a jump method provided in an embodiment of this disclosure; Figure 5 is an interactive flowchart of logging into a target application on a cloud device according to an embodiment of this disclosure; Figure 6 is an interactive flowchart of data synchronization from a physical machine to a cloud machine provided in an embodiment of this disclosure; Figure 7 is an interactive flowchart of data synchronization from cloud machine to physical machine provided in an embodiment of this disclosure; Figure 8 A schematic flowchart illustrating a hardware simulation relationship provided in this embodiment of the disclosure; Figure 9 A structural block diagram of a communication device provided in an embodiment of this disclosure; Figure 10 A hardware block diagram of an electronic device provided in an embodiment of this disclosure; Figure 11 This is a schematic diagram of a computer-readable storage medium provided in an embodiment of this disclosure. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this disclosure more apparent, exemplary embodiments according to this disclosure will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this disclosure, and not all embodiments of this disclosure. It should be understood that this disclosure is not limited to the exemplary embodiments described herein.

[0020] Currently, frequent application updates can cause user dissatisfaction, leading many users to remain on a certain version without upgrading. If a forced upgrade occurs, users are forced to either upgrade to the new version or choose not to, resulting in a forced exit. This negatively impacts user experience and application affinity, and may also cause some users to churn due to resistance to upgrades. It fails to balance application feature updates with user experience, making it difficult to achieve a balance between application iteration and user retention.

[0021] Therefore, to address the aforementioned issues, this disclosure provides a communication method that allows users to access the latest features of a target application through a cloud-rendered page without forcing them to upgrade their local application. This satisfies users' habits of using older versions while allowing them to experience new features on demand, avoiding the user experience degradation and user churn caused by forced upgrades, thus achieving a balance between application feature iteration and user retention. First, referring to... Figure 1 Overview of application scenarios according to embodiments of this disclosure.

[0022] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure. Figure 1 As shown, the communication system includes at least: physical devices and cloud devices.

[0023] The physical device refers to the user equipment disclosed herein. The cloud device refers to the cloud equipment disclosed herein.

[0024] A physical device can be understood as a mobile device that a user actually holds, such as a smartphone or tablet. It has built-in real hardware components (such as a processor, camera, and sensors), runs a native operating system and various applications, and is the terminal that the user directly operates and interacts with. Users install and use applications and store personal data on physical devices, and its hardware resources and software environment are all local entities.

[0025] A cloud device can be understood as a virtual mobile phone running the Android operating system, serving as a platform for cloud applications. Deployed in a remote server cluster, it uses virtualization technology to simulate a complete mobile phone operating environment, possessing independent system kernels, memory, storage, and other virtual resources, and can run applications.

[0026] Next, from Figure 1 As can be seen from this, the communication system also includes: a cloud application platform, a third-party application platform, and cloud storage.

[0027] The cloud application platform can be understood as the core service platform for managing the entire lifecycle of cloud applications and coordinating cloud-end interactions. As a bridge between physical and cloud devices, it handles user login, issues access credentials, configures redirection rules, and manages application uploads and installations. It also undertakes responsibilities such as monitoring cloud application runtime status, resource scheduling, and version control, ensuring that cloud applications can provide stable and efficient services to users.

[0028] A third-party application platform can be understood as the official service hub for third-party applications. It not only handles user login verification and business logic processing for its own applications, but also, through integration with cloud application platforms, enables the adaptation and management of third-party applications in the cloud environment. This includes providing login tickets for cloud applications, synchronizing user information, and ensuring data interoperability between end-user and cloud applications. It serves as a crucial hub for identity authentication and business support, connecting users, physical applications, and cloud applications.

[0029] Cloud storage can be understood as cloud-based storage space that provides distributed data storage and access services. It relies on server clusters to provide secure and reliable file storage capabilities for cloud applications and physical device applications, supporting data uploading, downloading, synchronization, and version management. This ensures that various types of data (such as documents and media files) generated during the interaction between the two applications can be shared in real time and updated consistently, providing fundamental support for data interoperability between the cloud and the application.

[0030] More specifically, in a real device, this communication system also includes: a third-party application (APP), a cloud application software development kit (SDK), a click event module, a startup interface module, and a system hardware module. The cloud application SDK further includes: a jump processing module, a cloud application rendering module, a data synchronization module, and an end-to-end cloud collaboration module.

[0031] Among them, third-party applications (APPs) can be understood as applications developed by third-party developers, installed and run on the user's real device, providing the user with specific business functions (such as social networking, shopping, office work, etc.), while integrating cloud application SDKs to achieve collaborative interaction with corresponding applications in the cloud machine.

[0032] A cloud application SDK can be understood as a software development kit embedded in a third-party application (APP). It provides technical support for third-party applications to access cloud application platforms and realize end-to-end cloud collaboration functions. It encapsulates core capabilities such as jumping to cloud applications, data synchronization, and audio and video streaming, simplifying the integration process for developers.

[0033] The click event module can be understood as a module that listens for and processes user interaction behavior when clicking buttons in a third-party application (APP). It can capture the user's click action and trigger the corresponding callback method, providing an event source for subsequent determination of whether to redirect to the cloud application rendering page.

[0034] The launch interface module can be understood as a module that manages the launch and navigation of pages in third-party applications (APP). It encapsulates the core methods of page navigation (such as start Activity), which are the methods used in the system for navigation between system activity pages.

[0035] The system hardware module can be understood as a collection of drivers and functional interfaces for various physical hardware in the actual device, including hardware devices such as GPS, sensors, Bluetooth, and NFC. It can respond to the calls of the application and provide real hardware data (such as location information and sensor data) and functional support.

[0036] The redirection module can be understood as the module in a third-party application (APP) responsible for managing page redirection logic and deciding whether to redirect to a cloud application rendering page. Its main responsibility is to obtain the redirection configuration data for cloud application rendering pages configured by the third-party developer from the cloud application platform. When a user wants to redirect to these configured pages on a real device, they will be directly redirected to the cloud application rendering page, and these configured pages will be opened within the cloud application.

[0037] The cloud application rendering module can be understood as the module responsible for displaying the application screen in the cloud machine and enabling interaction on the real device.

[0038] The data synchronization module can be understood as the module that ensures data consistency between the physical device and the cloud device for third-party applications. This module can include a file synchronization module and a file monitoring module. The file synchronization module is responsible for uploading, downloading, and deleting full or incremental data based on the data version number to ensure data synchronization between the two ends; the file monitoring module monitors the addition, modification, or deletion of local files in real time and triggers the synchronization mechanism to update the data in the cloud or locally.

[0039] The edge-cloud collaboration module – the edge side can be understood as the module in the physical device responsible for establishing a communication connection with the cloud machine and transmitting data. Specifically, it's the SDK embedded in the cloud application SDK, responsible for communicating with the cloud-side edge-cloud collaboration module, building a communication bridge between third-party applications and the cloud machine. Its main functions are sending command streams and receiving audio and video streams.

[0040] Within the cloud machine, the communication system also includes a third-party app and an edge-cloud collaboration module (cloud side). The third-party app further includes a data synchronization module, a hardware simulation module, and a redirection processing module.

[0041] For a detailed explanation of third-party apps and data synchronization modules, please refer to the above text; further details will not be provided here.

[0042] The edge-cloud collaboration module – the cloud side can be understood as the module in the cloud machine that establishes a communication link with the physical device and handles data interaction. Specifically, it's responsible for communicating with the edge-cloud collaboration module on the cloud side, transmitting data between third-party applications and the cloud machine, mainly including heartbeat detection, receiving command streams, and sending audio and video streams.

[0043] The hardware simulation module can be understood as a module in a cloud machine that simulates the hardware functions of a real machine and enables cloud applications to access the hardware resources of the real machine. It generates corresponding instructions from the cloud application's hardware access requests and sends them to the real machine. After receiving the hardware data returned by the real machine, it parses it and sends it back to the cloud application, enabling the cloud application to use the hardware functions of the real machine (such as GPS, sensors, etc.) normally in the virtual environment.

[0044] This disclosure provides a communication method. Please refer to... Figure 2 , Figure 2 This is a flowchart illustrating a communication method provided in an embodiment of this disclosure. Figure 2 As shown, the method includes: In step S201, the access rules for the target application on the cloud device are configured; In step S202, when the user device accesses the target application, page redirection requests and / or button click redirection are intercepted; In step S203, when at least one of the target page corresponding to the page jump request and the target identifier corresponding to the button matches the access rule, the user is redirected to the rendered page of the target application corresponding to the cloud device for access. In this disclosure, access rules can be understood as a pre-defined set of conditions used to determine whether a user device operation needs to be redirected to the target application on the cloud device. These rules typically include information such as the fully qualified name of the target page to be redirected to and the unique identifier of the button. They are configured by the developer on the cloud application platform and distributed to the user device.

[0045] In this disclosure, a page jump request can be understood as a page switching instruction initiated by the target application on the user's device. It is usually triggered by methods such as start Activity and includes information such as the class name of the target page and the business parameters passed, and is used to jump from the current page to another page within the application.

[0046] In this disclosure, button click navigation can be understood as the navigation behavior triggered when a user clicks a button in the application interface. The button uses a preset unique identifier, and clicking it will trigger a callback (on Click) method.

[0047] Specifically, when a user interacts with a target application on their device, the system intercepts page redirection requests and button click events in real time or periodically, comparing the target page information or button identifier with the access rules. If a match is found (e.g., the target page is in the rule list and meets the version requirements), the local redirection is not executed. Instead, the cloud application rendering page is launched, connecting to the cloud device through an end-to-cloud collaboration mechanism. The corresponding page of the target application on the cloud device is displayed in the rendering page, achieving the effect of using the latest cloud features without upgrading the local application.

[0048] The following will explain in detail how to configure access rules, including the following methods: Receive the target application version number, target page, target identifier, and rendering page configured by the third-party developer; Establish a mapping relationship between the target application version number, target page and / or target identifier, and rendered page to form access rule entries; Add effective conditions to access rule entries to obtain access rules; effective conditions include at least one of the following: time range, user permissions.

[0049] In this disclosure, the target application version number can be understood as a specific version identifier of the third-party application running on the cloud device, used to distinguish applications with different functional versions and ensure that the user is redirected to the matching version of the cloud application. The target page can be understood as a specific page in the third-party application that needs to be accessed through cloud application rendering, typically uniquely identified by its fully qualified class name. The target identifier can be understood as a unique marker in the application interface for interactive elements such as buttons that can trigger a redirect to the cloud application, used to accurately identify specific click events. The rendered page can be understood as a special page on the user's device used to display the target application's screen on the cloud device; it serves as the visual carrier for end-to-end cloud interaction.

[0050] In this disclosure, an access rule entry can be understood as a basic rule unit formed by associating and binding the target application version number, the target page to be redirected, and / or the target identifier with the corresponding cloud application rendering page. It is the core element constituting the access rule.

[0051] In this disclosure, the effective conditions can be understood as constraints that control whether access rule entries are enabled. The time range can be understood as the specific period during which the rule is effective. For example, the rule is effective from October 1, 2024 to December 31, 2024. User permissions can be understood as the scope of application of the rule based on user roles or permission levels. For example, only VIP users can trigger the corresponding cloud application redirection.

[0052] Specifically, third-party developers configure the target application version number, the target page to be redirected to (fully qualified class name), the target identifier (tag value) of the button, and the corresponding cloud application rendering page through the cloud application platform. The system associates this information to form access rule entries, and then adds time ranges (such as during a specific event) and user permissions (such as specific user groups) as effective conditions to the entries, ultimately forming a complete access rule. When a user's device operation triggers a page redirect or button click, the system will determine whether the effective conditions and matching relationships are met based on the access rules, and then decide whether to redirect to the cloud application rendering page.

[0053] For example, Figure 3 is a schematic diagram illustrating a configured access rule provided in this disclosure. As shown in Figure 3, the access rule includes an ID (primary key, used to uniquely identify a rule), the original redirect page (corresponding to the target page, i.e., the local page triggered by the user's redirection), a redirect tag (corresponding to the target identifier, identifying the button tag that needs to be redirected to the cloud application rendering), the target redirect page (corresponding to the rendering page, the page to be rendered and displayed in the cloud application), the version number (corresponding to the target application version number, the application version that limits the rule's effect), and the rule (corresponding to the effective conditions, such as time, permissions, and other redirection judgment criteria). These fields together define the complete logic of "which local pages / buttons, when clicked, redirect to which page of the cloud application for rendering".

[0054] The following will explain in detail how this disclosure intercepts redirects, including the following methods: Detect the access environment; When the access environment is a real environment, intercept system page redirects and / or button click views.

[0055] In this disclosure, the access environment can be understood as the runtime environment in which the user is currently operating the application. It is mainly used to distinguish whether the application is running directly in the local environment of the user's device (real device) or accessed through the environment of rendering the page through a cloud device.

[0056] In this disclosure, the real environment can be understood as the application runtime environment on the user's device (real device), that is, the scenario where the application is directly installed and runs on the user's physical device and interacts with the hardware resources and system environment of the real device.

[0057] In this disclosure, system page navigation can be understood as the switching behavior between pages (Activities) triggered by system methods (such as start Activity()) during application runtime, including instructions and related parameters for navigating from the current page to the target page. Button click view can be understood as the view of user-interactive button controls in the application interface and their triggered click events, which is associated with specific navigation logic (such as navigating to a certain page after clicking).

[0058] Specifically, the system can first detect the user's current application access environment. When it determines that the user is in a real environment (i.e., the user is directly using a local application on a real device), it will intercept system page navigation methods (such as start Activity()) and button click events using techniques such as Aspect-Oriented Programming (AOP). After interception, the system compares the obtained target page information, button identifiers, etc., with preset access rules to determine whether it is necessary to navigate to the rendered page of the cloud device, thereby controlling and guiding local navigation behavior.

[0059] The following will explain in detail how to perform the jump and display, including the following methods: Determine the degree of match between the target page and / or the target identifier and the access rule; When the matching degree meets the threshold, the target application on the user device and cloud device is logged in. The end-to-cloud collaboration module establishes a transmission channel between user devices and cloud devices, and then redirects to the rendering page.

[0060] In this disclosure, the matching degree can be understood as the degree of consistency between the fully qualified class name of the target page, the target identifier of the button, and the corresponding information preset in the access rules, used to determine whether the conditions for redirection to the cloud application rendering page are met. Typically, a perfect match (i.e., 100% match) is used as the threshold to ensure that only operations that conform to the preset rules will trigger the redirection. No specific restrictions are imposed.

[0061] In this disclosure, the end-to-cloud collaboration module can be understood as a set of functional modules deployed on both ends of the user equipment (end-side) and cloud equipment (cloud-side), responsible for establishing and maintaining the communication connection between the two. Through mechanisms such as encrypted transmission, command interaction, and audio and video stream processing, it enables data interoperability and collaborative work between the user equipment and the cloud equipment.

[0062] Specifically, the system can compare the intercepted target page information and / or button target identifiers with the configuration in the access rules to calculate the matching degree. When the matching degree reaches a preset threshold (such as a perfect match), the system first completes the login of the target application on the user device's local device and the corresponding target application on the cloud device (identity synchronization is achieved through a unified authentication center); then, a secure transmission channel (including data command channel and audio / video channel) is established between the user device and the cloud device through the end-to-cloud collaboration module, and finally the user device's operation interface is redirected to the rendering page, displaying the corresponding page content of the target application on the cloud device in real time, thus realizing the end-to-cloud collaborative access experience.

[0063] For example, Figure 4 is an interactive flowchart of a jump method provided in an embodiment of this disclosure. As can be seen from Figure 4, this process involves multi-module collaborative interaction between the user device (real device) and the cloud device (cloud machine), and the specific process is as follows: 1. User action trigger: When a user clicks a button or triggers a page jump (such as calling the startActivity() method) in a third-party application on a real device, a jump request is generated.

[0064] 2. AOP Aspect Interception: The cloud application SDK on the real device intercepts redirection requests (page redirection or button click) through the AOP module and extracts the fully qualified class name of the target page or the target identifier (tag value) of the button.

[0065] 3. Rule matching and verification: The redirection processing module matches the extracted information with the access rules obtained from the cloud application platform, and verifies whether conditions such as version number, effective time, and user permissions are met.

[0066] 4. Login and Authentication: If the match is successful, the real device establishes a connection with the cloud device through the End-to-Cloud Collaboration Module - End Side and the Cloud Device's End-to-Cloud Collaboration Module - Cloud Side to complete the synchronization of user identity (unified login of the target application between the real device and the cloud device is achieved based on the token).

[0067] 5. Parameter transmission: The real device transmits the target page's full name, business parameters, token, and other information to the cloud server through the end-to-cloud collaboration module. The third-party APP on the cloud server receives and parses the parameters.

[0068] 6. Cloud machine page redirection: The cloud machine's redirection processing module starts the corresponding target page according to the parameters, and records the full name of the page as the root page. The audio and video streams rendered by the page are sent to the real machine through the end-cloud collaboration module - cloud side.

[0069] 7. Real Device Rendering and Display: The cloud application rendering module of the real device receives audio and video streams and displays the content of the target page of the cloud device in real time on the rendering page. Users can operate the cloud device page on the real device.

[0070] 8. Return and Close Logic: When a user triggers a return operation after multiple navigations on the cloud server page, if the closed page is the recorded root page, the cloud server notifies the real device through the end-cloud collaboration module, and the real device closes the currently rendered page and returns to the native application page.

[0071] The entire process utilizes the end-to-cloud collaboration module to achieve encrypted data transmission, audio and video streaming, and command interaction, ensuring the security and smoothness of the jump process and enabling users to access the latest cloud features without upgrading local applications.

[0072] The following will explain in detail how to log in to the target application on the cloud device, including the following methods: Obtain the user device's first token and credentials for single sign-on to cloud devices; Based on credentials, obtain the second token for the cloud device; Log in to the target application on the cloud device based on the first token and the second token.

[0073] In this disclosure, the first token can be understood as an authentication token issued by the application server or authentication authority after a user successfully logs in to the target application on the user's device (real device). It identifies the user's login status and permissions on the real device and serves as the user's identity credential for operations within the local application. The second token can be understood as a token generated by the cloud application platform or corresponding authentication service after the user completes authentication in the target application on the cloud device (cloud machine) based on single sign-on credentials. It identifies the user's login status in the target application on the cloud machine and serves as the user's identity credential for accessing cloud application resources.

[0074] In this disclosure, the credentials for single sign-on to cloud devices can be understood as authentication information that enables identity exchange between user devices and cloud devices. They are usually generated by the user device or obtained from the authentication center and include user identity identifiers, encrypted information, etc. They can be used to quickly complete user authentication on the cloud device without requiring the user to repeatedly enter their account and password.

[0075] Specifically, after a user successfully logs in to the target application on the real device, the system obtains the first token (local login credential) returned by the application. At the same time, it generates a single sign-on credential for the cloud device (such as an encrypted string containing the user's unique identifier and validity period) through a unified authentication mechanism. The real device transmits this credential to the cloud device through the end-to-cloud collaboration module. The cloud device initiates a verification request to the authentication center based on the credential, and obtains the second token on the cloud device after successful verification. Finally, the system uses the first token (used to verify the consistency of local and cloud identities) and the second token (used for cloud application permission verification) together as login credentials to complete the login to the target application on the cloud device, achieving identity synchronization and a seamless login experience between the real device and the cloud device.

[0076] For example, Figure 5 is an interactive flowchart of logging into a target application on a cloud device according to an embodiment of this disclosure. As can be seen from Figure 5, this process involves the collaboration of the physical device, the cloud device, the authentication center, and related service modules. The specific process is as follows: 1. User-triggered login association: When a user's operation in a third-party application on a real device triggers a cloud application redirection request, the cloud application SDK on the real device first detects that the user is already logged in to the local application (holding the first token) and initiates the end-to-cloud login collaboration process.

[0077] 2. Generate Single Sign-On Credentials: The cloud application SDK on the real device sends a request to the unified authentication center to generate a single sign-on credential for the cloud device based on the local first token (containing information such as the user's unique ID, encrypted signature, and validity period). This credential is encrypted and used for cloud device authentication.

[0078] 3. Credential Transmission and Verification: The physical device transmits the encrypted single sign-on credentials to the cloud device's end-to-cloud collaboration module (cloud side) via the end-to-cloud collaboration module (cloud side). After receiving the credentials, the cloud device decrypts them and sends a credential verification request to the unified authentication center.

[0079] 4. Cloud machine obtains second token: The authentication center verifies the validity of the credentials (including signature verification, validity period check, user identity matching, etc.). After successful verification, it returns authorization information to the cloud machine. The third-party application of the cloud machine requests the cloud application platform based on the authorization information to obtain the second token used for cloud machine application login.

[0080] 5. Dual-Token Verification Login: The third-party application on the cloud device submits the second token it obtains together with the first token transmitted from the real device to the cloud application's authentication module to verify the association between the two (ensuring they are from the same user) and the degree of permission matching. After passing the verification, the login to the target application on the cloud device is completed, and a login success status is returned.

[0081] 6. Status Synchronization and Feedback: The cloud machine synchronizes the successful login status to the real machine through the end-to-cloud collaboration module. After the cloud application SDK on the real machine confirms the login, it can start the subsequent page redirection and data transmission process based on the established identity association.

[0082] The entire process achieves consistent identity verification between the end and the cloud through a unified authentication center, ensures login security and user identity uniqueness through a dual-token mechanism, and protects credential security through encrypted transmission of the end-to-cloud collaboration module. Ultimately, users can log in to the target application on the cloud device without having to repeatedly enter their account and password.

[0083] The following will explain in detail how to use the edge-cloud collaboration module to jump to the rendered page, including the following methods: The end-to-cloud collaboration module transmits the user device's parameters and the first token to the cloud device. When the user device starts up, perform a second token authentication for the cloud device; When authentication is successful, the target application's audio, video, and / or business data are rendered and sent to the user's device via cloud devices.

[0084] Specifically, after the user device triggers the process of redirecting to the cloud application rendering page, the real device's end-to-cloud collaboration module - the end side can encrypt the business parameters obtained from the local target application (such as the query conditions required for page redirection, user operation data, etc.) and the first TOKEN (used for identity association verification), and send them to the cloud device's end-to-cloud collaboration module - the cloud side through the established transmission channel.

[0085] After receiving the parameters and the first token, the cloud device can initiate the authentication process for the second token: the cloud-side cloud collaboration module sends the second token (cloud device login credential) and the received first token to the unified authentication center to verify the association and validity of the two (such as whether they belong to the same user, whether the token is within its validity period, etc.).

[0086] Once authentication is successful, the target application on the cloud device can load the corresponding target page based on the received business parameters. At the same time, the audio and video stream encoding module is activated to convert the real-time screen and operation interaction of the page into an audio and video stream. The cloud-side cloud collaboration module sends the audio and video stream and the business data generated by the page interaction (such as loaded text, image resources, etc.) to the user device in real time through the transmission channel.

[0087] The end-to-cloud collaboration module on the user device receives audio / video streams and service data. The cloud application rendering module then decodes and renders these data, ultimately reproducing the target application's page content and interactive effects on the real device's rendered page. This ensures a smooth user experience when interacting with the cloud application on the real device. Throughout this process, the end-to-cloud collaboration module continuously maintains the data transmission link, ensuring low-latency transmission of audio / video streams and real-time synchronization of service data.

[0088] For example, as shown in Figure 4 above, after a user triggers a page redirection in a third-party application (on the real device), the AOP intercepts the system's redirection method. The cloud application SDK first obtains information such as the original redirected page, and then establishes a connection with the corresponding module on the cloud side via the end-to-cloud collaboration module (on the real device). In this chain, the real device cloud application SDK, through the end-to-cloud collaboration module, encrypts and transmits the target page's fully qualified name, business parameters (such as docm, business parameter fields), and the first token to the cloud device end-to-cloud collaboration module. After receiving the data, the cloud device completes authentication using the second token combined with the first token. The target application on the cloud device loads the page according to the parameters, and after audio and video encoding, the end-to-cloud collaboration module sends the audio and video streams and business data back to the fax machine. The real device cloud application rendering module decodes and renders the cloud application page, realizing the end-to-cloud page redirection and rendering interaction. During the process, the link is continuously maintained and transmitted to ensure data synchronization and a low-latency experience.

[0089] It should be noted that the methods for redirection disclosed in this publication also include: When the target application within the cloud device is closed, a shutdown command is sent to the user device through the end-to-cloud collaboration module. The shutdown command is used to instruct the rendering page on the user device to be closed.

[0090] Specifically, when a target application within a cloud device (cloud server) performs a shutdown operation (such as when a user triggers a return to the root page and closes the application on the cloud server page, or when it automatically closes due to business logic), the cloud-end collaboration module on the cloud server side—the cloud side—recognizes the change in the target application's shutdown state and then generates and encapsulates a shutdown command (this command contains a clear "close real device rendering page" identifier and related verification information). Through the established and continuously maintained cloud-end data transmission channel, the shutdown command is sent to the cloud-end collaboration module on the user device (real device)—the end-side. Upon receiving the command, the end-end collaboration module on the real device—the end-side—verifies the command's legality and completeness. If the verification passes, it triggers the cloud application rendering module to execute the shutdown logic, destroying the rendering container currently displaying the cloud application page, releasing related resources, and ultimately closing the cloud application rendering page on the real device, returning the application to the original page state of the real device, ensuring synchronization between the cloud and end states.

[0091] For example, from above Figure 4 As can be seen, when the "Cloud Application SDK" on the cloud server side executes the "Close Cloud Application Page" operation, it sends a close command to the "End-to-Cloud Collaboration Module (Cloud Application SDK Integration)" on the real device side through the "End-to-Cloud Collaboration Module". After receiving the command, the real device side triggers the "Close Cloud Application Display Page" action, realizing that when the cloud application is closed, the real device rendering page closes synchronously, fully presenting the page closing linkage process under end-to-cloud collaboration, and ensuring that the application states on both ends are consistent.

[0092] The communication method disclosed herein will be described in detail below, and also includes: User equipment and cloud equipment communicate synchronously through a data synchronization module; When a user device logs in for the first time, the data synchronization module will synchronize the user device’s local data to the cloud device in full or in increments. When a cloud device logs in for the first time, the data synchronization module will synchronize the cloud device's data to the user's device in full or in increments. When a user device or cloud device detects a data update, the incremental data is determined by comparing the local data on the user device and the data on the cloud device, and then the incremental data is synchronized through the data synchronization module.

[0093] Specifically, during the interaction between user devices and cloud devices, the data synchronization module can pre-establish a bidirectional data channel. When a user device logs into the system for the first time, the data synchronization module can automatically scan the locally stored data related to the target application (such as user configuration information, historical operation records, cache files, etc.), determine the need for full or incremental synchronization based on the data version and identifier (if there is no corresponding record in the cloud, full synchronization is performed; if there is basic data, only the newly added or modified parts are synchronized), and push the data to the cloud device through encrypted transmission. After receiving the data, the cloud device verifies and stores it, building an initial data environment consistent with the user device.

[0094] When a cloud device logs in for the first time (such as when a user accesses a target application on the cloud device for the first time), the cloud device's data synchronization module can sort through the target application data stored on its own device and synchronize the cloud-specific configurations and business data to the user device according to the same full / incremental judgment logic, ensuring that the user can obtain the key data already available in the cloud on the real device.

[0095] In subsequent use, regardless of whether it is a user device or a cloud device, as long as the target application-related data is updated (such as a user modifying their personal information on the real device or a new business data being pushed to the application backend on the cloud device), the data synchronization module can immediately trigger the difference comparison mechanism: extract information such as the version number, modification timestamp, and data hash value of the data at both ends, accurately identify the incremental data that has been added or changed only on one end, and then synchronize the incremental data to the other end through the data channel, ensuring that the data of the user device and the cloud device always remain in real time and consistent, providing a reliable data foundation for the application experience of end-to-end cloud collaboration.

[0096] For example, Figure 6 is an interactive flowchart of data synchronization from a real device to a cloud machine provided in an embodiment of this disclosure. As can be seen from Figure 6: When a user interacts with a third-party application (such as Migu Music) on the real device, generating data (such as locally downloaded music files or modified personalized configurations), the file monitoring module in the real device's cloud application SDK continuously monitors file modifications in the third-party application's file storage area. When a new file is generated or an existing file is changed (i.e., a data update event), the file synchronization module is triggered. It first sends a request to the cloud application platform - storage service - to obtain the target file storage address. After obtaining the address, the file synchronization module encrypts and encapsulates the data to be synchronized locally (full or incremental; full if it's the first upload, incremental if it's an update, compared with existing records in the cloud). Then, through the transmission channel established by the end-cloud collaboration module, it transmits the data to the cloud application SDK corresponding to the new third-party application (new Migu Music) on the cloud phone side.

[0097] After receiving data, the file transfer module of the cloud application SDK on the cloud phone side verifies and decrypts it, and stores it in the cloud phone's third-party application file storage area according to the data type and application logic. At the same time, the file monitoring module on the cloud phone side detects changes in the file storage area. If it involves update information that needs to be fed back to the real device (such as the file index processed in the cloud, synchronization status), it will send it back to the real device through the end-cloud collaboration module. After receiving it, the cloud application SDK on the real device updates its local synchronization status record, completing a closed loop of data synchronization from the real device to the cloud device, ensuring real-time consistency of application data on both ends.

[0098] For example, Figure 7 is an interactive flowchart of data synchronization from a cloud device to a real device provided by an embodiment of this disclosure. As can be seen from Figure 7: When a user operates a new third-party application (such as the new Migu Music) on the cloud phone side, resulting in data changes (such as music resources or configuration information updated in the cloud), the file monitoring module in the cloud application SDK of the cloud phone continuously monitors the file storage area of ​​the third-party application. When a file modification or addition (data update event) is captured, the file synchronization module is activated and first requests the file storage target address from the cloud application platform - storage service. After obtaining the address, the file synchronization module encrypts and packages the data to be synchronized on the cloud device side (full or incremental, full for the first synchronization, incremental for subsequent updates), and pushes it to the cloud application SDK corresponding to the third-party application (Migu Music) on the real device side through the transmission channel established by the end-cloud collaboration module.

[0099] After receiving data, the file transfer module of the cloud application SDK on the real device verifies, decrypts, and stores it in the file storage area of ​​the third-party application on the real device. Simultaneously, the file monitoring module on the real device detects changes in the file storage area. If there is updated information (such as synchronization status or local processing results), it needs to be transmitted back. This feedback is sent to the cloud phone through the end-to-cloud collaboration module. The cloud application SDK on the cloud phone receives this feedback and updates the cloud synchronization record, completing the data synchronization process from the cloud device to the real device. This ensures real-time consistency of application data on both ends, allowing users to access the latest data from the cloud device application on the real device.

[0100] The communication method disclosed herein will be further described below, including: When a cloud device requests to obtain hardware data, it sends a retrieval command carrying a hardware type identifier to the user device. Based on the retrieval command, acquire the hardware data collected by the user equipment; Send hardware data to cloud devices.

[0101] In this disclosure, hardware data can be understood as real-time data collected or generated by various physical hardware components of the user device (real device), including but not limited to location information (GPS data), sensor data (accelerometer, gyroscope, light sensor, etc.), images / videos captured by the camera, audio recorded by the microphone, Bluetooth device information, NFC tag data, etc., which are key data support for cloud devices to simulate the hardware environment of the real device and realize application function adaptation.

[0102] Specifically, when a target application in a cloud device needs to invoke hardware functions (such as a map application obtaining location data or a motion application reading accelerometer data), since the cloud device is a virtual environment and cannot directly obtain physical hardware data, a retrieval command carrying a hardware type identifier (such as "GPS" or "accelerometer sensor," explicitly specifying the required hardware type) can be generated and sent through the cloud-side cloud-edge collaboration module. After receiving this command, the user device's cloud-edge collaboration module (edge-side) parses the hardware type identifier and invokes the corresponding system hardware module interface (such as the GPS service interface or sensor management interface), triggering the real device's hardware components to collect real-time data. After collection, the real device's cloud-edge collaboration module (edge-side) encapsulates and encrypts the hardware data and transmits it back to the cloud device's cloud-edge collaboration module (cloud-side) through the established transmission channel. Upon receiving the hardware data, the cloud device parses it and transmits it to the target application, enabling the cloud application to run its relevant functions normally based on the real device's actual hardware data, achieving remote invocation and adaptation of the real device's hardware capabilities in the cloud environment. Throughout the entire process, the transmission of hardware data follows the principle of real-time performance, ensuring that the interactive experience of the cloud application is consistent with local operation.

[0103] For example, Figure 8 This is a schematic flowchart illustrating a hardware simulation relationship provided in an embodiment of this disclosure. From Figure 8 As can be seen, Figure 8 is a schematic flowchart of a hardware simulation relationship provided by an embodiment of this disclosure. As can be seen from Figure 8, when a target application in a cloud device (such as a cloud service or cloud phone) triggers a hardware call request, the cloud-side end-cloud collaboration module (the cloud-corresponding functional unit in the figure) generates a call instruction with a hardware type identifier (such as GPS, camera, etc.), which is then sent to the user device (real device) via the network transmission channel.

[0104] After the end-to-cloud collaboration module on the real device side (the receiving unit corresponding to the real device in the diagram) captures the instruction, it parses the hardware type, calls the real device's own system hardware interface (such as calling the GPS module, camera driver, etc.), and triggers the real device's physical hardware to collect corresponding data (such as GPS positioning information, camera footage). The collected hardware data is encapsulated and encrypted by the end-to-cloud collaboration module before being sent back to the cloud device side. After receiving and parsing the hardware data, the cloud device injects it into the target application on the cloud side, enabling the cloud application to perform functions based on the real device's hardware data (such as cloud map applications using real device GPS data for positioning, cloud video applications calling real device camera footage), fully presenting the process of the cloud device remotely calling and simulating the use of the real device's hardware capabilities through the end-to-cloud collaboration mechanism, ensuring the consistency of the cloud application's functional experience with the local operation of the real device.

[0105] This disclosure also provides a communication device. Figure 9 A structural block diagram of a communication device provided in an embodiment of this disclosure, such as... Figure 9 As shown, the communication device 900 includes: Configuration unit 901 is used to configure the access rules of the target application on the cloud device; Interception unit 902 is used to intercept page redirection requests and / or button click redirection when a user device accesses the target application; The jump unit 903 is used to jump to the rendered page of the target application corresponding to the cloud device for access when at least one of the target page corresponding to the page jump request and the target identifier corresponding to the button matches the access rule.

[0106] In one exemplary embodiment, the configuration unit 901 is specifically configured to: receive the target application version number, target page, target identifier, and rendering page configured by the third-party developer; establish a mapping relationship between the target application version number, target page, and / or target identifier and rendering page to form an access rule entry; add effective conditions to the access rule entry to obtain an access rule; the effective conditions include at least one of the following: time range and user permissions.

[0107] In one exemplary embodiment, the interception unit 902 is specifically used to: detect the access environment; and when the access environment is a real environment, intercept system page jumps and / or button click views.

[0108] In one exemplary embodiment, the jump unit 903 is specifically used to: determine the matching degree between the target page and / or the target identifier and the access rules respectively; when the matching degree meets the threshold, log in to the target application of the user device and the cloud device; establish a transmission channel between the user device and the cloud device through the end-cloud collaboration module, and jump to the rendering page.

[0109] In one exemplary embodiment, the jump unit 903 is specifically configured to: obtain a first token of the user device and a single sign-on credential of the cloud device; obtain a second token of the cloud device based on the credentials; and log in to the target application of the cloud device based on the first token and the second token.

[0110] In one exemplary embodiment, the jump unit 903 is specifically used to: transmit the parameters of the user device and the first token to the cloud device through the end-to-cloud collaboration module; perform second token authentication of the cloud device when the user device starts up; and when the authentication is successful, render and send the audio, video and / or business data of the target application to the user device through the cloud device.

[0111] In one exemplary embodiment, the jump unit 903 is further configured to: when the target application in the cloud device is closed, send a shutdown command to the user device through the end-cloud collaboration module, the shutdown command being used to instruct the user device to close the rendering page.

[0112] In one exemplary embodiment, the jump unit 903 is further configured to: enable synchronous communication between the user equipment and the cloud device through the data synchronization module; when the user equipment logs in for the first time, synchronize the user equipment's local data to the cloud device in full or incrementally through the data synchronization module; when the cloud device logs in for the first time, synchronize the cloud device's data to the user equipment in full or incrementally through the data synchronization module; when the user equipment or the cloud device detects a data update, compare the user equipment's local data and the cloud device's data to determine the incremental data, and synchronize the incremental data through the data synchronization module. In one exemplary embodiment, the jump unit 903 is further configured to: send a retrieval instruction carrying a hardware type identifier to the user device when the cloud device requests to obtain hardware data; obtain the hardware data collected by the user device based on the retrieval instruction; and send the hardware data to the cloud device.

[0113] Figure 10 This is a hardware block diagram of an electronic device provided according to an embodiment of the present disclosure. The electronic device 1000 according to an embodiment of the present disclosure includes at least a processor and a memory for storing computer-readable instructions. When the computer-readable instructions are loaded and executed by the processor, the processor performs the communication method described in any of the preceding embodiments of the present disclosure.

[0114] Figure 10The illustrated electronic device 1000 specifically includes a central processing unit (CPU) 1001, a graphics processing unit (GPU) 1002, and a memory 1003. These units are interconnected via a bus 1004. The CPU 1001 and / or GPU 1002 can function as the aforementioned processor, and the memory 1003 can function as the aforementioned memory storing computer-readable instructions. Furthermore, the electronic device 1000 may also include a communication unit 1005, a storage unit 1006, an output unit 1007, an input unit 1008, and an external device 1009, all of which are also connected to the bus 1004.

[0115] Figure 11 This is a schematic diagram of a computer-readable storage medium provided in an embodiment of this disclosure. (As shown...) Figure 11 As shown, a computer-readable storage medium 1100 according to an embodiment of the present disclosure stores computer-readable instructions 1101 thereon. When the computer-readable instructions 1101 are executed by a processor, the communication method described with reference to the above figures according to any embodiment of the present disclosure is performed. The computer-readable storage medium includes, but is not limited to, volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, optical disk, magnetic disk, etc.

[0116] This disclosure further provides a computer program product, including a computer program that, when executed by a processor, implements the communication method described in any of the preceding embodiments of this disclosure.

[0117] The present disclosure provides a communication method, apparatus, electronic device, storage medium, and program product. This disclosure configures access rules for a target application on a cloud device; when a user device accesses the target application, it intercepts page redirection requests and / or button clicks; when at least one of the target page corresponding to the page redirection request and the target identifier corresponding to the button matches the access rules, it redirects the user to the rendered page of the target application on the cloud device for access. Compared to existing models that force users to upgrade local applications or restrict usage due to version incompatibility, this disclosure allows users to access the latest features of a target application through a cloud-rendered page without forcing them to upgrade their local applications. This satisfies users' habits of using older versions while allowing them to experience new features on demand, avoiding user experience degradation and user churn caused by forced upgrades, thus achieving a balance between application feature iteration and user retention. In summary, the technical solution provided by this disclosure can maximize user experience and satisfaction while ensuring continuous application iteration and updates, providing strong support for the long-term development of applications.

[0118] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0119] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0120] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0121] Additionally, as used herein, the "or" used in a list of items beginning with "at least one" indicates a separate list, such that a list of, for example, "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not imply that the described example is preferred or better than other examples.

[0122] It should also be noted that in the systems and methods of this disclosure, the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered as equivalent solutions to this disclosure.

[0123] Various changes, substitutions, and modifications can be made to the technology described herein without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of this disclosure is not limited to the specific aspects of the processes, machines, manufactures, events, means, methods, and actions described above. Currently existing or later-developed processes, machines, manufactures, events, means, methods, or actions that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein can be utilized. Therefore, the appended claims include such processes, machines, manufactures, events, means, methods, or actions within their scope.

[0124] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0125] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

Claims

1. A communication method, characterized in that, The method includes: Configure access rules for the target application on cloud devices; When a user device accesses the target application, intercept page redirection requests and / or button click redirections; When at least one of the target page corresponding to the page redirection request and the target identifier corresponding to the button matches the access rule, the user is redirected to the rendered page of the target application corresponding to the cloud device for access.

2. The method according to claim 1, characterized in that, The configuration target applies to the access rules of cloud devices, including: Receive the target application version number, the target page, the target identifier, and the rendered page configured by the third-party developer; Establish a mapping relationship between the target application version number, the target page and / or the target identifier, and the rendered page to form access rule entries; The access rule is obtained by adding an effective condition to the access rule entry; the effective condition includes at least one of the following: time range, user permissions.

3. The method according to claim 1, characterized in that, The step of intercepting page redirection requests and / or button click redirection when a user device accesses the target application includes: Detect the access environment; When the access environment is a real environment, intercept system page jumps and / or button click views.

4. The method according to claim 1, characterized in that, When the target page corresponding to the page redirection request and / or the target identifier corresponding to the button respectively match the access rule, the user is redirected to the rendered page of the target application corresponding to the cloud device for access, including: Determine the degree of match between the target page and / or the target identifier and the access rule; When the matching degree meets the threshold, log in to the target application of the user device and the cloud device; The user device and the cloud device establish a transmission channel through the end-to-cloud collaboration module, and then the user is redirected to the rendering page.

5. The method according to claim 4, characterized in that, When the matching degree meets the threshold, logging into the target application of the user device and the cloud device includes: Obtain the first token (TOKEN) of the user device and the credentials for single sign-on to the cloud device; Based on the credentials, obtain the second token of the cloud device; Log in to the target application of the cloud device based on the first token and the second token.

6. The method according to claim 4 or 5, characterized in that, The step of establishing a transmission channel between the user device and the cloud device through the end-to-cloud collaboration module and redirecting to the rendering page includes: The end-to-cloud collaboration module transmits the parameters of the user device and the first token to the cloud device. When the user equipment starts up, the cloud device performs a second token authentication. When the authentication is successful, the target application's audio, video, and / or business data are rendered and sent to the user device via the cloud device.

7. The method according to claim 4, characterized in that, The method further includes: When the target application within the cloud device is closed, a shutdown command is sent to the user device through the end-cloud collaboration module. The shutdown command is used to instruct the rendering page on the user device to be closed.

8. The method according to claim 1, characterized in that, The method further includes: The user equipment and the cloud equipment communicate synchronously through a data synchronization module; When the user device logs in for the first time, the data synchronization module synchronizes the user device's local data to the cloud device in full or incrementally. When the cloud device logs in for the first time, the data synchronization module synchronizes the full or incremental data of the cloud device to the user device. When the user equipment or the cloud device detects a data update, it compares the local data of the user equipment with the data of the cloud device to determine the incremental data, and then synchronizes the incremental data through the data synchronization module.

9. The method according to claim 1, characterized in that, The method further includes: When the cloud device requests to obtain hardware data, it sends a retrieval instruction carrying a hardware type identifier to the user equipment. Based on the retrieval instruction, the hardware data collected by the user equipment is obtained; The hardware data is sent to the cloud device.

10. A communication device, characterized in that, The device includes: The configuration unit is used to configure the access rules for the target application on the cloud device. The interception unit is used to intercept page jump requests and / or button click jumps when a user device accesses the target application; The jump unit is used to jump to the rendered page of the target application corresponding to the cloud device for access when at least one of the target page corresponding to the page jump request and the target identifier corresponding to the button matches the access rule.

11. An electronic device, characterized in that, include: Memory, used to store computer-readable instructions; as well as A processor for executing the computer-readable instructions, causing the electronic device to perform the method as described in any one of claims 1-9.

12. A non-transitory computer-readable storage medium for storing computer-readable instructions, characterized in that, When the computer-readable instructions are executed by a processor, the processor performs the method as described in any one of claims 1-9.

13. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method as described in any one of claims 1-9.

Images