A vehicle-mounted application system, componentized processing method, device and medium

Abstract

The application relates to the technical field of vehicle-mounted application, and provides a vehicle-mounted application system, which comprises a basic layer, a vehicle model service layer, a public service layer, a user interface adaptation layer and an application configuration management layer; the basic layer is used for establishing corresponding basic components according to different vehicle model service functions; the vehicle model service layer is used for determining a vehicle model and creating a vehicle model component corresponding to the vehicle model service; the public service layer is used for extracting public service logic of the vehicle model service layer and creating a public service component corresponding to the public service logic by relying on the basic component and the vehicle model component; the user interface adaptation layer is used for establishing an adaptation component corresponding to the vehicle model component; and the application configuration management layer is used for constructing an application according to the corresponding basic component, the public service component, the vehicle model component and the adaptation component, so as to complete the construction of the vehicle-mounted application system. The application can shorten the adaptation time of the vehicle-mounted application and improve the adaptation efficiency of the vehicle-mounted application.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle application, in particular to a vehicle application system, device and medium. BACKGROUND

[0002] The vehicle system is an interface of vehicle hardware and upper software, including management of hardware, software and data resources of the vehicle system, providing support for the upper software. The vehicle application utilizes the resources of the vehicle system to provide various forms of user interface, helping the driver to provide auxiliary driving, semi-automatic driving, and even automatic driving.

[0003] However, the existing vehicle application system has less hierarchical componentization configuration, and the components of each layer are not finely divided, which can only be adapted to a small number of vehicle models. Moreover, the existing vehicle application system generally adopts an interface callback mode to process communication between business layers, which has poor scalability. When the number of vehicle application interfaces increases, the stability of the vehicle application becomes worse, resulting in a long adaptation time and low adaptation efficiency of the vehicle application. SUMMARY

[0004] In view of the above-mentioned shortcomings of the prior art, the present application provides a vehicle application system, a componentization processing method, a device and a medium to solve the above technical problems.

[0005] The vehicle application system provided by the present application comprises:

[0006] A basic layer is configured to establish corresponding basic components according to different vehicle model business functions;

[0007] A vehicle model business layer is configured to determine a vehicle model and create a vehicle model component corresponding to a vehicle model business;

[0008] A public business layer is configured to extract a public business logic of the vehicle model business layer and create a public business component corresponding to the public business logic in dependence on the basic component and the vehicle model component;

[0009] A user interface adaptation layer is configured to establish an adaptation component corresponding to the vehicle model component; and

[0010] An application configuration management layer is configured to construct an application according to the corresponding basic component, the public business component, the vehicle model component and the adaptation component, and complete construction of the vehicle application system.

[0011] In an embodiment of the present application, the basic component comprises a network request component, a log auxiliary component, a file storage component, a class component, a conversion tool component, a life cycle management component and a plurality of third-party components.

[0012] In an embodiment of the present application, the network request component, the log auxiliary component, the file storage component, the class component, the conversion tool component, the life cycle management component, and the third-party components are independent of each other.

[0013] In an embodiment of the present application, the vehicle type component includes a software development component and different vehicle type service components, which are established by the software development component.

[0014] In an embodiment of the present application, the common service component includes a download service component, a network request encapsulation component, a storage component, a user interface component, a callback processing component, an entity state processing component, a data management component, and a data processing component.

[0015] In an embodiment of the present application, the download service component, the network request encapsulation component, the storage component, the user interface component, the callback processing component, the entity state processing component, the data management component, and the data processing component are independent of each other.

[0016] In an embodiment of the present application, the user interface adaptation layer is established in dependence on the vehicle type service layer, the adaptation components correspond to the vehicle type service components, and the adaptation components are independent of each other.

[0017] The present application also provides a vehicle-mounted application componentization processing method, which includes:

[0018] Dividing different vehicle type service functions in the basic layer to generate corresponding basic components;

[0019] Extracting common service logic of the common service layer of different vehicle types, and dividing the common service logic in dependence on the basic components to generate common service components;

[0020] Packaging the basic components and the common service components, and uploading the packaged files to a remote server;

[0021] Inputting different vehicle type services into the vehicle type service layer, and depending on the basic components and the common service components of the remote server to generate vehicle type components corresponding to the vehicle type services;

[0022] Dividing vehicle type services in the user interface adaptation layer in dependence on the basic components, the common service components, and the vehicle type components of the remote server to generate adaptation components;

[0023] Within the application configuration management layer, the application is constructed based on the basic components, common business components, vehicle model components, and adaptation components corresponding to the vehicle model business, thereby generating the vehicle model application.

[0024] The present invention also provides an electronic device, the electronic device comprising:

[0025] One or more processors;

[0026] A storage device for storing one or more programs, which, when executed by the one or more processors, cause the electronic device to operate the vehicle application system as described in any one of claims 1 to 7.

[0027] The present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer processor, causes the computer to run the vehicle application system of any one of claims 1 to 7.

[0028] The beneficial effects of this invention are as follows: This invention establishes multiple different basic components at the base layer, creates vehicle model components corresponding to vehicle model business in the vehicle model business layer, extracts the common business logic of the vehicle model business layer in the common business layer, and creates common business components corresponding to the common business logic based on the basic components and vehicle model components. In the user interface adaptation layer, an adaptation component corresponding to the vehicle model component is established, and the application is built based on the corresponding basic components, common business components, vehicle model components, and adaptation components to complete the construction of the in-vehicle application system, shorten the adaptation time of the in-vehicle application, and improve the adaptation efficiency of the in-vehicle application.

[0029] 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

[0030] 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:

[0031] Figure 1 This is a schematic diagram illustrating the implementation environment of an in-vehicle application system, as shown in an exemplary embodiment of this application.

[0032] Figure 2 This is a schematic diagram of the system architecture of an adaptation structure for an in-vehicle application system, as illustrated in an exemplary embodiment of this application.

[0033] Figure 3This is a schematic flowchart illustrating a component-based processing method for an in-vehicle application, as shown in an exemplary embodiment of this application.

[0034] Figure 4 This is a timing diagram illustrating the component-based adaptation of an in-vehicle application, as shown in an exemplary embodiment of this application.

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

[0036] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0037] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0038] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0039] First, it's important to clarify that in existing intelligent vehicles, the in-vehicle system serves as the interface between the in-vehicle hardware and upper-layer software. This includes managing the hardware, software, and data resources of the in-vehicle system and providing support for the upper-layer software. In-vehicle applications utilize these resources to provide various user interfaces, assisting drivers with assisted driving, semi-autonomous driving, and even autonomous driving. However, existing in-vehicle application systems have limited configuration layers and insufficient component breakdown at each layer, allowing adaptation to only a small number of vehicle models. Furthermore, existing in-vehicle application systems generally use interface callbacks to handle communication between business layers, resulting in poor scalability. The more interfaces an in-vehicle application has, the worse its stability becomes. The componentization of in-vehicle applications adopts a software architecture design pattern (Model-View-ViewModel, MVVM) for system development. It globally uses observable data storage classes (LiveData) to achieve single, trusted source monitoring, ensuring the entire in-vehicle application system remains in a predictable state and reducing its instability. In other application scenarios, the in-vehicle application system can be configured according to actual conditions; the embodiments in this application do not impose such limitations.

[0040] Figure 1 This is a schematic diagram illustrating the implementation environment of an in-vehicle application system, as shown in an exemplary embodiment of this application. Figure 1 As shown, a basic layer can be established using the in-vehicle system installed on the smart terminal 110, and corresponding basic components can be established according to different business functions. A vehicle model business layer is established based on the basic layer, and vehicle model components corresponding to the vehicle model business are established within this layer. The common business logic of the vehicle model business layer is extracted to establish a common business layer, and common business components corresponding to this common business logic are established within this layer. A user interface adaptation layer is established based on the vehicle model business layer, and corresponding adaptation components are established according to the vehicle model components. Finally, the application is built based on the corresponding basic components, common business components, vehicle model components, and adaptation components, completing the construction of the in-vehicle application system. Figure 1 The smart terminal 110 shown can be any terminal device that supports the installation of in-vehicle application systems, such as cars of various models, but is not limited to this. Figure 1The server 120 shown is a server, which can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. No restrictions are placed on this. The smart terminal 110 can communicate with the server 120 via wireless networks such as 3G (third-generation mobile information technology), 4G (fourth-generation mobile information technology), and 5G (fifth-generation mobile information technology). No restrictions are placed on this either. Because current in-vehicle application systems have fewer configuration layers and insufficient component breakdown at each layer, they can only be adapted to a limited number of vehicle models. Furthermore, existing in-vehicle application systems generally use interface callbacks to handle communication between business layers, resulting in poor scalability. The more interfaces an in-vehicle application has, the worse its stability becomes. To address these issues, embodiments of this application propose an in-vehicle application system, an electronic device, a computer-readable storage medium, and a computer program product, which will be described in detail below.

[0041] Please see Figure 2 As shown, Figure 2This is a schematic diagram of the system architecture of an in-vehicle application system adaptation structure, as illustrated in an exemplary embodiment of the present invention. In some embodiments, the in-vehicle application system may include a base layer 210, a vehicle model business layer 220, a common business layer 230, a user interface adaptation layer 240, and an application configuration management layer 250. The base layer 210 is used to establish corresponding basic components based on different business functions. The vehicle model business layer 220 is used to determine the vehicle model and create vehicle model components corresponding to the vehicle model business. The common business layer 230 is used to extract the common business logic of the vehicle model business layer and create common business components corresponding to the common business logic. Both the base layer 210 and the common business layer 230 are managed using a remote dependency method. This involves encapsulating each component in the base layer and each component in the common business layer into a binary archive file (Android Archive, AAR), and then uploading the AAR file to the in-vehicle server 120. This provides dependencies for the application configuration management layer to call lower-level components and separates different vehicle model businesses. The AAR file is the product of each component being packaged separately. Although it cannot run like an in-vehicle application, the AAR file can provide program packages to external systems. The User Interface (UI) adaptation layer 240 can be used to establish adaptation components corresponding to vehicle model components. The application configuration management layer 250 can be used to build applications based on the corresponding basic components, common business components, vehicle model components, and adaptation components, thus completing the construction of the in-vehicle application system. Specifically, when building the in-vehicle application system, the basic layer 210 is built first, followed by the construction of the vehicle model business layer 220 on the architecture of the basic layer 210, then the common business layer 230, and finally the UI adaptation layer 240 and the application configuration management layer 250. However, when adapting in-vehicle application components, it is necessary to first call the common business components of the common business layer 230, then call the common components of the basic layer 210, then call the vehicle model components in the vehicle model business layer 220, and send the vehicle model components to the application configuration management layer 250 to build the vehicle model application configuration. Then, the adaptation components of the UI adaptation layer 240 are called, and the adaptation components are sent to the application configuration management layer 250 to build the UI application configuration. Finally, within the application configuration management layer 250, the in-vehicle application is built based on the common dependency configuration, basic dependency configuration, vehicle application configuration, and UI application configuration. Both the adaptation components of the user interface adaptation layer 240 and the application configuration management layer 250 employ the software architecture design pattern (Model-View-ViewModel, MVVM) to decouple UI, data, and logic, avoiding inconsistencies between UI and data.

[0042] Please see Figure 2As shown, in an exemplary embodiment, the basic components may include multiple different basic business components. For example, the basic components may include a network request component, a log assist component, a file storage component, a class component, a conversion tool component, a lifecycle management component, and multiple third-party components, and each component is independent of the others. However, this is not the case; the basic components may also include other components. The network request component is used to obtain input request characters and standardize them. The log assist component is used to track the program execution process and quickly locate the root cause of problems. The file storage component may include a distributed storage component (Hadoop Distributed File System, HDFS), a shared storage component (General Parallel File System, GPFS), and a scalable storage component (Google File System, GFS) to store vehicle business file data, ensuring file persistence and data consistency between replicas. The class component is used to display the user interface. The conversion tool component is used to perform data conversion operations on input and output ports and encapsulate functions. The lifecycle management component is used to perceive the application lifecycle of the in-vehicle application system components and decouple the user interface from the components.

[0043] Please see Figure 2As shown, in an exemplary embodiment, the vehicle model component may include multiple different vehicle model business components. For example, the vehicle model component may include a software development kit (SDK) and multiple different vehicle model business components, each of which relies on the SDK for its creation. The SDK is used in the development and maintenance of the system, while the vehicle model business components are encapsulated based on the business logic adapted to the vehicle model. Common business components may include multiple different common business components. For example, common business components may include download business components, network request encapsulation components, storage components, user interface components, callback processing components, entity state processing components, data management components, and data processing components. The download business component provides download functionality for the application, the network request encapsulation component simply encapsulates network data and methods and makes requests, the storage component records data in the vehicle application browser and stores files, ensuring file persistence and data consistency between copies, the user interface component provides user interface display and interaction functions, and the callback processing component performs unified processing of the results returned by the network request. The entity state handling component is a component that uniformly processes the state of the core entity class returned by network requests. The data management component is a component that classifies and independently manages all cached data in the application. The data processing component is a component that processes all cached data in the application.

[0044] Please see Figure 2 As shown, in an exemplary embodiment, the adaptation component may include multiple different components corresponding to the vehicle model component to match different vehicle model services. For example, vehicle model adaptation 1 in the adaptation component corresponds to vehicle model service 1 in the vehicle model component. However, this is not the only possibility; vehicle model adaptation 2 in the adaptation component also corresponds to vehicle model service 2 in the vehicle model component, and so on. Each vehicle model adaptation component in the adaptation component corresponds to a vehicle model service component.

[0045] Please see Figure 3 As shown, Figure 3 This is a schematic flowchart illustrating a component-based processing method for in-vehicle applications, as shown in an exemplary embodiment of the present invention. This method can be applied to… Figure 1 The implementation environment shown is specifically executed by the smart terminal 110 within that implementation environment. It should be understood that this method can also be applied to other exemplary implementation environments and executed by devices in other implementation environments; this embodiment does not limit the implementation environment to which the method is applicable.

[0046] like Figure 3In one exemplary embodiment, the componentization processing method for in-vehicle applications includes at least steps S310 to S350, which are detailed below:

[0047] Step S310: Divide the business functions of different vehicle models within the basic layer and generate corresponding basic components;

[0048] Step S320: Extract the common business logic of the common business layer for different vehicle models, and divide the common business logic based on the basic components to generate common business components;

[0049] Step S330: Package the basic components and common business components, and upload the packaged files to the remote server;

[0050] Step S340: Input different vehicle model services into the vehicle model service layer, and make dependencies on the basic components and common business components of the remote server to generate vehicle model components corresponding to the vehicle model services;

[0051] Step S350: The basic components, common business components, and vehicle model components that depend on the remote server are divided into vehicle model business in the user interface adaptation layer to generate adaptation components;

[0052] Step S360: Within the application configuration management layer, build the application based on the basic components, common business components, vehicle components, and adaptation components corresponding to the vehicle model business, and generate the vehicle model application.

[0053] like Figure 3 In an exemplary embodiment, when step S310 is executed, the business functions of different vehicle models are divided within the base layer, generating corresponding base components. It should be noted that the base layer 210 is built within the smart terminal 110, and the base components can include various different components. For example, base components can include network request components, log assistance components, file storage components, class components, conversion tool components, lifecycle management components, and multiple third-party components, and each component is independent of the others. However, this is not the only possibility; the base components can also include other components.

[0054] like Figure 3In an exemplary embodiment, when step S320 is executed, the common business logic of the common business layer for different vehicle models is extracted, and the common business logic is divided based on the basic components to generate common business components. The common business layer 230 is constructed based on the vehicle model business layer 220, and the common business components are generated within the common business layer 230. Common business components may include multiple different common business components. For example, common business components may include different components such as download business components, network request encapsulation components, storage components, user interface components, callback processing components, entity state processing components, data management components, and data processing components.

[0055] like Figure 3 In one exemplary embodiment, when step S330 is executed, the basic components and common business components are packaged, and the packaged files are uploaded to a remote server.

[0056] like Figure 3 In an exemplary embodiment, when step S340 is executed, different vehicle model services are input into the vehicle model service layer, and dependencies are made on the basic components and common business components of the remote server to generate vehicle model components corresponding to the vehicle model services. The vehicle model service layer 220 is built upon the basic layer 210. A vehicle model component may include multiple different vehicle model service components. For example, a vehicle model component may include a software development kit (SDK) and multiple different vehicle model service components, each of which depends on the software development kit (SDK) for its creation. The software development kit (SDK) is a component used in the development and maintenance of the system, and the vehicle model service component is a component encapsulated according to the business logic adapted to the vehicle model.

[0057] like Figure 3 In one exemplary embodiment, when step S350 is executed, the vehicle model business is divided in the user interface adaptation layer based on the basic components, common business components, and vehicle model components of the remote server, and adaptation components are generated. The user interface adaptation layer 240 is constructed based on the vehicle model business layer 220, and the adaptation components are generated within the user interface adaptation layer 240.

[0058] like Figure 3 In an exemplary embodiment, when step S360 is executed, the application is constructed within the application configuration management layer based on the basic components, common business components, vehicle components, and adaptation components corresponding to the vehicle model business, thereby generating a vehicle model application.

[0059] Please see Figure 4 As shown, Figure 4This is a sequence diagram illustrating the component-based adaptation of an in-vehicle application in an exemplary embodiment of the present invention. First, based on the vehicle model business requirements, the necessary common business components are determined. These common business components are then located within the common business layer 230, and common dependency configurations related to these common business components are generated using the application configuration management layer 250. Next, based on the common business requirements, the necessary basic components are determined. These basic components are then located within the basic layer 210, and basic dependency configurations related to these basic components are generated using the application configuration management layer 250. Then, the vehicle model components in the vehicle model business layer 220 are invoked and sent to the application configuration management layer 250 to construct the vehicle model application configuration. The adaptation components in the UI adaptation layer 240 are then invoked and sent to the application configuration management layer 250 to construct the UI application configuration. Finally, within the application configuration management layer 250, the in-vehicle application is constructed based on the common dependency configurations, basic dependency configurations, vehicle model application configurations, and UI application configurations.

[0060] It should be noted that the in-vehicle application system provided in the above embodiments and the component-based processing method for in-vehicle applications provided in the above embodiments belong to the same concept. The specific ways in which each module and unit performs operations have been described in detail in the method embodiments, and will not be repeated here. In practical applications, the in-vehicle application system provided in the above embodiments can allocate the above functions to different functional modules as needed, that is, divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not a limitation.

[0061] Embodiments of this application also provide an electronic device, including: one or more processors, and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the electronic device to run the in-vehicle application system provided in the above embodiments.

[0062] Figure 5 A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 5 The computer system 700 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0063] like Figure 5As shown, the computer system 700 includes a Central Processing Unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 702 or programs loaded from storage portion 708 into Random Access Memory (RAM) 703, such as performing the methods described in the above embodiments. The RAM 703 also stores various programs and data required for system operation. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An Input / Output (I / O) interface 705 is also connected to the bus 704.

[0064] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN (Local Area Network) card and a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0065] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs various functions defined in the system of this application.

[0066] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in connection with an instruction execution system, apparatus, or device. Computer programs contained on a computer-readable medium can be transmitted using any suitable medium, including but not limited to:

[0067] Wireless, wired, etc., or any suitable combination of the above.

[0068] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, or they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0069] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0070] Another aspect of this application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer's processor, causes the computer to perform the component-based processing method for the aforementioned in-vehicle application. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not incorporated into the electronic device.

[0071] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to run the in-vehicle application system provided in the various embodiments described above.

[0072] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in the present invention should still be covered by the claims of the present invention.

Claims

1. A vehicle-mounted application system, characterized in that, The system includes: The base layer is used to establish corresponding basic components based on the business functions of different vehicle models; The vehicle model business layer is used to determine the vehicle model and create vehicle model components corresponding to the vehicle model business. The vehicle model components include software development components and multiple different vehicle model business components. The vehicle model business components are established through the software development components. The common business layer is used to extract the common business logic of the vehicle model business layer and create common business components corresponding to the common business logic based on the basic components and the vehicle model components. A user interface adaptation layer is used to establish adaptation components corresponding to the vehicle model components. This user interface adaptation layer is established based on the vehicle model business layer. The adaptation components correspond to the vehicle model business components, and multiple adaptation components are independent of each other. The application configuration management layer is used to build applications based on the corresponding basic components, common business components, vehicle model components and adaptation components, thereby completing the construction of the in-vehicle application system. Each component in the basic components and the common business components is encapsulated and packaged into an independent binary archive file, and the binary archive file is uploaded to a remote server so that the basic layer and the common business layer are managed through remote dependency. The adaptation components of the user interface adaptation layer and the application configuration management layer all adopt software architecture design patterns to decouple UI, data and logic.

2. The vehicle-mounted application system according to claim 1, characterized in that, The basic components include network request components, log assistance components, file storage components, class components, transformation tool components, lifecycle management components, and multiple third-party components.

3. The vehicle-mounted application system according to claim 2, characterized in that, The network request component, the log assist component, the file storage component, the class component, the conversion tool component, the lifecycle management component, and the multiple third-party components are independent of each other.

4. The vehicle-mounted application system according to claim 1, characterized in that, The common business components include a download business component, a network request encapsulation component, a storage component, a user interface component, a callback processing component, an entity state processing component, a data management component, and a data processing component.

5. The vehicle-mounted application system according to claim 4, characterized in that, The download service component, the network request encapsulation component, the storage component, the user interface component, the callback processing component, the entity state processing component, the data management component, and the data processing component are independent of each other.

6. A component-based processing method for in-vehicle applications, characterized in that, include: Within the base layer, different vehicle model business functions are divided, and corresponding basic components are generated; The common business logic of the common business layer of different vehicle models is extracted, and the common business logic is divided according to the basic components to generate common business components; The basic components and the common business components are packaged, and the packaged files are uploaded to a remote server. Different vehicle model services are input into the vehicle model service layer, and the basic components and common service components of the remote server are depended on to generate vehicle model components corresponding to the vehicle model services. The vehicle model components include software development components and multiple different vehicle model service components, and the vehicle model service components are established through the software development components. The user interface adaptation layer divides the vehicle business based on the basic components, common business components, and vehicle model components of the remote server, and generates adaptation components. The user interface adaptation layer is established based on the vehicle business layer, and the adaptation components correspond to the vehicle business components. Moreover, multiple adaptation components are independent of each other. Within the application configuration management layer, the application is constructed based on the basic components, common business components, vehicle components, and adaptation components corresponding to the vehicle model business, thereby generating a vehicle model application. Each component in the basic components and the common business components is encapsulated and packaged into an independent binary archive file, and the binary archive file is uploaded to a remote server so that the basic layer and the common business layer are managed through remote dependency. The adaptation components of the user interface adaptation layer and the application configuration management layer all adopt software architecture design patterns to decouple UI, data and logic.

7. An electronic device, characterized in that, The electronic device includes: One or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, cause the electronic device to operate the vehicle application system as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by the computer's processor, causes the computer to run the vehicle application system as described in any one of claims 1 to 5.

Images