Method for managing path failures of OSEK networks

• US 9,323,629 B2
• Filed: 05/04/2012
• Issued: 04/26/2016
• Est. Priority Date: 05/11/2011
• Status: Active Grant

• Current Assignee: SungKyunKwan University's Research & Business Foundation (SungKyunKwan University)
• Original Assignee: SungKyunKwan University's Research & Business Foundation (SungKyunKwan University)
• Inventors: Jeon, Jae Wook, Jung, Sung Suk, Jeong, Ho Young, Kim, Jin Ho
• Primary Examiner(s): Bonzo, Bryce
• Assistant Examiner(s): Mehrmanesh, Elmira
• Application Number:
  US14/116,220
• Publication Number:
  US 20140143589A1
• Time in Patent Office: 1,453 Days
• Field of Search: 714/4.2
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2033 switching over of hardware resources
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

Disclosed herein is a method of managing the path of an OSEK network. The method of managing the path of an OSEK network includes step S1 at which a message is transferred along nodes of the OSEK network; step S2 at which a failed node at which a network failure has occurred is detected while the message is being transferred at step S1; step S3 at which the failed node of step S2 is eliminated from the overall network; and step S4 at which the message is transferred from a source node that has transferred the message to the failed node of step S2 to a target node to which the failed node will transfer the message by connecting the source node with the target node.

Claims

1. A method of managing a path of an OSEK network, comprising:

step S1 at which a message is transferred along nodes of the OSEK network;

step S2 at which a failed node at which a network failure has occurred is detected while the message is being transferred at step S1;

step S3 at which the failed node of step S2 is eliminated from the network; and

step S4 at which the message is transferred from a source node that has transferred the message to the failed node of step S2 to a target node to which the failed node will transfer the message by establishing connection between the source node and the target node, the connection being established in response to detection of the failed node at step S2 and prior to elimination thereof at step S3.

2. The method of claim 1, wherein step S2 comprises a step at which, if a node that has received the message has not transferred the message within a reference time, the node that has received the message is detected as the failed node.

3. The method of claim 1, wherein step S3 comprises a step at which the failed node is excluded from a configuration of the network by eliminating the failed node from a node ID table that manages nodes of the network.

4. The method of claim 1, further comprising step S5 of detecting whether a network failure has occurred at the target node of step S4, and, if a network failure is detected at the target node, connecting the source node with a second target node to which the target node will transfer the message, thereby transferring the message from the source node to the second target node.

5. The method of claim 1, further comprising step S6 of, if the failed node has recovered from the network failure, connecting the source node with the failed node, and connecting the failed node with the target node so as to recover the failed node and transfer the message from the source node through the failed node to the target node.

6. A method of managing a path of an OSEK network, comprising:

step “

a”

at which a ring-type message path having a sequential message transfer topology is established in an OSEK network having a bus topology;

step “

b”

at which a failed node at which a network failure has occurred is detected while the message is being transferred along the message path of step “

a”

;

step “

c”

at which the failed node detected at step “

b”

is eliminated from the message path;

step “

d”

at which a message path is reestablished by connecting a source node, comprising a node previous to the failed node, with a target node comprising a node subsequent to the failed node, the message path being reestablished through connection of the source node with the target node in response to detection of the failed node at step “

b” and

prior to elimination of the failed node at step “

c”

; and

step “

e”

at which if the failed node has recovered from the network failure, the message path is restored by connecting the source node with the failed node and connecting the failed node with the target node.

7. The method of claim 6, wherein step “

b”

comprises a step at which, if a node that has received the message has not transferred the message within a reference time, the node that has received the message is detected as the failed node.

8. The method of claim 6, wherein step “

c”

comprises a step at which the failed node is excluded from a configuration of the network by eliminating the failed node from a node ID table that manages nodes of the network.

9. The method of claim 6, wherein steps “

b”

to “

d”

are repeated while the message is being transferred along the message path.

10. The method of claim 6, wherein step “

e”

comprises a step of, in order to detect whether the failed node has recovered from the failure, determining whether a message has been transferred to the failed node by transferring the message to the failed node every reference time.