Application operation method and device and electronic equipment

Abstract

The invention discloses an application operation method and device and electronic equipment, and belongs to the technical field of information processing. The method comprises the following steps: receiving a first input for a first application through an application auxiliary operation service; in response to the first input, operation request information is sent to the second electronic equipment through the application auxiliary operation service, and the operation request information at least comprises application information of the first application; operation response information sent by the second electronic equipment is received through the application auxiliary operation service, and the operation response information is generated after the second electronic equipment receives the operation request information, locally runs a page corresponding to the first application and responds to auxiliary operation on the page; and operating the first application based on the operation response information through the application auxiliary operation service.

Description

Technical Field

[0001] This application belongs to the field of information processing technology, specifically relating to an application operation method, apparatus, and electronic device. Background Technology

[0002] With the widespread adoption of mobile smart devices and digital services, all aspects of social life are increasingly reliant on various applications. However, for elderly users, visually impaired individuals, and those with limited digital skills, it is difficult to fully enjoy the convenience brought by technology.

[0003] Currently, most mainstream operating systems have integrated or support remote assistance functions, allowing family members, friends, or customer service personnel to remotely view and operate the user's device interface, thereby providing real-time step-by-step guidance and problem-solving support. This has played a significant role in overcoming spatial barriers and providing immediate assistance. However, its overly broad scope has raised security risks.

[0004] Therefore, existing remote assistance technologies pose a risk of privacy breaches. Summary of the Invention

[0005] The purpose of this application is to provide an application operation method, device, and electronic device that can solve the problem of privacy leakage risks based on existing remote assistance technologies.

[0006] In a first aspect, embodiments of this application provide an application operation method applied to a first electronic device, wherein the operating system framework layer of the first electronic device deploys application-assisted operation services, and the method includes: Receive the first input to the first application through the application's auxiliary operation service; In response to the first input, an operation request information is sent to the second electronic device through the application-assisted operation service. The operation request information includes at least: application information of the first application. The system receives operation response information sent by the second electronic device through the application's auxiliary operation service. The operation response information is generated by the second electronic device after receiving the operation request information, running the page corresponding to the first application locally, and responding to the auxiliary operation on the page. By using the application's auxiliary operation service, the first application is operated based on the operation response information.

[0007] Secondly, embodiments of this application provide an application operation method applied to a second electronic device, wherein the operating system framework layer of the second electronic device deploys application-assisted operation services, and the method includes: The application receives auxiliary request information sent by the first electronic device through the application auxiliary operation service. The operation request information includes at least: application information of the first application. Run the page corresponding to the first application locally using the application's auxiliary operation service; In response to auxiliary operations on the page, operation response information is generated by applying auxiliary operation services; By applying auxiliary operation services, operation response information is sent to the first electronic device.

[0008] Thirdly, embodiments of this application provide an application operation device applied to a first electronic device, wherein the operating system framework layer of the first electronic device deploys application-assisted operation services, and the device includes: The first input module is used to receive the first input to the first application through the application auxiliary operation service; The first sending module is used to respond to the first input by sending operation request information to the second electronic device through an application-assisted operation service. The operation request information includes at least: application information of the first application. The first receiving module is used to receive operation response information sent by the second electronic device through the application auxiliary operation service. The operation response information is generated by the second electronic device after receiving the operation request information, running the page corresponding to the first application locally and responding to the auxiliary operation on the page. The operation module is used to operate the first application based on the operation response information through the application-assisted operation service.

[0009] Fourthly, embodiments of this application provide an application operation device for a second electronic device, wherein the operating system framework layer of the second electronic device deploys application-assisted operation services, and the device includes: The second receiving module is used to receive auxiliary request information sent by the first electronic device through the application auxiliary operation service. The operation request information includes at least: application information of the first application. The runtime module is used to run the page corresponding to the first application locally through the application auxiliary operation service; The generation module is used to respond to auxiliary operations on the page by generating operation response information through the application auxiliary operation service; The second sending module is used to send operation response information to the first electronic device through the application-assisted operation service.

[0010] Fifthly, embodiments of this application provide an electronic device including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.

[0011] In a sixth aspect, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0012] In a seventh aspect, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0013] Eighthly, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the first aspect.

[0014] In the embodiments of this application, a first input to a first application is received through an application-assisted operation service. In response to the first input, an operation request message is sent to a second electronic device through the application-assisted operation service. The operation request message includes at least application information of the first application, thereby precisely limiting the scope of assistance to a specific application, significantly reducing data transmission volume and avoiding unnecessary permission exposure. Operation response information sent by the second electronic device is received through the application-assisted operation service. This operation response information is generated by the second electronic device after receiving the operation request message, running the page corresponding to the first application locally, and responding to the assisted operation on the page. This eliminates the need for the second electronic device to directly access or interfere with the actual operating state of the first device, thus isolating privacy risks. By using the application-assisted operation service to operate the first application based on the operation response information, effective cross-device operation assistance is achieved while reducing the risk of privacy leakage and improving the security and controllability of the assistance process. Attached Figure Description

[0015] Figure 1 This is a flowchart of an application operation method provided in an embodiment of this application; Figure 2 This is a flowchart of an application operation architecture provided in an embodiment of this application; Figure 3 This is a flowchart of another application operation method provided in the embodiments of this application; Figure 4 This is a flowchart of an application operation device provided in an embodiment of this application; Figure 5 This is a structural diagram of another application operation device provided in the embodiments of this application; Figure 6 This is one of the hardware structure diagrams of the electronic device according to an embodiment of this application; Figure 7 This is the second schematic diagram of the hardware structure of the electronic device according to an embodiment of this application. Detailed Implementation

[0016] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0017] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0018] The technical terms used in the embodiments of this application are explained below: The Accessibility Operate Service (AOS), located at the operating system framework layer, is the core hub of this technical solution. It is primarily responsible for managing core functions related to cross-device application-assisted operation, including but not limited to: maintaining a list of applications allowed for remote assistance, synchronizing application status and operation commands between devices, scheduling interface content transmission and privacy filtering, and handling connections and communication between devices.

[0019] The Application Permission Management Service (PMS) manages application access permissions to system resources and user data. In this technical solution, its functionality has been expanded to include device-level authorization capabilities. This allows users to grant specific data permissions of an application on one device to another trusted device, enabling secure collaborative data access without screen sharing.

[0020] Screen Display Permission (SDP) is a fine-grained type of remote assistance permission. When a user grants this permission to an application, the assisting party can only view the application's live interface content on the assisted device, but cannot remotely control the interface by clicking, swiping, or doing anything else.

[0021] Screen Display and Control Permission (SDACP) is a more advanced type of remote assistance permission than SDP. When a user grants this permission to an application, the assisting party can view the application's live interface and is also allowed to control the interface remotely. This permission is suitable for complex assistance scenarios that require direct intervention from the other party.

[0022] In response to the problems in related technologies, this application provides an application operation method, device, and electronic device that can solve the problem of privacy leakage risks in existing remote assistance technologies.

[0023] The application operation methods provided in this application embodiment will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0024] Figure 1 This is a flowchart of an application operation method provided in an embodiment of this application.

[0025] like Figure 1 As shown, the application operation method may include steps 110-140. This method is applied to a first electronic device, and the operating system framework layer of the first electronic device has an application-assisted operation service deployed, as detailed below: Step 110: Receive the first input to the first application through the application assistance service; Step 120: In response to the first input, send operation request information to the second electronic device through the application-assisted operation service. The operation request information includes at least: application information of the first application. Step 130: Receive operation response information sent by the second electronic device through the application auxiliary operation service. The operation response information is generated by the second electronic device after receiving the operation request information, running the page corresponding to the first application locally and responding to the auxiliary operation on the page. Step 140: Using the application's auxiliary operation service, the first application is operated based on the operation response information.

[0026] The first electronic device refers to the device requiring operational assistance, such as a smartphone for an elderly user. The second electronic device refers to the device providing remote assistance, such as a tablet computer held by the elderly user's children. The first input is a specific interactive command triggered by the user on the first electronic device when intending to obtain assistance. Application information is a set of data used to uniquely identify the application to be operated and its state. Operation request information is a data packet encapsulating the aforementioned application information and used to initiate an assistance request to the assisting party. Operation response information is a feedback data packet containing a sequence of operation commands generated by the second electronic device after completing local simulation operations.

[0027] In step 110, the user's explicit intent to request assistance is captured through the application's accessibility services. For example, a user might perform a long-press gesture on a specific button in an application for more than three seconds, and the long-press event is recognized as the first input requesting assistance. Alternatively, a user might generate the first input by triggering an accessibility shortcut that floats in a hierarchy.

[0028] The application's Assistive Operations Service actively listens for system-wide interaction events that conform to specific patterns. When a user performs a preset, defined first input request for assistance on any application interface, the gesture event is first captured by the system's input subsystem and passed to the framework layer. The application's Assistive Operations Service is registered here as a priority handler for this type of special input event. Upon receiving the gesture event, the application's Assistive Operations Service immediately parses the gesture event to confirm that it is a valid assistance request, thus completing the conversion and determination from the original hardware event to a clear assistance intent.

[0029] In step 120, after confirming the auxiliary intent, the core state identifier of the current application is automatically extracted and assembled into a structured request, which is then sent through the established communication link between devices. For example, the extracted application information of the first application could be the package name of the first application. Alternatively, the application information could be a combination of the package name and the name of the currently active foreground page. Together, this achieves an accurate description of the application state, enabling the second electronic device to locate the same application scenario.

[0030] The application-assisted operation service interacts with components such as the system activity management service to accurately obtain the context information of the current foreground application. Then, the obtained raw information undergoes secure processing, such as calling a privacy filtering module to remove sensitive fields. Next, it assembles the processed application information, along with potentially included application identity signature information, into a structured, lightweight operation request data packet. Finally, through the operating system's underlying network communication framework, it addresses and connects to the paired and online trusted application-assisted operation service instance corresponding to the second electronic device, accurately sending the request information. The entire process is completed under system permission control, ensuring the legality of information collection and the secure and controllable outbound data transmission.

[0031] In step 130, the application assistive operation service listens for and receives processing results from the second electronic device server. The generation of operation response information involves the second electronic device locally recreating the operating environment and recording the operation trajectory. For example, if the second electronic device launches the same application based on the received package name, and the assistant clicks the "Next" button on the corresponding page of the application, this click event is recorded, and operation response information containing event type and coordinate information is generated. For example, if the assistant performs a series of operations, such as clicking a radio button and then swiping the screen, the second electronic device records these events sequentially, forming an ordered sequence of operations encapsulated in the operation response information.

[0032] The application's auxiliary operation service continuously monitors network packets from a second electronic device. Upon receiving an operation response, it first verifies the integrity and authenticity of the data packet's origin to prevent man-in-the-middle attacks or data tampering. Then, it parses the instruction content. For example, if the operation response is a linked list of operation information, the service parses its structure; if it contains fast execution instructions based on shared signatures, the service verifies the signature's validity. The application's auxiliary operation service transforms the raw, cross-network byte stream into a set of secure operation instructions that the system can understand and schedule internally.

[0033] In step 140, by applying an auxiliary operation service, the operation response information is converted into a locally executable simulated input event to operate the first application. For example, the first electronic device parses the "click next" event from the operation response information and injects a simulated touch event at the same button position in the local first application. For example, for a series of operation sequences, the first electronic device will parse and execute each sub-operation event in sequence, thereby reproducing the entire operation process completed remotely by the assistant.

[0034] By using an auxiliary operation service to simulate user operations in a secure and controlled manner, and based on the parsed operation instructions, a simulated touch event is generated as a system instance by calling the input management service interface of the framework layer, and injected into the window and input queue of the current primary application. The auxiliary operation service securely and accurately translates abstract operation instructions from the outside and applies them to the local, specific application interface.

[0035] In one possible embodiment, the operating system framework layer of the first electronic device also deploys a permission management service, and the following steps may be included before step 110: Based on the device interconnection relationship established between the first electronic device and the second electronic device, the permission management service adds device-level authorization for the second electronic device for at least one data permission of the first application; The device-level authorization is used to authorize the second electronic device to access data in the first application corresponding to the authorized data permissions in order to perform the auxiliary operation.

[0036] The access control service is a core service within the operating system framework layer responsible for managing and controlling access permissions for all applications within the system to device resources, user data, and sensitive functions. In this embodiment, the functionality of the access control service is extended to support cross-device access control. Device interconnection refers to the pairing and trusted connection between two devices via a security protocol. Data permissions refer to the permission granted to an application to access specific types of user data or device functions, such as reading the address book, accessing the photo album, or using location services.

[0037] By extending the underlying system permission model, a novel, fine-grained data access control mechanism is created for cross-device collaboration scenarios, enabling precise determination of whether a specific device has the right to access specific data of a particular application on that device. This requires the permission management service to maintain an underlying authorization record containing a triplet of device identifier, application identifier, and permission item.

[0038] For example, when a user wants to allow their tablet to assist with the photo app on their phone, they can add an authorization entry for the tablet's device identifier for the "Read Images" permission in the phone's permission settings. Similarly, a user can grant the in-vehicle smart terminal's device identifier the "Get Precise Location" permission for the "Maps" app.

[0039] By leveraging the device interconnection relationship established between the first and second electronic devices, and through the permission management service, device-level authorization is added to at least one data permission of the first application for the second electronic device, thereby giving the user the decision-making and control rights over data sharing. When subsequent auxiliary operations require data, the second electronic device can securely access the required data based on this pre-obtained and explicit device-level authorization.

[0040] In one possible embodiment, step 120 may specifically include the following steps: In response to the first input, obtain the initial application information of the first application; The initial application information is processed to remove privacy information, resulting in the application information of the first application; the removal of privacy information includes: hiding, blurring or replacing. Generate operation request information based on the application information of the first application; Send an operation request message to the second electronic device.

[0041] The initial application information may contain various data used to locate the application's status. The initial application information undergoes privacy-de-privacy processing to obtain the application information of the first application that ultimately constitutes the operation request information. This privacy-de-privacy processing aims to identify and process data items that may involve user privacy, and methods include, but are not limited to: hiding specific fields (i.e., directly removing privacy information); or obfuscating the information, such as replacing a precise contact name with "Mr."; or replacing the actual account ID with a generic identifier without specific meaning. After privacy de-privacy processing, a structured operation request is generated based on the processed application information of the first application, which no longer contains sensitive content, and then the request is sent to the second electronic device via the inter-device communication link.

[0042] Before sending application status information to the assistive device, privacy-related content unrelated to the current operation is actively stripped or obscured to ensure minimal data transmission. For example, when the first input occurs within a banking application, the initial application information may include fields such as the last four digits of the account number and the balance. After de-privacy processing, these sensitive fields are hidden or replaced with asterisks before generating the operation request information, so that the generated application information only contains the application identifier and page identifier. As another example, when requesting assistance in a contacts application, the specific contact name and phone number in the initial application information are first obfuscated into generalized identifiers such as "Contact A" and "Number B" before being used to construct the operation request.

[0043] By performing privacy de-privacy processing, the security of the entire assisted operation process is improved. Privacy protection actions are brought forward, and sensitive information is stripped or desensitized before the data leaves the first electronic device. This ensures that the information transmitted and received subsequently does not pose a risk of privacy leakage, reduces the risk of privacy leakage that may occur due to the transmission of application information, and at the same time ensures that the transmitted information is still sufficient for the second electronic device to accurately locate the application scenario that requires assistance, thus achieving a balance between security and functionality.

[0044] In one possible embodiment, the application information of the first application includes: The application identifier of the first application, the page identifier of the first page currently displayed by the first application, and the control identifier of the first control for the first input indication; Step 140 may specifically include the following steps: Based on the operation response information, the first control is operated on the first page of the first application.

[0045] The operation response information is parsed to obtain the contained operation instructions. On the first page of the first application, the first control is located, and the corresponding operation on the first control is executed. The application identifier can be the unique package name of the first application during the operation. The page identifier can be the active class name of the page component when it is in the foreground. The control identifier can be the resource ID of the view control in the layout file. Together, these ensure the lossless transfer and accurate reproduction of the operation target across devices.

[0046] For example, when the first input is an accessibility request for a login button, the generated application information might include the social application's package name (com.example.social), the current login page's class name (LoginActivity), and the login button's resource ID (button_login). The second electronic device uses this information to locate and manipulate the button locally, and the returned response information is specific to that button. The first electronic device then uses this information to accurately locate the button corresponding to `button_login` on the social application's login page and performs a simulated click.

[0047] With lightweight identification information, precise operation injection can be completed locally on the first electronic device, which significantly reduces communication overhead and further strengthens privacy protection, because the assisting party does not need to see the actual interface content on the first electronic device from beginning to end, but only operates its local copy of the corresponding application.

[0048] In one possible embodiment, the operation response information is an operation information linked list, which is a data structure consisting of multiple nodes recorded in the order in which the operations occur. Each node is associated with at least one control identifier and an operation event on the control indicated by the control identifier. Step 140 may specifically include the following steps: The operation events associated with each node are executed sequentially according to the order in which the operations occur in the operation information chain.

[0049] An operation information linked list is a data structure that records operations in the actual order they occur, consisting of multiple sequentially linked nodes. Each node is associated with at least two types of key information: a control identifier and a specific operation event for the control indicated by the control identifier. The control identifier uniquely identifies an element on the interface, while the operation event defines the interactive action applied to the element, such as clicking, long-pressing, or swiping.

[0050] The first electronic device first parses the received operation response information and extracts an operation information linked list. Following the order of the nodes in the linked list, i.e., the chronological order in which the operations occurred, it sequentially reads and executes the specific operation event associated with each node.

[0051] By using a linked list data structure to serialize complex operation flows, the timing and atomicity of multiple auxiliary operation instructions are ensured. The specific form of the control identifier in each node can be a unique resource ID of the control in the application, or its hierarchical path index in the view tree. The operation event can be a type of standard input event, such as a touch event containing coordinates and action type, or an input event containing specific text content.

[0052] For example, an action information list might contain two nodes: the first node is associated with a control with resource ID "button_next" and a click event; the second node is associated with a control with resource ID "checkbox_agree" and a click event. During execution, a click on the "next" button will be simulated first, followed by a click on the "agree" checkbox. As another example, a node in another action list might be associated with a control at view path 0 / 1 / 2 and an event for inputting the text "Hello," in which case a text input operation will be performed on this control.

[0053] By parsing and sequentially executing a linked list of operation information, accurate and reliable reproduction of complex remote operation processes is achieved. The linked list structure ensures that multiple operation instructions are processed as an ordered whole, avoiding operational sequence disorder caused by network transmission or processing timing issues, thus ensuring the correctness of the auxiliary logic. Simultaneously, this structured instruction set is very lightweight and has high transmission efficiency. Furthermore, because it describes operation intent information rather than screen pixels, it further avoids leakage of the primary electronic device's interface content, enhancing privacy and security while achieving efficient assistance.

[0054] In one possible embodiment, the operation request information may also include the interface content of the first application, and before step 120, the following steps may also be included: Retrieve the list of authorized applications, which includes application identifiers authorized for display across devices; If the authorized application list includes the application identifier information of the first application, an operation request information is generated based on the application information and interface content of the first application.

[0055] The operation request information may also include the current interface content of the first application, such as a screenshot or view hierarchy snapshot. Before executing step 120, a judgment process can also be performed. Specifically, a pre-set list of authorized applications will be obtained. This list is specifically used to record the identification information of applications that the user has authorized to display their interface content across devices to a second electronic device. When it is determined that the application identification information of the first application is included in the list of authorized applications, it means that the first application has been authorized. Based on the application information and interface content of the first application, the operation request information is generated.

[0056] A whitelist-based authorization mechanism is introduced to control the sensitive operation of transmitting application interface content between devices. Whether interface content is included depends on whether the target application is pre-existing in a trusted list, enabling fine-grained management of transmission permissions. The authorized application list can be a user-configured configuration file stored locally on the device, listing the application package names that are allowed to share the screen. The interface content can be a real-time screenshot of the current application window or a snapshot of the view structure generated by the view renderer. For example, the user might only authorize a shopping app and a map app in the list. When the first input occurs within the authorized shopping app, a screenshot of the current product details page is captured and packaged with the application information before being sent.

[0057] By adding an authorization verification step before step 120, users are given the ability to control their privacy boundaries. For auxiliary scenarios where viewing the interface is unnecessary or prohibited, only lightweight application information is transmitted; interface content is only transmitted for reference when the user explicitly authorizes it and it is indeed necessary. While meeting the auxiliary needs of complex operations that require visual reference, the explicit authorization list mechanism eliminates the risk of unauthorized application interface content being accidentally or maliciously transmitted, making privacy protection more proactive and controllable.

[0058] In one possible embodiment, step 140 may specifically include the following steps: Based on the operation response information, output a safety execution confirmation message; In response to the confirmation prompt for security execution, the first application is operated based on the operation response information.

[0059] Based on the received operation response information, a security execution confirmation prompt is generated and output to inform the user that the operation suggested by the auxiliary party is about to be executed. The system will wait for and respond to the user's confirmation operation in response to the prompt. Only when the confirmation operation occurs will the corresponding operation on the first application be triggered.

[0060] The specific form of the output confirmation message can be varied, such as displaying a modal dialog box with an operation description in the center of the screen, or sending an interactive notification via the notification bar. The confirmation action can also take different forms, such as the user clicking the "OK" or "Continue" button on the prompt box, or the user pressing a specific combination of physical keys.

[0061] For example, when the operation response indicates that the "Pay" button is about to be clicked, a dialog box may pop up saying, "The 'Confirm Payment' operation is about to be performed. Do you want to continue?" The user must click the "Yes" button in the dialog box for the payment operation to be simulated.

[0062] By responding to the confirmation prompt for security execution and operating the first application, the risks that may arise from the auxiliary party's misoperation or malicious commands are effectively prevented. This ensures that any changes to the local application must be explicitly authorized by the device owner, thus achieving a crucial balance between convenient cross-device assistance and absolute local control, thereby improving reliability and user trust.

[0063] In one possible embodiment, the operation request information further includes an application identity signature; the application identity signature is the same identity information shared by a first application on the first electronic device and a second application on the second electronic device, wherein the first application and the second application are the same application.

[0064] Application identity signature is an encrypted, globally unique identifier that is the same identity information held and identified by a first application on a first electronic device and a second application on a second electronic device. Here, the first application and the second application are the same application, that is, they have the same package name and source.

[0065] By distributing and maintaining a shared, trusted, encrypted identity credential across multiple trusted devices for the same application, a trusted collaborative relationship is established at the application level, rather than just the device level. This requires application developers or app stores to generate and securely synchronize a unique signing key for the same application instance under the same user account used across devices during application installation or user login. Cryptographic techniques can be used to ensure the uniqueness and tamper-proof nature of the signature, which can then be stored in an application sandbox or a secure system area.

[0066] For example, if a user logs into a shopping app using the same account on both their phone and tablet, the app's backend service can generate and synchronize the same app identity signature for the app instances on both devices. Another example is a family-shared note-taking app; after being installed on different devices belonging to family members, it can obtain a shared family app identity signature through family group authentication.

[0067] When the first electronic device generates the operation request information in step 120, it encapsulates the application identity signature along with it. After receiving the request in step 210, the second electronic device first verifies whether the same application running locally holds an application identity signature that is completely identical to that in the request before performing any local simulation operation. If the signatures match, it means that the applications on both devices are in the same trusted domain, and auxiliary operations can be performed based on a higher level of trust.

[0068] By introducing and verifying shared application identity signatures, the operation response information generated by the second electronic device can be executed more directly by the first electronic device once the trusted relationship between the two applications is proven through the shared signature.

[0069] In the embodiments of this application, a first input to a first application is received through an application-assisted operation service. In response to the first input, an operation request message is sent to a second electronic device through the application-assisted operation service. The operation request message includes at least application information of the first application, thereby precisely limiting the scope of assistance to a specific application, significantly reducing data transmission volume and avoiding unnecessary permission exposure. Operation response information sent by the second electronic device is received through the application-assisted operation service. This operation response information is generated by the second electronic device after receiving the operation request message, running the page corresponding to the first application locally, and responding to the assisted operation on the page. This eliminates the need for the second electronic device to directly access or interfere with the actual operating state of the first device, thus isolating privacy risks. By using the application-assisted operation service to operate the first application based on the operation response information, effective cross-device operation assistance is achieved while reducing the risk of privacy leakage and improving the security and controllability of the assistance process.

[0070] like Figure 2 As shown, the system's layered architecture for cross-device assisted operation is illustrated. Its core process begins at the application layer and extends to the kernel layer. When a user triggers a specific gesture on the application layer interface of the first electronic device, the current foreground application obtains context data such as its own package name, active page information, and the unique identifier of the target control, and submits this information to the framework layer. The framework layer is the central hub of this solution. Its application assisted operation service receives and processes the aforementioned requests. This service queries the authorized application list to confirm whether the current application is allowed to be assisted, reads the identifier of the bound trusted second electronic device from the secure storage area maintained by the same framework layer, and assembles the application information into structured operation request information.

