rfc9450v2.txt | rfc9450.txt | |||
---|---|---|---|---|
skipping to change at line 998 ¶ | skipping to change at line 998 ¶ | |||
This use case might combine multiple communication flows, with some | This use case might combine multiple communication flows, with some | |||
of them being latency critical (like those related to robot-control | of them being latency critical (like those related to robot-control | |||
tasks). Note that there are still many communication flows (like | tasks). Note that there are still many communication flows (like | |||
some offloading tasks) that only demand reliability and availability. | some offloading tasks) that only demand reliability and availability. | |||
9. Instrumented Emergency Medical Vehicles | 9. Instrumented Emergency Medical Vehicles | |||
9.1. Use Case Description | 9.1. Use Case Description | |||
An instrumented ambulance would be one or multiple network segments | An instrumented ambulance would have one or multiple network segments | |||
that are connected to end systems such as: | that are connected to end systems such as: | |||
* vital signs sensors attached to the casualty in the ambulance to | * vital signs sensors attached to the casualty in the ambulance to | |||
relay medical data to hospital emergency room, | relay medical data to hospital emergency room, | |||
* a radio-navigation sensor to relay position data to various | * a radio-navigation sensor to relay position data to various | |||
destinations including dispatcher, | destinations including dispatcher, | |||
* voice communication for ambulance attendant (likely to consult | * voice communication for ambulance attendant (likely to consult | |||
with ER doctor), and | with ER doctor), and | |||
End of changes. 1 change blocks. | ||||
1 lines changed or deleted | 1 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |