Network control system and method

• US 5,224,095 A
• Filed: 01/30/1990
• Issued: 06/29/1993
• Est. Priority Date: 01/30/1990
• Status: Expired due to Term

• Current Assignee: Johnson Controls Technology Company (Johnson Controls International plc)
• Original Assignee: Johnson Service Company
• Inventors: Rasmussen, David E., Woest, Karen L., Stark, James K.
• Primary Examiner(s): Olms, Douglas W.
• Assistant Examiner(s): Ton, Dang
• Application Number:
  US07/472,647
• Time in Patent Office: 1,246 Days
• Field of Search: 370/94.1, 370/60, 370/13, 370/16, 370/85.1, 370/85.6, 370/85.13, 370/85.15, 370/95.2, 370/96.1, 370/85.8, 370/94.3, 370/85.14, 370/100.1, 370/105.1 , 370/105.2, 370/105.4, 370/105.5, 370/106, 370/108, 340/825.52, 340/825.5, 340/825.8, 340/827, 340/826.51, 371/33, 371/32, 371/11.1, 371/20.1, 379/28, 379/93, 379/92, 375/106-114
• US Class Current: 370/401
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols
• CPC Class Codes: H04L 69/324 in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A network control system for use in a communication network controls the receipt and transmission of messages between at least a pair of nodes of the network. Messages conveyed within the network include short messages having a length less than a predetermined number of bytes and long messages having a length greater than the predetermined number of bytes. The network control system is located at least at one of the nodes and includes a connectionless network control portion for controlling the transmission and receipt of the short messages and a connection-oriented network control portion coupled to the connectionless network control portion for establishing a connection with the other node for controlling the transmission and receipt of the long messages between the pair of nodes. The connectionless portion of the system includes a transport stage which provides end-to-end reliability within the system, a network stage for establishing routing of the messages, and a data link stage for providing point-to-point reliability and other control functions such as message flow control, node resynchronization, and node suspension. The connection-oriented portion of the system includes a session stage for handling the communication of long messages greater then the predetermined number of bytes in length.

Claims

1. In a communication network including a plurality of nodes distributed on a bi-directional bus, a network control system for controlling the reception and transmission of messages at one node of said plurality of nodes, said network control system being coupled between a plurality of application modules and a transmit/receive module which is in turn coupled to said bi-directional bus, each said application module having a unique address and being arranged to originate a message with a destination address and a memory location address, said network control system comprising:

a buffer pool for storing messages to be transmitted from said one node at memory locations corresponding to said memory location addresses;

a data link stage coupled to said application modules for receiving the memory location address of a message to be transmitted from said one node; and

a timer manager including timing means for timing a time period up to a predetermined time period after said message to be transmitted is transmitted;

said transmit/receive module being coupled to said data link stage for receiving the memory location address of said message to be transmitted, coupled to said buffer pool for obtaining said message to be transmitted for transmitting said message onto said bus, and coupled to said timer manager for starting said timing means responsive to transmitting said message onto said bus.

2. A system as defined in claim 1 wherein said data link stage is coupled to said timer manager and is responsive to receiving said message memory location for conditioning said timing means.

3. A system as defined in claim 2 wherein said data link stage is arranged for receiving an acknowledgement message acknowledging receipt of said transmitted message, and wherein said data link stage is arranged to cause said timer manager to delete said timing means responsive to receiving said acknowledgement message within said predetermined time period.

4. A system as defined in claim 3 wherein said timer manager is arranged to convey a time-out message to said data link stage responsive to said timing means when said predetermined time period has expired.

5. A system as defined in claim 4 wherein said timer manager is arranged for including the memory location address of said transmitted message within said time-out message.

6. A system as defined in claim 5 wherein said data link stage is arranged to cause said transmit/receive module to retransmit said message in response to receiving said time-out message from said timer manager.

7. A system as defined in claim 6 wherein said data link stage is arranged to cause said transmit/receive module to retransmit said message up to a given number of times.

8. A system as defined in claim 7 wherein said network is arranged for asynchronous transmission and reception of messages between said nodes and wherein said data link stage includes reset means for resynchronizing said one node with any one of said other nodes when said message has been retransmitted said given number of times.

9. A system as defined in claim 8 wherein said reset means are arranged to preclude said buffer pool from clearing said messages to be transmitted from said one node during the resynchronizing of said one node with any one of said other nodes.

10. A system as defined in claim 9 wherein said reset means includes means for originating reset messages to be received by said any one of said other nodes which is not synchronized with said one node.

11. A system as defined in claim 10 wherein said reset means further include means for suspending the transmission of all messages from said one node except for said reset messages during the resynchronizing of said one node with said any one of said other nodes.

