Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “time service”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 865 records · Page 48

Position surveillance using one active ranging satellite and time-of-arrival of a signal from an independent satellite

A satellite-aided mobile communication service was tested for position surveillance, with an automatic responder circuit connected between the vehicle receiver and transmitter, and a receiver coded for signals from another satellite. Using the ATS-6 and GOES satellites, a tone-code ranging transponder was connected between the receiver and transmitter, and a 468 MHz receiver was connected to the responder unit for passive reception of the 100 bit per second timing and data signal. Results showed lines of position derived from the active ranging through ATS-6 to be accurate to approximately 0.1 nautical mile, while the NOAA-GOES signals were accurate to about 1.6 miles. The active ranging bandwidth was 2.44 kHz, and the integration time was 0.1 second, while the limitation on accuracy was the 100 Hz bandwidth. This technique of position surveillance was concluded to be feasible and simple to operate, providing needed, good quality communications to the inland waterways industry.

Anderson, R. E.↗

QoS-aware edge AI placement and scheduling with multiple implementations in FaaS-based edge computing

Resource constraints on the computing continuum require that we make smart decisions for serving AI-based services at the network edge. AI-based services typically have multiple implementations (e.g., image classification implementations include SqueezeNet, DenseNet, and others) with varying trade-offs (e.g., latency and accuracy). The question then is how should AI-based services be placed across Function-as-a-Service (FaaS) based edge computing systems in order to maximize total Quality-of-Service (QoS). To address this question, we propose a problem that jointly aims to solve (i) edge AI service placement and (ii) request scheduling. These are done across two time-scales (one for placement and one for scheduling). Here we first cast the problem as an integer linear program. We then decompose the problem into separate placement and scheduling subproblems and prove that both are NP-hard. We then propose a novel placement algorithm that places services while considering device-to-device communication across edge clouds to offload requests to one another. Our results show that the proposed placement algorithm is able to outperform a state-of-the-art placement algorithm for AI-based services, and other baseline heuristics, with regard to maximizing total QoS. Additionally, we present a federated learning-based framework, FLIES, to predict the future incoming service requests and their QoS requirements. Our results also show that our FLIES algorithm is able to outperform a standard decentralized learning baseline for predicting incoming requests and show comparable predictive performance when compared to centralized training.

97 MATHEMATICS AND COMPUTING↗

The Design of a Flexible, Interoperable Navigation Signal for Future Lunar Missions

The LunaNet Interoperability Specification (LNIS) is a set of standards currently under development by NASA, ESA, and JAXA, which define a common, interoperable set of services and interfaces for lunar communication and navigation. The LNIS includes specifications for the GNSS-like Augmented Forward Signal (AFS). The LANS (Lunar Augmented Navigation Service) will be comprised of Multiple LunaNet Service Provider (LNSP) nodes broadcasting the AFS, such as NASA’s LCRNS (Lunar Communications Relay and Navigation Systems), ESA’s Moonlight LCNS (Lunar Communication and Navigation Services) and the Japan LNSS (Lunar Navigation Satellite System). The LANS will provide a GNSS-like capability enabling orbiting and surface users in lunar space (such as Artemis) to estimate their position, velocity and time as described in Giordano et al., (2023). Initial capabilities will focus on providing service to the lunar South pole region. The specification of AFS defines two orthogonal signal components on a single carrier, with the in-phase component (AFS-I) being a lower-chip-rate data channel tailored for applications where low SWaP is critical (e.g., IoT devices or search and rescue), and the quadrature component (AFS-Q) being a high-chip-rate data-less pilot signal for high-precision, robust lunar navigation and positioning applications. An initial description of AFS was provided in the LNIS, (2023), and initial analysis results were shown in Dafesh, et al., (2024). In this work, we provide rationale for updates to the LNIS that define key aspects of the signal including the primary spreading code designs for the data and pilot channels, and a three-tiered overlay code approach for the pilot channel that provides flexible signal acquisition alternatives, rapid time dissemination and robust frame Sync. The paper also describes a robust data sync word that is designed to enable frame Sync. for low-SWaP receivers that only use the I channel, as well as a low-density parity check code (LDPC) data message encoding design and interleaving definition. The work further describes the impact of the updated AFS design in terms of improved acquisition performance, interference resistance, navigation message capabilities and rapid absolute time dissemination for users able to access clock and ephemeris data over an external network. The cross-correlation and synchronization performance of the AFS design is also compared to potential alternatives, further providing rationale for the final signal design configuration.

LANS↗

Pre-flight risk assessment in Emergency Medical Service (EMS) helicopters

The Emergency Medical Service (EMS) industry has been the subject of several television and newspaper articles (Harvey and Jensen, 1987) which emphasized the negative aspects, (e.g., fatalities and high accident rates), rather than the life saving services performed. Until recently, the accident rate of the EMS industry has been five times as high as that of other civil helicopters. This high accident rate has been coupled with the dramatic rise in the number of programs. The industry has built from a single service at its inception in 1972, to over 180 in 1987 (Spray, 1987), to the point that 93 percent of the contiguous U.S. is now covered by some type of EMS service. These factors prompted the National Transportation Safety Board (NTSB) to study the accidents that occurred between May 11, 1978 and December 3, 1986 (NTSB, 1988). The NTSB report concluded that 'Sound pilot judgment is central to safe flight operations.' They further stated that '... factors unique to EMS helicopter operations--such as the influence of the mission itself, program competition, and EMS program management perspectives--can drastically influence pilot judgment during the EMS mission.' One of the most difficult decisions that a pilot must make is whether to accept or decline a mission. A pre-flight risk assessment system (SAFE) was developed at NASA-Ames Research Center for civil EMS operations to aid pilots in making this decision objectively. The ability of the SAFE system to predict mission risk profiles was tested at an EMS facility. The results of this field study demonstrated that the usefulness of SAFE was highly dependent on the type of mission flown. SAFE is now being modified so that it can 'learn' with each mission flown. For example, after flying a mission to a particular site, an EMS pilot would input information about this mission into the system, such as new buildings, wires, or approach procedures. Then, the next time a pilot flew a similar mission or one to the same area, this additional information would be taken into account in computing a risk assessment.

Shively, R. J.↗

The Design of a Flexible, Interoperable Navigation Signal for Future Lunar Missions

The LunaNet Interoperability Specification (LNIS) is a set of standards currently under development by NASA, ESA, and JAXA, which define a common, interoperable set of services and interfaces for lunar communication and navigation. The LNIS includes specifications for the GNSS-like Augmented Forward Signal (AFS). The LANS (Lunar Augmented Navigation Service) will be comprised of Multiple LunaNet Service Provider (LNSP) nodes broadcasting the AFS, such as NASA’s LCRNS (Lunar Communications Relay and Navigation Systems), ESA’s Moonlight LCNS (Lunar Communication and Navigation Services) and the Japan LNSS (Lunar Navigation Satellite System). The LANS will provide a GNSS-like capability enabling orbiting and surface users in lunar space (such as Artemis) to estimate their position, velocity and time as described in Giordano et al., (2023). Initial capabilities will focus on providing service to the lunar South pole region. The specification of AFS defines two orthogonal signal components on a single carrier, with the in-phase component (AFS-I) being a lower-chip-rate data channel tailored for applications where low SWaP is critical (e.g., IoT devices or search and rescue), and the quadrature component (AFS-Q) being a high-chip-rate data-less pilot signal for high-precision, robust lunar navigation and positioning applications. An initial description of AFS was provided in the LNIS, (2023), and initial analysis results were shown in Dafesh, et al., (2024). In this work, we provide rationale for updates to the LNIS that define key aspects of the signal including the primary spreading code designs for the data and pilot channels, and a three-tiered overlay code approach for the pilot channel that provides flexible signal acquisition alternatives, rapid time dissemination and robust frame Sync. The paper also describes a robust data sync word that is designed to enable frame Sync. for low-SWaP receivers that only use the I channel, as well as a low-density parity check code (LDPC) data message encoding design and interleaving definition. The work further describes the impact of the updated AFS design in terms of improved acquisition performance, interference resistance, navigation message capabilities and rapid absolute time dissemination for users able to access clock and ephemeris data over an external network. The cross-correlation and synchronization performance of the AFS design is also compared to potential alternatives, further providing rationale for the final signal design configuration.

