US20090046709A1 - Common protocol and routing scheme for space data processing networks - Google Patents
Common protocol and routing scheme for space data processing networks Download PDFInfo
- Publication number
- US20090046709A1 US20090046709A1 US11/838,013 US83801307A US2009046709A1 US 20090046709 A1 US20090046709 A1 US 20090046709A1 US 83801307 A US83801307 A US 83801307A US 2009046709 A1 US2009046709 A1 US 2009046709A1
- Authority
- US
- United States
- Prior art keywords
- endpoint
- flexible
- level
- network
- layer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/382—Information transfer, e.g. on bus using universal interface adapter
- G06F13/385—Information transfer, e.g. on bus using universal interface adapter for adaptation of a particular data processing system to different peripheral devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
Definitions
- each data processing architecture is highly specialized and often relies upon a separate system interconnect technology. Since each customer has different system-level performance requirements, each system interconnect design starts from scratch. There is high risk associated with adopting new technology for each and every mission, and network technology is vulnerable to obsolescence since support for a given protocol may die out, leaving no path to higher performance as technology scales. Furthermore, only one protocol type may run over each physical network fabric, implying that complex space systems often require separate physical networks for separate functions such as data traffic, control, and management. The requirement of separate physical networks for each function further increases system complexity, size, weight, and power.
- a method of communicatively coupling network elements supporting multiple network protocol types comprises receiving input having multiple network protocol types from an upper-level of the protocol stack at an endpoint-flexible-interface layer in a network endpoint, mapping the input between the upper-level of a protocol stack and a common-lower-level in the protocol stack at the endpoint-flexible-interface layer, and implementing the common-lower-level protocol layer to interface the multiple network protocol types to the physical layer, so that at least two endpoints of a network are communicatively coupled.
- FIG. 1 is a block diagram of one embodiment of protocol stacks in communicatively coupled network endpoints in accordance with the present invention.
- FIG. 3 is a block diagram of one embodiment of an endpoint protocol stack in accordance with the present invention.
- FIG. 4 is a block diagram of one embodiment of a switch protocol stack in accordance with the present invention.
- FIG. 6 is a flow diagram of one embodiment of a method to implement a common-lower-level protocol layer in a switch protocol stack in accordance with the present invention.
- FIG. 7 is a flow diagram of one embodiment of a method to implement a common-lower-level protocol layer in an endpoint protocol stack in accordance with the present invention.
- FIG. 1 is a block diagram of one embodiment of protocol stacks 100 and 200 in respective communicatively coupled network endpoints 10 and 20 in accordance with the present invention.
- the network endpoints 10 and 20 are also referred to herein as “endpoints 10 and 20 .”
- a data processing architecture for space applications is shown in a space processing system 40 housed in a spacecraft vehicle 50 .
- the space processing system 40 is referred to herein as “network 40 .”
- the space processing system 40 includes a plurality of network elements 10 and 20 , also referred to herein as “first endpoint 10 and second endpoint 20 .”
- the first endpoint 10 and second endpoint 20 are communicatively coupled to each other via the respective physical interfaces 140 and 240 of the physical layer.
- the physical interfaces 140 and 240 comprise a plurality of physical interconnections for receiving and/or transmitting inputs having a respective plurality of protocols.
- the terms “input” and “inputs” are used to represent datum, data, signals, and/or information indicative of data and/or signals that are received at layers of the protocol stacks and that are sent from the layers of the protocol stack.
- the term input generically represents input signals and output signals.
- a management processor 190 manages the network elements 10 and 20 in the space processing system 40 .
- the management processor 190 is communicatively coupled to the first endpoint 10 and the second endpoint 20 via the respective physical interfaces 140 and 240 in order to manage them.
- the management processor 190 is one of the endpoints in the space processing system 40 .
- the protocol stacks 100 and 200 in the respective network endpoints 10 and 20 each include a plurality of lower-level interconnect protocols 330 (also referred to herein as “common-lower-level protocol layer 330 ”), a plurality of upper-level network protocols 310 (also referred to herein as upper-level 310 of a network protocol stack), and a flexible interface layer 320 that lies between the plurality of lower-level interconnect protocols and the plurality of upper-level network protocols.
- Each upper-level network protocol is associated with a respective type of data traffic. As shown in FIG.
- the protocol stack 100 of the first endpoint 10 includes the upper-level network protocol layer (ULNPL) 110 , such as an application layer, in the upper-level 310 of the network protocol stack 100 , the endpoint-flexible-interface layer (Endpoint-Flexible IL) 120 in the flexible interface layer 320 , and the low-level protocol 130 in the common-lower-level protocol layer 330 .
- the protocol stack 200 of the second endpoint 20 includes the upper-level network protocol layer 210 in the upper-level 310 of the network protocol stack 200 , the endpoint-flexible-interface layer 220 in the flexible interface layer 320 , and the low-level protocol 230 in the common-lower-level protocol layer 330 .
- the low-level protocol 130 is a low-level serial protocol 130 .
- the lower-level interconnect protocols such as low-level protocols 130 and 230 , are common to each of the plurality of network elements in the space processing system 40 .
- the low-level protocols 130 and 230 include the same protocols.
- the common-lower-level protocol layer 330 provides the platform on which the plurality of upper-level network protocols co-exist.
- the flexible interface layer maps the plurality of upper level protocols in the flexible interface layer 320 to an associated one of the plurality of lower-level interconnect protocols in the common-lower-level protocol layer 330 of a network element, such as first and second endpoints 10 and 20 .
- the lower-level protocols are independent of the physical transport medium and the upper-layer protocols.
- all the network elements are network endpoints.
- the network elements in the space processing system 40 comprise a tightly coupled embedded system.
- the network elements are in a processing system that is not a space processing system in a spacecraft vehicle 50 .
- the network elements comprise a tightly coupled embedded system that is not a space processing system.
- FIGS. 2A and 2B are block diagrams of embodiments of protocol stacks communicatively coupling endpoints and switches in accordance with the present invention.
- FIG. 2A is a block diagram of one embodiment of protocol stacks 100 and 200 in respective network endpoints 10 and 20 communicatively coupled via a protocol stack 300 in a switch 30 in accordance with the present invention.
- a first portion of the network elements represented generally by the numeral 105 include network endpoints, such as network endpoints 10 and 20 , which each have an endpoint-flexible-interface layer 120 and 220 , respectively, in the flexible interface layer 321 .
- a second portion of the network elements represented generally by the numeral 106 includes switches, such as switch 30 .
- Each switch 30 has a flexible-routing layer (Flexible RL) 160 in the flexible interface layer 321 .
- the network elements 10 and 20 and the switch 30 are in a space processing system in a spacecraft vehicle 50 .
- the management processor 190 manages the network elements, such as network endpoints 10 and 20 and the switch 30 .
- the management processor 190 is communicatively coupled to the physical interfaces 140 , 180 , and 240 of the first endpoint 10 , the switch 30 , and the second endpoint 20 in order to manage them.
- the management processor 190 is communicatively coupled to the physical interface 180 of the switch 30 , and the management processor 190 indirectly manages the first endpoint 10 and the second endpoint 20 via the switch 30 .
- the protocol stack 300 of the switch 30 includes the flexible routing layer 160 in the flexible interface layer 321 and the low-level protocol 170 in the common-lower-level protocol layer 331 .
- the protocol stacks 100 and 200 in the respective network endpoints 10 and 20 are as described above with reference to FIG. 1 .
- the protocol stacks 100 and 200 of the respective first endpoint 10 and second endpoint 20 include the endpoint-flexible-interface layers 120 and 220 in the flexible interface layer 321 and the low-level protocol 130 and 230 in the common-lower-level protocol layer 331 .
- the low-level protocols 130 and 230 have at least one protocol in common with the low-level protocols 170 in the switch 30 , however low-level protocols 130 and 230 do not need to have any protocols in common with each other.
- the common-lower-level protocol layer 331 provides the platform on which the plurality of upper-level network protocols co-exist. In one implementation of this embodiment, a single standard lower-level protocol is run on the common-lower-level protocol layer of each protocol stack when the system is powered-on.
- the flexible routing layer 160 in the switch 30 routes the input from the first endpoint 10 to the second endpoint 20 .
- the flexible routing layer 160 in the switch 30 maps the received input to the second endpoint and, based on the mapping, the switch 30 sends the input via the physical interface 180 .
- the physical interface 180 comprises at least one physical interconnection for receiving and/or transmitting inputs in a respective plurality of protocols. In one implementation of this embodiment, the same physical interconnection is used for multiple upper-level protocols. In another implementation of this embodiment, the same physical interconnections are also used for some lower-level protocols. In yet another implementation of this embodiment, some lower-level protocols use different physical interconnections from the other lower-level protocols.
- FIG. 2B is a block diagram of one embodiment of protocol stack 100 in respective network endpoint 10 communicatively coupled to a second switch 32 via a protocol stack 300 in a first switch 30 in accordance with the present invention.
- FIG. 2B differs from FIG. 2A in that the endpoint 10 is communicatively coupled to a second switch 32 via the switch 30 , also referred to as first switch 30 .
- the second switch 32 is similar in structure to the first switch 30 described above with reference to FIG. 2A .
- the low-level protocol 172 in the common-lower-level protocol layer 331 of the second switch 32 is similar to the low-level protocol 170 in the common-lower-level protocol layer 331 of the first switch 30 .
- the flexible-routing layer 162 in the second switch 32 is similar to the flexible-routing layer 160 in the first switch 30 .
- the input sent to the second switch 32 is sent to yet another network element, such as a third switch or a second endpoint.
- the input sent to the second switch 32 is stored or implemented at the second switch 32 and is not sent to any other network element.
- the management processor 190 manages the network elements, such as network endpoint 10 and the switches 30 and 32 .
- the management processor 190 is communicatively coupled to the physical interfaces 140 , 180 , and 182 of the respective endpoint 10 , the first switch 30 , and the second switch 32 in order to directly manage the endpoint 10 , the first switch 30 , and the second switch 32 .
- the management processor 190 is communicatively coupled to the physical interface 180 of the first switch 30 , and the management processor 190 indirectly manages the endpoint 10 and the second switch 32 via the first switch 30 .
- two switches are communicatively coupled to each other via a third switch.
- FIG. 3 is a block diagram of one embodiment of an endpoint protocol stack 101 in accordance with the present invention.
- the physical interface is an electrical interface 141 .
- the upper level 310 of the protocol stack includes applications using commercially available network protocols RapidIO 111 , Gigibit Ethernet (GigE) 112 , SpaceWire 113 , and InfiniBand Architecture (IBA) 114 .
- the common-lower-level protocol layer 331 of FIG. 3 includes commercially available protocols including Interlaken 131 and System Packet Interface-Scalable (SPI-S) 132 .
- SPI-S System Packet Interface-Scalable
- FIG. 4 is a block diagram of one embodiment of a switch protocol stack 301 in accordance with the present invention.
- the physical interface is an electrical interface 181 .
- the common-lower-level protocol layer 331 of FIG. 3 includes commercially available protocols including Interlaken 131 and SPI-S 132 so the switch protocol stack 301 is compatible with the endpoint protocol stack 101 as shown in FIG. 3 .
- FIG. 5 is a flow diagram of one embodiment of a method 500 to communicatively couple network elements supporting multiple network protocol types.
- the method 500 is described with reference to the exemplary protocol stacks 100 , 200 , and 300 of FIGS. 1 and 2 although it is to be understood that method 500 can be implemented using other embodiments of the communicatively coupled protocol stacks as is understandable by one skilled in the art who reads this document.
- a network endpoint receives input having multiple network protocol types from an upper-level of the protocol stack at an endpoint-flexible-interface layer in the network endpoint.
- input having multiple network protocol types includes one or more inputs having multiple network protocol types.
- an endpoint-flexible-interface layer 120 in the network endpoint 10 receives input having multiple network protocol types from an upper-level network protocol layer 110 of the protocol stack 100 .
- the network endpoint 10 receives input from applications that support RapidIO 111 , Gigibit Ethernet (GigE) 112 , SpaceWire 113 , and InfiniBand Architecture (IBA) 114 ( FIG. 3 ).
- RapidIO 111 Gigibit Ethernet
- IBA InfiniBand Architecture
- the common-lower-level protocol layer 331 is implemented to interface the multiple network protocol types to the physical interface 140 of the first network endpoint 10 so that the first network endpoint 10 is communicatively coupled to the second network endpoint 20 .
- the input received from the endpoint-flexible-interface layer is sent from the network element via the first physical interface.
- the input received from the endpoint-flexible-interface layer 120 is sent from the first network element 10 via the physical interface 140 .
- the management processor 190 of FIG. 1 or 2 sends instructions to communicatively couple the first endpoint 10 to the second endpoint 20 .
- the management processor 190 knows if the network endpoint is communicatively coupled to a switch. If the network endpoint is communicatively coupled to a switch, the flow proceeds to block 512 .
- the input sent from the first endpoint is received at the physical interface of the switch in the physical layer. In one implementation of this embodiment, the input sent from the first endpoint 100 is received at the physical interface 180 of the switch 30 ( FIG. 2A ).
- the flow of method 500 is directed to block 602 of method 600 in FIG. 6 .
- the flow proceeds to block 516 from block 510 .
- the input sent from the first endpoint flexible interface layer is received at a second physical interface in the physical layer of the second endpoint.
- the input sent from the first endpoint flexible interface layer 120 via the physical interface 140 is received at a second physical interface 240 of the second endpoint 20 ( FIG. 1 ).
- the flow of method 500 is directed to block 702 of method 700 in FIG. 7 .
- the protocol stack in the switch is the protocol stack shown in FIG. 4 .
- FIG. 6 is a flow diagram of one embodiment of a method 600 to implement a common-lower-level protocol layer in a switch protocol stack in accordance with the present invention.
- Method 600 is implemented when the first endpoint is communicatively coupled to the switch and after input is received at the switch from the first endpoint.
- the method 600 is described with reference to the exemplary protocol stacks 100 , 200 , and 300 of FIG. 2A , although it is to be understood that method 600 can be implemented using other embodiments of the communicatively coupled network endpoints and switches as is understandable by one skilled in the art who reads this document.
- the switch receives input from the physical interface at the common-lower-level protocol layer.
- the switch 30 (also referred to herein as first switch 30 ) receives input from the physical interface 180 at the low-level protocol 170 of the common-lower-level protocol layer 331 .
- the switch implements the routing requirements and functionality of the protocol of the received input at the flexible routing layer.
- the first switch 30 implements the routing requirements and functionality of the protocol of the received input at the flexible routing layer 160 .
- the switch maps the received input to another network element, such as a second endpoint or a second switch, at a flexible-routing layer of the switch.
- the first switch 30 maps the received input to a second endpoint 20 at a flexible-routing layer 160 of the flexible interface layer 321 .
- the first switch 30 maps the received input to a second switch 32 at a flexible-routing layer 160 of the flexible interface layer 321 .
- the switch routes the input via the lower-level of the protocol stack based on the mapping at the flexible-routing layer by sending the input from a physical interface of the switch.
- the first switch 30 routes the input via the low-level protocol 170 in the common-lower-level protocol layer 331 based on the mapping at the flexible-routing layer 160 and sends the input from a physical interface 180 of the first switch 30 .
- the input is routed to the second endpoint 20 .
- the input is routed to the second switch 32 . It is to be appreciated that the switch can route input received from the second endpoint 20 (or the second switch 32 as shown in FIG. 2B ) to the first endpoint 10 , since communication between the network elements is bidirectional. Thus, in other embodiments, the functionality of the first endpoint and the second endpoint are switched.
- the second endpoint receives the input sent from the switch at a second physical interface.
- the second endpoint 20 receives the input sent from the first switch 30 at a second physical interface 240 .
- the flow proceeds to block 702 of method 700 in FIG. 7 .
- FIG. 7 is a flow diagram of one embodiment of a method 700 to implement a common-lower-level protocol layer 331 in an endpoint protocol stack 200 accordance with the present invention.
- Method 700 is implemented when input is received at the second endpoint from either a communicatively coupled first endpoint or a communicatively coupled switch in a system, such as space processing system 40 ( FIG. 1 ).
- the method 700 is described with reference to the exemplary protocol stacks 100 , 200 , and 300 of FIGS. 1 and 2A although it is to be understood that method 700 can be implemented using other embodiments of the communicatively coupled protocol stacks as is understandable by one skilled in the art who reads this document.
- the second endpoint implements the protocol associated with the received input at the common-lower-level protocol.
- the second endpoint has received the input either directly from the first endpoint (see block 516 of method 500 in FIG. 5 ) or indirectly from the first endpoint via the switch (see block 610 of method 600 in FIG. 6 ).
- the second endpoint 20 implements the protocol associated with the received input at the low-level protocol 230 of the common-lower-level protocol 331 .
- the second endpoint maps the received input to an upper-level network protocol layer at a second endpoint-flexible-interface layer.
- An implementation of methods 500 , 600 and/or 700 provides a method of sending and/or receiving a mixture of upper-level protocol types from at least one endpoint in the network. Additionally, an implementation of methods 500 , 600 and/or 700 provides a method of sending and/or receiving a mixture of upper-level protocol types from at least one switch in the network.
- a “sending and/or receiving a mixture of upper-level protocol types” includes sending and/or receiving different types of upper-level protocols in a relatively short time frame.
- a network element in an exemplary network having the architecture described in this document can send data in RapidIO format followed by data in SpaceWire format, followed by data in Gigibit Ethernet format, followed by data in SpaceWire format. Effectively, multiple protocol types can run nearly simultaneously over the flexible network using a single interconnect for sending and receiving data, control signals and management signals.
Abstract
Description
- This application is related to U.S. patent application Ser. No. ______ (Attorney Docket No. H0015888-5802) having a title of “VIRTUAL NETWORK ARCHITECTURE FOR SPACE DATA PROCESSING” (also referred to here as the “H0015888-5802 Application”).
- Currently, as new data processing architectures are developed for space applications, each data processing architecture is highly specialized and often relies upon a separate system interconnect technology. Since each customer has different system-level performance requirements, each system interconnect design starts from scratch. There is high risk associated with adopting new technology for each and every mission, and network technology is vulnerable to obsolescence since support for a given protocol may die out, leaving no path to higher performance as technology scales. Furthermore, only one protocol type may run over each physical network fabric, implying that complex space systems often require separate physical networks for separate functions such as data traffic, control, and management. The requirement of separate physical networks for each function further increases system complexity, size, weight, and power.
- In a first aspect, a method of communicatively coupling network elements supporting multiple network protocol types comprises receiving input having multiple network protocol types from an upper-level of the protocol stack at an endpoint-flexible-interface layer in a network endpoint, mapping the input between the upper-level of a protocol stack and a common-lower-level in the protocol stack at the endpoint-flexible-interface layer, and implementing the common-lower-level protocol layer to interface the multiple network protocol types to the physical layer, so that at least two endpoints of a network are communicatively coupled.
-
FIG. 1 is a block diagram of one embodiment of protocol stacks in communicatively coupled network endpoints in accordance with the present invention. -
FIGS. 2A and 2B are block diagrams of embodiments of protocol stacks communicatively coupling endpoints and switches in accordance with the present invention. -
FIG. 3 is a block diagram of one embodiment of an endpoint protocol stack in accordance with the present invention. -
FIG. 4 is a block diagram of one embodiment of a switch protocol stack in accordance with the present invention. -
FIG. 5 is a flow diagram of one embodiment of a method to communicatively couple network elements supporting multiple network protocol types. -
FIG. 6 is a flow diagram of one embodiment of a method to implement a common-lower-level protocol layer in a switch protocol stack in accordance with the present invention. -
FIG. 7 is a flow diagram of one embodiment of a method to implement a common-lower-level protocol layer in an endpoint protocol stack in accordance with the present invention. - In accordance with common practice, the various described features are not drawn to scale but are drawn to emphasize features relevant to the present invention. Reference characters denote like elements throughout figures and text.
- In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific illustrative embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical and electrical changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense.
-
FIG. 1 is a block diagram of one embodiment of protocol stacks 100 and 200 in respective communicatively couplednetwork endpoints network endpoints endpoints space processing system 40 housed in aspacecraft vehicle 50. Thespace processing system 40 is referred to herein as “network 40.” Thespace processing system 40 includes a plurality ofnetwork elements first endpoint 10 andsecond endpoint 20.” Thefirst endpoint 10 andsecond endpoint 20 are communicatively coupled to each other via the respectivephysical interfaces physical interfaces - A
management processor 190 manages thenetwork elements space processing system 40. Themanagement processor 190 is communicatively coupled to thefirst endpoint 10 and thesecond endpoint 20 via the respectivephysical interfaces management processor 190 is one of the endpoints in thespace processing system 40. - The protocol stacks 100 and 200 in the
respective network endpoints level protocol layer 330”), a plurality of upper-level network protocols 310 (also referred to herein as upper-level 310 of a network protocol stack), and aflexible interface layer 320 that lies between the plurality of lower-level interconnect protocols and the plurality of upper-level network protocols. Each upper-level network protocol is associated with a respective type of data traffic. As shown inFIG. 1 , theprotocol stack 100 of thefirst endpoint 10 includes the upper-level network protocol layer (ULNPL) 110, such as an application layer, in the upper-level 310 of thenetwork protocol stack 100, the endpoint-flexible-interface layer (Endpoint-Flexible IL) 120 in theflexible interface layer 320, and the low-level protocol 130 in the common-lower-level protocol layer 330. Likewise, theprotocol stack 200 of thesecond endpoint 20 includes the upper-levelnetwork protocol layer 210 in the upper-level 310 of thenetwork protocol stack 200, the endpoint-flexible-interface layer 220 in theflexible interface layer 320, and the low-level protocol 230 in the common-lower-level protocol layer 330. In one implementation of this embodiment, the low-level protocol 130 is a low-levelserial protocol 130. - The lower-level interconnect protocols, such as low-
level protocols space processing system 40. Thus, the low-level protocols level protocol layer 330 provides the platform on which the plurality of upper-level network protocols co-exist. - The flexible interface layer maps the plurality of upper level protocols in the
flexible interface layer 320 to an associated one of the plurality of lower-level interconnect protocols in the common-lower-level protocol layer 330 of a network element, such as first andsecond endpoints FIG. 1 , all the network elements are network endpoints. In one implementation of this embodiment, the network elements in thespace processing system 40 comprise a tightly coupled embedded system. In another implementation of this embodiment, the network elements are in a processing system that is not a space processing system in aspacecraft vehicle 50. In yet another implementation of this embodiment, the network elements comprise a tightly coupled embedded system that is not a space processing system. -
FIGS. 2A and 2B are block diagrams of embodiments of protocol stacks communicatively coupling endpoints and switches in accordance with the present invention.FIG. 2A is a block diagram of one embodiment of protocol stacks 100 and 200 inrespective network endpoints protocol stack 300 in aswitch 30 in accordance with the present invention. A first portion of the network elements represented generally by thenumeral 105 include network endpoints, such asnetwork endpoints interface layer flexible interface layer 321. A second portion of the network elements represented generally by thenumeral 106 includes switches, such asswitch 30. Eachswitch 30 has a flexible-routing layer (Flexible RL) 160 in theflexible interface layer 321. In one implementation of this embodiment, thenetwork elements switch 30 are in a space processing system in aspacecraft vehicle 50. - The
management processor 190 manages the network elements, such asnetwork endpoints switch 30. Themanagement processor 190 is communicatively coupled to thephysical interfaces first endpoint 10, theswitch 30, and thesecond endpoint 20 in order to manage them. In one implementation of this embodiment, themanagement processor 190 is communicatively coupled to thephysical interface 180 of theswitch 30, and themanagement processor 190 indirectly manages thefirst endpoint 10 and thesecond endpoint 20 via theswitch 30. - As shown in
FIG. 2A , theprotocol stack 300 of theswitch 30 includes theflexible routing layer 160 in theflexible interface layer 321 and the low-level protocol 170 in the common-lower-level protocol layer 331. The protocol stacks 100 and 200 in therespective network endpoints FIG. 1 . The protocol stacks 100 and 200 of the respectivefirst endpoint 10 andsecond endpoint 20 include the endpoint-flexible-interface layers flexible interface layer 321 and the low-level protocol level protocol layer 331. - The low-
level protocols level protocols 170 in theswitch 30, however low-level protocols level protocol layer 331 provides the platform on which the plurality of upper-level network protocols co-exist. In one implementation of this embodiment, a single standard lower-level protocol is run on the common-lower-level protocol layer of each protocol stack when the system is powered-on. - The
flexible routing layer 160 in theswitch 30 routes the input from thefirst endpoint 10 to thesecond endpoint 20. Theflexible routing layer 160 in theswitch 30 maps the received input to the second endpoint and, based on the mapping, theswitch 30 sends the input via thephysical interface 180. Thephysical interface 180 comprises at least one physical interconnection for receiving and/or transmitting inputs in a respective plurality of protocols. In one implementation of this embodiment, the same physical interconnection is used for multiple upper-level protocols. In another implementation of this embodiment, the same physical interconnections are also used for some lower-level protocols. In yet another implementation of this embodiment, some lower-level protocols use different physical interconnections from the other lower-level protocols. -
FIG. 2B is a block diagram of one embodiment ofprotocol stack 100 inrespective network endpoint 10 communicatively coupled to asecond switch 32 via aprotocol stack 300 in afirst switch 30 in accordance with the present invention.FIG. 2B differs fromFIG. 2A in that theendpoint 10 is communicatively coupled to asecond switch 32 via theswitch 30, also referred to asfirst switch 30. Thesecond switch 32 is similar in structure to thefirst switch 30 described above with reference toFIG. 2A . The low-level protocol 172 in the common-lower-level protocol layer 331 of thesecond switch 32 is similar to the low-level protocol 170 in the common-lower-level protocol layer 331 of thefirst switch 30. Likewise, the flexible-routing layer 162 in thesecond switch 32 is similar to the flexible-routing layer 160 in thefirst switch 30. In one implementation of this embodiment, the input sent to thesecond switch 32 is sent to yet another network element, such as a third switch or a second endpoint. In another implementation of this embodiment, the input sent to thesecond switch 32 is stored or implemented at thesecond switch 32 and is not sent to any other network element. - The
management processor 190 manages the network elements, such asnetwork endpoint 10 and theswitches management processor 190 is communicatively coupled to thephysical interfaces respective endpoint 10, thefirst switch 30, and thesecond switch 32 in order to directly manage theendpoint 10, thefirst switch 30, and thesecond switch 32. In one implementation of this embodiment, themanagement processor 190 is communicatively coupled to thephysical interface 180 of thefirst switch 30, and themanagement processor 190 indirectly manages theendpoint 10 and thesecond switch 32 via thefirst switch 30. In one implementation of this embodiment, two switches are communicatively coupled to each other via a third switch. -
FIG. 3 is a block diagram of one embodiment of anendpoint protocol stack 101 in accordance with the present invention. The physical interface is anelectrical interface 141. Theupper level 310 of the protocol stack includes applications using commercially availablenetwork protocols RapidIO 111, Gigibit Ethernet (GigE) 112,SpaceWire 113, and InfiniBand Architecture (IBA) 114. The common-lower-level protocol layer 331 ofFIG. 3 includes commercially availableprotocols including Interlaken 131 and System Packet Interface-Scalable (SPI-S) 132. -
FIG. 4 is a block diagram of one embodiment of aswitch protocol stack 301 in accordance with the present invention. The physical interface is anelectrical interface 181. There is no level of theswitch protocol stack 301 above the flexible-routing layer 160. The common-lower-level protocol layer 331 ofFIG. 3 includes commercially availableprotocols including Interlaken 131 and SPI-S 132 so theswitch protocol stack 301 is compatible with theendpoint protocol stack 101 as shown inFIG. 3 . -
FIG. 5 is a flow diagram of one embodiment of amethod 500 to communicatively couple network elements supporting multiple network protocol types. Themethod 500 is described with reference to the exemplary protocol stacks 100, 200, and 300 ofFIGS. 1 and 2 although it is to be understood thatmethod 500 can be implemented using other embodiments of the communicatively coupled protocol stacks as is understandable by one skilled in the art who reads this document. - At
block 502, a network endpoint receives input having multiple network protocol types from an upper-level of the protocol stack at an endpoint-flexible-interface layer in the network endpoint. As defined herein, input having multiple network protocol types includes one or more inputs having multiple network protocol types. In one implementation of this embodiment, an endpoint-flexible-interface layer 120 in thenetwork endpoint 10 receives input having multiple network protocol types from an upper-levelnetwork protocol layer 110 of theprotocol stack 100. In an exemplary case, thenetwork endpoint 10 receives input from applications that supportRapidIO 111, Gigibit Ethernet (GigE) 112,SpaceWire 113, and InfiniBand Architecture (IBA) 114 (FIG. 3 ). - At
block 504, the endpoint-flexible-interface layer in the network endpoint maps the input between the upper-level of the protocol stack and a common-lower-level in the protocol stack. In one implementation of this embodiment, the endpoint-flexible-interface layer 120 in thefirst network endpoint 10 maps the input between the upper-level 310 of theprotocol stack 100 and a common-lower-level 331 (FIG. 2A ) in theprotocol stack 100. Atblock 506, the multiple network protocol types are interfaced to the physical interface in the physical layer with the common-lower-level protocol layer so that at least two endpoints of the network are communicatively coupled. In one implementation of this embodiment, the common-lower-level protocol layer 331 is implemented to interface the multiple network protocol types to thephysical interface 140 of thefirst network endpoint 10 so that thefirst network endpoint 10 is communicatively coupled to thesecond network endpoint 20. Atblock 508, the input received from the endpoint-flexible-interface layer is sent from the network element via the first physical interface. In one implementation of this embodiment, the input received from the endpoint-flexible-interface layer 120 is sent from thefirst network element 10 via thephysical interface 140. In one implementation of this embodiment, themanagement processor 190 ofFIG. 1 or 2 sends instructions to communicatively couple thefirst endpoint 10 to thesecond endpoint 20. - At
block 510, it is determined if thefirst endpoint 10 is communicatively coupled to a switch. In one implementation of this embodiment, themanagement processor 190 knows if the network endpoint is communicatively coupled to a switch. If the network endpoint is communicatively coupled to a switch, the flow proceeds to block 512. Atblock 512, the input sent from the first endpoint is received at the physical interface of the switch in the physical layer. In one implementation of this embodiment, the input sent from thefirst endpoint 100 is received at thephysical interface 180 of the switch 30 (FIG. 2A ). Atblock 514, the flow ofmethod 500 is directed to block 602 ofmethod 600 inFIG. 6 . - If the network endpoint is not communicatively coupled to a switch, it is communicatively coupled directly to another network endpoint. In this case, the flow proceeds to block 516 from
block 510. Atblock 516, the input sent from the first endpoint flexible interface layer is received at a second physical interface in the physical layer of the second endpoint. In one implementation of this embodiment, the input sent from the first endpointflexible interface layer 120 via thephysical interface 140 is received at a secondphysical interface 240 of the second endpoint 20 (FIG. 1 ). Atblock 518, the flow ofmethod 500 is directed to block 702 ofmethod 700 inFIG. 7 . In one implementation of this embodiment, the protocol stack in the switch is the protocol stack shown inFIG. 4 . -
FIG. 6 is a flow diagram of one embodiment of amethod 600 to implement a common-lower-level protocol layer in a switch protocol stack in accordance with the present invention.Method 600 is implemented when the first endpoint is communicatively coupled to the switch and after input is received at the switch from the first endpoint. Themethod 600 is described with reference to the exemplary protocol stacks 100, 200, and 300 ofFIG. 2A , although it is to be understood thatmethod 600 can be implemented using other embodiments of the communicatively coupled network endpoints and switches as is understandable by one skilled in the art who reads this document. - At
block 602, the switch receives input from the physical interface at the common-lower-level protocol layer. In one implementation of this embodiment, the switch 30 (also referred to herein as first switch 30) receives input from thephysical interface 180 at the low-level protocol 170 of the common-lower-level protocol layer 331. - At
block 604, the switch implements the routing requirements and functionality of the protocol of the received input at the flexible routing layer. In one implementation of this embodiment, thefirst switch 30 implements the routing requirements and functionality of the protocol of the received input at theflexible routing layer 160. - At
block 606, the switch maps the received input to another network element, such as a second endpoint or a second switch, at a flexible-routing layer of the switch. In one implementation of this embodiment, thefirst switch 30 maps the received input to asecond endpoint 20 at a flexible-routing layer 160 of theflexible interface layer 321. In another implementation of this embodiment, thefirst switch 30 maps the received input to asecond switch 32 at a flexible-routing layer 160 of theflexible interface layer 321. - At
block 608, the switch routes the input via the lower-level of the protocol stack based on the mapping at the flexible-routing layer by sending the input from a physical interface of the switch. In one implementation of this embodiment, thefirst switch 30 routes the input via the low-level protocol 170 in the common-lower-level protocol layer 331 based on the mapping at the flexible-routing layer 160 and sends the input from aphysical interface 180 of thefirst switch 30. In one implementation of this embodiment, the input is routed to thesecond endpoint 20. In another implementation of this embodiment, the input is routed to thesecond switch 32. It is to be appreciated that the switch can route input received from the second endpoint 20 (or thesecond switch 32 as shown inFIG. 2B ) to thefirst endpoint 10, since communication between the network elements is bidirectional. Thus, in other embodiments, the functionality of the first endpoint and the second endpoint are switched. - At
block 610, the second endpoint receives the input sent from the switch at a second physical interface. In one implementation of this embodiment, thesecond endpoint 20 receives the input sent from thefirst switch 30 at a secondphysical interface 240. Atblock 612, the flow proceeds to block 702 ofmethod 700 inFIG. 7 . -
FIG. 7 is a flow diagram of one embodiment of amethod 700 to implement a common-lower-level protocol layer 331 in anendpoint protocol stack 200 accordance with the present invention.Method 700 is implemented when input is received at the second endpoint from either a communicatively coupled first endpoint or a communicatively coupled switch in a system, such as space processing system 40 (FIG. 1 ). Themethod 700 is described with reference to the exemplary protocol stacks 100, 200, and 300 ofFIGS. 1 and 2A although it is to be understood thatmethod 700 can be implemented using other embodiments of the communicatively coupled protocol stacks as is understandable by one skilled in the art who reads this document. - At
block 702, the second endpoint implements the protocol associated with the received input at the common-lower-level protocol. The second endpoint has received the input either directly from the first endpoint (seeblock 516 ofmethod 500 inFIG. 5 ) or indirectly from the first endpoint via the switch (seeblock 610 ofmethod 600 inFIG. 6 ). In one implementation of this embodiment, thesecond endpoint 20 implements the protocol associated with the received input at the low-level protocol 230 of the common-lower-level protocol 331. Atblock 704, the second endpoint maps the received input to an upper-level network protocol layer at a second endpoint-flexible-interface layer. In one implementation of this embodiment, the second endpoint-flexible-interface layer 220 in thesecond endpoint 20 maps the received input to an upper-levelnetwork protocol layer 210. Based on the mapping at the second endpoint-flexible-interface layer, atblock 706, the second endpoint sends the received input from the second endpoint-flexible-interface layer to the upper-level network protocol layer in the second endpoint. In one implementation of this embodiment, thesecond endpoint 20 sends the received input from the second endpoint-flexible-interface layer 220 to the upper-levelnetwork protocol layer 210 in thesecond endpoint 20. In one implementation of this embodiment, the protocol stack in the second endpoint is the protocol stack shown inFIG. 3 . - An implementation of
methods methods - Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement, which is calculated to achieve the same purpose, may be substituted for the specific embodiment shown. This application is intended to cover any adaptations or variations of the present invention. Therefore, it is manifestly intended that this invention be limited only by the claims and the equivalents thereof.
Claims (20)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/838,013 US7720099B2 (en) | 2007-08-13 | 2007-08-13 | Common protocol and routing scheme for space data processing networks |
EP08161955A EP2037371B1 (en) | 2007-08-13 | 2008-08-06 | Common protocol and routing scheme for space data processing networks |
JP2008207815A JP2009049999A (en) | 2007-08-13 | 2008-08-12 | Common protocol and routing scheme for space data processing networks |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/838,013 US7720099B2 (en) | 2007-08-13 | 2007-08-13 | Common protocol and routing scheme for space data processing networks |
Publications (2)
Publication Number | Publication Date |
---|---|
US20090046709A1 true US20090046709A1 (en) | 2009-02-19 |
US7720099B2 US7720099B2 (en) | 2010-05-18 |
Family
ID=40262709
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/838,013 Active 2028-07-01 US7720099B2 (en) | 2007-08-13 | 2007-08-13 | Common protocol and routing scheme for space data processing networks |
Country Status (3)
Country | Link |
---|---|
US (1) | US7720099B2 (en) |
EP (1) | EP2037371B1 (en) |
JP (1) | JP2009049999A (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120065813A1 (en) * | 2010-09-14 | 2012-03-15 | Nguyen Quang H | System and method for command and data handling in space flight electronics |
JP6480163B2 (en) * | 2014-11-26 | 2019-03-06 | Necスペーステクノロジー株式会社 | Routing table setting device and routing table setting method |
US10320712B2 (en) | 2017-08-17 | 2019-06-11 | The Boeing Company | System and method for configuring a switch matrix on-board a vehicle based on network information |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5446736A (en) * | 1993-10-07 | 1995-08-29 | Ast Research, Inc. | Method and apparatus for connecting a node to a wireless network using a standard protocol |
US6331986B1 (en) * | 1998-04-24 | 2001-12-18 | Lucent Technologies Inc. | Method for resource allocation and routing in multi-service virtual private networks |
US6353594B1 (en) * | 1998-03-04 | 2002-03-05 | Alcatel Canada Inc. | Semi-permanent virtual paths for carrying virtual channels |
US20020097725A1 (en) * | 1998-07-27 | 2002-07-25 | Nec Corporation | Resource and protocol management for virtual private networks within multiprocessor ATM switches |
US6427173B1 (en) * | 1997-10-14 | 2002-07-30 | Alacritech, Inc. | Intelligent network interfaced device and system for accelerated communication |
US20020159456A1 (en) * | 2001-04-27 | 2002-10-31 | Foster Michael S. | Method and system for multicasting in a routing device |
US20040081203A1 (en) * | 2002-07-16 | 2004-04-29 | Enterasys Networks, Inc. | Apparatus and method for a virtual hierarchial local area network |
US6807169B2 (en) * | 2000-11-30 | 2004-10-19 | George P. Mattathil | Dynamic private network |
US20040225490A1 (en) * | 2003-05-07 | 2004-11-11 | Arteris | Device for emulating one or more integrated-circuit chips |
US20040264503A1 (en) * | 2003-06-30 | 2004-12-30 | Microsoft Corporation | Method and system for providing a virtual protocol interlayer |
US20050022143A1 (en) * | 2003-07-03 | 2005-01-27 | Cadence Design Systems, Inc. | System and method for performing design verification |
US20050220143A1 (en) * | 2004-04-05 | 2005-10-06 | Mci, Inc. | System and method for a communications access network |
US20060153070A1 (en) * | 2004-04-05 | 2006-07-13 | Delregno Nick | System and method for monitoring, controlling and provisioning a telecommunications access network |
US20060203747A1 (en) * | 2005-03-11 | 2006-09-14 | Nortel Networks Limited | Network topology systems and methods |
US20060206218A1 (en) * | 1996-08-23 | 2006-09-14 | Glanzer David A | Flexible Function Blocks |
US7124205B2 (en) * | 1997-10-14 | 2006-10-17 | Alacritech, Inc. | Network interface device that fast-path processes solicited session layer read commands |
US7197546B1 (en) * | 2000-03-07 | 2007-03-27 | Lucent Technologies Inc. | Inter-domain network management system for multi-layer networks |
US7212543B1 (en) * | 1998-10-12 | 2007-05-01 | Teliasonera Ab | Method, system and device for establishing communication between different communication networks |
US20070136495A1 (en) * | 1997-10-14 | 2007-06-14 | Boucher Laurence B | TCP/IP offload network interface device |
US7379454B2 (en) * | 2001-08-06 | 2008-05-27 | Hitachi, Ltd. | Packet routing apparatus and routing controller |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH03178245A (en) * | 1989-12-07 | 1991-08-02 | Nippon Telegr & Teleph Corp <Ntt> | Protocol processing system |
JPH0563749A (en) * | 1991-09-02 | 1993-03-12 | Hitachi Ltd | Multi-protocol communication controller |
JP3255238B2 (en) * | 1992-06-25 | 2002-02-12 | 日本電信電話株式会社 | Communication control processor |
JP2716028B2 (en) * | 1995-12-26 | 1998-02-18 | 日本電気株式会社 | Protocol converter |
JP2000035930A (en) * | 1998-07-17 | 2000-02-02 | Ricoh Co Ltd | Network system |
JP3622607B2 (en) * | 1999-11-30 | 2005-02-23 | オムロン株式会社 | Management station, node and communication method |
US6611532B1 (en) | 1999-12-07 | 2003-08-26 | Telefonaktielbolaget Lm Ericsson (Publ) | Methods and apparatus for integrating signaling system number 7 networks with networks using multi-protocol label switching |
JP2002368861A (en) * | 2001-06-06 | 2002-12-20 | Casio Comput Co Ltd | Portable telephone system |
KR100597396B1 (en) * | 2003-06-04 | 2006-07-06 | 삼성전자주식회사 | Method for transmitting and receiving multi protocol data frame, and device for the same |
FR2857114B1 (en) | 2003-07-04 | 2005-09-30 | Arteris | SYSTEM AND METHOD FOR COMMUNICATION BETWEEN MODULES |
JP2005072759A (en) * | 2003-08-21 | 2005-03-17 | Sony Corp | Transmission device and method therefor, reception device and method therefor, communication device and method therefor, and program |
JP4443880B2 (en) * | 2003-09-05 | 2010-03-31 | 株式会社エヌ・ティ・ティ・ドコモ | Node device and inter-layer control information exchange method in the device |
-
2007
- 2007-08-13 US US11/838,013 patent/US7720099B2/en active Active
-
2008
- 2008-08-06 EP EP08161955A patent/EP2037371B1/en not_active Expired - Fee Related
- 2008-08-12 JP JP2008207815A patent/JP2009049999A/en active Pending
Patent Citations (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5446736A (en) * | 1993-10-07 | 1995-08-29 | Ast Research, Inc. | Method and apparatus for connecting a node to a wireless network using a standard protocol |
US5627829A (en) * | 1993-10-07 | 1997-05-06 | Gleeson; Bryan J. | Method for reducing unnecessary traffic over a computer network |
US20060206218A1 (en) * | 1996-08-23 | 2006-09-14 | Glanzer David A | Flexible Function Blocks |
US6427173B1 (en) * | 1997-10-14 | 2002-07-30 | Alacritech, Inc. | Intelligent network interfaced device and system for accelerated communication |
US20070136495A1 (en) * | 1997-10-14 | 2007-06-14 | Boucher Laurence B | TCP/IP offload network interface device |
US7124205B2 (en) * | 1997-10-14 | 2006-10-17 | Alacritech, Inc. | Network interface device that fast-path processes solicited session layer read commands |
US6353594B1 (en) * | 1998-03-04 | 2002-03-05 | Alcatel Canada Inc. | Semi-permanent virtual paths for carrying virtual channels |
US6331986B1 (en) * | 1998-04-24 | 2001-12-18 | Lucent Technologies Inc. | Method for resource allocation and routing in multi-service virtual private networks |
US20020097725A1 (en) * | 1998-07-27 | 2002-07-25 | Nec Corporation | Resource and protocol management for virtual private networks within multiprocessor ATM switches |
US7212543B1 (en) * | 1998-10-12 | 2007-05-01 | Teliasonera Ab | Method, system and device for establishing communication between different communication networks |
US7197546B1 (en) * | 2000-03-07 | 2007-03-27 | Lucent Technologies Inc. | Inter-domain network management system for multi-layer networks |
US6807169B2 (en) * | 2000-11-30 | 2004-10-19 | George P. Mattathil | Dynamic private network |
US20020159456A1 (en) * | 2001-04-27 | 2002-10-31 | Foster Michael S. | Method and system for multicasting in a routing device |
US7379454B2 (en) * | 2001-08-06 | 2008-05-27 | Hitachi, Ltd. | Packet routing apparatus and routing controller |
US20040081203A1 (en) * | 2002-07-16 | 2004-04-29 | Enterasys Networks, Inc. | Apparatus and method for a virtual hierarchial local area network |
US20040225490A1 (en) * | 2003-05-07 | 2004-11-11 | Arteris | Device for emulating one or more integrated-circuit chips |
US20040264503A1 (en) * | 2003-06-30 | 2004-12-30 | Microsoft Corporation | Method and system for providing a virtual protocol interlayer |
US20050022143A1 (en) * | 2003-07-03 | 2005-01-27 | Cadence Design Systems, Inc. | System and method for performing design verification |
US20050220143A1 (en) * | 2004-04-05 | 2005-10-06 | Mci, Inc. | System and method for a communications access network |
US20060153070A1 (en) * | 2004-04-05 | 2006-07-13 | Delregno Nick | System and method for monitoring, controlling and provisioning a telecommunications access network |
US20060203747A1 (en) * | 2005-03-11 | 2006-09-14 | Nortel Networks Limited | Network topology systems and methods |
Also Published As
Publication number | Publication date |
---|---|
EP2037371A2 (en) | 2009-03-18 |
EP2037371B1 (en) | 2012-01-25 |
JP2009049999A (en) | 2009-03-05 |
US7720099B2 (en) | 2010-05-18 |
EP2037371A3 (en) | 2009-08-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8102843B2 (en) | Switching apparatus and method for providing shared I/O within a load-store fabric | |
US7430461B1 (en) | Networking method and network for marine navigation devices | |
CN101048981B (en) | Fibre channel transparent switch for mixed switch fabrics | |
US7219183B2 (en) | Switching apparatus and method for providing shared I/O within a load-store fabric | |
US7188209B2 (en) | Apparatus and method for sharing I/O endpoints within a load store fabric by encapsulation of domain information in transaction layer packets | |
US6735625B1 (en) | System and method for automatically determining whether a product is compatible with a physical device in a network | |
EP1143761A2 (en) | Backplane configuration without common switch fabric | |
US20060013248A1 (en) | Switching device interfaces | |
US20040151118A1 (en) | Process for controlling a switched full-duplex Ethernet type communication network | |
EP1457993A3 (en) | Multiport memory architecture, devices and systems including the same, and methods of using the same | |
US7539184B2 (en) | Reconfigurable interconnect/switch for selectably coupling network devices, media, and switch fabric | |
US7720099B2 (en) | Common protocol and routing scheme for space data processing networks | |
US6154449A (en) | Switchless network | |
EP1104967A2 (en) | Priority forwarding in a communication system | |
US8359401B2 (en) | Network switch | |
US7995463B2 (en) | Transmission device | |
JP2003501976A (en) | Method and apparatus for switching signals of multiple different transmission protocols | |
CN104639898B (en) | A kind of multifunctional service transmitting device based on Rapidio exchange networks | |
US7688869B2 (en) | Serial line circuit, an apparatus implemented with a serial line circuit, and method thereof | |
US20180013671A1 (en) | Embedded communications network of a vehicle | |
CN111385016B (en) | Switch for avionic communication system and avionic communication system | |
Cisco | Introduction to Cisco Router Configuration Cisco Internetwork Operating System Release 10.3 | |
Parkes et al. | SpaceWire: Spacecraft onboard data-handling network | |
CN109413052A (en) | Virtual machine communication system and virtual machine | |
US20080307149A1 (en) | Clustering System and Flexible Interconnection Architecture Thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: HONEYWELL INTERNATIONAL INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUENO, DAVID R.;KIMMERY, CLIFFORD E.;REEL/FRAME:019703/0664 Effective date: 20070806 Owner name: HONEYWELL INTERNATIONAL INC.,NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUENO, DAVID R.;KIMMERY, CLIFFORD E.;REEL/FRAME:019703/0664 Effective date: 20070806 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: 11.5 YR SURCHARGE- LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1556); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |