Task data sharing method and electronic device

Abstract

The present application relates to the technical field of communications, and provides a task data sharing method and an electronic device. In the method, display and sharing are performed on a first target system interface of a first electronic device and a second target system interface of a second electronic device, so that system-level display and sharing of application data are realized, without the need of performing the entire operation in an application, thereby simplifying the operation, thus providing better user experience.

Description

Task data sharing methods and electronic devices

[0001] This application claims priority to Chinese Patent Application No. 202411961207.5, filed on December 28, 2024, entitled “Task Data Sharing Method and Electronic Device”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a task data sharing method and electronic device. Background Technology

[0003] Currently, application task data on terminal devices is displayed and updated locally. To share data, two methods are available: one is through traditional screenshot sharing with other users, and the other is sharing partial data within the same application, such as WeChat. TM Location sharing functionality.

[0004] Therefore, in related technologies, the methods of sharing task data are relatively cumbersome, and the user experience needs to be improved. Summary of the Invention

[0005] This application provides a task data sharing method and electronic device, which can realize system-level application task data sharing, simplify user operations for task data sharing between electronic devices, and improve user experience.

[0006] The first aspect of this application discloses a method for sharing task data, including:

[0007] The target task data is output on the first target system interface of the first electronic device; wherein, the target task data is the task data of the first target application in the first electronic device;

[0008] The first electronic device responds to a first operation on the target task data and generates sharing link information corresponding to the target task data.

[0009] In response to a second operation performed on the first electronic device, the first electronic device sends the sharing link information to the second electronic device;

[0010] In response to a third operation concerning the shared link information, the second electronic device outputs the target task data on the second target system interface.

[0011] In this task data sharing method, display and sharing are performed on the first target system interface of the first electronic device and the second target system interface of the second electronic device. This achieves system-level display and sharing of application data, eliminating the need for full operation within the application, simplifying the operation and providing a better user experience.

[0012] Optionally, in response to a first operation on the target task data, the first electronic device generates sharing link information corresponding to the target task data, including:

[0013] In response to a first operation on the target task data, the first electronic device sends a first message about the target task data to the first server and generates sharing link information corresponding to the target task data.

[0014] In response to a third operation concerning the shared link information, the second electronic device outputs target task data on the second target system interface, including:

[0015] In response to a third operation concerning the shared link information, the second electronic device receives a second message from the first server regarding the target task data.

[0016] The second electronic device outputs target task data on the second target system interface based on the second message.

[0017] In this embodiment, the sharing of target task data is achieved through the first server, enabling remote sharing between the first electronic device and the second electronic device.

[0018] Optionally, in response to a third operation concerning the sharing link information, the second electronic device receives a second message from the first server regarding target task data, including:

[0019] In response to a third operation concerning the shared link information, the second electronic device sends a data acquisition request to the first server; wherein the data acquisition request includes device information of the second electronic device.

[0020] In response to the data acquisition request sent by the second electronic device, the first server sends a second message about the target task data to the second electronic device corresponding to the device information.

[0021] The second electronic device receives a second message regarding the target mission data.

[0022] In this embodiment, target task data can be accurately pushed to the second electronic device through a data acquisition request containing device information.

[0023] Optionally, after outputting the target task data on the second target system interface, the method further includes:

[0024] The first server receives the target task update data from the target task data.

[0025] The first server pushes a third message about the updated data of the target task to the second electronic device corresponding to the device information;

[0026] The second electronic device receives a third message regarding updated target task data and updates the second target task data accordingly.

[0027] In this embodiment, by pushing update data through the first server, the target task data displayed on the system on the second electronic device can be updated in real time, so that the user can receive the update data in real time on the system interface.

[0028] Optionally, the first server receives target task update data from the target task data, including:

[0029] The first server receives the target task update data pushed by the second server; wherein, the second server is the server corresponding to the first target application.

[0030] In this embodiment, the first server receives data pushed by the server corresponding to the first target application and can directly push it to the device, which can reduce latency, improve the timeliness of data updates, and further enhance the user experience.

[0031] Optionally, the second electronic device includes multiple devices, and each second electronic device sends a data acquisition request to the first server, which includes device information, and each second electronic device outputs target task data.

[0032] The first server pushes a third message regarding the updated data for the target task to the second electronic device corresponding to the device information, including:

[0033] The first server pushes the third message about the updated data of the target task to the second electronic device corresponding to each device information.

[0034] In this embodiment, the system-level task data sharing between one and many is achieved through the first server, which can enable more application scenarios and further improve the user experience.

[0035] Optionally, in response to a first operation on the target task data, the first electronic device generates sharing link information corresponding to the target task data, including:

[0036] In response to a first operation on target task data, the first electronic device displays a first display area on its screen.

[0037] In response to a first selection operation of a target option in a first display area, the first electronic device generates a sharing link information corresponding to the target task data.

[0038] In this embodiment, by using the first display area to receive the selection operation, a more eye-catching interface can be provided to the user, further enhancing the user experience.

[0039] Optionally, in response to a second operation performed on the first electronic device, the first electronic device sends sharing link information to the second electronic device, including:

[0040] In response to a second operation targeting the first electronic device, the first electronic device sends the sharing link information to the second electronic device via a second target application.

[0041] In this embodiment, sending the sharing link information through the second target application is simple, quick, and facilitates interaction with the user.

[0042] Optionally, in response to a user's first selection of a target option in the first display area, the first electronic device generates sharing link information corresponding to the target task data, including:

[0043] In response to a first selection operation on a target option in a first display area, the first electronic device generates sharing link information corresponding to the target task data and displays a second display area on the screen of the first electronic device.

[0044] In response to a second operation targeting the first electronic device, the first electronic device sends sharing link information to the second electronic device via a second target application, including:

[0045] In response to a second selection operation on a target application icon in a second display area, the first electronic device sends sharing link information to the second electronic device via the second target application; wherein the target application icon is the icon corresponding to the second target application.

[0046] In this embodiment, by using a second display area to handle the selection operation in addition to the first display area, a more eye-catching interface can be provided to the user, further enhancing the user experience.

[0047] Optionally, the target task data is output on the first target system interface of the first electronic device, including:

[0048] The first target system interface of the first electronic device displays the first target task window corresponding to the target task data;

[0049] In response to a first operation on the target task data, the first electronic device generates sharing link information corresponding to the target task data, including:

[0050] The first electronic device, in response to a first operation on the first target task window, generates sharing link information corresponding to the target task data;

[0051] The second electronic device outputs target task data to the second target system interface, including:

[0052] The second electronic device displays the second target task window corresponding to the target task data on the second target system interface.

[0053] In this embodiment, the target task data is displayed in a task window, which is more intuitive and facilitates the management and operation of the target task data.

[0054] Optionally, after the second electronic device outputs the second target task window corresponding to the target task data on the second target system interface, the method further includes:

[0055] When the first preset condition is met, the sharing task corresponding to the second target task window is terminated; wherein the first preset condition includes at least one of the following: the second electronic device receives task termination information, the second electronic device receives a fourth operation from the user on the second target task window, and the output of the second target task window reaches a preset time.

[0056] In this embodiment, the user actively ends the sharing task, avoiding unnecessary resource consumption due to the inability to end the sharing task in situations where it could be temporarily ended. This provides users with more options and a better experience. Ending the task within a preset time avoids resource waste, reduces battery consumption and operating resource usage, and enhances the user experience.

[0057] Optionally, the target task data is real-time task data.

[0058] In this embodiment, which is a scenario of live task sharing, the necessity of live task sharing is greater. System-level live task sharing can further improve the convenience of operation and enhance the user experience.

[0059] Optionally, the first target application is a third-party application.

[0060] In this embodiment, for a scenario of sharing a live task using a third-party application, the third-party application may not be installed on the second electronic device. Therefore, the task data sharing method of this embodiment can complete sharing and display regardless of whether the second electronic device has the first target application or not.

[0061] A second aspect of this application discloses a task data sharing method for a first electronic device, comprising:

[0062] The target task data is output on the first target system interface; wherein, the target task data is the task data of the first target application in the first electronic device;

[0063] In response to the first operation on the target task data, generate the sharing link information corresponding to the target task data;

[0064] In response to a second operation on the first electronic device, sharing link information is sent to the second electronic device; wherein the sharing link information is used by the second electronic device to output target task data.

[0065] Optionally, in response to the first operation on the target task data, share link information corresponding to the target task data is generated, including:

[0066] In response to the first operation on the target task data, a first message about the target task data is sent to the first server, and the corresponding share link information for the target task data is generated.

[0067] Optionally, in response to the first operation on the target task data, share link information corresponding to the target task data is generated, including:

[0068] In response to a first operation on the target task data, display the first display area;

[0069] In response to the first selection operation of the target option in the first display area, the share link information corresponding to the target task data is generated.

[0070] Optionally, in response to a first selection operation on a target option in the first display area, share link information corresponding to the target task data is generated, including:

[0071] In response to a first selection operation on a target option in the first display area, share link information corresponding to the target task data is generated and displayed in the second display area;

[0072] In response to a second operation on the first electronic device, the sharing link information is sent to the second electronic device via a second target application, including:

[0073] In response to a second selection operation on a target application icon in a second display area, sharing link information is sent to a second electronic device; wherein the target application icon is the icon corresponding to the second target application.

[0074] Optionally, in response to a second operation on the first electronic device, sending sharing link information to the second electronic device includes:

[0075] In response to a second operation on the first electronic device, the sharing link information is sent to the second electronic device via the second target application.

[0076] Optionally, target task data is output on the first target system interface, including:

[0077] The first target task window, corresponding to the target task data, is displayed on the first target system interface;

[0078] In response to the first operation on the target task data, generate the corresponding share link information for the target task data, including:

[0079] In response to the first operation on the target task window, generate the share link information corresponding to the target task data.

[0080] Optionally, the target task data is real-time task data.

[0081] Optionally, the first target application is a third-party application.

[0082] A third aspect of this application discloses a task data sharing method for a second electronic device, comprising:

[0083] Receive a sharing link information about target task data sent by a first electronic device; wherein, the target task data is the task data of a first target application in the first electronic device;

[0084] In response to a third operation on the shared link information, target task data is output on the second target system interface of the second electronic device.

[0085] Optionally, in response to a third operation on the shared link information, target task data is output on the second target system interface of the second electronic device, including:

[0086] In response to a third operation concerning shared link information, a second message regarding target task data sent by the first server is received;

[0087] Based on the second message, target task data is output on the second target system interface of the second electronic device.

[0088] Optionally, in response to a third operation concerning shared link information, a second message regarding target task data sent by the first server is received, including:

[0089] In response to a third operation concerning the shared link information, a data retrieval request is sent to the first server; wherein the data retrieval request includes device information of the second electronic device;

[0090] Receive a second message from the first server in response to the data retrieval request, containing data about the target task.

[0091] Optionally, after outputting the target task data on the second target system interface of the second electronic device, the method further includes:

[0092] Receive a third message from the first server regarding updated data for the target task. The updated data for the target task is the updated data about the target task.

[0093] Update the target task data based on the third message.

[0094] Optionally, target task data is output on the second target system interface of the second electronic device, including:

[0095] The second target task window corresponding to the target task data is output on the second target system interface of the second electronic device;

[0096] Based on the third message, update the target task data, including:

[0097] Based on the third message, update the second target task window corresponding to the target task data.

[0098] Optionally, after outputting the second target task window corresponding to the target task data on the second target system interface of the second electronic device, the method further includes:

[0099] When the first preset condition is met, the sharing task corresponding to the second target task window is terminated; wherein the first preset condition includes at least one of the following: the second electronic device receives the task termination information pushed by the first server, the second electronic device receives the user's fourth operation on the second target task window, and the output of the second target task window reaches a preset time.

[0100] Optionally, receiving a sharing link information about the target task data sent by the first electronic device, including:

[0101] The second target application receives a sharing link information about the target task data sent by the first electronic device.

[0102] Optionally, the target task data is real-time task data.

[0103] Optionally, the first target application is a third-party application.

[0104] A fourth aspect of this application discloses a task data sharing method for a first server, comprising:

[0105] Receive a first message about target task data sent by a first electronic device; wherein the target task data is the task data of the first target application output on the first target system interface of the first electronic device;

[0106] In response to a data acquisition request sent by a second electronic device, a second message regarding target task data is sent to the second electronic device, so that the second target system interface of the second electronic device outputs the target task data; wherein, the data acquisition request is generated based on sharing link information, and the sharing link information is generated based on the target task data on the first target system interface of the first electronic device.

[0107] Optionally, it also includes:

[0108] A third message regarding the updated data of the target task is sent to the second electronic device; wherein, the updated data of the target task is the updated data regarding the target task data.

[0109] Optionally, a third message regarding updated data for the target task is sent to the second electronic device, including:

[0110] Receive target task update data pushed by the second server; wherein, the second server is the server corresponding to the first target application;

[0111] A third message regarding updated data for the target mission is sent to the second electronic device.

[0112] Optionally, the data acquisition request includes device information of the second electronic device; sending a third message about updated data for the target task to the second electronic device includes:

[0113] Based on the device information, a third message regarding the updated data of the target task is sent to the second electronic device corresponding to the device information.

[0114] Optionally, the second electronic device includes multiple devices, and each second electronic device sends a data acquisition request to the first server, which includes device information.

[0115] Based on the device information, a third message regarding the updated data for the target task is sent to the second electronic device corresponding to the device information, including:

[0116] Based on the device information of each second electronic device, a third message regarding the updated data of the target task is sent to each second electronic device respectively.

[0117] Optionally, the target task data is real-time task data.

[0118] Optionally, the first target application is a third-party application.

[0119] The fifth aspect of this application discloses a graphical user interface (GUI) for an electronic device, the electronic device including a display screen, a memory, and one or more processors, the one or more processors being used to execute one or more computer programs stored in the memory, the graphical user interface including:

[0120] A first GUI is displayed on the screen. The first GUI includes a target system interface. The target system interface includes a target display area. The target display area is used to output target task data.

[0121] In response to a first gesture targeting a display area, a first control is displayed on the first GUI;

[0122] In response to a second gesture toward the first control, a second GUI is displayed on the screen, the second GUI including a second control for sharing target task data.

[0123] Optionally, the graphical user interface also includes:

[0124] In response to a third gesture to the second control, a third GUI is displayed on the screen, the third GUI including at least the target application icon;

[0125] In response to a fourth gesture targeting the target app icon, display the fourth GUI of the target app corresponding to the target app icon on the screen.

[0126] Optionally, the graphical user interface also includes:

[0127] The fifth GUI is displayed on the screen. The fifth GUI is the application interface, and a sharing link is displayed on the fifth GUI.

[0128] In response to a fifth gesture for sharing a connection, a sixth GUI is displayed on the screen, which includes the target system interface.

[0129] The sixth aspect of this application discloses a first electronic device, comprising:

[0130] The first output unit is used to output target task data on the first target system interface; wherein, the target task data is the task data of the first target application in the first electronic device;

[0131] The generation unit is used to generate sharing link information corresponding to the target task data in response to the first operation on the target task data;

[0132] The sending unit is configured to send sharing link information to the second electronic device in response to a second operation on the first electronic device; wherein the sharing link information is used by the second electronic device to output target task data.

[0133] The seventh aspect of this application discloses a second electronic device, comprising:

[0134] The receiving unit is used to receive sharing link information about target task data sent by the first electronic device; wherein, the target task data is the task data of the first target application in the first electronic device;

[0135] The second output unit is used to output target task data on the second target system interface of the second electronic device in response to a third operation on the shared link information.

[0136] The eighth aspect of this application discloses a first electronic device, including one or more displays, one or more memories, and one or more processors; wherein the one or more memories store one or more programs; when the one or more processors execute one or more programs, the first electronic device enables the above-described task data sharing method.

[0137] The ninth aspect of this application discloses a second electronic device, including one or more displays, one or more memories, and one or more processors; wherein the one or more memories store one or more programs; when the one or more processors execute one or more programs, the second electronic device enables the above-described task data sharing method.

[0138] The tenth aspect of this application discloses a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the computer device performs the aforementioned task data sharing method.

[0139] The eleventh aspect of this application discloses a computer program product containing instructions that, when run on an electronic device, causes the electronic device to perform the aforementioned task data sharing method.

[0140] The twelfth aspect of this application discloses a computer-readable storage medium including instructions that, when executed on an electronic device, cause the electronic device to perform the aforementioned task data sharing method.

[0141] The thirteenth aspect of this application discloses a system for realizing communication between devices, the system including the aforementioned first electronic device and at least one of the aforementioned second electronic devices; the first electronic device and at least one second electronic device establish a communication link with each other.

[0142] It should be understood that the task data sharing methods of the second, third, and fourth aspects, the graphical user interface (GUI) of the fifth aspect, the electronic devices of the sixth, seventh, eighth, and ninth aspects, the computer device of the tenth aspect, the computer program product of the eleventh aspect, the computer-readable storage medium of the twelfth aspect, and the system for realizing inter-device communication of the thirteenth aspect correspond to the methods of the first aspect above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0143] Figure 1 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0144] Figure 2 is a software architecture diagram of an electronic device provided in an embodiment of this application;

[0145] Figure 3 is a schematic diagram of a system 20 for realizing inter-device communication according to an embodiment of this application;

[0146] Figure 4 is a schematic diagram of another system 20 for realizing inter-device communication provided in an embodiment of this application;

[0147] Figure 5 is a flowchart of a task data sharing method provided in an embodiment of this application;

[0148] Figure 5A is a schematic diagram of the notification center interface of the first electronic device provided in an embodiment of this application;

[0149] Figure 5B is a schematic diagram of the lock screen interface of the first electronic device provided in an embodiment of this application;

[0150] Figure 5C is a schematic diagram of the desktop interface of the first electronic device provided in an embodiment of this application;

[0151] Figure 5D is a front view of the first electronic device displaying the first live window and option controls provided in an embodiment of this application;

[0152] Figure 5E is a front view of the first electronic device displaying the first display area provided in an embodiment of this application;

[0153] Figure 5F is a front view of the first electronic device displaying the first application interface provided in an embodiment of this application;

[0154] Figure 5G is a front view of a first electronic device displaying a second display area, provided in an embodiment of this application.

[0155] Figure 5H is a front view of the second electronic device displaying the second application interface provided in the embodiment of this application;

[0156] Figure 5I is a schematic diagram of the first electronic device and the second electronic device displaying target task data provided in the embodiments of this application;

[0157] Figure 6 is a flowchart illustrating a specific execution method of S540 in Figure 5;

[0158] Figure 7 is a schematic diagram of the process of a second electronic device acquiring target task data according to an embodiment of this application;

[0159] Figure 8 is a schematic diagram of a process for updating target task data according to an embodiment of this application;

[0160] Figure 9 is a timing diagram of a task data sharing method provided in an embodiment of this application;

[0161] Figure 10 is a flowchart illustrating the task data sharing method performed by the first electronic device according to an embodiment of this application;

[0162] Figure 11 is a flowchart illustrating a specific execution method of S104 in Figure 10;

[0163] Figure 12 is a flowchart illustrating the task data sharing method performed by the second electronic device according to an embodiment of this application;

[0164] Figure 13 is a flowchart illustrating a specific execution method of S108 in Figure 12;

[0165] Figure 14 is a flowchart illustrating the task data sharing method executed by the first server according to an embodiment of this application;

[0166] Figure 15 is a schematic diagram of the structure of a first electronic device provided in an embodiment of this application;

[0167] Figure 16 is a schematic diagram of the structure of a second electronic device provided in an embodiment of this application.

[0168] In the diagram, 100 is an electronic device, 110 is a processor, 120 is a memory, 130 is a display screen, 20 is a system, 21 is a first electronic device, 22 is a second electronic device, 23 is a second server, 24 is a first server, 52 is a notification center interface, 53 is a first live view window, 54 is an option control, 55 is a first display area, 56 is a lock screen interface, 57 is a desktop interface, 58 is a first application interface, 59 is a second application interface, 60 is a second display area, 61 is a second live view window, 152 is a first output unit, 154 is a generation unit, 156 is a sending unit, 162 is a receiving unit, and 164 is a second output unit. Detailed Implementation

[0169] The embodiments of this application are described below with reference to the accompanying drawings.

[0170] It should be noted that in this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The terms "first," "second," "third," "fourth," etc. (if present) in this application are used to distinguish similar objects, not to describe a specific order or sequence.

[0171] Figure 1 illustrates a structural schematic diagram of an electronic device 100. As shown in Figure 1, this application embodiment provides an electronic device 100.

[0172] Electronic device 100 may include at least one of the following: mobile phone, foldable electronic device, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, super mobile personal computer, netbook, cellular phone, PDA, AR device, VR device, artificial intelligence device, wearable device, in-vehicle device, smart home device, and smart city device. This application does not impose any special limitations on the type of electronic device 100. Therefore, in the embodiments of this application, electronic device 100 includes the first electronic device, second electronic device, computer device, etc., as described in subsequent embodiments.

[0173] Electronic device 100 may include processor 110, memory 120, display screen 130, etc. The structures illustrated in the embodiments of this application do not constitute a limitation on electronic device 100. In other embodiments of this application, electronic device 100 may include more or fewer components than illustrated. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0174] Processor 110 may include one or more processing units, such as application processors, modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0175] The processor 110 can generate operation control signals based on the instruction opcode and timing signals to control the instruction fetching and execution.

[0176] The memory 120 can be used to store computer executable program code, which includes instructions. The memory 120 may include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, phonebook, etc.). Furthermore, the memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional methods or data processing of the electronic device 100 by running instructions stored in the memory 120 and / or instructions stored in memory disposed in the processor. For example, the memory 120 stores one or more programs, and when one or more processors of the electronic device 100 execute one or more programs, the electronic device 100 implements the task data sharing method in the embodiments of this application.

[0177] Electronic device 100 can implement display functions through a GPU, display screen 130, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 130 and the application processor. The GPU is used to perform mathematical and geometric calculations and graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0178] Display screen 130 is used to display images, videos, etc. In some embodiments, electronic device 100 may include one or more display screens 130. Display screen 130 may be at least one of LCD, OLED, AMOLED, FLED, Miniled, MicroLED, Micro-OLED, quantum dot light-emitting diode (QLED) displays, etc. In some embodiments, display screen 130 may be a touch screen.

[0179] The software architecture of the electronic device 100 provided in the embodiments of this application is described below.

[0180] The electronic device 100 provided in this application embodiment can run an operating system (OS). This operating system can be various operating systems currently used in the industry, such as HarmonyOS, an operating system developed based on OpenHarmony; or other operating systems such as Android. TMAn operating system (OS) can refer to various open-source operating systems or their derivatives, such as Linux (Linux OS) and other embedded operating systems. It can also be a future-oriented operating system, such as an AI-based operating system. An operating system is a set of interconnected system software programs that manage and control the operation of electronic devices, utilize and run hardware and software resources, and provide public services to organize user interactions. In electronic devices, the operating system occupies a crucial position, connecting to the physical hardware layer below and providing a runtime environment for application software above.

[0181] An operating system typically includes a kernel layer, a middleware layer, and an application layer. The application layer includes applications, which can include system applications and third-party applications. The middleware layer is a set of software, or frameworks, that provides various services to application developers, such as databases, multimedia, and graphics, or capabilities like distributed scheduling and system expansion. For example, the middleware layer can also be broadly divided into a framework layer and / or a system service layer. The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The system service layer includes the core capabilities of the system, providing services to applications through the framework layer. The kernel layer is the layer between hardware and software. The kernel layer can include hardware drivers and the operating system kernel. In addition to providing hardware drivers, the kernel layer also supports functions such as memory management and system process management.

[0182] The electronic devices we use in our daily lives come in various types and forms, and the application scenarios of electronic device 100 are also very wide. Therefore, based on the different forms and functions of electronic devices 100, different application scenarios, and different user needs, the operating systems used in electronic devices 100 may also be different. These operating systems have commonalities as well as their own characteristics, and different operating systems affect user experience, application ecosystem, and system performance. The basic functions implemented by the electronic device 100 provided in this application can be implemented through a general-purpose operating system or through a dedicated operating system. To more clearly illustrate the implementation of the embodiments of this application under a specific operating system, the following shows an operating system architecture. Those skilled in the art can deduce the implementation of the embodiments of this application under other specific operating systems, such as HarmonyOS or Android. TM Implementation under the operating system.

[0183] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered architecture operating system as an example to exemplify the software architecture of electronic device 100.

[0184] Figure 2 is a software architecture diagram of an electronic device 100 according to an embodiment of this application. As shown in Figure 2, the layered architecture may include several layers, and the layers communicate with each other through software interfaces.

[0185] In some embodiments, the layered architecture of the operating system includes an application layer, a framework layer, a system service layer, and a kernel layer. The application layer may include system applications and extended / third-party applications. System applications may include the desktop, control bar, settings, contacts, phone, camera, etc., while extended / third-party applications may include social applications, travel applications, etc.

[0186] Figure 3 is a schematic diagram of a system 20 for realizing inter-device communication according to an embodiment of this application. As shown in Figure 3, the system 20 includes a first electronic device 21 and a second electronic device 22. A communication connection is established between the first electronic device 21 and the second electronic device 22, enabling message exchange between applications. In one embodiment, the first electronic device 21 is communicatively connected to a second server 23, which provides application data to the first electronic device 21.

[0187] In one embodiment, the first electronic device 21 can act as the active sharer of task data, and the second electronic device 22 can act as the receiver of task data.

[0188] In one embodiment, the second electronic device 22, acting as a data receiver, may include multiple devices. That is, the first electronic device 21 can communicatively connect to multiple second electronic devices 22 to share task data with them.

[0189] In one embodiment, the second server 23 is an application server responsible for pushing corresponding application data to electronic devices, such as the application cloud server corresponding to a mobile travel application.

[0190] Figure 4 is a schematic diagram of another system 20 for realizing inter-device communication provided in an embodiment of this application. As shown in Figure 4, based on the aforementioned embodiment, system 20 further includes a first server 24. The first server 24 is communicatively connected to the first electronic device 21 and the second electronic device 22. In one embodiment, the first server 24 is connected to a second server 23, and the second server 23 pushes application data to the first electronic device 21 and the second electronic device 22 through the first server 24.

[0191] In one embodiment, the second server 23 can also directly push application data to the first electronic device 21.

[0192] In one embodiment, the structure of the first electronic device 21 and the second electronic device 22 can refer to the structural diagram of the electronic device 100 in the foregoing embodiment.

[0193] In one embodiment, the first server 24 may be a system server, such as a push cloud server, to provide data push services for the first electronic device 21 or the second electronic device 22.

[0194] In one embodiment, the first server 24 may be a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it causes the computer device to implement the task data sharing method provided in the embodiments of this application.

[0195] In one embodiment, the first electronic device 21 or the second electronic device 22 may be electronic devices of the same brand or different brands. In one embodiment, a separate storage space may be provided in the first server 24 to store the target task data in this embodiment.

[0196] In one embodiment, the second server 23 may be a cloud server corresponding to any application in the first electronic device 21 or the second electronic device 22.

[0197] For a specific embodiment of the method for system 20 to participate in the execution of task data sharing, please refer to the following embodiments.

[0198] Figure 5 is a flowchart illustrating a task data sharing method provided in an embodiment of this application. As shown in Figure 5, based on the system 20 shown in Figures 3 and 4, the task data sharing method of this embodiment includes:

[0199] In step S520, the target task data is output on the first target system interface of the first electronic device.

[0200] In specific implementation, the first target system interface is the system interface on the first electronic device, which can be used to display target task data. It is understood that, according to the description of the software architecture of the electronic device (e.g., a mobile phone) in the foregoing embodiments, the software architecture of the electronic device includes the operating system and various applications in the application layer of the operating system. The various applications in the application layer can be divided into system applications and extended / third-party applications. In one embodiment, system applications can be further divided into software involved in the operating system itself and software included with the operating system. Software involved in the operating system itself may include the desktop, control bar, notifications and status bar (notification center), settings, etc., while software included with the operating system may include telephone, SMS, browser, photo album, calculator, calendar, clock, etc. It should be noted that the names of software may differ in different operating systems, but their functionalities are essentially the same. For example, the notification center in the iOS mobile operating system is also called the notification and status bar in the Android and HarmonyOS operating systems.

[0201] In this embodiment, the first target system interface refers to the software involved in the operating system itself. For example, the first target system interface can be the interface where the mobile phone's notification center (the name in the iOS system) is located, or it can be the interface where the notification and status bar are located in the Android operating system and the HarmonyOS operating system. This interface is also referred to as the notification center interface in this embodiment. In one embodiment, the notification center interface may display the words "Notification Center" or it may not display them. For example, as shown in FIG5A, FIG5A is a schematic diagram of the notification center interface of the first electronic device provided in this application embodiment. The first electronic device is a mobile phone. In the figure, the mobile phone includes a display screen 130, and the display screen 130 displays the notification center interface 52. As shown in FIG5A, it is a front view of the mobile phone. By touching the top left side of the mobile phone's display screen and sliding down from the top edge, one can switch to the notification center interface 52 shown in FIG5A.

[0202] The target task data refers to the task data of the first target application in the first electronic device. The first target application can be software within the first electronic device, such as third-party applications for social networking, navigation, or travel, or software built into the operating system, such as alarm clocks or timers. In one embodiment, the first target application is an extended application / third-party application, for example, a travel application or map software. As an extended application / third-party application, the first target application has a corresponding application cloud server, exemplarily the second server 23 in Figure 4. The second server 23 can push updates to the first electronic device and present the target task data through the first target application installed on the first electronic device or the target system interface.

[0203] The target task data can be any data generated by the first target application. In one embodiment, the target task data is real-time task data generated by the first target application, and the real-time task data corresponds to a real-time task. For example, a real-time task is an activity initiated by a user, such as travel, food delivery, navigation, flights, high-speed rail, etc. In one example, the target task data is data related to a user's travel itinerary executed through a travel application, such as real-time data. Real-time data can be understood as data that includes real-time updates. The travel itinerary-related data may include images or text data such as vehicle type information, vehicle location information, and vehicle arrival time information.

[0204] In one embodiment, the target task data can be output on the first target system interface by display, voice broadcast, or a combination of display and voice broadcast.

[0205] In one embodiment, a first target task window is displayed on the first target system interface, and the first target task window displays target task data. For example, continuing to refer to Figure 5A, the first target task window is a first real-time window 53, displayed on the notification center interface 52. The first real-time window 53 displays real-time data of the "Travel Application," which may include data formats such as icons, text, and graphics. The real-time data may include at least one of vehicle type information, vehicle location information, and vehicle arrival time information. It is understood that in some embodiments, the notification center interface 52 may also include other task windows to display task data or notifications from other applications.

[0206] In one embodiment, the target task data can be defined in a data format, or other formats can be defined as needed. The target task data may include icon data, main text data, secondary text data, extended area data, and auxiliary area data, which are displayed in different areas of the live view window. For example, in Figure 5A, the first live view window 53 displays the live view data for the "Travel Application". For instance, in the HarmonyOS operating system, icon data can be obtained from the Bundle Management Service (BMS), while the main text data, secondary text data, and extended area data are provided by third-party developers. The auxiliary area data can be obtained from the cloud via a link provided by the developer. Regarding the implementation of the live view window, data can be transmitted using the desktop screen recording software LiveView.

[0207] In some embodiments, the first target system interface may also be a lock screen interface, a desktop, etc. For example, referring to FIG5B, which is a schematic diagram of the lock screen interface of the first electronic device provided in an embodiment of this application, the display screen 130 displays the lock screen interface 56, and the first live view window 53 is located on the lock screen interface 56. For example, referring to FIG5C, which is a schematic diagram of the desktop interface of the first electronic device provided in an embodiment of this application, the display screen 130 displays the desktop interface 57, and the first live view window 53 is located on the desktop interface 57.

[0208] In one embodiment, the first electronic device is a foldable screen phone, which may include multiple displays, and the first target system interface may be an interface on any display of the foldable screen phone.

[0209] The task data sharing method in this embodiment further includes step S540, in which the first electronic device, in response to the first operation on the target task data, generates sharing link information corresponding to the target task data.

[0210] In specific implementation, the sharing link information may include a URL (Uniform Resource Locator) format link to the target task data, identification information of the target task data, and supplementary descriptive text information. In one embodiment, the target task data is real-time task data, specifically the real-time data corresponding to a real-time task. In this case, the identification information can be an ID (Identity Document) used to uniquely identify a real-time task, such as a string like "bb4d786633053a0b9c0da20d54ea7e38e8776da4". Specifically, the sharing link information can be generated based on deep links. It should be noted that the identification information can be carried in the sharing link information, but it is not necessarily displayed. For example, the content of the sharing link information could be: "Real-time travel sharing from Li Si's mobile phone, you can click the following link to follow: deeplink: / / v.notifi....12mqE: / ".

[0211] The first operation can be a gesture operation or a voice control operation. For example, the first operation can be a touch operation on the first target system interface, such as a touch operation on the display area where the target task data is located, such as any operation or combination of click, long press, and swipe. In one embodiment, the first operation can also be an operation performed on controls related to the target task data. It is understood that the generated sharing link information can be displayed on the display interface or not. The interface displaying the sharing link information can be the system interface or the interface of the application sending the sharing link information. It should be noted that subsequent operations similar to the first operation in this embodiment can be either gesture operations or voice control operations.

[0212] In one embodiment, as shown in FIG6, S540 specifically includes:

[0213] S542, in response to a first operation on target task data, the first electronic device displays a first display area on the display screen of the first electronic device.

[0214] In specific implementation, taking the target task data displayed in the first target task window as an example, the first display area can include one or more options related to the first target task window. The first display area can be displayed under any display background of the first target system interface, and the rest of the background can be blurred when displayed. For example, as shown in FIG5E, FIG5E is a front view of the first electronic device displaying the first display area provided in the embodiment of this application. In the figure, the first display area 55 includes options such as: "Live status of the travel application", "Close the live status of this application", "Share", and more settings. Among them, the "Live status of the travel application" is a description of the live data in the first live status window 53, "Close the live status of this application" and "Share" are operation options, and "More settings" are general options, which can be expanded to include more options after clicking.

[0215] In one embodiment, the first operation is an operation performed on controls related to the target task data. The controls related to the target task data can be displayed through operations on the first target task window. For example, as shown in Figures 5D and 5E, Figure 5D is a front view of the first electronic device provided in this embodiment displaying the first live view window and option controls. In the figure, the first operation is a click operation on the option control 54 corresponding to the first live view window 53. When performing a leftward swipe operation on the first live view window 53 as shown in the figure, at least the option control 54 can be displayed on the right side of the first live view window 53.

[0216] S544, the first electronic device, in response to a first selection operation of a target option in the first display area, generates sharing link information corresponding to the target task data.

[0217] In the specific implementation process, continuing as shown in Figure 5E, the target option is the "Share" option in the first display area, and the position of the "Share" option in the first display area 55 is not restricted. The first selection operation can also be a touch operation on the first target system interface, such as a touch operation on the display area where the target task data is located, such as any operation or combination of click operation, long press operation, swipe operation, etc.

[0218] The task data sharing method in this embodiment further includes step S560, in which the first electronic device, in response to the second operation for the first electronic device, sends the sharing link information to the second electronic device.

[0219] In practice, the second operation can be a touch operation on the interface of the first target system, such as a touch operation on the display area where the target task data is located, including any operation or combination of click, long press, and swipe. Specifically, after generating the share link information, the second operation can be an operation on the share link information displayed on the screen, or an operation on the interface of the application that sends the share link information.

[0220] In one embodiment, the first electronic device can send the sharing link information to the second electronic device through any communicative application installed on both the first and second electronic devices. In another embodiment, the sharing link information can be sent to the second electronic device through a second target application. In this embodiment, the second target application can be a third-party application (e.g., a social application), and the second target application differs from the first target application. Sending the sharing link information directly through an existing application is quick and convenient.

[0221] In one embodiment, in response to a first operation on target task data, the first electronic device, in addition to generating the target task data, directly jumps to the first application interface of the second target application, that is, designates the second target application as the default application for sending the sharing link information. In one embodiment, the first application interface can be the interface for selecting contacts in a social application, or it can be a dialogue interface with a certain contact. In this embodiment, the second operation can be a click operation on a control displayed in the first application interface. For example, as shown in FIG5F, FIG5F is a front view of the first electronic device displaying the first application interface provided in this application embodiment. In the figure, the first application interface 58 is a dialogue interface with "Zhang San", and the dialog box displays the sharing link information in the aforementioned embodiment. The figure also shows the user's finger clicking the "send" control on the first application interface 58 (i.e., the second operation). In response to the click operation on the "send" control, the sharing link information is sent to the second target application in Zhang San's second electronic device.

[0222] In one embodiment, S544 specifically includes: in response to a first selection operation on a target option in a first display area, the first electronic device generates sharing link information corresponding to the target task data and displays a second display area on the display screen of the first electronic device; correspondingly, S560 specifically includes: in response to a second selection operation on a target application icon in the second display area, the first electronic device sends the sharing link information to the second electronic device through the second target application; wherein, the target application icon is the icon corresponding to the second target application.

[0223] In specific implementation, the second display area can be a response display to the first selection operation, that is, it can be displayed based on a click operation on the "Share" option in the first display area. The position of the second display area on the display screen is not limited and can be located anywhere on the display screen. The second display area can include multiple application icons, and the second selection operation can be a selection operation on any one of the multiple application icons. In one embodiment, the second selection operation can also be a touch operation on the first target system interface, such as a touch operation on the display area where the target task data is located, such as any operation or combination of click operation, long press operation, swipe operation, etc.

[0224] For example, as shown in Figure 5G, which is a front view of a second display area displayed on a first electronic device according to an embodiment of this application, the second display area 60 is displayed near the bottom of the display screen 130. The second display area 60 includes multiple application icons: first application, second application, third application, fourth application, fifth application, etc. The target application icon can be any one of them; for example, the target application icon is the first application. The figure also shows a user's finger clicking on the target application icon (first application) in the second display area 60 (i.e., a second selection operation).

[0225] The task data sharing method in this embodiment further includes step S580, in which the second electronic device responds to a third operation on the sharing link information and outputs the target task data on the second target system interface.

[0226] In the specific implementation process, the various implementation methods for the first electronic device to send the sharing link information to the second electronic device have been described in detail in the previous steps. The second electronic device only needs to receive the sharing link information in the appropriate way, which will not be repeated here.

[0227] Similar to the first target system interface in the first electronic device, the second target system interface can also refer to the software involved in the operating system itself, such as the notification center interface, desktop, lock screen interface, etc. For specific implementation methods, please refer to the first target system interface in the foregoing embodiments, which will not be repeated here.

[0228] The third operation can be any operation on the sharing link information displayed on the screen 130 of the second electronic device, as long as it can trigger the output of target task data on the second target system interface. For example, click operation, swipe operation, long press operation, etc., or voice control, etc.

[0229] For example, continuing the example of sending sharing link information through a second target application in the foregoing embodiments, as shown in Figure 5H, Figure 5H is a front view of the second electronic device displaying the second application interface provided in this application embodiment. Taking a mobile phone as an example, the second application interface 59 in the figure is the dialogue interface of the second target application, specifically the chat interface with Li Si, in which the sharing link information is displayed in the chat history. The third operation is the finger clicking operation on the sharing link information as shown in the figure. After clicking the sharing link information, it can directly jump to the second target system interface, and the target task data is output on the second target system interface.

[0230] The target task data output on the second target system interface can be displayed, broadcast via voice, or a combination of both. In one embodiment, similar to the first target task window displayed on the first target system interface of the first electronic device, the second electronic device outputs the target task data by displaying the second target task window corresponding to the target task data on the second target system interface. For example, see Figure 5I, which is a schematic diagram of the first and second electronic devices displaying target task data according to an embodiment of this application. It should be understood that Figure 5I does not show the content displayed by the first and second electronic devices at the same time. In one embodiment, the content displayed by the first and second electronic devices at the same time should be the same or similar. In one embodiment, the task data displayed by the second electronic device at the same time is slightly later than the task data displayed by the first electronic device. The content displayed by the first electronic device in the figure is the same as that in Figure 5A, that is, the first real-time window 53 is displayed on the first target system interface. The travel status in the first real-time window 53 is displayed as "The driver is expected to arrive in 5 minutes", that is, it is in the state of waiting for the vehicle to arrive at the starting point. The travel progress bar in the first real-time window 53 also shows that the vehicle has not yet arrived at the starting point. The task data sharing method of the aforementioned embodiment is executed based on the first electronic device and the second electronic device. In the figure, the second target system interface of the second electronic device displays the target task data shared by the first electronic device, and displays it in the form of a second live view window 61. After a period of time following the sharing by the first electronic device, the status in the second live view window 61 has changed to display the words "In progress from the starting point to the destination". The progress bar in the second live view window 61 also shows that the vehicle has traveled a certain distance from the starting point. In addition, the second target system interface of the second electronic device also displays other notifications such as notification 5 and notification 6.

[0231] It should be noted that there are multiple ways to transfer the target task data from the first electronic device to the second device. This can be achieved through direct end-to-end transmission between the two devices, such as via Wi-Fi Direct, Bluetooth, or NFC. Alternatively, any third-party device can be used as an intermediary, for example, by using the first server.

[0232] Therefore, in the above embodiments, both the first electronic device and the second electronic device realize the output and sharing of task data generated by the first target application in the system interface, realizing system-level sharing of task data in the electronic device, which is simple to operate and has a better user experience.

[0233] In one embodiment, a first target application is installed on a first electronic device, while the first target application is not installed on a second electronic device. In this case, even though the first target application is not installed on the second electronic device, the second electronic device can still display the live sharing of the first target application from the first electronic device on its system interface. Because system-level sharing is implemented, output via sharing is still possible on the second electronic device even when the first target application is not installed.

[0234] In one embodiment,

[0235] S540 specifically includes: the first electronic device responding to the first operation on the target task data, sending a first message about the target task data to the first server, and generating sharing link information corresponding to the target task data;

[0236] In a specific implementation, the first server can be the first server 24 shown in Figure 4. In response to a first operation targeting the target task data, the first electronic device, in addition to generating sharing link information, also sends a first message about the target task data to the first server. The first message can be any message related to the target task data, including descriptive information about the target task data and data identification information of the target task data. The first message enables the first server 24 to identify or obtain the target task data. For example, the target task data can be obtained from the second server 23 of the first target application based on the first message; or, if the first electronic device has a backup on a third-party device, it can be obtained from the backup third-party device based on the first message. This ensures that the first server 24 at least receives the first message and may obtain and store the target task data. In this embodiment, a separate data storage space can be set up in the first server 24 to store such target task data.

[0237] S560, specifically includes:

[0238] In response to a third operation concerning the shared link information, the second electronic device receives a second message from the first server regarding the target task data.

[0239] In the specific implementation process, since the first server receives at least the first message, which is a message related to the target task data, and the shared link information is a link corresponding to the target task data, in response to the third operation on the shared link information, at least the second message about the target task data can be obtained from the first server. The second message can be generated based on the first message or based on the target task data. The second message can be any message related to the target task data, and may include descriptive information about the target task data or data identification information about the target task data.

[0240] The second electronic device outputs target task data on the second target system interface based on the second message.

[0241] In specific implementation, the second electronic device can obtain target task data from the second server of the first target application based on the second message; alternatively, if the first electronic device has a backup on a third-party device, the second electronic device can obtain the data from the backup third-party device based on the second message. In one embodiment, the second electronic device can also obtain target task data from the first server based on the second message.

[0242] In one embodiment, as shown in FIG7, the second electronic device, in response to a third operation concerning the sharing link information, receives a second message from the first server regarding target task data, specifically including:

[0243] S561, in response to a third operation concerning the shared link information, the second electronic device sends a data retrieval request to the first server.

[0244] The data acquisition request includes device information of the second electronic device. In practice, the data acquisition request may include an access token, which can contain the device information of the second electronic device. The data acquisition request can also take other forms, as long as it includes device information. Furthermore, since the data acquisition request is generated based on the shared link information, it also carries information related to the target task data.

[0245] S562, in response to the data acquisition request sent by the second electronic device, the first server sends a second message about the target task data to the second electronic device corresponding to the device information.

[0246] In the specific implementation process, after receiving a data acquisition request, the first server can associate the device information with the target task data, thereby enabling it to send a second message about the target task data to the second electronic device corresponding to the associated device information.

[0247] S563, the second electronic device receives a second message regarding target mission data.

[0248] Understandably, data acquisition requests can be used to accurately push data to target tasks.

[0249] In one embodiment, the second electronic device may also respond to a third operation regarding the sharing link information by directly obtaining the target task data from the first server. It is understood that remote sharing between the first and second electronic devices can be achieved through the first server.

[0250] In one embodiment, referring to Figure 8, after outputting the target task data on the second target system interface, the method of this embodiment further includes:

[0251] S564, the first server receives the target task update data of the target task data.

[0252] In specific implementation, the target task update data refers to updates to at least a portion of the target task data. Taking the real-time task data of the "travel application" in the aforementioned embodiment as an example, the target task update data can include updated text data and updated graphic data, thereby updating vehicle location information and vehicle arrival time information. Specifically, the first server can receive update data pushed by the second server or by the first electronic device. It should be noted that since the second server can push the target task update data to the first electronic device to update the data of the first target application, the first server can also receive update data from the first electronic device.

[0253] In one embodiment, the first server receives target task update data, including:

[0254] The first server receives target task update data pushed by the second server; wherein, the second server is the application server corresponding to the first target application.

[0255] It is understandable that the application server can be the second server 23 in Figure 4, directly receiving the update data pushed by the second server, resulting in less latency and smoother device operation.

[0256] S565, the first server pushes a third message about the target task update data to the second electronic device corresponding to the device information;

[0257] In practice, the third message can be any message related to the target task update data, including descriptive information about the target task update data and data identification information about the target task update data.

[0258] S566, the second electronic device receives a third message regarding the updated target task data and updates the second target task data according to the third message.

[0259] In the specific implementation process, similar to the second message mentioned above, the way the second electronic device obtains the target task update data based on the third message can also refer to the implementation method of the second electronic device obtaining the target task data based on the second message in the aforementioned embodiment, which will not be repeated here.

[0260] In one embodiment, multiple second electronic devices are included. Each second electronic device sends a data acquisition request to the first server, including device information, and each second electronic device outputs target task data. Specifically, the first electronic device can simultaneously send sharing link information to multiple second electronic devices, and users of the multiple second electronic devices can send data acquisition requests by responding to the sharing link information.

[0261] In one embodiment, S565 specifically includes: the first server pushing a third message about the target task update data to the second electronic device corresponding to each device information.

[0262] In this specific implementation, the scenario is one first electronic device to multiple second electronic devices. With the help of a first server, one-to-many remote sharing between terminals in the live stream window can be achieved, and the live stream tasks in the live stream window can be updated and displayed in real time on the system interface. This allows users to conveniently follow other users' live streams in real time, providing a better user sharing experience.

[0263] In one embodiment, after the second electronic device outputs the second target task window on the second target system interface, the method further includes the following steps:

[0264] When the first preset condition is met, the sharing task corresponding to the second target task window is terminated; wherein the first preset condition includes at least one of the following: the second electronic device receives task termination information, the second electronic device receives a fourth operation from the user on the second target task window, and the output of the second target task window reaches a preset time.

[0265] In the specific implementation process, this embodiment shows several ways to end the second target task window, as follows:

[0266] The first preset condition is that the second electronic device receives task completion information. It can be understood that the shared task in the second target task window is based on target task data generated by the first target application. For example, if the target task data is real-time data, corresponding to a real-time task, then the real-time task has an end time, and task completion information can be generated upon completion. The second electronic device can obtain the task completion information from a second server, a first server, or directly from the first electronic device. For example, the completion information for a travel task could be "Passenger has arrived at the destination" or "Passenger has completed payment," etc.

[0267] The first preset condition is that the second electronic device receives a fourth operation from the user targeting the second target task window. This fourth operation can still be a click, swipe, or other similar action on the second target task window, without restriction. This condition allows the user to actively end the sharing task, avoiding unnecessary resource consumption caused by the inability to end the sharing task in situations where it could be temporarily terminated. This provides users with more options and a better user experience.

[0268] The first preset condition is that the output of the second target task window reaches a preset time. The preset time can be set according to different applications or different real-time tasks within an application. For example, the preset time can be the normal running time of the real-time task, or it can be a time exceeding the normal running time. The normal running time can be determined by the average of the task's historical running times; for example, if the normal running time is 30 minutes, the preset time can be 30 minutes, or it can be 35 minutes, 40 minutes, etc. It is understood that ending within the preset time can avoid resource waste, reduce phone battery and operating resource consumption, and improve the user experience.

[0269] Figure 9 is a timing diagram illustrating a task data sharing method provided in an embodiment of this application. In this embodiment, the target task data is real-time data, which is a real-time task running in a first target application. Correspondingly, both the first target system interface and the second target system interface are notification center interfaces, with the first target task window being a first real-time window and the second target task window being a second real-time window.

[0270] The second server includes an application cloud, which is the application cloud corresponding to the first target application. In some embodiments, the second server is responsible for pushing data related to the first target application to the first electronic device, the second electronic device, the first server, etc.

[0271] The first server includes data storage space, which can be used to temporarily store live data for live tasks.

[0272] The first notification center and the second notification center are programs corresponding to the system functions in the first electronic device and the second electronic device, respectively, and are responsible for providing the first target system interface and the second target system interface.

[0273] The first social application and the second social application are the same third-party applications in the first electronic device and the second electronic device, respectively, corresponding to the second target application in the aforementioned embodiment, and are used to provide a sharing channel for sharing link information.

[0274] Notification services are system programs responsible for sending and receiving system notifications, messages, and data. For example, in HarmonyOS, ANS (Advanced Notification Service) is the system notification service.

[0275] The execution process of the task data sharing method in this embodiment will be described below with reference to Figure 9.

[0276] In one embodiment, the following steps are included:

[0277] S10, Start Live Task. The live task is started by user A's trigger operation on the first target application on the first electronic device. Alternatively, it can be understood that the first target application on the first electronic device receives user A's trigger operation and starts the live task.

[0278] S30, Displaying Live Data. In the first electronic device, after a live task is started, the live data corresponding to the live task is displayed on the notification center interface of the first notification center. For example, the notification center interface of the first notification center includes a first live window, in which the live data is displayed. Therefore, step S30 is a specific implementation of step S520 in the aforementioned embodiment.

[0279] S40, the first notification center receives the first operation from user A. Specifically, this is achieved by user A performing the first operation on the first live window through the notification center interface of the first notification center.

[0280] S60, Generate sharing link information. Specifically, the first notification center responds to the first operation and generates sharing link information. Therefore, step S60 is a specific implementation of step S540 in the aforementioned embodiment.

[0281] S90, the first social application receives a second operation from user A. The second operation is the second operation in step S560 of the aforementioned embodiment.

[0282] S100, the first social application sends a sharing link to the second social application. Specifically, in response to the second operation, the first social application sends a sharing link to the second social application. Therefore, step S100 is a specific implementation of step S560 in the aforementioned embodiment.

[0283] S110, the second social application receives a third operation from user B regarding the shared link information. Specifically, after receiving the shared link information, the second social application can display it within the application. User B performs a third operation on the shared link information within the second social application, thereby enabling the second social application to receive user B's third operation regarding the shared link information.

[0284] S160, display live data. Specifically, in response to the third operation, live data is displayed on the notification center interface of the second notification center. For example, the notification center interface of the second notification center includes a second live window, in which the live data is displayed. Therefore, step S160 is a specific implementation of step S580 in the aforementioned embodiment.

[0285] In one embodiment, between steps S10 and S30, the following steps are further included:

[0286] S20, Send live data to the first notification center. It is understood that after the first target application starts the live task, there are multiple ways to send live data to the first notification center. For example, the live data can be pushed to the first notification center via a first server or a second server. In this embodiment, the live task can also be sent directly from the first target application to the first notification center locally within the first electronic device, which is more efficient and provides a better user experience.

[0287] In one embodiment, between steps S60 and S90, the following steps are further included:

[0288] S80: Send the sharing link information to the first social application. It is understood that there are multiple ways to send the sharing link information via the first social application on the first electronic device, such as copying and pasting the generated sharing link information into the first social application through interaction with user A. In this embodiment, sending it directly from the first notification center to the first social application via S80 reduces user operations and further improves the user experience.

[0289] In one embodiment, after step S40, the method further includes:

[0290] S50 sends live data to the first server. The live data sent to the first server can then be pushed to the second electronic device.

[0291] In one implementation, after step S50, the method further includes:

[0292] The S70 stores real-time data in a data storage space. To enable the push of real-time data based on device information, a separate data storage space is needed to store the real-time data, thus waiting for a data retrieval request before pushing it.

[0293] It is understandable that, as described in the foregoing embodiments, live data can be directly sent from the first electronic device to the second electronic device, but remote sharing is difficult to achieve, and one-to-many sharing is also challenging. In this embodiment, remote sharing can be achieved through the first server, and one-to-many sharing can be realized.

[0294] In one implementation, after step S100, the method further includes:

[0295] S120, Send information related to the sharing link to the notification service.

[0296] S130, send a data acquisition request (including device information and sharing link information) to the first server.

[0297] Specifically, in order to obtain live data from the first server, it is necessary to send relevant information about the live data (i.e., information related to the sharing link information) and the device information of the second electronic device to the first server. In this embodiment, this is done through the system's notification service, which can carry the device information of the second electronic device and send it to the first server as a data acquisition request. Therefore, it is necessary to first send the information related to the sharing link information to the notification service, and then include the device information in the notification service. Therefore, S120 and S130 can be a specific implementation of S561 in the aforementioned embodiment.

[0298] Furthermore, it also includes:

[0299] In step S140, the first server transmits live data to the notification service of the second electronic device based on the device information. Specifically, the transmission of live data can also be achieved through a notification service. S140 can be a specific implementation of step S562 in the aforementioned embodiment.

[0300] In step S150, the second notification center receives the live data sent by the notification service. After receiving the live data, the second notification center displays it. Therefore, S150 can be a specific implementation of S563 in the aforementioned embodiment.

[0301] In one implementation, after step S160, the method further includes:

[0302] S202, the updated live data is displayed in the second notification center. The live data can be updated in real time to provide a more accurate understanding of the situation. It is understood that there can be multiple methods to display the updated live data, such as directly pushing the updated live task data through the second server, pushing the updated live task data through the first server, or directly receiving the updated live task data from the first electronic device and updating accordingly. Therefore, S202 can be a specific implementation of S566 in the aforementioned embodiment.

[0303] In one implementation, before step S202, the method further includes:

[0304] In step S170, the first server receives updated data from the live task. Specifically, the updated data comes from a push notification from the second server. Therefore, S170 can be a specific implementation of S564 in the aforementioned embodiment.

[0305] S180, query device information associated with real-time data. Specifically, when a data acquisition request is sent to the first server, a relationship between real-time data and device information can be established. Therefore, when data is updated, the device information associated with the real-time data can be queried.

[0306] S201, the updated data for the live task is pushed to the second notification center. Specifically, the updated data can be pushed directly based on device information. In one embodiment, the push can also be made through a notification service (not shown in the figure). Therefore, S201 can be a specific implementation of S565 in the aforementioned embodiment.

[0307] In one implementation, after step S180, the method further includes:

[0308] S190, the updated data of the live mission is pushed to the first notification center.

[0309] The S200 displays updated live data in the first notification center.

[0310] The above is the execution process of the task data sharing method shown in Figure 9.

[0311] Therefore, this embodiment provides a method for sharing live tasks, which shares a first live window displayed on one terminal (e.g., a first electronic device) to another terminal (e.g., a second electronic device) at the system level for live window display, and can actively update the live window in real time through push from the first server, so as to achieve the effect of actively reminding the user of the live status on the receiving party.

[0312] The above embodiments illustrate the process of at least two of the first electronic device, the second electronic device, and the first server participating in the execution of a task data sharing method. The following embodiments illustrate the execution of the task data sharing method from only one side of the first electronic device, the second electronic device, and the first server.

[0313] As shown in Figure 10, Figure 10 illustrates a task data sharing method provided in an embodiment of this application. As shown, the method is executed by a first electronic device and includes:

[0314] S102, output target task data on the first target system interface; wherein, the target task data is the task data of the first target application in the first electronic device.

[0315] In specific implementation, the first target system interface is the system interface on the first electronic device, which can be used to display target task data. It is understood that, according to the description of the software architecture of the electronic device (e.g., a mobile phone) in the foregoing embodiments, the software architecture of the electronic device includes the operating system and various applications in the application layer of the operating system. The various applications in the application layer can be divided into system applications and extended / third-party applications. In one embodiment, system applications can be further divided into software involved in the operating system itself and software included with the operating system. Software involved in the operating system itself may include the desktop, control bar, notifications and status bar (notification center), settings, etc., while software included with the operating system may include telephone, SMS, browser, photo album, calculator, calendar, clock, etc. It should be noted that the names of software may differ in different operating systems, but their functionalities are essentially the same. For example, the notification center in the iOS mobile operating system is also called the notification and status bar in the Android and HarmonyOS operating systems.

[0316] In this embodiment, the first target system interface refers to the software involved in the operating system itself. For example, the first target system interface can be the interface where the mobile phone's notification center (the name in the iOS system) is located, or it can be the interface where the notification and status bar are located in the Android operating system and the HarmonyOS operating system. This interface is also referred to as the notification center interface in this embodiment. In one embodiment, the notification center interface may display the words "Notification Center" or it may not display them. For example, as shown in FIG5A, FIG5A is a schematic diagram of the notification center interface of the first electronic device provided in this application embodiment. The first electronic device is a mobile phone. In the figure, the mobile phone includes a display screen 130, and the display screen 130 displays the notification center interface 52. As shown in FIG5A, it is a front view of the mobile phone. By touching the top left side of the mobile phone's display screen and sliding down from the top edge, one can switch to the notification center interface 52 shown in FIG5A.

[0317] The target task data refers to the task data of the first target application in the first electronic device. The first target application can be software within the first electronic device, such as third-party applications for social networking, navigation, or travel, or software built into the operating system, such as alarm clocks or timers. In one embodiment, the first target application is an extended application / third-party application, for example, a travel application or map software. As an extended application / third-party application, the first target application has a corresponding application cloud server, exemplarily the second server 23 in Figure 4. The second server 23 can push updates to the first electronic device and present the target task data through the first target application installed on the first electronic device or the target system interface.

[0318] The target task data can be any data generated by the first target application. In one embodiment, the target task data is real-time task data generated by the first target application, and the real-time task data corresponds to a real-time task. For example, a real-time task is an activity initiated by a user, such as travel, food delivery, navigation, flights, high-speed rail, etc. In one example, the target task data is data related to a user's travel itinerary executed through a travel application, such as real-time data. Real-time data can be understood as data that includes real-time updates. The travel itinerary-related data may include images or text data such as vehicle type information, vehicle location information, and vehicle arrival time information.

[0319] In one embodiment, the target task data can be output on the first target system interface by display, voice broadcast, or a combination of display and voice broadcast.

[0320] In one embodiment, a first target task window is displayed on the first target system interface, and the first target task window displays target task data. For example, continuing to refer to Figure 5A, the first target task window is a first real-time window 53, displayed on the notification center interface 52. The first real-time window 53 displays real-time data of the "Travel Application," which may include data formats such as icons, text, and graphics. The real-time data may include at least one of vehicle type information, vehicle location information, and vehicle arrival time information. It is understood that in some embodiments, the notification center interface 52 may also include other task windows to display task data or notifications from other applications.

[0321] In one embodiment, the target task data can be defined in a data format, or other formats can be defined as needed. The target task data may include icon data, main text data, secondary text data, extended area data, and auxiliary area data, which are displayed in different areas of the live view window. For example, in Figure 5A, the first live view window 53 displays the live view data for the "Travel Application". For instance, in the HarmonyOS operating system, icon data can be obtained from the Bundle Management Service (BMS), while the main text data, secondary text data, and extended area data are provided by third-party developers. The auxiliary area data can be obtained from the cloud via a link provided by the developer. Regarding the implementation of the live view window, data can be transmitted using the desktop screen recording software LiveView.

[0322] In some embodiments, the first target system interface may also be a lock screen interface, a desktop, etc. For example, referring to FIG5B, which is a schematic diagram of the lock screen interface of the first electronic device provided in an embodiment of this application, the display screen 130 displays the lock screen interface 56, and the first live view window 53 is located on the lock screen interface 56. For example, referring to FIG5C, which is a schematic diagram of the desktop interface of the first electronic device provided in an embodiment of this application, the display screen 130 displays the desktop interface 57, and the first live view window 53 is located on the desktop interface 57.

[0323] In one embodiment, the first electronic device is a foldable screen phone, which may include multiple displays, and the first target system interface may be an interface on any display of the foldable screen phone.

[0324] The task data sharing method in this embodiment further includes: S104, in response to the first operation on the target task data, generating sharing link information corresponding to the target task data.

[0325] In specific implementation, the sharing link information may include a URL (Uniform Resource Locator) format link to the target task data, identification information of the target task data, and supplementary descriptive text information. In one embodiment, the target task data is real-time task data, specifically the real-time data corresponding to a real-time task. In this case, the identification information can be an ID (Identity Document) used to uniquely identify a real-time task, such as a string like "bb4d786633053a0b9c0da20d54ea7e38e8776da4". Specifically, the sharing link information can be generated based on deep links. It should be noted that the identification information can be carried in the sharing link information, but it is not necessarily displayed. For example, the content of the sharing link information could be: "Real-time travel sharing from Li Si's mobile phone, you can click the following link to follow: deeplink: / / v.notifi....12mqE: / ".

[0326] The first operation can be a touch operation on the first target system interface, such as a touch operation on the display area where the target task data is located, including any operation or combination of click, long press, and swipe. In one embodiment, the first operation can also be an operation on controls related to the target task data. It is understood that the generated sharing link information may or may not be displayed on the display screen. The interface displaying the sharing link information can be the system interface or the interface of the application that sent the sharing link information.

[0327] In one embodiment, as shown in FIG11, S104 specifically includes:

[0328] S124, in response to a first operation on the target task data, displays a first display area;

[0329] S144, in response to the first selection operation of the target option in the first display area, generate the sharing link information corresponding to the target task data.

[0330] This embodiment describes an interface interaction scheme for generating target task data. In specific implementation, taking the target task data displayed in the first target task window as an example, the first display area can include one or more options related to the first target task window. The first display area can be displayed under any display background of the first target system interface, and the rest of the background can be blurred during display. For example, as shown in Figure 5E, Figure 5E is a front view of the first electronic device displaying the first display area provided in this application embodiment. In the figure, the first display area 55 includes options such as: "Live feed of the travel application", "Close this application's live feed", "Share", and more settings. The "Live feed of the travel application" describes the live data within the first live feed window 53; "Close this application's live feed" and "Share" are operation options; and "More settings" are general options, which can be expanded by clicking.

[0331] In one embodiment, the first operation is an operation performed on controls related to the target task data. The controls related to the target task data can be displayed through operations on the first target task window. For example, as shown in Figures 5D and 5E, Figure 5D is a front view of the first electronic device provided in this embodiment displaying the first live view window and option controls. In the figure, the first operation is a click operation on the option control 54 corresponding to the first live view window 53. When performing a leftward swipe operation on the first live view window 53 as shown in the figure, at least the option control 54 can be displayed on the right side of the first live view window 53.

[0332] In the specific implementation process, continuing as shown in Figure 5E, the target option is the "Share" option in the first display area, and the position of the "Share" option in the first display area 55 is not restricted. The first selection operation can also be a touch operation on the first target system interface, such as a touch operation on the display area where the target task data is located, such as any operation or combination of click operation, long press operation, swipe operation, etc.

[0333] The task data sharing method in this embodiment further includes: S106, in response to a second operation on the first electronic device, sending sharing link information to the second electronic device; wherein the sharing link information is used by the second electronic device to output target task data.

[0334] In practice, the second operation can be a touch operation on the interface of the first target system, such as a touch operation on the display area where the target task data is located, including any operation or combination of click, long press, and swipe. Specifically, after generating the share link information, the second operation can be an operation on the share link information displayed on the screen, or an operation on the interface of the application that sends the share link information.

[0335] In one embodiment, the first electronic device can send the sharing link information to the second electronic device through any communicative application installed on both the first and second electronic devices. In another embodiment, the sharing link information can be sent to the second electronic device through a second target application. In this embodiment, the second target application can be a third-party application (e.g., a social application), and the second target application differs from the first target application. Sending the sharing link information directly through an existing application is quick and convenient.

[0336] In one embodiment, in response to a first operation on target task data, the first electronic device, in addition to generating the target task data, directly jumps to the first application interface of the second target application, that is, designates the second target application as the default application for sending the sharing link information. In one embodiment, the first application interface can be the interface for selecting contacts in a social application, or it can be a dialogue interface with a certain contact. In this embodiment, the second operation can be a click operation on a control displayed in the first application interface. For example, as shown in FIG5F, FIG5F is a front view of the first electronic device displaying the first application interface provided in this application embodiment. In the figure, the first application interface 58 is a dialogue interface with "Zhang San", and the dialog box displays the sharing link information in the aforementioned embodiment. The figure also shows the user's finger clicking the "send" control on the first application interface 58 (i.e., the second operation). In response to the click operation on the "send" control, the sharing link information is sent to the second target application in Zhang San's second electronic device.

[0337] In one embodiment, step S144 specifically includes:

[0338] In response to a first selection operation on a target option in the first display area, share link information corresponding to the target task data is generated and displayed in the second display area;

[0339] Accordingly, step S106 specifically includes: in response to a second selection operation on the target application icon in the second display area, sending the sharing link information to the second electronic device; wherein, the target application icon is the icon corresponding to the second target application.

[0340] In specific implementation, the second display area can be a response display to the first selection operation, that is, it can be displayed based on a click operation on the "Share" option in the first display area. The position of the second display area on the display screen is not limited and can be located anywhere on the display screen. The second display area can include multiple application icons, and the second selection operation can be a selection operation on any one of the multiple application icons. In one embodiment, the second selection operation can also be a touch operation on the first target system interface, such as a touch operation on the display area where the target task data is located, such as any operation or combination of click operation, long press operation, swipe operation, etc.

[0341] For example, as shown in Figure 5G, which is a front view of a second display area displayed on a first electronic device according to an embodiment of this application, the second display area 60 is displayed near the bottom of the display screen 130. The second display area 60 includes multiple application icons: first application, second application, third application, fourth application, fifth application, etc. The target application icon can be any one of them; for example, the target application icon is the first application. The figure also shows a user's finger clicking on the target application icon (first application) in the second display area 60 (i.e., a second selection operation).

[0342] It should be noted that there are multiple ways to transfer the target task data from the first electronic device to the second device. This can be achieved through direct end-to-end transmission between the two devices, such as via Wi-Fi Direct, Bluetooth, or NFC. Alternatively, any third-party device can be used as an intermediary, for example, by using the first server.

[0343] Therefore, in the above embodiments, both the first electronic device and the second electronic device realize the output and sharing of task data generated by the first target application in the system interface, realizing system-level sharing of task data in the electronic device, which is simple to operate and has a better user experience.

[0344] In one embodiment, a first target application is installed on a first electronic device, while the first target application is not installed on a second electronic device. In this case, even though the first target application is not installed on the second electronic device, the second electronic device can still display the live sharing of the first target application from the first electronic device on its system interface. Because system-level sharing is implemented, output via sharing is still possible on the second electronic device even when the first target application is not installed.

[0345] In one embodiment, S104 specifically includes:

[0346] In response to the first operation on the target task data, a first message about the target task data is sent to the first server, and the corresponding share link information for the target task data is generated.

[0347] In a specific implementation, the first server can be the first server 24 shown in Figure 4. In response to a first operation targeting the target task data, the first electronic device, in addition to generating sharing link information, also sends a first message about the target task data to the first server. The first message can be any message related to the target task data, including descriptive information about the target task data and data identification information of the target task data. The first message enables the first server 24 to identify or obtain the target task data. For example, the target task data can be obtained from the second server 23 of the first target application based on the first message; or, if the first electronic device has a backup on a third-party device, it can be obtained from the backup third-party device based on the first message. This ensures that the first server 24 at least receives the first message and may obtain and store the target task data. In this embodiment, a separate data storage space can be set up in the first server 24 to store such target task data.

[0348] In this embodiment, the first server participates in the sharing of target task data. Therefore, in one embodiment, S144 may also involve the first server participating in the sharing of target task data.

[0349] As shown in Figure 12, Figure 12 illustrates a task data sharing method provided in an embodiment of this application. As shown, this method is executed by a second electronic device and includes:

[0350] S107, receive sharing link information about target task data sent by the first electronic device; wherein, the target task data is the task data of the first target application in the first electronic device.

[0351] In practice, the second electronic device acts as a passive recipient, receiving the sharing link information according to the appropriate method. The sharing link information can be received through any communicative application installed on both the first and second electronic devices. In one embodiment, the sharing link information about target task data sent by the first electronic device is received through a second target application. In another embodiment, the second target application can be a third-party application (e.g., a social application), and the second target application is different from the first target application. Sending the sharing link information directly through an existing application is quick and convenient.

[0352] The target task data refers to the task data of the first target application in the first electronic device. The first target application can be software in the first electronic device, such as third-party applications for social networking, navigation, and travel, or software built into the operating system such as alarm clocks and timers. In one embodiment, the first target application is an extended application / third-party application, for example, a travel application or map software. As an extended application / third-party application, the first target application has a corresponding application cloud server, exemplarily, as shown by the second server 23 in Figure 4. The second server 23 can push updates to the first electronic device and present the target task data through the first target application installed on the first electronic device or the first target system interface.

[0353] The target task data can be any data generated by the first target application. In one embodiment, the target task data is real-time task data generated by the first target application, and the real-time task data corresponds to a real-time task. For example, a real-time task is an activity initiated by a user, such as travel, food delivery, navigation, flights, high-speed rail, etc. In one example, the target task data is data related to a user's travel itinerary executed through a travel application, such as real-time data. Real-time data can be understood as data that includes real-time updates. The travel itinerary-related data may include images or text data such as vehicle type information, vehicle location information, and vehicle arrival time information.

[0354] In one embodiment, the target task data can be output on the first target system interface by display, voice broadcast, or a combination of display and voice broadcast.

[0355] In one embodiment, a first target task window is displayed on the first target system interface, and the first target task window displays target task data. For example, continuing to refer to Figure 5A, the first target task window is a first real-time window 53, displayed on the notification center interface 52. The first real-time window 53 displays real-time data of the "Travel Application," which may include data formats such as icons, text, and graphics. The real-time data may include at least one of vehicle type information, vehicle location information, and vehicle arrival time information. It is understood that in some embodiments, the notification center interface 52 may also include other task windows to display task data or notifications from other applications.

[0356] The task data sharing method in this embodiment further includes step S108, which, in response to a third operation on the sharing link information, outputs target task data on the second target system interface of the second electronic device.

[0357] In the specific implementation process, the various implementation methods for the first electronic device to send the sharing link information to the second electronic device have been described in detail in the previous steps. The second electronic device only needs to receive the sharing link information in the appropriate way, which will not be repeated here.

[0358] Similar to the first target system interface in the first electronic device, the second target system interface can also refer to the software involved in the operating system itself, such as the notification center interface, desktop, lock screen interface, etc. For specific implementation methods, please refer to the first target system interface in the foregoing embodiments, which will not be repeated here.

[0359] The third operation can be any operation on the sharing link information displayed on the screen 130 of the second electronic device, as long as it can trigger the output of target task data on the second target system interface. For example, click operation, swipe operation, long press operation, etc., or voice control, etc.

[0360] For example, continuing the example of sending sharing link information through a second target application in the foregoing embodiments, as shown in Figure 5H, Figure 5H is a front view of the second electronic device displaying the second application interface provided in this application embodiment. Taking a mobile phone as an example, the second application interface 59 in the figure is the dialogue interface of the second target application, specifically the chat interface with Li Si, in which the sharing link information is displayed in the chat history. The third operation is the finger clicking operation on the sharing link information as shown in the figure. After clicking the sharing link information, it can directly jump to the second target system interface, and the target task data is output on the second target system interface.

[0361] The target task data can be output on the second target system interface through display, voice broadcast, or a combination of both. In one embodiment, similar to displaying a first target task window on the first target system interface in the first electronic device, the second electronic device outputs target task data by displaying a second target task window corresponding to the target task data on the second target system interface. Examples of displaying the second target task window corresponding to the target task data on the second target system interface can be found in Figures 5A to 5C, and will not be repeated here.

[0362] It should be noted that there are multiple ways to transfer the target task data from the first electronic device to the second device. This can be achieved through direct end-to-end transmission between the two devices, such as via Wi-Fi Direct, Bluetooth, or NFC. Alternatively, any third-party device can be used as an intermediary, for example, by using the first server.

[0363] In one embodiment, as shown in FIG13, S108 specifically includes:

[0364] S128, in response to the third operation on the shared link information, receive the second message about the target task data sent by the first server;

[0365] S148, based on the second message, output the target task data on the second target system interface of the second electronic device.

[0366] In the specific implementation process, since the first server receives at least the first message, which is a message related to the target task data, and the shared link information is a link corresponding to the target task data, in response to the third operation on the shared link information, at least the second message about the target task data can be obtained from the first server. The second message can be generated based on the first message or based on the target task data. The second message can be any message related to the target task data, and may include descriptive information about the target task data or data identification information about the target task data.

[0367] The second electronic device can obtain target task data from the second server of the first target application based on the second message; alternatively, if the first electronic device has a backup on a third-party device, the second electronic device can obtain the data from the backup third-party device based on the second message. In one embodiment, the second electronic device can also obtain target task data from the first server based on the second message.

[0368] In one embodiment, S128 specifically includes:

[0369] In response to a third operation concerning the shared link information, a data retrieval request is sent to the first server; wherein the data retrieval request includes device information of the second electronic device;

[0370] Receive a second message from the first server in response to the data retrieval request, containing data about the target task.

[0371] In practice, the data acquisition request includes device information of the second electronic device. The request may also include an access token, which can contain device information. Other forms of data acquisition requests are also acceptable, as long as they include device information. Furthermore, since the data acquisition request is generated based on shared link information, it also carries information related to the target task data. Upon receiving the data acquisition request, the first server can associate the device information with the target task data, thereby enabling the sending of a second message about the target task data to the second electronic device corresponding to the associated device information. It is understandable that the data acquisition request method allows for precise delivery of target task data.

[0372] In one embodiment, continuing as shown in FIG12, after S108, the method further includes:

[0373] S109, Receive a third message from the first server regarding the updated data of the target task, the updated data of the target task being the updated data of the target task; Update the target task data according to the third message.

[0374] In specific implementation, the target task update data refers to updates to at least a portion of the target task data. Taking the real-time task data of the "travel application" in the aforementioned embodiment as an example, the target task update data can include updated text data and updated graphic data, thereby updating vehicle location information and vehicle arrival time information. Specifically, the first server can receive update data pushed by the second server or by the first electronic device. It should be noted that since the second server can push the target task update data to the first electronic device to update the data of the first target application, the first server can also receive update data from the first electronic device.

[0375] The third message can be any message related to the target task update data, and may include descriptive information about the target task update data, or data identification information about the target task update data.

[0376] Similar to the second message mentioned above, the method by which the second electronic device obtains the target task update data based on the third message can also refer to the implementation method of the second electronic device obtaining the target task data based on the second message in the aforementioned embodiments, and will not be repeated here.

[0377] In one embodiment, if the second target system interface includes a second target task window, the second target task window can be updated directly based on the third message.

[0378] In one embodiment, after S108, the method of this embodiment further includes:

[0379] When the first preset condition is met, the sharing task corresponding to the second target task window is terminated; wherein the first preset condition includes at least one of the following: the second electronic device receives the task termination information pushed by the first server, the second electronic device receives the user's fourth operation on the second target task window, and the output of the second target task window reaches a preset time.

[0380] In the specific implementation process, this embodiment shows several ways to end the second target task window, as follows:

[0381] The first preset condition is that the second electronic device receives task completion information. It can be understood that the shared task in the second target task window is based on target task data generated by the first target application. For example, if the target task data is real-time data, corresponding to a real-time task, then the real-time task has an end time, and task completion information can be generated upon completion. The second electronic device can obtain the task completion information from a second server, a first server, or directly from the first electronic device. For example, the completion information for a travel task could be "Passenger has arrived at the destination" or "Passenger has completed payment," etc.

[0382] The first preset condition is that the second electronic device receives a fourth operation from the user targeting the second target task window. This fourth operation can still be a click, swipe, or other similar action on the second target task window, without restriction. This condition allows the user to actively end the sharing task, avoiding unnecessary resource consumption caused by the inability to end the sharing task in situations where it could be temporarily terminated. This provides users with more options and a better user experience.

[0383] The first preset condition is that the output of the second target task window reaches a preset time. The preset time can be set according to different applications or different real-time tasks within an application. For example, the preset time can be the normal running time of the real-time task, or it can be a time exceeding the normal running time. The normal running time can be determined by the average of the task's historical running times; for example, if the normal running time is 30 minutes, the preset time can be 30 minutes, or it can be 35 minutes, 40 minutes, etc. It is understood that ending within the preset time can avoid resource waste, reduce phone battery and operating resource consumption, and improve the user experience.

[0384] As shown in Figure 14, Figure 14 illustrates a task data sharing method provided in an embodiment of this application. As shown, this method is executed by a first server and includes:

[0385] S122, receive a first message about target task data sent by the first electronic device; wherein, the target task data is the task data of the first target application output on the first target system interface of the first electronic device;

[0386] In a specific implementation, the first server can be the first server 24 shown in Figure 4. In response to a first operation targeting the target task data, the first electronic device, in addition to generating sharing link information, also sends a first message about the target task data to the first server. The first message can be any message related to the target task data, including descriptive information about the target task data and data identification information of the target task data. The first message enables the first server 24 to identify or obtain the target task data. For example, the target task data can be obtained from the second server 23 of the first target application based on the first message; or, if the first electronic device has a backup on a third-party device, it can be obtained from the backup third-party device based on the first message. This ensures that the first server 24 at least receives the first message and may obtain and store the target task data. In this embodiment, a separate data storage space can be set up in the first server 24 to store such target task data.

[0387] The target task data refers to the task data of the first target application in the first electronic device. The first target application can be software in the first electronic device, such as third-party applications for social networking, navigation, and travel, or software built into the operating system such as alarm clocks and timers. In one embodiment, the first target application is an extended application / third-party application, for example, a travel application or map software. As an extended application / third-party application, the first target application has a corresponding application cloud server, exemplarily, as shown by the second server 23 in Figure 4. The second server 23 can push updates to the first electronic device and present the target task data through the first target application installed on the first electronic device or the first target system interface.

[0388] The target task data can be any data generated by the first target application. In one embodiment, the target task data is real-time task data generated by the first target application, and the real-time task data corresponds to a real-time task. For example, a real-time task is an activity initiated by a user, such as travel, food delivery, navigation, flights, high-speed rail, etc. In one example, the target task data is data related to a user's travel itinerary executed through a travel application, such as real-time data. Real-time data can be understood as data that includes real-time updates. The travel itinerary-related data may include images or text data such as vehicle type information, vehicle location information, and vehicle arrival time information.

[0389] In one embodiment, the target task data can be output on the first target system interface by display, voice broadcast, or a combination of display and voice broadcast.

[0390] In one embodiment, a first target task window is displayed on the first target system interface, and the first target task window displays target task data. For example, continuing to refer to Figure 5A, the first target task window is a first real-time window 53, displayed on the notification center interface 52. The first real-time window 53 displays real-time data of the "Travel Application," which may include data formats such as icons, text, and graphics. The real-time data may include at least one of vehicle type information, vehicle location information, and vehicle arrival time information. It is understood that in some embodiments, the notification center interface 52 may also include other task windows to display task data or notifications from other applications.

[0391] In one embodiment, the target task data can be defined in a data format, or other formats can be defined as needed. The target task data may include icon data, main text data, secondary text data, extended area data, and auxiliary area data, which are displayed in different areas of the live view window. For example, in Figure 5A, the first live view window 53 displays the live view data for the "Travel Application". For instance, in the HarmonyOS operating system, icon data can be obtained from the Bundle Management Service (BMS), while the main text data, secondary text data, and extended area data are provided by third-party developers. The auxiliary area data can be obtained from the cloud via a link provided by the developer. Regarding the implementation of the live view window, data can be transmitted using the desktop screen recording software LiveView.

[0392] S124, in response to the data acquisition request sent by the second electronic device, a second message about the target task data is sent to the second electronic device so that the second target system interface of the second electronic device outputs the target task data; wherein, the data acquisition request is generated based on the sharing link information, and the sharing link information is generated based on the target task data on the first target system interface of the first electronic device.

[0393] In the specific implementation process, after receiving a data acquisition request, the first server can associate the device information with the target task data, thereby enabling it to send a second message about the target task data to the second electronic device corresponding to the associated device information.

[0394] Furthermore, since the first server receives at least a first message, which is a message related to the target task data, and the sharing link information is a link corresponding to the target task data, in response to the third operation on the sharing link information, at least a second message about the target task data can be obtained from the first server. The second message can be generated based on the first message or based on the target task data. The second message can be any message related to the target task data, and may include descriptive information about the target task data, or data identification information about the target task data. The second electronic device can obtain the target task data from the second server of the first target application based on the second message; the second electronic device can also obtain it from the backed-up third-party device based on the second message if the first electronic device has a backup on the third-party device. In one embodiment, the second electronic device can also obtain the target task data from the first server based on the second message.

[0395] In one embodiment, the data acquisition request includes device information of the second electronic device; sending a third message about updated data for the target task to the second electronic device includes:

[0396] Based on the device information, a third message regarding the updated data of the target task is sent to the second electronic device corresponding to the device information.

[0397] In practice, a data acquisition request may include an access token, which can contain device information about the second electronic device. The data acquisition request can also take other forms, as long as it includes device information. Furthermore, since the data acquisition request is generated based on the shared link information, it also carries information related to the target task data.

[0398] In one embodiment, as shown in FIG14, after S124, the following is further included:

[0399] S126, a third message about the target task update data is sent to the second electronic device; wherein, the target task update data is update data about the target task data.

[0400] In specific implementation, the target task update data refers to updates to at least a portion of the target task data. Taking the real-time task data of the "travel application" in the aforementioned embodiment as an example, the target task update data can include updated text data and updated graphic data, thereby updating vehicle location information and vehicle arrival time information. Specifically, the first server can receive update data pushed by the second server or by the first electronic device. It should be noted that since the second server can push the target task update data to the first electronic device to update the data of the first target application, the first server can also receive update data from the first electronic device.

[0401] The third message can be any message related to the target task update data, and may include descriptive information about the target task update data, or data identification information about the target task update data.

[0402] In one embodiment, S126 specifically includes:

[0403] Receive target task update data pushed by the second server; wherein, the second server is the server corresponding to the first target application;

[0404] A third message regarding updated data for the target mission is sent to the second electronic device.

[0405] It is understandable that the second server could be the second server 23 in Figure 4, which directly receives the update data pushed by the second server, resulting in less latency and smoother device operation.

[0406] In one embodiment, the second electronic device includes multiple devices, and each second electronic device sends a data acquisition request to the first server, which includes device information.

[0407] Based on the device information, a third message regarding the updated data for the target task is sent to the second electronic device corresponding to the device information, including:

[0408] Based on the device information of each second electronic device, a third message regarding the updated data of the target task is sent to each second electronic device respectively.

[0409] This embodiment describes a scenario involving one first electronic device and multiple second electronic devices. With the aid of a first server, one-to-many remote sharing between terminals in the live feed window can be achieved, and the live tasks in the live feed window can be updated and displayed in real time on the system interface. This allows users to conveniently follow other users' live feeds in real time, providing a better user sharing experience.

[0410] This application also provides a graphical user interface (GUI) stored in an electronic device. The electronic device includes a display screen, a memory, and one or more processors. The one or more processors are used to execute one or more computer programs stored in the memory. The graphical user interface includes:

[0411] A first GUI is displayed on the screen. The first GUI includes a target system interface. The target system interface includes a target display area. The target display area is used to output the target task data in the aforementioned embodiments.

[0412] In response to a first gesture targeting a display area, a first control is displayed on the first GUI;

[0413] In response to a second gesture toward the first control, a second GUI is displayed on the screen, the second GUI including a second control for sharing target task data.

[0414] In specific implementation, the target system interface can be the first target system interface or the second target system interface in the aforementioned embodiments, specifically a desktop interface, lock screen interface, notification center interface, etc. The target display area can be the first live window or the second live window in the aforementioned embodiments. The first control can be the option control in the aforementioned embodiments. The second GUI can be the first display area in the aforementioned embodiments, and the second control can be the control corresponding to the "share" option in the first display area.

[0415] For example, the interface, controls, and display area in the graphical user interface (GUI) can be as shown in Figures 5A to 5E. The first GUI is the first target system interface, the target display area is the first live window 53, the first gesture can be sliding the first live window 53 to the left as shown in Figure 5D, the first control is the option control 54, the second gesture is the click operation on the option control 54, the second GUI is the first display area 55, and the second control is the control corresponding to the "share" option in the first display area 55.

[0416] In one embodiment, the graphical user interface further includes:

[0417] In response to a third gesture to the second control, a third GUI is displayed on the screen, the third GUI including at least the target application icon;

[0418] In response to a fourth gesture targeting the target app icon, display the fourth GUI of the target app corresponding to the target app icon on the screen.

[0419] In the specific implementation process, referring to Figures 5E to 5G, the third gesture can be a click operation on the second control, the third GUI can be the second display area 60 in the aforementioned embodiment, the fourth gesture can be a click operation on the target application icon, the target application can be the second target application in the aforementioned embodiment, and the fourth GUI can be the first application interface 58 in the aforementioned embodiment.

[0420] In one embodiment, the graphical user interface further includes:

[0421] The fifth GUI is displayed on the screen. The fifth GUI is the application interface, and a sharing link is displayed on the fifth GUI.

[0422] In response to a fifth gesture for sharing a connection, a sixth GUI is displayed on the screen, which includes the target system interface.

[0423] In specific implementation, referring to Figure 5H, the fifth GUI can be the second application interface 59 in the aforementioned embodiment, and the fifth gesture can be a click operation on the sharing link. The sixth GUI can be the second target system interface in the aforementioned embodiment.

[0424] It should be noted that the first gesture, second gesture, third gesture, fourth gesture, and fifth gesture in this embodiment can be understood as gesture operation, that is, the interaction between the hand and the display screen. The specific interaction operation can be one or more gesture operations such as the first operation, second operation, third operation, first selection operation, etc. in the aforementioned embodiment.

[0425] It should be noted that the descriptions of the graphical user interface (GUI) not covered in this embodiment can be found in the various implementation methods and technical effects of the task data sharing method in the foregoing embodiments, and will not be repeated here.

[0426] In one embodiment, referring to FIG15, an embodiment of this application also provides a first electronic device 21, comprising:

[0427] The first output unit 152 is used to output target task data on the first target system interface; wherein, the target task data is the task data of the first target application in the first electronic device 21;

[0428] The generation unit 154 is used to generate sharing link information corresponding to the target task data in response to the first operation on the target task data.

[0429] The sending unit 156 is configured to send sharing link information to the second electronic device in response to a second operation on the first electronic device 21; wherein the sharing link information is used by the second electronic device to output target task data.

[0430] It should be noted that the steps performed by each unit (152, 154, 156) in the first electronic device in this embodiment are the same as the steps (S102, S104, S106) performed by the first electronic device in the previous embodiment. Therefore, the various implementation methods and technical effects can be referred to the task data sharing method performed by the first electronic device in the previous embodiment, and will not be repeated here.

[0431] In one embodiment, referring to FIG16, an embodiment of this application also provides a second electronic device 22, comprising:

[0432] The receiving unit 162 is used to receive sharing link information about target task data sent by the first electronic device; wherein, the target task data is the task data of the first target application in the first electronic device;

[0433] The second output unit 164 is used to output target task data on the second target system interface of the second electronic device 22 in response to a third operation on the shared link information.

[0434] It should be noted that the steps performed by each unit (162, 164) in the second electronic device in this embodiment are the same as the steps (S107, S108) performed by the second electronic device in the previous embodiment. Therefore, the various implementation methods and technical effects can be referred to the task data sharing method performed by the second electronic device in the previous embodiment, and will not be repeated here.

[0435] In one embodiment, the present application also provides a computer program product containing instructions that, when run on an electronic device, cause the electronic device to perform the task data sharing method of any of the foregoing embodiments.

[0436] In one embodiment, embodiments of this application also provide a computer-readable storage medium including instructions that, when executed on an electronic device, cause the electronic device to perform the task data sharing method of any of the foregoing embodiments.

[0437] In this embodiment, the computer program product and computer-readable storage medium are used to execute the corresponding task data sharing method provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding method provided above, and will not be repeated here.

[0438] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0439] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0440] The unit described as a separate component may or may not be physically separate. The component shown as a unit can be one physical unit or multiple physical units, that is, it can be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of the solution in this embodiment according to actual needs.

[0441] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0442] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0443] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A task data sharing method, characterized by, The method includes: The first target system interface of the first electronic device outputs target task data; wherein, the target task data is the task data of the first target application in the first electronic device; In response to a first operation on the target task data, the first electronic device generates sharing link information corresponding to the target task data; In response to a second operation performed on the first electronic device, the first electronic device sends the sharing link information to the second electronic device; In response to a third operation on the shared link information, the second electronic device outputs the target task data on the second target system interface.

2. The method as described in claim 1, characterized in that, In response to a first operation on the target task data, the first electronic device generates sharing link information corresponding to the target task data, including: In response to a first operation on the target task data, the first electronic device sends a first message about the target task data to the first server and generates sharing link information corresponding to the target task data. In response to a third operation concerning the shared link information, the second electronic device outputs the target task data on the second target system interface, including: In response to a third operation concerning the shared link information, the second electronic device receives a second message from the first server regarding target task data. The second electronic device outputs the target task data on the second target system interface based on the second message.

3. The method as described in claim 2, characterized in that, In response to a third operation concerning the shared link information, the second electronic device receives a second message from the first server regarding target task data, including: In response to a third operation concerning the shared link information, the second electronic device sends a data acquisition request to the first server; wherein the data acquisition request includes device information of the second electronic device. In response to a data acquisition request sent by a second electronic device, the first server sends a second message about the target task data to the second electronic device corresponding to the device information. The second electronic device receives a second message regarding the target task data.

4. The method as described in claim 3, characterized in that, After outputting the target task data on the second target system interface, the method further includes: The first server receives the target task update data from the target task data; The first server pushes a third message about the updated data of the target task to the second electronic device corresponding to the device information; The second electronic device receives a third message regarding the updated data of the target task, and updates the second target task data according to the third message.

5. The method as described in claim 4, characterized in that, The first server receives target task update data from the target task data, including: The first server receives target task update data pushed by the second server; wherein, the second server is the server corresponding to the first target application.

6. The method as described in claim 4 or 5, characterized in that, The second electronic device includes multiple devices, and each second electronic device sends a data acquisition request to the first server, which includes device information, and each second electronic device outputs the target task data. The first server pushes a third message regarding the updated data of the target task to the second electronic device corresponding to the device information, including: The first server pushes a third message about the updated data of the target task to the second electronic device corresponding to each device information.

7. The method as described in claims 1 to 6, characterized in that, In response to a first operation on the target task data, the first electronic device generates sharing link information corresponding to the target task data, including: In response to a first operation on the target task data, the first electronic device displays a first display area on its screen. In response to a first selection operation of a target option in the first display area, the first electronic device generates sharing link information corresponding to the target task data.

8. The method as described in claim 7, characterized in that, In response to a second operation performed on the first electronic device, the first electronic device sends the sharing link information to a second electronic device, including: In response to a second operation targeting the first electronic device, the first electronic device sends the sharing link information to the second electronic device via a second target application.

9. The method as described in claim 8, characterized in that, In response to a user's first selection of a target option in the first display area, the first electronic device generates sharing link information corresponding to the target task data, including: In response to a first selection operation on a target option in the first display area, the first electronic device generates sharing link information corresponding to the target task data and displays a second display area on the screen of the first electronic device; In response to a second operation targeting the first electronic device, the first electronic device sends the sharing link information to the second electronic device via a second target application, including: In response to a second selection operation on a target application icon in the second display area, the first electronic device sends the sharing link information to the second electronic device via the second target application; wherein, the target application icon is the icon corresponding to the second target application.

10. The method according to any one of claims 1 to 9, characterized in that, The first target system interface of the first electronic device outputs target task data, including: The first target system interface of the first electronic device displays the first target task window corresponding to the target task data; In response to a first operation on the target task data, the first electronic device generates sharing link information corresponding to the target task data, including: In response to a first operation on the first target task window, the first electronic device generates sharing link information corresponding to the target task data. The second electronic device outputs the target task data on the second target system interface, including: The second electronic device displays the second target task window corresponding to the target task data on the second target system interface.

11. The method as described in claim 10, characterized in that, After the second electronic device outputs the second target task window corresponding to the target task data on the second target system interface, the method further includes: When a first preset condition is met, the sharing task corresponding to the second target task window is terminated; wherein, the first preset condition includes at least one of the following: the second electronic device receives task termination information, the second electronic device receives a fourth operation from the user on the second target task window, and the output of the second target task window reaches a preset time.

12. The method according to any one of claims 1 to 11, characterized in that, The target task data is real-time task data.

13. The method as described in claim 12, characterized in that, The first target application is a third-party application.

14. A method for sharing task data, characterized in that, For a first electronic device, the method includes: The target task data is output on the first target system interface; wherein, the target task data is the task data of the first target application in the first electronic device; In response to a first operation on the target task data, share link information corresponding to the target task data is generated; In response to a second operation on the first electronic device, the sharing link information is sent to the second electronic device; wherein the sharing link information is used by the second electronic device to output the target task data.

15. The method as described in claim 14, characterized in that, The step of generating sharing link information corresponding to the target task data in response to a first operation on the target task data includes: In response to a first operation on the target task data, a first message about the target task data is sent to a first server, and sharing link information corresponding to the target task data is generated.

16. The method as described in claim 14 or 15, characterized in that, The step of generating sharing link information corresponding to the target task data in response to a first operation on the target task data includes: In response to a first operation on the target task data, a first display area is displayed; In response to a first selection operation of a target option in the first display area, share link information corresponding to the target task data is generated.

17. The method as described in claim 16, characterized in that, The step of generating share link information corresponding to the target task data in response to a first selection operation on a target option in the first display area includes: In response to a first selection operation on a target option in the first display area, share link information corresponding to the target task data is generated, and a second display area is displayed; The step of sending the sharing link information to the second electronic device via a second target application in response to a second operation on the first electronic device includes: In response to a second selection operation on a target application icon in the second display area, the sharing link information is sent to the second electronic device; wherein the target application icon is the icon corresponding to the second target application.

18. The method according to any one of claims 14 to 17, characterized in that, The step of sending the sharing link information to the second electronic device in response to the second operation on the first electronic device includes: In response to a second operation on the first electronic device, the sharing link information is sent to the second electronic device via a second target application.

19. The method according to any one of claims 14 to 18, characterized in that, The step of outputting target task data on the first target system interface includes: The first target task window corresponding to the target task data is displayed on the first target system interface; The step of generating sharing link information corresponding to the target task data in response to a first operation on the target task data includes: In response to the first operation on the target task window, share link information corresponding to the target task data is generated.

20. The method according to any one of claims 14 to 19, characterized in that, The target task data is real-time task data.

21. The method as described in claim 20, characterized in that, The first target application is a third-party application.

22. A method for sharing task data, characterized in that, For a second electronic device, the method includes: Receive a sharing link information about target task data sent by a first electronic device; wherein, the target task data is the task data of a first target application in the first electronic device; In response to a third operation on the shared link information, the target task data is output on the second target system interface of the second electronic device.

23. The method as described in claim 22, characterized in that, The third operation in response to the shared link information, outputting the target task data on the second target system interface of the second electronic device, includes: In response to a third operation on the shared link information, a second message regarding the target task data sent by the first server is received; Based on the second message, the target task data is output on the second target system interface of the second electronic device.

24. The method as described in claim 23, characterized in that, The response to the third operation concerning the shared link information, receiving a second message from the first server regarding the target task data, includes: In response to a third operation concerning the shared link information, a data acquisition request is sent to the first server; wherein the data acquisition request includes device information of the second electronic device; Receive a second message from the first server in response to the data acquisition request, containing data about the target task.

25. The method as described in claim 2 or 3, characterized in that, After outputting the target task data on the second target system interface of the second electronic device, the method further includes: Receive a third message pushed by the first server regarding updated data for the target task, wherein the updated data for the target task is updated data regarding the target task data; Update the target task data according to the third message.

26. The method according to any one of claims 22 to 25, characterized in that, The step of outputting the target task data on the second target system interface of the second electronic device includes: The second target task window corresponding to the target task data is output on the second target system interface of the second electronic device; The step of updating the target task data according to the third message includes: Based on the third message, update the second target task window corresponding to the target task data.

27. The method as described in claim 26, characterized in that, After outputting the second target task window corresponding to the target task data on the second target system interface of the second electronic device, the method further includes: When a first preset condition is met, the sharing task corresponding to the second target task window is terminated; wherein, the first preset condition includes at least one of the following: the second electronic device receives task termination information pushed by the first server, the second electronic device receives a fourth operation from the user on the second target task window, and the output of the second target task window reaches a preset time.

28. The method according to any one of claims 22 to 27, characterized in that, The receipt of the sharing link information about the target task data sent by the first electronic device includes: The second target application receives a sharing link information about the target task data sent by the first electronic device.

29. The method according to any one of claims 22 to 28, characterized in that, The target task data is real-time task data.

30. The method as described in claim 29, characterized in that, The first target application is a third-party application.

31. A method for sharing task data, characterized in that, For use with a first server, the method includes: Receive a first message about target task data sent by a first electronic device; wherein the target task data is the task data of a first target application output on the first target system interface of the first electronic device; In response to a data acquisition request sent by a second electronic device, a second message regarding the target task data is sent to the second electronic device, so that the second target system interface of the second electronic device outputs the target task data; wherein, the data acquisition request is generated based on sharing link information, and the sharing link information is generated based on the target task data on the first target system interface of the first electronic device.

32. The method as described in claim 31, characterized in that, The method further includes: A third message regarding the updated data of the target task is sent to the second electronic device; wherein, the updated data of the target task is the updated data regarding the target task data.

33. The method as described in claim 32, characterized in that, Sending a third message about updated target task data to the second electronic device includes: Receive the target task update data pushed by the second server; wherein, the second server is the server corresponding to the first target application; A third message regarding the updated data for the target task is sent to the second electronic device.

34. The method as described in claim 32 or 33, characterized in that, The data acquisition request includes device information of the second electronic device; sending a third message about the target task update data to the second electronic device includes: Based on the device information, a third message regarding the updated data of the target task is sent to the second electronic device corresponding to the device information.

35. The method as described in claim 34, characterized in that, The second electronic device includes multiple devices, and each second electronic device sends a data acquisition request to the first server, which includes device information. The step of sending a third message regarding target task update data to the second electronic device corresponding to the device information based on the device information includes: Based on the device information of each of the second electronic devices, a third message regarding the target task update data is sent to each of the second electronic devices respectively.

36. The method according to any one of claims 31 to 35, characterized in that, The target task data is real-time task data.

37. The method as described in claim 36, characterized in that, The first target application is a third-party application.

38. A graphical user interface (GUI) for an electronic device, the electronic device including a display screen, a memory, and one or more processors, the one or more processors being configured to execute one or more computer programs stored in the memory, characterized in that, The graphical user interface includes: A first GUI is displayed on the display screen. The first GUI includes a target system interface, and the target system interface includes a target display area for outputting target task data. In response to a first gesture toward the target display area, a first control is displayed on the first GUI; In response to a second gesture toward the first control, a second GUI is displayed on the display screen, the second GUI including a second control for sharing the target task data.

39. The graphical user interface as described in claim 38, characterized in that, The graphical user interface also includes: In response to a third gesture toward the second control, a third GUI is displayed on the screen, the third GUI including at least a target application icon; In response to a fourth gesture toward the target application icon, a fourth GUI of the target application corresponding to the target application icon is displayed on the screen.

40. The graphical user interface as described in claim 38 or 39, characterized in that, The graphical user interface also includes: The fifth GUI displayed on the screen is an application interface, and a sharing link is displayed on the fifth GUI; In response to a fifth gesture for the sharing connection, a sixth GUI is displayed on the screen, the sixth GUI including the target system interface.

41. A first electronic device, characterized in that, include: The first output unit is used to output target task data on the first target system interface; wherein, the target task data is the task data of the first target application in the first electronic device; A generation unit is configured to generate sharing link information corresponding to the target task data in response to a first operation on the target task data. A sending unit is configured to send the sharing link information to a second electronic device in response to a second operation on the first electronic device; wherein the sharing link information is used by the second electronic device to output the target task data.

42. A second electronic device, characterized in that, include: A receiving unit is configured to receive sharing link information about target task data sent by a first electronic device; wherein the target task data is task data of a first target application in the first electronic device; The second output unit is configured to output the target task data on the second target system interface of the second electronic device in response to a third operation on the shared link information.

43. A first electronic device, comprising one or more displays, one or more memories, and one or more processors; wherein the one or more memories store one or more programs; characterized in that, When the one or more processors execute the one or more programs, the first electronic device causes the first electronic device to implement the method as described in any one of claims 14 to 21.

44. A second electronic device, comprising one or more displays, one or more memories, and one or more processors; wherein the one or more memories store one or more programs; characterized in that, When the one or more processors execute the one or more programs, the second electronic device causes the second electronic device to implement the method as described in any one of claims 22 to 30.

45. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it causes the computer device to implement the method as described in any one of claims 31 to 37.

46. ​​A computer program product containing instructions, characterized in that, When the computer program product is run on an electronic device, it causes the electronic device to perform the method as described in any one of claims 1-37.

47. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-37.

48. A system for realizing inter-device communication, characterized in that, The system includes a first electronic device as described in claim 43 and at least one second electronic device as described in claim 44; the first electronic device and at least one second electronic device establish a communication link with each other.

Images