[0071] The driver layer provides hardware support for this request, sending the request information to the second electronic device via a secure communication link established by the network driver. On the second electronic device side, the driver layer receives the data and uploads it to its framework layer's application-assisted operation service. This service parses the request, launches the same application locally based on the application identifier, and navigates to the corresponding page, thus completely recreating the required operational environment locally. When the assistant performs simulated operations on the local page, the application-assisted operation service captures these interaction events and converts them into abstract operation response information. This response information is then transmitted back to the first electronic device via the network link of the driver layer. Upon receiving the response, the application-assisted operation service in the first electronic device's framework layer can initiate a user security confirmation. After confirmation, it injects the encapsulated operation instructions through the system input mechanism, completing the simulated operation of the target control on the application layer interface that initially triggered the request.

[0072] Throughout the process, the kernel layer provides fundamental process, memory, and file system support for all steps, ensuring stable and secure execution. This architecture achieves precise application-level assistance through centralized coordination of core services at the framework layer and reliable communication at the driver layer. Furthermore, privacy protection mechanisms are embedded at the data source, transmission process, and final execution stage, enabling secure remote assistance without requiring global control authorization or full-screen transmission.

[0073] Figure 3 This is a flowchart of an application operation method provided in an embodiment of this application.

[0074] like Figure 3 As shown, the application operation method may include steps 310-340, and is applied to a second electronic device. The operating system framework layer of the second electronic device has an application-assisted operation service deployed, as detailed below: Step 310: Receive auxiliary request information sent by the first electronic device through the application auxiliary operation service. The operation request information includes at least: application information of the first application. Step 320: Run the page corresponding to the first application locally through the application assistance service; Step 330: In response to the auxiliary operation on the page, generate operation response information by applying the auxiliary operation service; Step 340: Send operation response information to the first electronic device through the application auxiliary operation service.

[0075] The operation request information includes at least application information for the first application used to locate the application's status. Running the corresponding page locally refers to the process by which the second electronic device, based on the received application information, launches and presents the same application and interface as on the first electronic device. Assistive operations are simulated interactions performed by an assistant on the local page of the second electronic device, intended to guide or verify operations. The generated operation response information is feedback data encapsulating these simulated operation instructions.

[0076] In step 310, the second electronic device, acting as a service listener, receives structured request data packets from the first electronic device via an inter-device communication protocol. For example, the second electronic device receives a data packet containing the target application package name "com.example.browser" via a Wi-Fi Direct channel or an encrypted channel via the cloud. Alternatively, the received data packet might be a JSON object conforming to a specific protocol, encapsulating application and page identifiers.

[0077] The application-assisted operation service, acting as a resident network server on the second electronic device, is responsible for continuously monitoring specific secure communication ports or channels of the paired first electronic device. Upon receiving an encrypted auxiliary request data packet, it first performs a security verification process, such as verifying the digital signature of the data packet to confirm its origin from the trusted first electronic device, and then decrypting the data content. Subsequently, the data packet is parsed to extract core operation request information, particularly application information of the first application, such as packet name and page identifier. This step securely and accurately converts external network data into structured operation instruction requests that the internal system can process.

[0078] In step 320, the second electronic device parses the key identifier in the operation request information and uses its own capabilities to launch the same application, while navigating to the corresponding interface state to recreate the operation scenario requiring assistance on the first electronic device. All operations are completed in the local virtual environment of the assisting device. For example, after parsing the application identifier as "com.example.settings", the settings application is launched on the second electronic device, and further, based on the page identifier "WiFiSettingsActivity", it jumps to the Wi-Fi settings page. For example, if the request information also contains a control identifier, after launching the application, the focus can be automatically positioned or highlighted for that specific control.

[0079] The application-assisted operation service calls the system's activity management service to launch or switch to the same application as the first application within the application sandbox on the second electronic device, and precisely navigates to the corresponding interface state based on the page identifier. For example, if the request information indicates "transfer confirmation page of a bank application," the service launches the bank application locally and jumps to the transfer confirmation interface. This process is completely independent, does not involve any reading or modification of the actual application state of the first electronic device, and only creates an isolated operating environment locally for simulation and demonstration.

[0080] In step 330, all interaction events on the page reconstructed by the assistant on the local machine are listened to and captured, and these events are transformed into a set of serializable operation instructions independent of the interface rendering. For example, if the assistant clicks the "Submit" button on the local page, the control identifier and event type corresponding to this click event are recorded, and an operation instruction is generated accordingly. For example, if the assistant performs a swipe-down gesture from the top of the screen, the starting coordinates, offset, and action of this gesture are recorded, and it is transformed into a swipe event instruction.

[0081] When an assistant performs assisted operations on a page locally restored on a second electronic device, the assistance service acts as a listener for advanced input events, analyzing the semantics of the interaction events. For example, it identifies a click event acting on a button with the ID "confirm_button," and then abstracts this specific interaction into a structured instruction: "Execute a click event on the control 'confirm_button'." For complex operation sequences, the service records them sequentially and constructs a data structure such as an operation linked list. It extracts the specific operations of the graphical interface into serializable logical instructions that are independent of specific screen pixels, generating operation response information.

[0082] In step 340, the second electronic device sends a sequence of instructions generated that describes the operational intent rather than the screen content back to the first electronic device via a reverse communication link. For example, one or more operation instructions generated in step 230 are encapsulated into specific data packets and then sent back via an established P2P connection.

[0083] The application-assisted operation service is responsible for securely encapsulating data containing pure operational logic, such as re-encrypting and signing it, to ensure the confidentiality, integrity, and non-repudiation of instructions during transmission. Subsequently, it accurately sends the encapsulated operation response information back to the peer service endpoint of the first electronic device via the system network service.

[0084] In one possible embodiment, the operation response information is an operation information linked list; step 330 may specifically include the following steps: By applying auxiliary operation services, an operation information linked list is generated according to the order in which the operations occur. The operation information linked list is a data structure consisting of multiple nodes that are recorded in the order in which the operations occur. Each node is associated with at least one control identifier and one operation event on the control indicated by the control identifier.

[0085] An operation information linked list is a data structure that records operations sequentially according to their actual occurrence time. It consists of multiple nodes linked together in sequence. Each node, as the basic unit of the linked list, is associated with at least two key information items: a control identifier, used to uniquely identify a specific interactive element on the interface; and an operation event, used to describe the specific interactive action performed on the control pointed to by the aforementioned control identifier.

[0086] When an assistant performs a series of auxiliary operations on the corresponding page running locally on the second electronic device, the application-assisted operation service deployed in the framework layer of the second electronic device initiates a dynamic capture and construction process. This service creates a new node for each valid interaction, following the order in which the operations occur. For each interaction, the application-assisted operation service first determines its target, that is, it parses the unique control identifier corresponding to the operated control, such as the resource ID of the control in the application view tree or its absolute path index.

[0087] By analyzing the type of this interaction using the application's auxiliary operation service, it abstracts it into a standard operation event. The service encapsulates this control identifier and operation event as a pair of related information into a newly created node, and links this node to the end of the operation information chain being built in chronological order. When a series of auxiliary operations are completed, a complete operation information chain that records all operation steps and their strict timing is generated.

[0088] For example, if an assistant clicks the "Next" button, enters a "Username" in the text box, and then clicks the "Submit" button, the application's accessibility service will generate three nodes in sequence: the first node is associated with the resource ID of the "Next" button and a click event; the second node is associated with the resource ID of the text box and an event indicating the entered text "Username"; and the third node is associated with the resource ID of the "Submit" button and a click event. As another example, if an assistant performs a swipe gesture from left to right on the screen to switch tabs, the service will generate a node associated with the identifier of the container control carrying the swipe gesture and an operation event describing the swipe direction and distance.

[0089] The linked list data structure inherently guarantees the strict timing of multiple operation instructions, which is crucial for complex tasks that need to be executed in a specific order, avoiding operational errors caused by network transmission or processing delays. Each node in the linked list is directly associated with an abstract control identifier and operation event, rather than the original pixel coordinates or image stream, making the instruction set extremely lightweight and significantly reducing network transmission overhead. This abstract description completely strips away the specific visual content of the interface, achieving accurate operation reproduction while completely avoiding the transmission of any interface screenshots or private content from the first electronic device to the second electronic device, thus strengthening privacy and security at the information encoding level. The generated operation information linked list provides the first electronic device with a precise and reliable operational basis, ensuring the complete and accurate transmission and reproduction of auxiliary intentions.

[0090] In the embodiments of this application, an application-assisted operation service receives operation request information sent by a first electronic device, which includes at least the application information of the first application, thus precisely limiting the scope of assistance to a specific application. By running the page corresponding to the first application locally through the application-assisted operation service, all subsequent interactions are conducted entirely within the environment of the second electronic device itself, isolating direct access to the real data and state of the first electronic device and preventing privacy leaks. In response to the assisted operation on the local page, the application-assisted operation service generates operation response information and sends this information to the first electronic device, thereby feeding back the operation intent without sensitive context information to the initiator. This effectively supports cross-device assistance functions without requiring the acquisition of control of the first device or sensitive data.

[0091] The application operation method provided in this application embodiment can be executed by an application operation device. This application embodiment uses an application operation device executing the application operation method as an example to illustrate the application operation device provided in this application embodiment.

[0092] Figure 4 This is a block diagram of an application operation device provided in an embodiment of this application. The device 400 includes: The first input module 410 is used to receive a first input to the first application through the application auxiliary operation service; The first sending module 420 is used to send operation request information to the second electronic device through an application-assisted operation service in response to the first input. The operation request information includes at least: application information of the first application. The first receiving module 430 is used to receive operation response information sent by the second electronic device through the application auxiliary operation service. The operation response information is generated by the second electronic device after receiving the operation request information, running the page corresponding to the first application locally and responding to the auxiliary operation on the page. The operation module 440 is used to operate the first application based on the operation response information through the application-assisted operation service.

[0093] In one possible embodiment, the operating system framework layer of the first electronic device also deploys a permission management service, and the device 400 further includes: The module is used to add device-level authorization for at least one data permission of the first application to the second electronic device based on the device interconnection relationship established between the first electronic device and the second electronic device through the permission management service. Among them, device-level authorization is used to authorize a second electronic device to access data in the first application corresponding to the authorized data permissions in order to perform auxiliary operations.

[0094] In one possible embodiment, the first transmitting module 420 is specifically used for: In response to the first input, obtain the initial application information of the first application; The initial application information is de-privacy processed to obtain the application information of the first application; the de-privacy processing includes: hiding, obfuscation or replacement processing; Generate operation request information based on the application information of the first application; Send an operation request message to the second electronic device.

[0095] In one possible embodiment, the application information of the first application includes: The application identifier of the first application, the page identifier of the first page currently displayed by the first application, and the control identifier of the first control for the first input indication; Operation module 440 is specifically used for: Based on the operation response information, the first control is operated on the first page of the first application.

[0096] In one possible embodiment, the operation response information is an operation information linked list, which is a data structure consisting of multiple nodes recorded in the order in which the operations occur. Each node is associated with at least one control identifier and an operation event on the control indicated by the control identifier. Operation module 440 is specifically used for: The operation events associated with each node are executed sequentially according to the order in which the operations occur in the operation information chain.

[0097] In one possible embodiment, the device 400 includes: The acquisition module is used to acquire a list of authorized applications, which includes the identification information of applications authorized for display across devices. The generation module is used to generate operation request information based on the application information and interface content of the first application, provided that the authorized application list includes the application identifier information of the first application.

[0098] In one possible embodiment, the operation module 440 is specifically used for: Based on the operation response information, output a safety execution confirmation message; In response to the confirmation prompt for security execution, the first application is operated based on the operation response information.

[0099] In one possible embodiment, the operation request information further includes an application identity signature; the application identity signature is the same identity information shared by the first application on the first electronic device and the second application on the second electronic device, and the first application and the second application are the same application.

[0100] In the embodiments of this application, a first input to a first application is received through an application-assisted operation service. In response to the first input, an operation request message is sent to a second electronic device through the application-assisted operation service. The operation request message includes at least application information of the first application, thereby precisely limiting the scope of assistance to a specific application, significantly reducing data transmission volume and avoiding unnecessary permission exposure. Operation response information sent by the second electronic device is received through the application-assisted operation service. This operation response information is generated by the second electronic device after receiving the operation request message, running the page corresponding to the first application locally, and responding to the assisted operation on the page. This eliminates the need for the second electronic device to directly access or interfere with the actual operating state of the first device, thus isolating privacy risks. By using the application-assisted operation service to operate the first application based on the operation response information, effective cross-device operation assistance is achieved while reducing the risk of privacy leakage and improving the security and controllability of the assistance process.

[0101] Figure 5 This is a block diagram of an application operation device provided in an embodiment of this application. The device 500 includes: The second receiving module 510 is used to receive auxiliary request information sent by the first electronic device through the application auxiliary operation service. The operation request information includes at least: application information of the first application. The running module 520 is used to run the page corresponding to the first application locally through the application auxiliary operation service; The generation module 530 is used to respond to auxiliary operations on the page and generate operation response information by applying auxiliary operation services; The second sending module 540 is used to send operation response information to the first electronic device through an application-assisted operation service.

[0102] In one possible embodiment, the operation response information is an operation information linked list; Module 530 is generated, specifically for: By applying auxiliary operation services, an operation information linked list is generated according to the order in which the operations occur. The operation information linked list is a data structure consisting of multiple nodes that are recorded in the order in which the operations occur. Each node is associated with at least one control identifier and one operation event on the control indicated by the control identifier. In the embodiments of this application, an application-assisted operation service receives operation request information sent by a first electronic device, which includes at least the application information of the first application, thus precisely limiting the scope of assistance to a specific application. By running a page corresponding to the first application locally through the application-assisted operation service, all subsequent interactions are conducted entirely within the environment of the second electronic device itself, isolating direct access to the real data and state of the first electronic device and preventing privacy leaks. In response to an assisted operation on this local page, an operation response information is generated through the application-assisted operation service and sent to the first electronic device, thereby feeding back the operation intent without sensitive context information to the initiator. This effectively supports cross-device assistance functions without requiring the acquisition of control of the first device or sensitive data.

[0103] The application operating device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0104] The application operation device in this application embodiment can be a device with an action system. The action system can be an Android action system, an iOS action system, or other possible action systems, and this application embodiment does not specifically limit it.

[0105] The application operation device provided in this application embodiment can implement the various processes implemented in the above method embodiment. To avoid repetition, it will not be described again here.

[0106] Optionally, such as Figure 6 As shown, this application embodiment also provides an electronic device 610, including a processor 611, a memory 612, and a program or instructions stored in the memory 612 and executable on the processor 611. When the program or instructions are executed by the processor 611, they implement the various steps of any of the above application operation method embodiments and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0107] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0108] Figure 7 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application. The electronic device 700 includes, but is not limited to, components such as: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.

[0109] Those skilled in the art will understand that the electronic device 700 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 710 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 7 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0110] The processor 710 is used to receive a first input to the first application through an application-assisted operation service; The processor 710 is also configured to, in response to the first input, send operation request information to the second electronic device via an application-assisted operation service, the operation request information including at least: application information of the first application; The processor 710 is also used to receive operation response information sent by the second electronic device through an application-assisted operation service. The operation response information is generated by the second electronic device after receiving the operation request information, running the page corresponding to the first application locally, and responding to the auxiliary operation on the page. The processor 710 is also used to operate the first application based on operation response information through an application-assisted operation service.

[0111] Optionally, the operating system framework layer of the first electronic device also deploys a permission management service. The processor 710 is also used to add device-level authorization for at least one data permission of the first application to the second electronic device based on the device interconnection relationship established between the first electronic device and the second electronic device through the permission management service. Among them, device-level authorization is used to authorize a second electronic device to access data in the first application corresponding to the authorized data permissions in order to perform auxiliary operations.

[0112] Optionally, the processor 710 is also configured to, in response to the first input, obtain initial application information of the first application; The processor 710 is also used to perform de-privacy processing on the initial application information to obtain the application information of the first application; wherein, the de-privacy processing includes: hiding processing, obfuscation processing or replacement processing; The processor 710 is also used to generate operation request information based on the application information of the first application; The processor 710 is also used to send operation request information to the second electronic device.

[0113] Optionally, the application information of the first application includes: The application identifier of the first application, the page identifier of the first page currently displayed by the first application, and the control identifier of the first control for the first input indication; The processor 710 is also used to operate the first control on the first page of the first application based on the operation response information.

[0114] Optionally, the operation response information is an operation information linked list. The operation information linked list is a data structure consisting of multiple nodes recorded in the order in which the operations occur. Each node is associated with at least one control identifier and one operation event on the control indicated by the control identifier. The processor 710 is also used to execute the operation events associated with each node in sequence according to the order in which the operations occur in the operation information chain.

[0115] Optionally, the processor 710 is also configured to obtain a list of authorized applications, which includes application identification information authorized for display across devices; The processor 710 is also used to generate operation request information based on the application information of the first application and the interface content of the first application when the authorized application list includes the application identifier information of the first application.

[0116] Optionally, the processor 710 is also configured to output a safety execution confirmation message based on the operation response information; The processor 710 is also configured to perform an operation on the first application based on the operation response information in response to a confirmation operation for a security execution confirmation prompt.

[0117] Optionally, the operation request information may also include an application identity signature; the application identity signature is the same identity information shared by the first application on the first electronic device and the second application on the second electronic device, and the first application and the second application are the same application.

[0118] In the embodiments of this application, a first input to a first application is received through an application-assisted operation service. In response to the first input, an operation request message is sent to a second electronic device through the application-assisted operation service. The operation request message includes at least application information of the first application, thereby precisely limiting the scope of assistance to a specific application, significantly reducing data transmission volume and avoiding unnecessary permission exposure. Operation response information sent by the second electronic device is received through the application-assisted operation service. This operation response information is generated by the second electronic device after receiving the operation request message, running the page corresponding to the first application locally, and responding to the assisted operation on the page. This eliminates the need for the second electronic device to directly access or interfere with the actual operating state of the first device, thus isolating privacy risks. By using the application-assisted operation service to operate the first application based on the operation response information, effective cross-device operation assistance is achieved while reducing the risk of privacy leakage and improving the security and controllability of the assistance process.

[0119] or, The processor 710 is configured to receive auxiliary request information sent by the first electronic device through an application-assisted operation service, wherein the operation request information includes at least: application information of the first application; The processor 710 is also used to run the page corresponding to the first application locally via the application assistance service; The processor 710 is also used to respond to auxiliary operations on the page by generating operation response information through the application auxiliary operation service; The processor 710 is also used to send operation response information to the first electronic device through application-assisted operation services.

[0120] Optionally, the operation response information is an operation information linked list; the processor 710 is also used to generate an operation information linked list in the order of operation occurrence by using an application-assisted operation service. The operation information linked list is a data structure consisting of multiple nodes recorded in the order of operation occurrence, and each node is associated with at least one control identifier and one operation event on the control indicated by the control identifier. In the embodiments of this application, an application-assisted operation service receives operation request information sent by a first electronic device, which includes at least the application information of the first application, thus precisely limiting the scope of assistance to a specific application. By running a page corresponding to the first application locally through the application-assisted operation service, all subsequent interactions are conducted entirely within the environment of the second electronic device itself, isolating direct access to the real data and state of the first electronic device and preventing privacy leaks. In response to an assisted operation on this local page, an operation response information is generated through the application-assisted operation service and sent to the first electronic device, thereby feeding back the operation intent without sensitive context information to the initiator. This effectively supports cross-device assistance functions without requiring the acquisition of control of the first device or sensitive data.

[0121] It should be understood that, in this embodiment, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042. The GPU 7041 processes image data of still images or video images obtained by an image capture device (such as a camera) in video image capture mode or image capture mode. The display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here. The memory 709 can be used to store software programs and various data, including but not limited to applications and motion systems. Processor 710 can integrate an application processor and a modem processor. The application processor mainly handles the action system, user page, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into processor 710.

[0122] The memory 709 can be used to store software programs and various data. The memory 709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 709 may include volatile memory or non-volatile memory, or it may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 709 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0123] Processor 710 may include one or more processing units; optionally, processor 710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 710.

[0124] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described application operation method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0125] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0126] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above application operation method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0127] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0128] This application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the application operation method embodiments described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0129] It should be noted that, in this document, 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 limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0130] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0131] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. An application operation method, characterized in that, Applied to a first electronic device, wherein the operating system framework layer of the first electronic device deploys application-assisted operation services, the method includes: The application-assisted operation service receives the first input to the first application. In response to the first input, the operation request information is sent to the second electronic device through the application-assisted operation service, and the operation request information includes at least: application information of the first application; The application-assisted operation service receives operation response information sent by the second electronic device. The operation response information is generated by the second electronic device after receiving the operation request information, running the page corresponding to the first application locally, and responding to the assisted operation on the page. The first application is operated based on the operation response information through the application-assisted operation service.

2. The method according to claim 1, characterized in that, The operating system framework layer of the first electronic device also deploys a permission management service. Before receiving the first input to the first application through the application-assisted operation service, the method further includes: Based on the device interconnection relationship established between the first electronic device and the second electronic device, the permission management service adds device-level authorization for the second electronic device for at least one data permission of the first application; The device-level authorization is used to authorize the second electronic device to access data in the first application corresponding to the authorized data permissions in order to perform the auxiliary operation.

3. The method according to claim 1, characterized in that, The step of sending the operation request information to the second electronic device in response to the first input includes: In response to the first input, obtain the initial application information of the first application; The initial application information is de-privacy processed to obtain the application information of the first application; wherein, the de-privacy processing includes: hiding processing, obfuscation processing, or replacement processing; The operation request information is generated based on the application information of the first application; The operation request information is sent to the second electronic device.

4. The method according to claim 1, characterized in that, The application information of the first application includes: The application identifier of the first application, the page identifier of the first page currently displayed by the first application, and the control identifier of the first control of the first input indication; The operation on the first application based on the operation response information includes: Based on the operation response information, the first control is operated on the first page of the first application.

5. The method according to claim 1, characterized in that, The operation response information is an operation information linked list, which is a data structure consisting of multiple nodes recorded in the order of operation occurrence. Each node is associated with at least one control identifier and one operation event on the control indicated by the control identifier. The operation on the first application based on the operation response information includes: The operation events associated with each node are executed sequentially according to the order in which the operations occur in the operation information chain.

6. The method according to claim 1, characterized in that, The operation request information also includes the interface content of the first application. Before sending the operation request information to the second electronic device in response to the first input, the method further includes: Obtain a list of authorized applications, which includes application identifiers authorized for display across devices; If the authorized application list includes the application identifier information of the first application, the operation request information is generated based on the application information of the first application and the interface content of the first application.

7. The method according to claim 1, characterized in that, The operation on the first application based on the operation response information includes: Based on the operation response information, output a security execution confirmation message; In response to the confirmation operation of the security execution confirmation prompt, the first application is operated based on the operation response information.

8. The method according to claim 1, characterized in that, The operation request information also includes an application identity signature; the application identity signature is the same identity information shared by the first application on the first electronic device and the second application on the second electronic device, and the first application and the second application are the same application.

9. An application operation method, characterized in that, Applied to a second electronic device, wherein the operating system framework layer of the second electronic device has application-assisted operation services deployed thereon, the method includes: The application-assisted operation service receives assistance request information sent by the first electronic device, wherein the operation request information includes at least: application information of the first application; The application-assisted operation service is used to run the page corresponding to the first application locally; In response to auxiliary operations on the page, operation response information is generated through the application auxiliary operation service; The operation response information is sent to the first electronic device through the application-assisted operation service.

10. The method according to claim 9, characterized in that, The operation response information is an operation information linked list; The response to an auxiliary operation on the page, generating operation response information through the application auxiliary operation service, includes: The application-assisted operation service generates an operation information linked list in the order of operation occurrence. The operation information linked list is a data structure consisting of multiple nodes recorded in the order of operation occurrence. Each node is associated with at least one control identifier and one operation event on the control indicated by the control identifier.

11. An application operating device, characterized in that, Applied to a first electronic device, wherein the operating system framework layer of the first electronic device deploys application-assisted operation services, the device includes: The first input module is used to receive a first input to the first application through the application-assisted operation service; A first sending module is configured to, in response to the first input, send the operation request information to a second electronic device through the application-assisted operation service, wherein the operation request information includes at least: application information of the first application; The first receiving module is used to receive operation response information sent by the second electronic device through the application auxiliary operation service. The operation response information is generated by the second electronic device after receiving the operation request information, running the page corresponding to the first application locally and responding to the auxiliary operation on the page. The operation module is used to operate the first application based on the operation response information through the application-assisted operation service.

12. An application operating device, characterized in that, An application for a second electronic device, wherein the operating system framework layer of the second electronic device is deployed with application-assisted operation services, the device comprising: The second receiving module is used to receive auxiliary request information sent by the first electronic device through the application auxiliary operation service, wherein the operation request information includes at least: application information of the first application; The running module is used to run the page corresponding to the first application locally through the application auxiliary operation service; A generation module is used to generate operation response information through the application auxiliary operation service in response to auxiliary operations on the page. The second sending module is used to send the operation response information to the first electronic device through the application-assisted operation service.

13. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the application operation method as described in any one of claims 1-10.

Images