Standard controller and control system including standard controller

Abstract

This control system for a device having mobility may comprise: standard controllers installed in any one of a plurality of areas of the device and configured to detect an input for a function related to a component connected thereto, and generate and transmit an input control signal corresponding to the detected input, or configured to detect an output control signal corresponding to an output for the function related to the component connected thereto and perform control corresponding to the output control signal; a central computer configured to define the function and determine an association between the input and the output to generate an output control signal corresponding to the input control signal for the function; and a gateway controller configured to transfer the input control signal and the output control signal between the standard controllers and the central computer.

Description

Standard controller, control system including standard controller

[0001] The present invention relates to a standard controller and a control system including the standard controller, and more particularly, to an electric and electronic platform of a vehicle including the standard controller, and to a standard controller, a control system including the standard controller, and a connection structure between each component.

[0002] Conventional techniques, when designing vehicle signal input / output circuits, typically involved checking the input / output specifications of the component to which the wiring harness is connected and then configuring an optimized circuit that meets these specifications with a small margin. This approach offers advantages such as reduced material costs when the controller uses a small number of vehicle signal inputs / outputs. However, when the controller uses a large number of vehicle inputs / outputs, the time required for each circuit configuration and software logic implementation increases, resulting in higher development costs.

[0003] In addition, due to the optimized design, it was very difficult to use the same circuit for other parts, and circuit modifications such as small changes in RC time constants or large changes in ICs were required, which resulted in the need to add new signals or develop a new controller itself when making changes.

[0004] In addition, the controllers and components (sensors / actuators) within the vehicle were designed to be connected based on function and have independent structures separated from the controllers of other functions. Therefore, the signals from components connected to one controller could not be used in other controllers. In addition, in order for the controller and components to operate as one function, direct wire connections were required for signal transmission even when they were far apart, which increased the length / weight of the wiring harness within the vehicle. In addition, since the signals required for each controller were not shared with each other, signals such as ACC and IGN that are commonly used by many controllers were duplicated, which also increased the length / weight of the wiring harness.

[0005] Accordingly, an electrical and electronic architecture was proposed, enabling the design of more flexible and efficient in-vehicle controllers and their associated wiring.

[0006] This proposal does not stop there, but proposes a controller and its connection structure that allows for the addition or change of parts or functions simply by updating the software to provide flexibility in adding parts or changing functions of the vehicle.

[0007] In accordance with the aforementioned background, the present invention seeks to provide a standard controller and a control system including the standard controller, and a connection structure between each component within the control system.

[0008] In addition, the present invention seeks to provide a standard controller for controlling a vehicle as well as a mobile device, a control system including the standard controller, and a connection structure between each component within the control system.

[0009] The objectives of the present invention are not limited to those described above. Other objectives not described above can be readily understood by those skilled in the art from the following description of the present invention.

[0010] A control system for a device having mobility is proposed, the control system comprising at least one standard controller installed in one of a plurality of areas of the device and configured to detect an input for a function related to a component connected thereto and generate and transmit an input control signal corresponding to the detected input, or to detect an output control signal corresponding to an output for a function related to the component connected thereto and perform a control corresponding to the output control signal, wherein the standard controller may include a processor including a register mapping and drive control unit configured to perform settings for registers of a high current driver, a low current driver or a switch detector according to a set signal database.

[0011] Additionally or alternatively, the standard controller may include a high-current driver configured to output a high-current drive signal to the connected component, a low-current driver configured to output a low-current drive signal to the connected component, and a switch detector configured to detect a change in the input signal.

[0012] Additionally or alternatively, the standard controller may be configured to determine whether the received signal is a signal related to itself based on the ID of the received signal, and if the received signal is a signal related to itself, output an input or output control signal corresponding to the received signal; and if the received signal is not a signal related to itself, ignore the received signal.

[0013] Additionally or alternatively, the signal database may contain signals for individual functions associated with the components connected to it.

[0014] Additionally or alternatively, the signal is generated according to a standard signal structure, which may include a signal identifier (ID), an indicator indicating whether the signal is an input or output signal, activation status information of the signal expressed as active high or low, standard controller or area information within the device, connected driver or switch detector information, and pin information of the connected driver or switch detector.

[0015] Additionally or alternatively, the standard controller may be configured to detect an input for an individual function associated with a component connected thereto, generate an input control signal corresponding to the detected input, and transmit the generated input control signal to a gateway controller or a central computer.

[0016] Additionally or alternatively, the standard controller may be configured to detect output control signals for individual functions associated with components connected thereto, and to perform control for the components connected thereto in accordance with the detected output control signals.

[0017] Additionally or alternatively, the input control signal and the output control signal may include: a signal identifier (ID) and information about a state value or a state value change associated with the component.

[0018] Additionally or alternatively, the standard controller may be configured to receive output control signals for the function from the central computer.

[0019] Additionally or alternatively, if there are a plurality of said at least one standard controllers, each of the standard controllers may be configured to be communicatively connected to one another, each of the standard controllers may be communicatively connected to a gateway controller, and the gateway controller may be configured to be communicatively connected to a central computer.

[0020] The solutions of the present invention described above are some of the embodiments of the present invention. Various solutions other than the solutions described above can be derived and understood based on the detailed description of the present invention described below.

[0021] The present invention has the following effects.

[0022] By placing standard controllers in multiple areas within the device, the length and weight of the wiring harness can be reduced.

[0023] It is a three-layer structure consisting of a standard controller, a central control unit (gateway controller), and a central computer (or vehicle computer). The standard controller and the central computer, to which the parts are directly connected, are separated, and their respective roles are distributed, allowing for flexible response to part updates or function updates.

[0024] The effects of the present invention are not limited to those described above. Other effects not described above can be understood by those skilled in the art from the following description of the present invention.

[0025] The accompanying drawings, which are incorporated in and constitute a part of the detailed description to aid in understanding the present invention, provide examples of the present invention and, together with the detailed description, explain the content of the present invention.

[0026] Figure 1 is a block diagram of the entire autonomous vehicle to which an autonomous driving device can be applied.

[0027] Figure 2 is an example diagram showing an example of an autonomous driving device being applied to a vehicle.

[0028] Figure 3 illustrates an in-vehicle control architecture according to the present invention.

[0029] Figure 4 shows signal and drive standardization for driving vehicle components according to the present invention.

[0030] Figure 5 illustrates the standardization of signals and interfaces for communication and sound for vehicle components according to the present invention.

[0031] Figure 6 shows the connection structure between the standard controller and components according to the present invention.

[0032] Figure 7 shows a connection structure between a standard controller, a gateway controller, and a vehicle computer according to the present invention.

[0033] Figure 8 shows a detailed configuration of a standard controller according to the present invention, a connection structure between the standard controller and components, and a connection structure between the standard controller, a gateway controller, and a vehicle computer.

[0034] Figure 9 shows a connection structure between a signal DB and a standard controller and components according to the present invention.

[0035] Figure 10 is a diagram for explaining a change or double connection of the connection between a standard controller and components according to the present invention.

[0036] Figure 11 illustrates a connection structure between a standard controller and a vehicle computer for adding new functions using components according to the present invention.

[0037] Figure 12 is a diagram for explaining the implementation of a function using a standard controller according to the present invention.

[0038] Figure 13 is a diagram for explaining the implementation of a function using a standard controller according to the present invention.

[0039] Figure 14 illustrates a connection structure between a standard controller, a gateway controller, and a vehicle computer according to the present invention.

[0040] Figure 15 illustrates a connection structure for explaining a function utilizing a component according to the present invention.

[0041] Figure 16 shows a software structure for a vehicle control system according to the present invention.

[0042] Figure 17 is a diagram for explaining the addition of components according to a conventional controller.

[0043] Figure 18 is a diagram for explaining the addition of components according to the standard controller according to the present invention.

[0044] Figure 19 is a diagram for explaining the addition of components according to a conventional controller.

[0045] Figure 20 is a diagram for explaining the addition of components according to a standard controller according to the present invention.

[0046] Figure 21 shows a block diagram of a standard controller according to the present invention.

[0047] Hereinafter, an embodiment of the present invention will be described with reference to the attached drawings.

[0048] The embodiments described below are intended to aid understanding of the present invention, and therefore, the present invention is not limited to the embodiments described below. Furthermore, in the attached drawings, certain components may be exaggerated or reduced in size to aid understanding of the invention. The present invention is not limited to the forms depicted in the attached drawings.

[0049] Throughout the specification, whenever a part is said to "include" a component, this does not mean that it excludes other components, but rather that it may include other components, unless otherwise stated.

[0050] Additionally, in the specification, the terms “passenger”, “driver”, “user”, etc. are mentioned to describe the invention, and it is noted that these may be used interchangeably.

[0051] FIG. 1 is a block diagram of an entire autonomous driving control system to which an autonomous driving device according to any one of the embodiments of the present invention can be applied.

[0052] FIG. 2 is an exemplary diagram showing an example of an autonomous driving device according to one embodiment of the present invention being applied to a vehicle.

[0053] First, with reference to FIGS. 1 and 2, the structure and function of an autonomous driving control system (e.g., an autonomous vehicle) to which the autonomous driving device according to the present embodiments can be applied will be described.

[0054] As illustrated in FIG. 1, an autonomous vehicle (1000) may be implemented centering around an autonomous driving integrated control unit (600) that transmits and receives data necessary for autonomous driving control of the vehicle through a driving information input interface (101), a driving information input interface (201), a passenger output interface (301), and a vehicle control output interface (401). However, the autonomous driving integrated control unit (600) may also be referred to as a controller, a processor, or simply a control unit in the specification.

[0055] The autonomous driving integrated control unit (600) can obtain driving information according to the passenger's operation of the user input unit (100) in the autonomous driving mode or manual driving mode of the vehicle through the driving information input interface (101). As illustrated in FIG. 1, the user input unit (100) may include a driving mode switch (110) and a control panel (120) (e.g., a navigation terminal mounted on the vehicle, a smartphone or tablet PC carried by the passenger, etc.), and accordingly, the driving information may include the vehicle's driving mode information and navigation information.

[0056] For example, the driving mode of the vehicle (i.e., autonomous driving mode / manual driving mode or sports mode / eco mode / safe mode / normal mode) determined according to the passenger's operation of the driving mode switch (110) can be transmitted to the autonomous driving integrated control unit (600) as the driving information through the driving information input interface (101).

[0057] In addition, navigation information such as the passenger's destination and the route to the destination (the shortest route or preferred route selected by the passenger among candidate routes to the destination) input by the passenger through the control panel (120) can be transmitted to the autonomous driving integrated control unit (600) through the driving information input interface (101) as the above-mentioned driving information.

[0058] Meanwhile, the control panel (120) may be implemented as a touch screen panel that provides a UI (User Interface) for the driver to input or modify information for autonomous driving control of the vehicle, and in this case, the driving mode switch (110) described above may be implemented as a touch button on the control panel (120).

[0059] In addition, the autonomous driving integrated control unit (600) can obtain driving information indicating the driving state of the vehicle through the driving information input interface (201). The driving information may include various information indicating the driving state and behavior of the vehicle, such as a steering angle formed as a passenger operates the steering wheel, an accelerator pedal stroke or a brake pedal stroke formed as a passenger presses the accelerator pedal or the brake pedal, and a behavior formed in the vehicle, such as vehicle speed, acceleration, yaw, pitch, and roll, and each of the driving information can be detected by a driving information detection unit (200) including a steering angle sensor (210), an APS (Accel Position Sensor) / PTS (Pedal Travel Sensor) (220), a vehicle speed sensor (230), an acceleration sensor (240), and a yaw / pitch / roll sensor (250), as illustrated in FIG. 1.

[0060] Furthermore, the vehicle's driving information may include vehicle location information, which may be acquired through a GPS (Global Positioning System) receiver (260) installed in the vehicle. This driving information may be transmitted to the autonomous driving integrated control unit (600) through the driving information input interface (201) and utilized to control the vehicle's driving in autonomous driving mode or manual driving mode.

[0061] In addition, the autonomous driving integrated control unit (600) can transmit driving status information provided to the passenger in the autonomous driving mode or manual driving mode of the vehicle to the output unit (300) through the passenger output interface (301). That is, the autonomous driving integrated control unit (600) can transmit the driving status information of the vehicle to the output unit (300), thereby allowing the passenger to check the autonomous driving status or manual driving status of the vehicle based on the driving status information output through the output unit (300), and the driving status information can include various information indicating the driving status of the vehicle, such as the current driving mode of the vehicle, the shift range, and the vehicle speed.

[0062] In addition, if the autonomous driving integrated control unit (600) determines that a warning is required for the driver in the autonomous driving mode or manual driving mode of the vehicle along with the driving status information described above, the warning information may be transmitted to the output unit (300) through the passenger output interface (301) so that the output unit (300) may output a warning to the driver. In order to output the driving status information and warning information audibly and visually, the output unit (300) may include a speaker (310) and a display device (320) as illustrated in FIG. 1. At this time, the display device (320) may be implemented as the same device as the control panel (120) described above, or may be implemented as a separate, independent device.

[0063] In addition, the autonomous driving integrated control unit (600) can transmit control information for driving control of the vehicle in the autonomous driving mode or manual driving mode of the vehicle to the lower control system (400) applied to the vehicle through the vehicle control output interface (401). The lower control system (400) for driving control of the vehicle can include an engine control system (410), a braking control system (420), and a steering control system (430) as illustrated in FIG. 1, and the autonomous driving integrated control unit (600) can transmit engine control information, braking control information, and steering control information as the control information to each lower control system (410, 420, 430) through the vehicle control output interface (401). Accordingly, the engine control system (410) can control the speed and acceleration of the vehicle by increasing or decreasing the fuel supplied to the engine, the brake control system (420) can control the braking of the vehicle by adjusting the braking force of the vehicle, and the steering control system (430) can control the steering of the vehicle through a steering device applied to the vehicle (e.g., a Motor Driven Power Steering (MDPS) system).

[0064] As described above, the autonomous driving integrated control unit (600) of the present embodiment obtains driving information according to the driver's operation and driving information indicating the driving status of the vehicle through the driving information input interface (101) and the driving information input interface (201), respectively, and transmits driving status information and warning information generated according to the autonomous driving algorithm to the output unit (300) through the passenger output interface (301), and also transmits control information generated according to the autonomous driving algorithm to the lower control system (400) through the vehicle control output interface (401) so that the vehicle driving control is performed.

[0065] Meanwhile, in order to ensure stable autonomous driving of a vehicle, it is necessary to continuously monitor the driving state by accurately measuring the driving environment of the vehicle and control driving according to the measured driving environment. To this end, the autonomous driving device of the present embodiment may include a sensor unit (500) for detecting objects around the vehicle, such as surrounding vehicles, pedestrians, roads, or fixed facilities (e.g., traffic lights, milestones, traffic signs, construction fences, etc.), as illustrated in FIG. 1.

[0066] The sensor unit (500) may include one or more of a lidar sensor (510), a radar sensor (520), and a camera sensor (530) to detect surrounding objects outside the vehicle, as illustrated in FIG. 1.

[0067] The lidar sensor (510) can detect surrounding objects outside the vehicle by transmitting a laser signal around the vehicle and receiving a signal that is reflected by the object and returned, and can detect surrounding objects located within a predefined set distance, set vertical field of view, and set horizontal field of view range according to its specifications. The lidar sensor (510) may include a front lidar sensor (511), an upper lidar sensor (512), and a rear lidar sensor (513) installed at the front, top, and rear of the vehicle, respectively, but the installation positions and number of installations are not limited to a specific embodiment. A threshold value for determining the validity of a laser signal reflected from the object may be stored in advance in a memory (not shown) of the autonomous driving integrated control unit (600), and the autonomous driving integrated control unit (600) may determine the position (including the distance to the object), speed, and direction of movement of the object by measuring the time it takes for a laser signal transmitted through the lidar sensor (510) to be reflected from the object and return.

[0068] The radar sensor (520) can detect surrounding objects outside the vehicle by emitting electromagnetic waves around the vehicle and receiving signals that are reflected by the objects and returned, and can detect surrounding objects located within a predefined set distance, set vertical angle of view, and set horizontal angle of view range according to its specifications. The radar sensor (520) may include a front radar sensor (521), a left radar sensor (521), a right radar sensor (522), and a rear radar sensor (523) installed on the front, left side, right side, and rear of the vehicle, respectively, but the installation positions and the number of installations are not limited to a specific embodiment. The autonomous driving integrated control unit (600) can determine the location (including the distance to the object), speed, and moving direction of the object by analyzing the power of the electromagnetic waves transmitted and received through the radar sensor (520).

[0069] The camera sensor (530) can detect surrounding objects outside the vehicle by capturing images of the surroundings of the vehicle, and can detect surrounding objects located within a predefined set distance, set vertical angle of view, and set horizontal angle of view range according to its specifications.

[0070] The camera sensor (530) may include a front camera sensor (531), a left camera sensor (532), a right camera sensor (533), and a rear camera sensor (534) installed respectively on the front, left side, right side, and rear of the vehicle, but the installation positions and number of installations are not limited to a specific embodiment. The autonomous driving integrated control unit can determine the position (including the distance to the object), speed, and moving direction of the corresponding object by applying predefined image processing to the image captured by the camera sensor (530).

[0071] In addition, an internal camera sensor (535) for capturing images inside the vehicle may be mounted at a predetermined location inside the vehicle (e.g., a rearview mirror), and the autonomous driving integrated control unit (600) may monitor the behavior and status of the passenger based on the image acquired through the internal camera sensor (535) and output guidance or warnings to the passenger through the aforementioned output unit (300).

[0072] In addition to the lidar sensor (510), radar sensor (520), and camera sensor (530), the sensor unit (500) may further include an ultrasonic sensor (540) as illustrated in FIG. 1, and various types of sensors for detecting objects surrounding the vehicle may be further employed in the sensor unit (500).

[0073] FIG. 2 illustrates an example in which a front lidar sensor (511) or a front radar sensor (521) is installed at the front of the vehicle, a rear lidar sensor (513) or a rear radar sensor (524) is installed at the rear of the vehicle, and a front camera sensor (531), a left camera sensor (532), a right camera sensor (533), and a rear camera sensor (534) are installed at the front, left side, right side, and rear of the vehicle, respectively, to help understand the present embodiment. However, as described above, the installation location and number of each sensor are not limited to a specific embodiment.

[0074] Furthermore, the sensor unit (500) may further include a biosensor for detecting the biosignals of the passenger (e.g., heart rate, electrocardiogram, respiration, blood pressure, body temperature, brain waves, blood flow (pulse waves), and blood sugar, etc.) in order to determine the condition of the passenger in the vehicle. The biosensor may include a heart rate sensor, an electrocardiogram (Electrocardiogram) sensor, a respiration sensor, a blood pressure sensor, a body temperature sensor, an electroencephalogram (Electroencephalogram) sensor, a blood flow (Photoplethysmography) sensor, and a blood sugar sensor.

[0075] Lastly, the sensor unit (500) additionally adds a microphone (550), and the internal microphone (551) and external microphone (552) are each used for different purposes.

[0076] The internal microphone (551) can be used, for example, to analyze the voice of a passenger in an autonomous vehicle (1000) based on AI or the like, or to immediately respond to a direct voice command.

[0077] On the other hand, an external microphone (552) can be used to analyze various sounds generated from the outside of an autonomous vehicle (1000) using various analysis tools such as deep learning and to respond appropriately for safe driving, etc.

[0078] For reference, the symbol illustrated in FIG. 2 may perform the same or similar function as the symbol illustrated in FIG. 1, and FIG. 2 illustrates in more detail the relative positional relationship of each component (based on the inside of the autonomous vehicle (1000)) compared to FIG. 1.

[0079]

[0080] Figure 3 illustrates the architecture of an in-vehicle control system according to the present invention. The vehicle control system comprises a vehicle computer (VC) (10), a gateway controller (or central communication unit) (20), and standard controllers (30).

[0081] However, in FIGS. 3 through 21 and the related descriptions to follow, the vehicle control system is applicable to control systems for mobile devices such as robots, unmanned aerial vehicles, and autonomous vehicles. Therefore, vehicle-specific designations such as "vehicle computer" and "vehicle control system" are merely designations and do not limit the scope of the present invention. For example, the vehicle computer may be referred to as a central computer, and the vehicle control system may be referred to as a device control system.

[0082] The standard controllers (30) are configured to control components (e.g., actuators or sensors) connected to each other, and a plurality of standard controllers may be configured to cooperate to provide one function or perform control for providing the function.

[0083] In this specification, a function refers to an operation that can be implemented as a component, defined by input (control) signals and output (control) signals. Depending on the function, the input control signals and output control signals may be linked. That is, at least one input control signal and at least one corresponding output control signal can constitute a single function.

[0084] For example, when the emergency light button of a vehicle is pressed, the emergency lights at the front and rear of the vehicle turn on, and the input control signal is a signal corresponding to the pressing of the emergency light button, and the output control signal is a signal corresponding to the driving signal for turning on the emergency lights.

[0085] Additionally, each of the standard controllers (30) is installed or located in one of multiple areas of the vehicle, and the standard controllers in different areas can transmit and receive signals to each other through the gateway controller (20) or the vehicle computer (10).

[0086] More specifically, an input control signal generated from a standard controller (310) is transmitted to a vehicle computer (10) via a gateway controller (20), and the vehicle computer (10) can generate an output control signal corresponding to the input control signal and transmit the output control signal to a standard controller (320) via the gateway controller (20). The output control signal can include information for operating an individual function (or operation) of a component connected to the standard controller (320). Accordingly, the standard controller (320) can operate the corresponding component using the output control signal.

[0087] The present invention classifies input and output signals and power for controlling components in order to provide for addition or change of components or addition or change of functions related to components, and configures each classified signal group to operate according to a standardized circuit and software.

[0088] For example, the output signal can be classified into two types: high current output and low current output, and all input signals can be classified into one.

[0089] Below, examples of classification of signals, drives, interfaces, etc. according to the present invention are described, and other classifications in addition to the classifications below are also possible in the present invention.

[0090] Additionally, in this specification, "software" or "SW" corresponds to logic that performs a specific operation or function, and may refer to a function that can be performed by a controller or processor. Accordingly, in this specification, "software" or "SW" may also be referred to by other names, and the scope of the rights is not limited to the names.

[0091]

[0092] Figure 4 shows signal and drive standardization for component driving according to the present invention.

[0093] S1 represents some of the signals used in existing vehicles. In this proposal, the signals used in existing vehicles are standardized and classified, distinguishing input and output signals into high-current active high / low signals and low-current active high / low signals (S2). Furthermore, based on these input and output signals (S2), the corresponding drivers or switch detection interfaces are classified (S3).

[0094]

[0095] Figure 5 illustrates the standardization of signals and interfaces for communication and sound for components according to the present invention.

[0096] Power, sound, or wireless signals (S11) were classified into signals applicable to the first interface, signals applicable to the second interface, and signals requiring a separate MCU (micro controller unit) (S12), and these were further classified by interface IC into first interface transceiver, second interface transceiver, Ethernet, CAN transceiver, LIN transceiver, etc. (S13).

[0097]

[0098] In the present invention, the Ethernet, CAN, and LIN interfaces for in-vehicle communication are used in the same manner as before.

[0099]

[0100] Figure 6 shows the connection structure between the standard controller and components according to the present invention.

[0101] According to the classification of signals, drives and interfaces described above, the configuration of a standard controller (31) is proposed.

[0102] The standard controller (31) may include an MCU, a high current driver, a low current driver, a switch detector, an Ethernet interface, a CAN (Controller Area Network) transceiver, a LIN (Local Interconnect Network) transceiver, a first interface transceiver, and a second interface transceiver.

[0103] The MCU can receive or detect control signals, or generate or transmit control signals, to provide the functions described above. Based on the structure or information of signals, etc. related to each connector stored in the memory (hereinafter referred to as a signal database or signal DB), the MCU can set the channel register of the driver or switch detector matching each connector according to the desired control signal. In addition, the MCU can receive control signals from an actuator or sensor connected to the standard controller (31), or transmit control signals to the actuator or sensor.

[0104] Additionally, the MCU can control the power block according to the operating mode (Normal, Sleep, etc.) and control the communication block for communication with other standard controllers.

[0105] High-current drivers (ICs) are ICs capable of outputting high currents and may have multiple output channels. High-current drivers have a register area for setting detailed signal specifications for each output channel, and the registers can be configured via an SPI interface or other interface on an MCU. This allows the registers of channels matching the signals connected to the connector to be set, allowing the control of the functions provided by those signals.

[0106] Low-current drivers (ICs) are ICs capable of outputting low currents and can be equipped with multiple output channels. Low-power drivers typically have a register area for setting detailed signal specifications for each output channel. These registers can be configured via an SPI interface or other interface on an MCU. This allows the registers of channels matching the signals connected to the connector to be set, allowing the control of the functions provided by those signals.

[0107] A switch detector is an IC capable of detecting changes in an input signal and may have multiple input channels. Each switch detector has a register area where detailed signal specifications can be configured for each input channel. This register can be configured via an SPI interface or other interface on an MCU. This allows the register of a channel matching a signal connected to a connector to be set, allowing the control of the function provided by that signal.

[0108] The Ethernet interface is a communication interface that supports the Ethernet protocol, the CAN transceiver is a communication interface that supports CAN communication, the LIN transceiver is a communication interface that supports LIN communication, the transceiver for the first interface is a communication interface that supports the first interface communication, and the transceiver for the second interface is a communication interface that supports the second interface communication.

[0109] The standard controller (31) can be connected to actuators (41, 43, 45, 47), sensors (42, 44, 46), a central gateway (48), and an RF antenna (49).

[0110]

[0111] Figure 7 shows a connection structure between a standard controller, a gateway controller, and a vehicle computer according to the present invention.

[0112] The present invention proposes a three-layer architecture comprising a plurality of standard controllers, a gateway controller (or central communication unit), and a vehicle computer (VC).

[0113] Multiple standard controllers form Layer 1, gateway controllers form Layer 2, and vehicle computers form Layer 3.

[0114] Each layer can be connected with an Ethernet interface, and standard controllers can be connected to each other with a CAN or Ethernet interface.

[0115] As illustrated in Fig. 7, a standard controller is connected to a component, and the present invention proposes a vehicle control system with a 3-layer structure to provide functions linked to the component, and proposes a signal structure and signal processing logic accordingly.

[0116] The signal DB proposed according to the present invention may include the following parameters.

[0117] Classification Parameter Description Overall Signal ID (SIG_ID)Signal ID. Parameter indicating the identifier assigned to each signal. Overall Signal Classification 1 (CAT_1)Signal major classification parameter. Contains information such as which type of IC should be assigned. Indicates either input IC, low current output / drive IC, or high current output / drive IC. Overall Signal Classification 2 (CAT_2)Signal minor classification parameter. Contains specification information such as Active High / Low or analog signal. Overall Standard Controller Information (SC)Indicates which standard controller the signal is assigned to. Overall IC Classification Parameter defining which IC the signal is connected to. Indicates the IC number or identifier. Overall Pin Classification Parameter defining which PIN the signal is connected to. Indicates the PIN number.Number of output pins (USED) Parameter that defines how many pins the signal uses Output Maximum operating current (MOC) Parameter that is used when the maximum operating current is required for the power signal Output Overcurrent protection (OCP) Parameter that defines whether the signal requires the Over Current Protection function and at what output current the OCP function will operate All Real-time necessity (RT) Parameter that defines whether the signal needs to be transmitted and received in real time All PWM Parameter that defines whether the signal requires PWM output Output OLD Parameter that defines whether the signal requires the Open Load Detection function Output PWM_F Parameter that defines the PWM frequency of the signal Output CT (Charging time) In the case of the power signal, inrush current may occur when the minimum is applied, and if a charging operation that can reduce the inrush current is required, the parameter that indicates how long the charging operation will be performed Output SR Parameter that defines the output slew rate of the signal Output DEF_V Parameter that defines the default value of the signal All PRE_Value Parameter for reserve Input WC Parameter that defines the wetting current of the signal Input Threshold_V Threshold that detects a change in the status of the input signal Parameter that defines the voltage value outputPWM_DutyParameter that defines the default duty of the PWM output signal.

[0118] In the above table, “Classification” indicates whether the parameter is used in an input signal, an output signal, or both input / output signals. Although not shown in Table 1, each parameter can be set to have a value of a predetermined length, and such a signal DB can be stored in the memory of each standard controller. Preferably, the standard controller can store a signal DB related to components connected to it (e.g., sensors, actuators, etc.) in its memory. Accordingly, the signal DB can include multiple signals (see Table 2 described below as an example), and the values ​​of individual parameters can be set for each signal. The signal DB can be modified, added, deleted, etc. according to the functional updates to be provided.

[0119] Furthermore, referring to Table 1, each parameter in the signal DB does not describe any function related to the component. In other words, each signal in the signal DB merely represents a physical signal, which is used to set registers for high-current / low-current drivers for the component, or to detect status values ​​for switch detectors, etc. Accordingly, there is no limitation or indication as to what function the signal in the signal DB provides using the component. Accordingly, from the standpoint of the standard controller, it is impossible to recognize the function using the component, and only processes the input control signal or output control signal for it.

[0120] In contrast, the vehicle computer (VC) can define and store functions utilizing components through the linkage of multiple signals by the function SW described below. The data in which such functions are defined is referred to as a function database. However, the connection SW of the VC can recognize or interpret individual functions from the signal ID received from the standard controller, but does not know the individual functions connected thereto. The connection SW can transmit the fact that a signal for the individual function has been received to the function SW related to or supporting the individual function according to the received signal ID, and can receive the linked individual function in response thereto. The function SW can respond to the connection SW with the individual function corresponding to the output corresponding to the individual function acting as an input. The connection SW can obtain the signal ID and / or its status value for the linked individual function, and transmit the obtained signal ID and / or status value to all standard controllers.

[0121]

[0122] Figure 8 shows a detailed configuration of a standard controller according to the present invention, a connection structure between the standard controller and components, and a connection structure between the standard controller, a gateway controller, and a vehicle computer.

[0123] FIG. 8 adds a configuration not shown in FIG. 6 and omits a configuration shown in FIG. 6, but the present invention is not limited thereto.

[0124] The standard controller (31) includes an MCU (310), which includes an IC register mapping and drive control unit (3111) and an autosar (AUTomotive Open System ARchitecture) standard platform (3112).

[0125] In addition, the standard controller (31) may include a high current driver (IC) (3211), a low current driver (IC) (3311), a switch detector (3411), and a memory (3511). In addition, the standard controller (31) may include a connector (3611) for a high current output signal connected to the high current driver, a connector (3711) for a low current output signal connected to the low current driver, and a connector (3811) for an input signal connected to the switch detector for inputting or receiving signals from vehicle components, etc. In particular, the memory (3511) may store a signal DB related to a component (e.g., an actuator (40)) connected thereto as described above.

[0126] Additionally, the standard controller (31) can be connected to the actuator (41) via a connector (3611, 3711, 3811).

[0127] Hereinafter, the generation or setting of input or output control signals for a new actuator (41) and the processing or control of signals for functions related to the actuator (41) will be briefly described.

[0128] An input or output control signal for the actuator (41) may be generated according to the prescribed specifications of the signal DB and stored in the memory (3511). In addition, a function related to the actuator (41) may be defined based on the input or output control signal for the actuator (41), and such information (i.e., a function database) may be stored in a storage medium such as the function SW (11) of the VC (10) or the memory of the function SW.

[0129] VC (10) is a controller in which such function SW (11) is stored or located, and supports adding, changing, or deleting functions desired by the user. VC (10) drives the function SW based on the input control signal and / or the status value of a component (such as a sensor / actuator) received from the standard controller (31). In addition, VC (10) can transmit an output control signal acquired through the function SW to the standard controller. At this time, the input control signal or the output control signal may include a signal ID and / or its status value (or a change in the status value). The signal ID must be in the signal DB stored in the memory of the standard controller related to the corresponding function or component.

[0130] The combined information of input or output control signals of components (e.g., actuators or sensors) associated with these functions is referred to herein as "linkage" information. Furthermore, the linkage information may include a description of the corresponding function associated with the component. Examples of linkage information include the following:

[0131] Linked Information 1: Warning light flashing function when horn switch is pressed

[0132] SIG_IDCAT_1CAT_2SCICPINUSEDOCPRTWCThreshold_V0000 0000 0011 0011InputActive LowDriver114--O2mA2V0000 0000 0111 0001OutputActive HighTrunk1133AO--

[0133] In Table 2, SIG_ID=0000 0000 0011 0011 is an input control signal indicating the pressing of the horn switch, and SIG_ID=0000 0000 0111 0001 is an output control signal that activates the flashing of the trunk side warning light. That is, each of the input control signal and the output control signal can correspond to or represent an individual function. Meanwhile, referring to the above-mentioned linkage information, it can be seen that the function of flashing the trunk side warning light when the horn switch is pressed is defined, and this function is provided through an actuator connected to a specific IC and pin. That is, when an input control signal is generated or detected from a certain component (e.g., an input control signal according to the sensing information of a sensor or the occurrence of a button touch / press, etc.), an output control signal for (another) component according to the input control signal is generated, and a series of linkage information can be set so that the component is controlled accordingly.

[0134] The standard controller (31) can be connected to an actuator (41) according to a signal DB stored in the memory (3511). That is, it can be connected to a high-current / low-current driver, or a switch detector and its connector, according to the IC and pin information indicated by each signal of the signal DB. When the standard controller (31) is rebooted, the IC register mapping and drive control unit (3111) can set a register for the corresponding driver (and / or its pin) based on the signal DB. For example, assuming that SIG_ID=0000 0000 0011 0011 in Table 2 is an output control signal for the actuator (41), the IC register mapping and driving control unit (3111) enables pin 14 of driver (IC) 1, selects CSO (current source) because it is Active Low, and performs an operation of setting the wetting current and Threshold_V to 2 mA and 2 V, respectively.

[0135] When a detection corresponding to an input control signal from an actuator (41) is made (via a switch detector), the standard controller (31) can transmit a signal ID corresponding to the input control signal and its status value (e.g., “Low” or “Active”) or a change in the status value (e.g., a change from “High” to “Low” or a change from “Inactive” to “Active”) to the VC (10) side via the gateway controller (20).

[0136] After that, the connection SW (11) of the VC (10) can identify which individual function the signal is based on the signal ID of the received input control signal (e.g., pressing the horn switch), and notify the related function SW (12) that the individual function has been triggered. At this time, if there are multiple function SWs that support the individual functions related to the input control signal, a notification about the triggering of the individual function can be transmitted to the multiple function SWs. For this, the connection SW (11) must know information about the individual functions supported by each function SW (12). The connection SW (11) may store information about the function SW (12) and the individual functions supported by the function SW in a memory, etc.

[0137] Upon trigger notification for the identified individual function, the function SW (12) can respond back to the connection SW (11) with an individual function (e.g., activation of a warning light flashing) that responds to the identified function. The connection SW (11) can generate a signal ID and its status value (e.g., “Active”) corresponding to an output control signal for the individual function that responds to the identified function, and transmit this to the standard controllers via the gateway controller (20).

[0138] Meanwhile, in the above description, it is explained that VC (10) is implemented by dividing into connection SW (11) and function SW (12), but connection SW (11) and function SW (12) may be integrated into one entity.

[0139] When an output control signal is received, the standard controllers can determine whether the output control signal is related to a component connected to them by using the signal ID of the signal DB stored in the memory. The standard controllers can determine whether the signal is related to a component connected to them by using the signal ID of the received output control signal. That is, the standard controllers can find a signal ID identical to the signal ID of the received output control signal in the signal DB stored in the memory and determine whether the signal is connected to them by referring to the standard controller information (“SC”) parameter of the signal ID.

[0140] If the output control signal is related to a component connected to itself (e.g., a warning light), the standard controller can set the signal indicated by the signal ID of the output control signal to the indicated state value. The standard controller searches for the signal ID identical to the signal ID of the received output control signal in the signal DB stored in the memory, refers to the “CAT_2” parameter of the signal ID, determines whether the indicated state value (Active) is High or Low, and sets the signal to Active (High or Low) accordingly.

[0141] Depending on the state value settings, the operation of the actuator connected to the IC or pin indicated by the output control signal can be performed. Then, the standard controller can transmit or report to the VC (10) side that the state value change according to the output control signal has been completed.

[0142] Figure 9 shows a connection structure between a signal DB and a standard controller and components according to the present invention.

[0143] The following signal DB can be added or generated for actuators connected to the standard controller (31).

[0144] SIG_IDCAT_1CAT_2SCICPINUSEDOCPRTWCThreshold_V0000 0000 1011 0011OutputActive High11213AO--0000 0000 1011 0011OutputActive High12413AO--

[0145] It is assumed that the standard controller (31) of Fig. 9 is standard controller 1 (SC=1). A signal DB such as the above can be stored in the memory (3511) of the standard controller (31), and correspondingly, a driver and an actuator can be connected to its pins. When the standard controller (31) is rebooted, register settings for each driver (IC, 3211, 3212) can be performed according to the signal DB.

[0146]

[0147] Referring to FIG. 9, it is shown that an actuator (41) is connected to pin 2 of high current driver #1, and also that an actuator (41) is connected to pin 4 of high current driver #2.

[0148]

[0149] Figure 10 is a diagram for explaining a change or double connection of the connection between a standard controller and components according to the present invention.

[0150] The following describes a case where the actuator (41) is disconnected from the standard controller 1 (31) and changed to be connected to the standard controller 2 (32) according to a change in the signal DB.

[0151] Table 4 shows the signal DB before the change, and Table 5 shows the signal DB after the change.

[0152] SIG_IDCAT_1CAT_2SCICPINUSEDOCPRTWCThreshold_V0000 0000 1011 0011OutputActive High11213AO--

[0153] SIG_IDCAT_1CAT_2SCICPINUSEDOCPRTWCThreshold_V0000 0000 1011 0011OutputActive High22413AO--

[0154] According to the change of this signal DB, the connection of the actuator (41) with the standard controller may be changed, as illustrated in FIG. 10. That is, referring to Table 5, it can be confirmed that the actuator (41) is connected to the 4th pin of the 2nd driver (IC) of the standard controller 2 (32) (SC=2). This movement of the actuator between standard controllers can be referred to as signal movement, and since only the SC, IC, and pin information are changed and the remaining values ​​are maintained as is, it can be utilized for changing the position of the actuator in the vehicle, etc.

[0155] Meanwhile, referring to FIG. 10, it is also possible to consider a case where the actuator (41) establishes a connection with the standard controller 2 (32) while maintaining the connection with the standard controller 1 (31).

[0156] This is for functional safety purposes, and by connecting one actuator (41) to two standard controllers (31, 32) simultaneously and configuring the signal DB identically (SIG_ID is the same), there is an advantage in that even if a problem occurs in one connection, the corresponding function can be supported through the remaining connection. Accordingly, the following signal DB configuration is possible.

[0157] SIG_IDCAT_1CAT_2SCICPINUSEDOCPRTWCThreshold_V0000 0000 1011 0011OutputActive High11213AO--0000 0000 1011 0011OutputActive High22413AO--

[0158]

[0159] Figure 11 illustrates a connection structure between a standard controller and a vehicle computer for adding new functions using components according to the present invention.

[0160] Fig. 11 shows a case where a new function SW (13) is added to VC (10). The new function SW (13) stores a function associated with the actuator (41) and includes linkage information for an input control signal and a corresponding output control signal.

[0161] VC (10) can receive a signal ID and a state value (or a change in the state value) corresponding to any input control signal from any standard controller. The received signal ID and state value (or a change in the state value) can correspond to a function stored in a new function SW (13) or linkage information between an input control signal and an output control signal. Of course, the received signal ID and state value (or a change in the state value) can also correspond to a function stored in an existing function SW (12) or linkage information between an input control signal and an output control signal.

[0162] Accordingly, VC (10) can generate an output control signal corresponding to an input control signal according to the existing function SW (12) or the new function SW (13) or the link information stored therein.

[0163] For example, consider a case where a function for linking an actuator (41) and a sensor (not shown) is added. In a situation where the function for linking the actuator (41) and the sensor is not present in the function SW (12), the function for linking the actuator (41) and the sensor can be added in the additional function SW (13). It is assumed that signals related to the operation of the actuator (41) are predefined or stored in the signal database of the standard controller, and input signals related to the sensor are also predefined or stored in the signal database of the standard controller. In this case, since signals for the actuator (41) and the sensor are defined in the signal database, no additional update of the signal database is necessary.

[0164] Such embodiments may enable users to add functions not provided by the manufacturer by adding additional functional SW.

[0165] In this way, new functions related to the part can be added or set by adding or changing the function SW of VC(10).

[0166]

[0167] Additionally, signals can be sequentially controlled without functional SW via trigger parameters in the signal database. This can replace existing fuses or relays and can be useful even during vehicle development.

[0168] SIG_IDCAT_1CAT_2SCICPINUSEDOCPOutput TriggerTrigger IDTrigger Delay0000 0000 1011 00XXOutputActive High11213ATrigger Available0000 0000 1011 XX00(ACC)20ms

[0169] As shown in Table 7, if the trigger signal ID (0000 0000 1011 XX00) means an ACC signal, the signal can be set to change to the Active state 20 ms later when ACC changes to the Active state. By using this function, functions that were operated without SW, such as fuses or relays in existing vehicles, can be replaced without SW. Fig. 12 is a diagram for explaining the implementation of a function using a standard controller according to the present invention.

[0170] Figure 12 shows an example in which four standard controllers (31, 32, 33, 34) are placed in each area within the vehicle.

[0171] A signal database for controlling components is configured in advance and can be shared among all standard controllers. However, each standard controller can identify or recognize the signal database for the components connected to it.

[0172]

[0173] [Wiper activation function according to wiper switch]

[0174] This describes a case where the wiper activation function according to the operation of the wiper switch (46) is defined in the function SW.

[0175] The standard controller #1 (31) can detect an ON signal from the wiper switch (46). After booting, the standard controller #1 (31) completes register settings for input determination of the wiper switch ON signal to the switch detector, and can then determine the status value of the signal. Accordingly, the standard controller #1 (31) can transmit the signal ID and status value (or status value change) to all standard controllers (32, 33, 34) as well as the VC (10).

[0176] The VC (10) can identify which individual function (i.e., wiper switch operation) the received signal ID (and / or status value) indicates. Then, the VC (10) can recognize another individual function (e.g., activation of the output of the motor of the wiper (45)) linked to the individual function. According to the above assumption, the function SW may store that the wiper activation function is linked to the operation of the wiper switch (46). In an additional example, the function SW may also store mapping information of related signal IDs corresponding to the functions (i.e., mapping between the ID of the input control signal and the ID of the output control signal).

[0177] Accordingly, VC (10) can generate a signal ID and its status value (e.g., Active) corresponding to another linked individual function and transmit them back to the standard controllers.

[0178] If the standard controllers have information corresponding to the received signal ID in their signal database, they can configure the registers of the relevant ICs to output the status value of the corresponding signal ID as the received value. If the standard controllers do not have information corresponding to the received signal ID in their signal database, they can ignore the received signal ID (and / or status value).

[0179] In the illustrated example, since the standard controller #4 (34) is connected to the wiper or wiper motor (46), if the corresponding signal is stored in the signal DB of the memory of the standard controller #4 (34), the standard controller #4 (34) can perform register settings of the related IC.

[0180]

[0181] [Warning light output function according to wiper switch]

[0182] Additionally, a case is described where a warning light flashing function according to the operation of the wiper switch (46) is added to the function SW.

[0183] The signal ID and status value transmission according to the wiper switch ON up to VC(10) refer to the example described above.

[0184] The VC (10) can identify which individual function (i.e., wiper switch operation) the received signal ID (and / or status value) indicates. Then, the VC (10) can recognize another individual function (e.g., warning light output) associated with that individual function.

[0185] Accordingly, VC (10) can generate a signal ID and its status value (e.g., Active) corresponding to another linked individual function and transmit them back to the standard controllers.

[0186] Standard controllers can set the registers of the IC corresponding to the received signal ID to output the status value of the signal ID as the received value if there is a signal corresponding to the received signal ID in their signal DB. If there is no information corresponding to the received signal ID in their signal DB, the standard controller can ignore the received signal ID (and / or status value).

[0187] In the illustrated example, since the standard controller #3 and the standard controller #4 (33, 34) are connected to the warning lights (41, 42, 43, 44), if the corresponding signal is stored in the signal DB of the memory of the standard controller #3 or the standard controller #4 (33, 34), the standard controller #3 or the standard controller #4 can perform register settings of the related IC.

[0188]

[0189] Meanwhile, in the example described with reference to FIG. 12, the VC (10) identifies the linked individual function based on the received signal ID and / or status value, and generates and transmits the signal ID and its status value for the linked individual function. However, additional conditions may be accompanied for this. That is, the VC (10) can determine the preconditions under which the linked individual function can be executed. For example, when the linked individual function is a warning light output function, the VC (10) can check in advance whether the warning light is controllable from the standard controller connected to the warning light. The state that satisfies this precondition is referred to as a “control ready state.” When the VC (10) is in the control ready state, it can transmit the corresponding signal ID and its status value to the standard controllers.

[0190]

[0191] Figure 13 is a diagram for explaining the implementation of a function using a standard controller according to the present invention.

[0192] Figure 13 illustrates a case where a warning light (47) and standard controller #5 (35) are added after vehicle development is completed. After vehicle development is completed, actuators, sensors, or standard controllers may be added.

[0193] As shown, the warning light (47) can be added, and the standard controller #5 (35) can be added, and the warning light (42) connected to the standard controller #4 (34) in the past (Fig. 12) can be connected to the standard controller #5 (35). In this case, as described above, the function can be flexibly provided in response to the addition of changed parts and connection changes, etc., through updates (addition, change, deletion, etc.) of the function SW of the VC (10), updates of the signal DB of the related standard controller, etc.

[0194] The signal associated with the warning light (42) must be changed so that the “SC”, “IC”, and “PIN” parameters among the DB parameters are assigned to the standard controller #5 (35), and the signal DB associated with the warning light (47) can be added or the signal of the existing warning light (42) can be used in common. In addition, when the signal DB associated with the warning light (47) is added, the function related to the output of the warning light (47) can be added or updated in the function SW of the VC (10). When the output signal of the warning light (42) is used in common by the warning light (47), the addition of the warning light (47) is possible only by changing the output signal parameters (SC, IC, PIN) of the warning light (42) in the signal DB without changing the function SW of the VC (10). Meanwhile, the standard controller #4 (34) can determine that the signal is not assigned to itself because the “SC” parameter of the signal associated with the warning light (42), which was previously assigned to itself in the signal DB, has been changed to the standard controller #5 (35). The function related to the output of the warning light (42) may be maintained in the function SW of VC (10) depending on the setting, or may be changed depending on the setting.

[0195]

[0196] Meanwhile, a method to reduce inrush is needed when outputting an output control signal.

[0197] 1. When power is supplied, it can be driven to output in PWM mode in the section where the voltage rises to reduce inrush.

[0198] 2. Define the PWM frequency, duty, and PWM output time as signal DB parameters according to the characteristics of the component being powered (input capacitor capacity, etc.).

[0199] 3. Activate the power signal as defined in the signal DB parameter.

[0200]

[0201] Additionally, a method is needed to reduce noise generated by instantaneous current changes when all power supplied from the standard controller is turned on simultaneously.

[0202] Accordingly, by sequentially turning ON each pin of the high-current driver (IC) of the standard controller, noise generation can be suppressed.

[0203]

[0204] Figure 14 illustrates a connection structure between a standard controller, a gateway controller, and a vehicle computer according to the present invention.

[0205]

[0206] Conventional zonal architecture technology divides a vehicle into several zones (i.e., areas), determines the number of signals within each zone and their specifications, and then develops the hardware for the zone controller accordingly, followed by software development. This process is time-consuming. Furthermore, if additional signals are added or signal specifications are changed during development, the hardware must be modified, frequently resulting in delays in the development schedule.

[0207] Furthermore, changing the designated area divisions can be difficult. For example, if the circuit design is initially divided into four areas and 50 signals are assigned to each area, but the number of areas needs to be reduced to three after the circuit design is complete, the previously manufactured four-area controller cannot be reused, and all three area controllers must be newly manufactured.

[0208] The present invention standardizes all vehicle signals connected to a standard controller and integrates the hardware and software for standardized vehicle signal processing, thereby enabling the use of the same standard controller regardless of vehicle type, number of areas, number of signals, or signal specifications. Once developed, the standard controller can be applied to other vehicles without hardware or software modifications. This eliminates the need for separate reliability assessments for individual components and allows for a comprehensive vehicle system evaluation, thereby shortening development schedules.

[0209] The vehicle control system according to the present invention has a three-layer structure, with a standard controller positioned at the lowest level. As previously described, the standard controller consists of identical hardware and software. To achieve this, information regarding the function of input / output signals connected to the standard controller is removed from the standard controller. In other words, the standard controller is unaware of "functions." Since information regarding functions varies for each signal, if the function information is present in or connected to the standard controller, hardware and software cannot be integrated.

[0210] The input control signal of the standard controller is transmitted to the vehicle computer, which is the top layer, through the central communication unit (or gateway controller, CCU), which is the middle layer.

[0211] When the vehicle computer receives an input control signal from the standard controller, it can recognize or provide functional information for each input control signal.

[0212] The input control signal with the function information is processed by the vehicle computer, and the result (i.e., the output control signal corresponding to the input control signal) is transmitted back to the relevant standard controller via the central communication unit. At this time, the output control signal before being output from the vehicle computer is transmitted in a form with the function information removed, just as when the input control signal was received.

[0213] The central communication unit transmits the output control signal received from the vehicle computer to all standard controllers, and the standard controllers output the output control signal. Standard controllers that are not related to the received output control signal only store the output status value of the output control signal and do not perform any other actions.

[0214] The 3-layer structure proposed in the present invention is a functional classification, and is not intended to be implemented by classifying the controller into three types based on physical criteria.

[0215] A controller can be manufactured that integrates the vehicle computer, which is the top layer, and the central communication unit, which is the middle layer, if necessary, but has a separate structure in terms of functionality.

[0216] This technology has a structure that connects in-vehicle controllers and components (sensors / actuators, etc.) according to area rather than function.

[0217] A vehicle can be divided into several zones, each with a single standard controller. Input / output control signals from all components (sensors, actuators, etc.) within a given zone are transmitted to the standard controller configured within that zone, regardless of function.

[0218] Each standard controller (31, 32, 33, 34) shares input / output control signals and / or their status values ​​(or status value changes) related to components connected to it with the central communication unit (20), and additionally, the standard controllers can share the information among themselves. The central communication unit (20) can share the input / output control signals and / or their status values ​​(or status value changes) of each standard controller with the vehicle computer (10). As illustrated in FIG. 14, the standard controllers can be configured to communicate with each other via a CAN or Ethernet interface, the standard controllers and the central communication unit can communicate with each other via an Ethernet interface, and the central communication unit and the vehicle computer can communicate with each other via an Ethernet interface.

[0219] Conversely, the vehicle computer drives the functional SW and transmits the result to the central communication unit, which then forwards it to the standard controller. The standard controller processes or controls the output control signal based on the received result, but as previously explained, the standard controller cannot know which function the output control signal is for. This connection structure allows for reduction in the length / weight of the wiring harness within the vehicle, and by separating the input / output control signals transmitted between the standard controller and the vehicle computer from the function SW of the vehicle computer, it allows for flexible response to updates (additions, changes, or removals) of parts or functions.

[0220]

[0221] Figure 15 is a diagram for explaining a function utilizing a component according to the present invention.

[0222] Specifically, the function is to change the audio mode from FM radio to USB music mode via the rear seat console switch (401).

[0223] In the signal DB stored in the memory of the standard controller #1 (31), a signal for detecting that the rear seat console switch (401) is pushed is defined. However, even if the standard controller #1 (31) detects a signal corresponding to the push of the rear seat console switch (401), it cannot know that the signal indicates the push of the rear seat console switch (401).

[0224] For example, the standard controller #1 (31) can detect an electrical signal (e.g., voltage level) detected from a switch detector (IC) connected to a rear seat console switch (401) and its pin. If an electrical signal above or below a threshold value is detected from the corresponding driver and pin defined in the signal DB, the standard controller #1 (31) can transmit the corresponding signal ID and its status value (in the case of “Low” or “Active Low”) to the vehicle computer (10) via the central communication unit (20), and additionally directly to the standard controller #2 (32).

[0225] In addition, a signal for controlling the power OFF of the radio antenna is defined in the signal DB stored in the memory of the standard controller #2 (32). However, even if the standard controller #2 (32) detects a signal for controlling the power OFF of the radio antenna, it cannot know that the signal is a signal for controlling the power OFF of the radio antenna.

[0226] The vehicle computer (10) must process the signal ID and its status value received from the standard controller #1 (31).

[0227] Before that, the connection SW (11) of the vehicle computer (10) will be described. The connection SW (11) holds the signal ID information of the input control signal received from the standard controller, information about which individual function each signal ID is for, and what meaning the status value of the signal has in the individual function. Therefore, the connection SW (11) can convert the signal ID and status value received from the standard controller into a function and meaning and transmit this information to the function SW that requires it. However, the connection SW (11) cannot know about the signal ID received from the standard controller and the output control signal corresponding to the status value (i.e., the input control signal). The linkage information between the input control signal and the output control signal is owned or managed by the function SW (12, 13).

[0228] The connection SW (11) identifies the functional meaning according to the signal ID and status value received from the standard controller through the central communication unit and transmits it to the function SW providing the corresponding function, so that the function SW can provide the function. That is, the connection SW (11) may at least know the function SW related to the received signal ID and its status value. The connection SW (11) may transmit the individual function and / or its meaning corresponding to the received signal ID and its status value only to the related function SW, and receive a response thereto. Alternatively, each function SW (12, 13) may register the required signal in advance in the connection SW (11), and when the status value of the corresponding signal changes, the connection SW (11) may transmit it to the function SW (12, 13).

[0229] In addition, the connection SW (11) can receive a response (i.e., an individual function) from the function SW, convert the received response into a signal ID and its status value for the individual function, and transmit it to the standard controllers (31, 32) via the central communication unit (20).

[0230] The connection SW (11) of the VC (10) recognizes individual functions from an input control signal including a received signal ID and its status value, and can confirm audio mode change information accordingly. The connection SW (11) can transmit to the function SW (12, 13) that the audio mode change information has been received.

[0231] The function SW (12, 13) can prepare an operation for the USB music mode according to the audio mode change information. In addition, the function SW (12, 13) can check whether the control preparation state for executing the USB music mode is complete. That is, the function SW (12, 13) can check the connection signal status of the USB multi-terminal (402) connected to the standard controller #2 (32). The connection signal status of the USB multi-terminal (402) can be provided from the standard controller #2 (32), and this can be transmitted as a signal in the form of a signal ID and its status value. In addition, the connection signal status can also be recognized by the connection SW (11) as an individual function and / or meaning, and the result can be transmitted to the function SW (12, 13).

[0232] Function SW (12, 13) can execute USB music mode and switch the sound source to USB after confirming that USB is connected. Function SW (12, 13) can terminate the FM radio function and output a radio antenna power OFF command.

[0233] The connection SW (11) can obtain a signal ID of a signal corresponding to the radio antenna power OFF, obtain a status value (or a status value change, e.g., “Inactive”) for the radio antenna power OFF, and transmit an output control signal including the signal ID and the status value (or the status value change) to the standard controller. The output control signal can be transmitted to all standard controllers #1, #2 (31, 32) via the central communication unit (20).

[0234] Each standard controller checks whether the received signal ID is a signal ID related to the component connected to it based on the signal DB stored in the memory.

[0235] Standard Controller #1 (31) ignores the received output control signal as it does not have a signal ID associated with the component to which it is connected.

[0236] Since the standard controller #2 (32) is a signal ID related to a component connected to itself, it can change the status value of the corresponding signal to “Low” (e.g., in the case of “Active High”) according to the received output control signal. In addition, the standard controller #2 (32) can share the changed status value with all standard controllers. In addition, the standard controller #2 (32) can also share the changed status value with the vehicle computer (10) or function SW (12, 13) via the central communication unit (20).

[0237]

[0238] Figure 16 illustrates a software architecture for a vehicle control system according to the present invention. The vehicle control system according to the present invention has a three-layer architecture, with a vehicle computer (10) positioned at the top, a central communication unit (20) positioned in the middle layer, and a standard controller (30) positioned at the bottom layer.

[0239]

[0240] Figure 17 is a diagram for explaining problems when adding parts according to a conventional controller.

[0241] Let us explain using the vehicle body controller (300) as an example.

[0242] The left side shows a state in which a horn sensor (4020) and a corresponding external buzzer (4010) are connected to the body controller (300).

[0243] When pressure is applied to the horn sensor (4020) by a user, etc., the actuator B (3312) to which the horn sensor (4020) is connected transmits a pressure (pressing) signal to the MCU (3100), and in response, the MCU (3100) can output a buzzer sounding signal to the actuator A (3311) to which the external buzzer (4010) is connected.

[0244] Accordingly, control linkage between the horn sensor (4020) and the external buzzer (4010) is established and performed.

[0245] On the other hand, the right side shows a situation in which the external buzzer (4010) as well as the warning light (4030) are to be turned on according to the pressure on the horn sensor.

[0246] A driver C (3313) for the warning light (4030) must be added, and new software and logic must be added to link the warning light (4030) with the horn sensor (4020).

[0247] This is a limitation of the arrangement of parts in a static vehicle or moving object, as mentioned above, and the present invention seeks to solve this by proposing a standard controller.

[0248]

[0249] Figure 18 is a diagram for explaining the addition of components according to the standard controller according to the present invention.

[0250] A warning light (4030) is added, and the warning light (4030) is connected to the driver (GPO) (3211) responsible for output. The external buzzer (4010) is also connected to the driver (3211). The horn sensor (4020) is for detecting an input control signal for the corresponding control, and can be connected to the driver (GPI) (3212) responsible for input. The driver (3212) can correspond to the switch detector described above.

[0251] When pressure is applied to the horn sensor (4020) by a user, etc., the actuator (3212) to which the horn sensor (4020) is connected transmits a pressure (pressing) signal to the MCU (310), and in response, the MCU (310) can output a buzzer sounding signal and a warning light lighting signal to the actuator (3211) to which the external buzzer (4010) and warning light (4030) are connected.

[0252] Accordingly, the external buzzer (4010) may sound a buzzer sound and the warning light (4030) may light up.

[0253] According to the present invention, hardware-wise, components simply need to be connected to a suitable driver, and software-wise, a corresponding signal can be added to the previously described signal database to implement the corresponding function. In other words, there is no need to add a driver to the hardware, nor is there any need for new software development.

[0254]

[0255] Figure 19 is a diagram for explaining problems when adding parts according to a conventional controller.

[0256] Figure 19 illustrates a controller (300) for controlling the rear curtain and wiper, and the connection relationship between the controller and the rear curtain motor, wiper motor, etc.

[0257] Traditionally, circuits and software had to be optimized for components like motors and sensors. Consequently, any changes or additions to components could require reconfiguration of the circuit configuration, software, or logic. This resulted in increased development costs and time.

[0258] That is, a review of an additional driver (3313) for an additional motor (4060) was required, and development of circuit configuration, software, and logic to link it with the drivers of other components was required.

[0259]

[0260] Figure 20 is a diagram for explaining the addition of components according to a standard controller according to the present invention.

[0261] Even if an additional motor (4060) is additionally connected to the standard controller (32) of the present invention, it is possible to link the relevant component with other components and provide functions using them only by updating or adding a signal DB, without adding a circuit or developing software or logic.

[0262]

[0263] Figure 21 shows a block diagram of a standard controller according to the present invention.

[0264] The standard controller (1) can be installed in one of the multiple areas of the device.

[0265] The standard controller (1) may include a transceiver (710) configured to transmit and receive signals with a gateway controller or a central computer; and a controller (or processor) (610) configured to process the transmitted and received signals.

[0266] Additionally, the standard controller (1) may include a memory (320) that stores a signal database.

[0267] The controller (610) may be configured to detect an input for a function related to a component connected thereto, and generate and transmit an input control signal corresponding to the detected input. The generated input control signal may be transmitted to a gateway controller or other standard controller(s) of the device.

[0268] The controller (610) may be configured to detect an output control signal corresponding to an output for a function related to a component connected thereto, and perform control corresponding to the output control signal.

[0269] The output control signal may be generated by the central computer according to an input for a function related to a component connected to another standard controller of a device communicatively connected to the gateway controller, i.e., a third standard controller, and may be received by the standard controller (1) via the gateway controller. Alternatively, the output control signal may be generated by the central computer according to an input for a function related to another component connected to the standard controller (1) and may be received by the standard controller (1) via the gateway controller.

[0270]

[0271] For the contents related to the device (1) not described with reference to Fig. 21, reference may be made to the descriptions related to Figs. 3 to 20, and the contents thereof may be applied to the device (1) of Fig. 21.

[0272]

[0273] Meanwhile, as another embodiment of the present invention, a vehicle (1000) including the above-described device (1) is proposed.

[0274]

[0275] In the above specification, it is described that the “device” or “system” or each component included therein performs control, but the “device”, “system” and the components included therein are only names and the scope of rights is not dependent on them.

[0276] That is, the proposed technology may be performed by other names than a device or processor or controller, and in addition, the method or method described above may be performed by a code readable by software or a computer or other machine, device, etc. for vehicle control or function provision.

[0277] In addition, as another aspect of the present invention, the operation of the proposed technology described above may be implemented, performed, or executed by a "computer" (a comprehensive concept including a system on chip (SoC) or a (micro) processor, etc.), or may be provided as a computer-readable storage medium storing or including the code, or a computer program product. The scope of the present invention may be extended to the code, or a computer-readable storage medium storing or including the code, or a computer program product.

[0278] The detailed description of the preferred embodiments of the present invention disclosed above has been provided to enable a person skilled in the art to implement and practice the present invention.

[0279] Although the present invention has been described above with reference to preferred embodiments thereof, it will be understood by those skilled in the art that the present invention may be variously modified and altered within the scope of the following claims.

[0280] Accordingly, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. As a control system for a device having mobility, At least one standard controller installed in any one of the plurality of areas of the device and configured to detect an input for a function related to a component connected thereto and generate and transmit an input control signal corresponding to the detected input, or to detect an output control signal corresponding to an output for a function related to the component connected thereto and perform a control corresponding to the output control signal, The above standard controllers: A processor including a register mapping and drive control unit configured to perform settings for registers of a high current driver, a low current driver, or a switch detector according to a set signal database, Control system.

2. In paragraph 1, the standard controller: A high current driver configured to output a high current driving signal to a connected component, a low current driver configured to output a low current driving signal to a connected component; and a switch detector configured to detect a change in an input signal. Control system.

3. In the first paragraph, the standard controller determines whether the received signal is a signal related to itself based on the ID of the received signal, If the received signal is a signal related to itself, output an input or output control signal corresponding to the received signal; If the received signal is not a signal related to itself, it is configured to ignore the received signal. Control system.

4. In the first paragraph, the signal database includes signals for individual functions related to components connected thereto. Control system.

5. In the fourth paragraph, the signal is generated according to a standard signal structure, The above standard signal structure includes a signal identifier (ID), an indicator indicating whether the signal is an input or output signal, activation status information of the signal expressed as active high or low, standard controller or area information within the device, connected driver or switch detector information, and pin information of the connected driver or switch detector. Control system.

6. In the third paragraph, the standard controller detects input for individual functions related to the components connected thereto, Generate an input control signal corresponding to the detected input, and configured to transmit the above generated input control signal to a gateway controller or a central computer, Control system.

7. In the third paragraph, the standard controller is configured to detect an output control signal for an individual function related to a component connected thereto, and perform control for the component connected thereto according to the detected output control signal. Control system.

8. In either of paragraphs 6 or 7, The above input control signal and the above output control signal are: Contains information about the signal identifier (ID) and the status value or status value change associated with the component; Control system.

9. In the first paragraph, the standard controller, configured to receive an output control signal for the above function from a central computer, Control system.

10. In the first paragraph, if there are multiple standard controllers, each of the standard controllers is connected to each other so as to be able to communicate with each other one-to-one, Each of the above standard controllers is communicatively connected to a gateway controller, The above gateway controller is communicatively connected to a central computer, Control system.

Images