CN108667869B - Vehicle information interaction system - Google Patents
Vehicle information interaction system Download PDFInfo
- Publication number
- CN108667869B CN108667869B CN201710204258.7A CN201710204258A CN108667869B CN 108667869 B CN108667869 B CN 108667869B CN 201710204258 A CN201710204258 A CN 201710204258A CN 108667869 B CN108667869 B CN 108667869B
- Authority
- CN
- China
- Prior art keywords
- vehicle
- control
- mcu
- vehicle control
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000003993 interaction Effects 0.000 title claims abstract description 41
- 238000004891 communication Methods 0.000 claims abstract description 41
- 238000000034 method Methods 0.000 claims abstract description 23
- 230000008569 process Effects 0.000 claims abstract description 14
- 238000011161 development Methods 0.000 claims abstract description 6
- 230000006870 function Effects 0.000 claims description 22
- 230000005540 biological transmission Effects 0.000 claims description 2
- 238000001514 detection method Methods 0.000 claims description 2
- 230000001360 synchronised effect Effects 0.000 claims 1
- 238000012544 monitoring process Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 239000011230 binding agent Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000001133 acceleration Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 239000007943 implant Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000035515 penetration Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a vehicle information interaction system, which is configured in an Android operating system, wherein a cloud server provides instance interfaces corresponding to each vehicle control class to a plurality of vehicle control application clients through a network communication module; each vehicle control application client displays the vehicle state in the vehicle running process in real time, receives a control instruction input by a vehicle driving user, and calls an instance interface corresponding to the vehicle control class corresponding to the control instruction, so that the cloud server and the plurality of vehicle control application clients perform information interaction based on an Android operating system arranged on the vehicle. According to the vehicle state monitoring and control method, the vehicle state monitoring and control related instance interface can be conveniently and safely provided for development and use of a platform and a third party, the safety, compatibility and transportability of the interface are guaranteed, the whole vehicle can be integrated from the system bottom layer, data cloud interaction is carried out, and real-time driving of the vehicle can be effectively guaranteed.
Description
Technical Field
The invention relates to the technical field of software engineering, in particular to a vehicle information interaction system.
Background
With the penetration of the idea of "internet +", the combination of smart operating systems with traditional automotive systems yields a new definition of an automobile: the internet becomes infrastructure, the intelligent operating system is integrated into the whole vehicle from the bottom layer, data can be subjected to cloud interaction, the data can become important driving force of the vehicle, the intelligent operating system provides a second engine for the vehicle, and the vehicle can run on a road and the internet at the same time.
Disclosure of Invention
The present invention is directed to solving, at least to some extent, one of the technical problems in the related art.
Therefore, the invention aims to provide a vehicle information interaction system, which follows the framework of an Android operating system, can conveniently and safely provide a vehicle state monitoring and control related instance interface for development and use of a platform and a third party application, ensures the safety, compatibility and transportability of the interface, can realize integration of the whole vehicle from the system bottom layer, performs data cloud interaction, and can effectively ensure real-time driving of the vehicle.
In order to achieve the above object, the vehicle information interaction system provided in the embodiment of the present invention is configured in an Android operating system, and includes: the system comprises a driving module, a hardware interface providing module, a database interface providing module and a network communication module, wherein the driving module is used for driving the hardware interface providing module to provide an API (application programming interface) interface for upper-layer services and functions through a built-in MCU (micro control unit) serial port circuit; the database interface providing module is used for calling various cpp files in a cpp file library and providing a JNI (just-in-package) interface for the network communication module, wherein the cpp file library is a local C/C + + program language file library of the Android operating system; the cloud server and the vehicle control application clients respectively establish communication links with the network communication module, and each vehicle control application client respectively controls different devices in the vehicle through the network communication module; the cloud server is provided with a plurality of vehicle control classes which are written in advance, and provides an instance interface corresponding to each vehicle control class for the plurality of vehicle control application clients through the network communication module; each vehicle control application client is used for displaying the vehicle state in the vehicle running process in real time, receiving a control instruction input by a vehicle driving user, and calling an instance interface corresponding to the vehicle control class corresponding to the control instruction, so that the cloud server and the plurality of vehicle control application clients perform information interaction based on an Android operating system arranged on the vehicle.
According to the vehicle information interaction system provided by the embodiment of the invention, each vehicle control application client controls different devices in the vehicle through the network communication module in the Android operating system on the vehicle, and the cloud server provides an example interface corresponding to each vehicle control class for the plurality of vehicle control application clients through the network communication module; each vehicle control application client is used for displaying the vehicle state in the vehicle running process in real time, receiving a control instruction input by a vehicle driving user, and calling an instance interface corresponding to the vehicle control class corresponding to the control instruction, so that the cloud server and the vehicle control application clients perform information interaction based on an Android operating system arranged on the vehicle.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
The foregoing and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a schematic structural diagram of a vehicle information interaction system according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a vehicle information interaction system according to another embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a call flow of an API interface according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a database interface providing module according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a hardware interface providing module according to an embodiment of the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar controls throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention, and are not to be construed as limiting the present invention. On the contrary, the embodiments of the invention include all changes, modifications and equivalents coming within the spirit and terms of the claims appended hereto.
Fig. 1 is a schematic structural diagram of a vehicle information interaction system according to an embodiment of the present invention.
The vehicle information interaction system is configured in the Android operating system.
Referring to fig. 1, the vehicle information interaction system 10 includes: the system comprises a driving module 101, a hardware interface providing module 102, a database interface providing module 103 and a network communication module 104, wherein the driving module 101 is used for driving the hardware interface providing module 102 to provide an API (application programming interface) for upper-layer services and functions through a built-in MCU (microprogrammed control unit) serial port circuit 1011; the database interface providing module 103 is configured to call multiple cpp files in a cpp file library 1031, and provide a JNI interface for the network communication module 104, where the cpp file library 1031 is a local C/C + + program language file library of the Android operating system;
in an embodiment of the present invention, further comprising: the network communication module 104, the cloud server 105 and the plurality of vehicle control application clients 106 respectively establish communication links with the network communication module 104, and each vehicle control application client 106 respectively controls different devices in the vehicle through the network communication module 104, wherein,
in the embodiment of the present invention, a plurality of vehicle control classes written in advance are set in the cloud server 105, and the cloud server 105 provides an instance interface corresponding to each vehicle control class, which is written in Java programming language, to the plurality of vehicle control application clients 106 through the network communication module 104.
Optionally, the plurality of vehicle control classes are at least one of the following control classes:
fault detection control, positioning control, vehicle lamp control, air conditioner control, wheel control, airbag control, transmission control, vehicle body control, and throttle control.
Optionally, the vehicle control class includes: the message type, cloud server 105 is also used to,
the message type of the device to be monitored in the vehicle is acquired through the network communication module 104, and an instance interface of the vehicle control class corresponding to the message type is called from the cpp file library 1031, so that the message of the device to be monitored is monitored in the driving process of the vehicle.
Optionally, the cloud server 105 is further configured to, when a message of the device to be monitored is monitored, distribute the message to the corresponding vehicle control application client 106 by calling the JNI interface provided by the database interface providing module 103.
Optionally, each vehicle control application client 106 calls, through the network communication module 104, an instance interface of a part of control classes in the plurality of vehicle control classes to control the devices in the vehicle, where the control classes included in the part of control classes called by each vehicle control application client 106 are different or the same.
Each vehicle control class is used for providing a corresponding instance interface for the vehicle, so that the vehicle control application client 106 calling the vehicle control class in the vehicle realizes a corresponding function of controlling the vehicle.
In an embodiment of the present invention, one or more vehicle control application clients 106 may establish communication links with different devices in the vehicle via the network communication module 104, each vehicle control application client 106 being used to control a different device in the vehicle.
For example, the corresponding vehicle control application client 106 may be a vehicle light control application client corresponding to a vehicle light in a vehicle, and in the implementation process based on the driving module 101, the vehicle light control application client may implement a corresponding function of controlling the vehicle light by calling a vehicle light control instance interface provided by the cloud server 105, where the function of controlling the vehicle light may specifically be, for example, turning on and off the vehicle light, double flashing, and the like; or, the vehicle control application client 106 corresponding to the air conditioner in the vehicle may be an air conditioner control application client, and in the implementation process based on the driving module 101, the air conditioner control application client may implement a corresponding function of controlling the air conditioner by calling an example interface of an air conditioner control class provided by the cloud server 105, where the function of controlling the air conditioner may specifically be, for example, turning on and off the air conditioner, adjusting an air conditioner parameter, and the like, and is not limited thereto.
In the embodiment of the present invention, a plurality of vehicle control classes which are written in advance are set in the cloud server 105, the cloud server 105 provides instance interfaces corresponding to each vehicle control class to a plurality of vehicle control application clients 106 through the network communication module 104, wherein each vehicle control class is written in Java programming language, when the cloud server 105 and the plurality of vehicle control application clients 106 perform data interaction based on the driving module 101 set on the vehicle, each vehicle control class can call a data interface layer to provide a JNI interface for the network communication module 104, and further, the data base interface providing module 103 is triggered to call a plurality of cpp files in the cpp file library 1031 through the JNI layer 1032 to realize a plurality of vehicle control application clients 106 of the vehicle, perform information interaction with the cloud server 105 based on an Android operating system integrated in the vehicle, because the vehicle information interaction system 10 follows the architecture of the Android operating system, the vehicle state monitoring and control related instance interface can be conveniently and safely provided for a platform and a third party to use, the safety, compatibility and transportability of the interface are guaranteed, the whole vehicle can be integrated from the system bottom layer, data cloud interaction is carried out, and real-time driving of the vehicle can be effectively guaranteed.
In the embodiment of the present invention, each vehicle control application client 106 is configured to display a vehicle state in a vehicle driving process in real time, receive a control instruction input by a vehicle driving user, and invoke an instance interface corresponding to a vehicle control class corresponding to the control instruction, so that the cloud server 105 and the plurality of vehicle control application clients 106 perform information interaction based on an Android operating system arranged on the vehicle.
It can be understood that, since the vehicle information interaction system 10 is developed and used by a platform and a third party application, a developer of the third party application can also compile a new vehicle control class based on an Android operating system on a vehicle according to a service requirement of the developer, and implant the new vehicle control class into the cloud server 105 to control a function of the new vehicle, which is not limited to this.
Optionally, each vehicle control application client 106 calls, through the network communication module 104, an instance interface of a part of the plurality of vehicle control classes to control the device in the vehicle, where the control classes included in the part of the control classes called by each vehicle control application client 106 are different or the same, or after a new vehicle control class is added to the plurality of vehicle control classes, the updated instance interfaces of the part of the plurality of vehicle control classes may also be called to control the device in the vehicle, which is not limited herein.
In an embodiment of the present invention, referring to fig. 2, fig. 2 is a schematic structural diagram of a vehicle information interaction system 10 according to another embodiment of the present invention, and a hardware interface providing module 102 includes: a plurality of MCU codecs 1021, each MCU codec 1021 is used for performing coding and decoding processing on vehicle data of different MCU types, the hardware interface providing module 102 is further used for,
the MCU type of the vehicle connected to the network communication module 104 is analyzed, and the MCU codec 1021 corresponding to the MCU type is determined.
In the embodiment of the present invention, the driving module 101 drives the MCU codec 1021 in the hardware interface providing module 102 through the MCU serial port circuit 1011 to provide an API interface for the service and function of the vehicle corresponding to the MCU codec 1021 in the upper layer.
In the embodiment of the present invention, the driver module 101 provides, through the MCU serial port circuit 1011, the driver hardware interface providing module 102 to provide an API interface for upper layer services and functions, where the upper layer services may be, for example, the vehicle control application client 106 to obtain required vehicle information, and the API interface may be, for example, an API interface for some operation classes that need to be loaded when the vehicle control application client 106 calls the vehicle control class, which is not limited thereto.
In the embodiment of the present invention, the hardware interface providing module 102 not only can provide an API interface for upper layer services and functions, but also can monitor messages of the MCU serial port circuit 1011 and maintain communication data cached in the MCU, and by configuring the hardware interface providing module 102, the influence of the driver module 101 on the upper layer services can be shielded, and since the MCU codec 1021 in the hardware interface providing module 102 provides an API interface for services and functions of a vehicle in the upper layer corresponding to the MCU codec 1021, the network communication module 104 can be allowed to access vehicles of various MCU types, thereby ensuring expandability. Further, the hardware interface providing module 102 may also perform fault tolerance processing on abnormal inputs that may occur in the upper layer service, for example, processing message loss and feedback timeout of the MCU of the vehicle.
In the implementation of the present invention, the driving module 101 included in the vehicle information interaction system 10 follows the Android API mode, and designs the API interface according to the using method and naming specification of the Android API mode, so that a developer of a third-party application can conveniently operate and develop the API. Moreover, the vehicle information interaction system 10 adopts a modular design, so that the code coupling of the design is reduced, and the repairability is improved.
In the implementation of the present invention, the hardware interface providing module 102 included in the vehicle information interaction system 10 may also buffer status information of the MCU of the vehicle, wherein the status information is, for example, status information such as a driving speed and an acceleration during driving of the vehicle, and is not limited thereto.
By caching the state information of the MCU of the vehicle, the query efficiency of the state information can be improved. Moreover, the hardware interface providing module 102 may also shield the influence of different MCU types on the vehicle information interaction system 10. In the embodiment of the present invention, the hardware interface providing module 102 may analyze the MCU type of the vehicle accessing the network communication module 104, and determine the MCU codec 1021 corresponding to the MCU type, so that the vehicle information interaction system 10 may be integrated on vehicles of different MCU types, and the hardware interface providing module 102 stores the MCU type of the vehicle accessing the network communication module 104, and feeds the stored MCU type back to each vehicle control application client 106 through the vehicle information interaction system 10, thereby enabling each vehicle control application client 106 to be self-adaptive to vehicles of different MCU types.
In the implementation of the present invention, the vehicle information interaction system 10 sets a permission type for the API interface and sets a corresponding signature level to limit the application to use the API interface, and limits the invocation of the API interface to prevent malicious applications from frequently invoking the API interface and causing congestion, along with using an Android default API permission mechanism.
In the implementation of the invention, the API interface can be synchronously called, only one command can be processed at the same time, and the others return err _ busy, and a safe coding method is used, so that code loopholes are reduced, and the difficulty of hacker attack is increased.
In the embodiment of the present invention, the API permission control system built in the driver module 101 in the related art may be used to perform permission control on the call of the API interface, for example, referring to fig. 3, fig. 3 is a schematic diagram of a call flow of the API interface in the embodiment of the present invention, where the API interface is an example of a BYD Auto API, and in the call flow, the API permission control system built in the driver module 101 in the related art performs permission control on the call of the BYD Auto API.
Further, in the embodiment of the present invention, the database interface providing module 103 provides the vehicle automatic control type service for the cloud server 105 and the plurality of vehicle control application clients 106 that establish the communication link based on the network communication module 104 by calling the API interface provided by the hardware interface providing module 102, or provides other rights management type services, which is not limited herein.
Referring to fig. 4, fig. 4 is a schematic structural diagram of the database interface providing module 103 in the embodiment of the present invention, where a BnBYDAutoServer class inherits an ibydautoarver interface and a server end of a vehicle control service. The vehicle control service adopts a binder structure, runs in an independent process, and is registered in a ServiceManager; the BpBYDAutoServer class inherits from an IBYDAutoServer interface, and a user of vehicle service uses an interface of the service provided by the database interface providing module 103 through an agent of a service manager or a server end; IBYDAutoCallback type, the vehicle control has the change of the equipment state, and the IBYDAutoCallback type is called back to the server end by registering, so that the equipment change information of the server end is received. Since the service runs in a separate process, the IBYDAutoCallback class can adopt a binder structure; the IBYDAutoCallback class may be inherited by the service consumer (i.e., each vehicle control application client 106) and registered to the server; the BYDAutoServer class interface and IBYDAutoCallback class processing logic are packaged by BYDAuutoManager. cpp, an equivalent API interface is provided for project developers, an IBYDAutoObserver interface capable of being registered is provided, and the IBYDAutoCallback information is received; the IBYDAutoobserver class is realized by project developers and is registered to an interface of a BYDAutoManager to receive equipment information; android _ hardware _ BYDAutoManager is implemented by the JNI layer 1032, connects BYDAutoManager. JAVA and BYDAutoManager. cpp, sends callback information to JAVA layers encapsulated by BYDAutoManager. JAVA, BYDAutoManager. JAVA through a reflection invocation mechanism for use by APK project developers, and invokes interfaces of BYDAutoManager through the JNI layer 1032.
Referring to fig. 5, fig. 5 is a schematic structural diagram of the hardware interface providing module 102 in the embodiment of the present invention, where the auto hal implements an open function of the hw _ module _ methods _ t for an interface class of the hardware interface providing module 102, and provides a module additional function, for example: getAutoFeatureInfo; the automatic Hardware interface is an API interface, is a main class interacting with BYDAUTOSERVICE, provides hw _ device _ t, and is a function AutoAC and an AutoAudio for realizing all interactions with BYDAUTOSERVICE, and realizes parameter initialization, query, setting and updating functions of each specific function for a specific function class; the AutoStateObserver comprises an Indicator and a response monitoring class and is responsible for monitoring and distributing commands; the auto _ interface provides functions of opening, reading and writing driving MCU equipment nodes; auto _ common _ codec provides a common command extraction function.
In the embodiment, each vehicle control application client controls different devices in the vehicle through a network communication module in an Android operating system on the vehicle, and the cloud server provides an instance interface corresponding to each vehicle control class for the plurality of vehicle control application clients through the network communication module, wherein each vehicle control class is written in a Java programming language; each vehicle control application client is used for displaying the vehicle state in the vehicle running process in real time, receiving a control instruction input by a vehicle driving user, and calling an instance interface corresponding to the vehicle control class corresponding to the control instruction, so that the cloud server and the vehicle control application clients perform information interaction based on an Android operating system arranged on the vehicle.
It should be noted that the terms "first," "second," and the like in the description of the present invention are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In addition, in the description of the present invention, "a plurality" means two or more unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing steps of a particular logical control or process, and the scope of the preferred embodiments of the present invention includes additional implementations in which controls may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the control involved, as would be understood by those reasonably skilled in the art of the embodiments of the present invention.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: discrete logic circuits with logic gates for implementing logic control on data signals, application specific integrated circuits with appropriate combinational logic gates, Programmable Gate Arrays (PGAs), Field Programmable Gate Arrays (FPGAs), etc.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, each control unit in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software control module mode. The integrated module, if implemented in the form of a software controlled module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (6)
1. The vehicle information interaction system is configured in an Android operating system and comprises the following components: a driving module, a hardware interface providing module, a database interface providing module, and a network communication module, wherein,
the driving module is used for driving the hardware interface providing module to provide an API (application program interface) for synchronous calling for development and use of a platform and a third party application for upper-layer services and functions through a built-in MCU (micro control unit) serial port circuit;
the database interface providing module is used for calling various cpp files in a cpp file library and providing JNI (just noticeable information) interfaces for platform and third-party application development and use for the network communication module, wherein the cpp file library is a local C/C + + program language file library of the Android operating system;
the cloud server and the vehicle control application clients respectively establish communication links with the network communication module, and each vehicle control application client respectively controls different devices in the vehicle through the network communication module;
the cloud server is provided with a plurality of vehicle control classes which are compiled in advance, and provides an example interface which corresponds to each vehicle control class and is used for development and development of a platform and a third party application to the plurality of vehicle control application clients through the network communication module; when the cloud server monitors the message of the device to be monitored in the vehicle, the cloud server distributes the message to the corresponding vehicle control application client by calling the JNI interface;
each vehicle control application client is used for displaying the vehicle state in the vehicle running process in real time, receiving a control instruction input by a vehicle driving user, and calling an instance interface corresponding to the vehicle control class corresponding to the control instruction, so that the cloud server and the plurality of vehicle control application clients perform information interaction based on an Android operating system arranged on the vehicle.
2. The vehicle information interaction system of claim 1, wherein the plurality of vehicle control classes are at least one of the following control classes:
fault detection control, positioning control, vehicle lamp control, air conditioner control, wheel control, airbag control, transmission control, vehicle body control, and throttle control.
3. The vehicle information interaction system according to claim 1, wherein each vehicle control application client calls instance interfaces of a part of the control classes in the plurality of vehicle control classes through the network communication module to control the devices in the vehicle, and the control classes included in the part of the control classes called by each vehicle control application client are different or the same.
4. The vehicle information interaction system according to claim 1, wherein the vehicle control class includes: a message type, the cloud server further to,
and acquiring the message type of the equipment to be monitored through the network communication module, and calling an instance interface of a vehicle control class corresponding to the message type from the cpp file library so as to monitor the message of the equipment to be monitored in the running process of the vehicle.
5. The vehicle information interaction system of claim 1, wherein the hardware interface providing module comprises: a plurality of MCU codecs, each MCU codec for encoding and decoding vehicle data of different MCU types, the hardware interface providing module further for,
and analyzing the MCU type of the vehicle accessed to the network communication module, and determining an MCU codec corresponding to the MCU type.
6. The vehicle information interaction system according to claim 5, wherein the driving module drives the MCU codec in the hardware interface providing module through the MCU serial circuit to provide an API interface for services and functions of the vehicle corresponding to the MCU codec in an upper layer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710204258.7A CN108667869B (en) | 2017-03-30 | 2017-03-30 | Vehicle information interaction system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710204258.7A CN108667869B (en) | 2017-03-30 | 2017-03-30 | Vehicle information interaction system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108667869A CN108667869A (en) | 2018-10-16 |
| CN108667869B true CN108667869B (en) | 2020-09-15 |
Family
ID=63785643
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710204258.7A Active CN108667869B (en) | 2017-03-30 | 2017-03-30 | Vehicle information interaction system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108667869B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109409140B (en) * | 2018-10-17 | 2020-09-01 | 广汽丰田汽车有限公司 | Data storage method, device, readable storage medium and system of safety airbag |
| CN112015157B (en) * | 2019-05-29 | 2022-04-15 | 比亚迪股份有限公司 | Linux-based vehicle-mounted device interaction method and device, computer equipment and storage medium |
| CN111931753A (en) * | 2020-10-13 | 2020-11-13 | 蘑菇车联信息科技有限公司 | Internet of vehicles AI network interface implementation method and open platform system |
| CN112486599B (en) * | 2020-11-27 | 2023-10-31 | 北京罗克维尔斯科技有限公司 | Vehicle interface adaptation method, device, vehicle-mounted equipment and storage medium |
| CN113392044B (en) * | 2021-05-06 | 2024-08-30 | 深圳市广和通无线股份有限公司 | Positioning data transmission method and device based on Windows10 |
| CN114338636A (en) * | 2021-11-30 | 2022-04-12 | 重庆长安汽车股份有限公司 | Remote control instruction configuration type vehicle control system |
| CN115277744B (en) * | 2022-06-23 | 2023-05-26 | 重庆长安汽车股份有限公司 | Method for carrying out function definition and interactive design on remote control function of vehicle |
| CN115277099B (en) * | 2022-06-29 | 2024-07-19 | 锦图计算技术(深圳)有限公司 | Function safety method based on Android system and related equipment |
| CN115179939B (en) * | 2022-07-13 | 2025-06-24 | 岚图汽车科技有限公司 | Vehicle speed control service calling method and device |
| CN115092078B (en) * | 2022-07-13 | 2024-07-30 | 岚图汽车科技有限公司 | Vehicle body service calling method and device |
| CN115195765B (en) * | 2022-07-14 | 2025-06-27 | 岚图汽车科技有限公司 | Control method, device and electronic device for calling vehicle height control service |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104575062A (en) * | 2014-12-19 | 2015-04-29 | 阳珍秀 | Intelligent traffic control system and control method thereof |
| CN104808981A (en) * | 2015-03-19 | 2015-07-29 | 浙江大学 | Vehicle-mounted information system access control method based on Android platform |
| US9146603B2 (en) * | 2012-05-08 | 2015-09-29 | William Reber, Llc | Cloud computing system, vehicle cloud processing device and methods for use therewith |
| CN105450762A (en) * | 2015-12-03 | 2016-03-30 | 深圳市凯立德科技股份有限公司 | Vehicle networking device, cloud platform and system |
| US9363336B2 (en) * | 2012-02-09 | 2016-06-07 | Rockwell Automation Technologies, Inc. | Smart device for industrial automation |
-
2017
- 2017-03-30 CN CN201710204258.7A patent/CN108667869B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9363336B2 (en) * | 2012-02-09 | 2016-06-07 | Rockwell Automation Technologies, Inc. | Smart device for industrial automation |
| US9146603B2 (en) * | 2012-05-08 | 2015-09-29 | William Reber, Llc | Cloud computing system, vehicle cloud processing device and methods for use therewith |
| CN104575062A (en) * | 2014-12-19 | 2015-04-29 | 阳珍秀 | Intelligent traffic control system and control method thereof |
| CN104808981A (en) * | 2015-03-19 | 2015-07-29 | 浙江大学 | Vehicle-mounted information system access control method based on Android platform |
| CN105450762A (en) * | 2015-12-03 | 2016-03-30 | 深圳市凯立德科技股份有限公司 | Vehicle networking device, cloud platform and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108667869A (en) | 2018-10-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108667869B (en) | Vehicle information interaction system | |
| CN109032706B (en) | Intelligent contract execution method, device, equipment and storage medium | |
| US7793289B1 (en) | System accounting for operating system partitions | |
| US7263632B2 (en) | Programmatic computer problem diagnosis and resolution and automated reporting and updating of the same | |
| US20150067167A1 (en) | Hot pluggable extensions for access management system | |
| EP3590037A1 (en) | Constructing software delta updates for vehicle ecu software and abnormality detection based on toolchain | |
| US20080222617A1 (en) | Server side application integration framework | |
| CN113296950A (en) | Processing method, processing device, electronic equipment and readable storage medium | |
| KR20200090784A (en) | How to start an application, startup device and computer readable storage medium | |
| US7539743B2 (en) | Method and system of administration in a JMX environment comprising an administration application and software systems to be administered | |
| CN112835604A (en) | System gray scale version release management method, system, device and medium | |
| US10523581B2 (en) | Flighting of node controller in pilot mode in resource management system | |
| CN106055348A (en) | Method and device for informing system attribute updating | |
| US11531674B2 (en) | System and method for supporting rollback of changes made to target systems via an integration platform | |
| US11061715B2 (en) | Techniques for hybrid computer thread creation and management | |
| US20070044077A1 (en) | Infrastructure for verifying configuration and health of a multi-node computer system | |
| CA2543938C (en) | Programming and development infrastructure for an autonomic element | |
| CN115794219A (en) | Data source dynamic control method and device, electronic equipment and medium | |
| Staron | Software Architectures: Views and Documentation | |
| McGurren et al. | X-adapt: An architecture for dynamic systems | |
| Staron | Software Architectures—Views and Documentation | |
| CN115658134A (en) | Software version control method, device, equipment and storage medium | |
| Völter | A generative component infrastructure for embedded systems | |
| CN119718261A (en) | A vehicle software architecture and vehicle | |
| CN118277995A (en) | Method, equipment and medium for managing and controlling third party library based on sandbox isolation in application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |