Automove vehicle control interface simplified calling implementation method and system and vehicle

Abstract

The invention discloses an Automove vehicle control interface simplified calling implementation method and system and a vehicle, and the method comprises the steps: removing each sub-manager between a vehicle-mounted application and a vehicle service in the system, and only reserving a vehicle attribute manager to read, write and register related signals; wherein a list combination batch registration interface is added to the car attribute manager (CarProperty Manager). According to the method provided by the invention, the execution step of calling the Car API by the Car APP is simplified, so that the APP code for calling the CarService interface is simple, the workload of the vehicle control middleware is reduced, the coding efficiency is improved, and the development efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle testing technology, and in particular to an Automotive vehicle control interface simplified calling implementation method, system and vehicle. Background Art

[0002] In the process of vehicle control CAN communication docking, the application layer calls Automotive Carservice (car service in Android Automotive system) through each subclass API (Application ProgrammingInterface, application programming interface), such as CarCabinManager.java, CarVendorExtensionManager.java, CarSensorManager.java, CarHvacManager.java and other sub-managers to realize the interaction with APP. When there are few project function requirements, these native API managers of Android can probably cover the project requirements; but when it comes to high-configuration and complex product requirements, new applications will be added continuously, which increases the workload of maintaining CarAPI a lot. For example, more function managers need to be developed, such as: CarBodyControlManager.java, CarInfoManager.java, CarDrivingSystemManager.java, CarBrandAudioManager.java, etc., and may also involve some vague and inconvenient signal function definitions. With the iteration of the project, in order to make the code more organized, many managers will be added to match the functions, which greatly increases the workload of development and maintenance, and is not conducive to the handover and maintenance of different software developers. Summary of the invention

[0003] The technical problem to be solved by the present invention is to provide an Automotive vehicle control interface simplified calling implementation method, system and vehicle in view of the deficiencies in the prior art. The method simplifies the execution steps of Car APP calling Car API, makes the APP code that calls the CarService interface concise, reduces the workload of the vehicle control middleware, improves coding efficiency, and thus improves development efficiency.

[0004] To achieve the above object, according to one aspect of the present invention, a method for implementing simplified calling of an Automotive vehicle control interface is provided, comprising:

[0005] Remove the various sub-managers between the in-vehicle applications and the car services in the system, and only keep the car attribute manager to read, write and register related signals.

[0006] In the above solution, the sub-managers between the in-vehicle application Car APP and the car service CarService in the system are removed. Based on the principle of universal adaptation, the workload of upstream and downstream maintenance is reduced, and only the car property manager CarPropertyManager is considered to read, write and register related signals;

[0007] The car property manager CarPropertyManager adds a list combination batch registration interface, so that the in-vehicle application APP involving many vehicle control functions does not need to repeat the registration form of a single signal PropertyID over and over again. It only needs to call the registration interface once to complete the registration of all signals, simplifying the amount of application code.

[0008] In the above solution, the car property manager CarPropertyManager retains the separate registration form of each interface, which is convenient for personalized definition of vehicle applications and special signal scenario development.

[0009] In the above solution, after discarding each sub-manager, the propertyID of one of the original parameters of the in-vehicle application executing set, get and registerCallback needs to be redefined.

[0010] In the above solution, the vehicle-mounted application executes set, get and registerCallback, and one of the original parameters, propertyID, is passed by calling a new Java package propertyId.jar. This does not require the middleware Java developer to redefine it, and only requires the middleware C++ developer to complete the original VHAL parsing work, saving the middleware JAVA development workload.

[0011] In the above solution, the propertyId.jar is automatically generated by a ready-made jar package program static code referencing the C++ library of VHAL defining propertyID, so as to achieve the effect of automatic generation during compilation. By calling the new propertyID.jar, the propertyID.jar does not require the developer to manually add code every time an interface is added.

[0012] In the above solution, the propertyID is named according to the signal matrix to facilitate problem location.

[0013] In the above solution, the in-vehicle applications include apps developed by original equipment manufacturers OEM and third parties.

[0014] According to another aspect of the present invention, there is provided an Automotive vehicle control interface simplified calling system, comprising:

[0015] The calling unit is used to remove the various sub-managers between the vehicle application and the vehicle service in the system, and only retain the vehicle attribute manager to read, write and register related signals.

[0016] According to another aspect of the present invention, a vehicle is provided, the vehicle comprising the above-mentioned Automotive vehicle control interface simplified calling system.

[0017] In general, the above technical solutions conceived by the present invention can achieve the following beneficial effects compared with the prior art:

[0018] The present invention provides an Automotive vehicle control interface simplified calling implementation method, system and vehicle. The method removes various sub-managers between the vehicle application and the vehicle service in the system, and only retains the vehicle attribute manager to read, write and register related signals, thereby simplifying the execution steps of the Car APP calling the Car API, making the APP code that calls the CarService interface concise, reducing the workload of the vehicle control middleware, improving the coding efficiency, and thus improving the development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Also, throughout the accompanying drawings, the same reference figures are used to represent the same components. In the drawings:

[0020] Figure 1 The present invention is a flowchart of a simplified calling implementation method of an Automotive vehicle control interface in an embodiment of the present invention.

[0021] Figure 2 This is a schematic comparison diagram of the structure of the CarService interface call in an embodiment of the present invention.

[0022] Figure 3 This is a comparative schematic diagram of adding a list combination batch registration interface to CarPropertyManager in an embodiment of the present invention.

[0023] Figure 4 The figure is a flow chart of simplified calling of the vehicle-mounted application interface in an embodiment of the present invention.

[0024] Figure 5 The figure is a flow chart of calling a new Java package propertyId.jar in an embodiment of the present invention.

[0025] Figure 6 This is a schematic diagram of the process of automatically generating propertyId.jar in an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0027] It should be understood that the size of the serial numbers of the steps in the embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0028] Example

[0029] The present application provides a simplified method for implementing the Automotive vehicle control interface call. Figure 1 ,include:

[0030] S1, remove the various sub-managers between the in-vehicle applications and the car services in the system, and only keep the car attribute manager to read, write and register related signals.

[0031] Specifically, see Figure 2 , Figure 2 The upper part shows a schematic diagram of the CarService interface call structure in the prior art. Figure 2 The lower part shows a schematic diagram of the interface call structure of a simplified calling implementation method of an Automotive vehicle control interface provided by the present invention. In the embodiment of the present application, the various sub-managers between the in-vehicle application Car APP and the car service CarService in the system are removed, and based on the principle of universal adaptation, the upstream and downstream maintenance workload is reduced by considering only reading and writing and registering related signals through the car property manager CarPropertyManager; wherein the car property manager CarPropertyManager adds a list combination batch registration interface. Such a design makes it unnecessary for in-vehicle application APPs involving many vehicle control functions to repeat the registration form of a single signal PropertyID over and over again, and only needs to call the registration interface once to complete the registration of all signals, thereby simplifying the amount of application code. At the same time, in the embodiment of the present application, the car property manager CarPropertyManager retains the separate registration form of each interface, which is convenient for the personalized definition of in-vehicle applications. Please refer to Figure 3 and Figure 4 ,in Figure 3 is a comparative schematic diagram of CarPropertyManager adding a list combination batch registration interface in an embodiment of the present application, Figure 4 It is a flowchart of simplified calling of the vehicle application interface.

[0032] It is understandable that in the embodiment of the present application, after each sub-manager manager is abandoned, the propertyID of one of the original parameters of the vehicle-mounted application executing set, get and registerCallback needs to be redefined. Figure 5 In this embodiment, the vehicle application executes set, get and registerCallback, and one of the original parameters is propertyID by calling a new Java package propertyId.jar. For details, please refer to Figure 6 In the embodiment of the present application, propertyId.jar is automatically generated by a static code of a ready-made jar package program referencing a C++ library that defines propertyID in VHAL, thereby achieving the effect of automatic generation upon compilation.

[0033] In the embodiment of the present application, the propertyID is named according to the signal matrix to facilitate problem location.

[0034] In an embodiment of the present application, the in-vehicle applications include apps developed by original equipment manufacturers and third parties. Specifically, the in-vehicle applications include but are not limited to navigation-related apps, music-related apps, entertainment-related apps, education-related apps, smart assistant-related apps, and social and communication-related apps.

[0035] Another aspect of the present application provides an Automotive vehicle control interface simplified calling system, including:

[0036] The calling unit is used to remove the various sub-managers between the vehicle application and the vehicle service in the system, and only retain the vehicle attribute manager to read, write and register related signals.

[0037] Another aspect of an embodiment of the present application provides a vehicle, which includes the above-mentioned Automotive vehicle control interface simplified calling system.

[0038] The present invention provides an Automotive vehicle control interface simplified calling implementation method, system and vehicle. The method removes various sub-managers between vehicle-mounted applications and vehicle services in the system, and only retains a vehicle attribute manager to read, write and register related signals, thereby simplifying the execution steps of Car APP calling Car API, making the APP code that calls the CarService interface concise, reducing the workload of vehicle control middleware, improving coding efficiency, and thus improving development efficiency.

[0039] It should be pointed out that, according to the needs of implementation, the various steps described in this application can be divided into more steps, or two or more steps or partial operations of the steps can be combined into a new step to achieve the purpose of the present invention.

[0040] It will be easily understood by those skilled in the art that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A simplified calling implementation method for an Automotive vehicle control interface, characterized in that: include: Remove the various sub-managers between the in-vehicle applications and the car services in the system, and only keep the car attribute manager to read, write and register related signals.

2. The method for implementing simplified calling of an Automotive vehicle control interface according to claim 1, characterized in that: Remove the sub-managers between the in-vehicle application Car APP and the car service CarService in the system. Based on the principle of universal adaptation, reduce the workload of upstream and downstream maintenance and consider only reading, writing and registering related signals through the car property manager CarPropertyManager; The car property manager CarPropertyManager adds a list combination batch registration interface.

3. The method for implementing simplified calling of an Automotive vehicle control interface according to claim 2, characterized in that: The car property manager CarPropertyManager retains the separate registration form of each interface to facilitate the personalized definition of vehicle-mounted applications.

4. The method for implementing simplified calling of an Automotive vehicle control interface according to claim 2, characterized in that: After discarding each sub-manager, the propertyID of one of the original parameters of the in-vehicle application executing set, get and registerCallback needs to be redefined.

5. The method for implementing simplified calling of an Automotive vehicle control interface according to claim 4, characterized in that: The vehicle-mounted application executes set, get and registerCallback of one of the original parameters, propertyID, by calling a new Java package propertyId.jar.

6. The method for implementing simplified calling of an Automotive vehicle control interface according to claim 5, characterized in that: The propertyId.jar is automatically generated in the form of a C++ library that defines propertyID in VHAL by using a ready-made jar package program static code, so that the effect of automatic generation is achieved by compiling.

7. The method for implementing simplified calling of an Automotive vehicle control interface according to claim 4, characterized in that: The propertyID is named according to the signal matrix to facilitate problem location.

8. The method for implementing simplified calling of an Automotive vehicle control interface according to claim 2, characterized in that: The in-vehicle applications include apps developed by original equipment manufacturers and third parties.

9. An Automotive vehicle control interface simplified calling system, characterized in that: include: The calling unit is used to remove the various sub-managers between the vehicle application and the vehicle service in the system, and only retain the vehicle attribute manager to read, write and register related signals.

10. A vehicle, characterized in that: The vehicle includes an Automotive vehicle control interface simplified calling system as described in claim 9.

Images