Data sharing method and system, and electronic device

Through a unified data definition standard and management framework, the problem of inconsistency in the data transmission process between devices and between applications is solved, and the unified data format and the simplification of the transmission process is achieved.

WO2024235232A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/093173
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-16
Filing Date
2024-05-14
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In the prior art, the data transmission process between devices and applications is complicated, mainly due to the inconsistent definition standards of data by different applications and paths, resulting in complex data transmission and reception processing.

Method used

Adopting a unified data definition standard, data definitions are generated and parsed between the sender and the receiver through a data management framework to ensure the consistency of data formats under different applications and paths.

Benefits of technology

The data transmission process is simplified, the complexity of the sender and the receiver in data definition and parsing is reduced, and the convenience and efficiency of data transmission is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024093173_21112024_PF_FP_ABST
    Figure CN2024093173_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a data sharing method and system, and an electronic device. Regardless of whether data is shared between two applications on a same device or between two applications on different devices, a sender application can acquire a specified data definition standard from a unified data management framework, and generate redefined shared data from shared data on the basis of the specified data definition standard. A receiver application can also acquire the same specified data definition standard from the unified data management framework, and parse the redefined shared data to obtain the shared data. For different applications and different sharing paths, a unified data definition standard is provided, thereby achieving unified definition of shared data and simplifying the data processing flow.
Need to check novelty before this filing date? Find Prior Art

Description

Data sharing method and system-level electronic device

[0001] This application claims priority to the Chinese patent application with application number 202310555908.8 filed with the State Intellectual Property Office of China on May 16, 2023, and priority to the Chinese patent application with the invention name “A data sharing method, system-level electronic device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of data processing technology, and in particular to a data sharing method and a system-level electronic device. Background Art

[0003] With consumption upgrades, users are owning an increasing number of smart devices. In some scenarios, users can share data between different devices, for example, using drag-and-drop, clipboard, and other sharing methods. In other scenarios, users can also share data between different applications on the same device, and different applications on the same device can also share data using drag-and-drop, clipboard, and other sharing methods.

[0004] The different sharing paths for different applications and data require different standard definitions for shared data. For each sharing path, the sender must define the shared data using different sharing paths, and the receiver must parse the data sent by the sender based on multiple different standard definitions, making the data transmission and reception process more cumbersome. Further research is needed to improve the convenience of data transmission between devices and applications.

[0005] Summary of the Invention

[0006] The present application provides a data sharing method and a system-level electronic device, which simplifies the processing flow of data transmission between two applications through a unified data definition standard.

[0007] In a first aspect, the present application provides a data sharing system, which includes a first electronic device and a second electronic device, wherein the first electronic device and the second electronic device establish a communication connection, the first electronic device includes a first application, and the second electronic device includes a second application, wherein the first application is used to obtain first data; the first application is further used to: generate first definition data corresponding to the first data based on a specified data definition standard, the first definition data including attributes of the first data and the first data, or the first definition data including attributes of the first data and a storage path of the first data; send the first definition data to the second application via a first sharing path and a communication connection; the second application is used to obtain the first definition data via the first sharing path; the second application, It is also used to parse the first data or the storage path of the first data from the first definition data based on the specified data definition standard; the first application is also used to: obtain the second data; generate second definition data corresponding to the second data based on the specified data definition standard, the second definition data including the attributes of the second data and the second data, or the second definition data including the attributes of the second data and the storage path of the second data; send the second definition data to the second application through the second sharing path and the communication connection; the second application is also used to: obtain the second definition data through the second sharing path; parse the second data or the storage path of the second data from the second definition data based on the specified data definition standard; wherein the second sharing path is different from the first sharing path.

[0008] The first sharing path or the second sharing path includes any one of the following: a drag path, a clipboard path, a cross-device manual path, and a cross-device automatic path.

[0009] Optionally, the first application and the second application may be the same, or the first application and the second application may be different, which is not limited in this application.

[0010] Exemplarily, the first data may be a picture. When the picture is sent to the instant messaging application through the first sharing path and the second sharing path respectively, the two paths both define the type of the picture as "image".

[0011] This system allows for data sharing between two applications on different devices. Before data sharing can begin, each application must define the shared data according to this standard. After receiving the shared data, each application must also parse it based on this standard. This means that the data definition standard is unified across different applications and sharing paths, achieving a unified format for shared data.

[0012] In combination with the first aspect, in a possible implementation, the first electronic device also includes a first data management framework, and the second electronic device also includes a second data management framework; the first application is specifically used to send the first definition data to the first data management framework through the first sharing path; the first data management framework is used to send the first definition data to the second data management framework through a communication connection; the second data management framework is also used to send the first definition data to the second application through the first sharing path.

[0013] This application provides a data management framework (a first data management framework and a second data management framework) for statistical management of data on a device. The second data management framework can store the first defined data, and the second application can read the data from the second data management framework.

[0014] In combination with the first aspect, in a possible implementation method, the first application is also used to: generate a unified management protocol for the first data based on the unified management protocol standard, wherein the unified management protocol for the first data includes an identifier of the first sharing path; send the unified management protocol for the first data to the first data management framework: the first data management framework is also used to: send the unified management protocol for the first data to the second data management framework through a communication connection; the second data management framework is specifically used to: obtain the identifier of the first sharing path from the unified management protocol for the first data; and send the first definition data to the second application through the first sharing path based on the identifier of the first sharing path.

[0015] In this way, the unified data management framework can determine the identifier of the sharing path based on the unified management protocol of the first data, and share it to the peer application through the corresponding path.

[0016] In combination with the first aspect, in a possible implementation, the first application is further used to: generate instructions for use of the first data based on a specified data definition standard, wherein the instructions for use of the first data include personalized permissions of the first sharing path; send the instructions for use of the first data to the first data management framework; the first data management framework is further used to: send the instructions for use of the first data to the second data management framework through a communication connection; the second data management framework is specifically used to: obtain a first notification sent by the second application, the first notification is used to read the first data, and the first notification includes an identifier of the second application; obtain the permission rules of the first sharing path based on the identifier of the first sharing path in the unified management protocol of the first data; obtain the personalized permissions of the first data from the instructions for use of the first data; after determining that the second application has the ability to access the first data based on the instructions for use of the first data, when the first data management framework determines that the second application has the authority to access the first data based on the personalized permissions of the first data, the permission rules of the first sharing path, the permission rules of the second data management framework and the identifier of the second application, the first definition data is sent to the second application through the first sharing path based on the identifier of the first sharing path.

[0017] In this way, the unified data management framework can verify whether the second application has the ability to use the data based on the specified data definition standards. After verifying that the second application has the ability to use the data, the unified data management framework then determines whether the second application has the permission to use the data based on one or more of the personalized permissions of the first data, the permission rules of the first sharing path, and the permission rules of the second data management framework. If the second application has the permission to access the data, the data is then sent to the second application.

[0018] Specifically, the usage description of the first data includes an application source field, an operating system source field, and a type field of the first data.

[0019] When the type field indicates that the first data is basic data, the unified data management framework can directly determine whether the second application has permission to use the data without checking the application source field and the operating system source field.

[0020] If the Type field indicates that the first data is system-defined data, the unified data management framework first checks the Operating System Source field to determine whether the operating system of the device where the second application is installed and the Operating System Source field are the same. If they are, it means that the second application has access to the data. The unified data management framework then determines whether the second application has permission to use the data.

[0021] If the Type field indicates that the first data is application-defined data, the unified data management framework first checks the Operation Application Source field to determine whether the second application and the application source are the same. If they are, it means that the second application has access to the data. The unified data management framework then determines whether the second application has permission to use the data.

[0022] In a second aspect, the present application provides a data sharing method, the method comprising: a second application on a second electronic device obtains first definition data sent by a first application on a first electronic device through a first sharing path and a communication connection, wherein the first definition data is generated by the first application based on a specified data definition standard and the first data, the first definition data includes attributes of the first data and the first data, or the first definition data includes attributes of the first data and the storage path of the first data, the second electronic device is different from the first electronic device, and the first electronic device and the second electronic device establish a communication connection; the second application parses the first data or the storage path of the first data from the first definition data based on the specified data definition standard; the second application obtains second definition data sent by the first application through a second sharing path and a communication connection, wherein the second definition data is generated by the first application based on the specified data definition standard and the second data, the second definition data includes attributes of the second data and the second data, or the second definition data includes attributes of the second data and the storage path of the second data; the second application parses the second data or the storage path of the second data from the second definition data based on the specified data definition standard; wherein the second sharing path is different from the first sharing path.

[0023] Optionally, when the first data is non-file data, the first definition data includes the attributes of the first data and the first data. Non-file data may include but is not limited to text data, system-defined data, and application-defined data.

[0024] When the first data is file data, the first definition data includes attributes of the first data and a storage path of the first data.

[0025] In combination with the second aspect, in one possible implementation, the second application obtains the first definition data sent by the first application through the second sharing path and communication connection; the second application parses the first data or the storage path of the first data from the first definition data based on the specified data definition standard.

[0026] In this way, the same shared data is shared to the peer application through different sharing paths. The first application can directly reuse the previous first definition data without having to generate the first definition data based on the specified data definition standard and the first data.

[0027] In combination with the second aspect, in a possible implementation, the first electronic device also includes a first data management framework, and the second electronic device also includes a second data management framework; the second application obtains the first definition data sent by the first application through the first sharing path and the communication connection, specifically including: the second data management framework receives the first definition data sent by the first data management framework through the communication connection, wherein the first definition data stored in the first data management framework is sent by the first application; the second data management framework sends the first definition data to the second application through the first sharing path.

[0028] In combination with the second aspect, in a possible implementation method, the second application obtains the first definition data sent by the first application through the first sharing path, specifically including: the second data management framework receives the unified management protocol of the first data sent by the first data management framework through a communication connection, wherein the unified management protocol of the first data is generated by the first application based on the unified management protocol standard, and the unified management protocol of the first data includes the identifier of the first sharing path; the second data management framework obtains the identifier of the first sharing path from the unified management protocol of the first data; the second data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path.

[0029] In this way, the unified data management framework can determine the identifier of the sharing path based on the unified management protocol of the first data, and share it to the peer application through the corresponding path.

[0030] In combination with the second aspect, in a possible implementation method, the second application obtains the second definition data sent by the first application through the second sharing path, specifically including: the second data management framework receives the unified management protocol of the second data sent by the first data management framework through a communication connection, wherein the unified management protocol of the second data is generated by the first application based on the unified management protocol standard, and the unified management protocol of the second data includes the identifier of the second sharing path; the second data management framework obtains the identifier of the second sharing path from the unified management protocol of the second data; the second data management framework sends the second definition data to the second application through the second sharing path based on the identifier of the second sharing path; wherein the unified management protocol of the second data is different from the unified management protocol of the first data.

[0031] In this way, for different sharing paths, the unified management protocol of the shared data generated by the first application is different.

[0032] In combination with the second aspect, in a possible implementation, before the second data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path, the method further includes: the second data management framework receives the usage instructions of the first data sent by the first data management framework through a communication connection, the usage instructions of the first data are generated by the first application based on a specified data definition standard and sent to the first data management framework, and the usage instructions of the first data include personalized permissions of the first data; the second data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path, specifically including: the second data management framework obtains the first notification sent by the second application, the first notification is used to read the first data, The first notification includes the identifier of the second application; the second data management framework obtains the permission rules of the first sharing path based on the identifier of the first sharing path in the unified management protocol of the first data; the second data management framework obtains the personalized permissions of the first data from the instructions for use of the first data; after the second data management framework determines that the second application has the ability to access the first data based on the instructions for use of the first data, when the first data management framework determines that the second application has the authority to access the first data based on the personalized permissions of the first data, the permission rules of the first sharing path, the permission rules of the first data management framework and the identifier of the second application, the second data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path.

[0033] In combination with the second aspect, in one possible implementation, after the second data management framework receives the first definition data and the unified management protocol of the first data, the method also includes: the second data management framework verifies the first definition data based on the specified data definition standard; if the verification passes, the second data management framework stores the first definition data, the unified management protocol of the first data and the instructions for use of the first data.

[0034] In conjunction with the second aspect, in a possible implementation, if the verification fails, the first definition data and the instructions for using the first data in the unified management protocol of the first data are deleted.

[0035] In this way, it is ensured that the redefined data stored in the second data management framework is defined based on the specified data definition standard.

[0036] In conjunction with the second aspect, in a possible implementation, the specified data definition standard is stored in the second data management framework; the method further includes: the second data management framework sending the specified data definition standard to the second application.

[0037] In this way, the second application can parse the first definition data based on the specified data definition standard to obtain the first data.

[0038] In combination with the second aspect, in a possible implementation, after the second application parses the storage path of the first data from the first definition data based on the specified data definition standard, the method also includes: the second application sends the storage path of the first data to the first application through a communication connection; the second application receives the first data sent by the first application through the communication connection, and the first data is obtained by the first application based on the storage path of the first data.

[0039] In conjunction with the second aspect, in a possible implementation, after the second application parses the first data or the storage path of the first data from the first definition data, the method further includes: the second data management framework deleting the first definition data.

[0040] In this way, the second data management framework can clean up the shared data that has been used in a timely manner to avoid data leakage.

[0041] In a third aspect, the present application provides a data sharing method, which is characterized in that it is applied to a first electronic device, the first electronic device includes a first application and a second application, and the method includes: the first application obtains the first data; the first application generates first definition data corresponding to the first data based on a specified data definition standard, the first definition data includes the attributes of the first data and the first data, or the first definition data includes the attributes of the first data and the storage path of the first data; the first application sends the first definition data to the second application through a first sharing path; the second application parses the first data or the storage path of the first data from the first definition data based on the specified data definition standard; the first application obtains the second data; the first application generates second definition data corresponding to the second data based on the specified data definition standard, the second definition data includes the attributes of the second data and the second data, or the second definition data includes the attributes of the second data and the storage path of the second data; the first application sends the second definition data to the second application through a second sharing path; the second application parses the second data or the storage path of the second data from the second definition data based on the specified data definition standard; wherein the second sharing path is different from the first sharing path.

[0042] With this data sharing method between two applications on the same device, before sharing data, different applications need to define the shared data according to this standard. After receiving the shared data, different applications also need to parse the shared data based on this standard. In other words, the data definition standard is unified for different applications and different sharing paths, achieving a unified format for shared data.

[0043] In combination with the third aspect, in a possible implementation, the method also includes: the first application obtains the first definition data; the first application sends the first definition data to the second application through the second sharing path; the second application parses the first data or the storage path of the first data from the first definition data based on the specified data definition standard.

[0044] In this way, the same shared data is shared to the peer application through different sharing paths. The first application can directly reuse the previous first definition data without having to generate the first definition data based on the specified data definition standard and the first data.

[0045] In combination with the third aspect, in a possible implementation method, the first electronic device also includes a first data management framework, and the first application sends the first definition data to the second application through the first sharing path, specifically including: the first application generates a unified management protocol for the first data based on the unified management protocol standard, wherein the unified management protocol for the first data includes an identifier of the first sharing path; the first application sends the first definition data and the unified management protocol for the first data to the first data management framework: the first data management framework obtains the identifier of the first sharing path from the unified management protocol for the first data; the first data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path.

[0046] In combination with the third aspect, in a possible implementation method, the second application sends the second definition data to the second application through the second sharing path, specifically including: the first application generates a unified management protocol for the second data based on the unified management protocol standard, wherein the unified management protocol for the second data includes an identifier of the second sharing path; the first application sends the second definition data and the unified management protocol for the second data to the first data management framework: the first data management framework obtains the identifier of the second sharing path from the unified management protocol for the second data; the first data management framework sends the second definition data to the second application through the first sharing path based on the identifier of the second sharing path; wherein the unified management protocol for the second data is different from the unified management protocol for the first data.

[0047] In combination with the third aspect, in a possible implementation, the method also includes: the first application generates instructions for use of the first data based on a specified data definition standard, wherein the instructions for use of the first data include personalized permissions of the first data; the first data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path, specifically including: the first data management framework obtains a first notification sent by the second application, the first notification is used to read the first data, and the first notification includes the identifier of the second application; the first data management framework obtains the permission rules of the first sharing path based on the identifier of the first sharing path in the unified management protocol of the first data; the first data management framework obtains the personalized permissions of the first data from the instructions for use of the first data; after the first data management framework determines that the second application has the ability to access the first data based on the instructions for use of the first data, when the first data management framework determines that the second application has the permission to access the first data based on the personalized permissions of the first data, the permission rules of the first sharing path, the permission rules of the first data management framework and the identifier of the second application, the first data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path.

[0048] In combination with the third aspect, in one possible implementation, after the first application sends the first definition data and the unified management protocol of the first data to the first data management framework, the method also includes: the first data management framework verifies the first definition data based on the specified data definition standard; if the verification passes, the first data management framework stores the first definition data, the unified management protocol of the first data and the instructions for use of the first data.

[0049] In combination with the third aspect, in a possible implementation manner, the method further includes: if the verification fails, deleting the first definition data, the unified management protocol of the first data, and the usage instructions of the first data.

[0050] In combination with the third aspect, in a possible implementation, after the second application parses the first data or the storage path of the first data from the first definition data, the method further includes: the first data management framework deletes the first definition data.

[0051] In combination with the third aspect, in a possible implementation, the first sharing path or the second sharing path includes any one of the following: a drag path, a clipboard path, a cross-application manual path, and a cross-application automatic path.

[0052] In conjunction with the third aspect, in a possible implementation, the attributes of the first data include one or more of the following: the type of the first data, the size of the first data, and the creation time of the first data.

[0053] In a fourth aspect, the present application provides an electronic device, which includes: one or more processors, one or more memories, and one or more cameras; one or more cameras, one or more memories are coupled to one or more processors, the one or more memories are used to store computer program code, the computer program code includes computer instructions, and one or more processors call computer instructions to enable the electronic device to execute a data sharing method provided in any possible implementation of the third aspect.

[0054] In a fifth aspect, the present application provides a computer-readable storage medium for storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes a data sharing method provided in any possible implementation of the third aspect.

[0055] In a sixth aspect, the present application provides a computer program product, which, when running on an electronic device, enables the electronic device to execute a data sharing method provided in any possible implementation of the third aspect above.

[0056] In the seventh aspect, the present application provides an electronic device, which includes: one or more processors, one or more memories, and one or more cameras; one or more cameras, one or more memories are coupled to one or more processors, one or more memories are used to store computer program code, the computer program code includes computer instructions, and one or more processors call computer instructions to enable the electronic device to execute a data sharing method provided in any possible implementation of the second aspect.

[0057] In an eighth aspect, the present application provides a computer-readable storage medium for storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes a data sharing method provided in any possible implementation of the second aspect.

[0058] In a ninth aspect, the present application provides a computer program product. When the computer program product runs on an electronic device, the electronic device executes a data sharing method provided in any possible implementation of the second aspect.

[0059] For the description of the beneficial effects of the third to ninth aspects, reference may be made to the description of the beneficial effects in the first and second aspects, and this application will not repeat them here. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figures 1A-1J show UI diagrams of data sharing between two applications;

[0061] Figures 2A-2G show UI diagrams for sharing data between two applications on different devices;

[0062] Figure 3 shows the specific implementation of data sharing between two applications on the same device through different sharing paths;

[0063] Figure 4 shows the specific implementation of sharing data between two applications on different devices through different sharing paths;

[0064] FIG5 shows a schematic diagram of the architecture of a system 50 provided in an embodiment of the present application;

[0065] FIG6A shows a schematic structural diagram of an electronic device 100 provided in an embodiment of the present application;

[0066] FIG6B shows a software structure block diagram of an electronic device 100 provided in an embodiment of the present application;

[0067] FIG7 shows a specific implementation diagram of how a unified data management framework stores first data shared by application A on electronic device 100;

[0068] FIG8 shows a specific implementation diagram of how application B on the electronic device 100 reads the first data shared by application A from the unified data management framework;

[0069] FIG9 shows a specific implementation diagram of how a unified data management framework on an electronic device 200 stores first data shared by an application A on an electronic device 100;

[0070] FIG10 shows a specific implementation diagram of how application B on electronic device 200 reads first data shared by application A on electronic device 100 from a unified data management framework on electronic device 200;

[0071] FIG11 is a schematic diagram of a method for how application A on an electronic device 100 shares data with application B on the electronic device 100 provided by an embodiment of the present application;

[0072] FIG12 is a schematic diagram of a method for how application A on an electronic device 100 shares data with application B on an electronic device 200, provided in an embodiment of the present application. DETAILED DESCRIPTION

[0073] The following is a clear and detailed description of the technical solutions in the embodiments of the present application in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is only a description of the association relationship between related objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0074] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of the technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

[0075] The term "user interface (UI)" in the following embodiments of this application refers to the media interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. A common form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It can be a visual interface element such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. displayed on the display screen of an electronic device.

[0076] First, two application scenarios involved in this application are introduced, a data sharing scenario between two applications on the same device and a data sharing scenario between two applications on different devices.

[0077] The data sharing path between two applications on the same device may include, but is not limited to, drag paths, clipboard paths, and cross-application paths. The two applications on the same device can be the same or different.

[0078] 1A to 1J show UI schematic diagrams of data sharing between two applications.

[0079] FIG. 1A-FIG . 1B show a UI schematic diagram of sharing data in application A to application B via a drag path.

[0080] The drag path on the same device may refer to selecting data in application A (for example, by long pressing to select) and then directly sharing it to application B via the drag path.

[0081] For example, application A may be a gallery application, and application B may be an instant messaging application.

[0082] As shown in Figure 1A, the electronic device 100 displays a split screen of an application interface 110 of a gallery application and an application interface 120 of an instant messaging application. The application interface 110 displays multiple pictures, and the application interface 120 displays a dialog box of a contact "Lily".

[0083] As shown in FIG1A , the electronic device 100 can receive a long press and drag operation by the user on a picture 1101 among multiple pictures, and directly share the picture 1101 to the contact “Lily” through the drag path.

[0084] As shown in FIG. 1B , after the user shares the picture 1101 to the contact “Lily” by dragging the path, the electronic device 100 may display the shared picture 1101 in the application interface 120 .

[0085] It is not limited to split-screen dragging. This application only uses split-screen dragging as an example for explanation. The dragging path can also be applied to other scenarios, and this application does not limit this.

[0086] FIG1C-FIG1E show another UI diagram for sharing data in application A to application B by dragging a path.

[0087] For example, application A may be a gallery application, and application B may be an instant messaging application.

[0088] 1C , the electronic device 100 displays an application interface 110 of a gallery application, which displays multiple pictures. The electronic device 100 can receive a user's long press and drag operation on a picture 1101 among the multiple pictures and temporarily store the picture 1101 in the transfer station 130 .

[0089] 1D , the electronic device 100 may open the instant messaging application and display the instant messaging application interface 120. The electronic device 100 may receive a user's long press and drag operation on the image 1101 in the transfer station 130 and share the image 1101 with the contact "Lily".

[0090] As shown in FIG. 1E , after the user shares the picture 1101 in the transfer station 130 with the contact “Lily”, the electronic device 100 may display the shared picture 1101 in the application interface 120 .

[0091] Figures 1F-1G show UI diagrams for sharing data in application B to application C via the clipboard path.

[0092] The clipboard path on the same device may mean that a user opens application A, copies or cuts data in application A, and temporarily stores the data in application A in the clipboard of electronic device 100. The user then opens application B and shares the data in application A temporarily stored in the clipboard of electronic device 100 with application B.

[0093] For example, application B may be an instant messaging application, and application C may be a browser application.

[0094] As shown in FIG1F , an application interface 140 of an instant messaging application is displayed on the electronic device 100 . A dialog box of the contact “Lily” is displayed in the application interface 140 . The dialog box may include multiple chat records, one of which may be a website link “www.huawei.com”.

[0095] The electronic device 100 receives a long press operation of the user on the URL link. In response to the long press operation of the user, the electronic device 100 can display a prompt box 1401 as shown in Figure 1F. The prompt box 1401 displays multiple options, such as a copy option, a forwarding option, a favorite option, and other options.

[0096] As shown in FIG. 1F , the electronic device 100 may receive a user input operation (eg, a single click) for a copy option. In response to the user input operation, the electronic device 100 may store the website link “www.huawei.com” in the clipboard.

[0097] Afterwards, the electronic device 100 opens the browser application. As shown in FIG1G , the electronic device 100 displays a user interface 150 of the browser application. The user interface 150 includes an input field 1501 for receiving a URL or text input by the user.

[0098] The user can long press input field 1501. In response to the user's input operation, electronic device 100 can display prompt information 1502. Prompt information 1502 displays multiple options, such as a paste option, a line break option, a full-screen input option, etc. As shown in FIG1G , electronic device 100 can receive a user input operation (e.g., a single click) for the paste option. In response to the user's input operation, electronic device 100 can display the URL link "www.huawei.com" stored in the clipboard in input field 1501 shown in FIG1H , without the user having to enter the URL link through the keyboard.

[0099] FIG1I-FIG1J are UI diagrams showing how to share data in application B to application C via a cross-application path.

[0100] The cross-application path may refer to: a user opens application A, selects data in application A, and then selects the application icon of application B to share the selected data with application B.

[0101] For example, application A may be an instant messaging application, and application B may be an instant messaging application.

[0102] As shown in FIG1I , electronic device 100 may display user interface 160 of application A. User interface 160 may include a user-selected image and icons of multiple applications. Electronic device 100 may receive a user input operation (e.g., a single click) on the instant messaging application icon. In response to the user input operation, electronic device 100 may share the selected image with the instant messaging application.

[0103] As shown in FIG1J , the electronic device 100 displays a user interface 170 of an instant messaging application, and the user interface 170 includes pictures shared from the gallery application to the instant messaging application.

[0104] The above-mentioned drag path between the same devices, clipboard path between the same devices and cross-application path are only used to explain this application, and may also include other more data sharing paths between two applications on the same device, which are not limited by this application.

[0105] The aforementioned drag paths between devices, clipboard paths between devices, and cross-application paths between devices are all determined through user interaction. In some embodiments, data can be automatically shared between two applications on the same device without user interaction. This type of shared path for automatically sharing data between two applications on the same device can be referred to as a cross-application automatic path.

[0106] The data sharing path between two applications on different devices may also include a drag path, a clipboard path, a cross-device path, etc. The two applications on different devices may be the same or different.

[0107] Exemplarily, the two devices may be electronic device 100 and electronic device 200, respectively, and electronic device 100 and electronic device 200 establish a communication connection.

[0108] 2A-2G show UI schematic diagrams of sharing data between two applications on different devices.

[0109] 2A-2B show a UI schematic diagram of sharing data in application A to application B via a drag path.

[0110] A drag path between different devices may refer to the following: a user opens application A on electronic device 100, selects and drags data in application A, and stores the data in application A in a transfer station on electronic device 100. Electronic device 100 and electronic device 200 may synchronize the data stored in their respective transfer stations. Electronic device 200, in response to the user's operation, may send the data in its transfer station to application B on electronic device 200. The data in the transfer station on electronic device 200 may include data in application A.

[0111] For example, application A may be an instant messaging application on electronic device 100 , and application B may also be an instant messaging application on electronic device 200 .

[0112] 1C-1D , the electronic device 100 may receive a user operation to temporarily store a picture 1101 in the gallery application in the transfer station 130. The electronic devices 100 and 200 may synchronize the data temporarily stored in their respective transfer stations.

[0113] 2A , the electronic device 200 can receive a user's operation to display the transfer station 140, which displays a picture 1101. The electronic device 200 can receive a user's long press and drag operation on the picture 1101 in the transfer station 140 to share the picture 1101 with the contact group chat.

[0114] As shown in FIG2B , after the user shares the picture 1101 in the transfer station 140 in the electronic device 200 to the contact "Group Chat", the electronic device 200 can display the picture 1101 in the dialog box of the contact "Group Chat". This realizes the sharing method of dragging the path to share data between two applications on different devices.

[0115] FIG. 2C and FIG. 2D show a UI schematic diagram of sharing data in application A to application B via a clipboard path.

[0116] A clipboard path between different devices may refer to: a user opening application A on electronic device 100, copying or pasting data in application A, and storing the data in application A in the clipboard of electronic device 100. Electronic device 100 and electronic device 200 can synchronize the data stored in their respective clipboards. Electronic device 200 can receive a user operation and send the data in the clipboard of electronic device 200 to application B on electronic device 200. The data in the clipboard of electronic device 200 may include data in application A.

[0117] For example, application A may be an instant messaging application on electronic device 100 , and application B may be a browser application on electronic device 200 .

[0118] 1F-1G , electronic device 100 may receive a user operation to store the URL "www.huawei.com" in the instant messaging application in the clipboard of electronic device 100. Electronic devices 100 and 200 may synchronize the data temporarily stored in their respective clipboards.

[0119] 2C , the electronic device 200 may receive a user operation to start a browser application and display a user interface 210 of the browser application. The user interface 210 includes an input field 2101 for receiving a URL or text input by the user.

[0120] The user can long-press input field 2101. In response to the user's input operation, electronic device 200 can display prompt information 2102. Prompt information 2102 displays multiple options, such as a paste option, a line break option, a full-screen input option, and so on. As shown in FIG2C , electronic device 200 can receive a user input operation (e.g., a single click) for the paste option. In response to the user's input operation, electronic device 200 can display the URL "www.huawei.com" stored in the clipboard in input field 2101 shown in FIG2D . This enables data sharing between two applications on different devices via clipboard path sharing.

[0121] Figures 2E-2G show UI diagrams for sharing data in application B to application C via a cross-device path.

[0122] The cross-device path may refer to: the user opens application A in electronic device 100 , selects data in application A, and then selects the device icon of electronic device 200 to share the selected data with electronic device 200 .

[0123] For example, application A may be a gallery application on electronic device 100 , and application B may be a gallery application on electronic device 200 .

[0124] As shown in Figure 2E, the electronic device 100 can display the user interface of the gallery application on the electronic device 100. The user interface of the gallery application may include pictures selected by the user, icons of multiple nearby devices (for example, the "HUAWEIP50" option, the "Alee's phone" option, the "Alee's tablet" option) and application icons of multiple applications. The electronic device 100 can receive the user's input operation for the "HUAWEIP50" option (for example, a single click), and in response to the user's input operation, the electronic device 100 can share the selected picture to the electronic device 200. The device identifier of the electronic device 200 may be "HUAWEIP50".

[0125] After the electronic device 200 receives the picture sent by the electronic device 100, the electronic device 200 may display the receiving window 4130 shown in Figure 2F. The receiving window 4130 may include a thumbnail 4131 of the picture that the electronic device 100 has shared with the electronic device 200, a receiving prompt 4132, an open control 4133, and a storage control 4134. Among them, the receiving prompt 4132 can be used to prompt the user that the current electronic device 200 has received the picture sent by the electronic device 100. Among them, the prompt type of the receiving prompt 4132 can be any one or more of a text prompt (for example, "Received 1 picture sent to you by Daniel"), an image prompt, an animated image prompt, and a video prompt. The open control 4133 can be used to trigger the electronic device 200 to display a display interface including the pictures sent by the electronic device 100. The storage control 4134 can be used to trigger the electronic device 200 to save the pictures sent by the electronic device 100 in a designated storage path locally on the electronic device 200.

[0126] The electronic device 200 may receive user input (eg, a single click) on the storage control 4134 , and in response to the input, the electronic device 200 may display a storage interface 4140 as shown in FIG. 2G .

[0127] As shown in Figure 2G, the storage interface 4140 may include one or more storage path options, a return to previous page control 4141, and the like. Since the electronic device 100 shares pictures with the electronic device 200, the one or more storage path options may include one or more album options (for example, an "All Photos Album" option 4142, a "Camera Album" option, a "Screenshot Directory Album" option, a "Chat Application Album" option, a "Changlian Application Album" option, an "Other Albums" option, and the like). Optionally, the storage interface 4140 may further include a new control 4143, which may be used to trigger the electronic device 200 to add a new album option to the storage interface 4140.

[0128] The electronic device 200 may receive a user input (e.g., a single click) on the "All Photo Albums" option 4142. In response to the input, the electronic device 200 may store the pictures shared by the electronic device 100 to the electronic device 200 in the storage path corresponding to the All Photo Albums. After the electronic device 200 stores the pictures shared by the electronic device 100 to the electronic device 200 in the storage path corresponding to the All Photo Albums, when the electronic device 200 opens the album interface of the All Photo Albums in the gallery application, the album interface of the All Photo Albums may include thumbnails of the pictures shared by the electronic device 100 to the electronic device 200.

[0129] Optionally, the electronic device 200 may not display the user interface shown in FIG. 2F and FIG. 2G . After the electronic device 200 receives the picture shared by the electronic device 100 , the electronic device 200 may directly store the received picture in the gallery of the electronic device 200 .

[0130] The above-mentioned drag paths between different devices, clipboard paths between different devices, and cross-device paths are only used to explain this application, and may also include other data sharing paths between two applications on more different devices, which are not limited by this application.

[0131] The aforementioned drag paths between different devices, clipboard paths between different devices, and cross-device paths between different devices are all determined under the active operation of the user. In some embodiments, a device can automatically share data with other devices without user operation. This sharing path where a device automatically shares data with other devices can be referred to as an automatic cross-device path.

[0132] Based on the description of FIG. 1A to FIG. 1J , it can be known that data can be shared between two applications on the same device through different paths.

[0133] Different applications have different definitions of data, and different sharing paths have different data definition standards. The data shared between applications through each sharing path must meet the data definition standards of each sharing path.

[0134] Before App A sends shared data to App B, it needs to obtain the data definition standard of the current sharing path and redefine the shared data based on the data definition standard of the current sharing path to obtain the redefined shared data. App A then sends the redefined shared data to App B via the current sharing path.

[0135] As shown in Figure 3, the data sharing path between two applications on the same device may include, but is not limited to, a drag path and a clipboard path. The data definition standards corresponding to the drag path and the clipboard path are different.

[0136] For example, when the shared data is a picture, the type definition of the drag path for the picture may be "image", and the type definition of the clipboard path for the picture may be "picture".

[0137] For another example, when the shared data is a video, the drag path may be defined as "video" for the video type, and the clipboard path may be defined as "vlog" for the video type.

[0138] Before application A sends shared data to application B via a drag path or clipboard path, application A obtains the data definition standards corresponding to each path from the drag path model or clipboard path model. Application A then redefines the shared data according to the data definition standards in the drag path or clipboard path, generating the redefined shared data. Application A then sends the redefined shared data to the drag path or clipboard path, which then sends the redefined shared data to application B.

[0139] After receiving the redefined shared data, App B needs to obtain the data definition standards corresponding to each path from the drag path model or clipboard path model. App B then parses the redefined shared data according to the data definition standards in the drag path or clipboard path to obtain the shared data content, which the user can then use in App B.

[0140] As can be seen from the above process, the data definition standards for different sharing paths are different. The sender of shared data needs to redefine the shared data based on the data definition standards of the different sharing paths. The receiver of shared data also needs to parse the shared data based on the data definition standards of the different sharing paths. This makes the data sending and receiving process more complicated.

[0141] Figure 4 shows the specific implementation of data sharing between two applications on different devices through different sharing paths. Figure 4 is similar to Figure 3, except that Figure 3 is the specific implementation of data sharing between two applications on the same device through different sharing paths, and Figure 4 is the specific implementation of data sharing between two applications on different devices through different sharing paths. For the specific introduction of the embodiment of Figure 4, please refer to the description in Figure 3. As can be seen from Figure 4, Figure 4 has the same problem as Figure 3. The data definition standards that do not pass through the sharing path are different, and the sender of the shared data needs to redefine the shared data based on different data definition standards. The receiver of the shared data also needs to parse the shared data based on different data definition standards. This makes the processing process of sending and receiving data more cumbersome.

[0142] Based on the above problems, the present application provides a data sharing method. The method includes: for different applications and different sharing paths, the electronic device 100 provides a set of unified data definition standards (which can be called specified data definition standards). Through this method, the sender of the shared data does not need to consider the type of sharing path, but only needs to define the shared data based on the specified data definition standard, and then send it to the recipient of the shared data through the sharing path. The recipient of the shared data also does not need to consider the type of sharing path, but only needs to parse the redefined shared data based on the specified data definition standard to obtain the shared data, which simplifies the processing flow of data transmission between the sender and the recipient.

[0143] The specified data definition standard may include the attribute definition of the data and the content definition of the data. The attribute definition of the data may include, but is not limited to, the type definition, size definition, creation time definition, content definition of the data, etc. If the data type is file data, the content definition of the data may include the storage path of the data on the device, for example, the storage path may be the uniform resource identifier (URI) of the data. If the data type is non-file data, the content definition of the data may include the text content of the data. For a detailed introduction to the specified data definition standard, please refer to the description in the embodiment of Table 1.

[0144] This application can be applied to data sharing between two applications on the same device. In some embodiments, application A on electronic device 100 automatically shares data with application B on electronic device 100 without user intervention. Application A can obtain a specified data definition standard and define the data in application A (e.g., first data) based on the specified data definition standard to obtain redefined first data. Application B can obtain the redefined first data. Application B can parse the redefined first data based on the specified data definition standard to obtain and use the first data. In other embodiments, application A on electronic device 100 can also receive a user operation to select the first data in application A and send the first data to application B on electronic device 100 via a cross-application manual path. Specifically, application A can obtain a specified data definition standard and, based on defining the first data, obtain the redefined first data. Application A then sends the redefined first data to application B. Application B can also obtain a specified data definition standard and, based on the first data, parse the redefined first data to obtain the first data, which application B can use. This simplifies the processing flow of data transmission between two applications on the same device.

[0145] For example, users can share pictures in the gallery application to the instant messaging application through any sharing path including the drag path, clipboard path, cross-application manual path, or cross-application automatic path. Regardless of the drag path, clipboard path, cross-application manual path, or cross-application automatic path, the data definition standards of these four sharing paths are the same. The gallery application only needs to redefine the pictures in the gallery application based on the specified data definition standard to obtain the redefined pictures, and the gallery application then sends the redefined pictures to the instant messaging application through any selected sharing path. The instant messaging application also does not need to pay attention to which sharing path the redefined pictures are received. The instant messaging application only needs to parse the redefined pictures based on the specified data definition standard, obtain the pictures, and use the pictures. The processing flow of data transmission between the gallery application and the instant messaging application on the same device is simplified.

[0146] The present application can be applied to data sharing between two applications on different devices. Electronic device 100 and electronic device 200 establish a communication connection. In some embodiments, application A on electronic device 100 automatically shares data with application B on electronic device 200 without user operation. In other embodiments, application A on electronic device 100 can also share data with application B on electronic device 200 based on user operation. Specifically, application A on electronic device 100 can obtain the specified data definition standard and the data in application A (for example, the first data), and define the first data based on the specified data definition standard to obtain the redefined first data. Electronic device 100 sends the redefined first data to electronic device 200 via a communication connection. Application B on electronic device 200 can obtain the redefined first data through any sharing path including a drag path, a clipboard path, a cross-device manual path, or a cross-device automatic path. And the redefined first data is parsed based on the specified data definition standard to obtain the first data and use the first data. The processing flow of data transmission between two applications on different devices is simplified.

[0147] In some embodiments, the redefined first data may also be referred to as first definition data.

[0148] For example, a user can share pictures in the gallery application in electronic device 100 to electronic device 200 through any sharing path including drag path, clipboard path, cross-device manual path, or cross-device automatic path. Regardless of whether it is a drag path, clipboard path, cross-device manual path, or cross-device automatic path, the data definition standards of these four sharing paths are the same. The gallery application in electronic device 100 only needs to redefine the pictures in the gallery application based on the specified data definition standard to obtain the redefined pictures. The gallery application then sends the redefined pictures to the communication module in electronic device 100 through any sharing path, and the communication module in electronic device 200 can receive the redefined pictures. The gallery application in electronic device 200 can obtain the redefined pictures through the corresponding sharing path. The gallery application in electronic device 200 does not need to pay attention to which sharing path the redefined pictures are received. The gallery application in electronic device 200 only needs to parse the redefined pictures based on the specified data definition standard to obtain the pictures and use them. This simplifies the processing flow of data transmission between two gallery applications on different devices.

[0149] Next, a system architecture provided by an embodiment of the present application is introduced.

[0150] Please refer to FIG5 , which shows a schematic diagram of the architecture of a system 50 provided in an embodiment of the present application.

[0151] The system 50 may include one electronic device, or may include multiple electronic devices. The system 50 shown in FIG5 includes two electronic devices, such as the electronic device 100 and the electronic device 200 .

[0152] The types of electronic devices may include, but are not limited to, any of the following: mobile phones, tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, smart screens, wearable devices, augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, car computers, smart headphones, game consoles, and may also include Internet of Things (IOT) devices or smart home devices such as smart water heaters, smart lamps, smart air conditioners, etc. Without limitation, the multiple devices in system 10 may also include non-portable terminal devices such as laptop computers with touch-sensitive surfaces or touch panels, desktop computers with touch-sensitive surfaces or touch panels, and the like.

[0153] The software operating system (OS) of electronic devices, including but not limited to Etc. Among them, For Huawei's Hongmeng system. Optionally, multiple electronic devices can be configured with the same software operating system, for example,

[0154] The electronic device 100 and the electronic device 200 may establish a communication connection through any of the following methods.

[0155] Method 1: Multiple electronic devices can be connected to the same network. For example, multiple electronic devices can be connected to the same local area network to establish communication connections.

[0156] Method 2: Multiple electronic devices can also log in to the same system account to establish a communication connection. For example, the system account logged in by multiple electronic devices can all be "HW1234".

[0157] Method 3: System accounts logged in on multiple electronic devices can all belong to the same account group. For example, the system accounts logged in on multiple electronic devices include "HW001," "HW002," and "HW003." System accounts "HW001," "HW002," and "HW003" all belong to the account group "Huawei Home."

[0158] Method 4: Multiple electronic devices can establish communication connections through near field communication (NFC), Bluetooth (BT), wireless local area networks (WLAN) such as wireless fidelity point to point (Wi-Fi P2P), infrared technology (IR), etc.

[0159] Method 5: Multiple electronic devices can create a temporary account group by scanning the same QR code and establish a network connection to achieve communication.

[0160] Not limited to the above five methods, the electronic device 100 can also establish a communication connection in other ways, which is not limited in the present embodiment. In addition, multiple electronic devices can also establish a communication connection in combination with any of the above methods, which is not limited in the present embodiment.

[0161] In the case where the system 50 includes only one electronic device (e.g., electronic device 100), electronic device 100 can implement data sharing between two applications on the same device based on the method provided in this application, simplifying the processing flow of data transmission between two applications on the same device. Specifically, application A can obtain a specified data definition standard and define the data (e.g., first data) in application A based on the specified data definition standard to obtain redefined first data. Application B can obtain the redefined first data. Application B can parse the redefined first data based on the specified data definition standard to obtain the first data and use the first data. In other embodiments, application A on electronic device 100 can also receive a user operation, which is used to select the first data in application A and send the first data to application B on electronic device 100 via a cross-application manual path. Specifically, application A can obtain a specified data definition standard and, based on defining the first data, obtain the redefined first data. Application A then sends the redefined first data to application B. Application B can also obtain a specified data definition standard and, based on the first data, parse the redefined first data to obtain the first data, and application B can use the first data. This simplifies the data transfer process between two applications on the same device.

[0162] When the system 50 includes multiple electronic devices (e.g., electronic device 100 and electronic device 200), electronic device 100 and electronic device 200 can implement data sharing between two applications on different devices based on the method provided in this application, simplifying the processing flow of data transmission between two applications on different devices. Specifically, in some embodiments, application A on electronic device 100 automatically shares data with application B on electronic device 200 without user operation. In other embodiments, application A on electronic device 100 can also share data with application B on electronic device 200 based on user operation. Specifically, application A on electronic device 100 can obtain the specified data definition standard and the data in application A (e.g., first data), and define the first data based on the specified data definition standard to obtain redefined first data. Electronic device 100 sends the redefined first data to electronic device 200 via a communication connection. Application B on electronic device 200 can obtain the redefined first data through any sharing path including a drag path, a clipboard path, a cross-device manual path, or a cross-device automatic path. The redefined first data is parsed based on the specified data definition standard to obtain the first data and use the first data. Simplifies the data transmission process between two applications on different devices.

[0163] In some embodiments, the electronic device 200 may also be a cloud device such as a server to enable data sharing between the electronic device and the server.

[0164] The following embodiments of the present application are described using the electronic device 100 as a mobile phone as an example, and the electronic device 200 may also have the same or similar components.

[0165] FIG. 6A shows a schematic structural diagram of the electronic device 100 .

[0166] The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0167] It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0168] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0169] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0170] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0171] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0172] It is understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely an illustrative illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0173] The charging management module 140 is configured to receive charging input from a charger.

[0174] The power management module 141 is used to connect the battery 142 , the charging management module 140 and the processor 110 .

[0175] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0176] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0177] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0178] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0179] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0180] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with a network and other devices through wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0181] Electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0182] The display screen 194 is used to display images, videos, etc.

[0183] The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

[0184] The ISP is used to process data fed back by the camera 193 .

[0185] The camera 193 is used to capture still images or videos.

[0186] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0187] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. This allows electronic device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0188] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in electronic device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0189] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

[0190] Random access memory may include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM, for example, the fifth generation of DDR SDRAM is generally referred to as DDR5 SDRAM), etc.

[0191] Non-volatile memory may include disk storage devices and flash memory.

[0192] The external memory interface 120 can be used to connect to an external non-volatile memory to expand the storage capacity of the electronic device 100. The external non-volatile memory communicates with the processor 110 via the external memory interface 120 to implement data storage. For example, files such as music and videos can be stored in the external non-volatile memory.

[0193] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0194] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0195] The speaker 170A, also called a "horn", is used to convert audio electrical signals into sound signals.

[0196] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals.

[0197] Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals.

[0198] The headphone jack 170D is used to connect a wired headphone.

[0199] The pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. The gyroscope sensor 180B can be used to determine the motion posture of the electronic device 100. The air pressure sensor 180C is used to measure air pressure. The magnetic sensor 180D includes a Hall sensor. The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in various directions (generally three axes). The distance sensor 180F is used to measure distance. The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The ambient light sensor 180L is used to sense the brightness of ambient light. The fingerprint sensor 180H is used to collect fingerprints. The temperature sensor 180J is used to detect temperature. The touch sensor 180K is also called a "touch device". The bone conduction sensor 180M can obtain vibration signals.

[0200] The buttons 190 include a power button, a volume button, etc. The buttons 190 can be mechanical buttons or touch buttons.

[0201] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts and touch vibration feedback. For example, touch operations on different applications (such as taking photos, playing audio, etc.) can correspond to different vibration feedback effects. Motor 191 can also correspond to different vibration feedback effects for touch operations on different areas of the display 194.

[0202] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0203] The SIM card interface 195 is used to connect a SIM card.

[0204] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present invention, the Android system with a layered architecture is used as an example to illustrate the software structure of the electronic device 100.

[0205] FIG6B is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present invention.

[0206] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0207] The application layer can include a series of application packages.

[0208] As shown in FIG6B , the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

[0209] The application framework layer provides an application programming interface (API) for applications in the application layer. The application framework layer includes some predefined functions.

[0210] As shown in FIG. 6B , the application framework layer may include a unified data management framework (UDMF), various types of data sharing paths, and the like.

[0211] Among them, the unified data management framework includes multiple functional modules, including but not limited to: data definition standard model, data access / access module, data lifecycle management module, data security module, data authority management module, storage management module, etc.

[0212] The types of data sharing paths include but are not limited to: drag path, clipboard path, cross-application manual path, cross-device manual path, cross-application automatic path and cross-device automatic path, etc. Among them, the drag path, clipboard path, cross-application manual path and cross-application automatic path can be used as data sharing paths between two applications on the same device. The drag path, clipboard path, cross-device manual path and cross-device automatic path can be used as data sharing paths between two applications on different devices. Not limited to these data sharing paths. In some embodiments, data sharing can be achieved between two applications on the same device or between two applications on different devices without going through the above-mentioned data sharing path. The above-mentioned data sharing path is also only used to introduce this application, and this application does not limit this.

[0213] Optionally, in some embodiments, the data sharing path between two applications on the same device, such as a drag path or a clipboard path, and the data sharing path between two applications on different devices, such as a drag path or a clipboard path, may be the same path or different paths, and this application does not limit this.

[0214] The data definition standard model stores the specified data definition standards. The specified data definition standards are used by each application to define shared data according to these standards.

[0215] The data access module is used to receive the redefined shared data sent by the application and temporarily store the redefined shared data in the unified data management framework.

[0216] The data access module is also used for applications to read and redefine shared data from the unified data management framework.

[0217] The data lifecycle management module is used to manage the lifecycle of the redefined shared data stored in the unified data management framework, such as deleting the redefined shared data or continuing to store the redefined shared data.

[0218] The data security module is used to protect the security of redefined shared data stored in a unified data management framework, for example, through encrypted storage and other methods.

[0219] The data authority management module is used to verify whether the application has the ability and authority to access the redefined shared data before the application reads the redefined shared data from the unified data management framework.

[0220] The storage management module is used to temporarily store the redefined shared data.

[0221] For an introduction to the various functional modules in the unified data management framework, please refer to the detailed description in the embodiments of Figures 7 to 10, and this application will not go into details here.

[0222] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0223] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0224] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0225] The system library can include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0226] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0227] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0228] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0229] A 2D graphics engine is a drawing engine for 2D drawings.

[0230] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0231] Introduction to specified data definition standards and definition of shared data based on specified data definition standards.

[0232] First, the specified data definition standards stored in the data definition standard model in the unified data management framework are introduced.

[0233] The specified data definition standard may include data attribute definitions, which may include but are not limited to data type definition, size definition, creation time definition, data content definition, etc. This ensures that the sender's attribute definition of the shared data is the same as the receiver's, reducing the processing flow of sending and receiving data.

[0234] This application provides a data definition standard. Before sharing data, different applications need to define the shared data according to this standard. After receiving the shared data, different applications also need to parse the shared data based on this standard. In other words, the data definition standard is unified for different applications and different sharing paths, achieving a unified format for shared data.

[0235] The types of data may include, but are not limited to, plain text data, formatted text data, rich text data, link data, image data, file data, media file data, folder data, application project data, table data, etc. In other embodiments, other data may also be included, which is not limited in this application.

[0236] The following embodiments of the present application are described by taking the attribute definition of data including the type definition of data and the content definition of data as an example.

[0237] Table 1

[0238] As shown in Table 1, text data and file data can be referred to as basic data. This type of data can be transferred across applications, devices, and operating systems. In other words, data that can be transferred across applications, devices, and operating systems is referred to as basic data.

[0239] System-defined data can be transferred across applications and devices within the same operating system. In other words, data that can be transferred across applications and devices within the same operating system is called system-defined data.

[0240] Application-defined data can be transferred across devices and operating systems within the same application. In other words, data that can be transferred across devices and operating systems within the same application is called system-defined data.

[0241] As shown in Table 1, the type definition of plain text data defined in the specified data definition standard is "plain-text", and the content of plain text data is defined as plain text content. The type definition of plain text data can be expressed as text.plain-text.

[0242] The type definition of formatted text data defined in the specified data definition standard is "styled text," and the content of the formatted text data is defined as plain text. The type definition of formatted text data can be expressed as text.styled text.

[0243] The type definition of rich text data defined in the specified data definition standard is "HTML," and the content of rich text data is defined as plain text. The type definition of rich text data can be expressed as text.HTML.

[0244] The type of link data defined in the specified data definition standard is defined as "link", and the content of the link data is defined as plain text content. The type definition of the link data can be expressed as text.link.

[0245] The image data type defined in the specified data definition standard is defined as "image," and the image data content is defined as a URI. The image data URI indicates the storage path of the image data on the device. The image data type definition can be expressed as file.image.

[0246] The video data type defined in the data definition standard is defined as "video," and the video data content is defined as a URI. The video data URI indicates the storage path of the video data on the device. The video data type definition can be expressed as file.video.

[0247] The audio data type defined in the specified data definition standard is defined as "audio," and the audio data content is defined as a URI. The audio data URI is used to indicate the storage path of the audio data on the device. The audio data type definition can be expressed as file.audio.

[0248] The document data type defined in the specified data definition standard is defined as "word," and the document data content is defined as a URI. The document data URI indicates the storage path of the document data on the device. The document data type definition can be expressed as file.word.

[0249] The presentation file data type defined in the specified data definition standard is defined as "powerpoint," and the presentation file data content is defined as a URI. The presentation file data URI indicates the storage path of the presentation file data on the device. The presentation file data type definition can be expressed as file.powerpoint.

[0250] The table data type defined in the data definition standard is defined as "excel," and the table content is defined as a URI. The table data URI indicates the storage path of the table data on the device. The table data type definition can be expressed as file.excel.

[0251] The type definition of portable file format data defined in the specified data definition standard is "pdf," and the content of the portable file format data is defined as a URI. The URI of the portable file format data indicates the storage path of the portable file format data on the device. The type definition of the portable file format data can be expressed as file.pdf.

[0252] The type definition of the desktop icon control defined in the specified data definition standard is "appItem", and the content of the application item data is defined as plain text. The type definition of the desktop icon control can be expressed as SDT.appItem.

[0253] The data card type defined in the specified data definition standard is defined as "form", and the window data content is defined as plain text. The data card type definition can be expressed as SDT.form.

[0254] The type definition of high-performance bitmap data defined in the specified data definition standard is "pixelmap", and the content of high-performance bitmap data is defined as plain text content. The type definition of high-performance bitmap data can be expressed as SDT.pixelmap.

[0255] The type definition of application-customized graphics data defined in the specified data definition standard is "custom shape," and the content of high-performance bitmap data is defined as plain text. The type definition of application-customized graphics data can be expressed as ADT.custom shape.

[0256] That is, for the same type of data, different applications have the same type definition for the data. For example, for image data, different applications have the same type definition for the image data as "image".

[0257] If the data type is file data, the data content definition may include the data's URI, which indicates the data's storage path on the device. In other words, when the data's content definition is a URI, an application can send the data's storage path to another application without directly sending the data's content to the other application. When the other application uses the data, it can retrieve the data's content based on the data's URI.

[0258] In the case where the data type is non-file data, the content definition of the data may include text content of the data. In other words, when the content definition of the data is plain text content, the application may directly send the content of the data to another application.

[0259] It should be noted that Table 1 only exemplifies the standard type definitions and standard content definitions of some data, and may also include standard type definitions and standard content definitions of many other data, which are not limited in this application.

[0260] Optionally, before application A sends the redefined shared data to the sharing path, it is necessary to generate a unified management protocol for the shared data. The unified management protocol for the shared data is used to describe the sharing path for the shared data.

[0261] Application A can obtain the unified management protocol standard from the unified data management framework and generate a unified management protocol for sharing data based on the unified management protocol standard. The unified management protocol standard may include preset fields.

[0262] Illustratively, the unified management protocol standard may be as follows: udmf: / / intension / bundleName / groupName / guid.

[0263] The "udmf" field may be a protocol name, which is the abbreviation of Unified Data Management Framework.

[0264] The "intension" field can be the name of the sharing path. When the shared data is not determined by user operation, but is automatically determined by the application, the content of the "intension" field can be the name of the cross-application automatic channel or the cross-device automatic path. For example, the name of the cross-application automatic channel can be automatic1, and the name of the cross-device automatic path can be automatic2. When the shared data is determined by user operation, the content of the "intension" field can be any one of the names of the drag path, the clipboard path, the cross-application manual path, and the cross-device manual path. For example, the name of the drag path can be drag, the name of the clipboard path can be clipboard, the name of the cross-application manual path can be manual1, and the name of the cross-device manual path is manual2.

[0265] It should be noted that the "intension" field can also include the names of other sharing paths. The names of the above-mentioned sharing paths are only used to explain this application and this application does not limit them.

[0266] It should be noted that the name of the drag path and the name of the clipboard path between two applications on the same device may be the same as or different from the name of the drag path and the name of the clipboard path between two applications on different devices.

[0267] The "bundleName" field can be the name of the data source, such as the name of the application.

[0268] The "groupName" field can be a group name. Applications can share multiple data at once, so these multiple data belong to one group. Different group names are used for different data.

[0269] The "guid" field can be a data ID generated by the system. The data ID of each data is different and is used to identify different data in the same group.

[0270] The unified management protocol standard may also include other fields or other formats, which are not limited in this application.

[0271] Application A can generate a unified management protocol for shared data based on the unified management protocol standard. Application A can also generate instructions for using shared data based on the specified data definition standard. Application A sends the unified management protocol for shared data and the instructions for using shared data to the unified data management framework, which can bind and store the unified management protocol for shared data and the instructions for using shared data. For example, the unified management protocol for shared data and the instructions for using shared data can be stored in a key-value format, and the unified data management framework can obtain the instructions for using shared data based on the unified management protocol for shared data.

[0272] Optionally, the usage instructions for shared data may also be generated by application A based on a specified data definition standard. In other words, multiple fields in the usage instructions for shared data are defined in the specified data definition standard.

[0273] The usage instructions for sharing data may include multiple fields, such as the permission field, the source app field, the source OS field, and the data type field.

[0274] The "permission" field can be a personalized permission description of the data. Personalized permissions of data can include public permissions, system permissions, and application permissions.

[0275] The public permission may indicate that the data is unauthorized data and any application, any device, and any operating system can use the data with the public permission. The public permission identifier may be public.

[0276] System permissions can mean that devices with fixed systems installed can use the data. Fixed systems can include but are not limited to: etc. The system permissions can be Any one of .

[0277] Application permissions may indicate that a target application on a device can use the data. The identifier of the application permission may be the name of the target application.

[0278] The source app field specifies the application from which the shared data originates. This field may include the application ID of the application from which the shared data originates. For example, when the data is application-defined, such as application-defined graphics, application A may enter the application ID of the application from which the data originates in the source app field.

[0279] The source os field specifies the operating system from which the shared data originates. This field can include the operating system identifier of the operating system from which the shared data originates. For example, when the data is system-defined, such as desktop icon controls, data cards, and high-performance bitmaps, Application A can enter the operating system identifier of the electronic device where Application A is installed in the source os field.

[0280] For example, when the data is basic data such as text data and file data, application A may also fill in the application identifier of the source application in the source app field and the operating system identifier of the source operating system in the source os field.

[0281] The source app field and the source os field are managed by the user unified data framework to determine whether application B is capable of accessing the data. For specific judgment rules, please refer to the description of step 2 in Figure 8. This application will not be repeated here.

[0282] The data type field is used to describe the type of shared data. For example, when the shared data is a picture, the data type field may include the picture type "file.image".

[0283] Optionally, the multiple fields in the usage description of the shared data may further include a life field, which is a field used to describe the life cycle of the data.

[0284] Optionally, in other embodiments, one or more fields in the shared data usage instructions may also be incorporated into a unified management protocol for shared data, which may be used to describe the personalized permissions for shared data, the application from which the shared data originates, the operating system from which the shared data originates, and the type of shared data. This application does not impose any limitation on this.

[0285] Different apps on a device can set different personalized permissions for different data within the app. Personalized permissions for shared data can be described based on the "permission" field.

[0286] For example, personalized permissions for the above-mentioned plain text data, formatted text data, rich text data, link data, image data, video data, audio data, document data, presentation file data, table data, and portable file format data can be set as public permissions.

[0287] The personalized permissions for the system customized data such as the above-mentioned application project data, window data, and high-performance bitmap data can be set as system permissions.

[0288] The personalized permissions for the above-mentioned application custom data can be set as application permissions.

[0289] For example, before first data in application A on electronic device 100 is shared with application B on electronic device 200 or application B on electronic device 100, application A needs to define the first data based on a specified data definition standard to obtain redefined first data. Application A also needs to generate a unified management protocol for the first data based on a unified management protocol standard and generate instructions for use of the first data based on the specified data definition standard, so that the recipient can obtain the sharing path of the first data based on the unified management protocol of the first data, and the recipient can obtain personalized permissions for the first data based on the instructions for use of the first data.

[0290] For example, when the first data is a picture, redefining the first data may include the type definition of the first data and the content definition of the first data. The type definition of the first data may be "image", the content definition of the first data may be "URI of the first data", and the unified management protocol of the first data may be "udmf: / / drag / library application / 123 / 123456". The usage instructions of the first data may be

[0291] For another example, when the first data is plain text, redefining the first data may include the type definition of the first data and the content definition of the first data. The type definition of the first data may be "plain-text", and the content definition of the first data may be "department regular meeting at 4 pm". The sharing agreement of the first data may be The usage instructions for the first data can be

[0292] Based on the unified management protocol of the first data, it can be obtained that the sharing path of the first data is a drag path.

[0293] Based on the usage instructions of First Data, it can be known that the personalized permission of First Data is limited to those who have installed A device operating the system may use the first data.

[0294] Optionally, in other embodiments, one or more fields in the usage description of the first data may also be incorporated into the unified management protocol of the first data, and the unified management protocol of the first data may be used to describe the personalized permissions of the first data, the application from which the first data originates, the operating system from which the first data originates, and the type of the first data. This application does not impose any limitation on this.

[0295] Next, we will introduce the specific implementation of the data sharing scenario between two applications on the same device and the data sharing scenario between two applications on different devices.

[0296] Data sharing between two apps on the same device (Figures 7 and 8)

[0297] For example, the two applications may be application A on electronic device 100 and application B on electronic device 100. In some embodiments, application A may receive a user operation to share the first data in application A with application B. In other embodiments, application A may also automatically share the first data in application A with application B.

[0298] FIG. 7 shows a specific implementation diagram of how a unified data management framework stores first data shared by application A on the electronic device 100 .

[0299] The method steps for storing the first data shared by application A in the unified data management framework are as follows (step 1 to step 18):

[0300] 1. Application A obtains the unified management protocol standard and specified data definition standard from the data definition standard model.

[0301] After being installed on electronic device 100, application A can obtain the unified management protocol standard and the specified data definition standard from the data definition standard model. Application A can also obtain the unified management protocol standard and the specified data definition standard from the data definition standard model when it needs to share data. This application does not limit this.

[0302] In some embodiments, the unified management protocol standard and the specified data definition standard may also be one protocol standard.

[0303] 2. Application A determines the first data to be shared.

[0304] In some embodiments, application A may determine the first data to be shared based on a user operation. In this case, application A may share data with other applications on the electronic device 100 under the user's operation.

[0305] In other embodiments, application A may also automatically determine the first data to be shared without user operation. In this case, application A may automatically share data with other applications on the electronic device 100.

[0306] 3. Application A defines the first data based on the specified data definition standard to obtain redefined first data.

[0307] For an introduction to the specified data definition standards, please refer to the description in Table 1.

[0308] This application provides a set of data definition standards. Before applications share data, different applications can define the shared data based on this unified data definition standard. The recipient of the shared data can also parse the shared data based on this unified data definition standard, thus reducing the processing flow of data transmission and reception.

[0309] In other embodiments, the shared data is not limited to being defined according to the unified data definition standard. Applications can also be instructed to define the data within the application according to the unified data definition standard when generating application data. In this way, after the application determines the shared data, the shared data has already been defined according to the unified data definition standard, and the application does not need to define it again.

[0310] Application A defines the first data based on the specified data definition standard. Application A may define the attributes of the first data based on the specified data definition standard, including but not limited to the type definition of the first data, the size definition of the first data, the creation time definition of the first data, the content definition of the first data, etc.

[0311] For example, when the first data is non-text data (or file data), such as an image, redefining the first data may include a type definition of the first data and a content definition of the first data. The type definition of the first data may be "image," and the content definition of the first data may be "URI of the first data."

[0312] For another example, when the first data is text data, redefining the first data may include defining the type of the first data and defining the content of the first data. The type definition of the first data may be "plain-text" and the content definition of the first data may be "department regular meeting at 4:00 PM."

[0313] 4. Application A generates a unified management protocol for the first data and instructions for use of the first data.

[0314] Application A can generate a unified management protocol for first data based on a unified management protocol standard and generate instructions for use of the first data based on a specified data definition standard. The unified management protocol for first data describes the sharing path for the first data, and the instructions for use of the first data describe the personalized rights for the first data. For an introduction to the unified management protocol standard, please refer to the description in the embodiment of Table 1, and this application will not elaborate on it here.

[0315] For example, if the sharing path of the first data is a drag path, the personalized permission of the first data is to install The application on the device of the operating system can use the first data. Then the unified management protocol of the first data can be "udmf: / / drag / library application / 123 / 123456". The usage instructions of the first data can be

[0316] It should be noted that step 4 may also be performed before step 3, or simultaneously with step 3. Step 1 may also be performed after step 2, which is not limited in this application.

[0317] 5. Application A sends the redefined first data, the unified management protocol of the first data, and the usage instructions of the first data to the data access module.

[0318] After obtaining the redefined first data, the unified management protocol for the first data, and the instructions for using the first data, application A sends the redefined first data, the unified management protocol for the first data, and the instructions for using the first data to a data access / access module in the unified data management framework so that the data access / access module can verify the redefined first data.

[0319] 6. The data access / access module obtains the specified data definition standard from the data definition standard model.

[0320] 7. The data access / access module verifies the redefined first data based on the specified data definition standard and determines that the definition of the redefined first data meets the requirements.

[0321] After receiving the redefined first data sent by Application A, the data access module can verify the redefined first data based on the specified data definition standard obtained from the data definition standard model. This verification primarily verifies whether the redefined first data complies with the unified data management framework. Only data that passes verification can be shared with other applications through the unified data management framework to prevent Application A from defining the first data in a manner that does not conform to the specified data definition standard.

[0322] The data access module verifies the redefined first data based on the specified data definition standard according to the following rules:

[0323] Redefine whether the first data is defined in accordance with the data attribute definition and data content definition specified in the specified data definition standard. For example, if the first data is image data, redefine the type definition of the image data included in the first data to "image" instead of "picture." Redefine the content definition of the image data included in the first data to include the URI of the image data instead of the image file. Based on this rule, the data access module can determine that the definition of the first data meets the requirements.

[0324] In other embodiments, the data access / access module may further verify the unified management protocol of the first data and the instructions for use of the first data. Specifically, the data access / access module may obtain the unified management protocol standard from the data definition standard model, and verify the unified management protocol of the first data and the instructions for use of the first data based on the specified data definition standard based on the unified management protocol standard.

[0325] The data access / access module verifies the unified management protocol of the first data based on the unified management protocol standard and the usage instructions of the first data based on the specified data definition standard according to the following rules:

[0326] Verify whether the unified management protocol of the first data and the instructions for use of the first data include the preset fields included in the unified management protocol standard and the specified data definition standard, and whether each preset field is filled with content.

[0327] 8. The data access / access module sends the redefined first data to the data security module.

[0328] If the data access / access module determines that the redefined first data meets the requirements, the data access / access module then sends the redefined first data to the data security module. If not, the data access / access module may skip steps 8, 13, and 15 and may notify application A that data sharing has failed. The data access / access module may also prompt application A to redefine the first data according to the specified data definition standard.

[0329] 9. The data security module encrypts the redefined first data to obtain encrypted redefined first data.

[0330] 10. The data security module sends the encrypted redefined first data to the storage management module.

[0331] 11. The storage management module stores the encrypted redefined first data.

[0332] After the data access / access module verifies the redefined first data, or after the data access / access module also verifies the unified management protocol of the first data, the data access / access module can send the redefined first data to the data security module, so that the data security module encrypts the redefined first data to ensure the security of the data stored in the unified data management framework.

[0333] After receiving the redefined first data, the data security module may encrypt the redefined first data to obtain encrypted redefined first data.

[0334] The data security module then sends the encrypted redefined first data to the storage management module.

[0335] The storage management module may store the encrypted redefined first data.

[0336] Optionally, the data access / management module may also store the unified management protocol of the first data and the usage instructions of the first data in the storage management module, or encrypt them through the data security module and store them in the storage management module.

[0337] Optionally, the unified data management framework may not include a data security module. After the data access / access module verifies and passes the redefined first data, the data access / access module may directly send the redefined first data to the storage management module, and the storage management module only needs to store the redefined first data.

[0338] 12. The data access / access module sends the unified management protocol of the first data and the usage instructions of the first data to the data authority management module.

[0339] 13. The data authority management module obtains personalized authority of the first data based on the usage instructions of the first data.

[0340] The data access / access module can also send the unified management agreement of the first data and the usage instructions of the first data to the data authority management module.

[0341] The data permission management module can obtain the personalized permission of the first data based on the usage instructions of the first data, so that it can subsequently verify whether an application that needs to use the first data has the permission to use it based on the personalized permission of the first data.

[0342] Optionally, the personalized permissions of the first data are described in the "peimission" field of the usage description of the first data. The personalized permissions of the first data include but are not limited to public permissions, system permissions, application permissions, etc.

[0343] The data authority management module can obtain the personalized authority of the first data from the usage instructions of the first data.

[0344] 14. The data authority management module may determine the usage authority of the first data based on the personalized authority of the first data, the authority rules of the sharing path of the first data, and the authority rules of the unified data management framework.

[0345] Among them, the personalized permissions of the first data include but are not limited to public permissions, system permissions, application permissions, etc.

[0346] The permission rules of the sharing path of the first data include but are not limited to whether the target application can use the first data.

[0347] The permission rules of the unified data management framework include but are not limited to that all applications or some applications on the device can use the first data.

[0348] The priority of the personalized permission of the first data is greater than the priority of the permission rule of the sharing path of the first data, and the priority of the permission rule of the sharing path of the first data is greater than the priority of the permission rule of the unified data management framework.

[0349] The data authority management module may determine the usage authority of the first data based on the personalized authority of the first data, the authority rules of the sharing path of the first data, and the authority rules of the unified data management framework.

[0350] The permission to use the first data may be that one or more applications on the electronic device 100 can use the first data.

[0351] Specifically, when the usage instructions of the first data define that the personalized permission of the first data is not a public permission, the usage permission of the first data is the personalized permission of the first data specified in the usage instructions of the first data.

[0352] When the instructions for use of the first data define that the personalized permission of the first data is a public permission, then query the permission rules of the sharing path of the first data. It can be seen from the above description that the sharing path between two applications on the same device includes but is not limited to the drag path, clipboard path, cross-application manual path and cross-application automatic path. Among them, the drag path, clipboard path and cross-application manual path all define that the first data can only be used by the target application. For example, if the user shares the first data in application A to application B through the drag path, then the drag path defines that the first data can only be used by application B. The clipboard path and the cross-application manual path are similar to the drag path. The cross-application automatic path defines that the first data is available to all applications or some applications on the device, that is, the permission of the cross-application automatic path is a public permission, and there is no usage permission restriction.

[0353] When the sharing path of the first data is not an automatic cross-application path, the permissions specified by the sharing path of the first data shall prevail, and the usage permissions of the first data shall be the permissions specified by the sharing path of the first data.

[0354] When the sharing path of the first data is an automatic cross-application path, the permission rules of the unified data management framework are queried. The usage permissions of the first data are then the permission rules of the unified data management framework. If the permission rules of the unified data management framework are public permissions with no usage permission restrictions, then the first data is available to all applications on the electronic pen 100. If the permission rules of the unified data management framework are available to some applications, then the first data is available to those applications on the electronic pen 100.

[0355] It should be noted that the personalized permissions of the first data, the permission rules of the sharing path of the first data, and the permission rules of the unified data management framework can be preset or user-defined, and this application does not limit this.

[0356] It should be noted that steps 12 to 14 can be performed before, after or simultaneously with step 8, and this application does not limit this.

[0357] 15. The data access / access module sends the unified management protocol of the first data and the usage instructions of the first data to the data lifecycle management module.

[0358] 16. The data lifecycle management module determines the lifecycle of the first data based on the lifecycle rule of the first data, the lifecycle rule of the sharing path of the first data, and the lifecycle rule of the unified data management framework.

[0359] 17. The data lifecycle management module sends a notification to the storage management module based on the lifecycle of the first data.

[0360] 18. The storage management module continues to store or deletes the encrypted redefined first data.

[0361] The data lifecycle management module may determine, based on the determined lifecycle of the first data, whether the storage management module should continue to store the encrypted and redefined first data or delete the encrypted and redefined first data.

[0362] The lifecycle rules of the first data include, but are not limited to, immediate deletion or permanent storage. The lifecycle rules of the unused first data are permanent storage and the lifecycle rules of the used first data are immediate deletion.

[0363] The lifecycle rules of the sharing path of the first data include but are not limited to regular cleanup or permanent storage.

[0364] The permission rules of the unified data management framework include but are not limited to regular cleanup or permanent storage.

[0365] The priority of the lifecycle rule of the first data is greater than the priority of the lifecycle rule of the sharing path of the first data, and the priority of the lifecycle rule of the sharing path of the first data is greater than the priority of the lifecycle rule of the unified data management framework.

[0366] The data lifecycle management module may determine the lifecycle of the first data based on the lifecycle rule of the first data, the lifecycle rule of the sharing path of the first data, and the lifecycle rule of the unified data management framework.

[0367] Specifically, if the first data has been used, the lifecycle rule of the first data is immediate deletion. The data lifecycle management module may not need to query the lifecycle rules of the sharing path of the first data or the lifecycle rules of the unified data management framework. The data lifecycle management module may send a message to the storage management module, and the storage management module may delete the encrypted and redefined first data.

[0368] When the first data is not used, the lifecycle rule of the first data is to continue to be saved, and the data lifecycle management module can continue to query the lifecycle rule of the sharing path of the first data.

[0369] When the lifecycle rule of the sharing path of the first data is periodic cleaning, the data lifecycle management module can send a message to the storage management module if the storage time of the encrypted and redefined first data reaches a preset time and the first data is not used, and the storage management module can delete the encrypted and redefined first data.

[0370] Optionally, the periodic cleanup rules for different shared paths can be different or the same. For example, the preset timeout for a drag path is 1 hour, and the preset timeout for a clipboard path is 2 hours.

[0371] Optionally, the lifecycle rules for different shared paths can be different or the same. For example, the lifecycle rules for a drag path include, but are not limited to, periodic cleanup or permanent preservation, while the lifecycle rules for a clipboard path include, but are not limited to, overwrite on write, periodic cleanup, or permanent preservation, or one or more of these.

[0372] When the lifecycle rule of the sharing path of the first data is permanent storage, the data lifecycle management module may continue to query the lifecycle rule of the unified data management framework.

[0373] When the unified data management framework's lifecycle rule is permanent preservation, the storage management module may continue to store the encrypted and redefined first data. When the unified data management framework's lifecycle rule is periodic cleanup, the data lifecycle management module may send a message to the storage management module if the storage period of the encrypted and redefined first data reaches a preset period and the first data is unused, and the storage management module may delete the encrypted and redefined first data.

[0374] It should be noted that the lifecycle rules of the first data, the lifecycle rules of the sharing path of the first data, and the lifecycle rules of the unified data management framework can be preset or user-defined, and this application does not limit this.

[0375] It should be noted that steps 15 to 18 can be performed before, after or simultaneously with step 8, and this application does not limit this.

[0376] The data lifecycle management module manages the data stored in the storage management module. On the one hand, it can regularly clean up used data to free up memory. On the other hand, it can promptly clean up data that has not been used for a long time to ensure data security and prevent data leakage.

[0377] The steps in FIG. 7 are only used to illustrate the specific implementation of how the unified data management framework stores the first data shared by application A, but should not limit the execution steps of the steps.

[0378] FIG8 shows a specific implementation diagram of how application B on the electronic device 100 reads the first data shared by application A from the unified data management framework.

[0379] For example, after application A on electronic device 100 stores the first data to be shared in the storage management module of the unified data management framework, application B on electronic device 100 can obtain the first data from the storage management module of the unified data management framework, thereby realizing data sharing between two applications on the same device.

[0380] The method steps for application B to read the first data shared by application A from the unified data management framework are as follows (step 1 to step 11):

[0381] 1. Application B sends a read notification to the data rights management module.

[0382] The read notification is used to read the first data shared by application A from the unified data management framework.

[0383] Optionally, the read notification may carry an application identifier of application B, so that the data authority management module can check whether application B has the authority to access the first data shared by application A.

[0384] 2. The data authority management module checks whether application B has the authority to use the first data.

[0385] If application B has the authority to use the first data, step 4 is executed.

[0386] If application B does not have permission to use the first data, the process ends.

[0387] As can be seen from step 14 in the embodiment of FIG7 , the data permission management module can determine the usage permission of the first data based on the personalized permission of the first data, the permission rules of the sharing path of the first data, and the permission rules of the unified data management framework. For details, please refer to the description of step 14 in the embodiment of FIG7 .

[0388] First, the data rights management module can determine whether application B is capable of using the first data based on the usage instructions for the first data. If application B is capable of using the first data, the module can then determine whether application B is authorized to use the first data based on the usage permissions for the first data. If application B is authorized to use the first data, the data rights management module sends a notification to the data access / access module, instructing the module to redefine the first data and send it to application B.

[0389] The data authority management module determines whether application B is capable of using the first data, specifically including:

[0390] The data authority management module obtains the type of the first data from the usage instructions of the first data. The type of the first data includes but is not limited to a basic class, a system-defined class, and an application-defined class.

[0391] The data authority management module then obtains the application source or operating system source of the first data based on the type of the first data.

[0392] In the case where the data permission management module is a basic class, it indicates that the first data is available to any operating system, any application, and any device. In this case, the data permission management module does not need to determine the application source or operating system source of the first data, and can directly determine whether application B has permission to use the first data based on the usage permission of the first data.

[0393] In the case that the data authority management module is a system-defined class, the data authority management module then obtains the operating system source of the first data, and only applications on devices with the same operating system as the operating system source can use the first data. For example, the operating system source is If the device that installs application B also has If the device that installed the application B is not also installed with the first data, the data authority management module determines whether the application B has the right to use the first data. The operating system determines that application B is unable to use the first data. The data permission management module no longer needs to determine whether application B has permission to use the first data based on the permission to use the first data, and determines that application B cannot use the first data.

[0394] In the case where the data permission management module is an application-defined class, the data permission management module then obtains the application source of the first data, and only applications with the same application source can use the first data. In the case where application B has the same application source or application B and the application source are family applications, application B has the ability to use the first data, and the data permission management module then determines whether application B has the permission to use the first data based on the usage permissions of the first data. If application B and the application source are different or application B and the application source are not family applications, application B does not have the ability to use the first data. The data permission management module no longer needs to determine whether application B has the permission to use the first data based on the usage permissions of the first data, and determines that application B cannot use the first data.

[0395] If application B is able to use the first data, then based on the permission to use the first data, it is determined whether application B has permission to use the first data. The permission to use the first data includes one or more applications that can use it. If the one or more applications include application B, it means that application B has permission to use the first data.

[0396] For example, when the usage permission of the first data is public permission, application B has the permission to use the first data.

[0397] When the permission to use the first data is a channel permission (i.e., the target application sent through the sharing channel has permission to use the first data), and application B is the target application, then application B has permission to use the first data. When application B is not the target application, then application B does not have permission to use the first data.

[0398] 3. The data rights management module sends a notification to the data access / access module.

[0399] The notification is used to instruct the data access / access module to select a corresponding sharing path to send the first data to application B.

[0400] Optionally, the notification may include an identifier of application B, so that the data access / access module may send the redefined first data based on the identifier of application B to application B through the corresponding sharing path after determining the sharing path.

[0401] 4. The data access / access module obtains the redefined first data from the storage management module.

[0402] Optionally, the data access / management module may obtain the redefined first data from the storage management module after receiving the first notification sent by the data authority management module.

[0403] 5. The data access / access module obtains the sharing path of the first data from the unified management protocol of the first data.

[0404] 6. The data access / access module selects a corresponding sharing path based on the sharing path of the first data.

[0405] Optionally, the data access / insertion module may obtain the unified management protocol of the first data from the storage management module.

[0406] Optionally, after receiving the first notification sent by the data authority management module, the data access / access module may obtain the unified management protocol of the first data from the storage management module.

[0407] Optionally, the unified management protocol of the first data includes an "intension" field, and the "intension" field is used to fill in the name of the sharing path. Therefore, the data access / access module obtains the sharing path of the first data from the unified management protocol of the first data.

[0408] Specifically, when the name of the sharing path filled in the "intension" field is automatic1, the sharing path of the first data may be a cross-application automatic path.

[0409] When the name of the sharing path filled in the “intension” field is clipboard, the sharing path of the first data may be a clipboard path.

[0410] When the name of the sharing path filled in the “intension” field is drag, the sharing path of the first data may be a drag path.

[0411] When the name of the sharing path filled in the “intension” field is manual1, the sharing path of the first data may be a cross-application manual path.

[0412] After the data access / access module obtains the sharing path of the first data from the unified management protocol of the first data, the data access / access module may select a corresponding sharing path based on the sharing path of the first data and send the first data to the target application through the corresponding sharing path.

[0413] Optionally, step 4 may also be performed before, after, or simultaneously with step 5 and step 6, which is not limited in this application. Step 4 only needs to be performed before step 7.

[0414] Exemplarily, the data access / access module obtains from the unified management protocol of the first data that the sharing path of the first data may be a drag path. Then, the data access / access module may select the drag path.

[0415] 7. The data access module sends the redefined first data to the drag path in the drag channel.

[0416] Exemplarily, after the data access / access module selects the drag path, the data access / access module may send the redefined first data to the drag path in the drag channel.

[0417] Optionally, the data access / insertion module may further send the identifier of application B to the drag channel, so that the drag channel may send the redefined first data to application B based on the identifier of application B.

[0418] 8. The drag path will redefine the first data and send it to application B.

[0419] After receiving the identifier of application B and the redefined first data sent by the data access / access module, the drag path may send the redefined first data to application B based on the identifier of application B.

[0420] 9. Application B obtains the specified data definition standard from the data definition standard model.

[0421] 10. Application B parses the redefined first data based on the specified data definition standard to obtain the first data.

[0422] 11. Application B uses the first data.

[0423] After obtaining the redefined first data sent by the drag path, application B may obtain the specified data definition standard from the data definition standard model.

[0424] In other words, whether using a drag-and-drop path, a manual cross-app path, or an automatic cross-app path, application B only needs to obtain a data definition standard, namely a specified data definition standard, and then parse the redefined first data based on the specified data definition standard to obtain the first data. Application B can then use the first data, thus enabling data sharing between two applications on the same device.

[0425] Application B can use the first data, specifically including: when the first data is text data, application B on the electronic device 100 can directly obtain the text content of the first data from the first data and use the text content of the first data.

[0426] When the first data is non-text data (or called file data), when application B on the electronic device 100 needs to use the first data, application B on the electronic device 100 can obtain the URI of the first data from the first data, and obtain the file data of the first data based on the URI of the first data, and use the file data of the first data.

[0427] In the data sharing method between two applications on the same device provided by the embodiment of Figure 11, before data sharing, different applications need to define the shared data according to this standard. After receiving the shared data, different applications also need to parse the shared data based on this standard. In other words, the data definition standard is unified for different applications and different sharing paths, achieving a unified format for shared data.

[0428] 12. The data lifecycle management module determines that the redefined first data needs to be deleted.

[0429] 13. The data lifecycle management module sends a notification to the storage management module.

[0430] 14. The storage management module deletes the stored redefined first data.

[0431] Optionally, after application B uses the first data, the data lifecycle management module may determine to delete the used redefined first data in a timely manner to avoid data leakage.

[0432] Specifically, after application B uses the first data, the data lifecycle management module may send a notification to the storage management module. Upon receiving the notification, the storage management module may, in response to the notification, delete the stored redefined first data. This allows the storage management module to promptly delete the used redefined first data, thereby preventing data leakage and promptly freeing up the memory occupied by the used redefined first data.

[0433] It should be noted that the steps in FIG. 8 are only used to illustrate the specific implementation of how application B reads the first data from the unified data management framework, but should not limit the execution steps.

[0434] Data sharing between two apps on different devices (Figures 9 and 10)

[0435] For example, the different devices may be electronic device 100 and electronic device 200, and the two applications may be application A on electronic device 100 and application B on electronic device 200, respectively. In some embodiments, application A on electronic device 100 may receive a user operation to share the first data in application A with application B on electronic device 200. In other embodiments, application A on electronic device 100 may also automatically share the first data in application A with application B on electronic device 200.

[0436] FIG9 shows a specific implementation diagram of how a unified data management framework on an electronic device 200 stores first data shared by an application A on an electronic device 100 .

[0437] The steps of the method for storing the first data shared by application A in the unified data management framework on the electronic device 200 are as follows (step 1 to step 20):

[0438] The electronic device 100 sends the first data in the application A to the electronic device 200 (step 1 to step 8).

[0439] Among them, the description of steps 1 to 6 can refer to the description of steps 1 to 6 in the embodiment of Figure 7, and this application will not repeat them here.

[0440] Optionally, the electronic device 100 may not perform steps 5 and 6, and steps 5 and 6 may be performed by the electronic device 200, which is not limited in this application.

[0441] 7. The unified data management framework on the electronic device 100 sends the redefined first data, the unified management protocol of the first data, and the usage instructions of the first data to the communication module on the electronic device 100.

[0442] 8. The communication module on the electronic device 100 is used to send the redefined first data, the unified management protocol of the first data, and the usage instructions of the first data to the communication module on the electronic device 200.

[0443] In this way, data sharing across devices can be achieved.

[0444] 9. The communication module on the electronic device 200 sends the redefined first data, the unified management protocol of the first data, and the usage instructions of the first data to the data access / access module in the unified data management framework on the electronic device 200.

[0445] 10. The data access / access module on the electronic device 200 sends the redefined first data to the data security module on the electronic device 200.

[0446] 11. The data security module on the electronic device 200 encrypts the redefined first data to obtain encrypted redefined first data.

[0447] 12. The data security module on the electronic device 200 sends the encrypted redefined first data to the storage management module on the electronic device 200.

[0448] 13. The storage management module on the electronic device 200 stores the encrypted redefined first data.

[0449] After receiving the redefined first data, the data security module on the electronic device 200 may encrypt the redefined first data to obtain encrypted redefined first data.

[0450] The data security module on the electronic device 200 then sends the encrypted redefined first data to the storage management module.

[0451] The storage management module on the electronic device 200 may store the encrypted redefined first data.

[0452] Optionally, the data access / access module on the electronic device 200 may also store the unified management protocol of the first data and the instructions for use of the first data in the storage management module on the electronic device 200, or encrypt them through the data security module on the electronic device 200 and store them in the storage management module on the electronic device 200.

[0453] Optionally, the unified data management framework on the electronic device 200 may not include the data security module on the electronic device 200. After the data access / access module on the electronic device 200 verifies and passes the redefined first data, the data access / access module on the electronic device 200 may directly send the redefined first data to the storage management module on the electronic device 200. The storage management module on the electronic device 200 only needs to store the redefined first data.

[0454] 14. The data access / access module on the electronic device 200 sends the unified management protocol of the first data and the usage instructions of the first data to the data authority management module on the electronic device 200.

[0455] 15. The data authority management module on the electronic device 200 obtains personalized authority for the first data based on the usage instructions of the first data.

[0456] The data access / access module on the electronic device 200 may also send the usage instructions of the first data to the data authority management module on the electronic device 200.

[0457] The data permission management module on the electronic device 200 can obtain the personalized permission of the first data based on the usage instructions of the first data, so that it can subsequently verify whether an application that needs to use the first data has the permission to use it based on the personalized permission of the first data.

[0458] Optionally, the personalized permissions of the first data are described in the "peimission" field of the usage description of the first data. The personalized permissions of the first data include but are not limited to public permissions, system permissions, application permissions, etc.

[0459] The data authority management module on the electronic device 200 can obtain the personalized authority of the first data from the usage instructions of the first data.

[0460] 16. The data permission management module on the electronic device 200 can determine the usage permission of the first data based on the personalized permission of the first data, the permission rules of the sharing path of the first data, and the permission rules of the unified data management framework.

[0461] Step 16 is similar to step 14 in the embodiment of FIG. 7 , except that the permission to use the first data obtained in step 14 in the embodiment of FIG. 7 may be that one or more applications on the electronic device 100 can use the first data.

[0462] The usage permission of the first data obtained in step 16 in the embodiment of FIG. 9 may be that one or more applications on the electronic device 200 can use the first data.

[0463] For a detailed introduction to step 16, please refer to the introduction to step 14 in the embodiment of Figure 7, and this application will not go into details here.

[0464] 17. The data access / access module on the electronic device 200 sends the unified management protocol of the first data and the usage instructions of the first data to the data lifecycle management module on the electronic device 200.

[0465] 18. The data lifecycle management module on the electronic device 200 determines the lifecycle of the first data based on the lifecycle rule of the first data, the lifecycle rule of the sharing path of the first data, and the lifecycle rule of the unified data management framework on the electronic device 200.

[0466] 19. The data lifecycle management module on the electronic device 200 sends a notification to the storage management module on the electronic device 200 based on the lifecycle of the first data.

[0467] 20. The storage management module on the electronic device 200 continues to store or deletes the encrypted redefined first data.

[0468] The data lifecycle management module on the electronic device 200 can determine whether the storage management module continues to store the encrypted redefined first data or deletes the encrypted redefined first data based on the determined lifecycle of the first data.

[0469] The detailed introduction of steps 16 to 20 is similar to the implementation of steps 15 to 18 in the embodiment of FIG7 . Please refer to the introduction of steps 15 to 18 in the embodiment of FIG7 , and this application will not repeat them here.

[0470] FIG10 shows a specific implementation diagram of how application B on electronic device 200 reads first data shared by application A on electronic device 100 from the unified data management framework on electronic device 200 .

[0471] For example, after application A on electronic device 100 stores the first data to be shared in the storage management module of the unified data management framework on electronic device 200, application B on electronic device 200 can obtain the first data from the storage management module of the unified data management framework on electronic device 200, thereby realizing data sharing between two applications on different devices.

[0472] The method steps for application B on electronic device 200 to read the first data shared by application A on electronic device 100 from the unified data management framework on electronic device 200 are as follows (step 1 to step 14):

[0473] 1. Application B on the electronic device 200 sends a read notification to the data authority management module on the electronic device 200.

[0474] 2. The data authority management module on the electronic device 200 checks whether application B has the authority to use the first data.

[0475] 3. The data rights management module on the electronic device 200 sends a notification to the data access / access module on the electronic device 200.

[0476] 4. The data access / access module on the electronic device 200 obtains the redefined first data from the storage management module on the electronic device 200.

[0477] 5. The data access / access module on the electronic device 200 obtains the sharing path of the first data from the unified management protocol of the first data.

[0478] 6. The data access / access module on the electronic device 200 selects a corresponding sharing path based on the sharing path of the first data.

[0479] For the introduction of steps 1 to 6 in the embodiment of Figure 10, you can refer to the introduction of steps 1 to 6 in the embodiment of Figure 8. The difference is that, in the embodiment of Figure 10, steps 1 to 6 are about the specific implementation of how application B on electronic device 200 reads the first data from the unified data management framework on electronic device 200, while in the embodiment of Figure 8, steps 1 to 6 are about the specific implementation of how application B on electronic device 100 reads the first data from the unified data management framework on electronic device 100. The principles are similar and will not be repeated in this application.

[0480] 7. The data access module on the electronic device 200 redefines the first data and sends it to the drag path in the drag channel on the electronic device 200.

[0481] Exemplarily, after the data access / access module on the electronic device 200 selects the drag path on the electronic device 200 , the data access / access module on the electronic device 200 may send the redefined first data to the drag path in the drag channel on the electronic device 200 .

[0482] Optionally, the data access / access module on the electronic device 200 can also send the identifier of application B to the drag channel on the electronic device 200, so that the drag channel on the electronic device 200 can send the redefined first data to application B based on the identifier of application B.

[0483] 8. The dragging path on the electronic device 200 will redefine the first data and send it to application B.

[0484] After receiving the identification of application B and the redefined first data sent by the data access / access module on the electronic device 200, the drag path on the electronic device 200 can send the redefined first data to application B based on the identification of application B.

[0485] 9. Application B on the electronic device 200 obtains the specified data definition standard from the data definition standard model on the electronic device 200.

[0486] 10. Application B on the electronic device 200 parses the redefined first data based on a specified data definition standard to obtain the first data.

[0487] 11. Application B on electronic device 200 uses the first data.

[0488] After the application B on the electronic device 200 obtains the redefined first data sent by the drag path on the electronic device 200 , the application B on the electronic device 200 may obtain the specified data definition standard from the data definition standard model.

[0489] In other words, regardless of whether the path is a drag path, a clipboard path, a cross-device manual path, or a cross-device automatic path, application B on electronic device 200 only needs to obtain a data definition standard, namely a specified data definition standard, and parse the redefined first data based on the specified data definition standard to obtain the first data. Application B on electronic device 200 can use the first data, thus enabling data sharing between two applications on different devices.

[0490] Application B on the electronic device 200 may use the first data, specifically including:

[0491] In the case that the first data is text data, the application B on the electronic device 200 can directly obtain the text content of the first data from the first data and use the text content of the first data.

[0492] In the case where the first data is non-text data (or called file data), when application B on the electronic device 200 needs to use the first data, application B on the electronic device 200 can obtain the URI of the first data from the first data, and obtain the file data of the first data based on the URI of the first data. Specifically, application B on the electronic device 200 can send the URI of the first data to the communication module on the electronic device 100 through the communication module. After receiving the acquisition notification, the communication module on the electronic device 100 can obtain the file data of the first data based on the URI of the first data, and the communication module on the electronic device 100 then sends the file data of the first data to the communication module on the electronic device 200. The communication module on the electronic device 200 then sends the file data of the first data to application B on the electronic device 200, and application B on the electronic device 200 can use the file data of the first data.

[0493] 12. The data lifecycle management module on the electronic device 200 determines that the redefined first data needs to be deleted.

[0494] 13. The data lifecycle management module on the electronic device 200 sends a notification to the storage management module on the electronic device 200.

[0495] 14. The storage management module on the electronic device 200 deletes the stored redefined first data.

[0496] Optionally, after the application B on the electronic device 200 uses the first data, the data lifecycle management module on the electronic device 200 may determine to delete the used redefined first data in a timely manner to avoid data leakage.

[0497] Specifically, after application B on electronic device 200 uses the first data, the data lifecycle management module on electronic device 200 may send a notification to the storage management module on electronic device 200. After receiving the notification, the storage management module on electronic device 200 may delete the stored redefined first data in response to the notification. In this way, the storage management module on electronic device 200 can promptly delete the used redefined first data, which, on the one hand, can prevent data leakage, and on the other hand, can promptly release the memory occupied by the used redefined first data.

[0498] It should be noted that the steps in FIG. 10 are only used to illustrate the specific implementation of how the application B on the electronic device 200 reads the first data from the unified data management framework, but should not limit the execution steps.

[0499] FIG11 is a schematic diagram of a method for how application A on an electronic device 100 shares data with application B on the electronic device 100 , provided in an embodiment of the present application.

[0500] S1101: Application A obtains first data, which is data shared with application B.

[0501] In some embodiments, application A can receive a user operation to share the first data in application A to application B. For example, the first data in application A can be shared to application B via a drag path between the same devices, a clipboard path between the same devices, or a cross-application path between the same devices as shown in Figures 1A-1J.

[0502] In other embodiments, application A may also automatically share the first data in application A with application B. For example, the first data in application A may be shared with application B through an automatic cross-application path.

[0503] The first data in application A may also be shared to application B through other sharing paths. This application does not limit this.

[0504] S1102. Application A obtains the specified data definition standard and the unified management protocol standard from the unified data management framework.

[0505] Optionally, S1102 may also be executed before S1101, which is not limited in this application.

[0506] For an introduction to the specified data definition standards and the unified management protocol standards, please refer to the description in Table 1, which will not be repeated in this application.

[0507] It should be noted that different sharing paths on the electronic device 100 need to adapt to this specified data definition standard and unified management protocol standard. When applications on the electronic device 100 share data through different sharing paths, they only need to define the data according to this standard. When other applications on the electronic device 100 use this shared data, they only need to redefine the data according to this standard to parse and obtain the shared data. This achieves a unified definition standard for shared data across different paths.

[0508] S1103 . Application A defines the first data based on a specified data definition standard to obtain redefined first data.

[0509] This application provides a set of data definition standards (specified data definition standards). Before applications share data, different applications can define the shared data based on the specified data definition standards. The recipient of the shared data can also parse the shared data based on the specified data definition standards. This reduces the processing flow of data sending and receiving.

[0510] In other embodiments, the shared data is not limited to being defined according to the specified data definition standard. Applications can also be instructed to define the data within the application according to the specified data definition standard when generating application data. In this way, after the application determines the shared data, the shared data has already been defined according to the specified data definition standard, and the application does not need to define it again.

[0511] Application A defines the first data based on the specified data definition standard. Application A may define the attributes of the first data based on the specified data definition standard, including but not limited to the type definition of the first data, the size definition of the first data, the creation time definition of the first data, the content definition of the first data, etc.

[0512] For example, when the first data is non-text data (or file data), such as an image, redefining the first data may include a type definition of the first data and a content definition of the first data. The type definition of the first data may be "image," and the content definition of the first data may be "URI of the first data."

[0513] For another example, when the first data is text data, redefining the first data may include defining the type of the first data and defining the content of the first data. The type definition of the first data may be "plain-text" and the content definition of the first data may be "department regular meeting at 4:00 PM."

[0514] S1104. Application A generates a unified management protocol for the first data based on the unified management protocol standard and generates instructions for use of the first data based on the specified data definition standard.

[0515] Application A can generate a unified management protocol for the first data based on the unified management protocol standard and generate usage instructions for the first data based on the specified data definition standard. The unified management protocol for the first data describes the sharing path for the first data, and the usage instructions for the first data describe the personalized rights of the first data.

[0516] For example, if the sharing path of the first data is a drag path, the personalized permission of the first data is to install The application on the device of the operating system can use the first data. Then the unified management protocol of the first data can be "udmf: / / drag / library application / 123 / 123456". The usage instructions of the first data can be

[0517] It should be noted that S1104 can also be executed before S1103, and S1104 can also be executed simultaneously with S1103, and this application does not limit this.

[0518] S1105 . Application A sends the redefined first data, the unified management protocol of the first data, and the usage instructions of the first data to the unified data management framework.

[0519] After obtaining the redefinition of the first data, the unified management agreement for the first data, and the instructions for using the first data, application A sends the redefinition of the first data, the unified management agreement for the first data, and the instructions for using the first data to the unified data management framework. This allows the unified data management framework to verify the redefinition of the first data, or the redefinition of the first data, the unified management agreement for the first data, and the instructions for using the first data.

[0520] S1106. The unified data management framework verifies the redefined first data based on the specified data definition standard, and determines whether the definition of the redefined first data meets the requirements.

[0521] If the redefined first data does not meet the requirement, execute S1107.

[0522] If the redefined first data meets the requirements, execute S1108.

[0523] The unified data management framework verifies the redefined first data, primarily verifying that it complies with the unified data management framework. Only data that passes verification can be shared with other applications through the unified data management framework to prevent situations where application A does not define the first data according to the specified data definition standard.

[0524] The unified data management framework verifies the redefined first data based on the specified data definition standard as follows:

[0525] Redefine whether the first data is defined in accordance with the data attribute definition and data content definition specified in the specified data definition standard. For example, when the first data is image data, redefine the type definition of the image data included in the first data to be "image" instead of "picture". Redefine the content definition of the image data included in the first data to be the URI of the image data instead of including the image file. Redefine the content definition of the text data included in the first data to be the plain text content of the text data instead of including other content. According to this rule, the unified data management framework can determine that the definition of the first data meets the requirements.

[0526] Optionally, the unified data management framework can also verify the unified management protocol of the first data based on the unified management protocol standard and the usage instructions of the first data based on the specified data definition standard, and determine whether the unified management protocol of the first data and the usage instructions of the first data meet the requirements.

[0527] The unified data management framework verifies the unified management protocol of the first data based on the unified management protocol standard and verifies the usage instructions of the first data based on the specified data definition standard according to the following rules:

[0528] The unified management agreement of the first data and the instructions for use of the first data include the preset fields included in the unified management protocol standard and the specified data definition standard. The content in each preset field is also verified.

[0529] The listing verification rules may also be in other forms, which are not limited in this application.

[0530] S1107. The process ends.

[0531] When it is determined that the redefined first data meets the requirements, it means that the first data cannot be shared further, and the process ends.

[0532] Optionally, the unified data management framework may also send a notification to application A, and application A may be prompted that the requirements of the unified data management framework are not met and sharing cannot be performed.

[0533] S1108. The unified data management framework stores the redefined first data, the unified management of the first data, and the instructions for using the first data.

[0534] Optionally, in order to ensure the security of the redefined first data, the unified management of the first data, and the usage instructions of the first data, the redefined first data, the unified management of the first data, and the usage instructions of the first data may be stored in encrypted form.

[0535] Optionally, the unified data management framework can also manage the stored redefined first data, the unified management of the first data, and the instructions for use of the first data. For example, it can continue to store the redefined first data, the unified management of the first data, and the instructions for use of the first data, or delete the redefined first data, the unified management of the first data, and the instructions for use of the first data. For details, please refer to the description of step 18 in the embodiment of Figure 7, and this application will not repeat them here.

[0536] S1109. The unified data management framework determines the usage permission of the first data based on the personalized permission of the first data, the permission rule of the sharing path of the first data, and the permission rule of the unified data management framework.

[0537] The permission to use the first data may be that one or more applications on the electronic device 100 can use the first data.

[0538] The personalized permissions of the first data and the permission rules of the sharing path of the first data may be determined by the unified data management framework based on the unified management protocol of the first data and the usage instructions of the first data.

[0539] Optionally, the "peimission" field in the usage instructions of the first data describes the personalized permissions of the first data. The personalized permissions of the first data include, but are not limited to, public permissions, system permissions, and application permissions. The unified data management framework can obtain the personalized permissions of the first data from the unified management agreement of the first data.

[0540] Optionally, the "intension" field in the unified management protocol for the first data describes the sharing path of the first data. The unified data management framework can obtain permission rules for different sharing paths, then obtain the sharing path of the first data from the "intension" field, and determine the permission rules for the sharing path of the first data from the permission rules for the multiple different sharing paths.

[0541] The permission rules of the unified data management framework may be preset by the unified data management framework, and the unified data management framework may obtain the permission rules of the unified data management framework.

[0542] The unified data management framework may determine the usage permission of the first data based on the personalized permission of the first data, the permission rules of the sharing path of the first data, and the permission rules of the unified data management framework.

[0543] Among them, the personalized permissions of the first data include but are not limited to public permissions, system permissions, application permissions, etc.

[0544] The permission rules of the sharing path of the first data include but are not limited to whether the target application can use the first data.

[0545] The permission rules of the unified data management framework include but are not limited to that all applications or some applications on the device can use the first data.

[0546] The priority of the personalized permission of the first data is greater than the priority of the permission rule of the sharing path of the first data, and the priority of the permission rule of the sharing path of the first data is greater than the priority of the permission rule of the unified data management framework.

[0547] Specifically, when the unified management agreement of the first data defines that the personalized permission of the first data is not a public permission, the usage permission of the first data is the personalized permission of the first data specified in the unified management agreement of the first data.

[0548] When the unified management agreement of the first data defines that the personalized permission of the first data is a public permission, then query the permission rules of the sharing path of the first data. It can be seen from the above description that the sharing path between two applications on the same device includes but is not limited to the drag path, clipboard path, cross-application manual path and cross-application automatic path. Among them, the drag path, clipboard path and cross-application manual path all define that the first data can only be used by the target application. For example, if the user shares the first data in application A to application B through the drag path, then the drag path defines that the first data can only be used by application B. The clipboard path and the cross-application manual path are similar to the drag path. The cross-application automatic path defines that the first data is available to all applications or some applications on the device, that is, the permission of the cross-application automatic path is a public permission, and there is no usage permission restriction.

[0549] When the sharing path of the first data is not an automatic cross-application path, the permissions specified by the sharing path of the first data shall prevail, and the usage permissions of the first data shall be the permissions specified by the sharing path of the first data.

[0550] When the sharing path of the first data is an automatic cross-application path, the permission rules of the unified data management framework are queried. The usage permissions of the first data are then the permission rules of the unified data management framework. If the permission rules of the unified data management framework are public permissions with no usage permission restrictions, then the first data is available to all applications on the electronic pen 100. If the permission rules of the unified data management framework are available to some applications, then the first data is available to those applications on the electronic pen 100.

[0551] It should be noted that the personalized permissions of the first data, the permission rules of the sharing path of the first data, and the permission rules of the unified data management framework can be preset or user-defined. The above-mentioned personalized permissions of the first data, the permission rules of the sharing path of the first data, and the permission rules of the unified data management framework are only used to explain this application, and this application does not limit them.

[0552] Optionally, S1109 may be executed before S1109, after S1109, or simultaneously with S1109, which is not limited in this application.

[0553] S1110 . Application B on the electronic device 100 sends a read notification to the unified data management framework.

[0554] When an application (eg, application B) on the electronic device 100 needs to read data shared by application A on the electronic device 100 from the unified data management framework, application B may send a read notification to the unified data management framework.

[0555] In some embodiments, the read notification may carry an identifier of application B. In other embodiments, the identifier of application B may also be sent to the unified data management framework separately from the read notification.

[0556] S1111. The unified data management framework determines whether application B has permission to use the first data based on the permission to use the first data.

[0557] As can be seen from S1109 , the unified data management framework has determined the usage permission of the first data based on the personalized permission of the first data, the permission rules of the sharing path of the first data, and the permission rules of the unified data management framework.

[0558] The permission to use the first data may be that one or more applications on the electronic device 100 can use the first data.

[0559] The unified data management framework may first determine whether application B is capable of using the first data based on the usage instructions of the first data. If application B is capable of using the first data, the unified data management framework may then determine whether one or more applications that can use the first data include an identifier of application B.

[0560] If one or more applications that can use the first data do not include the identifier of application B, it means that application B has the permission to use the first data, and S1112 is executed.

[0561] If the one or more applications that can use the first data include the identifier of application B, it means that application B has the permission to use the first data, and S1113 is executed.

[0562] S1112, the process ends.

[0563] If one or more applications that can use the first data do not include the identifier of application B, it means that application B has the permission to use the first data, and the process ends.

[0564] Optionally, the unified data management framework may also send a notification to application B, and application B may prompt that the first data cannot be used.

[0565] S1113. The unified data management framework obtains a sharing path of the first data from the unified management protocol of the first data.

[0566] Optionally, the unified management protocol of the first data includes an "intension" field, and the "intension" field is used to fill in the name of the sharing path. Therefore, the unified data management framework can obtain the sharing path of the first data from the unified management protocol of the first data.

[0567] Specifically, when the name of the sharing path filled in the "intension" field is automatic1, the sharing path of the first data may be a cross-application automatic path.

[0568] When the name of the sharing path filled in the “intension” field is clipboard, the sharing path of the first data may be a clipboard path.

[0569] When the name of the sharing path filled in the “intension” field is drag, the sharing path of the first data may be a drag path.

[0570] When the name of the sharing path filled in the “intension” field is manual1, the sharing path of the first data may be a cross-application manual path.

[0571] Exemplarily, the sharing path of the first data obtained by the unified data management framework from the unified management protocol of the first data may be a drag path.

[0572] S1114. The unified data management framework sends the redefined first data to the drag path.

[0573] S1115 , the drag path redefines the first data and sends it to application B.

[0574] S1116. Application B obtains the specified data definition standard from the unified data management framework.

[0575] Optionally, S1116 is not limited to being executed after S1115, but can also be executed in any step before S1117.

[0576] S1117 . Application B parses the redefined first data based on the specified data definition standard to obtain the first data.

[0577] S1118. Application B uses the first data.

[0578] Optionally, the unified data management framework can also manage the stored redefined first data. For example, after the unified data management framework sends the redefined first data to application B or application B uses the first data, the unified data management framework can determine that the redefined first data is deleted in a timely manner. In this way, the unified data management framework can promptly delete the used redefined first data, which can, on the one hand, prevent data leakage, and, on the other hand, promptly free up the memory occupied by the used redefined first data.

[0579] After the unified data management framework determines the sharing path (eg, the dragging path), the unified data management framework may send the redefined first data to application B via the dragging path.

[0580] Application B may obtain the specified data definition standard from the unified data management framework, and parse the redefined first data based on the specified data definition standard to obtain the first data.

[0581] Thereafter, application B may use the first data.

[0582] Application B can use the first data, specifically including: when the first data is non-file data, application B on electronic device 100 can directly obtain the text content of the first data from the first data and use the text content of the first data.

[0583] When the first data is file data, when application B on the electronic device 100 needs to use the first data, application B on the electronic device 100 can obtain the URI of the first data from the first data, and obtain the file data of the first data based on the URI of the first data, and use the file data of the first data.

[0584] In the data sharing method between two applications on the same device provided by the embodiment of Figure 11, before data sharing, different applications need to define the shared data according to this standard. After receiving the shared data, different applications also need to parse the shared data based on this standard. In other words, the data definition standard is unified for different applications and different sharing paths, achieving a unified format for shared data.

[0585] FIG12 is a schematic diagram of a method for how application A on an electronic device 100 shares data with application B on an electronic device 200, provided in an embodiment of the present application.

[0586] S1201 : Application A on electronic device 100 obtains first data, which is data shared with application B on electronic device 200 .

[0587] In some embodiments, application A can receive a user operation to share the first data in application A to application B. For example, the first data in application A can be shared to application B via a drag path between different devices, a clipboard path between different devices, or a cross-device path between different devices as shown in Figures 2A-2G.

[0588] In other embodiments, application A may also automatically share the first data in application A with application B. For example, the first data in application A may be shared with application B through an automatic cross-device path.

[0589] The first data in application A on electronic device 100 may also be shared to application B on electronic device 200 through other sharing paths. This application does not limit this.

[0590] S1202-S1207: After application A on the electronic device 100 obtains the first data, application A on the electronic device 100 can generate redefined first data based on the specified data definition standard, or can generate a unified management protocol for the first data based on the unified management protocol standard and instructions for use of the first data based on the specified data definition standard. Application A on the electronic device 100 then sends the redefined first data, the unified management protocol for the first data, and the instructions for use of the first data to the unified data management framework on the electronic device 100. The unified data management framework on the electronic device 100 verifies whether the redefined first data meets the requirements.

[0591] For the introduction of S1202-S1207 in the embodiment of FIG12 , reference may be made to the description of S1102-S1107 in the embodiment of FIG11 , and this application will not go into details here.

[0592] S1208 . The unified data management framework on the electronic device 100 sends the redefined first data, the unified management protocol of the first data, and the usage instructions of the first data to the communication module on the electronic device 100 .

[0593] S1209 , the communication module on the electronic device 100 sends the redefined first data, the unified management protocol of the first data, and the usage instructions of the first data to the communication module on the electronic device 200 .

[0594] S1210 : The communication module on the electronic device 200 sends the redefined first data, the unified management protocol of the first data, and the usage instructions of the first data to the unified data management framework on the electronic device 200 .

[0595] After verifying that the redefined first data meets the requirements, the unified data management framework on the electronic device 100 can send the redefined first data, the unified management protocol of the first data and the instructions for using the first data to the communication module on the electronic device 200 through the communication module on the electronic device 100.

[0596] The communication module on the electronic device 200 then sends the redefined first data, the unified management protocol for the first data, and the instructions for using the first data to the unified data management framework on the electronic device 200. The unified data management framework on the electronic device 200 can save the redefined first data, the unified management protocol for the first data, and the instructions for using the first data, so that the application on the electronic device 200 can obtain and use the first data from the unified data management framework on the electronic device 200.

[0597] Optionally, S1206-S1207 may also be executed by a unified data management framework on the electronic device 200, and this application does not limit this.

[0598] S1211-S1220: After the unified data management framework on the electronic device 200 obtains the redefined first data that meets the requirements, the unified management protocol for the first data, and the instructions for using the first data, one or more applications on the electronic device 200 can obtain the first data shared by application A on the electronic device 100 from the unified data management framework on the electronic device 200. The unified data management framework on the electronic device 200 can verify whether the one or more applications on the electronic device 200 have the ability and permission to access the first data shared by application A on the electronic device 100. If they have the ability and permission, the unified data management framework on the electronic device 200 can send the redefined first data to the one or more applications on the electronic device 200.

[0599] For the introduction of S1211-S1220 in the embodiment of FIG12 , reference can be made to the description of S1108-S1117 in the embodiment of FIG11 , and this application will not go into details here.

[0600] S1221. Application B on the electronic device 200 uses the first data.

[0601] In the case that the first data is text data, the application B on the electronic device 200 can directly obtain the text content of the first data from the first data and use the text content of the first data.

[0602] In the case where the first data is file data, when application B on the electronic device 200 needs to use the first data, application B on the electronic device 200 can obtain the URI of the first data from the first data, and obtain the file data of the first data based on the URI of the first data. Specifically, application B on the electronic device 200 can send the URI of the first data to the communication module on the electronic device 100 through the communication module. After receiving the acquisition notification, the communication module on the electronic device 100 can obtain the file data of the first data based on the URI of the first data, and the communication module on the electronic device 100 then sends the file data of the first data to the communication module on the electronic device 200. The communication module on the electronic device 200 then sends the file data of the first data to application B on the electronic device 200, and application B on the electronic device 200 can use the file data of the first data.

[0603] In the data sharing method between two applications on different devices provided by the embodiment of Figure 12, before data sharing, different applications need to define the shared data according to this standard. After receiving the shared data, different applications also need to parse the shared data based on this standard. In other words, the data definition standard is unified for different applications and different sharing paths, achieving a unified format for shared data.

[0604] The present application provides an electronic device, which includes: one or more processors, one or more memories, and one or more cameras; one or more cameras, one or more memories are coupled to one or more processors, the one or more memories are used to store computer program code, the computer program code includes computer instructions, and one or more processors call computer instructions to enable the electronic device to execute a data sharing method provided in the embodiment of Figure 11.

[0605] The present application provides a computer-readable storage medium for storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes a data sharing method provided in the embodiment of FIG11 .

[0606] The present application provides a computer program product. When the computer program product is run on an electronic device, the electronic device executes a data sharing method provided in the embodiment of FIG11 .

[0607] The present application provides an electronic device, which includes: one or more processors, one or more memories, and one or more cameras; one or more cameras, one or more memories are coupled to one or more processors, and the one or more memories are used to store computer program code, the computer program code includes computer instructions, and one or more processors call computer instructions to enable the electronic device to implement a data sharing method provided in the embodiment of Figure 12.

[0608] The present application provides a computer-readable storage medium for storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes a data sharing method provided in the embodiment of FIG12 .

[0609] The present application provides a computer program product. When the computer program product is run on an electronic device, the electronic device executes a data sharing method provided in the embodiment of FIG12 .

[0610] The various implementation modes of this application can be combined arbitrarily to achieve different technical effects.

[0611] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described herein are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0612] Those skilled in the art will appreciate that all or part of the process steps in the above-described method embodiments can be implemented by a computer program instructing the relevant hardware. The program can be stored in a computer-readable storage medium, and when executed, the program can include the process steps in the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0613] In short, the above description is only an embodiment of the technical solution of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made based on the disclosure of the present invention should be included in the scope of protection of the present invention.

Claims

1. A data sharing system, It is characterized in that The system includes a first electronic device and a second electronic device, the first electronic device and the second electronic device establish a communication connection, the first electronic device includes a first application, and the second electronic device includes a second application, wherein: The first application is used to obtain first data; The first application is also used for: generating first definition data corresponding to the first data based on the specified data definition standard, wherein the first definition data includes attributes of the first data and the first data, or the first definition data includes attributes of the first data and a storage path of the first data; sending the first definition data to the second application via the first sharing path and the communication connection; The second application is used to obtain the first definition data through the first sharing path; The second application is further used to parse the first data or a storage path of the first data from the first definition data based on the specified data definition standard; The first application is also used for: Acquire second data; generating second definition data corresponding to the second data based on the specified data definition standard, wherein the second definition data includes attributes of the second data and the second data, or the second definition data includes attributes of the second data and a storage path of the second data; sending the second definition data to the second application via a second sharing path and the communication connection; The second application is also used for: Acquire the second definition data through the second sharing path; parsing the second data or a storage path of the second data from the second definition data based on the specified data definition standard; The second sharing path is different from the first sharing path.

2. The system according to claim 1, It is characterized in that The first electronic device further includes a first data management framework, and the second electronic device further includes a second data management framework; The first application is specifically used to send the first definition data to the first data management framework through the first sharing path; a first data management framework, configured to send the first definition data to the second data management framework via the communication connection; The second data management framework is further used to send the first definition data to the second application through the first sharing path.

3. The system according to claim 1 or 2, It is characterized in that The first application is further used to: generate a unified management protocol for the first data based on a unified management protocol standard, wherein the unified management protocol for the first data includes an identifier of the first sharing path; Sending the unified management protocol of the first data to the first data management framework: The first data management framework is further used to: send the unified management protocol of the first data to the second data management framework through the communication connection; The second data management framework is specifically used for: Acquire an identifier of the first sharing path from a unified management protocol of the first data; The first definition data is sent to the second application through the first sharing path based on the identifier of the first sharing path.

4. The system according to claim 2 or 3, It is characterized in that The first application is further used to: generate a usage description of the first data based on the specified data definition standard, wherein the usage description of the first data includes personalized permissions of the first sharing path; Sending the usage instructions of the first data to the first data management framework: The first data management framework is further used to: send the usage instructions of the first data to the second data management framework via the communication connection; The second data management framework is specifically used for: Obtaining a first notification sent by the second application, where the first notification is used to read the first data, and the first notification includes an identifier of the second application; Acquiring a permission rule for the first sharing path based on the identifier of the first sharing path in the unified management protocol of the first data; Obtaining personalized permissions for the first data from the usage instructions of the first data; After determining that the second application has the ability to access the first data based on the usage instructions of the first data, when the first data management framework determines that the second application has the ability to access the first data based on the personalized permissions of the first data, the permission rules of the first sharing path, the permission rules of the second data management framework and the identification of the second application, the first definition data is sent to the second application through the first sharing path based on the identification of the first sharing path.

5. The system according to claim 4, It is characterized in that The second data management framework is further used for: verifying the first definition data based on the specified data definition standard; If the verification is passed, the first definition data, the unified management protocol of the first data and the usage instructions of the first data are stored.

6. A data sharing method, It is characterized in that The method comprises: The second application on the second electronic device obtains the first definition data sent by the first application on the first electronic device through the first sharing path and the communication connection, wherein the first definition data is generated by the first application based on the specified data definition standard and the first data, the first definition data includes the attributes of the first data and the first data, or the first definition data includes the attributes of the first data and the storage path of the first data, the second electronic device is different from the first electronic device, and the first electronic device and the second electronic device establish the communication connection; The second application parses the first data or a storage path of the first data from the first definition data based on the specified data definition standard; The second application obtains the second definition data sent by the first application through the second sharing path and the communication connection, wherein the second definition data is generated by the first application based on the specified data definition standard and the second data, and the second definition data includes the attributes of the second data and the second data, or the second definition data includes the attributes of the second data and the storage path of the second data; The second application parses the second data or a storage path of the second data from the second definition data based on the specified data definition standard; The second sharing path is different from the first sharing path.

7. The method according to claim 6, It is characterized in that, The first electronic device further includes a first data management framework, and the second electronic device further includes a second data management framework; The second application acquires the first definition data sent by the first application through the first sharing path and the communication connection, specifically including: The second data management framework receives the first definition data sent by the first data management framework through the communication connection, wherein the first definition data stored in the first data management framework is sent by the first application; The second data management framework sends the first definition data to the second application through the first sharing path.

8. The method according to claim 6 or 7, It is characterized in that The second application acquires the first definition data sent by the first application through the first sharing path, specifically including: The second data management framework receives, through the communication connection, a unified management protocol for the first data sent by the first data management framework, wherein the unified management protocol for the first data is generated by the first application based on a unified management protocol standard, and the unified management protocol for the first data includes an identifier of the first sharing path; The second data management framework obtains the identifier of the first sharing path from the unified management protocol of the first data; The second data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path.

9. The method according to claim 8, It is characterized in that The second application acquires the second definition data sent by the first application through the second sharing path, specifically including: The second data management framework receives, through the communication connection, a unified management protocol for the second data sent by the first data management framework, wherein the unified management protocol for the second data is generated by the first application based on a unified management protocol standard, and the unified management protocol for the second data includes an identifier of the second sharing path; The second data management framework obtains the identifier of the second sharing path from the unified management protocol of the second data; The second data management framework sends the second definition data to the second application through the second sharing path based on the identifier of the second sharing path; The unified management protocol of the second data is different from the unified management protocol of the first data.

10. The method according to claim 8 or 9, It is characterized in that Before the second data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path, the method further includes: The second data management framework receives, through the communication connection, a usage description of the first data sent by the first data management framework, where the usage description of the first data is generated by the first application based on the specified data definition standard and sent to the first data management framework, and the usage description of the first data includes personalized permissions of the first data; The second data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path, specifically including: The second data management framework obtains a first notification sent by the second application, where the first notification is used to read the first data and includes an identifier of the second application; The second data management framework obtains the permission rules of the first sharing path based on the identifier of the first sharing path in the unified management protocol of the first data; The second data management framework obtains the personalized permission of the first data from the usage instructions of the first data; After the second data management framework determines that the second application has the ability to access the first data based on the usage instructions of the first data, when the first data management framework determines that the second application has the right to access the first data based on the personalized permissions of the first data, the permission rules of the first sharing path, the permission rules of the first data management framework and the identification of the second application, the second data management framework sends the first definition data to the second application through the first sharing path based on the identification of the first sharing path.

11. The method according to claim 10, It is characterized in that After the second data management framework receives the first definition data and the unified management protocol of the first data, the method further includes: The second data management framework verifies the first definition data based on the specified data definition standard; If the verification is passed, the second data management framework stores the first definition data, the unified management protocol of the first data and the usage instructions of the first data.

12. The method according to any one of claims 6 to 11, It is characterized in that The specified data definition standard is stored in the second data management framework; the method further comprises: The second data management framework sends the specified data definition criteria to the second application.

13. The method according to any one of claims 6 to 12, It is characterized in that After the second application parses the storage path of the first data from the first definition data based on the specified data definition standard, the method further includes: The second application sends the storage path of the first data to the first application through the communication connection; The second application receives the first data sent by the first application through the communication connection, and the first data is acquired by the first application based on a storage path of the first data.

14. The method according to any one of claims 6 to 13, It is characterized in that The attributes of the first data include one or more of the following: the type of the first data, the size of the first data, and the creation time of the first data.

15. A data sharing method, It is characterized in that Applied to a first electronic device, the first electronic device includes a first application and a second application, and the method includes: The first application obtains first data; The first application generates first definition data corresponding to the first data based on a specified data definition standard, the first definition data including attributes of the first data and the first data, or the first definition data including attributes of the first data and a storage path of the first data; The first application sends the first definition data to the second application through a first sharing path; The second application parses the first data or the first The storage path of the data; The first application obtains second data; The first application generates second definition data corresponding to the second data based on the specified data definition standard, where the second definition data includes attributes of the second data and the second data, or the second definition data includes attributes of the second data and a storage path of the second data; The first application sends the second definition data to the second application through a second sharing path; The second application parses the second data or a storage path of the second data from the second definition data based on the specified data definition standard; The second sharing path is different from the first sharing path.

16. The method according to claim 15, It is characterized in that The method further comprises: The first application acquires the first definition data; The first application sends the first definition data to the second application through the second sharing path; The second application parses the first data or a storage path of the first data from the first definition data based on the specified data definition standard.

17. The method according to claim 15 or 16, It is characterized in that The first electronic device further includes a first data management framework, and the first application sends the first definition data to the second application through a first sharing path, specifically including: The first application generates a unified management protocol for the first data based on a unified management protocol standard, wherein the unified management protocol for the first data includes an identifier of the first sharing path; The first application sends the first definition data and the unified management protocol of the first data to the first data management framework: The first data management framework obtains the identifier of the first sharing path from the unified management protocol of the first data; The first data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path.

18. The method according to claim 17, It is characterized in that The second application sends the second definition data to the second application through the second sharing path, specifically including: The first application generates a unified management protocol for the second data based on the unified management protocol standard, wherein the unified management protocol for the second data includes an identifier of the second sharing path; The first application sends the second definition data and the unified management protocol of the second data to the first data management framework: The first data management framework obtains an identifier of the second sharing path from the unified management protocol of the second data; The first data management framework sends the second definition data to the second application through the first sharing path based on the identifier of the second sharing path; The unified management protocol of the second data is different from the unified management protocol of the first data.

19. The method according to claim 17 or 18, It is characterized in that The method further comprises: The first application generates a usage description of the first data based on the specified data definition standard, wherein the usage description of the first data includes personalized permissions of the first data; The first data management framework sends the first definition data to the second application through the first sharing path based on the identifier of the first sharing path, specifically including: The first data management framework obtains a first notification sent by the second application, where the first notification is used to read the first data and includes an identifier of the second application; The first data management framework obtains the permission rules of the first sharing path based on the identifier of the first sharing path in the unified management protocol of the first data; The first data management box obtains the personalized permission of the first data from the usage instructions of the first data; After the first data management framework determines that the second application has the ability to access the first data based on the usage instructions of the first data, when the first data management framework determines that the second application has the authority to access the first data based on the personalized authority of the first data, the authority rules of the first sharing path, the authority rules of the first data management framework and the identifier of the second application, the first data management framework transmits the first defined data through the first sharing path based on the identifier of the first sharing path. Send to the second application.

20. The method according to claim 19, It is characterized in that After the first application sends the first definition data and the unified management protocol of the first data to the first data management framework, the method further includes: The first data management framework verifies the first definition data based on the specified data definition standard; If the verification is passed, the first data management framework stores the first definition data, a unified management protocol of the first data, and instructions for use of the first data.

21. The method according to claim 20, It is characterized in that The method further includes: if the verification fails, deleting the first definition data, the unified management protocol of the first data, and the usage instructions of the first data.

22. The method according to any one of claims 17 to 21, It is characterized in that The specified data definition standard and the unified management protocol standard are stored in the first data management framework; the method further includes: The first data management framework sends the specified data definition standard and the unified management protocol standard to the first application; The first data management framework sends the specified data definition criteria to the second application.

23. The method according to any one of claims 15 to 22, It is characterized in that After the second application parses the first data or a storage path of the first data from the first definition data, the method further includes: The first data management framework deletes the first definition data.

24. The method according to any one of claims 15 to 23, It is characterized in that The first sharing path or the second sharing path includes any one of the following: a drag path, a clipboard path, a cross-application manual path, and a cross-application automatic path.

25. The method according to any one of claims 15 to 24, It is characterized in that The attributes of the first data include one or more of the following: the type of the first data, the size of the first data, and the creation time of the first data.

26. An electronic device, It is characterized in that The electronic device includes: one or more processors, one or more memories, and one or more cameras; the one or more cameras and the one or more memories are coupled to the one or more processors, the one or more memories are used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute any one of the methods described in claims 15-25.

27. A computer-readable storage medium, It is characterized in that Used to store computer instructions, when the computer instructions are executed on an electronic device, the electronic device executes the method according to any one of claims 15 to 25.

28. A computer program product, It is characterized in that When the computer program product is executed on an electronic device, the electronic device is enabled to execute the method according to any one of claims 15 to 25.

Citation Information

Patent Citations

  • A data sharing method and system-level electronic device

    CN119003194B

  • Method for enabling a mobile user equipment to drag and drop data objects between distributed applications

    CN102057364A

  • Method used for transmitting data between first equipment and second equipment

    CN104243535A

  • Method of sharing data among corporation mobile applications

    CN104820803A

  • Method and apparatus of sharing data among a plurality of applications operating on mobile device

    CN104836715A