View update method, device, and storage medium

Abstract

The application provides a view updating method, device and storage medium, which are applied to a multi-system device including a main operating system and at least one slave operating system, a data sharing process is run in the main operating system, and the data sharing process stores data shared between an application in the main operating system and an application in the slave operating system; the method comprises the following steps: the data sharing process receives a shared data update notification sent by a first shared application, wherein the first shared application shares target data with a second shared application, the first shared application and the second shared application belong to different operating systems in the multi-system device, and the shared data update notification comprises updated target data; the data sharing process sends a trigger message to the second shared application, and the trigger message is used to trigger the second shared application to update a user interface view of the second shared application according to the updated target data. The technical solution can realize cross-operating system data sharing and UI view synchronous updating.

Description

Technical Field

[0001] This application relates to the field of data processing, and more particularly to view updating methods, devices, and storage media. Background Technology

[0002] Multi-system devices are designed to meet the diverse needs of users. They can run multiple operating systems, such as Android and Windows. Users can choose one operating system to use on a multi-system device according to their needs and habits.

[0003] Because multiple operating systems are independent systems, each operating system manages and processes data within its own system. The same data needs to be processed separately in different operating systems, resulting in inconsistent view presentation states for applications corresponding to the same data in different operating systems. Summary of the Invention

[0004] This application provides a view update method, device, and storage medium, which aim to achieve cross-operating system data sharing and synchronized updates of user interface (UI) views.

[0005] In a first aspect, a view update method is provided, applicable to a multi-system device, the multi-system device including multiple operating systems, the multiple operating systems including a main operating system and at least one slave operating system, the main operating system running a data sharing process, the data sharing process storing data shared between applications in the main operating system and applications in the slave operating system;

[0006] The method includes:

[0007] The data sharing process receives a shared data update notification sent by a first sharing application; wherein, the first sharing application and the second sharing application share target data, the first sharing application and the second sharing application belong to different operating systems in the multi-system device, the shared data update notification includes the updated target data, and the updated target data is obtained by the first sharing application updating the user interface view;

[0008] The data sharing process sends a trigger message to the second sharing application, which triggers the second sharing application to update its user interface view based on the updated target data.

[0009] In this technical solution, a data sharing process runs in the main operating system of a multi-system device containing multiple operating systems. The data sharing process stores data shared between applications in the multiple operating systems. After receiving a shared data update notification from a first sharing application, the data sharing process sends a trigger message to a second sharing application that shares the target data with the first sharing application. The trigger message is used to trigger the second sharing application to update its user interface view according to the updated target data. Since the first and second sharing applications belong to different operating systems in the multi-system device, the updated target data is obtained by the first sharing application updating its user interface view. By having the data sharing process running in the main operating system receive the data update notification from the first sharing application and send the trigger message to the second sharing application, the view presentation state corresponding to the updated user interface view of the second sharing application can be made consistent with the view presentation state corresponding to the user interface view of the first sharing application. This ensures that the view presentation states of applications sharing the same data in different operating systems are consistent, thereby achieving cross-operating system data sharing and synchronized UI view updates.

[0010] In conjunction with the first aspect, in one possible implementation, the data sharing process communicates with applications in the main operating system and applications in the slave operating system based on the Message Queuing Telemetry Transport (MQTT) protocol; the first sharing application and the second sharing application pre-subscribe to a target topic from the data sharing process; the data sharing process receives a shared data update notification sent by the first sharing application, including: the data sharing process receives a first publication message for the target topic sent by the first sharing application, the first publication message carrying the updated target data; the data sharing process sends a trigger message to the second sharing application, including: the data sharing process sends a second publication message for the target topic to the second sharing application, the second publication message carrying the updated target data.

[0011] The data sharing process and applications communicate based on the MQTT protocol, building a data channel for applications across operating systems.

[0012] In conjunction with the first aspect, in one possible implementation, the data sharing process stores data in the form of key-value pairs, and the target topic is the target key corresponding to the target data; after receiving the shared data update notification sent by the first sharing application, the data sharing process further includes: updating the value corresponding to the target key stored in the data sharing process to the updated target data.

[0013] The data sharing process stores data in key-value pairs, which can improve the read and write speed of data in the data sharing process. Using keys as topics in MQTT communication facilitates data change monitoring and event notification.

[0014] In conjunction with the first aspect, in one possible implementation, the data sharing process stores data in key-value pairs, where the target topic is the target key corresponding to the target data. Before the data sharing process receives the first publication message for the target topic sent by the first sharing application, the process further includes: the data sharing process receiving a message registration request sent by the target application, the message registration request carrying target data, and the target application being the first application to send the target data to the data sharing process; the data sharing process generating a target key corresponding to the target data and using the target key as the topic corresponding to the message registration request to obtain the target topic; and the data sharing process sending a first message registration response to the target application, the first message registration response carrying the target topic.

[0015] The data sharing process generates a key corresponding to the shared data based on the shared data carried in the message registration request, and uses the key corresponding to the shared data as the subject. This enables the management of data shared by applications in different operating systems and ensures the uniqueness of the shared data in the data sharing process.

[0016] In conjunction with the first aspect, in one possible implementation, the data sharing process generates a target key corresponding to the target data and uses the target key as the subject of the message registration request. After obtaining the target subject, the process further includes: the data sharing process receiving a message registration request sent by an application other than the target application, the message registration request carrying the target data; and the data sharing process sending a second message registration response to the other application, the second message registration response carrying the target subject.

[0017] When the data sharing process receives a message registration request from another application, it directly sends a topic to that application, which ensures the uniqueness of the shared data within the data sharing process.

[0018] In conjunction with the first aspect, in one possible implementation, a message processing middleware runs on the slave operating system, the message processing middleware communicates with the data sharing process based on a message queue telemetry transport protocol, and the second sharing application is an application on the slave operating system; the data sharing process sends a second publication message for the target topic to the second sharing application, including: the data sharing process sending the second publication message to the message processing middleware; the message processing middleware converting the second publication message into a third publication message, the third publication message being a publication message that the second sharing application can recognize and understand, the third publication message carrying the updated target data; and the message processing middleware sending the third publication message to the second sharing application.

[0019] By running a message processing middleware within the operating system, the middleware converts the publish messages sent by the data sharing process into publish messages that can be recognized and understood by the sharing applications within the operating system. This enables message compatibility between different operating systems and ensures that applications within the operating system correctly extract data from the host operating system.

[0020] In conjunction with the first aspect, in one possible implementation, the data sharing process maps the data stored in the data sharing process to the memory of the multi-system device based on memory mapping; after receiving the shared data update notification sent by the first sharing application, the data sharing process further includes: the data sharing process inserts the updated target data into the header of the cache space corresponding to the memory.

[0021] The data sharing process maps the data stored in the data sharing process to the memory of multiple system devices based on memory mapping, and inserts the updated shared data into the header of the corresponding cache space in memory, which can improve the access speed of the target data and thus improve system performance.

[0022] In a second aspect, a computer device is provided, including a memory and a processor, the memory being connected to the processor, the processor being configured to execute one or more computer programs stored in the memory, wherein, when executing the one or more computer programs, the processor causes the computer device to implement the view update method of the first aspect described above.

[0023] Thirdly, a computer-readable storage medium is provided, which stores a computer program, the computer program including program instructions, which, when executed by a processor, cause the processor to perform the view update method of the first aspect.

[0024] Fourthly, a multi-system device is provided, the multi-system device including multiple operating systems, the multiple operating systems including a master operating system and at least one slave operating system, the master operating system running a data sharing process, the data sharing process storing data shared between applications in the master operating system and applications in the slave operating system; the multi-system device is used to execute the view update method of the first aspect described above.

[0025] This application can achieve the following technical effects: Since the first shared application and the second shared application belong to different operating systems in a multi-system device, the updated target data is obtained by the first shared application updating the user interface view. By receiving the data update notification sent by the first shared application and sending a trigger message to the second shared application through the data sharing process running in the main operating system, the view presentation state corresponding to the updated user interface view of the second shared application can be consistent with the view presentation state corresponding to the user interface view of the first shared application. This ensures that the view presentation states of applications sharing the same data in different operating systems are consistent, thereby realizing cross-operating system data sharing and synchronized UI view updates. Attached Figure Description

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

[0027] Figure 1 This is a schematic diagram of the system composition of a multi-system device provided in an embodiment of this application;

[0028] Figure 2 A schematic flowchart illustrating a view update method provided in an embodiment of this application;

[0029] Figure 3 A flowchart illustrating another view update method provided in an embodiment of this application;

[0030] Figure 4 UI diagram of the application provided in the embodiments of this application;

[0031] Figure 5 This is a schematic diagram of the structure of a view update device provided in an embodiment of this application.

[0032] Figure 6 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0034] It should be noted that, unless there is a conflict, the various features in the embodiments of this application can be combined with each other, all of which are within the protection scope of this application. Furthermore, although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than the module division in the device or the order in the flowchart. Moreover, the terms "first," "second," and "third" used in this application do not limit the data or execution order, but only distinguish identical or similar items with essentially the same function and effect.

[0035] The technical solution of this application is used to realize cross-operating system data sharing and synchronized UI view updates. The technical solution of this application is applied to multi-system devices, which refers to devices containing multiple operating systems. For example, a multi-system device may contain two operating systems, such as Android and Windows, or Android and Linux.

[0036] In multi-system devices, multiple operating systems are typically independent, each storing, reading, writing, and processing data within its own system. In some scenarios, applications across multiple operating systems update their UI views based on the same data. When the data changes in one of these operating systems, because the data hasn't changed in the others, the UI views in those other operating systems don't match the actual data state, resulting in inconsistencies. For example, in a meeting scenario, application A in operating system A needs to determine whether to turn on lights, microphones, etc., based on meeting status data. This meeting status data indicates whether the meeting is on. The meeting application used for the meeting is deployed in operating system B. When the meeting status data changes in operating system B, because operating systems A and B independently manage and process their respective data, application A in operating system A cannot immediately detect the change in operating system B. Consequently, the UI views related to the meeting status data in application A remain the UI views corresponding to the previous meeting status data, which is inconsistent with the actual meeting status data.

[0037] In view of this, this application proposes a cross-operating system UI view update scheme. By setting up a data sharing process in the main operating system of a multi-system device containing multiple operating systems, the data sharing process stores data shared between applications in the multiple operating systems of the multi-system device. When the data of the application sharing the data is updated, it sends a data update notification to the data sharing process. The data sharing process sends trigger messages to other applications sharing the data, so that other applications update the UI view according to the updated data. The data sharing process builds a communication bridge between different cross-operating system applications sharing the data, enabling different cross-operating system applications corresponding to the shared data to perceive changes in the shared data in a timely manner, and thus update the UI view so that the presentation state of the UI view is consistent with the actual data, realizing cross-operating system data sharing and synchronous UI view updates.

[0038] For ease of understanding, the multi-system device of this application will be introduced first. See [link to relevant documentation]. Figure 1 , Figure 1 This is a schematic diagram of the system composition of the multi-system device provided in the embodiments of this application, such as... Figure 1 As shown, the multi-system device 10 includes multiple operating systems, including a master operating system 101 and at least one slave operating system 102. The master operating system 101 is the operating system that runs by default or with priority in the multi-system device 101. The master operating system 101 typically runs at the lower level of the multi-system device 10 and can be used to manage and schedule the hardware of the multi-system device 10. The master operating system 101 can be, for example, an Android system. The slave operating system 102 is an operating system that is connected to the multi-system device 10 through plug-in or external means, and runs on top of the master operating system 101. The slave operating system 102 can be, for example, a Windows system and / or a Linux system. It is understood that the number of slave operating systems 102 in the multi-system device 10 is not limited to one.

[0039] A data sharing process runs in the main operating system 101. This process stores data shared between applications in the main operating system 101 and applications in the slave operating system 102. This shared data can be read and written by applications in both the main and slave operating systems 101 and 102. The data sharing process acts as a communication bridge between applications in the main and slave operating systems 101, enabling bidirectional communication. When the target data stored in the data sharing process changes, the process notifies the applications sharing that data, causing them to update the corresponding UI view. This allows for synchronized updates of UI views across multiple applications on different operating systems when data is modified in one location.

[0040] In some embodiments, the data sharing process in the host operating system 101 can communicate with applications in the host operating system 101 and applications in the slave operating system 102 based on the MQTT protocol. Applications in the host operating system 101 and applications in the slave operating system 102 pre-register and subscribe to messages regarding shared data at the data sharing process. When the shared data changes, the data sharing process notifies the applications subscribed to the shared data by publishing messages, enabling the subscribed applications to update their corresponding UI views based on the updated shared data.

[0041] In some embodiments, a message processing middleware also runs in the slave operating system 102. The message processing middleware in the slave operating system 102 communicates with the data sharing process in the master operating system 101 based on the MQTT protocol. The message processing middleware in the slave operating system 102 is used to convert messages sent by the data sharing process in the master operating system 101 into a message format that the application in the slave operating system 102 can understand and recognize. The message processing middleware in the slave operating system 102 can uniformly receive messages sent by the data sharing process in the master operating system 101, convert the messages sent by the data sharing process in the master operating system 101 into messages that the application in the slave operating system 102 can understand and recognize, and then send the converted messages to the application in the slave operating system 102. The message processing middleware can also uniformly receive notifications sent by the application in the slave operating system 102 and send messages to the data sharing process in the master operating system 101 on behalf of the application in the slave operating system 102.

[0042] based on Figure 1 The multi-system device shown can implement the technical solution of this application. The technical solution of this application is described in detail below.

[0043] See Figure 2 , Figure 2 This is a flowchart illustrating a view update method provided in an embodiment of this application, as shown below. Figure 2 As shown, the method includes the following steps:

[0044] S201, The data sharing process in the multi-system device receives a shared data update notification sent by the first sharing application in the multi-system device.

[0045] Here, the first shared application and the second shared application in the multi-system device share target data, and the first and second shared applications belong to different operating systems in the multi-system device. When the first shared application belongs to the master operating system in the multi-system device, the second shared application belongs to the slave operating system in the multi-system device; when the first shared application belongs to the slave operating system in the multi-system device, the second shared application belongs to the master operating system in the multi-system device. When there is more than one slave operating system in the multi-system device, the first and second shared applications can also be applications in different slave operating systems.

[0046] The target data is the data shared between the first sharing application and the second sharing application, and the target data is stored in the data sharing process of multiple system devices.

[0047] The shared data update notification sent by the first sharing application includes the updated target data, which is obtained by the first sharing application from updating the user interface view. After obtaining the target data by updating the user interface view, the first sharing application can send the updated target data along with the shared data update notification to the data sharing process. The shared data update notification is used to notify the data sharing process to update the target data.

[0048] S202, the data sharing process in the multi-system device sends a trigger message to the second sharing application in the multi-system device. The trigger message is used to trigger the second sharing application to update the user interface view of the second sharing application according to the updated target data.

[0049] Here, the trigger message sent by the data sharing process to the second sharing application may carry the updated target data.

[0050] After receiving the trigger message, the second shared application can obtain the updated target data from the trigger message and update the user interface view of the second shared application according to the updated target data.

[0051] In addition to sending trigger messages to the second sharing application, the data sharing process can also send trigger messages to the third sharing application in the multi-system device, so that the third sharing application updates its user interface view according to the updated target data. The third sharing application is an application that shares target data with the first and second sharing applications, and the third sharing application and the first sharing application belong to the same operating system in the multi-system device.

[0052] Similarly, the trigger message sent by the data sharing process to the third-party sharing application can carry the updated target data. Upon receiving the trigger message, the third-party sharing application can retrieve the updated target data from it and update its user interface view accordingly. In this way, when data shared by multiple applications on different operating systems is updated due to a UI view update in an application on one operating system, the UI views of the multiple applications on different operating systems can be updated synchronously.

[0053] In the above Figure 2 In the corresponding technical solution, a data sharing process runs in the main operating system of a multi-system device containing multiple operating systems. The data sharing process stores data shared between applications in multiple operating systems. After receiving a shared data update notification from a first sharing application, the data sharing process sends a trigger message to a second sharing application that shares the target data with the first sharing application. The trigger message is used to trigger the second sharing application to update its user interface view according to the updated target data. Since the first and second sharing applications belong to different operating systems in the multi-system device, the updated target data is obtained by the first sharing application updating its user interface view. By receiving the data update notification from the first sharing application and sending the trigger message to the second sharing application through the data sharing process running in the main operating system, the view presentation state corresponding to the updated user interface view of the second sharing application can be made consistent with the view presentation state corresponding to the user interface view of the first sharing application. This ensures that the view presentation states of applications sharing the same data in different operating systems are consistent, thereby achieving cross-operating system data sharing and synchronized UI view updates.

[0054] In some possible scenarios, the data sharing process uses memory mapping to map data stored within the process to the memory of multiple system devices. Memory mapping, a memory management technique, allows the operating system and applications to map data into the virtual address space of a process, enabling them to access the data directly by accessing virtual addresses. Upon receiving a shared data update notification from the first sharing application, the data sharing process can also insert the updated target data into the head of the corresponding cache space in the memory of the multiple system devices. Inserting the updated target data into the head of the cache space in the memory of the multiple system devices refers to inserting the updated target data into the head of the linked list corresponding to the cache space in the memory of the multiple system devices. By using memory mapping to map data stored within the data sharing process to the memory of multiple system devices and inserting the updated shared data into the head of the corresponding cache space, the data sharing process can improve the access speed of the target data, thereby enhancing system performance.

[0055] In some possible scenarios, the data-sharing process in the host operating system stores data in key-value pairs, and the data-sharing process communicates with applications in both the host and slave operating systems based on the MQTT protocol. See also Figure 3 , Figure 3 A flowchart illustrating another view update method provided in this application embodiment is shown below. Figure 3 As shown, the method includes the following steps:

[0056] S301, the first sharing application updates the user interface view of the first sharing application to obtain the updated target data.

[0057] S302, the first sharing application sends a first publication message for the target topic to the data sharing process. The first publication message carries the updated target data, and the data sharing process receives the first publication message.

[0058] Here, the target subject is the target key corresponding to the target data. The target key corresponding to the target data is used to uniquely identify the target data in the data sharing process.

[0059] In addition to carrying the updated target data, the first release message also carries a target key, indicating that the updated target data belongs to the target topic. After receiving the first release message, the data sharing process can determine that the topic of the first release message is the target topic based on the target key carried in the first release message, and then notify the applications subscribed to the target topic to update the target data.

[0060] In the case where the first sharing application is an application from the operating system, the first sharing application can send a first publication message for the target topic to the data sharing process through the message processing middleware from the operating system.

[0061] S303, the data sharing process updates the value corresponding to the target key stored in the data sharing process to the updated target data.

[0062] S304, the data sharing process sends a second publication message for the target topic to the second sharing application. The second publication message carries the updated target data, and the second sharing application receives the second publication message.

[0063] Here, the second sharing application is an application that has pre-subscribed to the target topic from the data sharing process. In addition to carrying the updated target data, the second publishing message also carries a target key corresponding to the target data, indicating that the updated target data is data under the target topic. After receiving the second publishing message, the second sharing application can determine that the topic of the second publishing message is the target topic based on the target key carried in the second publishing message, and thus determine that the data carried in the second publishing message is the updated target data.