LunaNet↗

Cascaded clocks measurement and simulation findings

This paper will examine aspects related to network synchronization distribution and the cascading of timing elements. Methods of timing distribution have become a much debated topic in standards forums and among network service providers (both domestically and internationally). Essentially these concerns focus on the need to migrate their existing network synchronization plans (and capabilities) to those required for the next generation of transport technologies (namely, the Synchronous Digital Hierarchy (SDH), Synchronous Optical Networks (SONET), and Asynchronous Transfer Mode (ATM). The particular choices for synchronization distribution network architectures are now being evaluated and are demonstrating that they can indeed have a profound effect on the overall service performance levels that will be delivered to the customer. The salient aspects of these concerns reduce to the following: (1) identifying that the devil is in the details of the timing element specifications and the distribution of timing information (i.e., small design choices can have a large performance impact); (2) developing a standardized method of performance verification that will yield unambiguous results; and (3) presentation of those results. Specifically, this will be done for two general cases: an ideal input, and a noisy input to a cascaded chain of slave clocks.

Chislow, Don↗

Information Power Grid: Distributed High-Performance Computing and Large-Scale Data Management for Science and Engineering

We use the term "Grid" to refer to distributed, high performance computing and data handling infrastructure that incorporates geographically and organizationally dispersed, heterogeneous resources that are persistent and supported. This infrastructure includes: (1) Tools for constructing collaborative, application oriented Problem Solving Environments / Frameworks (the primary user interfaces for Grids); (2) Programming environments, tools, and services providing various approaches for building applications that use aggregated computing and storage resources, and federated data sources; (3) Comprehensive and consistent set of location independent tools and services for accessing and managing dynamic collections of widely distributed resources: heterogeneous computing systems, storage systems, real-time data sources and instruments, human collaborators, and communications systems; (4) Operational infrastructure including management tools for distributed systems and distributed resources, user services, accounting and auditing, strong and location independent user authentication and authorization, and overall system security services The vision for NASA's Information Power Grid - a computing and data Grid - is that it will provide significant new capabilities to scientists and engineers by facilitating routine construction of information based problem solving environments / frameworks. Such Grids will knit together widely distributed computing, data, instrument, and human resources into just-in-time systems that can address complex and large-scale computing and data analysis problems. Examples of these problems include: (1) Coupled, multidisciplinary simulations too large for single systems (e.g., multi-component NPSS turbomachine simulation); (2) Use of widely distributed, federated data archives (e.g., simultaneous access to metrological, topological, aircraft performance, and flight path scheduling databases supporting a National Air Space Simulation systems}; (3) Coupling large-scale computing and data systems to scientific and engineering instruments (e.g., realtime interaction with experiments through real-time data analysis and interpretation presented to the experimentalist in ways that allow direct interaction with the experiment (instead of just with instrument control); (5) Highly interactive, augmented reality and virtual reality remote collaborations (e.g., Ames / Boeing Remote Help Desk providing field maintenance use of coupled video and NDI to a remote, on-line airframe structures expert who uses this data to index into detailed design databases, and returns 3D internal aircraft geometry to the field); (5) Single computational problems too large for any single system (e.g. the rotocraft reference calculation). Grids also have the potential to provide pools of resources that could be called on in extraordinary / rapid response situations (such as disaster response) because they can provide common interfaces and access mechanisms, standardized management, and uniform user authentication and authorization, for large collections of distributed resources (whether or not they normally function in concert). IPG development and deployment is addressing requirements obtained by analyzing a number of different application areas, in particular from the NASA Aero-Space Technology Enterprise. This analysis has focussed primarily on two types of users: the scientist / design engineer whose primary interest is problem solving (e.g. determining wing aerodynamic characteristics in many different operating environments), and whose primary interface to IPG will be through various sorts of problem solving frameworks. The second type of user is the tool designer: the computational scientists who convert physics and mathematics into code that can simulate the physical world. These are the two primary users of IPG, and they have rather different requirements. The results of the analysis of the needs of these two types of users provides a broad set of requirements that gives rise to a general set of required capabilities. The IPG project is intended to address all of these requirements. In some cases the required computing technology exists, and in some cases it must be researched and developed. The project is using available technology to provide a prototype set of capabilities in a persistent distributed computing testbed. Beyond this, there are required capabilities that are not immediately available, and whose development spans the range from near-term engineering development (one to two years) to much longer term R&D (three to six years). Additional information is contained in the original.

Johnston, William E.↗

Raven: An On-Orbit Relative Navigation Demonstration Using International Space Station Visiting Vehicles

Since the last Hubble Servicing Mission five years ago, the Satellite Servicing Capabilities Office (SSCO) at the NASA Goddard Space Flight Center (GSFC) has been focusing on maturing the technologies necessary to robotically service orbiting legacy assets-spacecraft not necessarily designed for in-flight service. Raven, SSCO's next orbital experiment to the International Space Station (ISS), is a real-time autonomous non-cooperative relative navigation system that will mature the estimation algorithms required for rendezvous and proximity operations for a satellite-servicing mission. Raven will fly as a hosted payload as part of the Space Test Program's STP-H5 mission, which will be mounted on an external ExPRESS Logistics Carrier (ELC) and will image the many visiting vehicles arriving and departing from the ISS as targets for observation. Raven will host multiple sensors: a visible camera with a variable field of view lens, a long-wave infrared camera, and a short-wave flash lidar. This sensor suite can be pointed via a two-axis gimbal to provide a wide field of regard to track the visiting vehicles as they make their approach. Various real-time vision processing algorithms will produce range, bearing, and six degree of freedom pose measurements that will be processed in a relative navigation filter to produce an optimal relative state estimate. In this overview paper, we will cover top-level requirements, experimental concept of operations, system design, and the status of Raven integration and test activities.

Rendezvous↗

Role of communications satellites in the fiber era

Systenm descriptions of satellite and fiber optic networks are developed for the benchmark years 1983 and 1986, and forecasts are made for the years 1990 and 1995. Based on this information, the impact of fiber optics on satellite communications in the years 1995 and 2000 is assessed. Ten services are identified which are likely to be supplied at least in part by satellite in the 1995-2000 time frame. Estimates are made of the probability of existence and the number of transponders used by these future satellite services.

Price, Kent M.↗

How Improved Forecasting Can Increase the Bulk Power System Value of Price-Responsive Electric Vehicle Managed Charging

Personal light-duty vehicle (LDV) electric vehicle managed charging (EVMC) can reduce power system costs by better aligning electric vehicle (EV) charging with locations and times of low energy cost or infrastructure use. The need to coordinate charging demand across thousands to millions of vehicles while preserving mobility service is a barrier to realizing the value of EVMC. Price-responsive dispatch mechanisms like time-of-use rates (TOU) and hourly real-time prices (RTP) are attractive compared to direct load control (DLC) because they only require one-way communications and local controls. However, increasing participation in price responsive mechanisms can induce costly-to-serve spikes in load and otherwise increase, rather than decrease, production costs. We quantify the ability of improved EVMC forecasting to sustain savings from price responsive mechanisms beyond the limit of 14% of LDVs actively participating observed in previous work. Perfect forecasting of price-responsive EV load makes TOU and RTP value-competitive with a low-error DLC formulation with up to 27% (within-week flexibility) to 45% or more (within-session flexibility) of LDVs participating in EVMC in an envisioned New England power system with 84% clean energy. Additional costs of implementing DLC should be no more than tens of dollars per vehicle-year if DLC is to be value-competitive with accurately forecast price-responsive EVMC for double-digit percentage shares of LDVs participating.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Analysis of One-Way Laser Ranging Data to LRO, Time Transfer and Clock Characterization

We processed and analyzed one-way laser ranging data from International Laser Ranging Service ground stations to NASA's Lunar Reconnaissance Orbiter (LRO), obtained from June 13, 2009 until September 30, 2014. We pair and analyze the one-way range observables from station laser fire and spacecraft laser arrival times by using nominal LRO orbit models based on the GRAIL gravity field. We apply corrections for instrument range walk, as well as for atmospheric and relativistic effects. In total we derived a tracking data volume of approximately 3000 hours featuring 64 million Full Rate and 1.5 million Normal Point observations. From a statistical analysis of the dataset we evaluate the experiment and the ground station performance. We observe a laser ranging measurement precision of 12.3 centimeters in case of the Full Rate data which surpasses the LOLA (Lunar Orbiting Laser Altimeter) timestamp precision of 15 centimeters. The averaging to Normal Point data further reduces the measurement precision to 5.6 centimeters. We characterized the LRO clock with fits throughout the mission time and estimated the rate to 6.9 times10 (sup -8), the aging to 1.6 times 10 (sup -12) per day and the change of aging to 2.3 times 10 (sup -14) per day squared over all mission phases. The fits also provide referencing of onboard time to the TDB (Barycentric Dynamical Time) time scale at a precision of 166 nanoseconds over two and 256 nanoseconds over all mission phases, representing ground to space time transfer. Furthermore we measure ground station clock differences from the fits as well as from simultaneous passes which we use for ground to ground time transfer from common view observations. We observed relative offsets ranging from 33 to 560 nanoseconds and relative rates ranging from 2 times 10 (sup -13) to 6 times 10 (sup -12) between the ground station clocks during selected mission phases. We study the results from the different methods and discuss their applicability for time transfer.

Bauer, S.↗

MaROS: Information Management Service

This software is provided by the Mars Relay Operations Service (MaROS) task to a variety of Mars projects for the purpose of coordinating communications sessions between landed spacecraft assets and orbiting spacecraft assets at Mars. The Information Management Service centralizes a set of functions previously distributed across multiple spacecraft operations teams, and as such, greatly improves visibility into the end-to-end strategic coordination process. Most of the process revolves around the scheduling of communications sessions between the spacecraft during periods of time when a landed asset on Mars is geometrically visible by an orbiting spacecraft. These relay sessions are used to transfer data both to and from the landed asset via the orbiting asset on behalf of Earth-based spacecraft operators. This software component is an application process running as a Java virtual machine. The component provides all service interfaces via a Representational State Transfer (REST) protocol over https to external clients. There are two general interaction modes with the service: upload and download of data. For data upload, the service must execute logic specific to the upload data type and trigger any applicable calculations including pass delivery latencies and overflight conflicts. For data download, the software must retrieve and correlate requested information and deliver to the requesting client. The provision of this service enables several key advancements over legacy processes and systems. For one, this service represents the first time that end-to-end relay information is correlated into a single shared repository. The software also provides the first multimission latency calculator; previous latency calculations had been performed on a mission-by-mission basis.

Allard, Daniel A.↗

A Review of Value of Solar Studies In Theory and In Practice

This brief summarizes a collection of state- and utility-commissioned value-of-solar (VoS) studies and related literature, with a focus on who commissioned the study, which value and cost categories were discussed and/or quantified, and the methods used. Our objective is to compile information on prior VoS studies to inform state regulators and other stakeholders that may pursue related studies or integrate findings into rate design. The brief is organized into three parts: 1) an introduction to distributed solar photovoltaic (DPV) compensation; 2) a review of theoretical research on VoS; and 3) a review of VoS studies. The vast majority of VoS studies have served an informational role of quantifying the net benefits of PV. Three studies were commissioned in states or utility service territories that subsequently implemented VoS tariffs in California, New York, and Austin, Texas. When applied as a tariff, VoS aims to compensate PV output as efficiently as possible by doing so at rates that reflect the marginal benefits and costs of PV through value and cost categories that may vary temporally and/or geographically. This could lead to higher compensation in locations and times where more PV output is more valuable and consequently drive adoption in those locations to provide more societal benefits. Value and cost factors can be broadly grouped into five categories: generation, transmission, distribution, other utility, and other social categories. Those conducting VoS studies must weigh various tradeoffs when deciding which categories to include and quantify. Tradeoffs include prioritizing values based on their magnitude of value or cost impact, as well as taking into account the feasibility of data collection and accurate quantification. Values of higher magnitude and estimation feasibility are quantified in the majority of studies, including the earliest of studies conducted in the 2000s and 2010s. Additionally, some values of higher magnitude but low feasibility in the earliest of studies have become quantifiable in recent years. There are some values with low average system-wide levels but very high magnitude in specific locations or hours. The value magnitude in some cases can be tied to DPV penetration with low value in areas with little congestion and/or low penetration and vice versa. In these cases, values that are easier to quantify are often incorporated, while those that are more difficult are often addressed via a placeholder value. The placeholder value is paired with a discussion around data needs and methods to improve future estimates, as well as a conversation about when these value categories may increase in magnitude and necessitate more rigorous quantification. This brief summarizes findings from two meta-analyses of VoS studies that took place between 2005 and 2018, as well as findings from four additional studies published from 2018 to 2023. Table ES-1 summarizes the various value and cost categories included in each respective study and whether they were quantified, discussed, or omitted. Values such as avoided energy, capacity, transmission capacity, line losses, and avoided environmental costs are quantified in every study. Some categories were deemed harder to quantify and less impactful at the time of the study, so they were discussed but not quantified (e.g., ancillary services). Other categories, including many at the distribution level, were very locationally and/or temporally specific and dependent on high DPV penetration. These were sometimes quantified and at other times discussed. Notably, when it came to utility costs, integration costs were discussed in all cases, though they were deemed to have a small impact. Other utility costs were omitted for the most part; however, the utility-commissioned study (by NorthWestern Energy in Montana) included both lost utility revenue and programmatic/administrative cost categories. While there are some similarities across studies, each had fairly unique methods that are detailed in the body of this brief.

14 SOLAR ENERGY↗

Mobile Timekeeping Application Built on Reverse-Engineered JPL Infrastructure

Every year, non-exempt employees cumulatively waste over one man-year tracking their time and using the timekeeping Web page to save those times. This app eliminates this waste. The innovation is a native iPhone app. Libraries were built around a reverse- engineered JPL API. It represents a punch-in/punch-out paradigm for timekeeping. It is accessible natively via iPhones, and features ease of access. Any non-exempt employee can natively punch in and out, as well as save and view their JPL timecard. This app is built on custom libraries created by reverse-engineering the standard timekeeping application. Communication is through custom libraries that re-route traffic through BrowserRAS (remote access service). This has value at any center where employees track their time.

Witoff, Robert J.↗

Considerations for Isochronous Data Services over the Proximity-1 Space Link

Future mission concepts for robotic and human explorations will involve a high level of real time control/monitoring operations such as tele-operation for spacecraft rendezvous and surface mobile platforms carrying life-support equipments. The timely dissemination of voice, command, and real-time telemetry for monitoring and coordination purposes is critical for mission success. It is envisioned that future missions will require a network infrastructure capable of supporting isochronous data services. The CCSDS Proximity-1 Space Link Protocol1 could be used to provide isochronous service over the surface-to-Earth relay as well as "beyond-the-horizon" communications between distant Lunar or Mars surface elements. This paper will analyze the latency, jitter, and throughput performance of the Proximity-1 protocol for isochronous applications. In particular we will focus on constrained scenarios where the protocol operates in full-duplex mode, carrying isochronous traffic in one direction and error-controlled traffic in the other direction. We analyze the impact of the strict priority scheme in Proximity-1 on delay jitter and the impact of the isochronous traffic on the efficiency of the reliable data transfer in the other direction, and discuss methods for performance optimization. In general, jitter performance is driving by relative loading of isochronous traffic on the forward link compared to the acknowledgement traffic. Under light loading condition, the upper-bound of the delay jitter is the transmission duration of an acknowledgement frame on the forward link; for higher loading scenarios, the maximum jitter is scaled up by the inverse of the residual bandwidth, i.e., the spare capacity available in the forward link to carry isochronous traffic.

