Method and system for temporary cross-client data synchronization of same account

Abstract

Embodiments of the present specification relate to the field of information technology, in particular to a same-account temporary cross-client data synchronization method and system. The method comprises: establishing a communication connection with a commonly used device; receiving a cross-client request, the cross-client request comprising a preset account credential and a target application; creating a cloned application of the target application, setting the login account of the cloned application as the user account; listening to data requests generated by the cloned application; when a data request generated by the cloned application is listened to, sending the preset account credential and the data request to the commonly used device through the communication connection, and receiving the response data of the commonly used device to the data request after verifying the account credential, and submitting the response data to the cloned application as the result of the data request; when an end instruction is received, destroying the cloned application and the data in the data directory thereof.

Description

Technical Field

[0001] Several embodiments of this specification relate to the field of information technology, specifically to a method and system for temporary cross-client data synchronization under the same account. Background Technology

[0002] With the rapid development of mobile internet technology and the widespread adoption of smart devices, users are increasingly reliant on various applications (Apps) for information access, social communication, online shopping, mobile payments, and office collaboration in their daily lives and work. Users typically use the same application account on multiple devices, such as logging into some applications on their personal mobile phones (their primary devices) for extended periods, and wanting to conveniently access some of the account's functions on temporarily borrowed devices (such as public computers, other people's mobile phones, or temporary work machines).

[0003] Existing technologies have proposed application cloning or multi-instance functionality, allowing multiple instances of the same application to run on the same device. However, application cloning technology primarily focuses on isolating multiple accounts on the same device and does not meet the need to run or log in to accounts on temporary devices. Therefore, there is an urgent need to research technologies that can enable the secure temporary use of user accounts on temporary devices while ensuring user experience. Summary of the Invention

[0004] This specification describes a method and system for temporary cross-client data synchronization under the same account through several embodiments.

[0005] Firstly, this specification provides a method for temporary cross-client data synchronization under the same account, running on a temporary device, including the following steps:

[0006] Establish a communication connection with a commonly used device, which is a device that has been logged into with a user account;

[0007] Receive cross-client requests, the cross-client requests including preset account credentials and target applications;

[0008] Create a clone application of the target application. The clone application has an independent data directory, UID, and running space. Set the login account of the clone application to the user account.

[0009] Listen for data requests generated by the cloned application, including data read requests, data write requests, and network data requests;

[0010] When a data request is detected by the cloned application, the preset account credentials and the data request are sent to the primary device through the communication connection, and the response data of the primary device to the data request after verifying the account credentials is received. The response data is then submitted to the cloned application as the result of the data request.

[0011] When a termination command is received, the cloned application and the data in its data directory are destroyed.

[0012] Secondly, embodiments of this specification provide a temporary cross-client data synchronization system for the same account, running on a temporary device, including:

[0013] A communication module that establishes a communication connection with commonly used devices, wherein the commonly used devices are devices that have been logged into with a user account;

[0014] The triggering module receives cross-client requests, which include preset account credentials and target applications;

[0015] The creation module creates a clone application of the target application. The clone application has an independent data directory, UID, and running space. The login account of the clone application is set to the user account.

[0016] The monitoring module monitors the data requests generated by the cloned application, including data read requests, data write requests, and network data requests.

[0017] The synchronization module, when it detects that the cloned application generates a data request, sends the preset account credentials and the data request to the primary device through the communication connection, and receives the response data of the primary device to the data request after verifying the account credentials, and submits the response data as the result of the data request to the cloned application.

[0018] When a termination command is received, the cloned application and the data in its data directory are destroyed.

[0019] Thirdly, embodiments of this specification provide an electronic device, including a processor and a memory;

[0020] The processor is connected to the memory;

[0021] The memory is used to store executable program code;

[0022] The processor runs a program corresponding to the executable program code stored in the memory to perform the method described in any of the above aspects.

[0023] Fourthly, embodiments of this specification provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the methods described in any of the above aspects.

[0024] Fifthly, embodiments of this specification provide a computer program product, including a computer program that, when executed by a processor, implements the methods described in any of the above aspects.

[0025] The beneficial effects of the technical solutions provided in some embodiments of this specification include at least the following:

[0026] In several embodiments of this specification, the provided temporary cross-client data synchronization method and system for the same account retains the data on the logged-in primary device through actual data processing. The temporary device serves only as the front-end interface and data display terminal for user operations, avoiding the input, transmission, and storage of sensitive account information on the temporary device. All read and write operations for data processing are performed by the primary device. The temporary device does not generate or only generates a small amount of temporary cached data locally, which is destroyed upon completion, preventing the residue and leakage of user privacy data on the temporary device. Users can quickly and conveniently access application services they have logged into on their primary device without needing to go through a complex login verification process on the temporary device, improving usability while ensuring data security.

[0027] Other features and advantages of various embodiments of this specification will be further revealed in the following detailed description and accompanying drawings. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the embodiments of this specification, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 This is a diagram illustrating temporary cross-client data synchronization for the same account provided in this manual.

[0030] Figure 2 This is a flowchart illustrating the temporary cross-client data synchronization method for the same account provided in this manual.

[0031] Figure 3 This is a schematic diagram of the monitoring data request provided in this manual.

[0032] Figure 4 This is a schematic diagram of a temporary cross-client data synchronization system for the same account provided in this manual.

[0033] Figure 5 This is a schematic diagram of the electronic device provided in this manual. Detailed Implementation

[0034] The technical solutions of the embodiments of this specification will be explained and described below with reference to the accompanying drawings. However, the following embodiments are only preferred embodiments of this specification and not all of them. Other embodiments obtained by those skilled in the art based on the embodiments in the implementation methods without creative effort are all within the protection scope of this specification.

[0035] The terms "first," "second," "third," etc., in the description, claims, and accompanying drawings are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus.

[0036] In the following description, terms such as “inner,” “outer,” “upper,” “lower,” “left,” and “right” are used only to facilitate the description of the embodiments and to simplify the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this specification.

[0037] All data involved in this application are information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0038] Before introducing the technical solutions described in this manual, the application scenarios and related technologies of the technical solutions will be introduced.

[0039] Cross-client data synchronization refers to the technology that maintains the consistency of core data state for the same application or service running on multiple different user terminal devices (i.e., "clients," such as mobile phones, tablets, computers, smartwatches, etc.). It breaks down information barriers between devices, allowing users to enjoy a consistent and seamless user experience regardless of which device they use. When a user modifies data on one device (such as creating a new note, sending a message, or updating a shopping cart), these changes are automatically and reliably propagated to the user's other logged-in devices through a specific mechanism, ensuring data consistency across all devices. This frees users from the limitations of a single device, allowing them to access the latest information anytime, anywhere, improving operational efficiency and convenience.

[0040] With the development of network technology and the abundance and widespread use of smart devices, users have also developed a need for temporary cross-device access. Temporary cross-device access refers to a user's secure and convenient access to application services already logged into on their primary device (such as a personal mobile phone) from a non-personally owned, temporarily used device (such as a public computer, someone else's mobile phone, or a shared tablet), without leaving any trace after the session ends. (See attached image.) Figure 1 As shown. This technology differs from existing multi-device synchronization technologies, emphasizing temporariness, security, and seamlessness. Temporary cross-device technology addresses users' temporary usage needs in specific scenarios, eliminating the need for cumbersome login processes on temporary devices 30 or concerns about subsequent cleanup, allowing for quick and smooth use of core personal application functions. It provides technical solutions for scenarios such as shared office spaces, public information inquiries, and device borrowing.

[0041] This manual first provides a temporary cross-client data synchronization method for the same account, running on a temporary device 30. Please refer to the appendix. Figure 2 The steps include:

[0042] Step S1) Establish a communication connection with the primary device 20, which is a device already logged into with a user account. First, a secure communication connection needs to be established between the temporary device 30 (exemplary, such as a borrowed tablet) and the user's personal primary device 20 (e.g., a mobile phone already logged into their instant messaging application). This communication connection is used to carry out subsequent credential verification, data request forwarding, and result feedback. As an example, the communication connection method can be Wi-Fi Direct over the same local area network, Bluetooth pairing, or an encrypted tunnel over the Internet. The primary device 20 is a device already logged into with a user account according to the application settings; its logged-in status should have been achieved before this method is executed.

[0043] For example, User A is at a friend's house and wants to use Friend B's tablet to reply to an important instant messaging message. He first activates the "Temporary Access" function on his own phone (primary device 20) and generates a pairing code. Then, he enters this pairing code on Friend B's tablet (temporary device 30). The two devices establish an encrypted connection over the internet, and pairing is successful. After generating the pairing code, User A's phone can be used for other purposes, but these other uses exclude User A's own use. For example, if someone else takes User A's phone to view the phone's photo album, making it temporarily unusable for User A, he needs to borrow Friend B's tablet to temporarily reply to the instant messaging message.

[0044] Step S2) Receive a cross-client request, which includes a preset account credential and target application 32.

[0045] Methods for presetting account credentials include:

[0046] Set up account credentials based on one or more of the following: device owner information, user account information of target application 32, or time-limited credentials generated by the commonly used device 20.

[0047] The "temporary cross-client" process is initiated on temporary device 30. The cross-client request specifies the application the user wants to access (i.e., target application 32) and carries account credentials for authentication. These credentials are not the user's original username and password, but a newly generated credential used to prove that the request comes from an authorized user, and do not reveal the user's original username and password.

[0048] To enhance security, the original password is not used directly during implementation. Instead, new credentials are generated, ideally temporary credentials. Credentials can be generated in the following ways: By binding the user's identity with device owner information, such as the device ID and IMEI (which needs to be anonymized) of temporary device 30; or by binding the user's account information from the target application 32, such as the account ID and username (not the password). Using a time-limited credential generated by the primary device 20 is the most secure method. The primary device 20 generates a dynamic token or one-time password (OTP) that is valid only for the current session and has a limited validity period (e.g., 5 minutes). Even if the credential is intercepted, it will quickly become invalid.

[0049] For example, when user A selects "Start a temporary session for instant messaging software" on the tablet, the system automatically packages "Target application 32 = instant messaging software" and "Account credentials = 6-digit dynamic code generated by mobile phone (valid for 5 minutes)" into a cross-client request and sends it to the connected mobile phone, which is user A's personal mobile phone, a frequently used mobile phone, i.e., frequently used device 20.

[0050] Step S3) Create a clone application of the target application 32. The clone application has an independent data directory 31, UID and running space. Set the login account of the clone application to the user account.

[0051] An independent running instance of the designated target application 32 is created on temporary device 30. The cloned application has its own dedicated storage space (data directory 31), system identity (UID), and running memory space, isolated from other applications (including native applications) that may exist on temporary device 30. Although the cloned application logs into the user account, this login state is simulated; the real login session remains on the primary device 20, thus ensuring data consistency and security—the data on the primary device 20 is the standard. For example, after the tablet receives confirmation from the phone, it immediately creates an "instant messaging software clone." The clone has an independent desktop application icon, an independent storage folder (such as / data / com.tongxin.temporary / ), and a new UID assigned by the system. The instant messaging software interface seen by the user displays user A's avatar and nickname, simulating a logged-in state.

[0052] Step S4) Listen for data requests generated by the cloned application, including data read requests, data write requests, and network data requests.

[0053] Temporary device 30 will continuously monitor all data access intentions of the cloned application. (See attached...) Figure 3 As shown, whether an application attempts to read local chat history (data read request), save a new chat background (data write request), or send a new message to server 10 (network data request), all requests will be monitored and captured, and converted into "data requests" subsequently forwarded to the primary device 20. For example, user A, in the tablet's "instant messaging app clone," clicks to enter a chat window, triggering a data read request to "read the chat history." The system listens for this request. Then, he types "Received, will process immediately" and clicks send, triggering a network data request to "send a message to server 10," which is also monitored and captured.

[0054] Step S5) When a data request is detected by the cloned application, the preset account credentials and the data request are sent to the primary device 20 through the communication connection, and the response data of the primary device 20 to the data request after verifying the account credentials is received. The response data is then submitted to the cloned application as the result of the data request.

[0055] Temporary device 30 does not process the request itself, but forwards it (along with credentials) to primary device 20. Primary device 20 verifies the credentials and executes the request using its real login state (e.g., reading historical messages from a local database or sending a message via a real instant messaging app), and returns the execution result (response data) to temporary device 30. When it is a network data request, primary device 20 will interact with server 10 to obtain response data. Temporary device 30 then simulates the result as a local operation and feeds it back to the cloned application for normal display.

[0056] For example, the tablet, acting as temporary device 30, sends a request to "read chat history" along with account credentials to the mobile phone. After verifying the validity of the account credentials, the mobile phone queries the chat history from its local instant messaging software database, packages the message list, and sends it back to the tablet. Upon receiving this, the tablet displays it on the "App Cloning" interface. When user A sends a message, it similarly sends a network data request to the mobile phone. The real instant messaging software app on the mobile phone sends the message, and upon successful transmission, the mobile phone sends a "sent successfully" status back to the tablet. The "cloned" instant messaging software on the tablet then displays that the message has been sent.

[0057] Step S6) When the end command is received, the data in the clone application and its data directory 31 is destroyed.

[0058] When the session ends, all traces left on the temporary device 30 are cleared. The running instance of the cloned application is uninstalled or removed, and all files (chat cache, images, configurations, etc.) in its separate data directory 31 are deleted to ensure data security. For example, after user A finishes processing messages, they click "End Session" on the tablet. The tablet immediately performs a destruction procedure: removing the "Instant Messaging App Clone" icon from the desktop, forcibly stopping all its processes, and completely deleting all data in the / data / com.tongxin.temporary / directory. A few minutes later, when friend B retrieves the tablet, there is no indication that anyone had logged into the instant messaging app, ensuring privacy and security.

[0059] In some implementations, the method for creating a clone application of the target application 32 includes:

[0060] Create an independent sandbox runtime environment;

[0061] In the sandbox runtime environment, the executable file of the target application 32 is loaded;

[0062] Assign a separate user ID and data storage directory to the target application 32 in the sandbox runtime environment;

[0063] Run the target application 32 in the sandbox environment to complete the creation of the clone application.

[0064] The method for monitoring data requests generated by the cloned application includes:

[0065] In the sandbox runtime environment, system calls made by the cloned application to access local storage and network communication are intercepted;

[0066] The system call is parsed, and when the parsing reveals that the clone application has initiated a data read request, data write request, or network data request, a corresponding data request event is generated.

[0067] On temporary device 30, a logically isolated virtualized environment (i.e., a sandbox runtime environment) is constructed. This sandbox runtime environment is isolated from other applications on temporary device 30 and has independent resources and boundaries. The sandbox runtime environment serves as a dedicated runtime container for the cloned application. The installation package (APK file) of the target application 32 (such as instant messaging software) or the core executable code (such as classes.dex, lib libraries) of the installed application is loaded into the sandbox runtime environment. The sandbox runtime environment provides necessary runtime support (such as emulated Android Framework APIs). The sandbox runtime environment assigns a system-level user ID to the loaded application, different from the original application and other processes. The cloned application will act as an independent entity, implementing process isolation and permission control. Within the storage space of the sandbox runtime environment, a dedicated data directory 31 is created for the cloned application (for example, the path may be / data / user / virtual / com.tongxin.app / ). This directory is used to store the cloned application's data, including databases, cache files, etc., and is separate from the original application. The cloned application within the sandbox runtime environment is launched, executing its main Activity. At this point, a clone application instance with an independent identity (UID), independent storage space, and independent running environment has been successfully created. Users can see and operate it on temporary device 30.

[0068] Within the sandbox environment, system calls made by the cloned application to access local storage and network communication are intercepted. This can be achieved using a proxy mechanism or other technologies disclosed in the art. For example, an intermediate layer can be set up to listen and intercept between the cloned application and the underlying operating system services. Upon identifying a specific type of data request, the sandbox environment suspends the execution of that local operation and generates a structured "data request event." This event includes information such as the request type, target resource (filename / URL), and operation parameters (e.g., request body, read / write mode).

[0069] On the other hand, in some other embodiments, the method for creating a clone application of the target application 32 includes:

[0070] Obtain the pre-configured UI control 34 template and data interaction parsing file corresponding to the target application 32;

[0071] The user interface 33 of the clone application is constructed based on the UI control 34 template;

[0072] Based on the data interaction parsing file, the interaction logic of each UI control 34 in the user interface 33 is configured so that the user's operation on the UI control 34 can trigger the predefined data interaction behavior recorded in the data interaction parsing file.

[0073] Set the login status of the user interface 33 to the logged-in status of the user account to complete the creation of the clone application.

[0074] The method for monitoring data requests generated by the cloned application includes:

[0075] Listen for user interaction events with the UI control 34 of the cloned application;

[0076] When an operation event is detected, the system determines whether the operation event triggers a data interaction behavior based on the data interaction parsing file.

[0077] When a data interaction behavior is triggered, a data request is generated based on the data interaction behavior.

[0078] In this embodiment, a front-end simulation is constructed using a method based on UI control 34 templates and data interaction parsing files. In particular, this front-end simulation is lightweight, which can save hardware resources of temporary device 30.

[0079] Pre-configure UI control templates and data interaction parsing files for the target application 32 (such as instant messaging software).

[0080] The UI control template 34 is a template used to define the key UI elements and their layout required for defining the interface of a cloned application. Each target application 32 corresponds to one template. For example, a template for an "instant messaging chat" interface might include: a top title bar (containing contact avatars and nicknames), a message list area, a bottom input box, and a send button, as well as the type, ID, position, and style of these UI controls 34, as shown in the attached template. Figure 1 As shown.

[0081] The data interaction parsing file is a structured configuration file used to record the mapping relationship between UI control 34 operations and backend data requests. For example, it can be {"ui_event": "SEND_BUTTON_CLICK", "request_type": "NETWORK_WRITE", "api_endpoint": " / v1 / messages / send", "params": ["input_text_content", "receiver_id"]}, which records the data interaction behavior that will be triggered when a send button is clicked, thus sending a message.

[0082] On temporary device 30, based on the obtained UI control 34 template, the corresponding UI controls 34 are dynamically instantiated and assembled into a visual user interface 33 according to the layout rules defined in the template. User interface 33 is a simplified version of the original application's core functionality, consuming fewer system resources and supporting only a portion of the functions. The specific supported functions are determined by the UI control 34 template and the data interaction parsing file. Specifically, by reading the data interaction parsing file, corresponding event listeners and processing logic are registered for each UI control 34 in the interface. For example, temporary device 30 registers an OnClickListener event for the "Send Button". Its processing logic is: when clicked, a predefined "Send Message" data interaction behavior is triggered. At the UI level, user avatar, nickname, and other information are filled into the corresponding positions on the interface, and the application state is set to logged-in.

[0083] Through the event dispatch mechanism of the UI framework, continuously listen to all user interaction behaviors on the user interface 33 of the clone application, such as clicking, long pressing, text input, pull-to-refresh, etc.

[0084] When an operation event is detected, the system determines whether the operation event triggers a data interaction behavior based on the data interaction parsing file. For example, when an interaction event of "send button clicked" is captured, the system immediately queries the "data interaction parsing file" to check if there is an entry matching the event. If a match is found, it is determined that the operation triggered a predefined data interaction behavior. Conversely, if no match is found, it is determined that the operation does not require data interaction.

[0085] When a data interaction is triggered, the temporary device 30 constructs a data request based on the information in the parsed file. The generated data request will be used in subsequent steps and sent to the main device 20 for proxy execution via a communication connection. This implementation does not require copying and running the complete APK of the original application, does not occupy a large amount of storage space and memory, and has a fast startup speed. The temporary device 30 does not even contain the original application's code, avoiding the risk of exploiting vulnerabilities that may exist in the application itself; the core logic and data are entirely on the main device 20.

[0086] On the other hand, this manual provides a temporary cross-client data synchronization system for the same account, running on temporary device 30. Please refer to the appendix. Figure 4 ,include:

[0087] The communication module 100 establishes a communication connection with the commonly used device 20, which is a device that has been logged into with a user account.

[0088] Trigger module 200 receives cross-client requests, the cross-client requests including preset account credentials and target application 32;

[0089] The creation module 300 creates a clone application of the target application 32. The clone application has an independent data directory 31, UID and running space. The login account of the clone application is set to the user account.

[0090] The listening module 400 listens for data requests generated by the clone application, including data read requests, data write requests, and network data requests.

[0091] The synchronization module 500, when it detects that the cloned application generates a data request, sends the preset account credentials and the data request to the primary device 20 through the communication connection, and receives the response data of the primary device 20 to the data request after verifying the account credentials, and submits the response data as the result of the data request to the cloned application.

[0092] When a termination command is received, the clone application and the data in its data directory 31 are destroyed.

[0093] Please see Figure 5 The diagram shown is a structural schematic of an electronic device provided in an embodiment of this specification.

[0094] like Figure 5As shown, the electronic device 1100 may include: at least one processor 1101, at least one network interface 1104, a user interface 1103, a memory 1105, and at least one communication bus 1102. The communication bus 1102 can be used to connect and communicate with the various components mentioned above. The user interface 1103 may include buttons, and optionally may include standard wired or wireless interfaces. The network interface 1104 may include, but is not limited to, a Bluetooth module, an NFC module, or a Wi-Fi module. The processor 1101 may include one or more processing cores. The processor 1101 connects to various parts within the electronic device 1100 using various interfaces and lines, and performs various functions of the routing device and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 1105, and by calling data stored in the memory 1105. Optionally, the processor 1101 may be implemented using at least one hardware form of DSP, FPGA, or PLA. The processor 1101 may integrate one or more combinations of CPU, GPU, and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content that the display screen needs to show; and the modem is used for wireless communication.

[0095] It is understandable that the aforementioned modem may not be integrated into the processor 1101, but may be implemented using a separate chip.

[0096] The memory 1105 may include RAM or ROM. Optionally, the memory 1105 may include a non-transitory computer-readable medium. The memory 1105 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 1105 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory 1105 may also be at least one storage device located remotely from the aforementioned processor 1101. As a computer storage medium, the memory 1105 may include an operating system, a network communication module, a user interface module, and application programs. The processor 1101 may be used to call the application programs stored in the memory 1105 and execute the methods in the above-described embodiments.

[0097] This specification also provides a computer-readable storage medium storing instructions that, when executed on a computer or processor, cause the computer or processor to perform multiple steps as described in the above embodiments. If the constituent modules of the above-described electronic device are implemented as software functional units and sold or used as independent products, they can be stored in the computer-readable storage medium.

[0098] This specification also provides a computer program product, including a computer program that, when executed by a processor, implements the multiple steps described in the above embodiments.

[0099] Where there is no conflict, the technical features in this embodiment and implementation scheme can be combined arbitrarily.

[0100] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes multiple computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this specification are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server 10, or data center to another website, computer, server 10, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server 10 or data center that integrates multiple available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital versatile discs (DVDs)), or semiconductor media (e.g., solid state disks (SSDs)).

[0101] When implemented through hardware or firmware, the aforementioned method flow is programmed into the hardware circuit to obtain the corresponding hardware circuit structure and achieve the corresponding function. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit, whose logic function is determined by the user programming the device. Designers can program a digital system onto a PLD themselves, eliminating the need for chip manufacturers to design and fabricate dedicated integrated circuit chips. Furthermore, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, similar to the software compiler used in program development. The original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There is not just one HDL, but many. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of the aforementioned hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logic method flow can be easily obtained.

