SpaceWire Protocol ID: What Does It Means To You?

Rakow, Glenn; Schnurr, R.; Parkes, Steve

doi:10.1109/aero.2006.1655950

Cited by 3 publications

(3 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The broadcast service and routing protocol described in this paper are designed to be entirely compatible with the SpaceWire standard. Although last year we presented a packet encapsulation service [2] to provide a mechanism for identifying packet application or stack association, we have chosen to instead implement the encapsulation service more recently introduced by the SpaceWire Working Group [6].…”

Section: Automatic Configuration Of Spacewirementioning

confidence: 99%

See 1 more Smart Citation

A Link-Layer Broadcast Service for SpaceWire Networks

Roberts

Dykes

Klar

et al. 2007

2007 IEEE Aerospace Conference

View full text Add to dashboard Cite

SpaceWire, a recent ESA standard, is gaining popularity because of its simple circuitry, low power consumption, and high-link speed. However network management on SpaceWire networks is hampered by the lack of a link-layer broadcast mechanism which is required for services such as the Address Resolution Protocol (ARP) and the Dynamic Host Configuration Protocol (DHCP). Currently, address resolution and host IP assignments require manual configuration. This paper describes a linklayer broadcast service and encapsulation service for SpaceWire that is implemented in the host node software drivers and requires no change to routers or host node interface hardware. We believe this work will help move SpaceWire towards a future of Plug And Play networks, decreasing the cost and time required to develop and integrate space systems. 12

show abstract

Section: Automatic Configuration Of Spacewirementioning

confidence: 99%

“…A recently proposed addition to the SpaceWire standard is the definition of a protocol identifier [6]. The protocol identifier (PID) indicates the network stack or application process on the destination node.…”

Section: Figure 2 Spacewire Message Formatmentioning

confidence: 99%

A Link-Layer Broadcast Service for SpaceWire Networks

Roberts

Dykes

Klar

et al. 2007

2007 IEEE Aerospace Conference

View full text Add to dashboard Cite

show abstract

“…This work has resulted in the development of a protocol that will perform the lower level functions of network mapping and Change Of Status (COS) indication required by Plug 'n' Play over SpaceWire. This work will be presented to the SpaceWire working group for standardization under European Cooperation for Space Standardization (ECSS) and to obtain a permanent Protocol ID [2]. The portion of the Plug 'n' Play protocol that will be described in this paper is how the Host(s) of a SpaceWire network map the network and detect additions and deletions of devices on a SpaceWire network.…”

mentioning

confidence: 99%

Space Wire Plug `n' Play

Rakow

McGuirk

Kimmery

et al. 2007

2007 IEEE Aerospace Conference

View full text Add to dashboard Cite

The ability to rapidly deploy inexpensive satellites to meet tactical goals has become an important goal for military space systems. In fact, Operationally Responsive Space (ORS) has been in the spotlight at the highest levels. The Office of the Secretary of Defense (OSD) has identified that the critical next step is developing the bus standards and modular interfaces. Historically, satellite components have been constructed based on bus standards and standardized interfaces. However, this has not been done to a degree, which would allow the rapid deployment of a satellite [3]. Advancements in plug-andplay (PnP) technologies for terrestrial applications can serve as a baseline model for a PnP approach for satellite applications. Since SpaceWire (SpW) has become a de facto standard for satellite high-speed (>200Mbp) on-board communications, it has become important for SpW to adapt to this Plug and Play (PnP) environment. Because SpW is simply a bulk transport protocol and lacks built-in PnP features, several changes are required to facilitate PnP with SpW. The first is for Host(s) to figure out what the network looks like, i.e., how pieces of the network, routers and nodes, are connected together; network mapping, and to receive notice of changes to the network. The second is for the components connected to the network to be understood so that they can communicate. The first element, network topology mapping & change of status indication, is being defined (topic of this paper).The second element describing how components are to communicate has been defined by ARFL with the electronic data sheets known as XTEDS. The first element, network mapping, is recent activities performed by Air Force Research Lab (ARFL), Naval Research Lab (NRL), NASA and US industry (Honeywell, Clearwater, FL, and others). This work has resulted in the development of a protocol that will perform the lower level functions of network mapping and Change Of Status (COS) indication required by Plug 'n' Play over SpaceWire. This work will be presented to the SpaceWire working group for standardization under European Cooperation for Space Standardization (ECSS) and to obtain a permanent Protocol ID [2]. The portion of the Plug 'n' Play protocol that will be described in this paper is how the Host(s) of a SpaceWire network map the network and detect additions and deletions of devices on a SpaceWire network. 12

show abstract

SMC: A Shared Memory Based SpaceWire Controller Solution

Chen

Mao

et al. 2013

2013 12th IEEE International Conference on Trust, Security and Privacy in Computing and Communications

View full text Add to dashboard Cite

SpaceWire Protocol ID: What Does It Means To You?

Cited by 3 publications

References 0 publications

A Link-Layer Broadcast Service for SpaceWire Networks

A Link-Layer Broadcast Service for SpaceWire Networks

Space Wire Plug `n' Play

SMC: A Shared Memory Based SpaceWire Controller Solution

Contact Info

Product

Resources

About