CN106453465B - System and method for interworking between a vehicle controller and an external resource - Google Patents

System and method for interworking between a vehicle controller and an external resource Download PDF

Info

Publication number
CN106453465B
CN106453465B CN201510876215.4A CN201510876215A CN106453465B CN 106453465 B CN106453465 B CN 106453465B CN 201510876215 A CN201510876215 A CN 201510876215A CN 106453465 B CN106453465 B CN 106453465B
Authority
CN
China
Prior art keywords
vehicle
api
external
vehicle controller
external device
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
Application number
CN201510876215.4A
Other languages
Chinese (zh)
Other versions
CN106453465A (en
Inventor
金哲敏
金时浚
李东烈
金泳秀
金辰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hyundai Motor Co
Original Assignee
Hyundai Motor Co
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hyundai Motor Co filed Critical Hyundai Motor Co
Publication of CN106453465A publication Critical patent/CN106453465A/en
Application granted granted Critical
Publication of CN106453465B publication Critical patent/CN106453465B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/72Routing based on the source address
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/008Registering or indicating the working of vehicles communicating information to a remotely located station
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08Protocols for interworking; Protocol conversion
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30Services specially adapted for particular environments, situations or purposes
    • H04W4/40Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]

Abstract

The invention relates to a system and a method for interworking between a vehicle controller and an external resource. A system for interworking between a vehicle controller and an external resource includes at least one vehicle controller mounted within a vehicle and configured to control operation of the vehicle. The at least one external device provides processing information of the external resource based on a request of the vehicle controller. The vehicle movement gateway is connected to the vehicle controller via a vehicle internal network and to the external device via a vehicle external network, thereby interfacing so that the vehicle controller and the external device can communicate with each other.

Description

System and method for interworking between a vehicle controller and an external resource
Technical Field
The present invention relates to a system and method for interworking/linking (interworking) between a vehicle controller and an external resource, which provides a vehicle-oriented interface environment so that the vehicle controller can utilize the external resource of the external device.
Background
Due to the rapid development of the automobile industry in recent years, mechanical parts for vehicles have been remarkably developed, which has pushed the development of electric/electronic technology. For example, Information Technology (IT) has been considered as a key technology to realize vehicle control even if IT does not directly affect the vehicle control. Currently, infotainment (a compound word of information and entertainment) based on Audio Video Navigation Telematics (AVNT) has been applied. Accordingly, various attempts to apply IT to vehicles have been made through cooperation between automobile manufacturers and IT companies to achieve advanced vehicle control. For example, self-driving technology and various vehicular applications utilizing mobile devices have been developed. However, IT devices cannot be simply applied to a single unit of a vehicle or a conventional controller, and thus, various applications can be applied by communicating with the vehicle using conventional vehicle-to-device (V2D) technology.
Current V2D technology for interworking between vehicles and IT devices relies on IT companies, and thus, current V2D technology is configured based only on IT devices that treat vehicles as nodes. Namely, the following techniques are introduced: the picture of the IT device such as MirrorLink in the vehicle and the multimedia resource are utilized or the picture of the vehicle is displayed in the picture of the IT device based on the data of the vehicle collected and processed (analyzed, processed and remote communicated) by the IT device such as OpenXC. Such applications employ a user experience (UX) method in which a user can analyze a vehicle by using IT equipment, however, IT technology is not maximally utilized in terms of improving vehicle control performance.
As described above, conventional approaches for interworking between vehicles and IT technologies include embedding IT equipment in the vehicle in the form of a single item. This approach can increase the cost and weight of the vehicle and, due to installation limitations of IT equipment in the vehicle, there are limitations on utilization and performance. For example, if IT devices performing health management and biometric functions are installed in a vehicle, IT is not possible to know the driver's previous state before the driver enters the vehicle, because the corresponding functions can only be used when the driver is in the vehicle.
Another conventional method for interworking between vehicles and IT technology is to collect and utilize information (data) of the vehicle through interworking between IT devices outside the vehicle and a single controller inside the vehicle. The method enables the manipulation of the functionality of multimedia and other comfort systems inside the vehicle, or the use of new functionality of IT equipment in the vehicle. However, this second method also uses an approach (approach) oriented to UX, and thus, it controls only entertainment or information providing a level function. Therefore, in order to improve the vehicle control function using IT technology, there is a need to perform vehicle control using external resources.
Disclosure of Invention
The present invention has been made in view of the above problems, and provides a system and method for interworking between a vehicle controller and an external resource so that the vehicle controller can utilize the external resource of an external device required for vehicle control.
According to an embodiment of the inventive concept, a system for interworking between a vehicle controller and an external resource includes at least one vehicle controller installed within a vehicle and configured to control operation of the vehicle. The at least one external device provides processing information of the external resource based on a request from the vehicle controller. An Automobile Mobile Gateway (AMG) is connected to a vehicle controller via a vehicle internal network and to an external device via a vehicle external network, thereby interfacing so that the vehicle controller and the external device can communicate with each other.
The vehicle controller may include an Application Program Interface (API) generation section having an API set to utilize processing information provided by the external device in vehicle control. The API transmitting section is configured to request information required for vehicle control or transmit vehicle data according to an API called from the API set. The external information receiving section is configured to return processing information of the external device contained in a message received via the vehicle internal network to the vehicle controller. The first communication section is configured to connect the vehicle controller to a vehicle interior network.
The API transmitting section includes an API analyzing section configured to check validity and consistency of the called API. The message generation section is configured to generate a vehicle interior network message corresponding to the API that passes the validity and consistency checks.
The message generating section is configured to generate at least one vehicle interior network message for a single API.
The message generating part may analyze syntax of the API function that passes the inspection, and generate the vehicle interior network message from the analyzed API based on the generation rule.
The vehicle internal network message includes a header field, a payload field, and a trailer field.
The header fields contain information such as source, destination, message type, API function ID, node, total API size, start or end symbol of the API, and index.
The payload field contains a parameter flag, a parameter size and parameter data.
The external information receiving part includes an external information analyzing part configured to analyze the message received through the first communication part and extract the processing information of the external device. The API response generating section is configured to check stability when the processing information extracted from the external information analyzing section is applied, and generate an API response based on a result of the check.
When there is no abnormality in the stability, the API response generation portion may generate the API response by using the processing information of the external device and the vehicle interior data.
The AMG may include an external interworking API processing configured to perform protocol conversion from a vehicle internal network message to a vehicle external network message. The external calculation result processing part may convert the vehicle external network message into a vehicle internal network message.
The external device is an information communication device that provides resources.
The resources include infrastructure around the vehicle, cameras embedded in the portable device, Global Positioning Systems (GPS), gyroscopes, various sensors such as accelerometers, and include functions of the wearable device such as biometric identification, health management, and condition determination.
The external device includes a Database (DB) that accumulates and manages information about the condition of the driver before the driver enters the vehicle.
According to another embodiment of the inventive concept, a method for interworking between a vehicle controller and an external resource includes requesting, by the vehicle controller, use of the external resource of an external device through an Automobile Mobile Gateway (AMG). The request of the vehicle controller is sent to the external device by the AMG. The processing information based on the request of the vehicle controller is transmitted to the vehicle controller by the external device through the AMG.
Drawings
The objects, features and advantages of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings.
Fig. 1 is a block diagram illustrating a system for interworking between a vehicle controller and an external resource according to an embodiment of the inventive concept.
Fig. 2 is a block diagram illustrating a vehicle controller according to an embodiment of the inventive concept.
Fig. 3 is a diagram showing the arrangement of the message generation section shown in fig. 2.
Fig. 4 is a diagram showing the arrangement of the external information analysis section shown in fig. 2.
Fig. 5 is a diagram showing a configuration of an Application Program Interface (API) response generation section shown in fig. 2.
Fig. 6 is a flowchart illustrating a method for operating a vehicle controller according to an embodiment of the inventive concept.
Fig. 7 is a configuration of an external interworking API processing section of the car mobile gateway (AMG) shown in fig. 1.
Fig. 8 is a configuration of an external calculation result processing section of the AMG shown in fig. 1.
Fig. 9 is a diagram showing a configuration of the external device shown in fig. 1.
Fig. 10 is a flowchart illustrating a method for interworking between a vehicle controller and an external resource according to an embodiment of the inventive concept.
Symbols of the various elements of the drawings
11: vehicle controller
110: API generating section
112: API transmitting section
114: external information receiving unit
116: first communication unit
1200: API input unit
1202: API processing unit
1204: API output generation unit
1206: API output unit
1220: result input unit
1222: result processing unit
1224: result output generation unit
1226: result output unit
124: second communication unit
126: third communication unit
13: external device
130: API receiving part
132: API analysis section
134: information generating unit
136: result transmitting unit
138: fourth communication section
1101: external resource interworking API set
1120: API analysis section
1122: message generation unit
1140: external information analysis unit
1142: API response generation unit
1160: transmitting part
1162: receiving part
21: API syntax analysis part
22: generation rule storage unit
23: generating section
41: protocol analysis section
42: analysis rule storage unit
43: analysis section
S11: calling API for requesting/sending information
S13: analyzing contents of a called API
S15: content is consistent?
S17: generating a vehicle network message corresponding to the called API
S19: sending vehicle network messages
S21: does the reference time not elapse?
S23: receiving the processing result
S25: analyzing the processing results
S27: checking stability based on processing results
S29: generating API responses using processing results
S101: identifying external devices
S103: setting a vehicle communication environment
S105: requesting environment information of external device
S107: transmitting environment information of external device
S109: transmitting status information of a vehicle controller
S111: setting environment of external device
S113: requesting information from an external device
S115: sending requested information
S117: executing vehicle control
S119: sending execution results
Detailed Description
Exemplary embodiments of the present inventive concept are described in detail with reference to the accompanying drawings. The same reference numbers will be used throughout the drawings to refer to the same or like parts. A detailed description of well-known functions and constructions included herein may be omitted to avoid obscuring the subject matter of the present invention.
The present invention teaches gateway type interface technology that is vehicle-centric, enabling a vehicle controller to interwork with resources (external resources).
Fig. 1 is a block diagram showing a system for interworking between a vehicle controller and an external resource according to an embodiment of the inventive concept, fig. 2 is a block diagram showing the vehicle controller of the present invention, fig. 3 is a diagram showing a configuration of a message generating part shown in fig. 2, fig. 4 is a diagram showing a configuration of an external information analyzing part shown in fig. 2, and fig. 5 is a diagram showing a configuration of an API response generating part shown in fig. 2.
As shown in fig. 1, the system for interworking between a vehicle controller and an external resource may include at least one vehicle controller 11, an Automobile Mobile Gateway (AMG)12, and at least one external device 13.
The vehicle controller 11 may be an electronic device that controls a vehicle engine, a chassis, and electronic devices and comfort systems, etc. The vehicle controller 11 may include an Electronic Control Unit (ECU) that controls a battery, an engine, a transmission, a steering system, a suspension system, a brake system, etc., and a Body Control Module (BCM) that controls an air conditioning system, a cluster (cluster), a digital instrument panel, a wiper, a light source, rear obstacle detection equipment, an antitheft system, multiplex communication, a door lock, a power window, a power seat, a seatbelt, an airbag, etc.
The vehicle controller 11 may store a control program in a storage section (not shown), and control vehicle interior elements/elements by the control program.
The vehicle controller 11 may perform an operation by transmitting and receiving control information to and from each other using a vehicle internal network. Here, the vehicle internal network (hereinafter, referred to as a vehicle network) may use a Controller Area Network (CAN), a Media Oriented System Transfer (MOST) network, a Local Interconnect Network (LIN), an electronic wire control system (Flexray), or the like.
The AMG 12 may serve as an interface connecting the vehicle controller 11 and the external device 13. The AMG 12 may be installed in the vehicle interior along with the controller 11.
The AMG 12 may be connected to the vehicle controller 11 through a vehicle network, and may be connected to the external device 13 via a vehicle external network. Here, the vehicle-external network may include a wireless internet network such as a mobile communication network, Wi-Fi and WiBro, a short range communication network such as Bluetooth, Radio Frequency Identification (RFID) and Near Field Communication (NFC), and a vehicle communication network such as vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-device (V2D), and the like.
The AMG 12 may include an external interworking Application Program Interface (API) processing part 120 for requesting resource utilization of the external device 13 according to a request of the vehicle controller 11. The external calculation result processing section 122 is configured to transmit information obtained by the resource of the external device 13 to the vehicle controller 11. The second communication section 124 connects the external device 13 to the vehicle network, and the third communication section 126 connects the external device 13 to the vehicle external network.
The external device 13 may be an Information Technology (IT) device that provides an external resource. Here, the resource may include infrastructure around the vehicle, a camera embedded in the portable device, a Global Positioning System (GPS), a gyroscope, various apparatuses such as an accelerometer, and the like, and include functions such as biometric identification, health management, and status determination of the wearable device.
In order to maintain the communication system used by the existing vehicle controller, the above-described elements may configure the network layer by adding a base software layer to an upper layer of hardware.
As shown in fig. 1, the vehicle controller 11 may include an API generating section 110, an API transmitting section 112, an external information receiving section 114, and a first communication section 116.
The API generating part 110 may generate an API for executing a basic interface function used by the existing vehicle control logic so as to utilize information provided by a resource (external resource) of the external device 13. The API generating section 110 may store and manage the generated API as an external resource interworking API set 1101 (see fig. 2).
The external resource interworking API set 1101 may be composed of a set of interfaces such as Table 1.
[ TABLE 1 ]
Figure BDA0000866328310000081
The vehicle controller 11 may call the API from the API generating section to use the external resource 13. The API call sequence may vary depending on the use of the external resource 13.
The API transmission part 112 may request vehicle control or information required to transmit vehicle data (information required for control).
As shown in fig. 2, the API transmitting part 112 may include an API analyzing part 1120 and a message generating part 1122.
The API analyzing section 1120 may analyze the contents of the API called from the external resource interworking API set 1101, and may check the validity and consistency/matching (consistency) of the called API. The API call may generate at least one vehicle network message. However, in general, since the frequency bandwidth of the vehicle network may be limited, when the vehicle controller 11 unnecessarily calls the API or calls the wrong API in a random mode, the load of vehicle communication may be unnecessarily increased, which results in a waste of bandwidth. Therefore, in the present invention, the API analyzing section 1120 may function as a filter to prevent the waste of the bandwidth of the limited vehicle network.
The API analyzing part 1120 may check validity, communication environment conformity, and device performance of the device node against an OPEN (OPEN) API. In addition, the API analysis part 1120 may check the validity of the device node against a CLOSE (CLOSE) API, and may check the consistency of the data parameter range against other APIs. When an error is detected based on the verification result, the API analysis section 1120 may return the error.
The message generation unit 1122 may generate a valid vehicle internal network message (vehicle network message) for the API analyzed by the API analysis unit 1120. In other words, the message generation unit 1122 may generate a vehicle network message (vehicle communication message) corresponding to an API that passes the validity and consistency check of the API analysis unit 1120 among the called APIs.
The message generator 1122 may convert an API called for communication between the vehicle controller 11 and the AMG 12 into a vehicle network message, and may be an element required for the external resource interworking technology to have compatibility with the operating environment (communication input/output interface, protocol) of the existing vehicle controller.
Referring to fig. 3, the message generating part 1122 may include an API parsing part (parsing part) 21, a generation rule (pattern) storing part 22, and a generating part 23.
The API parsing part (parsing part) 21 may receive an API function to parse (parse) the syntax.
The generation rule (pattern) storage section 22 may be a rule for converting the API function into a vehicle network message.
The generation unit 23 may generate the vehicle network message from the syntax analyzed by the API parsing unit (analysis unit) 21 based on the generation rule. Meanwhile, the generating part 23 may generate at least one vehicle network message from a single API.
The vehicle network message may include a header field, a payload field, and a trailer field.
The header fields may store information such as Source (SRC), Destination (DEST), message type (normal or API), API function ID, node, total API size, start or end symbol of API, index, etc. The payload field may store information such as a parameter flag, a parameter size, and parameter data. The trailer field may be optionally used.
The first communication part 116 may include a transmission part 1160 and a reception part 1162.
The transmission unit 1160 may transmit the message generated by the message generation unit 1122 via the existing vehicle network. The receiving part 1162 may receive the message transmitted from the AMG 12 via the vehicle network.
The external information receiving part 114 may include an external information analyzing part 1140 and an API response generating part 1142.
The external information analyzing part 1140 may analyze the message received through the receiving part 1162 of the first communication part 116, and may extract the analysis result. The received message may include information (calculation result) requested by the vehicle controller 11 to the external resource 13.
As shown in fig. 4, the external information analysis section 1140 may include a protocol analysis section 41, an analysis rule storage section 42, and an analysis section 43.
The protocol analysis section 41 may analyze the message received from the AMG 12. The message may include a header field, a payload field, and a trailer field.
The header fields may store information such as Source (SRC), Destination (DEST), message type (normal or API), API function ID, node, size of the entire result (return value), start or end symbol, index, etc. The payload field may store information such as a result (return value) flag, a result size, and result data. The trailer field may be optionally used.
The analysis rule storage section 42 may store an analysis rule for analyzing the received information.
The analysis unit 43 may analyze the analyzed message based on the analysis rule. As the return values, the analysis section 43 may output the API function ID, the node, and the result data.
The API response generating part 1142 may check stability when the processing result output from the external information analyzing part 1140 is applied to vehicle control. In other words, as shown in fig. 5, the API response generating part 1142 may check (data consistency check) whether the range and type of data supplied from the external resource 13 are suitable for vehicle control by the stability checking part (SC).
When there is no abnormality in stability based on the verification result, the API response generation section 1142 may generate an API response by using the data received from the external resource 13 and the vehicle internal data. In this case, the API response generation unit 1142 may generate an API response having a structure format by the structure generation unit (SM). The API response generation section 1142 may return the generated API response to the vehicle controller 11.
Fig. 6 is a flowchart illustrating a method for operating a vehicle controller according to an embodiment of the inventive concept.
The vehicle controller 11 may call an API for requesting or transmitting information to the external device 13 (S11).
The vehicle controller 11 may analyze the contents of the called API (S13).
The vehicle controller 11 may check whether there is consistency in the analyzed content (S15).
When there is consistency in the analyzed content, the vehicle controller 11 may generate a vehicle network message by using the called API (S17). That is, the vehicle controller 11 may perform protocol conversion of the called API according to the protocol of the vehicle network.
The vehicle controller 11 may transmit the generated vehicle network message to the AMG 12 via the vehicle network (S19).
The vehicle controller 11 may check whether a reference time has elapsed after the transmission of the generated vehicle network message (S21).
The vehicle controller 11 may receive the processing result transmitted from the external device 13 within the reference time (S23).
The vehicle controller 11 may analyze the processing result received from the external device 13 (S25).
The vehicle controller 11 may check the stability when the analyzed processing result is applied to the vehicle control (S27).
Based on the check result, when there is no problem in the stability, the vehicle controller 11 may generate an API response by using the processing result (S29). The vehicle controller 11 may perform vehicle control according to the API response.
Fig. 7 is a configuration of an external interworking API processing section of the AMG shown in fig. 1, and fig. 8 is a configuration of an external calculation result processing section of the AMG shown in fig. 1.
Referring to fig. 7, AMG 12 may exchange information with each other between heterogeneous networks. Therefore, the vehicle controller 11 can transmit and receive information with external devices via the AMG 12 without changing hardware. Since there may be multiple vehicle controllers 11 and multiple external devices 13 at the same time, AMG 12 may support many-to-many bidirectional communication.
The AMG 12 may transmit an information request of the vehicle controller 11 to the external device 13 in real time, and may transmit information provided from the external device 13 to the vehicle controller 11 in real time.
AMG 12 may include an external interworking API processing section 120 and an external computation result processing section 122. The AMG 12 may be installed inside the vehicle controller 11 in the form of software.
The external interworking API processing part 120 may transmit the API call generated by the vehicle controller 11 to the external device 13. The external interworking API processing part 120 may perform protocol conversion from the vehicle internal network message to the vehicle external network message.
As shown in fig. 1, the external interworking API processing section 120 may include an API input section 1200, an API processing section 1202, an API output generation section 1204, an API output section 1206, and a buffer section.
The API input portion 1200 may receive API request information transmitted from the vehicle controller 11 via the vehicle interior network. The API input section 1200 may receive, as input, API request information received via the second communication section 124. API input 1200 may be implemented as a receive Queue (RX Queue).
The API processing section 1202 may perform protocol conversion of the vehicle interior network message received via the API input section 1200 by the analysis section, and the analysis section may analyze the converted message according to the analysis result.
The API output generating part 1204 may include a protocol analyzing part for analyzing a vehicle external network protocol, a security module for completing authentication and encryption in order to secure a message, and a generating part for generating a vehicle external network message. The API output generation unit 1204 may convert the vehicle internal network message into a message transmitted via the vehicle external network.
The API output section 1206 may transmit the message output from the API output generation section 1204 via the vehicle external network. In this case, the API output 1206 may be implemented in the form of a transmit Queue (TX Queue).
The fourth communication section 126 can transmit the message transmitted via the API output section 1206 to the external device 13 through the external network of the vehicle.
The external interworking API processing section 120 may include a buffer section implemented by a shared memory section, a dual port memory section, or a buffer section for high-speed serial communication.
Referring to fig. 8, the external calculation result processing part 122 may again transmit the calculation/processing result of the external resource 13 for the API call of the vehicle controller 11 to the vehicle controller 11. The external calculation result processing part 122 may convert the vehicle external network message into a vehicle internal network message.
As shown in fig. 1, the external calculation result processing section 122 may include a result input section 1220, a result processing section 1222, a result output generation section 1224, a result output section 1226, and a buffer section.
The result input part 1220 may receive an input of a message received through the second communication part 126. The result input part 1220 may be implemented by a receive QUEUE (RX QUEUE).
The result processing part 1222 may include a protocol analyzing part for analyzing a protocol of a message received through the vehicle external network, an analysis rule (pattern), a security module for completing verification and decryption of the received message, and an analyzing part for analyzing the received message based on the analysis rule.
The result output generating part 1224 may include a protocol analyzing part for analyzing a protocol of the vehicle interior network, a generating rule (pattern) for generating (converting) a vehicle interior network message from a received message according to the generating rule (pattern), and a generating part.
The result output part 1226 may transmit the message generated by the result output generation part 1224 to the vehicle controller 11 via the vehicle internal network. The result output section 1226 may be realized by a transmission QUEUE (TX QUEUE).
Fig. 9 is a diagram showing the configuration of the external device shown in fig. 1.
As described above, when receiving a request for information necessary for vehicle control from the vehicle controller 11, the external device 13 may collect information from various sensors and calculate the collected information to return the calculation result to the vehicle controller 11.
For example, the external device 13 may be various types of smart/wearable devices that are capable of performing high-performance computing processing that is difficult to handle in a vehicle, equipped with sensors that are difficult to install in a vehicle, or the external device 13 may be an external IT environment that is itself connected to a vehicle.
As shown in fig. 9, the external device 13 may include an API receiving section 130, an API analyzing section 132, a result generating section 134, a result transmitting section 136, and a fourth communication section 138.
The API receiving part 130 may receive the vehicle external network message received via the fourth communication part 138.
The API receiving part 130 may parse the vehicle external network message, and may complete authentication and decryption. Next, the API receiving part 130 may analyze the vehicle external network message according to the analysis rule.
The API analysis portion 132 may check the request of the vehicle controller 11 by analyzing the API syntax based on the generation rule.
The result generation portion 134 may generate information according to a request of the vehicle controller 11. The result transmitting part 136 may convert the information generated by the result generating part 134 into a vehicle outside network message.
In the case of a wearable device or a smart phone, since the external device 13 can accumulate and process various previous conditions before the driver gets on the vehicle, it is possible to utilize accumulated history information by preparing a Database (DB) within the external device 13. Next, in order to transmit and receive data with the AMG 12 via the external network of the vehicle, the external device 13 is equipped with a communication module and a security module equivalent to the hierarchy of the AMG 12.
Fig. 10 is a flowchart illustrating a method for interworking between a vehicle controller and an external resource according to an embodiment of the inventive concept.
First, the vehicle controller 11 may generate a recognizable external device 13 as a communication node, and set a vehicle communication environment with the external device 13 (S101, S103). At this time, the vehicle controller 11 and the AMG 12 may set a vehicle internal network, and the AMG 12 and the external device 13 may set a vehicle external network. The AMG 12 may convert a message transmitted from the vehicle controller into a vehicle external network message to transmit to the external device 13, and convert a message transmitted from the external device 13 into a vehicle internal network message to transmit to the vehicle controller 11.
The vehicle controller 11 may request environmental information of the external device 13 (S105). Here, the environment information may include information on the external device 13 capable of interworking with the vehicle controller 11 among the at least one external device 13 and information on resources available in the external device 13.
Based on the request of the vehicle controller 11, the external device 13 may transmit the environmental information of the external device 13 (S107).
Based on the request of the external device 13, the vehicle controller 11 may transmit the status information of the vehicle controller 11 (S109).
The vehicle controller 11 may set an environment (configuration) and available resources required by the external device 13 capable of interworking with the vehicle controller 11 based on the environment information of the external device 13 (S111).
The vehicle controller 11 may request information required for vehicle control to the external device 13 (S113).
The external device 13 may transmit information obtained from an external resource to the vehicle controller 11 according to a request of the vehicle controller 11 (S115).
The vehicle controller 11 may perform vehicle control by using information provided from the external device 13, and may transmit the execution result to the external device 13(S117, S119).
As described above, since the present invention provides an interface capable of utilizing resources of an external device required for vehicle control, a vehicle controller can improve control performance of a vehicle by utilizing the external resource.
Further, according to the present invention, since additional hardware is not added, IT is possible to utilize a new IT function without increasing cost and weight.
Further, the limitation of installing the apparatus in the vehicle can be overcome.
Furthermore, the latest IT technology can be easily used for vehicle control.
Although exemplary embodiments of the inventive concept have been described in detail hereinabove, it should be clearly understood that many variations and modifications of the basic inventive concept herein taught which may appear to those skilled in the present art will still fall within the spirit and scope of the present invention, as defined in the appended claims.

Claims (22)

1. A system for interworking between a vehicle controller and an external resource, the system comprising:
at least one vehicle controller mounted within the vehicle and configured to control operation of the vehicle;
at least one external device that provides processing information of an external resource based on a request from the vehicle controller; and
a car mobile gateway AMG connected to the vehicle controller via a vehicle internal network and to the external device via a vehicle external network so as to interface such that the vehicle controller and the external device communicate with each other,
wherein the vehicle controller controls the operation of the vehicle based on information obtained by the external resource in the external device.
2. The system of claim 1, wherein the vehicle controller comprises:
an Application Program Interface (API) generation unit having an API set and configured to utilize processing information provided by the external device in vehicle control;
an API transmitting part configured to request information required for vehicle control or transmit vehicle data according to an API called from the API set;
an external information receiving section configured to return processing information of an external device contained in a message received via a vehicle internal network to the vehicle controller; and
a first communication section configured to connect the vehicle controller to a vehicle interior network.
3. The system of claim 2, wherein the API sending part comprises:
an API analysis section configured to check validity and consistency of the called API; and
a message generating part configured to generate a vehicle interior network message corresponding to the API that passes the validity and consistency checks.
4. The system of claim 3, wherein the message generating portion is configured to generate at least one vehicle interior network message for a single API.
5. The system according to claim 3, wherein the message generating section is configured to analyze syntax of the API that passes the check, and is configured to generate the vehicle interior network message from the analyzed API based on the generation rule.
6. The system of claim 5, wherein the vehicle internal network message comprises a header field, a payload field, and a trailer field.
7. The system of claim 6, wherein the header fields include the following information: source, destination, message type, API function ID, node, total API size, start symbol of API or end symbol of API, and index.
8. The system of claim 6, wherein the payload field includes a parameter flag, a parameter size, and parameter data.
9. The system according to claim 2, wherein the external information receiving section includes:
an external information analysis section configured to analyze the message received through the first communication section and extract processing information of an external device; and
an API response generating section configured to check stability when the processing information extracted from the external information analyzing section is applied, and configured to generate an API response based on a result of the check.
10. The system according to claim 9, when there is no abnormality in stability, the API response generation section is configured to generate an API response by using processing information of an external device and vehicle interior data.
11. The system of claim 1, wherein the AMG comprises:
an external interworking API processing part configured to perform protocol conversion from a vehicle interior network message to a vehicle exterior network message; and
an external calculation result processing part configured to convert the vehicle external network message into a vehicle internal network message.
12. The system of claim 1, wherein the external device is an information communication device that provides an external resource.
13. The system of claim 12, wherein the external resources include infrastructure around the vehicle, cameras embedded in the portable device, global positioning systems, gyroscopes, sensors, and include functionality of the wearable device.
14. The system of claim 13, the sensor being an accelerometer.
15. The system of claim 13, the functions of the wearable device are functions of biometric identification, health management, and condition determination.
16. The system of claim 12, wherein the external device includes a database that accumulates and manages information about the condition of the driver before the driver enters the vehicle.
17. A method for interworking between a vehicle controller and an external resource, the method comprising the steps of:
requesting, by the vehicle controller, use of an external resource of the external device through the car mobile gateway AMG;
transmitting, by the AMG, a request of the vehicle controller to the external device; and
process information based on a request of the vehicle controller is transmitted to the vehicle controller through the AMG by the external device,
wherein the vehicle controller controls the operation of the vehicle based on information obtained by the external resource in the external device.
18. The method of claim 17, further comprising, prior to the requesting step, the steps of:
generating, by a vehicle controller, a communication node from an external device; and
the vehicle communication environment is set with the external device.
19. The method of claim 17, wherein the requesting step comprises:
the environmental information and information required for vehicle control are requested.
20. The method of claim 17, wherein the step of transmitting comprises:
environmental information of the external device and status information of the vehicle controller are transmitted.
21. The method of claim 17, wherein the transmitting step comprises:
the processing information obtained from the external resource according to the request of the vehicle controller is transmitted to the vehicle controller, and the execution result is transmitted to the external device.
22. The method of claim 17, further comprising the steps of:
an environment required for an external device interworking with the vehicle controller is set by the vehicle controller, and an external resource is set based on the environment required for the external device.
CN201510876215.4A 2015-08-12 2015-12-03 System and method for interworking between a vehicle controller and an external resource Active CN106453465B (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020150114023A KR101664734B1 (en) 2015-08-12 2015-08-12 System and method for interworking between vehicle controller and external resource
KR10-2015-0114023 2015-08-12

Publications (2)

Publication Number Publication Date
CN106453465A CN106453465A (en) 2017-02-22
CN106453465B true CN106453465B (en) 2020-12-18

Family

ID=57173452

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510876215.4A Active CN106453465B (en) 2015-08-12 2015-12-03 System and method for interworking between a vehicle controller and an external resource

Country Status (4)

Country Link
US (1) US10298492B2 (en)
KR (1) KR101664734B1 (en)
CN (1) CN106453465B (en)
DE (1) DE102015223512A1 (en)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020513708A (en) * 2016-12-09 2020-05-14 ホアウェイ・テクノロジーズ・カンパニー・リミテッド Interface, vehicle control system and network equipment for combining vehicle control with communication services
US11208060B2 (en) 2017-07-20 2021-12-28 Les Systèmes Cyberkar Configurable management system for a vehicle and method of use
US10424127B2 (en) * 2017-08-28 2019-09-24 GM Global Technology Operations LLC Controller architecture for monitoring health of an autonomous vehicle
DE102017222879A1 (en) 2017-12-15 2019-06-19 Volkswagen Aktiengesellschaft Apparatus, method, and computer program for enabling a vehicle component, vehicle-to-vehicle communication module
DE102017222882A1 (en) 2017-12-15 2019-06-19 Volkswagen Aktiengesellschaft Devices, methods and computer program for unlocking vehicle components, vehicle-to-vehicle communication module
US11560240B2 (en) 2018-03-29 2023-01-24 Airbus Operations Gmbh Aircraft area having a textile display, aircraft passenger seat having a textile display, and aircraft including an aircraft area
EP3546355B1 (en) * 2018-03-29 2021-07-07 Airbus Operations GmbH Aircraft area having a textile display, and an aircraft including such an aircraft area
CN110392067B (en) * 2018-04-16 2021-07-20 比亚迪股份有限公司 Development system and method of third-party application
CN110389538A (en) * 2018-04-20 2019-10-29 比亚迪股份有限公司 Vehicle and its vehicle safety control method, system based on open platform
EP3849150B1 (en) * 2018-09-04 2023-03-15 BYD Company Limited Secure open api for a vehicle
US10574794B1 (en) 2019-07-12 2020-02-25 Coupang Corp. Systems and methods for interfacing networks regardless of communication scheme
US10582019B1 (en) 2019-07-12 2020-03-03 Coupang Corp. Systems and methods for interfacing networks using a unified communication scheme

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1468409A (en) * 2000-08-18 2004-01-14 Nnt��˾ System, method and computer program product for remote vehicle diagnostics, monitoring, configuring and reprogramming
CN104142660A (en) * 2013-05-09 2014-11-12 洛克威尔自动控制技术股份有限公司 Remote assistance via a cloud platform for industrial automation

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070013129A (en) * 2005-07-25 2007-01-30 주식회사 팬택앤큐리텔 Mobile communication terminal having car control function and its method, and car control device by using controller area network
US8694328B1 (en) * 2006-12-14 2014-04-08 Joseph Gormley Vehicle customization and personalization activities
KR20090022038A (en) * 2007-08-29 2009-03-04 한국교통연구원 Car navigation system with image black box
US7822828B2 (en) * 2007-09-17 2010-10-26 Gm Global Technology Operations, Inc. System for using non-standard transfer protocol from software received at in-vehicle communications gateway for exchanging data with client device
KR20100000823A (en) * 2008-06-25 2010-01-06 아주대학교산학협력단 Intelligent system for vehicle stabilization driving assistance
KR100946991B1 (en) * 2008-08-22 2010-03-10 한국전자통신연구원 Vehicle Gateway, Apparatus and Method for Vehicle Network Interface
JP2010206697A (en) 2009-03-05 2010-09-16 Honda Motor Co Ltd Onboard communication network system and malfunction diagnostic method of the same
KR20120062089A (en) 2010-12-06 2012-06-14 한국전자통신연구원 Vehicle mobile gateway for controling charging of electric vehicle using mobile terminal, electric vehicle having the same, and method for controling charging of electric vehicle using mobile terminal
KR102002420B1 (en) 2013-01-18 2019-10-01 삼성전자주식회사 Smart home system with portable gateway
DE202013100347U1 (en) * 2013-01-24 2013-03-05 Ford Global Technologies, Llc If necessary activatable remote control system for motor vehicles
KR101491293B1 (en) * 2013-08-09 2015-02-10 현대자동차주식회사 Gateway apparatus and message routing method thereof
KR101509707B1 (en) * 2013-08-26 2015-04-07 현대자동차 주식회사 Vehicle control system and virtual electronic control unit development method

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1468409A (en) * 2000-08-18 2004-01-14 Nnt��˾ System, method and computer program product for remote vehicle diagnostics, monitoring, configuring and reprogramming
CN104142660A (en) * 2013-05-09 2014-11-12 洛克威尔自动控制技术股份有限公司 Remote assistance via a cloud platform for industrial automation

Also Published As

Publication number Publication date
US20170043731A1 (en) 2017-02-16
US10298492B2 (en) 2019-05-21
KR101664734B1 (en) 2016-10-12
DE102015223512A1 (en) 2017-02-16
CN106453465A (en) 2017-02-22

Similar Documents

Publication Publication Date Title
CN106453465B (en) System and method for interworking between a vehicle controller and an external resource
CN112291124B (en) Vehicle-mounted network ECU communication method based on SOME/IP protocol
US10511668B2 (en) Method of transmitting and receiving data in vehicle network and apparatus for the same
CN110741341A (en) Update couriers for vehicle computing devices
JP2005529531A (en) Method and apparatus for telematic service for vehicles
US10750339B2 (en) System for dynamically allocating services between controllers in an automobile
CN112055952A (en) Vehicle-mounted equipment upgrading method and related equipment
US9596225B2 (en) Out-of-vehicle device interface apparatus and method for protecting in-vehicle network
US9174648B2 (en) System for using short text messaging for remote diagnostic
US20180063246A1 (en) Method and apparatus for efficient data transfer protocol in a limited-bandwidth vehicle environment
CN106506583B (en) Method and system for wireless data transmission of vehicle computing system
CN105005539A (en) Authenticating data at a microcontroller using message authentication codes
US20150046342A1 (en) System and method for telematics service of vehicle
CN108702808B (en) Base station for receiving and processing vehicle control information and/or traffic condition information
Ai et al. OSGi based integrated service platform for automotive telematics
KR101126640B1 (en) System and method for diagnosticating of most network using wireless network
JP2003244187A (en) On-vehicle gateway device and computer program
KR100879888B1 (en) Vehicle ID Service System ? Method Using ECU
KR20150068517A (en) An opening method of the telematics service
Kim et al. Design and implementation of status based application manager for telematics
CN219761329U (en) Vehicle communication system and vehicle
CN106293324B (en) Vehicle computing system and method for communicating mobile device lock icons
JP6341231B2 (en) Vehicle information communication system and application program
CN105453522A (en) Method for providing a function in a computer system of a vehicle
US11122489B2 (en) On-board vehicular communication system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant