Application data communication method and apparatus, wearable device, and storage medium

Abstract

The present application relates to the technical field of wearable devices, and discloses an application data communication method and apparatus, a wearable device, and a storage medium. The wearable device comprises a bridging module, a first system, and a second system. The method comprises: when the first system acquires first application data of a first application in the first system, processing the first application data by means of a bridging module, and synchronizing the processed first application data to the second system; and / or, when the second system acquires second application data of a second application in the second system, processing the second application data by means of the bridging module, and synchronizing the processed second application data to the first system. In the present application, a bridging module is added to a wearable device, and application data is synchronized between a first operating system and a second operating system by means of the bridging module, thereby implementing synchronization of application data in a dual-core dual-system architecture.

Description

Method and device for communicating application data, wearable device and storage medium TECHNICAL FIELD

[0001] The present application relates to the technical field of wearable devices, and in particular to a method and device for communicating application data, a wearable device and a storage medium. BACKGROUND

[0002] An intelligent watch operating system is originally developed for a single-core single-system intelligent watch, and the biggest problem of the single-core single-system intelligent watch is high power consumption and short battery life. How to adapt the original intelligent watch operating system to dual-core hardware, and in particular how to perform data communication are the focus of the industry.

[0003] SUMMARY

[0004] The embodiments of the present application provide a method and device for communicating application data, a wearable device and a storage medium, which can realize synchronization of application data of dual-core dual-system. The technical solution is as follows:

[0005] In one aspect, a method for communicating application data is provided, which is executed by a wearable device including a bridge module, a first system and a second system. The method comprises:

[0006] When the first system obtains first application data of a first application in the first system, the first application data is processed by the bridge module, and the processed first application data is synchronized to the second system; and / or,

[0007] When the second system obtains second application data of a second application in the second system, the second application data is processed by the bridge module, and the processed second application data is synchronized to the first system.

[0008] In another aspect, a device for communicating application data is provided, which is deployed in a wearable device including a bridge module, a first system and a second system. The device comprises:

[0009] A first synchronization module is configured to, when the first system obtains first application data of a first application in the first system, process the first application data by the bridge module, and synchronize the processed first application data to the second system; and / or,

[0010] A second synchronization module is configured to, when the second system obtains second application data of a second application in the second system, process the second application data by the bridge module, and synchronize the processed second application data to the first system.

[0011] In another aspect, a wearable device is provided, which includes a processor and a memory having at least one program code stored therein, the at least one program code being loaded and executed by the processor to implement the application data communication method according to any of the above implementation manners.

[0012] In another aspect, a computer readable storage medium is provided, which has at least one program code stored therein, the at least one program code being loaded and executed by a processor to implement the application data communication method according to any of the above implementation manners.

[0013] In another aspect, a computer program product is provided, which stores at least one program code for being executed by a processor to implement the application data communication method according to any of the above implementation manners.

[0014] In some embodiments of the present application, by adding a bridge module in the wearable device, the synchronization of application data between the first operating system and the second operating system is realized through the bridge module, thereby realizing the synchronization of application data of the dual-core dual-system. BRIEF DESCRIPTION OF DRAWINGS

[0015] FIG. 1 shows a communication architecture diagram of a wearable device with dual-core dual-system according to an example embodiment of the present application;

[0016] FIG. 2 shows a flowchart of an application data communication method according to an example embodiment of the present application;

[0017] FIG. 3 shows a flowchart of an application data communication method according to an example embodiment of the present application;

[0018] FIG. 4 shows a schematic diagram of an application data communication method according to an example embodiment of the present application;

[0019] FIG. 5 shows a schematic diagram of an application data communication method according to an example embodiment of the present application;

[0020] FIG. 6 shows a flowchart of an application data communication method according to an example embodiment of the present application;

[0021] FIG. 7 shows a flowchart of an application data communication method according to an example embodiment of the present application;

[0022] FIG. 8 shows a flowchart of an application data communication method according to an example embodiment of the present application;

[0023] FIG. 9 shows a flowchart of an application data communication method according to an example embodiment of the present application;

[0024] FIG. 10 shows a flow chart of a method for communicating application data according to an example embodiment of the present application;

[0025] FIG. 11 shows a block diagram of an apparatus for communicating application data according to an example embodiment of the present application;

[0026] FIG. 12 shows a block diagram of a wearable device according to an example embodiment of the present application. DETAILED DESCRIPTION

[0027] For the purpose of making the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application will be described in further detail below with reference to the drawings.

[0028] As mentioned herein, "a plurality of" refers to two or more. "And / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, and B exists alone. The character " / " generally represents that the associated objects before and after it are in an "or" relationship.

[0029] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data for analysis, stored data, displayed data, etc.) and signals involved in the present application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions. For example, the application data and the like involved in the present application are obtained under full authorization.

[0030] The present application is a solution for the communication scenario of application data of dual-core dual-system.

[0031] It can be understood that the dual-core can be two processing units (such as processors), and the two processing units can be packaged in one chip. For example, the processing unit can be an integrated circuit or a chip. For example, the dual-core can also be understood as two independently packaged chips. The dual-system can refer to the programs running on the two processing units, such as operating systems.

[0032] The wearable device includes at least two systems, for example, an operating system; in some embodiments, not all of the two systems are independently developed, for example, part or all of the first system is provided by a system provider, unlike a completely independently developed system, the problem faced by the development of the dual-core communication architecture based on the first system is that some data links, data formats and data interfaces have been standardized by the developer of the first system. In order to achieve the purpose of dual-core application data communication, if the original module of the first system is directly modified, not only the difficulty and workload are large, but also it may cause unassessable risks; for example, the modified first system does not meet the requirements, thereby affecting the original process standard of the first system, resulting in uncontrollable problems or unsolvable problems. In some cases, it may not be modified or not allowed to be modified. Therefore, by adding a bridge module (for example, an Offload module), the bridge module synchronizes application data between the first system and the second system, thereby successfully accessing the dual-core application data communication scheme to the first system, solving the data adaptation problem between the first system and the second system.

[0033] In some embodiments, the bridge module can convert some application data that is inconsistent with the communication link format into a data format consistent with the communication link, so that it can be sent to another system through the communication link and recognized by another system; for example, when the bridge module obtains application data in the first system through a communication link, and the application data does not meet the data format of the communication link (for example, a dual-core communication link) for transmitting to the second system, the bridge module can perform format conversion and then transmit the data to the second system through the dual-core communication, so that the second system can recognize the related data. In some embodiments, the application data received by the second system through the communication link can also be converted into a data format that the first system can recognize and then provided to the first system (for example, some modules in the first system). The bridge module can be applied to dual-system (for example, dual-processor dual-system) communication, especially when the data format of part or all of the application data of one system is inconsistent with the data format of part or all of the application data of another system. The bridge module can solve the communication problem of inconsistent data formats. In some embodiments, the bridge module can also distinguish which data needs to be converted in data format; in some embodiments, the bridge module can also integrate other functions, which will be described in other embodiments.

[0034] In some embodiments, the bridge module can be provided in the first system; in some embodiments, the bridge module can also be independent of the first system, for example, running on an independent hardware module, for example, on a certain chip. In some embodiments, the bridge module can also be provided in the second system. In some embodiments, there can be corresponding bridge modules on the first system and the second system.

[0035] In some embodiments, the first processor is configured to run the first system, and the bridge module is added in the first system, that is, the bridge module is deployed in the first processor; for example, the bridge module is an independent process in the first system, so that the bridge module is decoupled from other processes in the first system, and changes in the other processes do not affect the function of the bridge module; for another example, the bridge module is attached to other processes in the first system, that is, the function of the bridge module is added in the other processes, so that the other processes are reused.

[0036] The wearable device has system applications and independent applications, and the system applications are generally system portal applications; for example, desktop, application list, or system interface (such as watch face), and the like, which are not displayed in the form of an icon in the application list, and the system applications can be a resident process, that is, the system applications are always running in the foreground or background. For example, please continue to refer to FIG. 1, the system applications include one or more of WearService, SystemUI, SysUI, and watch face applications. For example, the independent applications can be displayed in the form of an icon in the application list, and need to be clicked to run. In some embodiments, the independent applications can also be started or closed by other control components, such as a key, a button, a crown, and the like. In some embodiments, the independent applications are divided into one or more of first-party independent applications, third-party independent applications, and first-system-native independent applications; the first-system-native independent applications include telephone applications, short message applications, and calendar applications, and the like, which can also synchronize application data between the second system through the bridge module and the dual-core communication channel.

[0037] The first-party independent applications can be applications developed by the developer of the wearable device; for example, the first-party independent applications are self-developed applications by the second-system developer; for example, the first-party independent applications can be self-developed sports health applications by the second-system developer. Since the first-party independent applications are self-developed applications by the second-system developer, the second-system developer can directly communicate application data between the first-party independent applications. For example, please continue to refer to FIG. 1, the first system is a mobile operating system developed based on a Linux kernel, such as an Android system or a Hongmeng system, and the first system can also be an IOS system or other operating systems; for example, the first-party independent applications can communicate application data between the first system through an Android or Hongmeng native interface, and the first-party independent applications can communicate application data between the second system through the dual-core communication channel. For example, the third-party independent applications can be applications developed by a third party, and the third-party independent applications can communicate application data between the first system through an Android or Hongmeng native interface. In addition, the third-party independent applications can also communicate application data between the second system through the bridge module and the dual-core communication channel.

[0038] In some embodiments, the bridge module includes one or more of a lock screen state synchronization service, a notification data synchronization service, a watch face data synchronization service, and other data synchronization services. The lock screen state synchronization service can be used to synchronize lock screen state data of the wearable device between the first system and the second system, and the lock screen state data can be application data of SystemUI. The notification data synchronization service can be used to synchronize notification data of the wearable device between the first system and the second system, and the notification data can include one or more of notification data of a phone application, notification data of a message application, and notification data of a schedule application. The watch face data synchronization service can be used to synchronize data of a watch face application between the first system and the second system. The other data synchronization service can be used to synchronize application data of WearService and / or application data of SysUI between the first system and the second system, and the application data of SysUI can include desktop data or status bar data.

[0039] In some embodiments, the second processor is configured to run the second system, and the bridge module is deployed in the second processor, i.e., the bridge module is a separate process in the second system or is attached to another process in the second system. In some embodiments, the bridge module is not located in the first system or the second system, but is independent of the first system and the second system. In some embodiments, the bridge module can be a separate software module running on the hardware (processor) where the first system or the second system is located. In some embodiments, the bridge module can be a hardware module, e.g., a separate chip, i.e., the bridge module is deployed in a third processor. In some embodiments, the bridge module can run on another hardware module of the wearable device.

[0040] In some embodiments, when the bridge module is deployed in the second processor, the communication between the bridge module and the first processor, or the communication between the bridge module and the first system, needs to be transmitted according to the data format converted by the bridge module, i.e., the communication link between the bridge module and the first system needs to support the transmission of the data format converted by the bridge module from the application data of the second system.

[0041] In some embodiments, when the bridge module is a module independent of the first processor and the second processor, for example, in a third processor, the bridge module receives application data transmitted by the first system that needs to be converted, converts the application data into application data that can be transmitted to the second system and recognized by the second system. Alternatively, the bridge module receives application data transmitted by the second system that needs to be converted, and the bridge module converts the application data into a data format that can be transmitted to the first system and recognized by the first system, and then transmits to the first system. It can be understood that the transmission link between the bridge module and the first system and the transmission link between the bridge module and the second system support different data transmission formats before and after conversion.

[0042] For example, the power consumption of the first system is greater than the power consumption of the second system, and / or the performance of the first system is higher than the performance of the second system. For example, the power consumption of the first system is greater than the power consumption of the second system, which can be understood as the standby power consumption of the first system is greater than the standby power consumption of the second system, or the power consumption of the first system when processing services is greater than the power consumption of the second system when processing the same services, or the overall power consumption of the first system is greater than the overall power consumption of the second system. For example, the performance of the first system is higher than the performance of the second system, which can be understood as the computing power or hardware resources of the first system are lower than the computing power or hardware resources of the second system. The first system can be a smart system; in some embodiments, the first system is a Hongmeng system, an Android system, or an IOS system, etc.; for example, the first system is a WearOS system. The second system can be an embedded system; for example, the second system is a real-time system (RTOS) or a Hongmeng system. For example, a wearable device can include two processors, a first processor and a second processor, the first processor is used to run the first system, and the second processor is used to run the second system. The first processor can be a central processing unit (CPU). The second processor can be a microcontroller unit (MCU). It should be noted that the first processor and the second processor can be two independent packaged chips, or can be packaged in the same chip. Alternatively, the wearable device includes a multi-core processor, and the multiple cores of the processor respectively run the first system and the second system.

[0043] In some embodiments, the wearable device can include two or more systems, i.e., the wearable device can include at least three systems; the at least three systems include at least two embedded systems and at least one intelligent system; or, the at least three systems include at least two intelligent systems and at least one embedded system. Correspondingly, the wearable device includes at least three processors for running the at least three systems, wherein one processor is used for running one system; or, the wearable device includes a plurality of cores of one processor, which is used for running the at least three systems.

[0044] Referring to FIG. 2, a flowchart of a method for communicating application data is shown according to an example embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which includes a bridge module, a first system and a second system, and the bridge module is used for synchronizing application data between the first system and the second system. Referring to FIG. 2, the method includes:

[0045] Step 201: When the first system acquires first application data of a first application in the first system, the bridge module processes the first application data, and synchronizes the processed first application data to the second system.

[0046] It can be understood that the data format of part or all of the applications of the first system is different from that of part or all of the applications of the second system.

[0047] In some embodiments, the data format of the first application data before being processed by the bridge module is not suitable for the second system, and / or the data format of the second application data before being processed by the bridge module is not suitable for the first system. It can be understood that the data format of the first application data before being processed by the bridge module is suitable for the first system, and the data format of the processed first application data after being processed by the bridge module is suitable for the second system. For example, being suitable for the second system can be understood as being able to be acquired by the second system and being able to be recognized by the second system, such as being sent to the second system through a dual-core communication channel suitable for the second system, and further being parsed and read by the second system. For example, the processed first application data satisfies the transmission format of the above-mentioned dual-core communication channel, and can be parsed and read by the second system.

[0048] In some embodiments, the data of the second application data is not suitable for the first system, but is suitable for the second system, so it can be directly sent to the bridge module through a dual-core communication channel suitable for the second system, and provided to the first system after being processed by the bridge module, for example, provided to the corresponding module of the first system.

[0049] For example, the data format of the first application is different from that of the second application.

[0050] In some embodiments, the step of processing the first application data by the bridge module can be: converting, by the bridge module, a data format of the first application data from a first format to a second format, the processed first application data comprising the first application data in the second format; the first format being a data format adapted to the first system, i.e. the first application data in the first format can be acquired and recognized by the first system, and the second format being a data format adapted to the second system, i.e. the first application data in the second format can be acquired and recognized by the second system. In an embodiment of the present application, in the case that the first format is the same as the second format, i.e. the data format that can be acquired and recognized by the first system is the same as the data format that can be acquired and recognized by the second system, the bridge module can not perform the conversion of the data format of the application data, but directly perform the subsequent synchronization operation. In some embodiments of the present application, in some embodiments, synchronizing to the second system means synchronizing to an application of the second system.

[0051] In some embodiments, the step of processing the first application data by the bridge module and synchronizing the processed first application data to the second system can be: determining a service type corresponding to the first application; determining a communication mode matching the service type based on the service type; sending, by the first system, the first application data to the bridge module through the communication mode, processing the first application data by the bridge module, and synchronizing the processed first application data to the second system through the dual-core communication channel between the first processor and the second processor.

[0052] In some embodiments, the first processor is configured to run the first system, the second processor is configured to run the second system, and the bridge module is deployed in the first processor and / or the second processor. The bridge module is deployed in the first processor and the second processor, including that the bridge module comprises a first bridge module and a second bridge module, the first bridge module is deployed on the first processor, and the second bridge module is deployed on the second processor. Correspondingly, the step 201 can be: when the first system acquires the first application data of the first application in the first system, processing the received first application data by the first bridge module, and synchronizing the processed first application data to the second system through the dual-core communication between the first processor and the second processor.

[0053] Since the applications in the first system include native system applications and independent applications, and the independent applications include one or more of first-party independent applications, third-party independent applications, and native independent applications of the first system; for example, the native system applications, the native independent applications of the first system, and the third-party independent applications can communicate application data according to the method provided in the embodiments of the present application; therefore, when the first system obtains the first application data of the first application in the first system, in the case that the first application is a native system application, the first application data is processed by the bridging module, and the processed first application data is synchronized to the second system; and / or, in the case that the first application is a native independent application of the first system, the first application data is processed by the bridging module, and the processed first application data is synchronized to the second system; in the case that the first application is a third-party independent application, the first application data is processed by the bridging module, and the processed first application data is synchronized to the second system.

[0054] In some embodiments, the first system includes a native system, for example, a wear OS, which can be developed by a system manufacturer and then provided to a device manufacturer for further development or incorporation of the device manufacturer's own content.

[0055] In some embodiments, the native system includes one or more native independent applications, such as a native phone application, a native message application, a native schedule application, etc. For example, in the case of a Google wear OS, the native independent applications include, but are not limited to, one or more of Google Phone, Google Messages, and Google Calendar. In some embodiments, the first application includes third application data, the data format of the third application data is adapted to the first system and also adapted to the second system, in which case the third application data can be directly synchronized to the second system by the bridging module without the need to convert the data format of the third application data.

[0056] It can be understood that the first application can be an application including first application data, an application including third application data, or an application including both first application data and third application data.

[0057] In some embodiments, when the first application is a third-party independent application, the bridge module determines the data format of the application data of the first application, and when the data format of the application data (e.g., third application data) of the first application is adapted to the first system and also adapted to the second system, the bridge module synchronizes the third application data to the second system, i.e., the bridge module can not perform conversion of the application data format, but directly performs synchronization operation; when the data format of the application data (e.g., first application data included in the first application) of the first application is only adapted to the first system and not adapted to the second system, the bridge module converts the data format of the first application data from a first format to a second format, and synchronizes the first application data in the second format to the second system, the first format being a data format adapted to the first system, i.e., the first application data in the first format can be acquired and recognized by the first system, and the second format being a data format adapted to the second system, i.e., the first application data in the second format can be acquired and recognized by the second system.

[0058] In some embodiments of the present application, the first application is taken as an example of an independent application native to the first system; for example, the first application can include one or more of a telephone application, a short message application, and a schedule application; correspondingly, the first application data of the first application includes one or more of application data of the telephone application, application data of the short message application, and application data of the schedule application.

[0059] In some embodiments, when the first application data includes application data of the telephone application, when the telephone application generates new application data, the first system acquires the application data of the telephone application, converts the data format of the application data of the telephone application through the bridge module, and synchronizes the converted application data of the telephone application to the second system, and the converted application data of the telephone application can be acquired and recognized by the second system. For example, when the telephone application acquires a new missed call, the missed call is sent to the first system as the application data of the telephone application; for another example, when the telephone application adds new contact information, the new contact information is sent to the first system as the application data of the telephone application; for another example, when the telephone application modifies contact information, the modified contact information is sent to the first system as the application data of the telephone application; for another example, when the telephone application deletes contact information, the deleted contact information is sent to the first system as the application data of the telephone application.

[0060] In some embodiments, in the case that the first application data comprises application data of the short message application, when the short message application generates new application data, when the first system acquires the application data of the short message application, the bridge module converts the data format of the application data of the short message application, synchronizes the converted application data of the short message application to the second system, and the converted application data of the short message application can be obtained and recognized by the second system. For example, when the short message application acquires a new short message, the new short message is sent to the first system as the application data of the short message application; for another example, when the short message application deletes a short message, the deleted short message is sent to the first system as the application data of the short message application.

[0061] In some embodiments, in the case that the first application data comprises application data of the short message application, when the short message application generates new application data, when the first system acquires the application data of the short message application, the bridge module converts the data format of the application data of the short message application, synchronizes the converted application data of the short message application to the second system, and the converted application data of the short message application can be obtained and recognized by the second system. For example, when the short message application acquires a new short message, the new short message is sent to the first system as the application data of the short message application; for another example, when the short message application deletes a short message, the deleted short message is sent to the first system as the application data of the short message application.

[0062] In some embodiments, in the case that the first application data comprises application data of the short message application, when the short message application generates new application data, when the first system acquires the application data of the short message application, the bridge module converts the data format of the application data of the short message application, synchronizes the converted application data of the short message application to the second system, and the converted application data of the short message application can be obtained and recognized by the second system. For example, when the short message application acquires a new short message, the new short message is sent to the first system as the application data of the short message application; for another example, when the short message application deletes a short message, the deleted short message is sent to the first system as the application data of the short message application.

[0063] In some embodiments, in the case that the first application data comprises application data of the short message application, when the short message application generates new application data, when the first system acquires the application data of the short message application, the bridge module converts the data format of the application data of the short message application, synchronizes the converted application data of the short message application to the second system, and the converted application data of the short message application can be obtained and recognized by the second system. For example, when the short message application acquires a new short message, the new short message is sent to the first system as the application data of the short message application; for another example, when the short message application deletes a short message, the deleted short message is sent to the first system as the application data of the short message application.

[0064] In some embodiments, in the case that the first application data comprises application data of WearService, when WearService generates new application data, when the first system obtains the application data of WearService, the data format of WearService is converted by the bridging module, the application data of WearService after format conversion is synchronized to the second system, and the application data of WearService after format conversion can be obtained and recognized by the second system. For example, when the WearService of the wearable device obtains notification data, the WearService sends the notification data to the first system as application data.

[0065] In some embodiments, in the case that the first application data comprises application data of SystemUI, when the lock screen state of the wearable device changes, the SystemUI takes the changed lock screen state as application data of SystemUI, when the first system obtains the application data of SystemUI, the application data of SystemUI is format converted by the bridging module, the application data of SystemUI after format conversion is synchronized to the second system, and the application data of SystemUI after format conversion can be obtained and recognized by the second system.

[0066] In some embodiments, in the case that the first application data comprises application data of SysUI, when the desktop or status bar of the wearable device changes, the SysUI takes the changed desktop data or status bar data as application data of SysUI, when the first system obtains the application data of SysUI, the application data of SysUI is format converted by the bridging module, the application data of SysUI after format conversion is synchronized to the second system, and the application data of SysUI after format conversion can be obtained and recognized by the second system.

[0067] Step 202: When the second system obtains the second application data of the second application in the second system, the second application data is processed by the bridging module, and the processed second application data is synchronized to the first system.

[0068] In some embodiments, the data format of the second application data before being processed by the bridging module is adaptable to the second system, but the data format of the second application data before being processed by the bridging module is not adaptable to the first system. Therefore, the data format of the second application data needs to be converted by the bridging module, so that the data format of the second application data after being processed by the bridging module can be adaptable to the first system.

[0069] In some embodiments, the step of processing the second application data by the bridge module can be: converting, by the bridge module, a data format of the second application data from a third format to a fourth format, the processed second application data comprising the second application data in the fourth format; the fourth format being a data format adapted to the first system, i.e., the second application data in the fourth format can be acquired and recognized by the first system, and the third format being a data format adapted to the second system, i.e., the second application data in the third format can be acquired and recognized by the second system. In an embodiment of the present application, in the case that the third format is the same as the fourth format, i.e., the data format that can be acquired and recognized by the first system is the same as the data format that can be acquired and recognized by the second system, the bridge module can not perform the conversion of the data format of the application, but directly perform the subsequent synchronization operation. In some embodiments of the present application, synchronizing to the first system means synchronizing to a certain application of the first system.

[0070] In some embodiments, the step of processing the second application data by the bridge module and synchronizing the processed second application data to the first system can be: obtaining the second application data through a dual-core communication channel between the first processor and the second processor; processing the second application data by the bridge module; determining a service type corresponding to the second application; determining a communication mode matching the service type based on the service type; and synchronizing the processed second application data to the first system through the communication mode.

[0071] The first processor is configured to run the first system, and the second processor is configured to run the second system. The bridge module is deployed in the first processor and / or the second processor. The bridge module is deployed in the first processor and the second processor, including that the bridge module comprises a first bridge module and a second bridge module, the first bridge module is deployed on the first processor, and the second bridge module is deployed on the second processor. Correspondingly, the step 202 can be: when the second system acquires the second application data of the second application in the second system, processing the received second application data by the second bridge module, and synchronizing the processed second application data to the first system through a dual-core communication between the first processor and the second processor.

[0072] In some embodiments, the first application comprises one or more of a native system application, a native independent application, and a third-party independent application of the first system; and / or, the second application comprises one or more of a system application, a first-party independent application, and a third-party independent application of the second system.

[0073] For example, the native system application can include WearServices and / or SysUI; the native standalone application can include one or more of a native phone application, a short message application, a schedule application, and the like. For example, in the case of Google Wear OS, the native standalone application includes one or more of Google Phone, Google Messages, Google Calendar, and the like; the third-party standalone application can be an application developed by another third-party manufacturer, such as a WeChat application, an Alipay application, and the like; and the first-party standalone application can be an application developed by a device manufacturer, such as a heart rate detection application, a blood pressure detection application, and the like.

[0074] For example, the second application includes one or more of a system application of a second system, a first-party standalone application, and a third-party standalone application; in some embodiments, when the second system obtains second application data of the second application in the second system, in the case where the second application is a system application, the second application data is processed by the bridging module, and the processed second application data is synchronized to the first system; and / or, in the case where the second application is a first-party standalone application in the second system, the second application data is processed by the bridging module, and the processed second application data is synchronized to the first system; and / or, in the case where the second application is a third-party standalone application in the second system, the second application data is processed by the bridging module, and the processed second application data is synchronized to the first system.

[0075] In some embodiments, the second application further includes fourth application data, the data format of the fourth application data is adapted to the second system and also adapted to the first system, in which case the fourth application data can be directly synchronized to the first system by the bridging module without the need for conversion of the data format of the fourth application data.

[0076] It can be understood that the second application can be an application including second application data, an application including fourth application data, or an application including both second application data and fourth application data.

[0077] In some embodiments, in the case where the second application is a first-party standalone application, the data format of the application data of the second application is determined by the bridging module, in the case where the data format of the application data (for example, fourth application data) of the second application is adapted to the first system and also adapted to the second system, the fourth application data is synchronized to the first system by the bridging module, that is, the bridging module can not perform conversion of the data format of the application data, but directly perform the synchronization operation; in the case where the data format of the application data (for example, second application data included in the second application) of the second application is only adapted to the second system and not adapted to the first system, the data format of the second application data is converted from a third format to a fourth format by the bridging module, and the second application data in the fourth format is synchronized to the first system.

[0078] In some embodiments, the first-party independent application can run on the first system and / or the second system.

[0079] For example, the first-party independent application can also run on the first system, and the first-party independent application can directly communicate with the second system through the dual-core communication channel between the first processor and the second processor.

[0080] For example, the first-party independent application can also run on the first system, and the data of the first-party independent application can also be transmitted to the second system through the bridge module and the dual-core communication channel, but without format conversion through the bridge module.

[0081] For example, the first-party independent application can also run on the first system, and the data of the first-party independent application can also be transmitted to the second system through the bridge module and the dual-core communication channel, but without format conversion through the bridge module.

[0082] For example, the first-party independent application can also run on the first system, and the data of the first-party independent application can also be transmitted to the second system through the bridge module and the dual-core communication channel, but without format conversion through the bridge module.

[0083] In some embodiments of the present application, by adding a bridge module in the wearable device, the bridge module is used to synchronize the application data between the first system and the second system, so as to realize the synchronization of the application data of the dual-core dual-system.

[0084] It should be noted that only step 201 can be performed; or only step 202 can be performed; or steps 201 and 202 can be performed. It should be noted that the bridge module can not only synchronize the application data between the first system and the second system, but also have an interface display function; accordingly, the method further comprises: the wearable device displays the system interface of the first system through the bridge module; and / or, the wearable device displays the system interface of the second system through the bridge module.

[0085] In some embodiments, the bridge module has the display of the charging interface, the display of the power reminder interface, the display of the card swiping interface, and the display of the drainage interface of the second system; accordingly, the step of the wearable device displaying the system interface of the second system through the bridge module can be: the wearable device displays the charging interface of the second system through the bridge module; and / or, the wearable device displays the power reminder interface of the second system through the bridge module; and / or, the wearable device displays the card swiping reminder interface of the second system through the bridge module; and / or, the wearable device displays the drainage interface of the second system through the bridge module.

[0086] In some embodiments, the bridge module is provided with display of a charging interface of the first system, display of a power reminder interface, display of a card swiping interface, and display of a draining interface; accordingly, the step of displaying the system interface of the first system by the wearable device through the bridge module can be: displaying, by the wearable device through the bridge module, a charging interface of the first system; and / or, displaying, by the wearable device through the bridge module, a power reminder interface of the first system; and / or, displaying, by the wearable device through the bridge module, a card swiping interface of the first system; and / or, displaying, by the wearable device through the bridge module, a draining interface of the first system.

[0087] It should be noted that the display interface function of the bridge module can be customized; for example, the display function of the bridge module can be customized; for example, the bridge module displays a desktop interface; for another example, the bridge module displays a status bar interface, and the like.

[0088] In some embodiments, the bridge module can not only synchronize application data between the first system and the second system, but also implement system functions; accordingly, the method further includes: implementing, by the wearable device through the bridge module, system functions of the first system; and / or, implementing, by the wearable device through the bridge module, system functions of the second system.

[0089] In some embodiments of the present application, the bridge module is a newly added system application, and one of its functions is to communicate with the application data of the first system and the application data of the second system through conversion and adaptation. In some embodiments, the bridge module can be implanted in the system interface or system function of the second system.

[0090] Please refer to FIG. 3, which shows a flowchart of the application data communication method according to an example embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which includes a bridge module, a first system, and a second system, the power consumption of the first system is greater than that of the second system, and / or the performance of the first system is higher than that of the second system. In some embodiments of the present application, a first processor is used to run the first system, a second processor is used to run the second system, and the bridge module is deployed in the first processor. Referring to FIG. 3, the method includes:

[0091] Step 301: The first system obtains first application data of a first application.

[0092] In some embodiments, this step is similar to step 201, which will not be repeated here.

[0093] Step 302: The first system determines a business type corresponding to the first application.

[0094] In some embodiments, the first application comprises one or more of a native system application, a native standalone application, and a third-party standalone application of the first system. The description of each application can refer to other embodiments.

[0095] In some embodiments, the service type comprises one or more of a notification type, a watch face type, a widget type, a contact data type, and a lock screen state type. Different applications correspond to different service types, and the first system stores a correspondence between application identifiers and service types. In this step, the first system obtains, based on the application identifier of the first application, a service type corresponding to the first application from the correspondence between application identifiers and service types.

[0096] Step 303: The first system determines, based on the service type, a communication mode matching the service type.

[0097] The first system stores a correspondence between service types and communication modes. In this step, the first system obtains, based on the service type, a communication mode matching the service type from the correspondence between service types and communication modes. The communication mode can be one or more of a communication interface, broadcast communication, and component communication. In some embodiments, when the service type is a notification type, the communication mode is determined to be a communication interface; when the service type is a lock screen type, the communication mode is determined to be broadcast communication, which can be a communication mode of a broadcast function of the first system or a Bluetooth broadcast communication mode of a Bluetooth module included in the first system.

[0098] Step 304: The first system sends the first application data to the bridge module through the communication mode.

[0099] In some embodiments, when the communication mode is a communication interface, the first system sends the first application data to the bridge module through the communication interface between the first system and the bridge module, and the bridge module receives the first application data sent by the first system through the communication interface. For example, referring to FIG. 4, the terminal device establishes a communication connection with the second processor (the second processor is configured to run the second system) through a Bluetooth communication link, the second processor communicates with the bridge module through a dual-core communication channel, and the bridge module communicates with the first processor (the first processor is configured to run the first system) through a communication interface. For example, the first processor comprises WearService and SysUI. Accordingly, the bridge module communicates with WearService through the communication interface, and WearService communicates with SysUI through the communication interface.

[0100] In some embodiments, the bridge module synchronizes the processed first application data to the second system by a dual-core communication channel between the first processor and the second processor. The second system receives the synchronized first application data and processes based on the first application data; for example, the first application data is the watch face data, and the system running in the current interface is the second system, the second system updates the watch face application based on the watch face data.

[0101] Step 305: The bridge module processes the first application data and synchronizes the processed first application data to the second system.

[0102] In some embodiments, the step of the bridge module synchronizing the processed first application data to the second system can be: the bridge module synchronizes the processed first application data to the second system through a dual-core communication channel between the first processor and the second processor. The second system receives the synchronized first application data and processes based on the first application data; for example, the first application data is the watch face data, and the system running in the current interface is the second system, the second system updates the watch face application based on the watch face data.

[0103] In some embodiments of the present application, the bridge module is deployed between the first processor and the second processor running the second system to communicate data through a dual-core communication channel, and the communication mode between the bridge module in the first processor and the first system is determined based on the service type, so that different service types can be communicated through different communication modes, and the first application data obtained by the first system is synchronized to the second system.

[0104] Referring to FIG. 6, a flowchart of a method for communicating application data according to an example embodiment of the present application is shown. The execution subject in the embodiment of the present application can be a wearable device, which includes a bridge module, a first system and a second system. The power consumption of the first system is greater than that of the second system, and / or the performance of the first system is higher than that of the second system. In some embodiments of the present application, the first processor is used to run the first system, the second processor is used to run the second system, and the bridge module is deployed in the second processor. Referring to FIG. 6, the method includes:

[0105] Step 601: The first system obtains first application data of a first application.

[0106] In some embodiments, this step is similar to step 201 and will not be repeated here.

[0107] Step 602: The first system sends the first application data to the bridge module through a dual-core communication channel between the first processor and the second processor.

[0108] In some embodiments, the first system comprises a native system of the wearable device, and in the case that the bridge module is disposed in the second processor, the data format supported by the dual-core communication channel is set based on the first system, so that the dual-core communication channel supports transmission of the first application data.

[0109] Step 603: The bridge module receives the first application data sent by the first system through the dual-core communication channel, and processes the first application data.

[0110] Step 604: The bridge module synchronizes the processed first application data to the second system.

[0111] In some embodiments, the step of synchronizing the processed first application data to the second system by the bridge module can be: the bridge module determines the service type corresponding to the first application; based on the service type, determines a communication mode matching the service type; and synchronizes the processed first application data to the second system through the communication mode.

[0112] In some embodiments, in the case that the communication mode is a communication interface, the bridge module synchronizes the processed first application data to the second system through the communication interface between the second system and the bridge module. In other embodiments, in the case that the communication mode is broadcast communication, the bridge module broadcasts the processed first application data, and the second system receives the broadcasted first application data.

[0113] In some embodiments, in the case that the first application is a third-party independent application, the step can be replaced by: the bridge module synchronizes the first application data in the sixth format to the second system through the communication mode.

[0114] In some embodiments of the present application, the bridge module is disposed in the second processor, and the first system runs in the first processor, and the bridge module and the second system in the second processor communicate through the dual-core communication channel, and the communication mode between the bridge module and the second system is determined based on the service type, so that different service types can be communicated through different communication modes, and the first application data obtained by the first system can be synchronized to the second system.

[0115] Please refer to FIG. 7, which shows a flowchart of a method for communicating application data according to an example embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which comprises a bridge module, a first system and a second system. The power consumption of the first system is greater than that of the second system, and / or the performance of the first system is higher than that of the second system. In some embodiments of the present application, the first processor is used to run the first system, the second processor is used to run the second system, and the bridge module is disposed in the third processor. Referring to FIG. 7, the method comprises:

[0116] Step 701: The first system acquires first application data of a first application.

[0117] In some embodiments, the present step is similar to step 201, which will not be repeated here.

[0118] Step 702: The first system sends the first application data to the bridge module through a communication channel between the first processor and the third processor.

[0119] Step 703: The bridge module processes the first application data and synchronizes the processed first application data to the second system through a communication channel between the third processor and the second processor.

[0120] The third processor is connected to the first processor and the second processor through respective dual-core communication channels; or the third processor is connected to the first processor through a dual-core communication channel, and the first processor and the second processor are connected through a dual-core communication channel; or the third processor is connected to the second processor through a dual-core communication channel, and the first processor and the second processor are connected through a dual-core communication channel.

[0121] In some embodiments of the present application, the third processor and the first processor, and the third processor and the second processor communicate through communication channels, thereby realizing the synchronization of application data between the first system and the second system, and further synchronizing the first application data acquired by the first system to the second system.

[0122] Please refer to FIG. 8, which shows a flowchart of a communication method of application data according to an example embodiment of the present application. The execution subject in the present embodiment can be a wearable device, which includes a bridge module, a first system and a second system. The power consumption of the first system is greater than that of the second system, and / or the performance of the first system is higher than that of the second system. In some embodiments of the present application, the first processor is used to run the first system, the second processor is used to run the second system, and the bridge module is deployed in the second processor. Referring to FIG. 8, the method includes:

[0123] Step 801: The second system acquires second application data of a second application.

[0124] In some embodiments, the present step is similar to step 202, which will not be repeated here.

[0125] Step 802: The second system determines a business type corresponding to the second application.

[0126] Step 803: The second system determines a communication mode matching the business type based on the business type.

[0127] In some embodiments, this step is the same as step 303, and thus is not described here again.

[0128] Step 804: The second system sends the second application data to the bridge module through the communication mode.

[0129] In some embodiments, this step is similar to step 304, and thus is not described here again.

[0130] Step 805: The bridge module processes the second application data and synchronizes the processed second application data to the first system.

[0131] The step of synchronizing the processed second application data to the first system by the bridge module can be: the bridge module synchronizes the processed second application data to the first system through the dual-core communication channel between the first processor and the second processor.

[0132] In some embodiments, this step is similar to step 305, and thus is not described here again.

[0133] In some embodiments of the present application, the bridge module is disposed in the first processor, and the second processor runs the second system. The bridge module and the first system in the first processor communicate through the dual-core communication channel between the first processor and the second processor, and the communication mode between the bridge module and the first system is determined based on the service type, so that different service types can be communicated through different communication modes, and the first application data obtained by the second system can be synchronized to the first system.

[0134] Please refer to FIG. 9, which shows a flowchart of a method for communicating application data according to an example embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which includes a bridge module, a first system and a second system. The power consumption of the first system is greater than that of the second system, and / or the performance of the first system is higher than that of the second system. In some embodiments of the present application, the first processor is used to run the first system, the second processor is used to run the second system, and the bridge module is disposed in the first processor. Referring to FIG. 9, the method includes:

[0135] Step 901: The second system obtains second application data of a second application.

[0136] In some embodiments, this step is similar to step 202, and thus is not described here again.

[0137] Step 902: The second system sends the second application data to the bridge module through the dual-core communication channel between the first processor and the second processor.

[0138] Step 903: The bridge module processes the second application data.

[0139] Step 904: The bridge module synchronizes the processed second application data to the first system.

[0140] In some embodiments, the step of the bridge module synchronizing the processed second application data to the first system can be: the bridge module determining the service type corresponding to the second application; determining the communication mode matching the service type based on the service type; and synchronizing the processed second application data to the first system through the communication mode.

[0141] In some embodiments, when the communication mode is a communication interface, the bridge module synchronizes the processed second application data to the first system through the communication interface between the first system and the bridge module. In other embodiments, when the communication mode is a broadcast communication, the bridge module broadcasts the processed second application data, and the first system receives the broadcasted second application data in the fourth format.

[0142] In some embodiments of the present application, the bridge module is deployed between the second processor and the first processor running the first system to communicate data through a dual-core communication channel, while the communication mode between the bridge module of the second processor and the second system is determined based on the service type, so that different service types can be communicated through different communication modes, and the second application data obtained by the second system can be synchronized to the first system.

[0143] Please refer to FIG. 10, which shows a flowchart of a method for communicating application data according to an example embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which includes a bridge module, a first system and a second system. The power consumption of the first system is greater than that of the second system, and / or the performance of the first system is higher than that of the second system. In some embodiments of the present application, a first processor is used to run the first system, a second processor is used to run the second system, and the bridge module is deployed in a third processor. Referring to FIG. 10, the method includes:

[0144] Step 1001: The second system obtains second application data of a second application.

[0145] In some embodiments, this step is similar to step 202, which will not be repeated here.

[0146] Step 1002: The second system determines to send the second application data to the bridge module through a communication channel between the second processor and the third processor.

[0147] Step 1003: The bridge module processes the second application data and synchronizes the processed first application data to the first system through a communication channel between the first processor and the third processor.

[0148] The third processor is connected with the first processor and the second processor through respective dual-core communication channels; or, the third processor is connected with the first processor through a dual-core communication channel of both sides, and the first processor and the second processor are connected through a dual-core communication channel of both sides; or, the third processor is connected with the second processor through a dual-core communication channel of both sides, and the first processor and the second processor are connected through a dual-core communication channel of both sides.

[0149] In some embodiments of the present application, the third processor and the first processor and the third processor and the second processor communicate through a tri-core communication channel, thereby realizing synchronization of application data between the first system and the second system, and further synchronizing the first application data obtained by the first system to the second system.

[0150] Please refer to FIG. 11, which shows a block diagram of an application data communication device according to an exemplary embodiment of the present application. The device is deployed in a wearable device, which includes a bridge module, a first system and a second system. The device includes:

[0151] The first synchronization module 1101 is configured to, when the first system obtains first application data of a first application in the first system, process the first application data through the bridge module, and synchronize the processed first application data to the second system; and / or,

[0152] The second synchronization module 1102 is configured to, when the second system obtains second application data of a second application in the second system, process the second application data through the bridge module, and synchronize the processed second application data to the first system.

[0153] In some embodiments, the first processor is configured to run the first system, and the second processor is configured to run the second system.

[0154] The first synchronization module 1101 is configured to determine a service type corresponding to the first application, determine a communication mode matching the service type based on the service type, send the first application data to the bridge module through the communication mode, process the first application data through the bridge module, synchronize the processed first application data to the second system through the dual-core communication channel between the first processor and the second processor; and / or,

[0155] The second synchronization module 1102 is configured to obtain the second application data through the dual-core communication channel between the first processor and the second processor, process the second application data through the bridge module, determine a service type corresponding to the second application, determine a communication mode matching the service type based on the service type, and synchronize the processed second application data to the first system through the communication mode.

[0156] In some embodiments, the first synchronization module 1101 is configured to convert, by the bridge module, a data format of the first application data from a first format to a second format, and the processed first application data comprises the first application data in the second format; and / or,

[0157] The second synchronization module 1102 is configured to convert, by the bridge module, a data format of the second application data from a third format to a fourth format, and the processed second application data comprises the second application data in the fourth format.

[0158] In some embodiments, the bridge module is an independent process in the first system; or the bridge module is attached to other processes in the first system; and / or the bridge module is an independent process in the second system; or the bridge module is attached to other processes in the second system.

[0159] In some embodiments, the first processor is configured to run the first system, and the second processor is configured to run the second system, and the bridge module is deployed in the first processor and / or the second processor.

[0160] In some embodiments, the bridge module is deployed in the first processor and the second processor comprises: the bridge module comprises a first bridge module and a second bridge module, the first bridge module is deployed on the first processor, and the second bridge module is deployed on the second processor.

[0161] The first synchronization module 1101 is configured to process, by the first bridge module, the received first application data, and synchronizes the processed first application data to the second system through dual-core communication between the first processor and the second processor; and / or,

[0162] The second synchronization module 1102 is configured to process, by the second bridge module, the received second application data, and synchronizes the processed second application data to the first system through dual-core communication between the first processor and the second processor.

[0163] In some embodiments, the data formats of part or all of the applications of the first system are different from the data formats of part or all of the applications of the second system; wherein the data format of the first application data before being processed by the bridge module is not adapted to the second system, and / or the data format of the second application data before being processed by the bridge module is not adapted to the first system.

[0164] In some embodiments, the first processor is configured to run the first system, the second processor is configured to run the second system, and the bridge module is disposed in a third processor; the third processor is connected with the first processor and the second processor through respective dual-core communication channels; or, the third processor is connected with the first processor through a dual-core communication channel, and the first processor and the second processor are connected through a dual-core communication channel; or, the third processor is connected with the second processor through a dual-core communication channel, and the first processor and the second processor are connected through a dual-core communication channel.

[0165] In some embodiments, the service type includes one or more of a notification type, a watch face type, a widget type, a contact data type, and a lock screen state type; and the communication manner includes a communication interface and / or broadcast communication.

[0166] The first synchronization module 1101 is configured to, in a case where the service type is the notification type, determine that the communication manner is the communication interface; and / or,

[0167] The first synchronization module 1101 is configured to, in a case where the service type is the lock screen type, determine that the communication manner is the broadcast communication.

[0168] In some embodiments, the first application includes one or more of a native system application, a native standalone application, and a third-party standalone application of the first system; and / or, the second application includes one or more of a system application, a first-party standalone application, and a third-party standalone application of the second system.

[0169] In some embodiments, the first application includes third application data, the data format of the third application data is adapted to the first system and also adapted to the second system, and the apparatus further includes:

[0170] The third synchronization module is configured to synchronize the third application data to the second system through the bridge module.

[0171] In some embodiments, the power consumption of the first operating system is greater than the power consumption of the second operating system; and / or, the performance of the first operating system is higher than the performance of the second operating system.

[0172] In some embodiments, the apparatus further includes:

[0173] The first display module is configured to display a system interface of the first operating system through the bridge module; and / or,

[0174] The second display module is configured to display a system interface of the second operating system through the bridge module.

[0175] In some embodiments, the second display module is configured to display a charging interface of the second operating system through the bridge module; and / or,

[0176] The second display module is configured to display, by the bridging module, a power reminder interface of the second operating system; and / or,

[0177] The second display module is configured to display, by the bridging module, a card swiping reminder interface of the second operating system; and / or,

[0178] The second display module is configured to display, by the bridging module, a draining interface of the second operating system.

[0179] In some embodiments, the apparatus further includes:

[0180] The bridging module is configured to implement a system function of the first operating system; and / or,

[0181] The bridging module is configured to implement a system function of the second operating system.

[0182] In some embodiments of the present application, by adding the bridging module in the wearable device, the synchronization of the application data between the first operating system and the second operating system is realized by the bridging module, so that the synchronization of the application data of the dual-core dual-system is realized.

[0183] It should be noted that the application data communication device provided in the above embodiments is only used as an example for the division of the above functional modules when the application data is communicated, and in actual application, the above functions can be completed by different functional modules according to the needs, that is, the internal structure of the wearable device is divided into different functional modules to complete all or part of the functions described above. In addition, the application data communication device and the application data communication method provided in the above embodiments belong to the same concept, and the specific implementation process is described in the method embodiments, which will not be repeated here.

[0184] Referring to FIG. 12, a structural block diagram of a wearable device 1200 is shown according to an example embodiment. The device 1200 includes a processor 1210 and a memory 1220, and a display screen 1230. The processor 1210 can include one or more processing cores. The processor 1210 connects various parts within the wearable device through various interfaces and lines, and performs various functions of the wearable device and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 1220, and calling data stored in the memory 1220. Optionally, the processor 1210 can be implemented in at least one of a hardware form of a digital signal processing (DSP), a field-programmable gate array (FPGA), a programmable logic array (PLA). The processor 1210 can be integrated with a combination of one or more of a central processing unit (CPU), a graphics processing unit (GPU), a neural-network processing unit (NPU), and a modem. Among them, the CPU is mainly responsible for processing the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing the content to be displayed by the display screen 1230; the NPU is used to implement artificial intelligence (AI) functions; and the modem is used to process wireless communication. It can be understood that the above-mentioned modem can also not be integrated into the processor 1210, but be implemented by a separate chip.

[0185] The memory 1220 can include a random access memory (RAM) and can also include a read-only memory (ROM). Optionally, the memory 1220 includes a non-transitory computer-readable storage medium. The memory 1220 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 1220 can include a program storage area and a data storage area, wherein the program storage area can store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments described below, etc.; and the data storage area can store data created according to the use of the wearable device (such as audio data, a phone book, etc.).

[0186] The display screen 1230 is a display component for displaying a user interface. Optionally, the display screen 1230 is a display screen with touch function, through which the user can perform touch operation on the display screen 1230 using fingers, touch pens or any other suitable objects.

[0187] The display screen 1230 is usually arranged on the front panel of the wearable device. The display screen 1230 can be designed as a full screen, a curved screen, a special-shaped screen, a double-sided screen or a folding screen. The display screen 1230 can also be designed as a combination of a full screen and a curved screen, a combination of a special-shaped screen and a curved screen, etc., which is not limited in the embodiment.

[0188] In addition, those skilled in the art can understand that the structure of the wearable device shown in the above-mentioned drawings does not constitute a limitation on the wearable device, and the wearable device can include more or fewer components than the drawings, or combine certain components, or different component arrangements. For example, the wearable device also includes audio acquisition devices, speakers, radio frequency circuits, input units, sensors, audio circuits, wireless fidelity (WiFi) modules, power supplies, Bluetooth modules and other components, which are not described here.

[0189] The embodiment of the present application also provides a computer readable medium, which stores at least one program code, the at least one program code is loaded and executed by the processor to implement the application data communication method shown in the above various embodiments.

[0190] The embodiment of the present application also provides a computer program product, which stores at least one program code, the at least one program code is loaded and executed by the processor to implement the application data communication method shown in the above various embodiments.

[0191] In some embodiments, the computer program product related to the embodiment of the present application can be deployed on a wearable device for execution, or on multiple wearable devices located in one place for execution, or on multiple wearable devices distributed in multiple places and interconnected through a communication network for execution, and the multiple wearable devices distributed in multiple places and interconnected through a communication network can constitute a block chain system.

[0192] Those skilled in the art should be aware that, in the above one or more examples, the functions described in the embodiments of the present application can be implemented in hardware, software, firmware or any combination thereof. When implemented in software, the functions can be stored in a computer readable medium or transmitted as one or more instructions or code on the computer readable medium. The computer readable medium includes computer storage medium and communication medium, and the communication medium includes any medium that facilitates transfer of computer program from one place to another. The storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

[0193] The above merely provides the optional embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A communication method of application data, characterized by, The method is executed by a wearable device, the wearable device comprising a bridge module, a first system and a second system; the method comprising: when the first system obtains first application data of a first application in the first system, processing the first application data through the bridge module, and synchronizing the processed first application data to the second system; and / or, when the second system obtains second application data of a second application in the second system, processing the second application data through the bridge module, and synchronizing the processed second application data to the first system.

2. The method of claim 1, wherein, The first processor is configured to run the first system, and the second processor is configured to run the second system. The processing of the first application data through the bridge module and the synchronization of the processed first application data to the second system comprise: determining a business type corresponding to the first application; based on the business type, determining a communication mode matching the business type; the first system sends the first application data to the bridge module through the communication mode, processes the first application data through the bridge module, and synchronizes the processed first application data to the second system through a dual-core communication channel between the first processor and the second processor; and / or, The processing of the second application data through the bridge module and the synchronization of the processed second application data to the first system comprise: obtaining the second application data through a dual-core communication channel between the first processor and the second processor; processing the second application data through the bridge module; determining a business type corresponding to the second application; based on the business type, determining a communication mode matching the business type; synchronizing the processed second application data to the first system through the communication mode.

3. The method according to claim 1 or 2, characterized in that, The processing of the first application data through the bridge module comprises: converting the data format of the first application data from a first format to a second format through the bridge module, wherein the processed first application data comprises first application data in the second format; and / or, The processing of the second application data through the bridge module comprises: converting the data format of the second application data from a third format to a fourth format through the bridge module, wherein the processed second application data comprises second application data in the fourth format.

4. The method of claim 1, wherein, The bridge module is an independent process in the first system, or the bridge module is attached to other processes in the first system; and / or, the bridge module is an independent process in the second system, or the bridge module is attached to other processes in the second system.

5. The method of claim 1, wherein, The first processor is configured to run the first system, and the second processor is configured to run the second system, and the bridge module is deployed in the first processor and / or the second processor.

6. The method of claim 1, wherein, Part or all of the first system application is different from part or all of the second system application in data format; wherein the data format of the first application data before being processed by the bridge module is not adapted to the second system, and / or the data format of the second application data before being processed by the bridge module is not adapted to the first system.

7. The method of claim 1, wherein, The first processor is used to run the first system, the second processor is used to run the second system, and the bridge module is deployed in the third processor; The third processor is connected with the first processor and the second processor through respective dual-core communication channels; or, The third processor is connected with the first processor through a dual-core communication channel of both sides, and the first processor and the second processor are connected through a dual-core communication channel of both sides; or, The third processor is connected with the second processor through a dual-core communication channel of both sides, and the first processor and the second processor are connected through a dual-core communication channel of both sides.

8. The method of claim 2, wherein, The service type includes one or more of the following: notification type, watch face type, widget type, contact data type, and lock screen state type; The communication mode includes a communication interface and / or broadcast communication; The determination of the communication mode matching the service type based on the service type includes: In the case that the service type is the notification type, the communication mode is determined to be the communication interface; and / or, In the case that the service type is the lock screen type, the communication mode is determined to be the broadcast communication.

9. The method of claim 1, wherein, The first application includes one or more of the following: a native system application of a first system, a native independent application, and a third-party independent application; and / or, the second application includes one or more of the following: a system application of the second system, a first-party independent application, and a third-party independent application.

10. The method of claim 1, wherein, The first application includes third application data, the data format of the third application data is adapted to the first system and also adapted to the second system, and the method further includes: Synchronizing the third application data to the second system through the bridge module.

11. The method of claim 1, wherein, The power consumption of the first system is greater than that of the second system; and / or, the performance of the first system is higher than that of the second system.

12. The method of claim 11, wherein, The method further includes: Displaying a system interface of the first system through the bridge module; and / or, Displaying a system interface of the second system through the bridge module.

13. A communication apparatus for applying data, characterized by The device is deployed in a wearable device, the wearable device includes a bridge module, a first system, and a second system; the device includes: A first synchronization module is configured to, when the first system obtains first application data of a first application in the first system, process the first application data through the bridge module, and synchronize the processed first application data to the second system; and / or, A second synchronization module is configured to, when the second system obtains second application data of a second application in the second system, process the second application data through the bridge module, and synchronize the processed second application data to the first system.

14. A wearable device, comprising: The wearable device memory and processor; at least one program code is stored in the memory, the at least one program code is loaded and executed by the processor to realize the application data communication method as claimed in any one of claims 1 to 12.

15. A computer-readable storage medium, characterized in that, The storage medium stores at least one program code, and the at least one program code is loaded and executed by the processor to realize the application data communication method as claimed in any one of claims 1 to 12.

16. A computer program product, characterised in that, The computer program product stores at least one program code, and the at least one program code is used for being executed by the processor to realize the application data communication method as claimed in any one of claims 1 to 12.

Images