KR102429410B1 - Routing method and apparatus - Google Patents

Abstract

The present invention relates to a method and apparatus for stably routing data by minimizing omission of data occurring in a vehicle network. A routing method according to an embodiment of the present invention comprises: storing a received message in a shared buffer shared by each channel; checking a routing rule of each channel through which the received message is transmitted; generating a descriptor for each channel based on the checked routing rule and an index of a shared buffer in which the received message is stored; and including a part of the received message stored in the shared buffer as a payload with reference to the descriptor and transmitting a transmission message including a header prepared according to the routing rule to the corresponding channel.

Description

ROUTING METHOD AND APPARATUS

The present invention relates to a method and apparatus for routing messages. More particularly, it relates to a method and apparatus for stably routing data by minimizing omission of data occurring in a vehicle network.

A conventional automobile is a set of mechanical devices, but more and more electronic devices are being installed in recent automobiles, and it is no exaggeration to say that the automobile is a collection of various electronic devices. As functions such as vehicle posture control, automatic parking, intelligent driving assistance, and autonomous driving become more common, more and more electronic devices are interlocking with each other in automobiles.

Since various functions are implemented through cooperation of various electronic devices, a considerable amount of information exchange is required between distributed electronic devices. In the past, information was exchanged through 1:1 cable connection between electronic devices. However, as the number of electronic devices gradually increased, this type of network configuration was reduced due to weight increase, design complexity increase, and productivity decrease due to the exponentially increasing number of cables. As a result, it is no longer usable.

In order to solve the problem of complicated wiring inside the vehicle, a communication method that drives all communication inside the vehicle on a single network was needed. Networks and communication protocols were defined and started to be widely used.

CAN generally has a bus (BUS) topology. Message transmission using CAN is performed in such a way that the transmitting node transmits the message to all nodes connected to one bus topology. Multiple devices can send and receive messages through one BUS topology without a 1:1 cable connection between devices. In theory, up to 2,032 devices can be connected in the bus topology of standard CAN, and up to 5,120,000 devices can be connected in extended CAN.

On the other hand, CAN is divided into several classes according to the supported communication speed and purpose. Among them, CAN for low-speed communication (LS CAN) is responsible for general transmission of information such as power windows, seat control devices, and instrument clusters, and operates at 10 kbit/s. It operates at around 125 kbit/s. CAN for High-Speed Communication (HS CAN) is used in devices requiring real-time transmission of information such as powertrain, stability control (ABS brakes, suspension, etc.), engine management, and shifting, and operates from 125 kbit/s to 1 Mbit/s.

To provide communication between subnetworks (eg LS CAN and HS CAN) that exceed the maximum number of devices connectable to one bus (BUS) of CAN or operate at different communication speeds and electrical standards, A gateway device is used between them. In short, the CAN gateway is a device that transmits and exchanges signals and messages in real time between sub-networks of different standards.

As the in-vehicle communication traffic increases, the number of CAN channels increases, which in turn requires an improvement in the routing processing performance of the gateway. As the amount of data to be processed and the number of channels increases, the bus load fluctuates according to certain events, and this sudden bus load causes the loss of messages to be routed. If the amount of memory is sufficient, messages can be buffered for a specified amount of time, but gateways with insufficient memory often lose messages due to momentary bus loads.

1 is a diagram illustrating a process in which a message is routed through a conventional gateway.

Referring to FIG. 1 , a gateway may form channels ch1 to ch3 with different subnetworks, and the gateway includes buffers 12 , 13 , and 14 for each channel. The buffers 12, 13, and 14 are temporary storage spaces used exclusively by the corresponding channel, and are areas in which messages are temporarily stored.

According to FIG. 1, when a conventional gateway receives a message, it first stores the message in the reception buffer 11, identifies a channel through which the message is output, and then stores the message in the buffers 12, 13, and 14 of the channels, respectively. Save the message. That is, when a message is transmitted through three channels, the message is copied at least three times. In particular, when the message is transmitted to a subnetwork that supports segmentation routing (eg, HS CAN), the message is divided into a predetermined number and stored in a buffer of the corresponding channel, thereby further increasing the number of copies.