[0064] In the case where the second sharing application is the main operating system, the data sharing process can directly send a second release message for the target topic to the second sharing application.

[0065] When the second sharing application is an application within the operating system, the data sharing process can directly send a second publication message for a target topic to the second sharing application; alternatively, it can send the second publication message for a target topic to the second sharing application through a message processing middleware within the operating system, specifically including the following steps A1-A3:

[0066] A1. The data sharing process sends a second published message to the message processing middleware.

[0067] A2. The message processing middleware converts the second published message into a third published message.

[0068] Here, the third publishing message is a publishing message that the second sharing application can recognize and understand, and the third publishing message carries updated target data.

[0069] The message processing middleware can parse the updated target data and target key from the second published message, encapsulate the parsed updated target data and target key into a message format that can be understood by applications in the operating system, and obtain the third published message.

[0070] A3. The message processing middleware sends a third publication message to the second sharing application, and the second sharing application receives the third publication message.

[0071] By running a message processing middleware within the operating system, the middleware converts the publish messages sent by the data sharing process into publish messages that can be recognized and understood by the sharing applications within the operating system. This enables message compatibility between different operating systems and ensures that applications within the operating system correctly extract data from the host operating system.

[0072] S305, the second shared application updates the user interface view of the second shared application based on the updated target data.

[0073] In the above Figure 3 In the technical solution, the data sharing process stores data in the form of key-value pairs, which can improve the read and write speed of data in the data sharing process; the data sharing process and the application communicate based on the MQTT protocol to build a cross-operating system application data channel, using the key as the subject in the MQTT communication, which facilitates data change monitoring and event notification.

[0074] The following is a specific example to illustrate the above. Figure 3 The corresponding technical solution is explained below. Assume a multi-system device includes operating system A and operating system B. Operating system A deploys application A, and operating system B deploys a conferencing application. The conferencing application is used for remote conferencing, online collaboration, etc. The conferencing application includes conferencing status data, which indicates whether the meeting is in progress. When the meeting has not started, the UI view of the conferencing application is as follows: Figure 4 As shown in J1, the view element s1 in the UI view shown in J1 is a view element related to meeting status data; Application A is a hardware management application used to manage devices such as lights and microphones in the meeting room. One function of Application A is to automatically turn on the lights and microphones when the meeting starts and automatically turn them off when the meeting ends. Before the meeting starts, the user uses operating system A and opens application A. The UI view of application A is as follows: Figure 4 As shown in J2, view elements s2 and s3 in the UI view shown in J2 are view elements related to meeting status data. When a user switches from operating system A to operating system B, opens the meeting application, and starts a meeting, the UI view corresponding to the meeting application is as follows: Figure 4 As shown in J3, when the meeting status data changes, the meeting application sends a first release message to the data sharing process in the multi-system device. The first release message carries the key corresponding to the meeting status data and the changed meeting status data. The data sharing process sends a second release message to application A. The second release message carries the key corresponding to the meeting status data and the changed meeting status data. After receiving the second release message, application A determines that the meeting status data has changed based on the key corresponding to the meeting status data, and updates the UI view J2 according to the changed meeting status data to obtain the UI view J4.

[0075] Before the data sharing process interacts with the application sharing the target data by publishing messages, the application sharing the target data needs to register a message for the target data with the data sharing process. Prior to step S302 above, the data sharing process can also execute the following steps B1-B5:

[0076] B1. The data sharing process receives a registration request message sent by the target application.

[0077] Here, the target application is the first application to send the target data to the data sharing process. The target application can be an application in the master operating system or an application in the slave operating system. The message registration request sent by the target application carries the target data and is used to request the registration of a topic for the target data to achieve target data sharing.

[0078] B2. The data sharing process generates a target key corresponding to the target data and uses the target key as the subject corresponding to the message registration request to obtain the target subject.

[0079] B3. The data sharing process sends the first message registration response to the target application.

[0080] Here, the first message registration response represents the data sharing process's response to the message registration request sent by the target application. The first message registration response indicates successful registration of the target data's topic and carries the target topic.

[0081] In steps B1-B3 above, the data sharing process generates a key corresponding to the shared data based on the shared data carried in the message registration request, and uses the key corresponding to the shared data as the subject. This enables the management of data shared by applications in different operating systems and ensures the uniqueness of the shared data in the data sharing process.

[0082] B4. The data sharing process receives message registration requests from applications other than the target application.

[0083] Here, the message registration request sent by applications other than the target application carries the target data. The message registration request sent by applications other than the target application is used to request the registration of a topic for the target data in order to achieve target data sharing.

[0084] B5. The data sharing process sends a second message to applications other than the target application to register the response.

[0085] Here, the second message registration response is used to represent the response of the data sharing process to a message registration request sent by an application other than the target application. The second message registration response is used to indicate that the subject of the target data has been registered, and the second message registration response carries the target subject.

[0086] In steps B4-B5 above, when the data sharing process receives a message registration request from another application, it directly sends a topic to that application, which ensures the uniqueness of the shared data in the data sharing process.

[0087] The method of this application has been described above; the apparatus of this application will be described below.

[0088] See Figure 5 , Figure 5 This is a schematic diagram of a view update device provided in an embodiment of this application, applied to a multi-system device. The multi-system device includes multiple operating systems, including a main operating system and at least one slave operating system. A data sharing process runs in the main operating system, storing data shared between applications in the main operating system and applications in the slave operating system. Figure 5 As shown, the view update device 40 includes:

[0089] The receiving module 401 is used to receive a shared data update notification sent by the first sharing application; wherein the first sharing application and the second sharing application share target data, the first sharing application and the second sharing application belong to different operating systems in the multi-system device, the shared data update notification includes the updated target data, and the updated target data is obtained by the first sharing application updating the user interface view;

[0090] The sending module 402 is used to send a trigger message to the second sharing application, the trigger message being used to trigger the second sharing application to update the user interface view of the second sharing application according to the updated target data.

[0091] It should be noted that the view update device 40 described above can execute the view update method provided in the embodiments of this application, and has the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in the embodiments of the view update device 40 can be found in the view update method provided in the embodiments of this application.

[0092] See Figure 6 , Figure 6 This is a schematic diagram of the structure of a computer device 50 provided in an embodiment of this application. The computer device 50 includes a processor 501 and a memory 502. The memory 502 is connected to the processor 501, for example, via a bus.

[0093] Processor 501 is configured to support the computer device 50 in performing the corresponding functions in the methods described in the above method embodiments. Processor 501 may be a central processing unit (CPU), a network processor (NP), a hardware chip, or any combination thereof. The aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The aforementioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0094] Memory 502 is used to store program code, etc. Memory 502 may include volatile memory (VM), such as random access memory (RAM); memory 502 may also include non-volatile memory (NVM), such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); memory 502 may also include combinations of the above types of memory.

[0095] The memory 502 is used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the view update method in the embodiments of this application. The processor executes various functional applications and data processing of the view update method by running the non-volatile software programs, instructions, and modules stored in the memory, thereby realizing the function of the view update method provided in the above method embodiments.

[0096] Memory 502 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and applications required for at least one function. The data storage area may store data created based on the use of the view update device. In some embodiments, the memory may include memory remotely located relative to the processor, which may be connected to the view update device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0097] The one or more modules are stored in the memory. When executed by the one or more processors, they perform the view update method in any of the above method embodiments. For example, they perform the method steps described in the above method embodiments to realize the functions of the modules described in the above device embodiments.

[0098] This application also provides a computer-readable storage medium storing a computer program, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the method described in the foregoing embodiments.

[0099] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0100] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A view update method, characterized in that, Applied to multi-system devices, the multi-system devices include multiple operating systems, the multiple operating systems include a main operating system and at least one slave operating system, the main operating system runs a data sharing process, the data sharing process stores data shared between applications in the main operating system and applications in the slave operating system; The method includes: The data sharing process receives a shared data update notification sent by a first sharing application; wherein, the first sharing application and the second sharing application share target data, the first sharing application and the second sharing application belong to different operating systems in the multi-system device, the shared data update notification includes the updated target data, and the updated target data is obtained by the first sharing application updating the user interface view; The data sharing process sends a trigger message to the second sharing application, which triggers the second sharing application to update its user interface view based on the updated target data.

2. The method according to claim 1, characterized in that, The data sharing process communicates with applications in the main operating system and applications in the slave operating system based on a message queue telemetry transport protocol; the first sharing application and the second sharing application subscribe to target topics in advance from the data sharing process; The data sharing process receives a shared data update notification sent by the first sharing application, including: The data sharing process receives a first publishing message for the target topic sent by the first sharing application, the first publishing message carrying the updated target data; The data sharing process sends a trigger message to the second sharing application, including: The data sharing process sends a second publication message to the second sharing application for the target topic, the second publication message carrying the updated target data.

3. The method according to claim 2, characterized in that, The data sharing process stores data in the form of key-value pairs, and the target topic is the target key corresponding to the target data; After receiving the shared data update notification sent by the first sharing application, the data sharing process further includes: The data sharing process updates the value corresponding to the target key stored in the data sharing process to the updated target data.

4. The method according to claim 2, characterized in that, The data sharing process stores data in key-value pairs, where the target topic is the target key corresponding to the target data; before receiving the first publication message for the target topic sent by the first sharing application, the data sharing process further includes: The data sharing process receives a message registration request sent by the target application, the message registration request carrying target data, and the target application is the first application to send the target data to the data sharing process. The data sharing process generates a target key corresponding to the target data, and uses the target key as the topic corresponding to the message registration request to obtain the target topic; The data sharing process sends a first message registration response to the target application, the first message registration response carrying the target topic.

5. The method according to claim 4, characterized in that, The data sharing process generates a target key corresponding to the target data and uses the target key as the topic corresponding to the message registration request. After obtaining the target topic, the process further includes: The data sharing process receives a message registration request sent by an application other than the target application, and the message registration request carries the target data. The data sharing process sends a second message registration response to the other applications, the second message registration response carrying the target topic.

6. The method according to claim 2, characterized in that, The operating system runs a message processing middleware, which communicates with the data sharing process based on the message queue telemetry transmission protocol. The second shared application is an application of the operating system. The data sharing process sends a second publication message for the target topic to the second sharing application, including: The data sharing process sends the second publish message to the message processing middleware; The message processing middleware converts the second publishing message into a third publishing message, which is a publishing message that the second sharing application can recognize and understand, and carries the updated target data. The message processing middleware sends the third publishing message to the second sharing application.

7. The method according to any one of claims 1-6, characterized in that, The data sharing process maps the data stored in the data sharing process to the memory of the multi-system device based on memory mapping; After receiving the shared data update notification sent by the first sharing application, the data sharing process further includes: The data sharing process inserts the updated target data into the header of the cache space corresponding to the memory.

8. A computer device, characterized in that, The device includes a memory and a processor, the memory being connected to the processor, the processor being configured to execute one or more computer programs stored in the memory, the processor causing the computer device to perform the method as described in any one of claims 1-7 when executing the one or more computer programs.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform the method as described in any one of claims 1-7.

10. A multi-system device, characterized in that, The multi-system device includes multiple operating systems, including a master operating system and at least one slave operating system. A data sharing process runs in the master operating system, and the data sharing process stores data shared between applications in the master operating system and applications in the slave operating system. The multi-system device is used to perform the method as described in any one of claims 1-7.

Images