[0102] The embodiments described above are merely preferred embodiments of this specification and are not intended to limit the scope of this specification. Any modifications and improvements made by those skilled in the art to the technical solutions of this specification without departing from the spirit of this specification should fall within the protection scope defined by the claims of this specification.

Claims

1. A method for temporary cross-client data synchronization under the same account, running on a temporary device, characterized in that, The method comprises the steps of: establishing a communication connection with a common device that has logged in a user account; receiving a cross-client request, which includes preset account credentials and a target application, the account credentials being a newly generated credential for proving that the request comes from an authorized user; creating a clone application of the target application, the clone application having an independent data directory, UID, and running space, and setting the login account of the clone application as the user account; listening to data requests generated by the clone application, the data requests including data read requests, data write requests, and network data requests; when a data request generated by the clone application is listened to, sending the preset account credentials and the data request to the common device through the communication connection, and receiving response data of the common device to the data request after verifying the account credentials, and submitting the response data to the clone application as the result of the data request; when an end instruction is received, destroying the clone application and the data in the data directory of the clone application.

2. The method according to claim 1, wherein the method of setting the preset account credentials comprises: setting the account credentials according to one or more of the information of the device owner, the information of the user account of the target application, or the information of a time-limited credential generated by the common device.

3. The method according to claim 1 or 2, wherein the method of creating the clone application of the target application comprises: creating an independent sandbox running environment; loading an executable file of the target application in the sandbox running environment; allocating an independent user identification and a data storage directory to the target application in the sandbox running environment; running the target application in the sandbox running environment to complete the creation of the clone application.

4. The method according to claim 3, wherein the method of listening to the data requests generated by the clone application comprises: intercepting system calls for local storage and network communication of the clone application in the sandbox running environment; parsing the system calls, and generating a corresponding data request event when a data read request, a data write request, or a network data request initiated by the clone application is parsed.

5. The method according to claim 1 or 2, wherein the method of creating the clone application of the target application comprises: obtaining a pre-configured UI control template and a data interaction parsing file corresponding to the target application; constructing a user interface of the clone application based on the UI control template; configuring the interaction logic of each UI control in the user interface based on the data interaction parsing file, so that the operation of the user on the UI control can trigger the pre-defined data interaction behavior recorded in the data interaction parsing file; setting the login state of the user interface to the logged-in state of the user account, and completing the creation of the clone application. ​ ​ ​ ​ 6. The temporary cross-client data synchronization method for the same account according to claim 5, characterized in that, The method for monitoring data requests generated by the cloned application includes: Listen for user interaction events with the UI controls of the cloned application; When an operation event is detected, the system determines whether the operation event triggers a data interaction behavior based on the data interaction parsing file. When a data interaction behavior is triggered, a data request is generated based on the data interaction behavior.

7. A system for temporary cross-client data synchronization with an account, running on a temporary device, characterized in that, include: A communication module that establishes a communication connection with commonly used devices, wherein the commonly used devices are devices that have been logged into with a user account; The triggering module receives cross-client requests, which include preset account credentials and target applications. The account credentials are newly generated credentials used to prove that the request comes from an authorized user. The creation module creates a clone application of the target application. The clone application has an independent data directory, UID, and running space. The login account of the clone application is set to the user account. The monitoring module monitors the data requests generated by the cloned application, including data read requests, data write requests, and network data requests. The synchronization module, when it detects that the cloned application generates a data request, sends the preset account credentials and the data request to the primary device through the communication connection, and receives the response data of the primary device to the data request after verifying the account credentials, and submits the response data as the result of the data request to the cloned application. When a termination command is received, the cloned application and the data in its data directory are destroyed.

8. An electronic device, comprising: Including the processor and memory; The processor is connected to the memory; The memory is used to store executable program code; The processor runs a program corresponding to the executable program code stored in the memory to perform the method as described in any one of claims 1-6.

9. A computer readable storage medium having stored thereon a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-6.

10. A computer program product comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-6.

Images