isochronous communications↗

Considerations for Isochronous Data Services over the Proximity-1 Space Link

Future mission concepts for robotic and human explorations will involve a high level of real time control/monitoring operations such as tele-operation for spacecraft rendezvous and surface mobile platforms carrying life-support equipments. The timely dissemination of voice, command, and real-time telemetry for monitoring and coordination purposes is critical for mission success. It is envisioned that future missions will require a network infrastructure capable of supporting isochronous data services. The CCSDS Proximity-1 Space Link Protocol1 could be used to carry isochronous traffic. This paper we will focus on the data link layer portion of the Proximity-1 protocol specification and analyze its jitter and performance for supporting isochronous applications. In particular we will focus on constrained scenarios where the protocol operates in full-duplex mode, carrying isochronous traffic in one direction and error-controlled traffic in the other direction. We analyze the impact of the strict priority scheme in Proximity-1 used to arbitrate channel access on the latency jitter of the isochronous traffic and the efficiency of the reliable data transfer. In general, jitter performance is driven by the loading of the acknowledgement traffic on the forward link. Under light loading condition, the upper-bound of the delay jitter is the transmission duration of an acknowledgement frame on the forward link; for higher loading scenarios, the maximum jitter is scaled up by the inverse of the residual bandwidth, i.e., the spare capacity available in the forward link after accounting for the acknowledgement traffic. We derive analytical expression on the maximum jitter and discuss its performance.

space link↗

Advanced Utilization of the Payload Executive Processor (PEP) Ethernet Port to Support JSL Based Payloads

Increased interest by Payload Developers in utilization of the Joint Station LAN (Local Area Network) (JSL) for command and data transactions has driven the investigation of providing bi-directional Ethernet communication with PEP (Payload Executive Processor). Ethernet-only payload developers are interested in taking advantage of the services provided by PEP. Enabling Ethernet communications within PEP requires more than just turning on the hardware. PEP contains no Operating System (OS) or Ethernet stack so it does not inherit any built in functionality for Ethernet support. Both hardware drivers and application software must be developed from scratch. In the absence of an OS (Operating System) the design must address security issues in terms of access and data transferred, i.e. blocking unauthorized users and preventing denial of service. Developing a design to process Ethernet data within the existing real-time constraints of PEP requires a few compromises: data rates, supported protocols, custom packet format and limited client connections to name a few. Integration of the light weight internet protocol (LwIP). Ethernet stack provides a customizable solution for the embedded real-time environment. As utilization of the JSL increases, the successful implementation of an Ethernet interface enhances the utilization of PEP, and provides a new path for future Ethernet-only payloads to gain access to around the clock command and data services.

Guyette, Greg↗