View display method, controller and vehicle

Abstract

The application provides a view display method, a controller and a vehicle, and relates to the technical field of intelligent networking. The method comprises the following steps: in the case that a target view instance is displayed in a first display viewport, in response to a switching request for the display viewport of the target view instance, releasing a bearer relationship that has been established between the target view instance and the first display viewport; based on a second display viewport indicated by the switching request, establishing a new bearer relationship between the target view instance and the second display viewport, so as to switch the target view instance to the second display viewport for display; wherein, during the switching process of the display viewport, the target view instance remains unchanged. Based on the above scheme, the display flexibility of the view instance can be improved.

Description

Technical Field

[0001] This application relates to the field of intelligent connected vehicle technology, and more particularly to a view display method, controller, and vehicle in the field of information display technology. Background Technology

[0002] When displaying view instances, the limited display flexibility of view instances may make it difficult to switch between viewports.

[0003] Therefore, improving the display flexibility of view instances is a problem that urgently needs to be solved. Summary of the Invention

[0004] This application provides a view display method, controller, and vehicle, which can improve the display flexibility of view instances.

[0005] In a first aspect, this application provides a view display method, the method comprising: When the target view instance is displayed in the first display viewport, in response to a request to switch the display viewport of the target view instance, the established carrying relationship between the target view instance and the first display viewport is released; Based on the second display viewport indicated by the switching request, a new carrying relationship is established between the target view instance and the second display viewport, so as to switch the target view instance to the second display viewport for display; During the switching of display viewports, the target view instance remains unchanged.

[0006] In this embodiment of the application, when the target view instance is displayed in the first display viewport, if there is a request to switch the display viewport of the target view instance, in response to the request to switch the display viewport of the target view instance, the established bearing relationship between the target view instance and the first display viewport can be released first, and when the release is completed, a new bearing relationship between the target view instance and the second display viewport indicated by the switching request can be established to switch the target view instance to the second display viewport for display. Compared to tightly coupling a view instance to a display viewport, where the view instance can only be displayed in a single fixed display viewport and needs to be recreated to be displayed in other display viewports, resulting in overly rigid view instance display, this solution keeps the view instance unchanged when cross-viewport switching is required. It decouples the view instance from the current display viewport by first releasing and then rebuilding the carrier relationship between the view instance and the display viewport. Relying on the dynamically changeable carrier relationship, the same view instance can rebuild the carrier relationship with different display viewports, allowing the same view instance to flexibly switch between different display viewports. This achieves cross-viewport switching of view instances, making view instances reusable and thus improving the display flexibility of view instances.

[0007] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: Construct the instance identifier of the target view instance; The above-mentioned establishment of a new carrying relationship between the target view instance and the second display viewport includes: Construct the viewport identifier for the second display viewport; Bind the instance identifier of the target view instance and the viewport identifier of the second display viewport to obtain a new carrying relationship.

[0008] In this embodiment, by binding the instance identifier of the view instance and the viewport identifier of the display viewport together, an association mapping between the instance identifier of the view instance and the viewport identifier of the display viewport can be achieved, avoiding the problem of misalignment in the establishment of the carrying relationship and improving the accuracy of the establishment of the carrying relationship. Based on the more accurate establishment of the carrying relationship, the accuracy of the view instance display is improved, avoiding the problem of view instance display errors, thereby improving the display effect of the view instance.

[0009] In combination with the first aspect and the above implementation methods, in some implementation methods of the first aspect, the above-mentioned switching of the target view instance to the second display viewport includes: Based on the new carrying relationship, the target view instance is loaded into the display canvas of the second display viewport; In the display canvas, the target view instance is rendered to generate the target display screen of the target view instance displayed in the second display viewport.

[0010] In this embodiment, by loading the target view instance into the display viewport based on a new carrying relationship, the problem of misaligned loading of the target view instance can be avoided, improving the accuracy of target view instance loading. With more accurate view instance loading, the accuracy of view instance display is improved, avoiding display errors and thus enhancing the display effect of the view instance. Furthermore, separating the loading of the target view instance's display viewport from its rendering allows for independent control of view instance mounting and rendering, enabling the view instance to switch displays across viewports without being affected by rendering, thereby improving the display flexibility of the view instance.

[0011] Combining the first aspect and the above implementation methods, in some implementation methods of the first aspect, the above-mentioned rendering process of the target view instance in the display canvas to generate a target display screen of the target view instance displayed in the second display viewport includes: In the display canvas, the target view instance is rendered to generate the initial display screen of the target view instance displayed in the second display viewport; Based on the display scene of the second display viewport, the initial display screen is adjusted to obtain the target display screen.

[0012] In the embodiments of this application, the display scene of the display viewport is taken into account during the rendering of the target view instance, so that the final generated display screen (i.e. the target display screen) matches the display scene of the display viewport, thereby improving the accuracy of the final generated display screen and thus improving the display effect of the view instance.

[0013] In conjunction with the first aspect and the above implementation methods, in some implementations of the first aspect, the method further includes: Verify the display layout parameters of the second display viewport carried in the switching request; If the display layout parameters pass the verification, the step of establishing a new carrying relationship between the target view instance and the second display viewport based on the second display viewport indicated by the switching request is executed.

[0014] In this embodiment, the establishment of the carrying relationship between the view instance and the display viewport is only performed after the display layout parameters of the display viewport have passed verification. This ensures the security of the carrying relationship establishment environment and thus improves the security of the carrying relationship between the view instance and the display viewport. Based on the security of the carrying relationship between the view instance and the display viewport, the accuracy of the view instance display is improved, avoiding display errors and thus enhancing the display effect of the view instance.

[0015] In conjunction with the first aspect and the above implementation methods, in some implementation methods of the first aspect, the above-mentioned verification of the display layout parameters of the second display viewport carried in the switching request includes: If all parameters in the display layout parameters are valid and authentication is successful, the display layout parameter validation is considered successful. If at least one of the display layout parameters is invalid, and / or authentication fails, the display layout parameter validation is determined to have failed.

[0016] In this embodiment, the security of the environment for establishing the carrying relationship is ensured by verifying all parameters in the display layout parameters and the authentication, thereby improving the security of the carrying relationship between the view instance and the display viewport. Based on the security of the carrying relationship between the view instance and the display viewport, the accuracy of the view instance display is improved, avoiding display errors and thus enhancing the display effect of the view instance.

[0017] In conjunction with the first aspect and the above implementation methods, in some implementations of the first aspect, the method further includes: In response to the target build instruction, a target view instance of the object to be displayed is constructed based on the target build parameters carried in the target build instruction and the identity of the object to be displayed.

[0018] In this embodiment, by using the target construction parameters and the identity identifier of the object to be displayed carried in the construction instruction, the problems of incorrect view instance attributes and construction misalignment can be avoided, thus improving the accuracy of view instance construction. Based on more accurate view instance construction, the accuracy of view instance display is improved, avoiding display errors and thereby enhancing the display effect of the view instance. Furthermore, since the display layout parameters of the display viewport are not considered during the view instance construction process, the view instance construction is decoupled from the display layout parameters of the display viewport, further improving the display flexibility of the view instance.

[0019] Combining the first aspect and the above implementation methods, in some implementation methods of the first aspect, the above-mentioned construction of a target view instance of the object to be displayed based on the target construction parameters carried in the target construction instruction and the identity identifier of the object to be displayed includes: Based on the identity identifier of the object to be displayed, an initial view instance is determined, wherein there is a correspondence between the initial view instance and the identity identifier of the object to be displayed; Based on the target construction parameters, the initial view instance is adjusted to generate the target view instance.

[0020] In this embodiment, by using the identifier of the object to be displayed carried in the construction instruction, the problem of misaligned view instance construction can be avoided. Furthermore, by using the target construction parameters carried in the construction instruction, the problem of incorrect view instance attributes can be avoided, thus improving the accuracy of view instance construction. Based on more accurate view instance construction, the accuracy of view instance display is improved, avoiding display errors and thereby enhancing the display effect of the view instance.

[0021] Secondly, this application provides a view display device, the device comprising: The release module is used to release the established bearing relationship between the target view instance and the first display viewport in response to a switching request for the display viewport of the target view instance when the target view instance is displayed in the first display viewport. The processing module is used to establish a new carrying relationship between the target view instance and the second display viewport based on the second display viewport indicated by the switching request, so as to switch the target view instance to the second display viewport for display; wherein, the target view instance remains unchanged during the switching of the display viewport.

[0022] Thirdly, this application provides a controller, including a storage module and a processing module. The storage module is used to store executable program code, and the processing module is used to call and run the executable program code from the storage module, causing the controller to execute the methods in the first aspect or any possible implementation of the first aspect.

[0023] Fourthly, this application provides a vehicle including a memory and a processor. The memory is used to store executable program code, and the processor is used to call and run the executable program code from the memory, causing the vehicle to perform the methods described in the first aspect or any possible implementation thereof.

[0024] Fifthly, this application provides a computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform the method described in the first aspect or any possible implementation thereof.

[0025] Sixthly, this application provides a computer-readable storage medium storing computer program code that, when executed on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of a scenario for the view display method provided in an embodiment of this application; Figure 2 This is a flowchart illustrating a view display method provided in an embodiment of this application; Figure 3 This is a schematic diagram of the interaction flow of a view display method provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of the view display device provided in the embodiments of this application; Figure 5 This is a schematic diagram of the controller provided in an embodiment of this application; Figure 6 This is a schematic diagram of the vehicle structure provided in the embodiments of this application. Detailed Implementation

[0027] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0028] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0029] With the rapid development of intelligent vehicle cockpits, the display needs of in-vehicle information are becoming increasingly complex and diverse. To display in-vehicle information-related objects, a view instance corresponding to the object can be constructed, allowing the object to be displayed through that view instance. However, when displaying objects through view instances, the limited flexibility of view instances may lead to display errors, thus affecting the display effect. The displayed object can be at least one of the following: navigation map, media lyrics, live wallpaper, desktop cards, vehicle status information, etc.

[0030] For example, when displaying media lyrics, you can first construct a view instance corresponding to the media lyrics, and then display the media lyrics display object through the view instance corresponding to the media lyrics.

[0031] For example, when displaying a display object corresponding to a view instance, the business application process of the display object can create the view instance corresponding to the display object, and the desktop host program (Launcher) or system desktop process can host and display the view instance corresponding to the display object on the screen. Specifically, the view instance corresponding to the display object and the view instance corresponding to the display object can be created through various system components.

[0032] The system components may include at least one of the following: data provider component, binder, canvas control view host, remote canvas, media lyrics provider, lyrics view component, simple lyrics view component, widget binder component, canvas root view component, and widget binder. Different display objects may require different system components.

[0033] Data provider components: These manage data from business applications and provide an access point to enable system processes to access and share that data. For example, a media lyrics provider: This provides an access point to allow system processes to access and share media lyrics.

[0034] Binder: Used to implement cross-process data exchange and method calls, it serves as a communication channel between different processes, enabling direct communication between different processes without requiring the use of a data provider component as an intermediary for communication.

[0035] Canvas Control View Host: A class used to manage canvas controls to display view instances in system processes (e.g., desktop host programs or system desktop processes).

[0036] Remote canvas (also known as "remote rendering surface"): used to hold view instances and render the view instances.

[0037] Lyrics View Component: Used to create and manage lyrics display views.

[0038] Simple Lyrics View Component: A custom view control used to display lyrics in business applications.

[0039] Widget Binding Component: Used for binding connections between widgets and remote services, as well as managing view instances.

[0040] Canvas Root View Component: Serves as the root view container for the canvas rendering hierarchy.

[0041] Widget binder: A widget used to connect the state of child widgets, ensuring that the child widgets update automatically when the state changes.

[0042] For example, when the displayed object is media lyrics, the media lyrics provider provides an access point so that system processes can access and share the media lyrics. The lyrics view component is used to create simple lyrics view components, the widget binding component is responsible for managing view instances, the canvas root view component is responsible for connecting to the display screen, and the widget binder is responsible for passing subsequent display operations, together completing the cross-process display of media lyrics.

[0043] It should be noted that since the business application process and the desktop host program or system desktop process belong to different processes, the display of the displayed object involves cross-process interaction, and the "display of the displayed object" can be referred to as "cross-process display." Furthermore, "business" can refer to the related transactions involved in displaying the displayed object on the screen.

[0044] In related technologies, when constructing a view instance corresponding to a display object, the screen must be obtained first before creating the corresponding view instance. This means the view instance is tightly bound to the screen, making it adaptable only to that screen. If the screen changes, a new view instance corresponding to the changed screen needs to be generated. Therefore, this strong coupling between the view instance and the screen makes it difficult to reuse the view instance and results in poor display flexibility.

[0045] Figure 1 This is a schematic diagram of a view display method provided in an embodiment of this application.

[0046] For example, such as Figure 1 As shown, Figure 1 The system includes a vehicle cockpit 101. The vehicle cockpit 101 includes at least in-vehicle screen A and in-vehicle screen B. Both in-vehicle screen A and in-vehicle screen B can display objects related to in-vehicle information.

[0047] When displaying media lyrics on vehicle screen A, a view instance A of the media lyrics, tightly coupled with vehicle screen A, needs to be created first. This view instance A is then mounted on a remote canvas of vehicle screen A to obtain the rendered image of view instance A, which is then displayed on vehicle screen A. If you want to switch the display of the media lyrics from vehicle screen A to vehicle screen B, due to the tight coupling between vehicle screen A and the view instance A of the media lyrics, you cannot use view instance A to display the media lyrics on vehicle screen B. Instead, you need to create a new view instance B of the media lyrics, tightly coupled with vehicle screen B, and mount view instance B on a remote canvas of vehicle screen B to obtain the rendered image of view instance B, which is then displayed on vehicle screen B. Therefore, the strong coupling between the view instance of the media lyrics and the vehicle screen prevents cross-viewport switching and makes it difficult to reuse the view instance of the media lyrics across different screens, resulting in poor display flexibility.

[0048] In view of this, this application proposes a view display method, controller, and vehicle. Through the embodiments of this application, the established bearing relationship between the view instance and the display viewport can be released, and a new bearing relationship between the view instance and other display viewports can be re-established, so that the same view instance can be flexibly switched between different display viewports, realizing cross-viewport switching display of view instances, making view instances reusable, thereby improving the display flexibility of view instances.

[0049] The following is combined with Figures 2 to 3 The view display method provided in the embodiments of this application will be described in detail.

[0050] Figure 2This is a flowchart illustrating a view display method provided in an embodiment of this application. The method can be executed by a vehicle or by a controller within the vehicle.

[0051] For example, such as Figure 2 As shown, the method 200 includes the following implementation process: S210, if the target view instance is displayed in the first display viewport, in response to the request to switch the display viewport of the target view instance, the established bearing relationship between the target view instance and the first display viewport is released.

[0052] For example, when the first display viewport is displaying the target view instance, it can be determined whether a request to switch the display viewport of the target view instance has been detected. If a request to switch the display viewport of the target view instance is detected, the request can be responded to, and it can be determined whether the second display viewport indicated by the switching request of the first display viewport and the target view instance display viewport are different. If the second display viewport indicated by the switching request of the first display viewport and the target view instance display viewport are different, it indicates that the target view instance needs to be moved to a new display viewport for display and will no longer continue to be displayed in the first display viewport. In this case, the established carrying relationship between the target view instance and the first display viewport can be released, that is, the established carrying relationship between the target view instance and the first display viewport can be terminated, so that there is no carrying relationship between the target view instance and the first display viewport, so as to facilitate the reuse of the target view instance across different screens. If the second display viewport indicated by the switching request of the first display viewport and the target view instance display viewport are the same, it indicates that the target view instance will continue to be displayed in the first display viewport and does not need to switch display viewports; the current display viewport switching request can be ignored.

[0053] In this context, a display viewport represents a visual object used to carry view instances. A display viewport can consist of at least one of a display screen, a display canvas, or a display area. In other words, a display screen, a display canvas, and a display area can all serve as the carrier of a display viewport. Assuming a display viewport consists of a display screen, a display canvas, and a display area, the display viewport will change when at least one of these components changes. That is, different display viewports correspond to different display screens, display canvases, and / or display areas. For example, display viewport A consists of display screen A, display canvas A, and display area A. When the display screen changes from display screen A to display screen B, the display viewport changes from display viewport A to display viewport B, meaning display viewport B consists of display screen B, display canvas A, and display area A. Similarly, when the display area changes from display area A to display area C, the display viewport changes from display viewport A to display viewport C, meaning display viewport C consists of display screen A, display canvas A, and display area C.

[0054] Wherein, the first display viewport refers to the display viewport currently displaying the target view instance, for example, vehicle screen A. And, the target view instance is the view instance corresponding to the display object (which can be called the "object to be displayed") that needs to be displayed through the display viewport. For example, when the object to be displayed is media lyrics, the target view instance is the view instance corresponding to the media lyrics. There is at least one target view instance, and each target view instance represents the view instance corresponding to each object to be displayed. And, the carrying relationship between the view instance and the display viewport refers to the functional relationship whereby the display viewport, as a display carrier, carries and presents the rendered image composed of view instances. This functional relationship, embodied in "supporting" and "being presented," can be called the "carrying relationship." And, the target view instance display viewport switching request is used to request switching the target view instance display viewport to the display viewport indicated by the switching request (i.e., the second display viewport). Alternatively, the target view instance display viewport switching request is used to request switching the target view instance display viewport from the first display viewport to the second display viewport indicated by the switching request.

[0055] For example, upon detecting a switching operation on the display viewport of a target view instance, a switching request for the display viewport of the target view instance can be generated in response to the switching operation. That is, the switching request for the display viewport of the target view instance can be triggered by the switching operation. The switching operation can be performed via voice, gesture swipe, or interface button click, among other methods. Furthermore, the switching operation can be initiated by the user or automatically triggered by a system process based on the display requirements of the target view instance; this embodiment does not limit the specific actions taken in this regard.

[0056] It should be understood that the first display viewport and the second display viewport are generally different display viewports; otherwise, there would be no need for a request to switch the display viewport of the target view instance.

[0057] S220, based on the second display viewport indicated by the switching request, establish a new carrying relationship between the target view instance and the second display viewport, so as to switch the target view instance to the second display viewport for display.

[0058] For example, after the established carrying relationship between the target view instance and the first display viewport is released, a new carrying relationship between the target view instance and the second display viewport can be re-established through the second display viewport indicated by the target view instance's display viewport switching request. After the new carrying relationship between the target view instance and the second display viewport is established, the target view instance's display viewport is switched, thereby switching the target view instance to the second display viewport, and displaying the target view instance in the second display viewport.

[0059] During the switching of display viewports, the target view instance remains unchanged. That is, during the switching of the target view instance's display viewport, the target view instance displayed in the first and second display viewports is the same view instance, and it is not regenerated. Furthermore, the second display viewport represents the viewport where the target view instance needs to be displayed in the next moment. Until a new carrying relationship is established between the target view instance and the second display viewport, the target view instance is not displayed in the second display viewport.

[0060] It should be noted that the established carrying relationship between the target view instance and the first display viewport can be referenced to the method for establishing a new carrying relationship between the target view instance and the second display viewport, and will not be repeated here. Furthermore, the same view instance can only establish a carrying relationship with one display viewport at a time. This is because if the same view instance establishes carrying relationships with multiple display viewports simultaneously, it will lead to display conflicts, such as display errors or contention for display resources, which is detrimental to the normal display of the view instance. Also, the carrying relationships established between the same view instance and different display viewports are different, and the carrying relationships established between different view instances and the same display viewport are also different.

[0061] In such Figure 2 In the method 200 shown, if the target view instance is displayed in the first display viewport, and there is a request to switch the display viewport of the target view instance, in response to the request to switch the display viewport of the target view instance, the established bearing relationship between the target view instance and the first display viewport can be released first, and when the release is completed, a new bearing relationship between the target view instance and the second display viewport indicated by the switching request can be established to switch the target view instance to the second display viewport for display. Compared to tightly coupling a view instance to a display viewport, where the view instance can only be displayed in a single fixed display viewport and needs to be recreated to be displayed in other display viewports, resulting in overly rigid view instance display, this solution keeps the view instance unchanged when cross-viewport switching is required. It decouples the view instance from the current display viewport by first releasing and then rebuilding the carrier relationship between the view instance and the display viewport. Relying on the dynamically changeable carrier relationship, the same view instance can rebuild the carrier relationship with different display viewports, allowing the same view instance to flexibly switch between different display viewports. This achieves cross-viewport switching of view instances, making view instances reusable and thus improving the display flexibility of view instances.

[0062] It should be noted that S210~S220 above is a simplified description of the view display method provided in the embodiments of this application. The following is a more detailed explanation of... Figure 2 The specific implementation methods shown in the embodiments are described in detail below: When executing S210, in response to the target construction instruction, a target view instance of the object to be displayed is constructed based on the target construction parameters carried in the target construction instruction and the identity of the object to be displayed.

[0063] For example, upon detecting a target construction instruction, a target view instance of the object to be displayed can be constructed in response to the instruction, using the target construction parameters and the identifier of the object to be displayed carried in the instruction. The construction parameters may include at least one of the following: the view instance's size, hierarchy, structure, animation style, display orientation, and control parameters. The identifier of the object to be displayed may be its name identifier or a unique code.

[0064] Optionally, upon detecting a display operation on an object to be displayed, a target construction instruction can be generated in response to the display operation. That is, the target construction instruction can be triggered by the display operation on the object to be displayed, instructing the construction of a target view instance of the object to be displayed. The display operation on the object to be displayed can include at least one of voice, gesture swipe, or interface button click. Furthermore, the display operation on the object to be displayed can be initiated by the user or automatically triggered by a system process based on the display requirements of the target view instance; this embodiment does not limit the specific actions taken in this regard.

[0065] In this embodiment, by using the target construction parameters and the identity identifier of the object to be displayed carried in the construction instruction, the problems of incorrect view instance attributes and construction misalignment can be avoided, thus improving the accuracy of view instance construction. Based on more accurate view instance construction, the accuracy of view instance display is improved, avoiding display errors and thereby enhancing the display effect of the view instance. Furthermore, since the display layout parameters of the display viewport are not considered during the view instance construction process, the view instance construction is decoupled from the display layout parameters of the display viewport, further improving the display flexibility of the view instance.

[0066] Furthermore, the above-mentioned construction of a target view instance of the object to be displayed based on the target construction parameters carried in the target construction instruction and the identity identifier of the object to be displayed includes: determining an initial view instance based on the identity identifier of the object to be displayed; and adjusting the initial view instance based on the target construction parameters to generate a target view instance.

[0067] There is a correspondence between the initial view instance and the identity of the object to be displayed. This correspondence can be obtained through pre-configuration or testing and can be pre-stored in the vehicle's storage unit or in a cloud server that communicates with the vehicle so that the vehicle can retrieve it at any time.

[0068] For example, the initial view instance corresponding to the identity of the object to be displayed is determined by the object's identifier. Then, the initial view instance corresponding to the object's identifier is adjusted according to the target construction parameters to obtain an adjusted view instance that matches the target construction parameters, ensuring that the adjusted view instance meets the display requirements. This adjusted view instance is then designated as the target view instance.

[0069] Optionally, a target view instance of the object to be displayed can be constructed using the identifier of the object to be displayed carried in the target construction instruction. Specifically, the initial view instance corresponding to the identifier of the object to be displayed can be determined by using the identifier of the object to be displayed, and this initial view instance can be directly determined as the target view instance.

[0070] It should be noted that the target build parameters do not change with the switching of the display viewport. They are the baseline parameters required for building the target view instance. However, since system process updates and upgrades may cause the target build parameters to be updated as well, the initial view instance needs to be adapted and adjusted using the target build parameters to ensure that the adjusted view instance is compatible with the system process.

[0071] In this embodiment, by using the identifier of the object to be displayed carried in the construction instruction, the problem of misaligned view instance construction can be avoided. Furthermore, by using the target construction parameters carried in the construction instruction, the problem of incorrect view instance attributes can be avoided, thus improving the accuracy of view instance construction. Based on more accurate view instance construction, the accuracy of view instance display is improved, avoiding display errors and thereby enhancing the display effect of the view instance.

[0072] When executing S210, an instance identifier of the target view instance is constructed; the above-mentioned establishment of a new bearing relationship between the target view instance and the second display viewport includes: constructing a viewport identifier of the second display viewport; binding the instance identifier of the target view instance and the viewport identifier of the second display viewport to obtain a new bearing relationship.

[0073] For example, first, an instance identifier for the target view instance and a viewport identifier for the second display viewport are constructed. Then, a new carrying relationship is established between the target view instance and the second display viewport using these identifiers. Specifically, the instance identifier of the target view instance and the viewport identifier of the second display viewport are bound together to obtain a mapping relationship between them. This mapping relationship demonstrates the carrying binding between the target view instance and the second display viewport, thus establishing a new carrying relationship between them.

[0074] Optionally, an instance identifier for the target view instance and a viewport identifier for the second display viewport are generated using preset rules. The preset rules refer to the rules for generating the instance identifier for the view instance and the rules for generating the viewport identifier for the display viewport. For example, the preset rules can be any of the following: naming format rules, naming convention rules, uniqueness constraint rules, etc. Furthermore, the preset rules can be obtained through pre-configuration or testing and pre-stored in the vehicle's storage unit, or stored in a cloud server connected to the vehicle for easy retrieval by the vehicle at any time.

[0075] Optionally, the instance identifier of the target view instance can be constructed by at least one of the following: the identity identifier of the object to be displayed, the request timestamp of the view switching request of the target view instance, and the view type corresponding to the object to be displayed.

[0076] For example, at least one of the following is encoded: the identity of the object to be displayed, the request timestamp of the view switching request of the target view instance, and the view type corresponding to the object to be displayed. The encoded data is then concatenated or hashed to obtain the processed code, which is then used as the instance identifier of the target view instance.

[0077] The target view instance's viewport switching request may carry the screen identifier of the display screen, the canvas identifier of the display canvas, and the area identifier of the display area in the second display viewport. The screen identifier of the display screen, the canvas identifier of the display canvas, and the area identifier of the display area may be their respective name identifiers or unique codes, etc.

[0078] Optionally, the viewport identifier of the second display viewport is constructed by at least one of the screen identifier of the display screen, the canvas identifier of the display canvas, and the area identifier of the display area in the second display viewport.

[0079] For example, at least one of the screen identifier of the display screen, the canvas identifier of the display canvas, and the area identifier of the display area in the second display viewport is encoded, and the encoded data is concatenated or hashed to obtain the processed code, which is then used as the viewport identifier of the second display viewport.

[0080] In this embodiment, by binding the instance identifier of the view instance and the viewport identifier of the display viewport together, an association mapping between the instance identifier of the view instance and the viewport identifier of the display viewport can be achieved, avoiding the problem of misalignment in the establishment of the carrying relationship and improving the accuracy of the establishment of the carrying relationship. Based on the more accurate establishment of the carrying relationship, the accuracy of the view instance display is improved, avoiding the problem of view instance display errors, thereby improving the display effect of the view instance.

[0081] In one implementation, the above-mentioned switching of the target view instance to the second display viewport includes: loading the target view instance into the display canvas of the second display viewport based on the new carrying relationship; and performing screen rendering processing on the target view instance in the display canvas to generate the target display screen of the target view instance displayed in the second display viewport.

[0082] For example, upon obtaining a new carrying relationship between the target view instance and the second display viewport, the target view instance can be loaded into the display canvas of the second display viewport, which has a carrying relationship with the target view instance, through this new carrying relationship. Then, the target view instance is rendered on the display canvas of the second display viewport, and after the rendering process is complete, a target display screen is generated and displayed on the target view instance in the second display viewport.

[0083] Optionally, the target view instance can be switched to the second display viewport using a new hosting relationship. Specifically, a target display screen for the target view instance displayed in the second display viewport can be generated using the new hosting relationship.

[0084] Here, the display canvas of the display viewport refers to the drawing area or buffer within the display viewport used to draw the display image of the view instance, such as a remote canvas. And, canvas rendering processing refers to the process of drawing the view instance as a pixel image that can be displayed on the display viewport.

[0085] In this embodiment, by loading the target view instance into the display viewport based on a new carrying relationship, the problem of misaligned loading of the target view instance can be avoided, improving the accuracy of target view instance loading. With more accurate view instance loading, the accuracy of view instance display is improved, avoiding display errors and thus enhancing the display effect of the view instance. Furthermore, separating the loading of the target view instance's display viewport from its rendering allows for independent control of view instance mounting and rendering, enabling the view instance to switch displays across viewports without being affected by rendering, thereby improving the display flexibility of the view instance.

[0086] In one implementation, the above-mentioned screen rendering processing of the target view instance to generate the target display screen of the target view instance displayed in the second display viewport includes: performing screen rendering processing on the target view instance based on the display scene of the second display viewport to generate the target display screen.

[0087] For example, when rendering the target view instance, the rendering process can also be combined with the display scene of the second display viewport to generate a target display screen that matches the display scene of the second display viewport.

[0088] The display scene of the display viewport refers to the context in which the display viewport exists. The display scene of the display viewport may include at least one of the following: the environmental scene in which the display viewport exists, the driving scene in which the display viewport exists, the usage scene in which the display viewport exists, the system operation scene in which the display viewport exists, and the user interaction scene in which the display viewport exists.

[0089] Optionally, the target view instance is switched to be displayed in the second display viewport by means of the new carrying relationship and the display scene of the second display viewport. Specifically, a target display screen of the target view instance displayed in the second display viewport is generated by means of the new carrying relationship and the display scene of the second display viewport.

[0090] Optionally, an initial display screen of the target view instance displayed in the second display viewport is generated through a new carrying relationship; the initial display screen is adjusted through the display scene of the second display viewport to obtain an adjusted view instance, and the adjusted view instance is determined as the target view instance.

[0091] For example, the target view instance is first loaded into the display canvas of the second display viewport through a new carrying relationship; in the display canvas, the target view instance is rendered to generate the initial display screen of the target view instance displayed in the second display viewport. Then, the initial display screen is adaptively adjusted according to the display scene of the second display viewport to obtain the target display screen of the target view instance.

[0092] In the embodiments of this application, the display scene of the display viewport is taken into account during the rendering of the target view instance, so that the final generated display screen (i.e. the target display screen) matches the display scene of the display viewport, thereby improving the accuracy of the final generated display screen and thus improving the display effect of the view instance.

[0093] In one implementation, the display layout parameters of the second display viewport carried in the switching request are verified; if the display layout parameters pass the verification, a step is performed to establish a new carrying relationship between the target view instance and the second display viewport based on the second display viewport indicated by the switching request.

[0094] For example, in response to a request to switch the display viewport of a target view instance, the display layout parameters of the second display viewport carried in the switch request can be validated. If the display layout parameters pass the validation, it indicates that the conditions for establishing a new carrying relationship are met, and only then will the step of establishing a new carrying relationship between the target view instance and the second display viewport based on the second display viewport indicated by the switch request be executed.

[0095] If the display layout parameter verification fails, it means that the conditions for establishing a new carrying relationship are not met. Therefore, the step of establishing a new carrying relationship between the target view instance and the second display viewport based on the second display viewport indicated by the switching request will not be executed. In other words, the establishment of the new carrying relationship fails, and the target view instance cannot be displayed in the second display viewport.

[0096] Optionally, after the target view instance is generated, the display layout parameters of the second display viewport carried in the target view instance display viewport switching request can be verified in response to the target view instance display viewport switching request.

[0097] The display layout parameters of the display viewport may include at least one of the following: whether the display screen in the display viewport is valid, whether the display canvas is valid, whether the display area is valid, and whether the communication token is valid.

[0098] Determining the validity of the viewport's display screen: Check the display screen's identifier (which can be denoted as "DisplayId") to see if the display screen actually exists and can serve as the hosting screen for the target view instance. If the display screen actually exists and can serve as the hosting screen for the target view instance, it is considered valid. If the display screen does not actually exist, or cannot serve as the hosting screen for the target view instance, it is considered invalid.

[0099] To determine if the viewport's display canvas is valid: Verify that the display canvas actually exists and is usable. If the display canvas actually exists, is usable, and has not been released, destroyed, or expired, it is valid. If the display canvas does not actually exist or is unusable, it is invalid.

[0100] To determine if the display area of ​​the display port is valid, check if the display area is greater than 0 and if it matches the display size of the target view instance. If the display area is greater than 0 and matches the display size of the target view instance, the display area is valid. If the display area is equal to 0, or does not match the display size of the target view instance, the display area is invalid.

[0101] Validity of the communication token: Verify whether the communication token is null and whether it is a bearer channel for the target view instance. If the communication token is not null, contains data, and is a bearer channel for the target view instance (and not a mismatched bearer channel), the communication token is valid. If the communication token is null or is not a bearer channel for the target view instance, the communication token is invalid.

[0102] In this embodiment, the establishment of the carrying relationship between the view instance and the display viewport is only performed after the display layout parameters of the display viewport have passed verification. This ensures the security of the carrying relationship establishment environment and thus improves the security of the carrying relationship between the view instance and the display viewport. Based on the security of the carrying relationship between the view instance and the display viewport, the accuracy of the view instance display is improved, avoiding display errors and thus enhancing the display effect of the view instance.

[0103] In one implementation, the above-mentioned verification of the display layout parameters of the second display viewport carried in the switching request includes: determining that the display layout parameter verification is successful if all parameters in the display layout parameters are valid and the authentication is successful; and determining that the display layout parameter verification is unsuccessful if at least one parameter in the display layout parameters is invalid and / or the authentication is unsuccessful.

[0104] If all parameters in the display layout parameters are valid and the authentication is successful, it means that all pre-verification conditions have been met. Therefore, it can be determined that the display layout parameter verification has passed.

[0105] If at least one parameter in the display layout parameters is invalid, and / or authentication fails, it indicates that not all pre-validation conditions have been met and there are still unmet conditions. Therefore, it can be determined that the display layout parameter validation has failed.

[0106] In this embodiment, the security of the environment for establishing the carrying relationship is ensured by verifying all parameters in the display layout parameters and the authentication, thereby improving the security of the carrying relationship between the view instance and the display viewport. Based on the security of the carrying relationship between the view instance and the display viewport, the accuracy of the view instance display is improved, avoiding display errors and thus enhancing the display effect of the view instance.

[0107] Figure 3 This is a schematic diagram of the interaction flow of a view display method provided in an embodiment of this application. Wherein, Figure 3 This includes the host process (i.e., the system process mentioned above) and the business application process. The business application process includes a data provider component, an event channel, and a remote host container. The event channel (IPC Channel) is used for event transmission, distribution, and synchronization in cross-process communication. The remote host container is used for verifying location parameters, establishing bearer relationships, and creating and managing view instances. Furthermore, it is assumed that display viewport A is the first display viewport, and display viewport B is the second display viewport.

[0108] For example, such as Figure 3 As shown, the method 300 includes the following implementation process: S1, send the data access request for the object to be displayed and the target construction instructions.