12. A system as defined in claim 11 wherein said nodes of said network are arranged to acknowledge receipt of said reset message and wherein said reset means are arranged for retransmitting said reset message a preset number of times in the absence of an acknowledgement thereto by said any one of said other nodes.

13. A system as defined in claim 12 wherein said reset means includes means for causing said messages to be transmitted by said one node to be cleared from said buffer pool after said reset message has been retransmitted said preset number of times.

14. A system as defined in claim 1 further including a session stage coupled between said application modules and said data link stage and to said buffer pool of said one node for providing a session service including dividing a long message having a length greater than a predetermined number of bytes into message parts having lengths less than said predetermined number of bytes and for conveying said message parts in sequence from said buffer pool to said transmit/receive module.

15. A system as defined in claim 14 wherein said session stage is arranged for establishing a connection with the node for which said long message is destined.

16. A system as defined in claim 15 wherein said session stage is arranged to divide said long message into said message parts after establishing said connection with the node for which said long message is destined.

17. A system as defined in claim 16 wherein said session stage includes means for originating a connect request message to be transmitted to said node for which said long message is destined for establishing said connection.

18. A system as defined in claim 17 wherein said session stage is arranged to receive a connection response from said node for which said long message is destined and wherein said session stage is arranged to commence dividing said long message into said message parts after receiving a positive connection response from said destined node.

19. A system as defined in claim 18 wherein said session stage is arranged to abort said session service responsive to the lack of receipt of said connection response within a predetermined time period after sending said connect request message.

20. A system as defined in claim 19 wherein said session stage is arranged to originate an abort message to said node for which said long message is destined.

21. A system as defined in claim 20 wherein said session stage is arranged to notify the application module which originated said long message of a failure after sending said abort message.

22. A system as defined in claim 16 wherein said session stage is arranged to received an acknowledgement message from said destined node after all said message are received by said destined node.

23. A system as defined in claim 22 wherein said session stage is arranged to originate a close request message for said destined node after receiving said acknowledgement message from said destined node.

24. A system as defined in claim 23 wherein said session stage is arranged to receive a hang-up response from said destined node in response to said close request message and wherein said session stage is arranged for terminating said connection in response to said hang-up response.

25. A system as defined in claim 14 wherein said session service also includes logical groupings of messages to be sent to a given one of said nodes.

26. A system as defined in claim 14 wherein said session stage is further arranged to assemble the message parts of a long message received at said one node.

27. A system as defined in claim 26 wherein said one node includes a plurality of storage means within said buffer pool and wherein said session stage is arranged to acquire sufficient ones of said storage means for storing said message.

28. A system as defined in claim 27 wherein said session stage is arranged to acquire said storage means responsive to the receipt of a connection request from another one of said nodes.

29. A system as defined in claim 28 wherein said session stage is arranged to convey said long message from said storage means to one of said application modules after all of said message parts are stored.

30. A system as defined in claim 29 wherein said session stage is arranged to originate an acknowledge message upon receipt of all of said message parts.

31. A system as defined in claim 1 further including broadcasting means for transmitting a broadcast message to a plurality of said nodes simultaneously.

32. A system as defined in claim 31 wherein said data link stage is arranged to convey the memory location address of said broadcast message directly to said transmit/receive module.

33. A system as defined in claim 31 wherein said broadcast message is a data message or a control message.

34. A system as defined in claim 31 wherein said timer manager is precluded from timing a time period after said broadcast message is transmitted.

35. A system as defined in claim 1 wherein said data link stage includes means for receiving from one node a message having a destination address for another node, wherein said system further includes routing means for readdressing said message with an address for another one of said nodes, and wherein said data link stage causes said transmit/receive module to retransmit said message onto said bus after said message is readdressed.

36. In a communication network including a plurality of nodes distributed on a bi-directional bus, a method for controlling the reception and transmission of messages at one node of said plurality of nodes, said one node including a plurality of application modules and a transmit/receive module which is coupled to said bi-directional bus, each said application module having a unique address and being arranged to originate a message with a destination address and a memory location address, said method comprising the steps of:

providing a buffer pool;

storing messages to be transmitted form said one node in said buffer pool at memory locations corresponding to said memory location addresses;

providing a data link stage;

conveying to said data link stage form said application modules the memory location address of a message to be transmitted from said one node;

providing a timer manager including timing means for timing a time period up to a predetermined time period;

conveying from said data link stage to said transmit/receive module the memory location address of said message to be transmitted;

causing said transmit/receive module to obtain from said buffer pool said message to be transmitted;

causing said transmit/receive module to transmit said message onto said bus; and

causing said transmit/receive module to start said timing means responsive to transmitting said message onto said bus.

37. A method as defined in claim 36 including the further step of causing said data link stage to condition said timing means after receiving said message memory location.

38. A method as defined in claim 37 including the further step of receiving at said data link stage an acknowledgement message acknowledging receipt of said transmitted message, and causing said data link stage to delete said timer manager timing means if said acknowledgement message is received by said data link stage within said predetermined timer period.

39. A method as defined in claim 38 including the further step of causing said timer manager to convey a time-out message to said data link stage when said timing means predetermined time period has expired.

40. A method as defined in claim 39 wherein said timer manager includes the memory location address of said transmitted message within said time-out message.

41. A method as defined in claim 40 wherein said data link stage causes said transmit/receive module to retransmit said message in response to receiving said timeout message from said timer manager.

42. A method as defined in claim 41 wherein said data link stage causes said transmit/receive module to retransmit said message up to a given number of times.

43. A method as defined in claim 42 wherein said network is arranged for synchronous transmission and reception of messages between said nodes and wherein said data link stage resynchronizes said one node with any one of said other nodes when said message has been retransmitted said given number of times.

44. A method as defined in claim 43 wherein said data link stage precludes said buffer pool from clearing said messages to be transmitted from said one node during the resynchronizing of said one node with any one of said other nodes.

45. A method as defined in claim 44 wherein said resynchronizing step includes originating reset messages at said data link stage to be received by said any one of said other nodes which is not synchronized with said one node.

46. A method as defined in claim 45 wherein said resynchronizing step further includes suspending at said data link stage the transmission of all messages from said one node except for said reset messages during the resynchronizing of said one node with said any one of said other nodes.

47. A method as defined in claim 46 wherein said nodes of said network are arranged to acknowledge receipt of said reset message and wherein said data link stage retransmits said reset message a preset number of times in the absence of an acknowledgement thereto by said any one of said other nodes.

48. A method as defined in claim 47 wherein said data link stage causes said messages to be transmitted by said one node to be cleared from said buffer pool after said reset message has been retransmitted said preset number of times.

49. A method as defined in claim 36 further including providing a session stage coupled between said application modules and said data link stage and to said buffer pool of said one node and executing a session step at said session stage including dividing a long message having a length greater than a predetermined number of bytes into message parts having lengths less than said predetermined number of bytes and causing said message parts to be conveyed in sequence from said buffer pool to said transmit/receive module.

50. A method as defined in claim 49 wherein said session step further includes establishing a connection with the node for which said long message is destined.

51. A method as defined in claim 50 wherein said session stage includes dividing said long message into said message parts after establishing said connection with the node for which said long message is destined.

52. A method as defined in claim 51 wherein said session step includes originating a connect request message to be transmitted to said node for which said long message is destined for establishing said connection.

53. A method as defined in claim 52 wherein said session step includes receiving a connection response from said node for which said long message is destined and thereafter dividing said long into said message parts after receiving a positive connection response from said destined node.

54. A method as defined in claim 53 wherein said session step includes aborting said session step responsive to the lack of receipt of said connection response within a predetermined time period after sending said connect request message.

55. A method as defined in claim 54 wherein said session step includes originating at said session stage an abort message to said node for which said long message is destined.

56. A method as defined in claim 55 wherein said session step includes notifying the application module which originated said long message of a failure after sending said abort message.

57. A method as defined in claim 51 wherein said session step includes receiving an acknowledgement message from said destined node after all said message parts are received by said destined node.

58. A method as defined in claim 57 wherein said session step includes originating a close request message for said destined node after receiving said acknowledgement message from said destined node.

59. A method as defined in claim 58 wherein said session step includes receiving a hang-up response from said destined node in response to said close request message and terminating said connection in response to said hang-up response.

60. A method as defined in claim 49 wherein said session step further includes logically grouping messages to be sent to a given one of said nodes.

61. A method as defined in claim 49 wherein said session step further includes assembling the message parts of a long message received at said one node.

62. A method as defined in claim 61 wherein said one node includes a plurality of storage means within said buffer pool and wherein said session step includes acquiring sufficient ones of said storage means for storing said long message.

63. A method as defined in claim 62 wherein said session step includes acquiring said storage means responsive to the receipt of a connection request from another one of said nodes.

64. A method as defined in claim 63 wherein said session step includes conveying said long message from said storage means to one of said application modules after all of said parts are stored.

65. A method as defined in claim 64 wherein said session step includes originating an acknowledge message upon receipt of all of said message parts.

66. A method as defined in claim 36 including the further step of transmitting a broadcast message to a plurality of said nodes simultaneously.

67. A method as defined in claim 66 including the step of conveying the memory storage address of said broadcast message directly to said transmit/receive module from one of said application modules.

68. A method as defined in claim 66 including the further step of precluding said timer manager from timing a time period after said broadcast message is transmitted.

69. A method as defined in claim 66 wherein said broadcast message is a data message or a control message.

70. A method as defined in claim 69 wherein said control message is a reset message.

71. A method as defined in claim 69 wherein said broadcast message is a restart message.