KR102384978B1 - Automatic port design apparatus and method of electronic control unit based on value - Google Patents

Abstract

An apparatus for automatically designing a port of a micro controller unit (MCU) based on a value according to a preferred embodiment of the present invention comprises: a value setting unit for generating port value information by setting a value for each of a plurality of ports of an MCU and generating requirement value information by setting a value for each of a plurality of requirements of a vehicle domain; and an automatic design unit which uses the port value information and the requirement value information to set a priority of each of the plurality of requirements and the plurality of ports, and generates port design information by designing functions included in the plurality of requirements in the plurality of ports according to the priority. The present invention can reduce a port design time.

Description

AUTOMATIC PORT DESIGN APPARATUS AND METHOD OF ELECTRONIC CONTROL UNIT BASED ON VALUE

The present invention relates to an apparatus and method for automatically designing a port of a value-based microcontroller unit.

In recent years, as vehicle automation technology develops, many microcontroller units for automatic vehicle control are mounted on vehicles.

In addition, as the performance of the microprocessor is improved, the microcontroller unit can control more functions through one microprocessor.

Accordingly, the requirement for integrating various existing microcontroller units into one microcontroller unit is increasing, and the demand for a technology for controlling various functions of a vehicle using one microprocessor is increasing.

Conventionally, in order to control various functions using one microprocessor, a port design of a microcontroller unit has been made by an expert in the vehicle domain performing various functions.

However, in order to integrate a variety of new functions, it takes a lot of time because an expert in a domain performing various functions has to be involved in the selection of a microcontroller unit to a port design.

Accordingly, there is a need to reduce development time through design automation of a microcontroller unit that integrates and controls various new functions.

Republic of Korea Patent Publication No. 2011-0125989

Accordingly, the present invention has been devised in view of the above circumstances, and when it is desired to implement various control functions using a single microprocessor, port design is performed by automatically designing functions applied to the input/output ports of the microprocessor according to the port design algorithm. An object of the present invention is to provide an apparatus and method for automatically designing a port of a value-based microcontroller unit that can reduce time.

To achieve the above object, an apparatus for automatically designing a port of a value-based microcontroller unit according to a preferred embodiment of the present invention for achieving the above object sets a value to each of a plurality of ports of a microcontroller unit (MCU) to generate port value information, a value setting unit configured to set a value for each of a plurality of requirements of a domain to generate requirement value information; and setting a priority of each of the plurality of ports and the plurality of requirements by using the port value information and the requirement value information, and assigning a function included in the plurality of requirements according to the priority to the plurality of and an automatic design unit for designing the port and generating port design information.

The value setting unit may assign a higher value to a port having a relatively large number of available main functions among the plurality of ports.

It may further include; a requirements list design unit for designing a list of requirements by listing each type of main function included in the plurality of requirements.

The value setting unit may assign a higher value to a requirement in which a relatively large number of main functions of the same type are included in the requirement list among the plurality of requirements.

The automatic design unit, according to the port value information and the requirement value information, arranges the plurality of requirements in an order from a high value to a low value, and in the order from a low value to a high value By arranging a plurality of ports, a priority may be set for each of the plurality of requirements and the plurality of ports.

The automatic design unit may generate a checkpoint when at least two ports supporting the same requirement exist during function design for the plurality of ports.

The automatic design unit, when the checkpoint exists during the design of the function for the port of the lowest priority, the main function of the requirement in the port for which the design is not completed among the at least two ports used for the generation of the checkpoint can be designed.

a first database unit in which information about the plurality of ports is stored; and a second database unit storing information on the plurality of requirements.

It may further include; a weight setting unit for setting a weight according to a weight command of the user for each of the plurality of ports.

In a method for automatically designing a port of a value-based microcontroller unit according to a preferred embodiment of the present invention for achieving the above object, a value is set for each of a plurality of ports of a microcontroller unit (MCU) to generate port value information, and the vehicle a value setting step of setting a value for each of a plurality of requirements of the domain to generate requirement value information; a priority setting step of setting priorities of each of the plurality of ports and the plurality of requirements by using the port value information and the requirement value information; and a port design step of generating port design information by designing functions included in the plurality of requirements in the plurality of ports according to the priority.

The port design step may include: a port selection step of selecting a port having the highest priority among the plurality of ports; and a first requirement determination step of determining whether the selected port can support the main function of the requirement having the highest priority among the plurality of requirements.

The port design step is a port comparison step of determining whether the selected port has the same value by comparing the port of the next priority with the port of the next priority when the selected port can support the main function of the highest priority requirement ; and when the selected port and the port of the next priority have the same value, a second requirement determining step of determining whether the port of the next priority can support the main function of the requirement with the highest priority; may further include.

The port design step may further include a checkpoint generation step of generating a checkpoint when the port of the next priority can support the main function of the highest priority requirement.

In the port design step, if there is no port supporting the requirement with the highest priority except for the port that is created or selected for the checkpoint, a main function of the requirement with the highest priority is selected for the port It may further include; a first function design step of designing.

The port design step may include a port change step of changing to a port of a next priority when the selected port cannot support the requirement with the highest priority; a port completion determination step of determining whether the port changed through the port change step is the last port among a plurality of ports; and a checkpoint presence or absence determination step of determining whether the checkpoint exists when the last port is selected.

In the port design step, if there is the check point, a second function design step of designing a main function of the highest priority requirement in a port that has not been designed among at least two or more ports used for generating the check point ; may be further included.

The priority setting step sets the priority by arranging the plurality of requirements in an order from a high value to a low value, and arranging the plurality of ports in an order from a low value to a high value. can

The method may further include a weight setting step of setting a weight to a specific port among the plurality of ports according to a weight command from a user.

According to an apparatus and method for automatically designing a port for a value-based microcontroller unit according to a preferred embodiment of the present invention, when it is desired to implement various control functions using one microprocessor, the input/output port of the microprocessor according to the port design algorithm is By automatically designing the applied function, the port design time can be reduced.

In addition, according to the automatic design of the port, there is an effect of improving the part in which the quality may vary compared to the prior art.

In addition, there is an effect that the review on the selection of the integrated microcontroller unit proceeds quickly through the quick port design in the requirements review stage.

1 is a block diagram of an apparatus for automatically designing a port of a value-based microcontroller unit according to a preferred embodiment of the present invention.
FIG. 2 is a diagram illustrating an example of resource information available for each port of the MCU stored in the first database unit of FIG. 1 .
3 is a diagram illustrating an example of a plurality of requirements of a vehicle domain stored in a second database unit of FIG. 1 .
4 is a diagram illustrating an example of a requirements list generated by the requirements list design unit of FIG. 1 .
5 is a flowchart of a method for automatically designing a port of a value-based microcontroller unit according to a preferred embodiment of the present invention.
6 is a detailed flowchart of the weight setting step of FIG. 5 .
7 is a detailed flowchart of the value setting step of FIG. 5 .

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. First of all, it should be noted that in adding reference numerals to the components of each drawing, the same components are given the same reference numerals as much as possible even though they are indicated on different drawings. In addition, preferred embodiments of the present invention will be described below, but the technical spirit of the present invention is not limited thereto and may be variously implemented by those skilled in the art without being limited thereto.

1 is a block diagram of an apparatus for automatically designing a port of a value-based microcontroller unit according to a preferred embodiment of the present invention.

Referring to FIG. 1 , an apparatus 100 for automatically designing a port of a value-based microcontroller unit according to a preferred embodiment of the present invention provides modularization of specifications (SPEC.) of MCU (Micro Controller Unit) and modularization of requirements of vehicle domains. , it is characterized by performing the port priority selection of the MCU based on the integration requirements, and the priority-based port automatic design function.

The value-based microcontroller unit port automatic design device 100 includes a first database unit 110 , a second database unit 120 , a requirements list design unit 130 , a weight setting unit 140 , and a value setting unit ( 150 ), and an automatic design unit 160 .

The first database unit 110 may store information on a plurality of ports of the MCU. The plurality of port information may be provided by a manufacturer of the MCU. The first database unit 110 may store information of a main function, an ID, and an auxiliary function usable for each of a plurality of ports. For example, each of the plurality of ports may perform functions such as a voltage input port and a communication port. Information on the main function, ID, and auxiliary function of the plurality of ports will be described later in detail with reference to FIG. 2 .

The second database unit 120 may store requirements for each vehicle domain. The vehicle domain may include a powertrain, a chassis, a body, and infotainment. The infotainment may include a multimedia device, a telematic device, and a Human Machine Interface (HMI) device. A requirement of each vehicle domain may be configured by combining a plurality of main functions, a plurality of IDs, and a plurality of auxiliary functions. The requirements may be geared towards using the MCU for a specific purpose. The requirements of each vehicle domain will be described in detail later with reference to FIG. 3 .

The requirements list design unit 130 may call the requirement information stored in the second database unit 120 . The requirements list design unit 130 may newly design the requirements list based on the fetched requirements information. The requirements list design unit 130 may design the requirements list by listing up for each type of main function included in the requirements of each vehicle domain. The requirements list design unit 130 may transmit the requirements list to the value setting unit 150 .

The weight setting unit 140 may preferentially set a weight for each of the plurality of ports according to a weight command received from the user. In one embodiment, when it is determined that the MCU needs to process predetermined sensor information first, the user can set a high value to the port of the MCU that performs an analog-to-digital conversion function of converting an analog value of sensor information into a digital value. . The weight setting unit 140 may transmit port weight information set for each port of the MCU to the automatic design unit 160 according to a weight command of the user.

The value setting unit 150 may retrieve information of a main function usable for each of the plurality of ports from the first database unit 110 . Also, the value setting unit 150 may retrieve the requirements of each vehicle domain from the second database unit 120 . Also, the value setting unit 150 may receive a list of requirements from the requirements list design unit 130 .

The value setting unit 150 may generate port value information by assigning a high value to a port having a relatively large number of available main functions among a plurality of ports. In addition, the value setting unit 150 may generate the requirement value information by assigning a high value to a requirement including a relatively large number of main functions of the same type in the requirement list among a plurality of requirements.

The value setting unit 150 may transmit the port value information and the requirement value information to the automatic design unit 160 .

The automatic design unit 160 uses the port weight information transmitted from the weight setting unit 140 and the port value information and the requirement value information transmitted from the value setting unit 150 to each of a plurality of ports and a plurality of requirements. Port design information can be created by setting the priority of , and designing a function included in a plurality of requirements in a plurality of ports according to the priority.

The port design information generated in this way can be used to select an MCU and automatically design a main function suitable for each port of the selected MCU.

The automatic design unit 160 may generate final port value information by merging the port weight information and the port value information. The automatic design unit 160 may arrange a plurality of requirements in an order from a high value to a low value. The automatic design unit 160 may arrange a plurality of ports in an order from a low value to a high value. Through this, the automatic design unit 160 may set a priority for each of a plurality of requirements and a plurality of ports.

The automatic design unit 160 may design a function included in a plurality of requirements in a plurality of ports according to a set priority.

Meanwhile, the automatic design unit 160 may generate a checkpoint when at least two ports supporting the same requirement exist during function design for a plurality of ports.

The automatic design unit 160 may check the presence or absence of a checkpoint during function design for a port with the lowest priority. In this case, when the check point is generated, the automatic design unit 160 may design the main function of the requirement in a port for which design is not completed among at least two ports used to generate the check point.

When the checkpoint is not generated, the automatic design unit 160 may determine that the function design for each port has failed. In this case, the automatic design unit 160 may request an MCU having a higher structure than the existing MCU included in the first database unit 110 in a notification manner. Thereafter, the automatic design unit 160 may perform functional design of a plurality of ports using the port value information generated based on the new MCU information.

FIG. 2 is a diagram illustrating an example of resource information available for each port of the MCU stored in the first database unit of FIG. 1 .

Referring to FIG. 2 , available resource information for each port of the MCU stored in the first database unit 110 may be checked. The MCU may include a first port PORT1 , a second port PORT2 , a third port PORT3 , a fourth port PORT4 , and a fifth port PORT5 . Resource information available in each of the plurality of ports may include a main function, an ID, and an auxiliary function.

In an embodiment, the main function of the first port PORT1 may include two analog-to-digital converters (ADC) and a transmitter SENT. The ID of each main function of the first port PORT1 may be ADC0, ADC4, and SENT0. The auxiliary function of the first port PORT1 may include input functions IN1 , IN4 , and IN2 .

In an embodiment, the main function of the second port PORT2 may include two communication devices (CAN: Controller Area Network) and a PWM timer (PWMTIMER). The ID of each main function of the second port PORT2 may be CAN0, CAN1, or TIMER1. Auxiliary functions of the second port PORT2 may include a receiving end RX, a transmitting end TX, and an input device INPUT.

Hereinafter, detailed descriptions of the third port PORT3 , the fourth port PORT4 , and the fifth port PORT5 will be omitted.

The types of main functions available for each MCU port can be used to set the value of the MCU port.

3 is a diagram illustrating an example of a plurality of requirements of a vehicle domain stored in a second database unit of FIG. 1 .

Referring to FIG. 3 , a plurality of requirements of the vehicle domain stored in the second database unit 120 may be checked. In an embodiment, the requirement 1, the requirement 2, and the requirement 3 may be stored in the second database unit 120 . The requirements are not limited thereto, and a larger number may be stored in the second database unit 120 according to vehicle domains.

The plurality of requirements may be configured by combining a plurality of main functions, a plurality of IDs, and a plurality of auxiliary functions together.

Requirement 1 may include two communication devices (CAN), an analog-to-digital converter (ADC), and two PWM timers (PWMTIMER) as main functions. In addition, requirement 1 is ID information corresponding to the main function, and may include ADC3, TIMER1, and TIMER2 excluding the communication device (CAN) of the main function. In addition, Requirement 1 may include a receiving end (RX), a transmitting end (TX), an input end (IN), an input device (INPUT), and an output device (OUTPUT) sequentially corresponding to the main function as auxiliary functions.

Requirement 2 may include two communication devices (CAN), an analog-to-digital converter (ADC), and two PWM timers (PWMTIMER) as main functions. In addition, the requirement 2 may include CAN1 corresponding to the communication device (CAN) of the main function as ID information corresponding to the main function. In addition, Requirement 2 may include a receiving end (RX), a transmitting end (TX), an input terminal (IN), an input device (INPUT), and an output device (OUTPUT) sequentially corresponding to the main function as auxiliary functions.

Requirement 3 may include three Ethernets and a transmitter (SENT) as main functions. In addition, Requirement 3 may include SENT1 as an ID corresponding to the transmitter (SENT) of the main function. In addition, Requirement 3 includes a receiving end (RX) and a transmitting end (TX) corresponding to two Ethernets of the main function as auxiliary functions, and may include a receiving end (RX) corresponding to the transmitter (SENT) of the main function. .

These multiple requirements may be prepared to use the MCU for a specific purpose. For example, if the MCU is used for the purpose of converting an analog signal to a digital value, making a request for the converted digital value as an input of a CAN signal, and outputting a CAN signal in consideration of the time value, A combination of main functions may be required.

4 is a diagram illustrating an example of a requirements list generated by the requirements list design unit of FIG. 1 .

Referring to FIG. 4 , a list of requirements prepared through the requirements information stored in the second database unit 120 of FIG. 1 may be checked.

The requirements list design unit 130 may receive requirement information from the second database unit 120 . The requirements list design unit 130 may design the requirements list by using the received requirements information.

The requirements list design unit 130 may classify the main functions included in the requirements information by the same type. The requirements list design unit 130 may design the requirements list by arranging the main functions in the order of many of the same types. The requirements list design unit 130 may transmit the requirements list to the value setting unit 150 .

5 is a flowchart of a method for automatically designing a port of a value-based microcontroller unit according to a preferred embodiment of the present invention.

1 and 5 , the method for automatically designing a port of a value-based microcontroller unit according to a preferred embodiment of the present invention sets a value for each port of the MCU, sets the value for each requirement of the vehicle domain, It is characterized in that the port design information is created by setting the priority based on the value set port and requirements, and designing the function of the requirement in the port according to the priority. An MCU may be selected through such port design information, and a main function of each port of the selected MCU may be automatically designed.

The method for automatically designing a port of the value-based microcontroller unit may include steps S501 to S527.

First, in the weight setting step S501 , the weight setting unit 140 may set a weight to a specific port according to a weight command from the user. Ports to which weights are set may be weighted in subsequent value setting. In an embodiment, if the user determines that a weight is required for a specific main function, a weight may be set for all ports supporting the specific main function. The weight setting step S501 will be described in detail later with reference to FIG. 6 .

In the value setting step ( S503 ), the value setting unit 150 may set a value for each of a plurality of ports of the MCU, and set the value for each requirement of the vehicle domain. When setting values for each port, the value setting unit 150 may set a high value to a port having a relatively large number of available main functions among a plurality of ports. When setting a value for a requirement, the value setting unit 150 may set a high value to a requirement in which a relatively large number of main functions of the same type are included in the pre-generated list of requirements. Since the process of generating the requirements list has been described above, it is omitted. The value setting step ( S503 ) will be described later in detail with reference to FIG. 7 .

In the priority setting step (S505), the automatic design unit 160 sorts a plurality of requirements in an order from a high value to a low value, and arranges the plurality of ports in an order from a low value to a high value. can do. Through this, the automatic design unit 160 may set a priority for each of a plurality of requirements and a plurality of ports.

In the requirement design completion determination step ( S507 ), the automatic design unit 160 may determine whether port design for a plurality of aligned requirements is completed. When the port design for the plurality of aligned requirements is completed, the automatic design unit 160 may generate port design information and end the automatic port design of the MCU.

In the port selection step ( S509 ), the automatic design unit 160 may select a port having a high priority from among a plurality of arranged ports. Here, the priority J of the port may be represented by 0. Hereinafter, it is defined that the higher the value of the priority J, the lower the priority.

In the first requirement determination step S511 , the automatic design unit 160 may determine whether the currently selected port can support the main function of the highest priority requirement among the sorted requirements.

In the port comparison step (S513), when the currently selected port [J] can support the main function of the requirement, the automatic design unit 160 compares the currently selected port with the port of the next priority to see if it has the same value can judge Here, the currently selected port may have a priority of J, and a port of the next priority may have a lower priority (J++).

In the second requirement determination step (S515), the automatic design unit 160, when the port [J++] of the next priority has the same value as the currently selected port [J=0], the port [J++] of the next priority ] can be determined to support the highest priority requirements. If the automatic design unit 160 cannot support the requirement of the highest priority in the port [J++] of the next priority, it returns to the port comparison step (S513) and prioritizes whether there is a port having the same value as the currently selected port. You can find them by lowering the rank.

In the checkpoint generation step (S517), the automatic design unit 160 is the port [J++] of the next priority having the same value as the currently selected port [J = 0] If the highest priority can support the requirement , can create checkpoints. The check point may be a point at which the automatic design unit 160 returns to find a port supporting the predetermined requirement when there is no port supporting the predetermined requirement. After the checkpoint is generated, the automatic design unit 160 may design the main function in the port of the highest priority that can support the requirement of the highest priority. Then, the automatic design unit 160 returns to the value setting step ( S503 ) and may perform value setting on the remaining ports and requirements, except for the requirements for which the design of the ports of the main function is completed and the ports for which the design is completed.

On the other hand, in the first function design step (S519) after the port comparison step (S513), the automatic design unit 160, except for the selected port, if there is no port supporting the requirement of the highest priority, the highest priority The main function of the requirement can be designed in the selected port [J]. Then, the automatic design unit 160 returns to the value setting step ( S503 ) and may perform value setting on the remaining ports and requirements except for the requirements for which the port design of the main function is completed and the port for which the design of the main function is completed.

On the other hand, in the port change step (S521) after the first requirement determination step (S511), when the currently selected port [J] cannot support the requirement of the highest priority, the currently selected port You can change [J] to the port [J++] of the next priority.

In the port completion determination ( S523 ), the automatic design unit 160 may determine whether the currently selected port is the last port among the sorted ports. When the currently selected port is not the last port among the sorted ports, the automatic design unit 160 may return to step S511 and perform subsequent steps.

In the checkpoint presence determination step S525 , when the currently selected port is the last port among the sorted ports, the automatic design unit 160 may determine the checkpoint presence or absence. The automatic design unit 160 may end automatic port design when there is no checkpoint. At this time, when the automatic design unit 160 terminates the automatic design without finding the checkpoint, it may be determined that the automatic port design has failed. The automatic design unit 160 may additionally request specification information for the upper MCU.

In the second function design step ( S527 ), if there is a check point, the automatic design unit 160 returns to the check point generation time, and returns the main function to the incompletely designed port [J++] among at least two or more ports used to generate the check point. can be designed. Then, the automatic design unit 160 may return to the value setting step ( S503 ) and perform value setting on the remaining ports and requirements, except for the requirements for which the port design of the main function is completed and the ports for which the design is completed.

The automatic design unit 160 may generate port design information when the port design for the requirements is completed. Port design information may be used to select an MCU. The selected MCU can automatically design a port function based on the port design information.

6 is a detailed flowchart of the weight setting step of FIG. 5 .

Referring to FIG. 6 , the weight setting step S501 may include steps S610 to S680 .

In the weight command input step ( S610 ), the weight setting unit 140 may receive a weight command from the user. The weight setting unit 140 may receive a plurality of weight commands.

In the port selection step ( S620 ), when a weight command from the user is input, the weight setting unit 140 may select a port having a higher priority from among a plurality of ports. Here, the priority J of the port may be 0. A port may have a higher priority as the value of J is lower.

In the weight determination step S630 , the weight setting unit 140 may determine whether the selected port is a port currently included in the weight command.

In the weight application step S640 , when the selected port is included in the current weight command, the weight setting unit 140 may apply a predetermined weight to the selected port.

In the port determination step S650 , the weight setting unit 140 , when the port selected in step S630 is not included in the current weight command or a predetermined weight is applied in step S640 , the currently selected port has the lowest priority. It can be determined whether it is the last port.

In the port change step ( S660 ), when the currently selected port is not the last port, the weight setting unit 140 may change the currently selected port to the next port having a lower priority by one level. The weight setting unit 140 may return to step S630 to determine whether the selected port is currently included in the weight command.

In the weight command determination step S670 , the weight setting unit 140 may determine whether the user's weight command is the last command. The weight setting unit 140 may end weight setting when the user's weight command is the last command.

In the step of changing the weight command ( S660 ), the weight setting unit 140 may change to the next weight command when the current weight command is not the last command. The weight setting unit 140 may repeatedly perform steps after step S620 to apply a weight according to the next weight command.

7 is a detailed flowchart of the value setting step of FIG. 5 .

Referring to FIG. 7 , the value setting step S503 may include steps S710 to S790 .

In the information input step S710 , the value setting unit 150 may receive the MCU port information and the vehicle domain requirement information from the first database unit 110 and the second database unit 120 .

In the port selection step ( S720 ), the value setting unit 150 may select a port having a high priority from among a plurality of ports. Here, the priority j of the port may be 0. A port may have a higher priority as the value of j is lower.

In the value determination step S730 , the value setting unit 150 may determine whether the selected port [j] supports the main function of the requirement [i] having the highest priority. Here, the lower the i of the requirement, the higher the priority may be.

In the first value application step (S740), the value setting unit 150 reduces the value of the current requirement when the currently selected port [j] supports the main function of the highest priority requirement [i] can do.

In the second value application step S750 , the value setting unit 150 may increase the value of the currently selected port [j].

In the port determination step (S760), the value setting unit 150, if the port selected in step S730 does not support the main function of the current requirement, or if the value of the current port is increased in step S750, the currently selected port is It can be determined whether it is the last port with the lowest priority.

In the port change step S770 , when the currently selected port is not the last port, the value setting unit 150 may change the currently selected port to the next port having a lower priority by one level. The value setting unit 150 may return to step S730 to determine whether the changed port supports the main function of the current requirement.

In the requirement determination step (S780), the value setting unit 150 may determine whether the current requirement is the last requirement. The value setting unit 150 may end value setting when the current requirement is the last requirement.

In the requirement change step S790 , when the current requirement is not the last requirement, the value setting unit 150 may change to the next requirement [i++] having a lower priority by one level. The value setting unit 150 may repeat steps after step S720 to apply a value according to the following requirements.

The above description is merely illustrative of the technical idea of the present invention, and those of ordinary skill in the art to which the present invention pertains may make various modifications, changes and substitutions within the scope without departing from the essential characteristics of the present invention. will be. Accordingly, the embodiments disclosed in the present invention and the accompanying drawings are for explaining, not limiting, the technical spirit of the present invention, and the scope of the technical spirit of the present invention is not limited by these embodiments and the accompanying drawings .

Steps and/or operations according to the present invention may occur concurrently in different embodiments, either in a different order, or in parallel, or for different epochs, etc., as would be understood by one of ordinary skill in the art. can

Depending on the embodiment, some or all of the steps and/or operations run instructions, a program, an interactive data structure, a client and/or a server stored in one or more non-transitory computer-readable media. At least some may be implemented or performed using one or more processors. The one or more non-transitory computer-readable media may be illustratively software, firmware, hardware, and/or any combination thereof. Further, the functionality of a “module” discussed herein may be implemented in software, firmware, hardware, and/or any combination thereof.

100: port auto design device of value-based microcontroller unit
110: first database unit
120: second database unit
130: requirements list design department
140: weight setting unit
150: value setting unit
160: automatic design unit

Claims (18)

a value setting unit generating port value information by setting values in each of a plurality of ports of a microcontroller unit (MCU), and generating requirement value information by setting values in each of a plurality of requirements of a vehicle domain; and
Priority of each of the plurality of ports and the plurality of requirements is set using the port value information and the requirement value information, and a function included in the plurality of requirements is assigned to the plurality of ports according to the priority. An automatic design unit that designs and generates port design information;
A port auto design device for a value-based microcontroller unit that includes a. The method of claim 1,
The value setting unit,
A port automatic design device for a value-based microcontroller unit, characterized in that a higher value is given to a port having a relatively large number of main functions available among the plurality of ports. The method of claim 1,
a requirements list design unit for designing a requirements list by listing up for each type of main function included in the plurality of requirements;
Port automatic design device of the value-based microcontroller unit, characterized in that it further comprises. 4. The method of claim 3,
The value setting unit,
The device for automatically designing a port for a value-based microcontroller unit, characterized in that a higher value is given to a requirement in which a relatively large number of main functions of the same type are included in the requirement list among the plurality of requirements. The method of claim 1,
The automatic design unit,
According to the port value information and the requirement value information, sorting the plurality of requirements in an order from a high value to a low value, and arranging the plurality of ports in an order from a low value to a high value to set a priority for each of the plurality of requirements and the plurality of ports. 6. The method of claim 5,
The automatic design unit,
The device for automatically designing a port of a value-based microcontroller unit, characterized in that during the functional design of the plurality of ports, when at least two ports supporting the same requirement exist, a checkpoint is generated. 7. The method of claim 6,
The automatic design unit,
If the checkpoint exists during the function design for the lowest priority port, the main function of the requirement is designed in a port for which design is not completed among the at least two ports used for generating the checkpoint. As a value-based microcontroller unit port auto design device. The method of claim 1,
a first database unit in which information about the plurality of ports is stored; and
a second database unit for storing information on the plurality of requirements;
Port automatic design device of the value-based microcontroller unit, characterized in that it further comprises. The method of claim 1,
a weight setting unit configured to set a weight according to a weight command of a user for each of the plurality of ports;
Port automatic design device of the value-based microcontroller unit, characterized in that it further comprises. a value setting step in which a value setting unit sets a value to each of a plurality of ports of an MCU (Micro Controller Unit) to generate port value information, and sets a value to each of a plurality of requirements of a vehicle domain to generate requirement value information;
a priority setting step in which an automatic design unit sets priorities of each of the plurality of ports and the plurality of requirements by using the port value information and the requirement value information; and
a port design step in which the automatic design unit designs functions included in the plurality of requirements in the plurality of ports according to the priority to generate port design information;
A method for automatically designing ports in a value-based microcontroller unit, comprising: 11. The method of claim 10,
The port design step is
a port selection step in which the automatic design unit selects the port having the highest priority from among the plurality of ports; and
a first requirement determination step of determining whether the port selected by the automatic design unit can support the main function of the requirement having the highest priority among the plurality of requirements;
Port automatic design method of a value-based microcontroller unit comprising a. 12. The method of claim 11,
The port design step is
a port comparison step of determining whether the port selected by the automatic design unit has the same value by comparing the selected port with a port of the next priority when the port selected by the automatic design unit can support the main function of the highest priority requirement; and
A second requirement for determining whether the port of the next priority can support the main function of the requirement with the highest priority when the selected port and the port of the next priority have the same value value judgment step;
Port automatic design method of the value-based microcontroller unit, characterized in that it further comprises. 13. The method of claim 12,
The port design step is
a checkpoint generation step of generating a checkpoint when the automatic design unit can support the main function of the requirement with the highest priority in the port of the next priority;
Port automatic design method of the value-based microcontroller unit, characterized in that it further comprises. 14. The method of claim 13,
The port design step is
When the automatic design unit generates the checkpoint or there is no port supporting the highest priority requirement except for the selected port, the main function of the highest priority requirement is designed in the selected port a first functional design step;
Port automatic design method of the value-based microcontroller unit, characterized in that it further comprises. 14. The method of claim 13,
The port design step is
a port change step of changing to a port of the next priority when the port selected by the automatic design unit cannot support the requirement with the highest priority;
a port completion determination step in which the automatic design unit determines whether the port changed through the port change step is the last port among a plurality of ports; and
a checkpoint determination step of determining whether the checkpoint exists when the automatic design unit selects the last port;
Port automatic design method of the value-based microcontroller unit, characterized in that it further comprises. 16. The method of claim 15,
The port design step is
a second function design step of designing, by the automatic design unit, a main function having the highest priority requirement in a port that has not been designed among at least two or more ports used for generating the check point when there is the check point;
Port automatic design method of the value-based microcontroller unit, characterized in that it further comprises. 11. The method of claim 10,
The priority setting step is
characterized in that the automatic design unit sets the priority by arranging the plurality of requirements in an order from a high value to a low value, and arranging the plurality of ports in an order from a low value to a high value A method for auto-designing ports in a value-based microcontroller unit. 11. The method of claim 10,
a weight setting step in which a weight setting unit sets a weight to a specific port among the plurality of ports according to a weight command from a user;
Port automatic design method of the value-based microcontroller unit, characterized in that it further comprises.

Images