KR20220099444A - Central communication unit of purpose-buitl-mobility and method for checking and adjusting communication compatibilty thereof - Google Patents

Abstract

A communication compatibility checking method in a central communication device of a purpose built vehicle is provided. The method comprises the following steps of: configuring a DB corresponding to each controller connected to a central communication device as a predetermined module in the purpose built vehicle is changed; matching transmitting/receiving message signals between individual controllers based on the configured DB; and verifying compatibility of each controller connected to the central communication device based on a matching result.

Description

CENTRAL COMMUNICATION UNIT OF PURPOSE-BUITL-MOBILITY AND METHOD FOR CHECKING AND ADJUSTING COMMUNICATION COMPATIBILTY THEREOF

The present invention relates to a central communication device for multi-purpose based mobility and a method for checking and adjusting communication compatibility thereof.

Since the vehicle is a multi-master distributed processing system, information from another controller is independently required for one controller to operate.

As the number of controllers increases, the bandwidth also increases. In order to satisfy these bandwidth requirements, multi-channel CAN, CAN FD, and Ethernet have been introduced, and information transmission is required between networks with different standards. The Central Communication Unit (CCU) was developed for information transfer between these hybrid networks and for the entire network.

1 is a diagram illustrating each hybrid network used in a central communication device.

Since the function of the vehicle is determined at the development stage, it has a fixed network configuration and delivery information. Therefore, in the vehicle development stage, the number of mounted controllers and transmission information are all fixed, and communication is performed based on a determined DB.

2 is a diagram illustrating an example of module exchange in purpose-based mobility.

On the other hand, the recently proposed purpose-based mobility (Purpose Built Vehicle) can change the body module or drive module of the vehicle according to the purpose.

In this case, since the number and types of controllers mounted on each module vary depending on the module characteristics, it is difficult to smoothly exchange information between the controllers using the existing static vehicle network configuration method.

Also, since the configuration of the signal used varies according to the time when the controller is made, accurate information exchange may not be possible unless the module was made at the same time.

Therefore, when a module is changed in purpose-based mobility, it is necessary to check and adjust the communication compatibility between each controller connected to the central communication device.

The problem to be solved by the present invention is to check the compatibility of the controller connected to the central communication device as a predetermined module is changed in the multi-purpose-based mobility and adjust the compatibility if the compatibility is not met, the central communication device of the multi-purpose based mobility and its It provides a method for checking and adjusting communication compatibility.

However, the problems to be solved by the present invention are not limited to the problems described above, and other problems may exist.

In the method for checking communication compatibility in a central communication device of a purpose-built vehicle according to the first aspect of the present invention for solving the above problems, as a predetermined module in the multi-purpose-based mobility is changed, the configuring a DB corresponding to each controller connected to the central communication device; matching the transmission/reception message signals between the respective controllers based on the configured DB; and confirming compatibility of each controller connected to the central communication device based on the matching result.

In some embodiments of the present invention, the step of confirming compatibility of each controller connected to the central communication device based on the matching result may include, in a state in which the central communication device is not connected to an external network, the matching result transmission/reception message If the positions of the signals do not match, it may be determined that a compatibility problem exists in the unmatched controller.

In some embodiments of the present invention, the step of confirming compatibility of each controller connected to the central communication device based on the matching result may include, in a state in which the central communication device is not connected to an external network, the matching result transmission/reception message When the number of bits of the signal does not match, it may be determined that a compatibility problem exists in the mismatched controller.

In some embodiments of the present invention, the checking of compatibility of each controller connected to the central communication device based on the matching result includes version information different from version information of the configured DB among controllers connected to the central communication device In this case, the compatibility of the corresponding controller may be checked based on the compatibility summary table stored in the central communication device.

In some embodiments of the present invention, the step of checking the compatibility of each controller connected to the central communication device based on the matching result may include transmitting and receiving messages that do not match the matching result while the central communication device is connected to an external network. If a signal exists or there is a controller that includes version information different from the version information of the DB, you can check the compatibility by inquiring with the DB management server.

In addition, the method for adjusting communication compatibility in a central communication device of a purpose-built vehicle according to the second aspect of the present invention is connected to the central communication device as a predetermined module in the multi-purpose-based mobility is changed. configuring a DB corresponding to each controller; matching the transmission/reception message signals between the respective controllers based on the configured DB; checking compatibility of each controller connected to the central communication device based on the matching result; and adjusting so that compatibility is maintained between controllers determined to be incompatible as a result of the check.

In some embodiments of the present invention, the step of confirming compatibility of each controller connected to the central communication device based on the matching result may include, in a state in which the central communication device is not connected to an external network, the matching result transmission/reception message If the positions of the signals do not match, determining that a compatibility problem exists in the non-matched controller, and adjusting so that compatibility is maintained between the controllers determined to be incompatible as a result of the check includes: It is possible to adjust the position of the transmit/receive message signal so that compatibility between the controllers is maintained.

In some embodiments of the present invention, the step of confirming compatibility of each controller connected to the central communication device based on the matching result may include, in a state in which the central communication device is not connected to an external network, the matching result transmission/reception message When the number of bits of the signal does not match, it is determined that a compatibility problem exists in the mismatched controller, and the step of adjusting so that compatibility is maintained between the controllers determined to be incompatible as a result of the check includes: It can be adjusted so that compatibility between the controllers is maintained by using a transmit/receive message having a smaller number of bits in the transmit/receive message signal.

In some embodiments of the present invention, the step of adjusting so that compatibility is maintained between the controllers determined to be incompatible as a result of the check includes: Before the predetermined module is changed, the first controller connected to the central communication device is the predetermined module , the compatibility may be maintained by replacing the first controller with a second controller based on the matching result.

In addition, the central communication device capable of confirming communication compatibility in a purpose built vehicle according to the third aspect of the present invention is a communication module that is connected to a plurality of controllers to perform communication, in the multipurpose purpose-based mobility and a memory in which a program for checking compatibility of each connected controller is stored and a processor executing the program stored in the memory as a predetermined module of the controller is changed. In this case, the processor configures a DB corresponding to each connected controller as the predetermined module is changed as the predetermined module is changed as the program is executed, and then matches the transmission/reception message signals between the controllers based on the configured DB, and Based on the matching result, compatibility of each controller can be checked.

A computer program according to another aspect of the present invention for solving the above problems is combined with a computer that is hardware to execute a communication compatibility check and adjustment method in the central communication device of the multi-purpose based mobility, and a computer-readable recording medium is stored in

Other specific details of the invention are included in the detailed description and drawings.

In order to configure multipurpose purpose-based mobility, it is essential to exchange hardware modules suitable for the purpose. However, since all the controllers and information are fixed in a general vehicle network, it is difficult to exchange information between the controllers.

An embodiment of the present invention described above is a method of dynamically reconfiguring a network when a hardware module exchange occurs, and enables actual implementation of conceptual multi-purpose purpose-based mobility.

Since network reconfiguration occurs only in specific situations (module exchange, EOL, etc.), when the dynamic network configuration method of the present invention is applied to a current mass-production vehicle, there is an advantage that the entire vehicle model can be mass-produced with a single central communication device. Therefore, it is possible to reduce the development cost for each vehicle type and the management cost due to the change of the part number.

In addition, when a controller is added through vehicle modification, it is currently impossible to connect the added controller to the vehicle network. That is, even if the MFC (Multi-Function Camera) applied to the new vehicle is installed on the used vehicle and the control unit (MEB) software is updated, the MFC function cannot be operated normally due to the mismatch between the message ID and signal information.

On the contrary, according to an embodiment of the present invention, since a task of matching information in a network is performed, there is an advantage that vehicle update using a new controller is possible.

Effects of the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the following description.

1 is a diagram illustrating each hybrid network used in a central communication device.
2 is a diagram illustrating an example of module exchange in purpose-based mobility.
3A is a diagram for explaining a process of configuring a dynamic network according to an embodiment of the present invention.
3B is a diagram illustrating an example of vehicle communication network information after a module change.
3C is a diagram illustrating an example of a network configuration after the controller responds to a diagnostic message ID.
3D is a diagram for explaining a case where diagnosis message IDs are the same.
3E is a diagram illustrating an example of adding an arbitrary delay time when a communication failure occurs.
3F is a diagram illustrating an example of a result of checking attribute information using a diagnostic message ID of a controller.
4A and 4B are diagrams for explaining a case where message IDs of controllers connected to the same network are the same.
5 is a diagram for explaining a process of confirming communication compatibility.
6 is a view for explaining a central communication device according to an embodiment of the present invention.

Advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only these embodiments allow the disclosure of the present invention to be complete, and those of ordinary skill in the art to which the present invention pertains. It is provided to fully inform those skilled in the art of the scope of the present invention, and the present invention is only defined by the scope of the claims.

The terminology used herein is for the purpose of describing the embodiments and is not intended to limit the present invention. In this specification, the singular also includes the plural, unless specifically stated otherwise in the phrase. As used herein, “comprises” and/or “comprising” does not exclude the presence or addition of one or more other components in addition to the stated components. Like reference numerals refer to like elements throughout, and "and/or" includes each and every combination of one or more of the recited elements. Although "first", "second", etc. are used to describe various elements, these elements are not limited by these terms, of course. These terms are only used to distinguish one component from another. Therefore, it goes without saying that the first component mentioned below may be the second component within the spirit of the present invention.

Unless otherwise defined, all terms (including technical and scientific terms) used herein will have the meaning commonly understood by those of ordinary skill in the art to which this invention belongs. In addition, terms defined in a commonly used dictionary are not to be interpreted ideally or excessively unless clearly specifically defined.

In the description of the present invention, a method of dynamically configuring a network when module exchange occurs for multi-purpose-based mobility will be described, and a method of checking and adjusting communication compatibility between each controller in this process will be described together.

3A is a diagram for explaining a process of configuring a dynamic network according to an embodiment of the present invention.

Meanwhile, each of the steps illustrated in FIG. 3A may be understood to be performed by the central communication device 100, but is not limited thereto.

In the dynamic network configuration method according to an embodiment of the present invention, first, as a predetermined module in the multipurpose purpose-based mobility is changed, the central communication device 100 broadcasts a response request of a diagnostic message ID to the entire controller ( S110).

Since all communication networks used in the vehicle are connected to the central communication device 100 , when a predetermined module configuration is changed, the central communication device 100 must first identify the connected controller using a diagnostic message.

3B is a diagram illustrating an example of vehicle communication network information after a module change. 3C is a diagram illustrating an example of a network configuration after the controller responds to a diagnostic message ID.

At this time, when a module change occurs as shown in FIG. 3B , since the central communication device 100 cannot know information about the controller connected to each network, each controller is used to identify the controller connected to each network first. Broadcasts a request to respond with a diagnostic message ID.

Next, the central communication device 100 receives a response of the diagnostic message ID from the controller corresponding to the broadcasting (S120), and identifies the controller connected to each network based on the received diagnostic message ID.

When each controller responds to the diagnostic message ID, the central communication device 100 can know that the controller having the corresponding diagnostic message ID is connected to each communication network as shown in FIG. 3C .

3D is a diagram for explaining a case where diagnosis message IDs are the same. 3E is a diagram illustrating an example of adding an arbitrary delay time when a communication failure occurs.

On the other hand, when a predetermined module is changed in multi-purpose-based mobility, the manufacturing time of the controllers installed in each module may be different, so that the diagnostic message IDs of different controllers connected to each network are the same as shown in FIG. 3D. can In this case, the central communication device 100 may simultaneously receive responses from the controller A and the controller B in response to the request for a response of the diagnostic message ID, and as a result, communication between the controllers fails due to message duplication. Alternatively, when the central communication device communicates with the individual controllers through the diagnostic message ID, the two controllers A and B respond, making it impossible to receive information.

In order to solve this problem, an embodiment of the present invention checks whether there is a controller that has failed to communicate due to duplicate diagnostic message IDs among all controllers (S130).

And, if there is a duplicate diagnostic message ID as a result of the check, first, in order to prevent the response request process of the diagnostic message ID from failing, when a communication failure (Error frame) occurs in the corresponding response, a corresponding controller is installed as shown in FIG. 3E. A response of the diagnostic message ID is re-received by adding an arbitrary delay time in the process of retransmission to the target. This re-reception process is repeatedly performed until a response of the diagnostic message ID is re-received from the corresponding controller.

In this case, when the network of the controller having the overlapping diagnostic message ID is Ethernet, the central communication device 100 does not separately add a delay time. Since this is 1:1 communication in the case of Ethernet, communication always succeeds even if duplicate diagnostic message IDs occur, so no delay time is added.

When the physical communication process is successful by re-receiving the diagnostic message ID from the corresponding controller, the central communication device 100 can know that the controller A and the controller B use the same diagnostic message ID as shown in FIG. 3D.

Accordingly, the central communication device 100 identifies each controller by checking the classification information of the controller, and requests to change the diagnostic message ID to one of the identified controllers (S140).

For example, the distinction between controller A and controller B can be known by the classification number (0X01 BCM, 0X02 ACU, etc.) of the controller included in the response content of the diagnostic message ID. After confirming the classification information, the central communication device 100 requests to change the diagnostic message ID of the controller having the diagnostic message ID of 1 and the classification number B to 2 through the broadcasting process again, and the diagnostic messages of the controller A and the controller B ID duplication can be resolved.

Next, the central communication device 100 checks the connection information of each controller based on the diagnostic message ID, and transmits message, received message, message type information, message signal configuration and attribute information including DB version of the controller device. request.

Then, the central communication device 100 creates a DB by collecting responses corresponding to each attribute information request (S150), and reactivates each controller based on the generated DB to configure a dynamic network (S160).

3F is a diagram illustrating an example of a result of checking attribute information using a diagnostic message ID of a controller.

After checking the independent diagnostic message ID for each controller, the central communication device 100 requests transmission/reception message and message type information, signal configuration of the message, and DB version information using the diagnostic message ID of each controller.

Then, the central communication device 100 collects responses from each controller to generate a DB as shown in Table 1 below.

Network Node Diag ID Tx Msg Rx Msg DB Ver ID Type Signals ID Type Signals CAN A One One C ... 2 B ... 1.0 CAN B 2 2 B ... 3 P ... 1.0 CAN FD C 3 3 P ... 4 C ... 1.0 CAN FD D 4 4 C ... 5 C ... 1.0 Ethernet E 5 5 P ... 6 C ... 1.0 Ethernet F 6 6 C ... One C ... 1.0

In addition to this, according to an embodiment, the central communication device 100 may generate a routing DB (RDB) by extracting some of attribute information from the generated DB. That is, in the case of a message requiring inter-network information exchange, the central communication device 100 may extract some information as shown in Table 2 below to generate the RDB.

ID Type Source Network Destination Network One C CAN Ethernet 3 P CAN FD CAN 5 P Ethernet CAN FD

4A and 4B are diagrams for explaining a case in which message IDs of controllers connected to the same network are the same. Meanwhile, in an embodiment of the present invention, messages from controllers connected to the same network among all controllers have the same ID as shown in Table 3; It may occur to have In this case, the central communication device 100 may solve the duplicate message problem by adjusting the ID of the duplicate message after checking whether there is a duplicate message (S210).

Network Node Diag ID Tx Msg Rx Msg DB Ver ID Type Signals ID Type Signals CAN A One One C ... One B ... 1.0 CAN B 2 One B ... 3 P ... 1.0 CAN FD C 3 3 P ... 4 C ... 1.0 CAN FD D 4 4 C ... 5 C ... 1.0 Ethernet E 5 5 P ... 6 C ... 1.0 Ethernet F 6 6 C ... One C ... 1.0

Specifically, in order to confirm that the IDs having the same message are different messages, the central communication device 100 compares the message type information and the message signal configuration (S221). And based on the comparison result, the message is activated and removed based on the priority of each controller corresponding to the duplicate message. In one embodiment, the central communication device 100 configures message type information and message signal of the duplicate message as a result of the comparison. If this is exactly the same (S211-Y), the message of the controller having the higher priority of the diagnostic message ID of each controller corresponding to the duplicate message is activated, and the message of the controller having the lower priority is removed (S222). That is, when the two values are completely identical, the central communication device 100 activates only a message corresponding to a controller having a low diagnostic message ID.

Here, the priority of the diagnostic message ID has a higher priority as the value of the ID is lower.

On the other hand, if at least one of the message type information and the message signal configuration of the duplicate message is different from the comparison result (S221-N), the central communication device 100 determines that the priority of the diagnostic message ID of each controller corresponding to the duplicate message is different from each other (S221-N). The value is increased so that the message ID of the low controller does not overlap with the message ID of other controllers (S223).

If the value of the increased message ID exceeds the preset threshold (S224-Y), the priority of the message is much lowered, so the central communication device 100 generates and adds a Diagnostic Trouble Code (DTC). Thus, it is possible to reconfirm whether the module exchange process is correct (S225).

After configuring the DB by using the message information of the controller connected as described above, the central communication device 100 may perform a process of confirming communication compatibility.

5 is a diagram for explaining a process of confirming communication compatibility.

Specifically, the central communication device 100 matches the transmission/reception message signals between each controller based on the configured DB, and checks the compatibility of each controller connected to the central communication device 100 based on the matching result (S310). Then, the central communication device 100 adjusts to maintain compatibility between the controllers determined to be incompatible as a result of the check (S320).

In this case, an embodiment of the present invention may perform different methods of checking and adjusting compatibility based on whether the central communication device 100 is connected to an external Internet network.

In an embodiment, in a state in which the central communication device 100 is not connected to an external network, the central communication device 100 may determine that there is a problem in compatibility based on a predetermined rule.

First, when the location of the transmission/reception message signal does not match as a result of the matching, the central communication device 100 may determine that a compatibility problem exists in the non-matching controller. In addition, it is possible to adjust the positions of the transmission/reception message signals of the controllers that do not match so that compatibility between the controllers is maintained.

In another embodiment, when the number of bits of the transmission/reception message signal does not match in a state in which the central communication device 100 is not connected to an external network, it may be determined that a compatibility problem exists in the mismatched controller. In addition, it can be adjusted so that compatibility between the controllers is maintained by using a transmit/receive message having a smaller number of bits in the transmitted/received message signal of the non-matching controller.

Contrary to this, when the central communication device 100 is connected to the external network and the number of bits of the transmission/reception message signal does not match, the central communication device 100 may check the compatibility by inquiring the corresponding content to the DB management server through the external Internet network. .

In addition, in a state in which the central communication device 100 is connected to an external network, if the controller includes version information different from the DB version information, the controller inquires the corresponding content to the DB management server through the external Internet network to check the compatibility. can At this time, the central communication device 100 may change the DB and the RDB by inquiring the DB management server for information on the mounted controller and also receiving a replaceable controller signal when a specific controller signal disappears.

In one embodiment, the central communication device 100 is connected to the controller when the controller includes version information different from the version information of the DB configured according to the previous step (S330), since the controller may interpret the same value differently. Compatibility of the corresponding controller may be checked based on the compatibility summary table stored in the central communication device 100 (S340). Since the DB used in the vehicle does not change significantly unless the generation changes, if a compatibility summary table is created based on the changes, the signal compatibility can be checked even if the DB version used by the controller is different.

In addition, when the first controller connected to the central communication device 100 is changed to a predetermined module before being changed to a predetermined module, the central communication device 100 excludes the first controller based on the matching result of the transmission/reception message signals. By replacing the controller with a second controller, adjustments can be made to maintain compatibility. That is, when there is no specific controller signal required, the central communication device 100 may replace it with a similar controller signal. For example, if the ESC controller is excluded due to module exchange in purpose-based mobility in a state where there is a controller made to require reception of vehicle speed information from the ESC controller, the central communication device 100 matches based on the transmission/reception message signal Therefore, compatibility can be maintained by changing the DB and RDB to deliver vehicle speed information such as cluster.

Through this process, the central communication device 100 in an embodiment of the present invention transmits the finally adjusted DB to each controller so that each controller can activate communication based on the latest DB. . In this case, the central communication device 100 checks whether a function of the controller is operating based on the received information because the signal or DB version of the message received by the controller may vary. And if the controller function is not a problem, re-enable the controller to provide full or limited functionality. In addition, the central communication device 100 performs a message transfer function between networks based on the adjusted RDB.

On the other hand, when an essential function is not activated as a predetermined module is changed, the central communication device 100 may leave the DTC to check whether the progress of the module conversion process is valid.

Meanwhile, in the above description, steps S110 to S340 may be further divided into additional steps or combined into fewer steps according to an embodiment of the present invention. In addition, some steps may be omitted if necessary, and the order between steps may be changed. In addition, the contents of FIGS. 3A to 5 may also be applied to the contents of FIG. 6 even if other contents are omitted.

Hereinafter, a central communication device (hereinafter, the central communication device 100) capable of confirming communication compatibility in multi-purpose-based mobility according to an embodiment of the present invention will be described with reference to FIG. 6 .

6 is a view for explaining the central communication device 100 according to an embodiment of the present invention.

The central communication device 100 according to an embodiment of the present invention includes a communication module 110 , a memory 120 , and a processor 130 .

The communication module 110 is connected to a plurality of controllers through a predetermined communication network to perform communication.

The memory 120 stores a program for checking compatibility of each connected controller as a predetermined module is changed in the multi-purpose-based mobility, and the processor 130 executes the program stored in the memory 120 .

The processor 130 configures a DB corresponding to each connected controller as a predetermined module is changed, matches the transmission/reception message signals between the respective controllers based on the configured DB, and checks the compatibility of each controller based on the matching result do.

The communication compatibility check and adjustment method in the central communication device 100 of the multipurpose purpose-based mobility according to the embodiment of the present invention described above is implemented as a program (or application) to be executed in combination with a computer, which is hardware. may be stored in the medium.

The above-mentioned program, in order for the computer to read the program and execute the methods implemented as a program, C, C++, JAVA, Ruby, which the processor (CPU) of the computer can read through the device interface of the computer; It may include code coded in a computer language such as machine language. Such code may include functional code related to a function defining functions necessary for executing the methods, etc., and includes an execution procedure related control code necessary for the processor of the computer to execute the functions according to a predetermined procedure can do. In addition, such code may further include additional information necessary for the processor of the computer to execute the functions or code related to memory reference for which location (address address) in the internal or external memory of the computer to be referenced. have. In addition, when the processor of the computer needs to communicate with any other computer or server located remotely in order to execute the above functions, the code uses the communication module of the computer to determine how to communicate with any other computer or server remotely. It may further include a communication-related code for whether to communicate and what information or media to transmit and receive during communication.

The storage medium is not a medium that stores data for a short moment, such as a register, a cache, a memory, etc., but a medium that stores data semi-permanently and can be read by a device. Specifically, examples of the storage medium include, but are not limited to, ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage device. That is, the program may be stored in various recording media on various servers accessible by the computer or in various recording media on the computer of the user. In addition, the medium may be distributed in a computer system connected by a network, and a computer-readable code may be stored in a distributed manner.

The above description of the present invention is for illustration, and those of ordinary skill in the art to which the present invention pertains can understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. For example, each component described as a single type may be implemented in a distributed manner, and likewise components described as distributed may also be implemented in a combined form.

The scope of the present invention is indicated by the following claims rather than the above detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be interpreted as being included in the scope of the present invention. do.

100: central communication unit
110: communication module
120: memory
130: processor

Claims (10)

In a method for checking communication compatibility in a central communication device of a multipurpose purpose-based mobility (Purpose Built Vehicle),
configuring a DB corresponding to each controller connected to the central communication device according to a change in a predetermined module in the multi-purpose-based mobility;
matching the transmission/reception message signals between the respective controllers based on the configured DB; and
Comprising the step of confirming the compatibility of each controller connected to the central communication device based on the matching result,
A method of verifying communication compatibility in a central communication device of multi-purpose-based mobility.
According to claim 1,
Checking the compatibility of each controller connected to the central communication device based on the matching result comprises:
In a state in which the central communication device is not connected to an external network, when the location of the transmission/reception message signal does not match as a result of the matching, it is determined that a compatibility problem exists in the unmatched controller,
A method of verifying communication compatibility in a central communication device of multi-purpose-based mobility.
According to claim 1,
Checking the compatibility of each controller connected to the central communication device based on the matching result comprises:
In a state in which the central communication device is not connected to an external network, when the number of bits of the transmission/reception message signal does not match as a result of the matching, it is determined that a compatibility problem exists in the unmatched controller,
A method of verifying communication compatibility in a central communication device of multi-purpose-based mobility.
According to claim 1,
Checking the compatibility of each controller connected to the central communication device based on the matching result comprises:
When the controller connected to the central communication device includes version information different from the version information of the configured DB, checking the compatibility of the corresponding controller based on the compatibility summary table stored in the central communication device,
A method of verifying communication compatibility in a central communication device of multi-purpose-based mobility.
According to claim 1,
Checking the compatibility of each controller connected to the central communication device based on the matching result comprises:
When the central communication device is connected to the external network and there is a message signal that does not match the matching result or there is a controller including version information different from the version information of the DB, check the compatibility by inquiring with the DB management server that is,
A method of verifying communication compatibility in a central communication device of multi-purpose-based mobility.
In a method for adjusting communication compatibility in a central communication device of a multipurpose purpose-based mobility (Purpose Built Vehicle),
configuring a DB corresponding to each controller connected to the central communication device according to a change in a predetermined module in the multi-purpose-based mobility;
matching the transmission/reception message signals between the respective controllers based on the configured DB;
checking compatibility of each controller connected to the central communication device based on the matching result; and
Comprising the step of adjusting so that compatibility is maintained between the controllers determined to be incompatible as a result of the check,
A method for adjusting communication compatibility in a central communication device of multi-purpose-based mobility.
7. The method of claim 6,
Checking the compatibility of each controller connected to the central communication device based on the matching result comprises:
In a state in which the central communication device is not connected to an external network, if the location of the transmission/reception message signal does not match as a result of the matching, it is determined that a compatibility problem exists in the unmatched controller,
Adjusting so that compatibility is maintained between the controllers determined to be incompatible as a result of the check,
Adjusting the position of the transmitted and received message signal of the unmatched controller to maintain compatibility between the controllers,
A method for adjusting communication compatibility in a central communication device of multi-purpose-based mobility.
7. The method of claim 6,
Checking the compatibility of each controller connected to the central communication device based on the matching result comprises:
If the number of bits of the transmission/reception message signal does not match as a result of the matching in a state in which the central communication device is not connected to an external network, it is determined that a compatibility problem exists in the unmatched controller,
Adjusting so that compatibility is maintained between the controllers determined to be incompatible as a result of the check,
Adjusting so that compatibility between the controllers is maintained by using a transmit/receive message with a smaller number of bits in the transmit/receive message signal of the unmatched controller,
A method for adjusting communication compatibility in a central communication device of multi-purpose-based mobility.
7. The method of claim 6,
Adjusting so that compatibility is maintained between the controllers determined to be incompatible as a result of the check,
When the first controller connected to the central communication device is changed to the predetermined module before the predetermined module is changed and excluded as the predetermined module is changed, the compatibility is improved by replacing the first controller with a second controller based on the matching result. adjusted to maintain
A method for adjusting communication compatibility in a central communication device of multi-purpose-based mobility.
In a central communication device capable of confirming communication compatibility in a multipurpose purpose-based mobility (Purpose Built Vehicle),
A communication module that is connected to a plurality of controllers and performs communication;
A memory in which a program is stored for checking the compatibility of each connected controller as a predetermined module is changed in the multi-purpose-based mobility; and
Including a processor for executing the program stored in the memory,
As the program is executed, the processor configures a DB corresponding to each connected controller as the predetermined module is changed, then matches the transmission/reception message signals between the controllers based on the configured DB, and the matching result to check the compatibility of each controller based on
A central communication device that can check communication compatibility in multi-purpose-based mobility.

Images