Application Startup. Once a system’s network is up and working correctly, applications need to do their own startup procedure. Typically, applications have both a “cold start” and “warm start” to establish a valid initial state. Cold start is used when a system is in a safe state. Systems typically exchange a number of independent sources of data that, in the aggregate, indicate the system is in a safe state. For example, a commercial airliner could use a combination of weight on wheels, air speed below some minimum, and door open. A similar rationale applies to warm start. However, warm start procedures tend to be more ad hoc and application-specific than cold start. Regardless of the mechanism used at the application level, some form of agreement is required via the network. Mechanisms for reaching agreement on the exchange of this application data can be built on the TTEthernet agreement, fault tolerance, and synchronization mechanisms described above.
Appears in 5 contracts
Samples: ntrs.nasa.gov, ntrs.nasa.gov, ntrs.nasa.gov
