Page view generation method, control method, medium, and device

Abstract

The application discloses a page view generation method, a control method, a medium and equipment. The page view generation method is applied to an intelligent cockpit system of a vehicle. The intelligent cockpit system comprises a target application, and the target application comprises a target page. The page view generation method comprises the following steps: acquiring a component library and a manifest file of the target application. The component library comprises a plurality of basic components. The manifest file comprises configuration information of a container corresponding to the basic components. The configuration information is used for describing attribute information and a view type of the basic components. A target basic component is acquired from the component library. The manifest file is parsed. A target container corresponding to the target basic component is generated. The target attribute information and a target initial view are arranged in the target container. The target attribute information and the target initial view are bound, so that a target view with the target attribute information is generated on the target page. The application can improve the development efficiency of the intelligent cockpit system.

Description

Technical Field

[0001] This application belongs to the field of intelligent cockpit system technology, and in particular relates to a page view generation method, control method, medium and device. Background Technology

[0002] In the field of smart cockpits, OEMs typically need to undertake the application development work of smart cockpit systems in order to improve the performance of application software in smart cockpits.

[0003] Currently, in the application development process of intelligent cockpit systems, such as in the development of application pages, code design requires manual writing of all page layouts, followed by implementation of business logic within the layouts. This results in a large workload for writing code, high development efficiency, and low efficiency. Summary of the Invention

[0004] Embodiments of this application provide a page view generation method, control method, medium, and device, which can at least to some extent reduce the development workload of target applications for intelligent cockpit systems and improve development efficiency.

[0005] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0006] The first aspect of this application provides a page view generation method applied to a vehicle's intelligent cockpit system, the intelligent cockpit system including a target application, the target application including a target page, the method comprising:

[0007] Obtain the component library and manifest file of the target application. The component library includes multiple basic components, and the manifest file includes the configuration information of the containers corresponding to the basic components. The configuration information is used to describe the attribute information and view type of the basic components.

[0008] Obtain the target basic component from the component library, parse the manifest file, and generate a target container corresponding to the target basic component. The target container contains target attribute information and target initial view.

[0009] The target attribute information and the target initial view are bound together to generate a target view with the target attribute information on the target page.

[0010] Optionally, the target container includes an information storage unit and a view carrying unit, wherein the information storage unit is used to store the target attribute information, and the view carrying unit is used to carry the target initial view;

[0011] The step of binding the target attribute information and the target initial view includes:

[0012] The information storage unit and the view carrying unit are bound together so that the target attribute information and the target initial view are bound together.

[0013] Optionally, the target container further includes a control unit, and after the target page generates a target view with the target attribute information, the method further includes:

[0014] In response to a user's attribute change operation, the target view sends the attribute change operation to the target container;

[0015] The target container forwards the attribute change operation to the control unit, which modifies the target attribute information according to the attribute change operation so as to update the target view based on the binding relationship between the information storage unit and the view carrying unit.

[0016] Optionally, before obtaining the component library and manifest file of the target application, the method further includes:

[0017] Obtain the attribute requirement information of the target basic component, and at least one reference component among the multiple basic components, wherein the reference component is a component that already has the configuration information of the container;

[0018] If a target reference component exists among the at least one reference component, the configuration information of the reference control unit corresponding to the target reference component is used as the basic configuration information of the control unit corresponding to the target basic component, wherein the similarity between the attribute requirement information of the target reference component and the attribute requirement information of the target basic component is greater than or equal to a preset first threshold.

[0019] Optionally, obtaining the manifest file includes:

[0020] Obtain the application requirement information of the target application for the current vehicle model;

[0021] If there is a historical vehicle model whose similarity to the application requirement information of the current vehicle model is greater than or equal to a preset second threshold, then the historical list file of the historical vehicle model is obtained, and the historical list file is filtered based on preset filtering rules to obtain the list file of the target application of the current vehicle model.

[0022] Optionally, before obtaining the component library and manifest file of the target application, the method further includes:

[0023] Obtain the interface identifier file provided by the vehicle service gateway, wherein the interface identifier file includes multiple interface identifiers;

[0024] The target interface identifier corresponding to the target basic component is used as the configuration information of the target container object and configured in the manifest file.

[0025] A second aspect of this application provides a control method, the method further comprising:

[0026] Based on the target view in any of the methods described in the first aspect, in response to the user's business control operations;

[0027] A control command is generated based on the business control operation, and the control command and the target interface identifier are sent to the vehicle service gateway, so that the vehicle service gateway can identify the corresponding business controller based on the target interface identifier and forward the control command to the business controller. The target attribute information includes the target interface identifier.

[0028] Optionally, the target container includes a control unit, and the response to the user's service control operation includes:

[0029] The target view responds to the user's business control operation and sends the business control operation to the target container;

[0030] The step of generating control instructions based on the business control operation and sending the control instructions and target interface identifier to the vehicle service gateway includes:

[0031] The target container sends the service control operation to the control unit, which generates a control command based on the service control operation and sends the control command and the target interface identifier to the vehicle service gateway.

[0032] According to a third aspect of the embodiments of this application, a computer-readable storage medium is provided, the computer-readable storage medium storing at least one computer program instruction, the at least one computer program instruction being loaded and executed by a processor to perform an operation as described in any of the methods of the first aspect, or an operation as described in the method of the second aspect.

[0033] According to a fourth aspect of the embodiments of this application, an electronic device is provided, including one or more processors and one or more memories, wherein at least one piece of program code is stored in the one or more memories, the at least one piece of program code being loaded and executed by the one or more processors to perform an operation as described in any of the methods of the first aspect, or an operation as described in any of the methods of the second aspect.

[0034] The one or more technical solutions provided in the embodiments of the present invention achieve at least the following technical effects or advantages:

[0035] The page view generation method provided in this application is applied to a vehicle's intelligent cockpit system. The intelligent cockpit system includes a target application, and the target application includes a target page. The method includes: obtaining a component library and a manifest file of the target application. The component library includes multiple basic components, and the manifest file includes configuration information of containers corresponding to the basic components. The configuration information describes the attribute information and view type of the basic components. The method also includes: obtaining target basic components from the component library; parsing the manifest file to generate target containers corresponding to the target basic components; setting target attribute information and target initial views within the target containers; and binding the target attribute information and target initial views to generate a target view with target attribute information on the target page. Therefore, by pre-building a component library and a configuration manifest file, the attribute information of the view is abstracted onto the manifest file, improving the business integration and logic reuse capabilities of components and containers. This reduces the amount of code writing, lowers code coupling, reduces development workload, and improves development efficiency.

[0036] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0037] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0038] Figure 1 A flowchart illustrating a page view generation method according to an embodiment of this application is shown;

[0039] Figure 2 A flowchart of the control method according to an embodiment of this application is shown;

[0040] Figure 3 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0041] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0042] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0043] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0044] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0045] It should also be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such uses of these terms can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described.

[0046] In the field of smart cockpits, OEMs typically need to undertake the application development work of smart cockpit systems in order to improve the performance of application software in smart cockpits.

[0047] Currently, in the application development process of intelligent cockpit systems, such as in the application page development process, code design requires manual writing of all page layouts and then implementation of the business logic in the layout. For example, if a page needs to design 10 buttons, and if the interfaces of the 10 buttons are the same but the parameters are different, then it is necessary to write code 10 times and modify the parameters to get the 10 buttons. The workload of writing code is large, the development workload is large, and the development efficiency is low.

[0048] In view of this, the first aspect of the present application provides a page view generation method, which can reduce the development workload of the target application of the intelligent cockpit system to a certain extent and improve development efficiency.

[0049] The page view generation method of this application embodiment will be described below with reference to the specific accompanying drawings.

[0050] See Figure 1 The flowchart illustrates a page view generation method according to an embodiment of this application.

[0051] The first aspect of this application provides a page view generation method applied to a vehicle's intelligent cockpit system. The intelligent cockpit system includes a target application, the target application includes a target page, and the method can be executed on a computer operated by a developer. The method includes:

[0052] Step S10. Obtain the component library and manifest file of the target application. The component library includes multiple basic components, and the manifest file includes the configuration information of the containers corresponding to the basic components. The configuration information is used to describe the attribute information and view type of the basic components.

[0053] It is understood that the embodiments of this application may rely on the Android development platform to generate the page view of the target application.

[0054] The target application can refer to the settings application, which is a general application in the Android system. Users can control relevant attributes of the system, such as sound and brightness, through the settings application. It is understood that in the Android system, the settings application is an application with a high degree of component reusability. Therefore, the target application can also be other applications with high component reusability, which is not limited here.

[0055] It should be noted that during the development of intelligent cockpit systems, component reusability is typically assessed based on development requirements, leading to the construction of a general-purpose common component library. However, when targeting specific applications, the compatibility between this general-purpose common component library and the target application may be poor, for example, only meeting 70% of the requirements. Based on this, developers can extend or modify the common component library according to the development requirements of the target application, such as adding components, to build a component library that matches the target application. This component library includes several views. It is understood that at this stage, the views do not contain any business logic and do not have attributes such as style, size, width, or length. Therefore, in this embodiment, the views at this stage are defined as basic components.

[0056] Having built the component library, it is necessary to further clarify how to utilize it. This embodiment establishes a correspondence between basic components and containers, using the containers to carry the attribute information and view types of the basic components, and configuring the containers in the manifest file, thereby achieving code decoupling and improving the reusability of components and containers. The containers and manifest files are further described below.

[0057] It is understood that after the target application is developed, it is represented as one or more pages on the human-computer interaction interface (HMI). In order to carry the information in the human-computer interaction page, this application proposes the concept of a container (Preference), that is, the container can carry information on the human-computer interaction interface (HMI) (including one or more pages).

[0058] When configuring containers in the manifest file, it's necessary to specify which attributes should be configured. For example, if a page needs to design 10 buttons, and the only difference between the buttons might be their icons, then when configuring the container for each button component, the differentiated icon attributes need to be configured. Additionally, attributes for components such as titles and subtitles can also be configured.

[0059] In addition, containers are used to define default layout files. These layout files load the target base components from the component library, dragging and dropping them into the view's layout information (i.e., displaying the initial view of the target base components on the page). At this point, the initial view does not yet have attribute information. Furthermore, view style information, such as length and width, can be configured in the manifest file. Thus, one container corresponds to one base component with a unified style. It's understandable that the default layout file doesn't need to be configured in the manifest file, but it can be configured there for special requirements. For example, in a specific scenario, the width and height of a button component might need to be modified to other parameters; in this case, a custom layout file (containing the default layout file and the redefined layout parameters) can be defined and configured in the manifest file.

[0060] In addition, to implement the business logic of the components, the container can also define control units contained in the container when it is defined. These control units can use attribute information as input parameters, so that the control units can modify the view according to the attribute information.

[0061] Based on the preceding information, we now understand the components of a component library, the definition of containers, and the configuration of the manifest file. Therefore, by configuring the configuration information of each container in the manifest file according to a preset order (e.g., from top to bottom on a page), we can obtain the complete configuration information for a page.

[0062] In some embodiments, the manifest file may be in XML (Extensible Markup Language) format.

[0063] Step S20. Obtain the target basic component from the component library, parse the manifest file, and generate a target container corresponding to the target basic component. The target container contains target attribute information and a target initial view.

[0064] It is understandable that the target basic component can be obtained from the component library by querying the component library using its index. The target basic component can be a switch component or a button component.

[0065] It's important to note that parsing the manifest file is also the process of instantiating the target container. In other words, after parsing the manifest file, the resulting target container is automatically populated with target attribute information and an initial target view. This reduces coding work and improves development efficiency.

[0066] In some embodiments, after parsing the manifest file, the resulting target container includes an information storage unit (info) and a view carrying unit (view). The information storage unit is used to store target attribute information, and the view carrying unit is used to carry the initial view corresponding to the target basic component.

[0067] In other words, the process of parsing the manifest file is also a process of instantiating the information storage unit, that is, filling the information storage unit with the target attribute information. Furthermore, the view-carrying unit can use the aforementioned layout file to carry the initial view.

[0068] In some embodiments, after parsing the manifest file, the resulting target container includes an information storage unit, a view-bearing unit, and a controller. The controller can use the target attribute information within the information storage unit as input parameters; that is, the controller manipulates the target attribute information to modify the view. For example, if the information storage unit has four attributes, the controller can control and modify these four attributes to modify the view.

[0069] Step S30. Bind the target attribute information and the target initial view to generate a target view with the target attribute information on the target page.

[0070] In some embodiments, the target container includes an information storage unit and a view carrying unit, wherein the information storage unit is used to store the target attribute information, and the view carrying unit is used to carry the target initial view;

[0071] The step of binding the target attribute information and the target initial view includes:

[0072] The information storage unit and the view carrying unit are bound together so that the target attribute information and the target initial view are bound together.

[0073] Understandably, when binding the information storage unit and the view hosting unit, the `databinding` method in the Android development system can be called to perform the binding action. Specifically, `databinding` passes the target attribute information from the information storage unit to the layout file of the view hosting unit. After receiving the target attribute information, the layout file populates the layout file with the target attribute information, thus generating the target view by combining the target attribute information with the initial target view. In other words, whenever the target attribute information in the information storage unit changes, the corresponding target view will also be refreshed.

[0074] In some embodiments, the target container further includes a control unit, and after the target page generates a target view having the target attribute information, the method further includes:

[0075] Step S40. In response to the user's attribute change operation, the target view sends the attribute change operation to the target container;

[0076] Understandably, after the target page generates the target view, for example, if the target view is a view of a switch item, the user can change the attribute of that switch item, such as clicking the switch item to change the attribute from "on" to "off". Upon receiving this attribute change operation, the target view will send the attribute change operation to the target container.

[0077] Step S50. The target container forwards the attribute change operation to the control unit. The control unit modifies the target attribute information according to the attribute change operation so as to update the target view based on the binding relationship between the information storage unit and the view carrying unit.

[0078] Based on the above, the control unit can use the target attribute information within the information storage unit as input parameters. That is, the control unit manipulates the target attribute information to modify the view. For example, if a user clicks on a switch item, the switch item's title needs to be changed, such as from "on" to "off." This is equivalent to the default title being configured in the manifest file, which is now modified by the control unit. After the user clicks the switch item, the target view receives the click operation and exposes it to the target container. The target container then forwards it to the control unit, allowing the control unit to write business logic (modify input parameters) based on the click operation, thereby controlling the changes in the target view's parameters and updating the target view.

[0079] Based on the above disclosure, this application's embodiments, by pre-building a component library and a configuration manifest file, abstract the view's attribute information onto the manifest file, improving the business logic integration and reuse capabilities of components and containers. This reduces the amount of code to write, lowers code coupling, reduces development workload, and improves development efficiency. Furthermore, when multiple target views need to be built on a target page, if the differences between the multiple target views are only in their position on the page, they can be built simultaneously using the same container, further reducing the amount of code to write and improving development efficiency.

[0080] In some embodiments, prior to obtaining the component library and manifest file of the target application, the method further includes:

[0081] Step S01. Obtain the attribute requirement information of the target basic component, and at least one reference component among the multiple basic components, wherein the reference component is a component that already has the configuration information of the container;

[0082] Understandably, during the development of a target application, multiple pages may be developed, each containing views corresponding to multiple components. Therefore, if the target container corresponding to the current target basic component is configured with the configuration information for containers corresponding to other basic components in the manifest file before being configured with the target container corresponding to the current target basic component, and given that the input parameters of the control unit are attribute information, when configuring the control unit of the target basic component, the similarity between the attribute requirements of the current target basic component and other basic components can be used to determine whether the configuration information of the control units of other basic components can be directly reused in the control unit corresponding to the current target basic component, thereby reducing the configuration workload of the control unit.

[0083] Step S02. If a target reference component exists among the at least one reference component, the configuration information of the reference control unit corresponding to the target reference component is used as the basic configuration information of the control unit corresponding to the target basic component, wherein the similarity between the attribute requirement information of the target reference component and the attribute requirement information of the target basic component is greater than or equal to a preset first threshold.

[0084] For example, if the current target basic component is a switch item and the target reference component is a button, and the button has attributes such as title, subtitle, and icon, and the switch item has the same attribute requirements as the button, or the switch item has additional attribute requirements on top of the button's attribute requirements, such as needing to add on and off values, then when configuring the control unit of the switch item, the control unit of the button can be used directly, or further configuration can be made on the basis of the button's control unit, thereby achieving control unit reuse and reducing workload.

[0085] For example, both switches and buttons require four identical attribute information. Based on the binding relationship between attribute information and the view, this attribute information can affect both switches and buttons. For instance, the attribute information includes the title. This title information is stored in the information storage unit of the container corresponding to the button. After the container receives a touch event, since the control unit has common input parameters, such as `set data`, when the user clicks the button component, the container calls the `set data` method to the control unit. After receiving the user's click operation, the control unit executes subsequent business actions, such as changing the title to "closed". Thus, after the title attribute changes, it calls the method of the target view. `databinding` will directly call the button's text refresh method, and the switch will also receive the attribute change message. When the text attribute changes, the component being operated on becomes the switch, but the input parameter is the same—a piece of text. If the components have almost identical attributes, or contain each other, the control unit can be reused.

[0086] In some embodiments, obtaining the manifest file includes:

[0087] Step S21. Obtain the application requirement information of the target application for the current vehicle model;

[0088] Step S22. If there is a historical vehicle model whose similarity to the application requirement information of the current vehicle model is greater than or equal to a preset second threshold, then obtain the historical list file of the historical vehicle model, filter the historical list file based on the preset filtering rules, and obtain the list file of the target application of the current vehicle model.

[0089] It is understandable that when developing target applications for different vehicle models, the workload would be substantial if each model required a separate manifest file. Therefore, this application's embodiment analyzes the similarity between the application requirements information of the current vehicle model and historical models. When the similarity is greater than or equal to a second threshold, such as 80%, 90%, or 95%, the historical manifest file of the historical model is used as the basis for the manifest file of the current model. This reduces the workload of configuring manifest files and further improves development efficiency.

[0090] For example, each vehicle model has a corresponding configuration word, which can be parsed using attributes in the manifest file. For instance, the configuration word for model A might indicate a high-end configuration, while the configuration word for model B might indicate a low-end configuration. Therefore, when applying the manifest file for model A to model B, the configuration word for model B can be parsed based on the manifest file, and then filtered using preset rules (e.g., only retaining features supported by the low-end model). Thus, the manifest file for model A can be directly applied to model B, reducing the workload of the manifest file. Furthermore, when generating the target view for model B based on the manifest file, only the target view matching the features of model B is loaded on the page.

[0091] In some embodiments, if the requirements of the target application differ significantly between the current vehicle model and historical vehicle models, the manifest file can be reused to a certain extent through overlay packaging provided by the Android system. For example, if the manifest file for vehicle model A has 10 entries, and the manifest file for vehicle model B requires 20 entries, with 10 entries being identical to those for vehicle model A, then static packaging and compilation can be used to achieve vehicle model reuse.

[0092] In some embodiments, prior to obtaining the component library and manifest file of the target application, the method further includes:

[0093] Obtain the interface identifier file provided by the vehicle service gateway, wherein the interface identifier file includes multiple interface identifiers;

[0094] The target interface identifier corresponding to the target basic component is used as the configuration information of the target container object and configured in the manifest file.

[0095] It's important to note that in the field of smart cockpits, OEMs use various communication buses within the vehicle body domain to send commands to the body controller to achieve control effects. Among these, AAOS (Android Automotive Operating System) provides a CarService gateway to offer a control interface to Android applications, enabling communication with the ECU (Electronic Control Unit). However, because body communication buses include SOA (Service-Oriented Architecture), CAN (Controller Area Network), and LIN (Local Interconnect Network) architectures, the communication methods and usage are not uniform. This leads to conflicts when the same software system for a target application is adapted to multiple communication architectures, resulting in significant adaptation difficulties and high maintenance costs.

[0096] Based on the above, this application embodiment abstracts the interface identification file provided by the vehicle service gateway into a manifest file, thereby enabling the reuse of the same software system of the target application on different vehicle models, reducing development complexity, maintenance costs, and improving development efficiency.

[0097] It should be noted that the interface identifier file provided by the vehicle service gateway in the vehicle body may differ depending on the communication bus. This interface identifier file includes several interface identifiers (carlib), each of which is used for one of the service controllers in the vehicle body domain. For example, 10 represents the window controller, 11 represents the lighting controller, and 12 represents the music controller, etc.

[0098] Based on the above, this application embodiment transforms the interface identifier file into a resource file in the Android system. For example, the carlib interface is parsed into an XML resource file using a plugin script to obtain the interface parameter definition. Therefore, the manifest file can apply the resource file during subsequent configuration. For instance, when configuring each container, a specific interface identifier can be configured as one of the attribute information within the container.

[0099] Since the interface identifier file is converted into a resource file in the Android system, and this resource file is only referenced when configuring the manifest file, the interface identifier file is decoupled from the code. There is no need to write code to describe the interface identifier, which further reduces the workload of writing code.

[0100] Furthermore, when developing target applications for different vehicle models, it is only necessary to use the interface identifier file provided by the vehicle service gateway of that vehicle model to configure the manifest file. In other words, when developing target applications for different vehicle models, it is only necessary to modify the configuration information of the manifest file to solve problems such as different communication methods and usage methods for different vehicle models, and conflicts in the same software system of the target application in adapting to multiple communication architectures.

[0101] See Figure 2 The flowchart of the control method according to an embodiment of this application is shown.

[0102] A second aspect of this application provides a control method, the method further comprising:

[0103] Step S101. Based on the target view in any of the methods described in the first aspect, respond to the user's business control operation;

[0104] It should be noted that after the target view is generated, it can be loaded into the vehicle's central control system (such as the central control screen) for user operation. The target view can correspond to the views of various business units within the vehicle body, such as the views of windows, wipers, lights, and air conditioning. Therefore, business control operations can be operations that control a specific business unit, such as controlling the closing of a window.

[0105] Step S102. Generate a control command according to the service control operation, and send the control command and the target interface identifier to the vehicle service gateway, so that the vehicle service gateway can identify the corresponding service controller according to the target interface identifier and forward the control command to the service controller, wherein the target attribute information includes the target interface identifier.

[0106] The target container includes a control unit, and the response to the user's service control operation includes:

[0107] The target view responds to the user's business control operation and sends the business control operation to the target container;

[0108] For example: The target view is the view corresponding to the car window business unit, and the user operates the control to close the car window on the page.

[0109] The step of generating control instructions based on the business control operation and sending the control instructions and target interface identifier to the vehicle service gateway includes:

[0110] The target container sends the service control operation to the control unit, which generates a control command based on the service control operation and sends the control command and the target interface identifier to the vehicle service gateway.

[0111] According to a third aspect of the embodiments of this application, a computer-readable storage medium is provided, the computer-readable storage medium storing at least one computer program instruction, the at least one computer program instruction being loaded and executed by a processor to perform the operation as described in any of the methods in the first aspect.

[0112] Computer-readable storage media may be portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the computer-readable storage medium of this application is not limited thereto. In this application, the readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0113] A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0114] Program code for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0115] See Figure 3 This is a schematic diagram of the structure of a computer system suitable for implementing the embodiments of this application in a vehicle.

[0116] According to a fourth aspect of the embodiments of this application, an electronic device is provided, including one or more processors and one or more memories, wherein at least one piece of program code is stored in the one or more memories, and the at least one piece of program code is loaded and executed by the one or more processors to perform the operation as performed by any of the methods in the first aspect.

[0117] like Figure 3 As shown, the electronic device 400 is manifested in the form of a general-purpose computing device. The components of the electronic device 400 may include, but are not limited to: at least one processing unit 410, at least one storage unit 420, and a bus 430 connecting different system components (including storage unit 420 and processing unit 410).

[0118] The storage unit stores program code, which can be executed by the processing unit 410, causing the processing unit 410 to perform the steps described in the "Embodiment Method" section above according to various exemplary embodiments of this application.

[0119] Storage unit 420 may include readable media in the form of volatile storage units, such as random access memory (RAM) 421 and / or cache 422, and may further include read-only memory (ROM) 423.

[0120] Storage unit 420 may also include a program / utility 424 having a set (at least one) of program modules 425, such program modules 425 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0121] Bus 430 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0122] Electronic device 400 can also communicate with one or more external devices 500 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 400, and / or with any device that enables electronic device 400 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed through I / O (input / output) interface 450, which can also be connected to display unit 440 to display the communication content. Furthermore, electronic device 400 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public network, such as the Internet) through network adapter 460. As shown, network adapter 460 communicates with other modules of electronic device 400 via bus 430. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0123] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Other examples and embodiments are within the scope and spirit of this invention and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Furthermore, the functional units can be integrated into a single processing unit, or each unit can exist physically separately, or two or more units can be integrated into a single unit.

