Android-based vehicle end application software architecture system and device, vehicle development method and medium

Abstract

The invention discloses an Android-based vehicle end application software architecture system and device, a vehicle development method and a medium, and belongs to the technical field of vehicle-mounted system development, the Android-based vehicle end application software architecture system comprises a UI module, a controller module, a service layer module and a middleware module; wherein the business layer module comprises a USB module, a video module and a picture module; the middleware module comprises a system service module, a media service module and a database module; the UI module is used for realizing page rendering; the controller module is used for receiving an instruction of the UI module, sending the instruction to the service layer module and returning a processing result to the UI module; the business layer module is used for receiving instructions of the controller module and calling corresponding playing interfaces of the middleware module according to different instructions; and the middleware module is used for converting the differentiated interface of the automobile media processing equipment into a standardized unified interface, providing the standardized unified interface to the business layer module and controlling the corresponding automobile media processing equipment to work. According to the system, through a modularized and reusable software architecture, repeated adaptation and redesign development work of each project to a specific interface can be reduced.

Description

Technical Field

[0001] The present invention belongs to the technical field of vehicle-mounted system development, and specifically relates to an Android-based vehicle-side application software architecture system, equipment, vehicle development method and medium. Background Art

[0002] The software in the automotive industry has certain particularities. The design of the vehicle IVI domain generally adopts the method of separating software from hardware and cooperating across departments or even companies. Therefore, the hardware platform and system version change frequently. Based on this, a series of problems will arise in the software platform. Specifically, there are the following problems:

[0003] ① High development cost: Each project application software needs to be re-adapted to the interface, re-designed and re-developed, with a long development cycle and high cost.

[0004] ② Poor compatibility: Different models are equipped with different system versions and hardware configurations. Application software needs to be customized for each platform, which increases the complexity of development and maintenance.

[0005] ③ Difficulty in maintenance: Direct dependency between application software and between software and system will lead to high coupling. When the hardware platform or software module changes, a large number of application software often need to be updated, resulting in high maintenance costs. Summary of the invention

[0006] In view of the above-mentioned problems existing in the prior art, the present invention provides an Android-based vehicle-side application software architecture system, equipment, vehicle development method and medium; through a modular and reusable software architecture, the repeated adaptation and redesign and development work of specific interfaces for each project can be reduced; the middleware module is used to achieve the decoupling of the business layer module from the underlying hardware and system layer, thereby shortening the development cycle and reducing the overall development cost.

[0007] The present invention is achieved through the following technical solutions:

[0008] In a first aspect, the present invention provides an Android-based vehicle-side application software architecture system, including a UI module, a controller module, a business layer module, and a middleware module;

[0009] The business layer module includes a USB module, a video module and a picture module; the middleware module includes a system service module, a media service module and a database module;

[0010] UI module, used to implement page rendering;

[0011] The controller module is used to receive instructions from the UI module, send them to the business layer module, and return the processing results to the UI module;

[0012] The business layer module is used to receive instructions from the controller module and call the corresponding playback interface of the middleware module according to different instructions;

[0013] The middleware module is used to convert the differentiated interfaces of the automotive media processing equipment into a standardized unified interface, provide it to the business layer module, and control the operation of the corresponding automotive media processing equipment.

[0014] Furthermore, each module interacts and communicates with each other through interfaces, wherein one end of the middleware module is connected to the business layer module to provide an interface for it, and the other end is connected to the system's vehicle, media, vehicle control processor and the native interface of the Android system.

[0015] Furthermore, the automobile media processing device includes a vehicle server, a media player and a media decoder.

[0016] Furthermore, the system service module is connected to the USB module of the business layer module to convert the differentiated interface of the vehicle server into a standardized unified interface and provide it to the USB module;

[0017] The media service module is connected to the video module and the picture module respectively, and is used to convert the differentiated interfaces of the media player into a standardized unified interface, and provide it to the video module and the picture module respectively;

[0018] The database module is used to store data information required by the business layer module, such as media information, video progress, breakpoint resume information, etc.

[0019] Furthermore, the USB module is used for information scanning, classification and sorting of the USB flash drive;

[0020] The video module is used to control video playback;

[0021] The picture module is used to control picture operations.

[0022] In a second aspect, the present invention provides a vehicle function development device, including an Android-based vehicle-side application software architecture system as described in the first aspect.

[0023] In a third aspect, the present invention provides a vehicle function development method based on an Android vehicle-side application software architecture system, which specifically includes the following steps:

[0024] Obtain system data, media, vehicle control information and standardized interfaces;

[0025] Identify the output interface configuration requirements for the system data, media, and vehicle control information;

[0026] An input interface and an output interface are generated according to the output interface configuration requirement, and the input interface and the output interface are respectively mapped to interfaces of an external automobile media processing device.

[0027] In a fourth aspect, the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a vehicle function development method as described in any one of the present inventions.

[0028] Compared with the prior art, the advantages of the present invention are as follows:

[0029] 1. The Android-based vehicle-side application software architecture system, device, vehicle development method and medium of the present invention can significantly reduce the R&D cost of automobile IVI system software and improve the economic benefits of the project by reducing repeated development and customization work;

[0030] 2. Faster adaptation to different models and configurations, users can enjoy a more consistent, smooth and feature-rich in-vehicle infotainment experience. At the same time, the man-hours saved can be used to adapt and optimize more functions, thereby improving brand satisfaction and loyalty;

[0031] 3. Through modularization, service-oriented design and automated testing process, it can effectively reduce software defects, improve software quality and stability, reduce failure rate and ensure driving safety;

[0032] 4. Flexible architecture design and efficient development tool chain provide a good environment for technological innovation, enabling automakers to respond to market changes more quickly, launch new features and optimize upgrades, and maintain competitiveness;

[0033] 5. The separation of software and hardware and modular design ideas will help achieve resource sharing and complementary advantages among different departments and companies, and promote efficient collaboration among various controllers of the entire vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following is a brief introduction to the drawings required for the specific embodiments or the description of the prior art. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, the elements or parts are not necessarily drawn according to the actual scale.

[0035] Figure 1 This is a structural diagram of an Android-based vehicle-side application software architecture system;

[0036] Figure 2 A flowchart of a vehicle function development method for a vehicle-side application software architecture system based on Android;

[0037] Figure 3 This is a simplified timing diagram. DETAILED DESCRIPTION

[0038] In order to clearly and completely describe the technical solution and its specific working process of the present invention, the specific implementation methods of the present invention are as follows in conjunction with the accompanying drawings of the specification:

[0039] In the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements, unless otherwise clearly defined. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0040] In the present invention, unless otherwise clearly specified and limited, a first feature being "above" or "below" a second feature may mean that the first and second features are in direct contact, or the first and second features are in indirect contact through an intermediate medium. Moreover, a first feature being "above", "above" or "above" a second feature may mean that the first feature is directly above or obliquely above the second feature, or simply means that the first feature is higher in level than the second feature. A first feature being "below", "below" or "below" a second feature may mean that the first feature is directly below or obliquely below the second feature, or simply means that the first feature is lower in level than the second feature.

[0041] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0042] Example 1

[0043] like Figure 1 As shown, this embodiment provides an Android-based vehicle-side application software architecture system, including a UI module, a controller module, a business layer module and a middleware module;

[0044] The business layer module includes a USB module, a video module and a picture module; the middleware module includes a system service module, a media service module and a database module;

[0045] The UI module is used to implement page rendering, covering the implementation of HMI design such as user interaction, screen drawing, and animation.

[0046] The controller module is used to receive instructions from the UI module, send them to the business layer module, and return the processing results to the UI module;

[0047] The business layer module is used to receive instructions from the controller module and call the corresponding playback interface of the middleware module according to different instructions;

[0048] The middleware module is used to convert the differentiated interfaces of the automotive media processing equipment into a standardized unified interface, provide it to the business layer module, and control the operation of the corresponding automotive media processing equipment.

[0049] In this embodiment, each module interacts and communicates with each other through an interface, wherein one end of the middleware module is connected to the business layer module to provide an interface for it, and the other end is connected to the system's vehicle, media, vehicle control processor and the native interface of the Android system.

[0050] The automobile media processing device includes a vehicle server, a media player and a media decoder.

[0051] The system service module is connected to the USB module of the business layer module to convert the differentiated interface of the vehicle server into a standardized unified interface and provide it to the USB module;

[0052] The media service module is connected to the video module and the picture module respectively, and is used to convert the differentiated interfaces of the media player into a standardized unified interface, and provide it to the video module and the picture module respectively;

[0053] The database module is used to store data information required by the business layer module, such as media information, video progress, breakpoint resume information, etc.

[0054] The USB module is used for information scanning, classification and sorting of the USB flash drive;

[0055] The video module is used for controlling video playback; it connects to the media control layer interface downward and provides unified calls for the controller module upward.

[0056] The picture module is used to control picture operations.

[0057] An Android-based vehicle-side application software architecture system in this embodiment, through a middleware module, remains unchanged at the top and adapts to the bottom; a unified underlying docking protocol is encapsulated, and no matter the vehicle model, system, or Android version is different, the bottom layer can be required to adapt according to the unified protocol. If resistance is encountered and adaptation is impossible, a set of protocols can also be encapsulated separately at the interface layer. There is no need to change the code at the business layer, thus realizing interface platformization.

[0058] The vehicle-side application software architecture system described in this embodiment is used in the FAW Bestune E311 project, and the application layer software USB file adopts this structure to achieve platform design.

[0059] Specifically, take the video playback function as an example, Figure 3 The timing diagram shown is described in detail;

[0060] The various functions of the application layer software are encapsulated between the UI commands triggered by the user and the underlying Android player.

[0061] The media service module of the interface layer provides the start() interface of the media player of the docking system and provides the play() interface for the upper layer. The video module of the business layer provides the play() interface for the UI layer and the play() interface of the docking interface adaptation layer. Figure 3 As shown in the figure, the play() interface and the start() interface are platform interfaces. No matter how the vehicle model, system, etc. change, the platform interface and modular business remain unchanged.

[0062] Example 2

[0063] This embodiment provides a vehicle function development device, including an Android-based vehicle-side application software architecture system described in Example 1.

[0064] Example 3

[0065] like Figure 2 As shown, this embodiment provides a vehicle function development method based on an Android vehicle-side application software architecture system, which specifically includes the following steps:

[0066] Obtain system data, media, vehicle control information and standardized interfaces;

[0067] Identify the output interface configuration requirements for the system data, media, and vehicle control information;

[0068] An input interface and an output interface are generated according to the output interface configuration requirement, and the input interface and the output interface are respectively mapped to interfaces of an external automobile media processing device.

[0069] Example 4

[0070] Embodiment 4 of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle function development method provided in all the embodiments of the present application.

[0071] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device, or device.

[0072] Computer-readable signal media may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0073] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0074] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0075] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. An Android-based vehicle-side application software architecture system, characterized in that: Including UI module, controller module, business layer module and middleware module; The business layer module includes a USB module, a video module and a picture module; the middleware module includes a system service module, a media service module and a database module; UI module, used to implement page rendering; The controller module is used to receive instructions from the UI module, send them to the business layer module, and return the processing results to the UI module; The business layer module is used to receive instructions from the controller module and call the corresponding playback interface of the middleware module according to different instructions; The middleware module is used to convert the differentiated interfaces of the automotive media processing equipment into a standardized unified interface, provide it to the business layer module, and control the operation of the corresponding automotive media processing equipment.

2. The vehicle-side application software architecture system based on Android as claimed in claim 1, characterized in that: The modules interact and communicate with each other through interfaces. One end of the middleware module is connected to the business layer module to provide an interface for it, and the other end is connected to the system's vehicle, media, vehicle control processor and the native interface of the Android system.

3. The vehicle-side application software architecture system based on Android as claimed in claim 1, characterized in that: The automobile media processing device includes a vehicle server, a media player and a media decoder.

4. The vehicle-side application software architecture system based on Android as claimed in claim 1, characterized in that: The system service module is connected to the USB module of the business layer module to convert the differentiated interface of the vehicle server into a standardized unified interface and provide it to the USB module; The media service module is connected to the video module and the picture module respectively, and is used to convert the differentiated interfaces of the media player into a standardized unified interface, and provide it to the video module and the picture module respectively; The database module is used to store data information required by the business layer module.

5. The vehicle-side application software architecture system based on Android as claimed in claim 1, characterized in that: The USB module is used for information scanning, classification and sorting of the USB flash drive; The video module is used to control video playback; The picture module is used to control picture operations.

6. A vehicle function development device, characterized in that: It includes an Android-based vehicle-side application software architecture system as described in any one of claims 1-5.

7. The vehicle function development method of the vehicle-side application software architecture system based on Android as claimed in claim 1, characterized in that: The specific steps include: Obtain system data, media, vehicle control information and standardized interfaces; Identify the output interface configuration requirements for the system data, media, and vehicle control information; An input interface and an output interface are generated according to the output interface configuration requirement, and the input interface and the output interface are respectively mapped to interfaces of an external automobile media processing device.

8. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the program is executed by a processor, the vehicle function development method as claimed in claim 7 is implemented.

Images