Content display method and device, electronic equipment, storage medium and vehicle

Abstract

The invention relates to the field of data processing, and provides a content display method and device, electronic equipment, a storage medium and a vehicle. When a mode switching operation is monitored, a target mode management module corresponding to the mode switching operation outputs a mode switching instruction; the target mode processing module obtains a mode switching instruction and sends an updating instruction to all components stored in the target mode processing module; and for each component, determining that an update instruction is received, and determining and displaying target display content according to the update instruction. When a user changes the mode in the application, the target mode management module can monitor and update the desktop component through the target mode processing module, that is, synchronous update of the desktop component and the application is realized, and the user experience is improved. Meanwhile, when the desktop components are updated, all the desktop components related to the changed mode can be updated, the tedious operation that multiple desktop components need to be updated when a user manually updates the desktop components is reduced, and the user experience is improved.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the field of data processing, and particularly relates to a content display method and device, electronic equipment, storage medium and vehicle. BACKGROUND

[0002] In current vehicle-mounted systems, the desktop Widget card adopts a static content display mode. When the display mode within an application changes, only the display content within the application changes with the display mode, while the desktop Widget card remains unchanged, which cannot meet the user's needs. SUMMARY

[0003] Therefore, the present disclosure aims to provide a content display method, device, electronic equipment, storage medium and vehicle to solve the problem that when the display mode within an application changes, only the display content within the application changes with the display mode, while the desktop Widget card remains unchanged, which cannot meet the user's needs.

[0004] To achieve the above purpose, a first aspect of the present disclosure provides a content display method, which comprises: monitoring a mode switching operation, wherein the mode switching operation corresponds to a target mode management module outputting a mode switching instruction; a target mode processing module acquires the mode switching instruction and sends an update instruction to all components stored in the target mode processing module; for each component, determining that the update instruction is received, determining and displaying target display content according to the update instruction.

[0005] In some embodiments, before monitoring the mode switching operation, the method further comprises: initializing the target mode processing module, wherein the target mode processing module calls an interface creation class of the target mode management module; registering a callback interface in the target mode management module through the interface creation class.

[0006] In some embodiments, the monitoring of the mode switching operation, wherein the mode switching operation corresponds to the target mode management module outputting the mode switching instruction, comprises: monitoring a mode state through the callback interface; in response to monitoring that the mode state changes through the callback interface, determining that there is a mode switching operation, and the target mode management module outputs the mode switching instruction.

[0007] Through the above scheme, the target mode processing module is registered in the target management module through the callback interface, and the state change is acquired in real time through the callback interface. That is, when the target management module detects the mode switching operation, the target mode processing module is notified, and the direct function callback in the process is used. The direct function call is a CPU instruction level jump, without message packaging, queue, and traversal, and the time consumption is only nanoseconds. Compared with the system broadcast (Broadcast) mode using cross-component communication, the broadcast delay time is reduced, and great advantages are achieved in efficiency, real-time performance, reliability, and power consumption.

[0008] In some embodiments, for each component, determining that the update instruction is received, determining and displaying target display content according to the update instruction comprises: For each component, in response to receiving the update instruction, determining the target mode corresponding to the update instruction, obtaining the target display content corresponding to the target mode, and associating the target display content with the component name of the component; The component management module obtains the target display content corresponding to the component name according to the component name corresponding to each component, calls the remote view class to refresh the interface, and displays the target display content.

[0009] Through the above scheme, the target display content is obtained, and the target display content is associated with the component name. Then, the component management module can directly determine the target display content according to the component name, and the target display content is more accurate.

[0010] In some embodiments, before the mode switching operation is monitored, the method further comprises: Receiving a storage instruction, wherein the storage instruction includes the component name of the component; The storage instruction is encapsulated by the encapsulation component to obtain a first encapsulation instruction; The component name of the component in the first encapsulation instruction is stored in the target mode processing module by calling an enqueue instruction by the encapsulation component.

[0011] In some embodiments, the first encapsulation instruction is added to the processing queue by calling the enqueue instruction by the encapsulation component, and the first encapsulation instruction is forwarded to the component management module. The first encapsulation instruction is added to the processing queue by calling the enqueue instruction by the encapsulation component, and the first encapsulation instruction is forwarded to the component management module. The component management module receives the first encapsulation instruction and forwards the first encapsulation instruction to the target mode processing module. The target mode processing module receives the first packaging instruction, parses the first packaging instruction, obtains and stores the component name of the component.

[0012] Based on the same inventive concept, a second aspect of the present disclosure provides a content display device, comprising: A monitoring module configured to monitor a mode switching operation, wherein the mode switching operation corresponds to a target mode management module outputting a mode switching instruction; A sending module configured to, when the target mode processing module obtains the mode switching instruction, send an update instruction to all components stored in the target mode processing module; A display module configured to, for each component, determine that the update instruction is received, and determine and display target display content according to the update instruction.

[0013] Based on the same inventive concept, a third aspect of the present disclosure provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the content display method as described above when executing the computer program.

[0014] Based on the same inventive concept, a fourth aspect of the present disclosure provides a non-transitory computer readable storage medium, which stores computer instructions for causing a computer to execute the content display method as described above.

[0015] Based on the same inventive concept, a fifth aspect of the present disclosure provides a vehicle, comprising the content display device of the second aspect, the electronic device of the third aspect, or the storage medium of the fourth aspect.

[0016] It can be seen from the above that the present disclosure proposes a content display method, device, electronic equipment, storage medium and vehicle. When the mode switching operation is monitored, it indicates that the user has performed mode switching. The target mode management module outputs a mode switching instruction corresponding to the mode switching operation to prompt other modules that the user needs to perform mode switching. The target mode processing module obtains the mode switching instruction, and sends an update instruction to all components stored in the target mode processing module at this time. That is, at least one component is stored in each target mode processing module, and the stored component is the component corresponding to the mode. For each component, when receiving the update instruction sent by the target mode processing module, the target display content is determined according to the update instruction, and the current display content is updated by using the target display content. That is, when the user changes the mode in the application, the target mode management module can be listened to, and the update of the desktop component can be realized by the target mode processing module, that is, the synchronous update of the desktop component and the application is realized, and the user experience is improved. At the same time, when the desktop component is updated, the target mode processing module can realize the update of all desktop components related to the changed mode, which reduces the cumbersome operation that the user needs to update multiple desktop components one by one when manually updating, and improves the user experience. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the present disclosure or the related art, the following will briefly introduce the drawings needed to be used in the embodiments or related art descriptions. Obviously, the drawings in the following description are only embodiments of the present disclosure, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0018] Figure 1 The flowchart of the content display method of the embodiment of the present disclosure; Figure 2 The flowchart of the content display method of another embodiment of the present disclosure; Figure 3 The structural block diagram of the content display device of the embodiment of the present disclosure; Figure 4 The structural schematic diagram of the electronic equipment of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0019] In order to make the purpose, technical solutions and advantages of the present disclosure more clear, the following will further describe the present disclosure in combination with specific embodiments and with reference to the drawings.

[0020] It should be noted that, unless otherwise defined, technical terms or scientific terms used in the embodiments of the present disclosure shall have the common meaning understood by one of ordinary skill in the art to which the present disclosure belongs. The terms "first", "second" and similar terms used in the embodiments of the present disclosure do not denote any order, quantity or importance, but are used to distinguish different components. The terms "include", "contain" and similar terms mean that the elements or objects before the terms encompass the elements or objects listed after the terms and their equivalents, and do not exclude other elements or objects. The terms "connect" or "connected" and similar terms are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. The terms "upper", "lower", "left", "right" and the like are only used to represent relative positional relationships, and when the absolute positions of the described objects are changed, the relative positional relationships can also be changed accordingly.

[0021] The terms involved in the present disclosure are explained as follows: Widget: Widget is a reusable data block, which is a small piece of code that can be executed on any Hyper Text Markup Language (HTML) based Internet (Web) page, and users can achieve personalized Web pages or applications through aggregation assembly. The manifestation of Widget can be video, map, news, small game and the like, and some dynamic content can be added to an HTML based Web page. Widget can also be a click counter or real-time stock information and the like. Generally, the functions of a Widget are realized by third-party provided code, and Web developers only need to embed these code blocks into their own pages.

[0022] Launcher desktop: Launcher desktop is the main screen process of the Android system, which runs as AppWidgetHost, and is responsible for hosting and rendering all application icons, folders, wallpapers and desktop widgets. It receives RemoteViews instructions issued by AppWidgetManagerService through Binder, parses them into actual View trees in the main thread and draws them to the screen, realizing cross-process, secure and efficient UI update.

[0023] A widget is a reusable piece of data that is a small block of code that can be executed on any Hyper Text Markup Language (HTML) based Internet (Web) page, and users can assemble personalized Web pages or applications by aggregation. The widget can be a video, a map, a news, a small game, etc., and can add some dynamic content to an HTML based Web page. The widget can also be a click counter or real-time stock information, etc. Usually, the function of a widget is implemented by third-party provided code, and a Web developer only needs to embed these code blocks into his own page.

[0024] In the current vehicle-mounted system, the desktop widget card adopts a static content display mode. When the display mode in the application changes, only the display content in the application changes with the display mode, and the desktop widget card remains unchanged.

[0025] For example, if a user manually switches to a child mode in a video application, the desktop widget content remains unchanged and still displays widget content such as a wind chart and popular videos, which are not suitable for children to watch. When adjusting, the user needs to manually delete irrelevant widget content and add child-specific widget cards. That is, the user needs to perform dual operations of switching modes in the application and managing desktop components, which is fragmented and cumbersome.

[0026] At the same time, the current desktop widget cards are independently managed, which can easily cause inconsistent display content and cannot guarantee content consistency and synchronization.

[0027] That is, the traditional widget system lacks a linkage mechanism with the internal state of the host application, and the widget content update depends on external triggering or timed refreshing, which cannot perceive real-time changes in user behavior state in the application, and lacks unified state management. Therefore, the embodiment proposes a content display method as shown in Figure 1 The method comprises the following steps: Step 101, a mode switching operation is monitored, and a mode switching instruction is output by a target mode management module corresponding to the mode switching operation.

[0028] In a specific implementation, when the mode switching operation is monitored, it indicates that the user selects to switch modes in the application. The target mode management module corresponding to the mode switching operation outputs a mode switching instruction. The target mode management module corresponding to the mode switching operation is the mode management module corresponding to the mode after switching.

[0029] In this embodiment, when the target mode is the child mode, the child mode management module ChildModeManager is the target mode management module.

[0030] That is, each mode corresponds to a mode management module. After monitoring the mode switching operation, the mode switching operation corresponding switched mode is determined. The switched mode is used as the target mode, and the mode management module corresponding to the target mode is the target mode management module.

[0031] For example, when the user's mode switching operation is monitored, it is determined that the mode switching operation is switched to the child mode. At this time, the switched mode is the child mode, that is, the target mode is the child mode, and the child mode management module corresponding to the child mode is determined as the target mode management module.

[0032] In this embodiment, when monitoring the mode switching operation, it can be determined whether there is a mode switching operation according to the user's behavior, which specifically includes: If the user's touch operation on the mode switching button is received, it is determined that the mode switching operation is monitored. The mode switching button can include physical buttons and virtual buttons according to the scene. For example, if the current scene is the in-vehicle scene, the mode switching button can be a physical button in the vehicle, or a virtual button on the vehicle screen. Another example, if the current scene is the electronic device scene, the mode switching button is a virtual button on the electronic device.

[0033] If the user outputs voice data containing mode switching requirements, it is determined that the mode switching operation is monitored. It can be understood that the received user voice data can be subjected to intent recognition to determine whether it contains mode switching requirements.

[0034] In this embodiment, the mode switching operation indicates switching from the current mode to another mode. For example, the mode switching operation can be switching between the normal mode, the child mode and the old age mode, or switching between the daytime mode and the nighttime mode, or switching between different driving modes. The above is only an example and is not limited.

[0035] In step 102, the target mode processing module obtains the mode switching instruction and sends an update instruction to all components stored in the target mode processing module.

[0036] In specific implementation, the target mode processing module stores at least one component. When the target mode processing module obtains the mode switching instruction, it sends an update instruction to all components stored in the target mode processing module, so that each component updates according to the update instruction, so that the display content of each component corresponds to the switched mode corresponding to the mode switching instruction.

[0037] In this embodiment, the mode processing module is a Repo module, i.e., a Repo warehouse, which can perform data refreshing, jumping, and updating according to instruction types. Based on the foregoing example, when the target mode is a child mode, the corresponding child mode processing module ChildModeRepo is the target mode processing module.

[0038] In this embodiment, the target mode processing module stores an accurate mapping table of all active Widget instance IDs, i.e., component names. When the target mode processing module receives a state change, the accurate mapping table is traversed to ensure that each running Widget component is refreshed, achieving a one-time switching and multiple Widget components simultaneously responding.

[0039] In step 103, for each component, it is determined that the update instruction is received, and target display content is determined and displayed according to the update instruction.

[0040] In specific implementation, for each component, when the component receives an update instruction, target display content is determined according to the update instruction. After the target display content is determined, the target display content is displayed on the display interface. The target display content is the content corresponding to the switched mode corresponding to the mode switching instruction.

[0041] Through the foregoing scheme, a mode switching operation is monitored, which indicates that the user performs mode switching. The target mode management module corresponding to the mode switching operation outputs a mode switching instruction to prompt other modules that the user needs to perform mode switching. The target mode processing module obtains the mode switching instruction, and at this time, sends an update instruction to all components stored in the target mode processing module, i.e., at least one component is stored in each target mode processing module, and the stored component is the component corresponding to the mode. For each component, when the update instruction sent by the target mode processing module is received, target display content is determined according to the update instruction, and the current display content is updated by using the target display content. That is, when the user changes the mode in the application, the target mode management module can be listened to, and the update of the desktop component can be implemented by the target mode processing module, i.e., the synchronous update of the desktop component and the application is implemented, and the user experience is improved. At the same time, when the desktop component is updated, the target mode processing module can update all desktop components related to the changed mode, reducing the cumbersome operation that the user can only update one desktop component at a time when manually updating, and improving the user experience.

[0042] In some embodiments, the callback interface can be pre-registered to monitor whether there is a mode switching operation, i.e., before the mode switching operation is monitored in step 101, the specific process further includes: Step A, initializing the target mode processing module, the target mode processing module calling the interface creation class of the target mode management module; Step B, registering the callback interface in the target mode management module through the interface creation class.

[0043] In implementation, the target mode processing module is initialized, and the target mode processing module calls the interface creation class of the target mode management module, where the interface creation class is used to implement the abstract method declared in the interface and provide specific function implementation.

[0044] The callback interface is registered in the target mode management module through the interface creation class, and the callback interface is the listener interface, so that the target mode processing module can be notified when the target mode management module monitors the mode switching through the callback interface.

[0045] After the target mode processing module registers the callback interface in the target mode management module, it can be determined whether there is a mode switching operation according to the callback interface, that is, the mode switching operation is monitored in step 101, and the target mode management module outputs a mode switching instruction corresponding to the mode switching operation, which specifically includes: Step 1011, monitoring the mode state through the callback interface; Step 1012, in response to monitoring that the mode state changes through the callback interface, determining that there is a mode switching operation, and the target mode management module outputs a mode switching instruction.

[0046] In implementation, because the target mode processing module registers the callback interface in the target mode management module, the mode state can be monitored through the callback interface, where the mode state is the mode state in the application, that is, the current mode in the application.

[0047] When the user performs mode switching in the application, the mode state change can be monitored through the callback interface, which indicates that there is a mode switching operation, and then the target mode management module outputs a mode switching instruction.

[0048] Hereinafter, the foregoing steps are exemplarily illustrated by taking the target mode processing module ChildModeRepo as an example, and the specific implementation is as follows: The target mode processing module is a ChildModeRepo module, and the target mode management module is a ChildModeManager module. The ChildModeRepo module is initialized, and an interface creation class of the ChildModeManager module is called, so that the ChildModeRepo module registers a callback interface, that is, a ChildModeChangeListener, in the ChildModeManager module through the interface creation class. When the ChildModeManager module detects a mode switching operation through the ChildModeChangeListener, the ChildModeRepo module can be notified, that is, a mode switching instruction is sent to the ChildModeRepo module.

[0049] In this embodiment, the target mode management module is a globally unique manager in an application process, which is the only real source for all components to obtain a current mode. When the target mode management module detects a state change, the target mode processing module can be actively and accurately driven to refresh the content of all existing Widget instances.

[0050] Through the above scheme, the target mode processing module registers a callback interface in the target management module, and the state change is obtained in real time through the callback interface. When the target management module detects a mode switching operation, the target mode processing module can be notified, and the direct function callback in the process is used. The direct function call is a CPU instruction level jump, without message packaging, queue, and traversal. The time consumption is only nanoseconds. Compared with the system broadcast (Broadcast) method using cross-component communication, the broadcast delay time is reduced, and great advantages are obtained in efficiency, real-time performance, reliability, and power consumption.

[0051] In some embodiments, for each component, when an update instruction sent by the target mode processing module is received, the corresponding target display content can be determined through the component name of the component, and then the target display content is displayed, that is, step 103 specifically includes: Step 1031, for each component, in response to receiving the update instruction, determining a target mode corresponding to the update instruction, obtaining target display content corresponding to the target mode, and associating the target display content with the component name of the component; Step 1032, the component management module obtains the target display content corresponding to the component name according to the component name corresponding to each component, calls a remote view class to refresh the interface, and displays the target display content.

[0052] In implementation, for each component, when an update instruction is received, a target mode corresponding to the update instruction is determined, wherein the target mode is a mode changed after a mode switching operation.

[0053] Target display content corresponding to the target mode is obtained, wherein the target display content can be preset display content. The determined target display content is associated with the component name of the component, and the target display content can be determined according to the component name of the component subsequently.

[0054] The component management module obtains target display content corresponding to the component name of each component, calls a remote view class to refresh the interface, and displays the target display content.

[0055] Specifically, the component management module is an AppWidgetManager module, the remote view class is a RemoteView class, the component name of the component is a widgetId, and when the display content of the display interface is updated, the corresponding target display content can be found according to the component name. The AppWidgetManager calls an onUpdate method, updates the view of the Widget through a RemoteViews object, and calls an AppWidgetManager.updateAppWidget method to apply the updated target display content to the Widget, so as to update the interface, that is, display the target display content on the Widget interface.

[0056] In this embodiment, the Widget is actually run in a system desktop process, and the data source is usually in an application process. RemoteViews encapsulates, transmits, and applies in batches through a three-step mechanism, packs the update instruction into a Parcelable Action list, performs an IPC operation (inter-process operation) to the remote process for execution, so as to avoid the security and synchronization problems of directly operating the View in another process.

[0057] Through the above scheme, the target display content is obtained, and the target display content is associated with the component name, so that the component management module can directly determine the target display content according to the component name subsequently, and the determination of the target display content is more accurate.

[0058] In some embodiments, after the target mode processing module obtains the mode switching instruction, all component sending update instructions stored in the target mode processing module, and the subsequent components need to determine the corresponding target display content according to the component name when updating, therefore, the component name of each component should be stored in the target mode processing module. That is, before the mode switching operation is monitored in step 101, the method further includes: Step 10A, receiving a storage instruction, wherein the storage instruction includes the component name of the component; Step 10B, encapsulating the storage instruction by the encapsulation component to obtain a first encapsulation instruction; Step 10C, calling an enqueue instruction by the encapsulation component, and storing the component name of the component in the first encapsulation instruction to the target mode processing module by using the enqueue instruction.

[0059] In specific implementation, a storage instruction is received, indicating that a new component name needs to be stored in the target mode processing module, wherein the storage instruction includes the component name of the component.

[0060] The storage instruction is encapsulated by the encapsulation component to obtain a first encapsulation instruction. The encapsulation component is a TransferKit component, which is responsible for serializing objects in the storage instruction into Json and encapsulating Intent or deserializing, and maintaining a unified protocol.

[0061] After the storage instruction is encapsulated by the TransferKit component to obtain the first encapsulation instruction, an enqueue instruction is called, and the component name of the component in the first encapsulation instruction is stored in the target mode processing module by using the enqueue instruction. The enqueue instruction is an enqueueRequest() method.

[0062] Specifically, the process of storing the component name of the component in the first encapsulation instruction in the target mode processing module by using the enqueue instruction includes: Step 10C1, calling the enqueue instruction by the encapsulation component, adding the first encapsulation instruction to the processing queue by using the enqueue instruction, and forwarding the first encapsulation instruction to the component management module; Step 10C2, receiving the first encapsulation instruction by the component management module, and forwarding the first encapsulation instruction to the target mode processing module; Step 10C3, receiving the first encapsulation instruction by the target mode processing module, analyzing the first encapsulation instruction, and obtaining and storing the component name of the component.

[0063] In implementation, the enqueue instruction is called by the packaging component to add the first packaging instruction to the processing queue. The enqueue instruction is an enqueueRequest() method, which is used to add a request to a queue for subsequent processing. The queue is a first-in-first-out (FIFO) data structure, and a newly added request waits for the previous request to be processed before being processed.

[0064] In this embodiment, the enqueueRequest() method is used to add the first packaging instruction to the processing queue, i.e., to add the first packaging instruction to the end of the processing queue, and forward the first packaging instruction to the component management module for resource allocation and execution. In this embodiment, the component management module is an AppWidgetManager module.

[0065] In this embodiment, the enqueueRequest() method is an asynchronous processing method, which can return immediately after adding the first packaging instruction to the processing queue, without waiting for the first packaging instruction to be processed, thereby avoiding blocking of the packaging component and improving the response speed of the system.

[0066] In response to the component management module receiving the first packaging instruction, the first packaging instruction is forwarded to the target mode processing module for subsequent analysis and storage of the component name in the first packaging instruction by the target mode processing module after receiving the first packaging instruction.

[0067] The target mode processing module receives the first packaging instruction, analyzes the first packaging instruction, obtains and stores the component name of the component, so that the corresponding target display content can be determined according to the component name when the component is updated, and the current display content of the component is updated using the target display content.

[0068] In this embodiment, when adding a Widget component, the method described in steps 10A to 10C can also be used, which specifically includes: The component addition instruction is received, indicating that the component name of the component to be added needs to be stored in the target mode processing module. The component addition instruction includes the component name of the component to be added. The component addition instruction is packaged by the packaging component to obtain a second packaging instruction. The packaging component is a TransferKit component, After the second encapsulation instruction is obtained by encapsulating the component addition instruction by using the TransferKit component, an enqueue instruction is called, the enqueue instruction is called by encapsulating the component, and the second encapsulation instruction is added to the processing queue by using the enqueue instruction. The enqueue instruction is an enqueueRequest() method.

[0069] In this example, the enqueueRequest() method is used to add the second encapsulation instruction to the processing queue, that is, the second encapsulation instruction is added to the end of the processing queue, and the second encapsulation instruction is forwarded to the component management module for waiting for the component management module to allocate resources for execution. In this embodiment, the component management module is an AppWidgetManager module.

[0070] In response to the component management module receiving the second encapsulation instruction, the second encapsulation instruction is forwarded to the target mode processing module, it is determined that the target mode processing module receives the second encapsulation instruction, the second encapsulation instruction is analyzed, and the component name of the component to be added is obtained and stored.

[0071] For the component to be added, when the update instruction is received, the target mode corresponding to the update instruction is determined, wherein the target mode is the mode changed after the mode switching operation. The target display content corresponding to the target mode is obtained, wherein the target display content can be a preset display content. The determined target display content is associated with the component name of the component to be added, and the target display content can be determined according to the component name of the component to be added in the future.

[0072] In this embodiment, the created RemoteView is refreshed to the Launcher desktop by calling the corresponding widgetId by using the AppWidgetManager. Specifically, the corresponding component name widgetId is called by using the AppWidgetManager, and the corresponding target display content can be found according to the component name. In the AppWidgetProvider, the data update logic of the Widget is defined by rewriting the onUpdate() method. At the same time, the layout and appearance of the Widget are designed by using the RemoteViews class, and the view of the Widget is updated by using the AppWidgetManager when needed. When the user adds the Widget to the home screen, the Launcher will notify the AppWidgetProvider of the application to update by using the broadcast mechanism, so as to ensure that the Widget can display the latest information in real time.

[0073] In this embodiment, to realize the change of the mode in the application by the user, the target mode management module can be listened to, and the update of the desktop component can be realized by the target mode processing module, that is, the synchronous update of the desktop component and the application in the application can be realized. A unified encapsulation and unified distribution method can be used to realize the distribution of the command of the desktop Widget component, so as to avoid the logical redundancy caused by the independent processing of the instruction and the data encapsulation of different desktop Widget components. The specific distribution method includes: Step a, monitoring the component trigger operation for the target component, and determining the target command corresponding to the target component.

[0074] In specific implementation, the target component is monitored in real time, and the target command corresponding to the component trigger operation is determined in response to monitoring the component trigger operation for the target component. The target command is the command corresponding to the target component, which indicates the operation triggered by the user for which component.

[0075] In this embodiment, the target command is the WidgetData data, which can specifically include configuration data, state data, metadata, or interaction data of the target component. The configuration information is used to define the behavior, appearance, and function of the target component.

[0076] In this embodiment, the component trigger operation for the target component is the operation behavior of the user for the target component, which can specifically include a click operation for the target component, a long press operation for the target component, or a sliding operation for the target component.

[0077] For example, for the Widget component on the current display interface, the click operation can be performed on the Widget component to realize the jump of the interface. The long press operation can be performed on the Widget component to realize the editing of the Widget component. Or the sliding operation can be performed on the Widget component to realize the refreshing of the interface.

[0078] For example, the target component is a recommended Widget component. When the user performs the click operation on the recommended Widget component, the component trigger operation of the target component is monitored, and the target command corresponding to the component trigger operation is determined, that is, the WidgetData data corresponding to the recommended Widget component is obtained. According to the WidgetData data, it can be known that the user clicks the recommended Widget component.

[0079] Step b, encapsulating the target command by the encapsulation component to obtain an encapsulation command, and forwarding the encapsulation command to the unified dispatcher.

[0080] In implementation, the target command is encapsulated by an encapsulation component to obtain an encapsulated command. In the embodiment, the encapsulation component is a TransferKit component, which is responsible for serializing a WidgetData object into a Json and encapsulating an Intent or deserializing, and maintaining a unified protocol. The TransferKit is a unified data protocol adaptation layer, so that different Widget types can share the same set of instruction structures and distribution channels, and has good system expansion capability and platform consistency guarantee.

[0081] After the target command is encapsulated by the TransferKit component to obtain the encapsulated command, the encapsulated command is forwarded to a unified dispatcher for subsequent unified distribution of the target command by the unified dispatcher.

[0082] Specifically, after monitoring that a user performs a component triggering operation on a target component, a target broadcast containing a target command is generated by triggering a PendingIntent according to the target command, where the target broadcast is a PendingIntent broadcast. In Android development, PendingIntent is a special Intent used to execute an operation at a specific time point or event trigger. PendingIntent can be used to start an Activity, a Service, or generate and send a broadcast.

[0083] The target broadcast is received by a component broadcast receiver, which is an AppWidgetProvider in the embodiment. The component broadcast receiver listens to lifecycle events and click broadcasts, i.e., PendingIntent broadcasts, and encapsulates the target command in the PendingIntent broadcast into a standard instruction by using an encapsulation component.

[0084] After receiving the target broadcast, the target broadcast is parsed by an encapsulation component, i.e., the target broadcast is parsed by a TransferKit component to obtain the target command contained in the target broadcast. The target command is encapsulated by the encapsulation component to obtain an encapsulated command. That is, the encapsulation is performed by the TransferKit component to obtain the encapsulated command.

[0085] The enqueue instruction is called by the encapsulation component, and the encapsulation command is added to the processing queue by using the enqueue instruction. In this embodiment, the enqueueRequest() method is used to add the encapsulation command to the processing queue, that is, the encapsulation command is added to the end of the processing queue, and the encapsulation command is forwarded to the component scheduling module for waiting for the component scheduling module to allocate resources for execution. In this embodiment, the component scheduling module is the WidgetDispatcherHelper module.

[0086] In response to the component scheduling module receiving the encapsulation command, the encapsulation command is forwarded to the unified dispatcher for subsequent allocation of the encapsulation command to the target processing module by the unified dispatcher, so that the target processing module performs the corresponding function of the encapsulation command after analyzing the encapsulation command.

[0087] Specifically, the component scheduling module is the WidgetDispatcherHelper module, and the component scheduling module adopts single-thread Executor asynchronous scheduling, that is, a single-thread thread pool is used to execute tasks asynchronously, and it is ensured that all tasks are executed in sequence in the same thread.

[0088] When the component scheduling module receives a plurality of encapsulation commands, the receiving time corresponding to each encapsulation command is determined, that is, the time when the component scheduling module receives the encapsulation command.

[0089] The component scheduling module traverses the receiving time corresponding to all encapsulation commands, compares the receiving time corresponding to all encapsulation commands, and sorts and processes in the order from early to late to obtain a target order. It can be understood that in this embodiment, the order from early to late means that the current time is determined, the difference between the current time and the receiving time is calculated, and the smaller the difference, the later the corresponding order. That is, the earlier the receiving time, the larger the corresponding difference, and the earlier the order in sorting.

[0090] The component scheduling module selects the encapsulation command with the earliest receiving time as the target encapsulation command according to the receiving time corresponding to each encapsulation command, that is, the encapsulation command at the front of the target order obtained by sorting the receiving time is selected as the target encapsulation command, and the target encapsulation command is forwarded to the unified dispatcher, wherein the unified dispatcher is the WidgetCommandDispatcher.

[0091] After the unified dispatcher receives the target encapsulation command, the target processing module is determined according to the command type corresponding to the target encapsulation command, and then the target encapsulation command is dispatched to the target processing module for analysis and execution of the corresponding function by the target processing module. At the same time, after the unified dispatcher dispatches the target encapsulation command to the target processing module, a dispatch completion instruction is returned.

[0092] When the component dispatching module receives the dispatch completion instruction sent by the unified dispatcher, it indicates that the unified dispatcher has completed the dispatch of the target packaging command. At this time, the component dispatching module reselects a new target packaging command from all the received packaging commands, except for the target packaging command, according to the receiving time of each packaging command, and forwards the new target packaging command to the unified dispatcher.

[0093] The above-mentioned selection and forwarding operation of the new target packaging command is repeated until all the packaging commands are forwarded to the unified dispatcher.

[0094] Step c, determining the command type corresponding to the packaging command by using the unified dispatcher, and dispatching the packaging command to the target processing module according to the command type.

[0095] In specific implementation, when the unified dispatcher receives the packaging command, the command type corresponding to the packaging command, wherein the command type corresponds to the packaging command, and the packaging command is obtained by packaging the target command, and the target command is the command corresponding to the target component, therefore, it can be known that the command type corresponds to the target component.

[0096] According to the command type, the packaging command is dispatched to the target processing module. The target processing module is the Repo module, which is a specific business processing module, which can perform data refreshing, jumping, updating and other operations according to the command type.

[0097] In the embodiment, the target processing module corresponds to the command type, and it is known from the foregoing that the command type corresponds to the target component, that is, the target processing module corresponds to the target component, and different target components correspond to different target processing modules.

[0098] In the embodiment, the command type corresponds to the component triggered by the user. For example, the user clicks the recommended Widget component, and the command type is the recommended command at this time. Then, the target processing module is determined according to the command type, and the target processing module is the recommended processing module.

[0099] Step d, analyzing the packaging command by the target processing module, and executing the function corresponding to the packaging command.

[0100] In specific implementation, the packaging command is analyzed by the target processing module to determine the specific target operation corresponding to the packaging command, that is, the specific operation mode of the target component, such as page jumping, interface updating, data pulling and the like. After determining the specific target operation corresponding to the packaging command, the target operation is executed, that is, the function corresponding to the packaging command is executed.

[0101] By the above scheme, the component triggering operation for the target component is monitored, at this time it is indicated that the user clicks the target component. The target command corresponding to the target component is determined, the target command is the command corresponding to the target component, and different target components correspond to different target commands. The target command is encapsulated by the encapsulation component to obtain an encapsulation command, and the obtained encapsulation command is forwarded to the unified dispatcher. The command type corresponding to the encapsulation command is determined by the unified dispatcher, and the encapsulation command is dispatched to the target processing module according to the command type. The encapsulation command is analyzed by the target processing module, and the function corresponding to the encapsulation command is executed. The target command is uniformly encapsulated by the unified encapsulation component, and is uniformly dispatched by the unified dispatcher, avoiding the logical redundancy caused by independent processing of instructions and data encapsulation of different components, realizing unified protocol encapsulation and unified scheduling, and improving the data processing efficiency.

[0102] Based on the same inventive concept, taking switching to the child mode as an example of the mode switching operation, another embodiment of the disclosure provides a content display method, as shown in the following table: Figure 2 The method specifically includes the following steps: Step 201, the user switches the child mode in the application.

[0103] In specific implementation, when the mode switching operation is monitored, at this time it is indicated that the user selects to switch the mode in the application. The target mode management module corresponding to the mode switching operation outputs a mode switching instruction. The target mode management module corresponding to the mode switching operation is the mode management module corresponding to the mode changed by the switching.

[0104] Step 202, the ChildModeManager state manager is updated.

[0105] Step 203, the state change notification is triggered.

[0106] Step 204, the ChildModeRepo listener receives the notification.

[0107] Step 205, all registered Widget instances are updated in batches.

[0108] In specific implementation, the target mode processing module is the ChildModeRepo module, and the target mode management module is the ChildModeManager module. The ChildModeRepo module is initialized, and an interface creation class of the ChildModeManager module is called to register a callback interface of the ChildModeRepo module in the ChildModeManager module.

[0109] In this embodiment, the callback interface is ChildModeChangeListener, and the ChildModeRepo listener is ChildModeChangeListener.

[0110] Further, when the ChildModeManager module monitors the mode switching operation through the ChildModeChangeListener, the ChildModeRepo module can be notified, that is, the mode switching instruction is sent to the ChildModeRepo module.

[0111] The target mode processing module stores at least one component. When the target mode processing module obtains the mode switching instruction, an update instruction is sent to all components stored in the target mode processing module, so that each component is updated according to the update instruction, so that the display content of each component corresponds to the switched mode corresponding to the mode switching instruction.

[0112] Step 206: Distribute content according to the current state.

[0113] Step 207: If it is a normal mode, load adult appropriate content, such as the wind list, popular movies and television, etc.

[0114] Step 208: If it is a child mode, load child exclusive content, such as educational animation, intelligence game, etc.

[0115] Step 209: Push to the system desktop display.

[0116] Step 210: Realize the intelligent switching of Widget content.

[0117] In specific implementation, for each component, when the component receives the update instruction, the target display content is determined according to the update instruction. After determining the target display content, the target display content is displayed on the display interface. The target display content is the content corresponding to the switched mode corresponding to the mode switching instruction.

[0118] In this embodiment, the component management module is an AppWidgetManager module, and the remote view class is a RemoteView class. The component name of the component is widgetId, and when the display content of the display interface is updated, the corresponding target display content can be found according to the component name. The AppWidgetManager calls the onUpdate method to update the view of the Widget through the RemoteViews object. The AppWidgetManager.updateAppWidget method is called to apply the updated RemoteViews to the Widget, and the interface is updated, that is, the target display content is displayed on the Widget interface.

[0119] In this embodiment, after the user selects to switch the child mode in the video application, the interface method of the ChildModeManager is called, such as enterChildMode / exitChildMode. In the two interface methods, the notification of state change is triggered and notified to the ChildModeRepo. When the ChildModeRepo is initialized and created, a method of the ChildModeManager is called to register the callback interface in the ChildModeManager, and then when the ChildModeManager changes, the ChildModeRepo can be notified.

[0120] Meanwhile, all components that need to be switched between the child mode and the adult mode are stored in the ChildModeRepo. Specifically, when stored, the mapping relationship between the Widget identifier and the ID is stored, and the specific format is: widgetName_widgetId ->widgetId.

[0121] When the state changes, all Widgets can be notified to update. When distributed to different Widgets, the Widget will create different RemoteView layouts according to whether it is a normal mode or a child mode, and then refresh the created RemoteView to the Launcher desktop through the AppWidgetManager calling the corresponding widgetId.

[0122] It should be noted that the method of the embodiment of the present disclosure can be executed by a single device, such as a computer or a server. The method of the embodiment can also be applied to a distributed scenario and completed by multiple devices cooperating with each other. In this distributed scenario, one of the multiple devices can only execute one or more steps in the method of the embodiment of the present disclosure, and the multiple devices will interact with each other to complete the method.

[0123] It should be noted that the above describes some embodiments of the present disclosure. Other embodiments are within the scope of the appended claims. In some cases, the acts or steps recited in the claims can be performed in a different order than those described above and still achieve desirable results. In addition, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0124] Based on the same inventive concept, the present disclosure also provides a content display device corresponding to any of the above-mentioned embodiment methods.

[0125] Reference Figure 3 , Figure 3 The content display device of the embodiments comprises: The monitoring module 301 is configured to monitor the mode switching operation, and the target mode management module outputs a mode switching instruction corresponding to the mode switching operation; The sending module 302 is configured to send an update instruction to all components stored in the target mode processing module when the target mode processing module obtains the mode switching instruction; The display module 303 is configured to determine, for each component, that the update instruction is received, determine and display target display content according to the update instruction.

[0126] In some embodiments, the device further comprises a callback interface registration module, which specifically comprises: The target mode processing module initialization unit is configured to initialize the target mode processing module, and the target mode processing module calls an interface creation class of the target mode management module; The callback interface registration unit is configured to register a callback interface in the target mode management module through the interface creation class.

[0127] In some embodiments, the monitoring module 301 specifically comprises: The mode state monitoring unit is configured to monitor the mode state through the callback interface; The mode switching instruction sending unit is configured to determine that there is a mode switching operation in response to monitoring that the mode state changes through the callback interface, and the target mode management module outputs a mode switching instruction.

[0128] In some embodiments, the display module 303 specifically comprises: The association unit is configured to, for each component, in response to receiving the update instruction, determine the target mode corresponding to the update instruction, obtain the target display content corresponding to the target mode, and associate the target display content with the component name of the component; The refresh unit is configured so that the component management module obtains the target display content corresponding to the component name based on the component name of each component, calls the remote view class to refresh the interface, and displays the target display content.

[0129] In some embodiments, the apparatus further includes a queuing module, the queuing module specifically comprising: A storage instruction receiving unit is configured to receive a storage instruction, wherein the storage instruction includes the component name of the component; The encapsulation unit is configured to encapsulate the stored instructions through an encapsulation component to obtain a first encapsulated instruction; The component name storage unit is configured to call an enqueue instruction through the encapsulated component, and use the enqueue instruction to store the component name of the component in the first encapsulation instruction to the target mode processing module.

[0130] In some embodiments, the component name storage unit specifically includes: The enqueue subunit is configured to call the enqueue instruction through the encapsulation component, use the enqueue instruction to add the first encapsulation instruction to the queue to be processed, and forward the first encapsulation instruction to the component management module; The first encapsulation instruction forwarding subunit is configured such that when the component management module receives the first encapsulation instruction, it forwards the first encapsulation instruction to the target mode processing module; The component name storage subunit is configured so that when the target mode processing module receives the first encapsulation instruction, it parses the first encapsulation instruction to obtain and store the component name of the component.

[0131] For ease of description, the above apparatus is described in terms of its functions, divided into various modules. Of course, in implementing this disclosure, the functions of each module can be implemented in one or more software and / or hardware.

[0132] The apparatus described above is used to implement the corresponding content display method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0133] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the content display method described in any of the above embodiments.

[0134] Figure 4 A more specific electronic device hardware structure diagram provided by the embodiment is shown. The device can include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 for internal communication.

[0135] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits, etc., for executing related programs to implement the technical solutions provided by the embodiments of the present specification.

[0136] The memory 1020 can be implemented by a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, etc. The memory 1020 can store an operating system and other application programs. When the technical solutions provided by the embodiments of the present specification are implemented by software or firmware, the related program codes are stored in the memory 1020 and called and executed by the processor 1010.

[0137] The input / output interface 1030 is used to connect input / output modules to realize information input and output. The input / output modules can be configured as components in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. The input device can include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device can include a display, a speaker, a vibrator, an indicator light, etc.

[0138] The communication interface 1040 is used to connect a communication module (not shown in the figure) to realize the communication interaction between the device and other devices. The communication module can realize communication through a wired manner (such as USB, network cable, etc.) or through a wireless manner (such as mobile network, WIFI, Bluetooth, etc.).

[0139] The bus 1050 includes a channel for transmitting information between various components (such as the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040) of the device.

[0140] It should be noted that although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, but in the specific implementation process, the device can also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device can also only contain the components necessary to implement the embodiments of the present application, and does not necessarily contain all the components shown in the figure.

[0141] The electronic device of the above embodiment is used to implement the corresponding content display method in any of the preceding embodiments, and has the beneficial effects of the corresponding method embodiments, which are not repeated here.

[0142] Based on the same inventive concept, the present disclosure also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the content display method according to any of the preceding embodiments.

[0143] The computer-readable medium of the present embodiment includes permanent and non-permanent, removable and non-removable media, which can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device.

[0144] The computer instructions stored in the storage medium of the above embodiment are used to cause the computer to perform the content display method according to any of the preceding embodiments, and have the beneficial effects of the corresponding method embodiments, which are not repeated here.

[0145] Based on the same inventive concept, the present disclosure also provides a vehicle comprising the content display device of the above embodiment, the electronic device of the above embodiment, and the computer-readable storage medium of the above embodiment, the vehicle device implementing the content display method of any of the preceding embodiments.

[0146] The vehicle of the above embodiment is used to implement the content display method of any of the preceding embodiments, and has the beneficial effects of the corresponding method embodiments, which are not repeated here.

[0147] It can be understood that, before using the technical solutions of various embodiments in the present disclosure, the type of personal information involved, the use range, the use scenario, etc. are informed to the user in an appropriate manner, and the authorization of the user is obtained.

[0148] For example, in response to receiving the active request of the user, prompt information is sent to the user to explicitly prompt the user that the operation requested to be performed will require obtaining and using the personal information of the user. Thus, the user can voluntarily choose whether to provide the personal information to the software or hardware such as an electronic device, an application program, a server or a storage medium, etc. that performs the operation of the technical solutions of the present disclosure according to the prompt information.

[0149] As an optional but non-limiting implementation manner, in response to accepting the active request of the user, the manner of sending the prompt information to the user may, for example, be a pop-up window manner, and the prompt information may, for example, be presented in the form of text in the pop-up window. In addition, the pop-up window may also carry selection controls for the user to select “agree” or “disagree” to provide the personal information to the electronic device.

[0150] It can be understood that the above notification and obtaining of the authorization of the user are only illustrative, and do not limit the implementation manners of the present disclosure, and other manners meeting the relevant laws and regulations can also be applied to the implementation manners of the present disclosure.

[0151] It should be understood by those of ordinary skill in the art that the above discussion of any embodiment is only exemplary and is not intended to imply that the scope (including claims) of the present disclosure is limited to these examples; under the idea of the present disclosure, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other changes of different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of brevity.

[0152] In addition, in order to simplify the description and discussion, and so as not to make the embodiments of the present disclosure difficult to understand, the well-known power / ground connections of integrated circuit (IC) chips and other components can or can not be shown in the provided drawings. In addition, the devices can be shown in the form of block diagrams in order to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure are to be implemented (i.e. these details should be entirely within the understanding of those skilled in the art). Where specific details (e.g. circuits) are set forth in order to describe an illustrative embodiment of the present disclosure, it will be apparent to those skilled in the art that the present disclosure can be practiced without these specific details or with variations on these specific details. Therefore, these descriptions should be considered as illustrative rather than limiting.

[0153] While the present disclosure has been described in connection with certain embodiments thereof, many modifications, substitutions, and variations will be apparent to those of ordinary skill in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) can use the embodiments discussed.

[0154] Embodiments of the present disclosure are intended to cover all such alternatives, modifications, and variations as falling within the broad scope of the appended claims. Accordingly, any one or more of the above-described alternatives, modifications, equivalents, improvements as combinations thereof can be employed in the practice without departing from the spirit and scope of the present disclosure.

Claims

1. A content display method characterized by, The method comprises the following steps: monitoring a mode switching operation, wherein the mode switching operation corresponds to a target mode management module outputting a mode switching instruction; a target mode processing module acquiring the mode switching instruction and sending an update instruction to all components stored in the target mode processing module; for each component, determining that the update instruction is received, determining and displaying target display content according to the update instruction.

2. The method of claim 1, wherein, Before monitoring the mode switching operation, the method further comprises the following steps: initializing the target mode processing module, wherein the target mode processing module calls an interface creation class of the target mode management module; registering a callback interface in the target mode management module through the interface creation class.

3. The method of claim 2, wherein, The monitoring of the mode switching operation, wherein the mode switching operation corresponds to the target mode management module outputting the mode switching instruction, comprises the following steps: monitoring a mode state through the callback interface; in response to monitoring that the mode state changes through the callback interface, determining that there is a mode switching operation, and the target mode management module outputting the mode switching instruction.

4. The method of claim 1, wherein, The determining of the target display content for each component, comprises the following steps: for each component, in response to receiving the update instruction, determining a target mode corresponding to the update instruction, acquiring target display content corresponding to the target mode, and associating the target display content with a component name of the component; a component management module acquiring target display content corresponding to a component name of each component, calling a remote view class to refresh an interface, and displaying the target display content.

5. The method of claim 1, wherein, Before monitoring the mode switching operation, the method further comprises the following steps: receiving a storage instruction, wherein the storage instruction comprises a component name of a component; performing encapsulation processing on the storage instruction through an encapsulation component to obtain a first encapsulation instruction; calling an enqueue instruction through the encapsulation component, and storing the component name of the component in the first encapsulation instruction into a target mode processing module through the enqueue instruction.

6. The method of claim 5, wherein, The calling of the enqueue instruction through the encapsulation component and the storing of the component name of the component in the first encapsulation instruction into the target mode processing module through the enqueue instruction, comprises the following steps: calling the enqueue instruction through the encapsulation component, adding the first encapsulation instruction into a processing queue through the enqueue instruction, and forwarding the first encapsulation instruction to a component management module; the component management module receiving the first encapsulation instruction and forwarding the first encapsulation instruction to the target mode processing module; the target mode processing module receiving the first encapsulation instruction, analyzing the first encapsulation instruction, and obtaining and storing the component name of the component.

7. A content display device, characterized by comprising: The method comprises the following steps: a monitoring module configured to monitor a mode switching operation, wherein the mode switching operation corresponds to a target mode management module outputting a mode switching instruction; a sending module configured to a target mode processing module acquiring the mode switching instruction and sending an update instruction to all components stored in the target mode processing module; a display module configured to, for each component, determining that the update instruction is received, determining and displaying target display content according to the update instruction.

8. An electronic device, comprising: A computer program product comprising a memory, a processor and a computer program stored on the memory and loadable on the processor, the processor implementing the method according to any one of claims 1 to 6 when executing the program.

9. A non-transitory computer-readable storage medium, comprising: The non-transitory computer readable storage medium stores computer instructions for causing a computer to perform the method according to any one of claims 1 to 6.

10. A vehicle comprising a controller, characterized in that The controller is configured to perform the method according to any one of claims 1 to 6.

Images