[0109] For example, when the host process detects a display operation on an object to be displayed, it can generate a target construction instruction for the object to be displayed, and a data access request for the object to be displayed. Both the data access request and the target construction instruction for the object to be displayed are then sent to the business application process. The data access request for the object to be displayed is used to request access to the relevant data for displaying the object.

[0110] S2 returns the called data.

[0111] For example, when a business application process receives a data access request for an object to be displayed, it calls the relevant data for displaying the object through the data provider component in the business application, and sends the relevant data for displaying the object (which can be called "call data") to the host process to realize access to the relevant data for displaying the object.

[0112] The data related to the display of the object to be displayed may include at least one of the following: binder, event mask, component identifier, and display identifier. The event mask is used to specify the types of interactive events that the view instance of the object to be displayed can support. The component identifier is used to uniquely identify the view instance of the object to be displayed. The display identifier is used to indicate that the view instance of the object to be displayed should be displayed in the specified display viewport.

[0113] S3, send the target build command.

[0114] S4, send the target build command.

[0115] For example, the data provider component sends the target build instructions of the object to be displayed to the event channel, and then forwards the target build instructions of the object to be displayed to the remote host container through the event channel.

[0116] S5, create a container.

[0117] For example, when the remote host container receives a target build instruction for an object to be displayed, it can respond to the target build instruction by creating a container corresponding to the object to be displayed. The container corresponding to the object to be displayed is a view mount point created to hold the view instance corresponding to the object to be displayed, thereby mounting the view instance corresponding to the object to be displayed to the display viewport.

[0118] S6, Create a view instance.

[0119] For example, when the remote host container receives a target build instruction for an object to be displayed, it can respond to the target build instruction by creating a view instance corresponding to the object to be displayed (i.e., the aforementioned target view instance). It should be understood that the view instance corresponding to the object to be displayed is not bound to any display viewport at this time.

[0120] Optionally, when the view instance corresponding to the object to be displayed is created, an instance identifier (i.e., the instance identifier of the target view instance) can be generated using the view type and component identifier of the view instance corresponding to the object to be displayed. Specifically, the instance identifier of the view instance corresponding to the object to be displayed is generated using the key of the view type and component identifier of the view component. For example, the key composed of the view type and component identifier of the view instance corresponding to the object to be displayed (i.e., the key of widgetId-viewType) can be used as the instance identifier of the view instance corresponding to the object to be displayed. In this embodiment, the "component identifier of the view component" can be denoted as "widgetId", and the "view type of the view instance corresponding to the object to be displayed" can be denoted as "viewType".

[0121] For example, the view type of the view instance corresponding to the object to be displayed and the component identifier of the view component are concatenated or hashed to obtain the processed key. The processed key is then used as the instance identifier of the target view instance to facilitate the rapid location and management of the view instance corresponding to the object to be displayed. For example, it can be used to identify the view instance, route subsequent cross-process display events, and locate the view instance when re-establishing the bearing relationship.

[0122] Among them, the view component is used to create the view instance corresponding to the object to be displayed. That is, the view component is the component used to create the view instance corresponding to the object to be displayed. Different objects to be displayed correspond to different view components, that is, there is a one-to-one correspondence between the object to be displayed and the view component corresponding to the object to be displayed.

[0123] For example, when the object to be displayed is media lyrics, when the business application process receives a data access request for media lyrics from the host process, it can return relevant data for displaying the media lyrics to the host process through the media lyrics provider. Furthermore, the container and view instance for media lyrics can be created by binding components to widgets, and the creation of the container and view instance for media lyrics can be implemented through the lyrics view component.

[0124] S7, send the placement parameters for display viewport A.

[0125] S8, send the placement parameters for display viewport A.

[0126] For example, when the host process receives the placement parameters of the display viewport A (i.e., the display layout parameters mentioned above), it can send the placement parameters of the display viewport A to the event channel, and then forward the placement parameters of the display viewport A to the remote host container through the event channel.

[0127] Optionally, when sending the display viewport placement parameters, the host process needs to first determine whether it meets the target display conditions. If the target display conditions are met, it means the view instance can be displayed normally on the display viewport, and in this case, the display viewport placement parameters can be sent. If the target display conditions are not met, it means the view instance cannot be displayed normally on the display viewport, and in this case, the display viewport placement parameters are not sent. Additionally, error messages can be output to inform the user of any display errors in the object to be displayed. Error messages can be displayed in at least one of the following ways: voice, text, or image.

[0128] The target display conditions may include at least one of the following: the size of the display area in the display viewport used to display the view instance has been determined, the display canvas has been created, the screen identifier of the display screen has been determined, and the pass is ready.

[0129] S9, a route view instance.

[0130] S10, verify the positioning parameters of display viewport A.

[0131] For example, when the remote host container receives the placement parameters for display viewport A, it does not directly display the view instance corresponding to the object to be displayed. Instead, it first routes (i.e., looks up) the view instance corresponding to the instance identifier (which can be called the "composite instance routing key") of the view instance corresponding to the object to be displayed. Furthermore, it validates the placement parameters for display viewport A.

[0132] S11, verification passed, establish the carrying relationship between the view instance and the display viewport A.

[0133] For example, when the placement parameters of the display viewport A pass the verification, it means that the conditions for establishing a new carrying relationship are met, and the remote host container establishes the carrying relationship between the view instance and the display viewport A.

[0134] S12, Send the view instance; and the carrying relationship between the view instance and the display viewport A.

[0135] S13, Send the view instance; and the carrying relationship between the view instance and the display viewport A.

[0136] For example, the remote host container sends the view instance, and the bearer relationship between the view instance and the display viewport A, to the event channel, and forwards the view instance, and the bearer relationship between the view instance and the display viewport A, to the host process through the event channel.

[0137] S14, render the view instance, obtain the display screen corresponding to the view instance, and display the display screen corresponding to the view instance in the display viewport A.

[0138] For example, when the host process receives the view instance and the carrying relationship between the view instance and the display viewport A, it renders the view instance on the canvas of the display viewport A to obtain the display screen corresponding to the view instance (i.e. the target display screen mentioned above), and displays the display screen corresponding to the view instance in the display viewport A.

[0139] S15, if the verification fails, the current binding will be rejected, and the system will wait to receive the placement parameters for the next display viewport.

[0140] For example, if the placement parameter verification for display viewport A fails, it indicates that the conditions for establishing a new hosting relationship are not met, and the remote host container refuses to establish the hosting relationship between the view instance and display viewport A. It then waits to receive the placement parameters for the next display viewport.

[0141] S16, send failure feedback information.

[0142] S17, send failure feedback information.

[0143] For example, when the placement parameter verification of viewport A fails, the remote host container can send the failure feedback information to the event channel and forward the failure feedback information to the host process through the event channel.

[0144] S18, output display failure information on display viewport A.

[0145] For example, when the host process receives a display failure message, it can output the message on display viewport A to inform the user that the object to be displayed is displaying incorrectly. The failure message can be output in at least one of the following ways: voice, text, image, etc.

[0146] S19, send the positioning parameters for display viewport B.

[0147] S20, send the placement parameters for display viewport B.

[0148] For example, when the host process receives the placement parameters of the display viewport B (i.e., the display layout parameters mentioned above), it can send the placement parameters of the display viewport B to the event channel, and then forward the placement parameters of the display viewport B to the remote host container through the event channel.

[0149] S21, a route view instance.

[0150] S22, verify the positioning parameters of the display viewport B.

[0151] For example, when the remote host container receives the placement parameters for display viewport B, it does not directly display the view instance corresponding to the object to be displayed. Instead, it first routes to the view instance corresponding to the instance identifier of the view instance corresponding to the object to be displayed. Furthermore, it validates the placement parameters for display viewport B.

[0152] S23, verification passed, release the established bearer relationship, establish a new bearer relationship for the view instance and display viewport B.

[0153] For example, when the placement parameter verification of viewport A passes, it means that the conditions for establishing a new bearing relationship are met. The remote host container first releases the bearing relationship that was previously established between the view instance and viewport A. After the release is complete, a new bearing relationship is re-established between the view instance and viewport B.

[0154] S24, Send the view instance; and the carrying relationship between the view instance and the display viewport B.

[0155] S25, Send the view instance; and the carrying relationship between the view instance and the display viewport B.

[0156] For example, the remote host container sends the view instance, and the bearer relationship between the view instance and the display viewport B, to the event channel, and forwards the view instance, and the bearer relationship between the view instance and the display viewport B, to the host process through the event channel.

[0157] S26, render the view instance, obtain the display screen corresponding to the view instance, and display the display screen corresponding to the view instance in the display viewport B.

[0158] For example, when the host process receives the view instance and the carrying relationship between the view instance and the display viewport B, it renders the view instance on the canvas of the display viewport B to obtain the display screen corresponding to the view instance (i.e. the target display screen mentioned above), and displays the display screen corresponding to the view instance in the display viewport B.

[0159] S27 If the verification fails, the current binding will be rejected, and the system will wait to receive the placement parameters for the next display viewport.

[0160] For example, if the placement parameter verification for display viewport B fails, it indicates that the conditions for establishing a new hosting relationship are not met, and the remote host container refuses to establish the hosting relationship between the view instance and display viewport B. It then waits to receive the placement parameters for the next display viewport.

[0161] S28, Send failure feedback information.

[0162] S29, Send failure feedback information.

[0163] For example, when the positioning parameter verification of viewport B fails, the remote host container can send the failure feedback information to the event channel and forward the failure feedback information to the host process through the event channel.

[0164] S30, outputs a display failure message on display viewport B.

[0165] For example, when the host process receives a display failure message, it can output the display failure message on display viewport B to provide feedback to the user that the object to be displayed is displaying abnormally.

[0166] For example, when the object to be displayed is media lyrics, the Widget binder can receive the placement parameters of display viewport B from the host process and send them to the canvas root view component corresponding to the media lyrics. When the canvas root view component receives the placement parameters of display viewport B, it can first validate the placement parameters. If the validation passes, it releases the existing carrier relationship between the view instance and display viewport A, establishes a new carrier relationship between the view instance and display viewport B, and establishes a corresponding new canvas control view host. It should be understood that when the display viewport changes, the view instance corresponding to the media lyrics is not rebuilt. The widget binder already holds the corresponding canvas root view component, and the canvas root view component already loads a simple lyrics view component; only the display viewport has changed.

[0167] Optionally, the remote host container can save the last display viewport position parameters of the view instance so that when switching display viewports, the saved display viewport position parameters can be directly compared with the position parameters of another display viewport to determine whether the position parameters have changed, thus avoiding duplicate creation of view instances and display errors.

[0168] Optionally, in response to a target construction instruction, a target view instance of the object to be displayed is constructed; if the display layout parameters of the object to be displayed are verified to be valid, a target carrying relationship between the target view instance and the display layout parameters is constructed; based on the target carrying relationship and the target view instance, a target display screen of the target view instance to be displayed in the display viewport is generated, wherein the display viewport is the visible object indicated by the display layout parameters; and the target display screen is displayed on the display viewport.

[0169] like Figure 3As shown, when an object needs to be displayed, a view instance of the object is first created. Only after the view instance is created and the display layout parameters of the display viewport pass verification is the view instance temporarily bound to a specific display viewport. This is done instead of binding the view instance synchronously with a display viewport during the creation process, thus permanently binding the view instance to a specific viewport. In other words, the view instance of the object is only rendered and displayed; it is not permanently bound to a specific display viewport. This allows for the release and re-establishment of the relationship between the view instance and the display viewport. The view instance remains constant; only the display viewport that carries the view instance changes. This enables the view instance to be reused without needing to be recreated every time the display viewport is switched. This allows for flexible multi-screen switching of view instances, also known as "redirection display between different display viewports," and reduces the system resources required for repeated creation of view instances. Furthermore, by constructing the view instance of the object to be displayed before binding it to the display viewport, the problem of misaligned establishment of the carrying relationship between the view instance and the display viewport can be avoided by receiving construction instructions from different display viewports in a short period of time, thus improving the accuracy of the carrying relationship establishment. For example, if construction instructions for display viewport A and display viewport B are received in quick succession, with the construction instruction for display viewport A preceding the one for display viewport B, if the carrying relationship between the view instance and display viewport A is being established, and then the construction instruction for display viewport B is received, the carrying relationship may be mistakenly established as being between the view instance and display viewport B, resulting in an incorrect carrying relationship establishment.

[0170] It should be noted that, Figure 3 All steps are in Figure 2 The corresponding embodiments are described in detail, and will not be repeated here.

[0171] It should be understood that the above examples are provided to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific values ​​or scenarios exemplified. Those skilled in the art can obviously make various equivalent modifications or variations based on the above examples, and such modifications or variations also fall within the scope of the embodiments of this application.

[0172] The above text combined Figures 1 to 3 The view display method provided in the embodiments of this application is described in detail below; the following will be combined with Figure 4 and Figure 6 The apparatus embodiments of this application are described in detail below. It should be understood that the apparatus in the embodiments of this application can perform the various methods described in the foregoing embodiments of this application, that is, the specific working processes of the various products described below can be referred to the corresponding processes in the foregoing method embodiments.

[0173] Figure 4This is a schematic diagram of the structure of the view display device provided in the embodiments of this application.

[0174] For example, such as Figure 4 As shown, the device 400 includes: Release module 410 is used to release the established bearing relationship between the target view instance and the first display viewport in response to a switching request for the display viewport of the target view instance when the target view instance is displayed in the first display viewport. The processing module 420 is used to establish a new carrying relationship between the target view instance and the second display viewport based on the second display viewport indicated by the switching request, so as to switch the target view instance to the second display viewport for display; wherein, during the switching of the display viewport, the target view instance remains unchanged.

[0175] In one possible implementation, the processing module 420 is further used for: Construct the instance identifier of the target view instance; Processing module 420 is specifically used for: Construct the viewport identifier for the second display viewport; Bind the instance identifier of the target view instance and the viewport identifier of the second display viewport to obtain a new carrying relationship.

[0176] In one possible implementation, the processing module 420 is specifically used for: Based on the new carrying relationship, the target view instance is loaded into the display canvas of the second display viewport; In the display canvas, the target view instance is rendered to generate the target display screen of the target view instance displayed in the second display viewport.

[0177] In one possible implementation, the processing module 420 is specifically used for: In the display canvas, the target view instance is rendered to generate the initial display screen of the target view instance displayed in the second display viewport; Based on the display scene of the second display viewport, the initial display screen is adjusted to obtain the target display screen.

[0178] In one possible implementation, the processing module 420 is further used for: Verify the display layout parameters of the second display viewport carried in the switching request; If the display layout parameters pass the verification, the step of establishing a new carrying relationship between the target view instance and the second display viewport based on the second display viewport indicated by the switching request is executed.

[0179] In one possible implementation, the processing module 420 is further used for: If all parameters in the display layout parameters are valid and authentication is successful, the display layout parameter validation is considered successful. If at least one of the display layout parameters is invalid, and / or authentication fails, the display layout parameter validation is determined to have failed.

[0180] In one possible implementation, the processing module 420 is further used for: In response to the target build instruction, a target view instance of the object to be displayed is constructed based on the target build parameters carried in the target build instruction and the identity of the object to be displayed.

[0181] In one possible implementation, the processing module 420 is further used for: Based on the identity identifier of the object to be displayed, an initial view instance is determined, wherein there is a correspondence between the initial view instance and the identity identifier of the object to be displayed; Based on the target construction parameters, the initial view instance is adjusted to generate the target view instance.

[0182] It should be noted that the aforementioned device 400 is embodied in the form of a functional module. The term "module" here can be implemented in software and / or hardware, without specific limitations.

[0183] For example, a "module" can be a software program, hardware circuit, or a combination of both that implements the above functions. Hardware circuits may include application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or combined processors) and memory for executing one or more software or firmware programs, combined logic circuits, and / or other suitable components that support the described functions.

[0184] Therefore, the modules of the various examples described in the embodiments of this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0185] Figure 5 This is a schematic diagram of the controller provided in the embodiments of this application.

[0186] For example, such as Figure 5As shown, the vehicle includes a controller 500, which includes a storage module 510 and a processing module 520. The storage module 510 stores executable program code 5101, and the processing module 520 is used to call and execute the executable program code 5101 to perform a view display method.

[0187] Figure 6 This is a schematic diagram of the vehicle structure provided in the embodiments of this application.

[0188] For example, such as Figure 6 As shown, the vehicle 600 includes a memory 610 and a processor 620, wherein the memory 610 stores executable program code 6101, and the processor 620 is used to call and execute the executable program code 6101 to perform a view display method.

[0189] This application can divide the vehicle into functional modules based on the above method example. For example, each module can correspond to a separate function module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0190] When each functional module is divided according to its corresponding function, the vehicle may include a release module and a processing module, etc. It should be noted that all relevant content regarding the steps involved in the above method embodiments can be referenced from the functional descriptions of the corresponding functional modules, and will not be repeated here.

[0191] The vehicle provided in this application is used to execute the view display method described above, and thus can achieve the same effect as the implementation method described above.

[0192] When using integrated units, the vehicle may include a processing module and a storage module. The processing module is used to control and manage the vehicle's movements. The storage module is used to support the vehicle in executing relevant program code and data.

[0193] The processing module may be a processor or a controller, which can implement or execute various exemplary logic blocks, modules, and circuits shown in conjunction with the disclosure of this application. The processor may also be a combination of functions that implement computing capabilities, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and microprocessors, etc., and the storage module may be a memory.

[0194] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the methods described in the foregoing embodiments. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, DVDs (Digital Video Discs), CD-ROMs (Compact Disc Read-Only Memory), microdrives, magneto-optical disks, ROMs (Read-Only Memory), RAMs (Random Access Memory), EPROMs (Erasable Programmable Read-Only Memory), EEPROMs (Electrically Erasable Programmable Read Only Memory), DRAMs (Dynamic Random Access Memory), VRAMs (Video Random Access Memory), flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), or any type of medium or device suitable for storing instructions and / or data.

[0195] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned related steps to implement a view display method in the above embodiments.

[0196] In addition, the vehicle provided in the embodiments of this application may specifically be a chip, component or module. The vehicle may include a connected processor and a memory. The memory is used to store instructions. When the vehicle is running, the processor may call and execute the instructions to make the chip execute a view display method in the above embodiments.

[0197] The vehicle, computer-readable storage medium, computer program product or chip provided in this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

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

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

[0200] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A view display method, characterized in that, The method includes: When the target view instance is displayed in the first display viewport, in response to a request to switch the display viewport of the target view instance, the established bearing relationship between the target view instance and the first display viewport is released; Based on the second display viewport indicated by the switching request, a new carrying relationship is established between the target view instance and the second display viewport, so as to switch the target view instance to be displayed in the second display viewport; During the switching of the display viewport, the target view instance remains unchanged.

2. The method according to claim 1, characterized in that, The method further includes: Construct the instance identifier of the target view instance; Establishing a new carrying relationship between the target view instance and the second display viewport includes: Construct the viewport identifier for the second display viewport; The instance identifier of the target view instance and the viewport identifier of the second display viewport are bound together to obtain the new carrying relationship.

3. The method according to claim 1, characterized in that, Switching the target view instance to the second display viewport includes: Based on the new carrying relationship, the target view instance is loaded into the display canvas of the second display viewport; In the display canvas, the target view instance is rendered to generate a target display screen of the target view instance displayed in the second display viewport.

4. The method according to claim 3, characterized in that, The step of rendering the target view instance in the display canvas to generate a target display screen of the target view instance displayed in the second display viewport includes: In the display canvas, the target view instance is rendered to generate an initial display screen of the target view instance displayed in the second display viewport; Based on the display scene of the second display viewport, the initial display screen is adjusted to obtain the target display screen.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The display layout parameters of the second display viewport carried in the switching request are verified; If the display layout parameters pass the verification, the step of establishing a new carrying relationship between the target view instance and the second display viewport based on the second display viewport indicated by the switching request is executed.

6. The method according to claim 5, characterized in that, The step of verifying the display layout parameters of the second display viewport carried in the switching request includes: If all parameters in the display layout parameters are valid and the identity authentication is successful, the display layout parameter verification is deemed successful. If at least one of the display layout parameters is invalid, and / or authentication fails, the display layout parameter verification is determined to have failed.

7. The method according to any one of claims 1 to 4, characterized in that, The method further includes: In response to a target construction instruction, a target view instance of the object to be displayed is constructed based on the target construction parameters carried in the target construction instruction and the identity identifier of the object to be displayed.

8. The method according to claim 7, characterized in that, The step of constructing a target view instance of the object to be displayed based on the target construction parameters carried in the target construction instruction and the identity identifier of the object to be displayed includes: Based on the identity identifier of the object to be displayed, an initial view instance is determined, wherein there is a correspondence between the initial view instance and the identity identifier of the object to be displayed; Based on the target construction parameters, the initial view instance is adjusted to generate the target view instance.

9. A controller, characterized in that, The controller includes: The storage module is used to store executable program code; A processing module is configured to call and run the executable program code from the storage module, causing the controller to perform the method as described in any one of claims 1 to 8.

10. A vehicle, characterized in that, The vehicles include: Memory, used to store executable program code; A processor for calling and running the executable program code from the memory, causing the vehicle to perform the method as described in any one of claims 1 to 8.

Images