In FIG. 1, the sub-network #2 is exemplified as a network supporting segment routing, and also exemplifies that received data is divided into four and stored in the buffer 13 of the second channel. According to FIG. 1, received data is copied and stored in each buffer 6 times.

However, when the copy occurs frequently, not only the load of the gateway increases, but also data routing is delayed. Of course, it is also possible to immediately transmit the received data without storing it in the buffer, but message transmission may be delayed due to bus arbitration or bus errors in the subnetwork, so the no-copy policy that does not use a buffer is implemented in the vehicle network. cannot be considered in

Also, when the buffer of a specific channel is filled with data (when it overflows), a situation in which the reception buffer is not emptied or data is lost due to overload of the corresponding channel may occur.

Accordingly, there is a need for a technique for minimizing message loss, preventing overload of the gateway, and routing data through minimal copying.

Korean Patent Publication No. 10-1567973 (2015.11.04.)

The technical problem to be solved by the present invention is to provide a method and apparatus for routing data such that data copy is minimized and routing delay is prevented.

Another technical problem to be solved by the present invention is to provide a method and an apparatus for routing data by preventing an overload of a data routing device and an overflow of a buffer.

Another technical problem to be solved by the present invention is to provide a method and apparatus for routing data such that data loss is minimized.

Another technical problem to be solved by the present invention is to provide a routing method and apparatus for releasing a buffer in consideration of a situation in which a bus error occurs.

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

In order to solve the above technical problem, a routing method according to an embodiment of the present invention comprises the steps of: storing a received message in a shared buffer shared by each channel; checking a routing rule of each channel through which the received message is transmitted; generating a descriptor for each channel based on the checked routing rule and an index of a shared buffer in which the received message is stored; and including a part of the received message stored in the shared buffer as a payload with reference to the descriptor and transmitting a transmission message including a header prepared according to the routing rule to the corresponding channel.

The routing method may include: identifying a first number to which the received message is to be referenced; and confirming a second number of transmitted messages by referring to the received message. and when the second number reaches the first number, releasing an area of the shared buffer corresponding to the index.

The routing method may further include the step of checking the status of each channel and subtracting the first number by the number of channels in which an error has occurred.

The transmitting may include dividing the received message into a predetermined number when the corresponding channel is a channel connected to a destination network for performing division routing, and includes a plurality of transmissions including one of the divided received messages as a payload. It may include sending a message.

In one embodiment, the generating of the descriptor for each channel may include: generating a descriptor including identification information of the checked routing rule and an index of the shared buffer as a channel; and storing the generated descriptor in a storage area of the corresponding channel.

In another embodiment, the generating of the descriptor for each channel may include: generating a descriptor including identification information of the checked routing rule and an index of the shared buffer as a channel; and storing an address that can access the generated descriptor in a storage area of the corresponding channel.

In one embodiment, the transmitting includes the payload of the received message as the payload of the outgoing message, and maintaining or changing the header of the received message based on the routing rule to create a header of the outgoing message may include the step of

For solving the above technical problem, a routing device according to another embodiment of the present invention is shared by each channel and a shared buffer for storing a received message; a control unit that checks a routing rule of each channel through which a received message is transmitted, and generates a descriptor for generating a transmission message for each channel based on the checked routing rule and an index of a shared buffer in which the received message is stored; and forming a plurality of channels, checking the received message in the area of the shared buffer corresponding to the index by referring to the descriptor, and changing one or more of the header and payload of the received message according to the routing rule It may include a transmission unit for transmitting the generated transmission message to the corresponding channel.

1 is a diagram illustrating a process of routing a message through a conventional gateway.
2 is a diagram illustrating a CAN system according to an embodiment of the present invention.
FIG. 3 is a diagram illustrating the configuration of a gateway described with reference to FIG. 2 .
4 is a diagram illustrating a data structure of a message.
5 is a diagram illustrating a routing rule table.
6 is a first flowchart illustrating a method of routing a message in a gateway according to another embodiment of the present invention.
7 is a second flowchart illustrating a method of routing a message in a gateway according to another embodiment of the present invention.
8 is a third flowchart illustrating a method of routing a message in a gateway according to another embodiment of the present invention.
9 is a fourth flowchart illustrating a method of routing a message in a gateway according to another embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. 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 technical idea of the present invention is not limited to the following embodiments, but may be implemented in various different forms, and only the following embodiments complete the technical idea of the present invention, and in the technical field to which the present invention belongs It is provided to fully inform those of ordinary skill in the art of the scope of the present invention, and the technical spirit of the present invention is only defined by the scope of the claims.

In adding reference numerals to the components of each drawing, it should be noted that the same components are given the same reference numerals as much as possible even though they are indicated on different drawings. In addition, in describing the present invention, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

Unless otherwise defined, all terms (including technical and scientific terms) used herein may be used with the meaning commonly understood by those of ordinary skill in the art to which the present invention belongs. In addition, terms defined in a commonly used dictionary are not to be interpreted ideally or excessively unless clearly defined in particular. 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.

In addition, in describing the components of the present invention, terms such as first, second, A, B, (a), (b), #1, and #2 may be used. These terms are only for distinguishing the elements from other elements, and the essence, order, or order of the elements are not limited by the terms. When it is described that a component is “connected”, “coupled” or “connected” to another component, the component may be directly connected or connected to the other component, but another component is between each component. It should be understood that elements may be “connected,” “coupled,” or “connected.”

As used herein, "comprises" and/or "comprising" refers to the presence of one or more other components, steps, operations and/or elements mentioned. or addition is not excluded.

Hereinafter, some embodiments of the present invention will be described in detail with reference to the accompanying drawings.

2 is a diagram illustrating a CAN system according to an embodiment of the present invention.

As shown in FIG. 2 , a controller area network (CAN) system may include a gateway 100 and a plurality of sub-networks 210 , 220 , 230 , and the gateway 100 and each sub-network 210 , 220 and 230 may be connected to each other through a bus.

Each of the sub-networks 210 , 220 , and 230 may be a network corresponding to any one of a flexible data rate (FD) network, a high speed (HS) network, and the like.

The sub-networks 210 , 220 , and 230 include one or more nodes 241 to 246 , and the nodes 241 to 246 may be connected to a bus to communicate with the gateway 100 . The nodes 241 to 246 are a FRONT AREA MODULE for controlling the instrument panel, a POWER SEAT MODULE for controlling the seat, an ASSIST DOOR MODULE for controlling the passenger door, a DRIVER DOOR MODULE for controlling the driver's door, and a driver's position memory switch. may be an IMS SWITCH or the like. The nodes 241 to 246 may receive a message from the gateway 100 and operate based on the message. Although two nodes are exemplified as being included in the sub-network in FIG. 2 , a larger number of nodes may be included in the sub-network, and four or more sub-networks may be connected to the gateway 100 .

The gateway 100 is a routing device for routing data. When a message is received, the gateway 100 stores the message in a shared buffer, and checks the routing rule based on the source and destination of the message in the routing rule table. , a message is transmitted for each channel using the checked routing rule and the message stored in the shared buffer. The gateway 100 copies the message to the shared buffer only once even if there are a plurality of channels to be transmitted, and the message stored in the shared buffer is referenced and transmitted in each channel, thereby reducing the load through a minimum number of times. and minimize routing delays.

FIG. 3 is a diagram showing the configuration of a gateway described with reference to FIG. 2 .

As shown in FIG. 3 , the gateway 100 includes a receiver 110 , a shared buffer 120 , a storage 130 , a transmitter 140 and a controller 150 , and these components are hardware or It may be implemented in software or may be implemented through a combination of hardware and software.

The receiver 110 may form a communication line with the external subnetworks 210 , 220 , and 230 through CAN. The receiver 110 may be connected to each of the sub-networks 210 , 220 , and 230 through a plurality of buses like the transmitter 140 to perform communication. As another embodiment, the receiving unit 110 may share and use the bus formed by the transmitting unit 140 . The reception unit 110 includes a reception buffer 111 , and when a message is received, it may temporarily store the message in the reception buffer 111 .

The receiver 110 may receive a message having a predetermined format.

4 is a diagram illustrating a data structure of a message.

Referring to FIG. 4 , a message includes a first header, a second header, and a payload. The first header Header1 may include one or more of a remote transmission request (RTR), an identifier extension (IDE), and an identifier (ID). In addition, the second header Header2 may include one or more of a bit rate switch (BRS), an FD frame (FDF), and a data length code (DLC). The payload is an area in which actual data is recorded and may be a predetermined byte.

The shared buffer 120 is a storage area of a certain size and may temporarily store a received message. The shared buffer 120 includes a plurality of buffer areas, and each buffer area may be assigned a unique index. The received message stored in the shared buffer 120 may be referred to as a payload and transmitted to one or more buses through the transmission unit 140 . The message stored in the shared buffer 120 may be released to the control unit 150 .

The storage unit 130 is a storage means such as a memory or a disk device, and may store a routing rule table and a descriptor for each channel.

5 is a diagram illustrating a routing rule table.

Referring to FIG. 5 , the routing rule table may store different routing rules (Rule#N) according to a routing method and a network type of a transmission source and a destination. The routing rule (Rule#N) defines a header and a changed or maintained rule. For example, in FIG. 5, Rule#1 may define a detailed rule in which all of the first header, the second header, and the payload are not changed and the reception state is maintained, and Rule#2 is the first header in which the ID of the first header is reset. The detailed rule for the first header, the detailed rule for the second header in which one of the BRS and FDF of the second header is changed, and the detailed rule for the payload in which the payload is maintained may be included. As another example, Rule #3 changes one or more of the detailed rules for the first header in which four first headers are generated and a separate ID is generated for each header, and BRS, FDF, and DLC included in the second header. It may include a detailed rule for the payload that defines a detailed rule for the second header and an offset indicating the size into which the payload is divided and the order of the divided payload. The routing rule may be differently set and recorded in the routing rule table according to the type of the source network and the type of the destination network.

The descriptor is a kind of work specification referenced in order to transmit a message in the corresponding channel, and may include an index of the shared buffer 120 and routing rule identification information. That is, the descriptor stores the index of the shared buffer 120 that is the storage address of the message referenced as the payload, and the identification information of the routing rule referenced to change or maintain the payload and header. The descriptor may be used only in a single channel, and may be deleted from the storage unit 130 when transmission of a message is normally completed in the channel. A storage area in which the descriptor is stored may also be implemented in the form of a buffer. In this case, an index of the descriptor may be allocated to store the descriptor in a storage area corresponding to the index, and when transmission is completed, the index is retrieved and the descriptor is stored. The area can be released.

The controller 150 is an arithmetic processing means such as a microprocessor, and may control the overall operation of the gateway 100 . When a message is received through the receiving unit 110, the control unit 150 checks an unassigned buffer index from the buffer index pool, and transmits the received message to the area of the shared buffer 120 having the buffer index. can be saved When the storage of the reception message in the area of the shared buffer 120 is completed, the controller 150 may release the reception buffer 111 by deleting the message in the reception buffer 111 .

The control unit 150 checks the source address and the destination address in the message, identifies the type of the source network and the type of the destination network based on the addresses, and then sets one or more routing rules based on the identified network type. You can choose from the table. The control unit 150 may generate a descriptor including the identification information of the selected routing rule and the index of the shared buffer and store it in the storage unit 130 . When there are a plurality of destination addresses, the controller 150 may generate a descriptor for each channel (ie, a destination network) based on the type of the corresponding destination network and the type of the source network and store the descriptor in the storage unit 130 .

In an embodiment, the controller 150 may store the descriptor in a storage area of a corresponding channel (bus). For example, the controller 150 may store the descriptor of the first channel in the storage area 141 of the first channel and store the descriptor of the second channel in the storage area 142 of the second channel. In another embodiment, the controller 150 may store an address that can access the descriptor in the storage areas 141 , 142 , and 143 of the corresponding channel. For example, the controller 150 may store an address that can access the descriptor of the first channel in the storage area 141 of the first channel, and store the address that can access the descriptor of the second channel in the second channel. It can be stored in area 142 . The controller 150 may store the address or descriptor of the descriptor in the storage areas 141, 142, and 143 when sufficient storage space equal to or greater than the threshold value remains in the storage areas 141, 142, and 143 of the channel. have.

When descriptors or addresses are stored in the storage areas 141 , 142 , and 143 , the controller 150 may set a first number corresponding to the number of descriptors. The first number indicates the number of messages stored in the shared buffer 120 to be transmitted by reference, and may be used to release an area of the shared buffer 120 .

The control unit 150 counts the second number of times the stored message is referenced and used in the shared buffer 120 , and when the second number reaches the first number, the area of the shared buffer 120 corresponding to the buffer index can be released, and the buffer index can be registered in the index pool as a usable index. Accordingly, even if a specific buffer area of the shared buffer 120 is used in a plurality of channels, when the use is completed, the specific buffer area may be released to store other messages.

The controller 150 may detect that an error has occurred in one or more buses. The controller 150 may detect a bus error and an off by using a TEC (Transmission Error Counter) and a REC (Receive Error Counter) that are used to detect a bus error and a bus off in CAN.

When a bus error is detected, the controller 150 reduces the first number by subtracting the first number by the number of buses in which the error has occurred. When a bus-off is detected, the controller 150 may immediately release the buffer area corresponding to the index.

The transmission unit 140 may form each of the sub-networks 210 , 220 , and 230 and the buses BUS#1, BUS#2, and BUS#3. The transmission unit 140 may include storage areas 141 , 142 , and 143 for transmission for each channel (bus). For example, the transmission unit 140 includes a first storage area 141 for a first channel (bus), a second storage area 142 for a second channel (bus), and a third storage area for a third channel (bus). It may include a storage area 143 . Descriptors or descriptor addresses stored in the storage areas 141 , 142 , and 143 may be processed in a first in first out (FIFO) manner.

When the descriptor is stored in the storage areas 141 , 142 , and 143 , the transmitter 140 may check the descriptor in the storage areas 141 , 142 , 143 . As another embodiment, when the address of the descriptor is stored in the storage areas 141 , 142 , and 143 , the transmission unit 140 may identify the descriptor in the storage unit 130 based on the address. The transmitter 140 may obtain a received message with reference to the descriptor, change or maintain the received message according to a routing rule, and transmit the received message to a corresponding channel (bus). The transmitter 140 may check a buffer index in the descriptor, and may obtain a message by accessing a buffer area corresponding to the buffer index. The transmission unit 140 may transmit a transmission message including a part of the obtained message as a payload and a header prepared according to the routing rule through a corresponding channel. In this case, the transmission unit 140 includes the payload of the obtained message (received message), and generates a transmission message in which the header of the received message is changed or maintained in the original state according to the routing rule, and then the generated transmission Messages can be sent to that channel.

In one embodiment, the transmission unit 140 checks the routing rule identification information in the descriptor, checks the routing rule corresponding to the routing rule identification information in the routing rule table of the storage unit 130, and then adds to the checked routing rule. Accordingly, the transmission message may be generated by selectively changing one or more of the header and the payload of the message or maintaining the original state of the message. The transmission unit 140 transmits the changed or maintained message (ie, the transmission message) to the channel (bus) corresponding to the storage areas 141 , 142 , 143 , and receives the Ack message from the counterpart nodes 241 to 246 . Then, the Ack message may be transmitted to the controller 150 . When the Ack message is received, the transmitter 140 may delete a descriptor or an address of the descriptor stored in the corresponding storage areas 141 , 142 , and 143 .

According to this embodiment, each channel copies the message to the shared buffer 120 only once, and by allowing the message stored in the shared buffer 120 to be transmitted in each channel, not only data copying is minimized but also the message is transmitted quickly It can have the effect of being routed. In addition, according to this embodiment, the load of the gateway 100 is reduced by making a minimum copy of messages, and a buffer overflow is prevented through the shared buffer 120, thereby stably routing messages and preventing data loss. can have the effect of minimizing.

6 is a first flowchart illustrating a method of routing a message in a gateway according to another embodiment of the present invention.

Referring to FIG. 6 , the reception unit 110 may receive a message from another communication device and store it in the reception buffer 111 ( S101 ).

Next, the controller 150 may check an unassigned buffer index from the buffer index pool, and store the received message in the area of the shared buffer 120 having the buffer index (S103). Subsequently, when the storage of the received message in the area of the shared buffer 120 is completed, the control unit 150 may release the reception buffer 111 by deleting the message in the reception buffer 111 ( S105 ).

Next, the control unit 150 checks the source address and the destination address in the message, identifies the type of the source network and the type of the destination network based on the addresses, and then one or more routing rules based on the identified network type can be confirmed in the routing rule table (see FIG. 5) (S107). When there are a plurality of destination addresses (ie, a plurality of channels to be transmitted), the controller 150 may check the routing rule applied to each channel in the routing rule table.

Subsequently, the controller 150 may check whether a channel to which a message is to be transmitted is in a congested state ( S111 ), and in case of the congested state, the controller 150 may wait for a predetermined time. The controller 150 may receive the state information of each channel from the transmitter 140 and determine whether each channel is in a congestion state. As another embodiment, the controller 150 may determine the congestion state of each channel based on the number of descriptors remaining in the storage areas 141 , 142 , and 143 of each channel. For example, if more than a threshold number of descriptors are stored in the storage areas 141, 142, and 143 of a specific channel, the controller 150 may determine that the channel is in a congested state, and the storage areas 141, 142 of the specific channel , 143), if less than a threshold number of descriptors are stored, it can be determined that the channel is not congested.

In an embodiment, if the channel is not in a congested state, the controller 150 may store the descript to be referenced in the corresponding channel in the storage areas 141 , 142 , 143 of the channel ( S113 ). In another embodiment, the controller 150 may store an address that can access the descriptor in the storage area of the corresponding channel. For example, the controller 150 may store an address that can access the descriptor of the first channel in the storage areas 141 , 142 , 143 of the first channel, and generate an address that can access the descriptor of the second channel. It can be stored in the storage areas 141, 142, and 143 of the two channels.

The control unit 150 stores the address or descriptor of the descriptor in the storage areas 141, 142, and 143 when sufficient storage space equal to or greater than a threshold value remains in the storage areas 141, 142, and 143 of the channel. can When the storage space less than a threshold value does not remain in the storage areas 141, 142, and 143 of the channel (that is, when the storage space of the storage area is insufficient), the controller 150 controls the storage area 141, Until the storage space of 142 and 143 becomes equal to or greater than the threshold, the descriptor or address of the descriptor is reserved without being stored in the storage areas 141 , 142 and 143 .

When the descriptors or addresses are stored in the storage areas 141 , 142 , and 143 , the controller 150 may check the number of descriptors and set the first number so that the first number becomes the number of the descriptors ( S115 ). The first number indicates the number of messages stored in the shared buffer 120 to be transmitted by reference, and may be used to release the buffer area.

According to this embodiment, one copy of a message is made within the gateway 100 , and it is possible to not only quickly process message routing but also reduce the load on the gateway 100 .

7 is a second flowchart illustrating a method of routing a message in a gateway according to another embodiment of the present invention.

Referring to FIG. 7 , the transmission unit 140 may check the address of the descriptor or descriptor stored in the storage areas 141 , 142 , and 143 of the channel ( S201 ).

Subsequently, the transmission unit 140 accesses the buffer index included in the descriptor to obtain a received message in the area of the shared buffer 120, and changes the received message according to the routing rule or maintains the original, so that the transmitted message is transmitted. can be created (S203). When an address is stored in the storage areas 141 , 142 , and 143 , the transmission unit 140 may check the descriptor stored in the storage unit 130 based on the address. The transmitter 140 may check a buffer index in the descriptor, and may obtain a message by accessing a buffer area corresponding to the buffer index. In addition, the transmission unit 140 checks the routing rule identification information in the descriptor, and after checking the routing rule corresponding to the routing rule identification information in the storage unit 130, the header and payload of the message according to the checked routing rule. By selectively changing one or more of them or maintaining the original state of the message as it is, a transmission message may be generated.

Next, the transmitter 140 may transmit the generated transmission message to the counterpart device through the corresponding channel (bus) (S205). Next, the transmitter 140 monitors whether an Ack message indicating that the transmission message has been normally received is received from the counterpart device through the channel (bus) (S207).

Subsequently, when the Ack message is received from the counterpart device, the transmitter 140 may transmit the Ack message to the controller 150 (S209). When transmitting the Ack message, the transmitting unit 140 may transmit the index of the shared buffer included in the descriptor to the control unit 150, and the descriptor or address of the descriptor being stored in the storage areas 141, 142, and 143 of the corresponding channel. can be deleted. In addition, the control unit 150 may also delete the descriptor being stored in the storage unit 130 .

According to this embodiment, the message stored in the shared buffer 120 can be used in each channel to achieve the effect of efficiently using the storage space. In addition, according to the present embodiment, since the message is transmitted in a format supported by the corresponding channel according to the routing rule, or the original message is transmitted as it is, an effect applicable to various network environments can be exhibited.

8 is a third flowchart illustrating a method of routing a message in a gateway according to another embodiment of the present invention.

Referring to FIG. 8 , the control unit 150 checks whether an Ack message is received through the transmission unit 140 ( S301 ), and when the Ack message is received, the second number may be increased by the received Ack message. (S303). The initial value of the second number may be set to '0'. The control unit 150 may receive the index of the shared buffer 120 from the transmission unit 140 together with the Ack message.

When the second number is increased, the control unit 150 may check whether the increased second number has reached the first number (S305). When the second number reaches the first number, the control unit 150 releases the area of the shared buffer 120 corresponding to the index (S307), and retrieves the index and returns the index to a usable state in the buffer index pool. can register.

According to this embodiment, by comparing the number of times the message is used (ie, the second number) in the shared buffer with the number of times the message should be referenced (ie, the first number), the area of the shared buffer 120 can be effectively released. possible effect can be exerted.

9 is a fourth flowchart illustrating a method of routing a message in a gateway according to another embodiment of the present invention.

Referring to FIG. 9 , the controller 150 may monitor whether an error occurs in one or more buses (channels) using the transmitter 140 ( S401 ). The controller 150 may detect bus errors and errors by using a Transmission Error Counter (TEC) and a Receive Error Counter (REC) used to detect bus errors and bus offs in CAN.

When a bus error is detected, the controller 150 reduces the first number by subtracting the first number by the number of buses in which the error has occurred ( S403 ). When the first number is decreased, the controller 150 may check whether the second number reaches the reduced first number (S405). When the first number reaches the second number, the control unit 150 releases the area of the shared buffer 120 corresponding to the index (S407), retrieves the index, and restores the index to a usable state in the buffer index pool. can register.

On the other hand, the controller 150 may monitor the bus-off, and when the bus-off is detected, the area of the shared buffer corresponding to the index may be immediately released.

According to the present embodiment, in case a bus error occurs, the first number is reduced when a bus error occurs, and the area of the shared buffer is released when the first number and the second number match, so that according to the bus error It is possible to exert the effect of preventing the phenomenon that the area of the shared buffer 120 is continuously maintained.

The methods according to the embodiments of the present invention described so far may be performed by executing a computer program implemented as computer readable code. The computer program may be transmitted from the first computing device to the second computing device through a network such as the Internet and installed in the second computing device, thereby being used in the second computing device. The first computing device and the second computing device include all of a server device, a physical server belonging to a server pool for a cloud service, and a stationary computing device such as a desktop PC.

The computer program may be stored in a recording medium such as a DVD-ROM or a flash memory device.

Although the embodiments of the present invention have been described above with reference to the accompanying drawings, those of ordinary skill in the art to which the present invention pertains can realize that the present invention can be embodied in other specific forms without changing the technical spirit or essential features thereof. can understand Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive.

Claims (16)

A method performed by a gateway connected to a plurality of source networks and a plurality of destination networks to perform data routing,
storing the received message in a shared buffer shared by each destination channel;
checking a routing rule of the received message using a source network and a destination network of the received message;
generating a descriptor for each destination channel of the received message based on the checked routing rule and an index of a shared buffer in which the received message is stored; and
Transmitting a transmission message including a part of the received message stored in the shared buffer as a payload with reference to the descriptor of the destination channel and including a header prepared according to the routing rule to the destination network through the destination channel, Including the step of performing for each destination channel,
routing method. The method of claim 1,
checking a first number to which the received message should be referenced; and
checking the second number of transmitted messages by referring to the received message; and
When the second number reaches the first number, further comprising the step of releasing a region of the shared buffer corresponding to the index,
routing method. 3. The method of claim 2,
Further comprising the step of subtracting the first number by the number of destination channels in which an error has occurred by checking the state of each destination channel,
routing method. The method of claim 1,
Checking the state of each of the destination channels, further comprising the step of releasing the area of the shared buffer corresponding to the index when the destination channel in which the bus-off has occurred is detected,
routing method. The method of claim 1,
The routing rule includes one or more of a header change rule and a payload change rule, based on the type of the source network and the type of the destination network.
routing method. The method of claim 1,
The step of transmitting the transmission message to the destination network through the destination channel for each destination channel comprises:
When the destination channel is a channel connected to a destination network performing segmentation routing, dividing the received message into a predetermined number and transmitting a plurality of transmission messages including the divided one received message as a payload; containing,
routing method. The method of claim 1,
The step of generating the descriptor for each destination channel of the received message comprises:
generating a descriptor including identification information of the identified routing rule and an index of the shared buffer as a channel; and
storing the generated descriptor in a storage area of the corresponding channel;
routing method. 8. The method of claim 7,
The storing step is
storing the generated descriptor in the storage area of the channel when a storage space equal to or greater than a threshold value remains in the storage area of the channel;
routing method. The method of claim 1,
The step of generating the descriptor for each destination channel of the received message comprises:
generating a descriptor including identification information of the checked routing rule and an index of the shared buffer; and
storing an address that can access the generated descriptor in a storage area of the corresponding channel;
routing method. The method of claim 1,
The step of transmitting the transmission message to the destination network through the destination channel for each destination channel comprises:
Including the payload of the received message as the payload of the outgoing message, and maintaining or changing the header of the received message based on the routing rule to create a header of the outgoing message,
routing method. A routing device connected to a plurality of source networks and a plurality of destination networks to perform data routing, the routing device comprising:
a shared buffer shared by each destination channel and storing incoming messages;
The routing rule of the received message is checked using the source network and the destination network of the received message, and a descriptor for generating the transmitted message is generated based on the checked routing rule and the index of the shared buffer in which the received message is stored. a control unit generating each destination channel of a received message; and
Each destination network and a plurality of destination channels are formed, the received message is identified in the area of the shared buffer corresponding to the index with reference to the descriptor, and at least one of a header and a payload of the received message is the routing A transmission unit configured to transmit a transmission message generated by changing according to a rule to a destination network through the destination channel, for each destination channel,
routing device. 12. The method of claim 11,
The control unit is
After confirming the first number to which the received message is to be referenced, and confirming the second number of which the received message is referenced and transmitted as a transmission message, when the second number reaches the first number, the index corresponding to the to release an area of the shared buffer,
routing device. 13. The method of claim 12,
The control unit is
Checking the state of each destination channel and subtracting the first number by the number of destination channels in which an error has occurred,
routing device. 12. The method of claim 11,
The transmission unit,
When a specific destination channel is a channel connected to a destination network for performing segmentation routing, the received message is divided into a predetermined number, and a plurality of transmitted messages including one of the divided received messages as a payload are divided into the specific destination. transmitted to the channel,
routing device. 12. The method of claim 11,
The control unit generates a descriptor including the identified identification information of the routing rule and the index of the shared buffer, and stores the generated descriptor in a storage area of the corresponding destination channel,
The transmitting unit transmits the transmission message via a corresponding destination channel with reference to a descriptor stored in a storage area of the destination channel.
routing device. 12. The method of claim 11,
The control unit is
generating a descriptor including the identified identification information of the routing rule and the index of the shared buffer, and storing an address that can access the created descriptor in a storage area of the corresponding destination channel;
The transmission unit,
After obtaining the descriptor based on the address stored in the storage area of the destination channel, the transmission message is transmitted through the corresponding destination channel with reference to the obtained descriptor,
routing device.

Images