[0124] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be 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 system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0125] The units described as separate components may or may not be physically separate. Similarly, the components of the control device may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0126] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0127] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for generating a page view, characterized in that, A smart cockpit system for vehicles, the smart cockpit system including a target application, the target application including a target page, the method including: Obtain the component library and manifest file of the target application. The component library includes multiple basic components, and the manifest file includes configuration information of the containers corresponding to the basic components. The configuration information is used to describe the attribute information and view type of the basic components, and the containers are used to carry the attribute information and view type of the basic components. Obtain the target basic component from the component library, parse the manifest file, and generate a target container corresponding to the target basic component. The target container contains target attribute information and target initial view. The target attribute information and the target initial view are bound together to generate a target view with the target attribute information on the target page; Prior to obtaining the component library and manifest file of the target application, the method further includes: Obtain the interface identifier file provided by the vehicle service gateway. The interface identifier file includes multiple interface identifiers, each of which is used to represent one of the service controllers in the vehicle body domain. The interface identifier file provided by the vehicle service gateway is different when the communication bus of the vehicle is different. The target interface identifier corresponding to the target basic component is used as the configuration information of the target container and configured in the manifest file.

2. The method according to claim 1, characterized in that, The target container includes an information storage unit and a view carrying unit. The information storage unit is used to store the target attribute information, and the view carrying unit is used to carry the initial view of the target. The step of binding the target attribute information and the target initial view includes: The information storage unit and the view carrying unit are bound together so that the target attribute information and the target initial view are bound together.

3. The method according to claim 2, characterized in that, The target container further includes a control unit, and after the target page generates a target view with the target attribute information, the method further includes: In response to a user's attribute change operation, the target view sends the attribute change operation to the target container; The target container forwards the attribute change operation to the control unit, which modifies the target attribute information according to the attribute change operation so as to update the target view based on the binding relationship between the information storage unit and the view carrying unit.

4. The method according to any one of claims 1-3, characterized in that, Before obtaining the component library and manifest file of the target application, the method further includes: Obtain the attribute requirement information of the target basic component, and at least one reference component among the multiple basic components, wherein the reference component is a component that already has the configuration information of the container; If a target reference component exists among the at least one reference component, the configuration information of the reference control unit corresponding to the target reference component is used as the basic configuration information of the control unit corresponding to the target basic component, wherein the similarity between the attribute requirement information of the target reference component and the attribute requirement information of the target basic component is greater than or equal to a preset first threshold.

5. The method according to any one of claims 1-3, characterized in that, Obtaining the manifest file includes: Obtain the application requirement information of the target application for the current vehicle model; If there is a historical vehicle model whose similarity to the application requirement information of the current vehicle model is greater than or equal to a preset second threshold, then the historical list file of the historical vehicle model is obtained, and the historical list file is filtered based on preset filtering rules to obtain the list file of the target application of the current vehicle model.

6. A control method, characterized in that, The method further includes: Based on the target view in any of the methods described in claims 1-5, in response to user business control operations; A control command is generated based on the business control operation, and the control command and the target interface identifier are sent to the vehicle service gateway, so that the vehicle service gateway can identify the corresponding business controller based on the target interface identifier and forward the control command to the business controller. The target attribute information includes the target interface identifier.

7. The method according to claim 6, characterized in that, The target container includes a control unit, and the response to the user's service control operation includes: The target view responds to the user's business control operation and sends the business control operation to the target container; The step of generating control instructions based on the business control operation and sending the control instructions and target interface identifier to the vehicle service gateway includes: The target container sends the service control operation to the control unit, which generates a control command based on the service control operation and sends the control command and the target interface identifier to the vehicle service gateway.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one computer program instruction, which is loaded and executed by a processor to perform the operation performed by the method as described in any one of claims 1-5, or the operation performed by the method as described in claim 6 or 7.

9. An electronic device, characterized in that, It includes one or more processors and one or more memories, wherein at least one piece of program code is stored in the one or more memories, and the at least one piece of program code is loaded and executed by the one or more processors to perform the operation performed by the method as described in any one of claims 1-5, or the operation performed by the method as described in claim 6 or 7.

Images