Collecting, storing, and reporting accident data in an information handling system (IHS)
Systems and methods for collecting, storing, and reporting accident data in an IHS are described. In some embodiments, an Information Handling System (IHS) may include an Embedded Controller (EC) and a memory coupled to the EC, the memory having program instructions stored thereon that, upon execution, cause the EC to detect an accident and, before the accident ends, collect, store, or report data associated with the accident based, at least in part, upon an accident handling policy.
1 . An Information Handling System (IHS) that comprises:
an Embedded Controller (EC) coupled to an always-on power rail; and
a memory coupled to the EC, the memory configured with program instructions stored thereon that, upon execution in an EC memory space distinct from any IHS host processor memory space, cause the EC to perform EC operations that comprise:
detect an accident;
before end of the accident, collect, store, or report data associated with the accident based, at least in part, upon an accident handling policy;
determine whether an unexpected discrepancy in device inventory is detected based, at least in part, on a comparison between a device scan before the accident and a device scan after the accident; and
in response to a determination an unexpected discrepancy in device inventory was detected, notify a cloud service of the unexpected discrepancy, wherein the EC is configured to notify the cloud service via an Out-of-band (OOB) network stack while every IHS host processor remains in an IHS host processor low-power state, or via an in-band network stack if any IHS host processor is not in an IHS host processor low-power state.
2 . The IHS of claim 1 , wherein the accident comprises at least one of: a drop, a fall, a throw, a hit, a crash, an impact, or a collision involving the IHS or a component thereof.
3 . The IHS of claim 1 , wherein the accident handling policy determines when the EC collects, stores, or reports the data after the detection.
4 . The IHS of claim 1 , wherein to collect, store, or report data, the program instructions, upon execution, further cause the EC to collect, store, or report a first data portion a first amount of time after the detection.
5 . The IHS of claim 4 , wherein the first data portion comprises at least one of: an IHS identification, a power state of the IHS, or an IHS posture.
6 . The IHS of claim 4 , wherein the program instructions, upon execution, further cause the EC to select the first data portion based, at least in part, upon the accident handling policy.
7 . The IHS of claim 4 , wherein the program instructions, upon execution, further cause the EC to select the first amount of time based, at least in part, upon the accident handling policy.
8 . The IHS of claim 4 , wherein to collect, store, or report data, the program instructions, upon execution, further cause the EC to collect, store, or report a second data portion a second amount of time after the detection, wherein the second amount of time is configured to be greater than the first amount of time.
9 . The IHS of claim 8 , wherein the second data portion comprises at least one of: latest sensor telemetry, diagnostics data, or damage data captured after the first data portion is reported.
10 . The IHS of claim 8 , wherein the program instructions, upon execution, further cause the EC to select the first data portion based, at least in part, upon the accident handling policy.
11 . The IHS of claim 8 , wherein the program instructions, upon execution, further cause the EC to select the second amount of time based, at least in part, upon the accident handling policy.
12 . The IHS of claim 1 , wherein to store or report the data, the program instructions, upon execution, further cause the EC to transmit at least a portion of the data to at least one of: a backend service, or an Operating System (OS).
13 . The IHS of claim 1 , wherein the program instructions, upon execution, further cause the EC to store or report a message to indicate an end of the accident, wherein the message is triggered based at least in part upon a determination IHS acceleration reached zero and remained at zero for a predetermined minimum time period.
14 . A memory device configured with program instructions stored thereon that, upon execution by an Embedded Controller (EC) processor in an EC memory space distinct from any Information Handling System (IHS) host processor memory space, wherein the EC is coupled to an always-on power rail in an IHS, and wherein the program instructions are structured to cause the EC to perform EC operations that comprise:
detect an accident;
before end of the accident, collect, store, or report data associated with the accident based, at least in part, upon an accident handling policy, wherein collect, store, or report data comprises report a first data portion a first amount of time after the detection, and collect and report a second data portion a second amount of time after the detection, wherein the second amount of time is configured to be greater than the first amount of time, and wherein the second data portion comprises at least one of: latest sensor telemetry, diagnostics data, or damage data captured after the first data portion is reported;
determine whether IHS acceleration reached zero and remained at zero for a predetermined minimum time period;
in response to a determination IHS acceleration reached zero and remained at zero for the predetermined minimum time period, send a message to a cloud service to indicate end of the accident via an Out-of-band (OOB) network stack while every IHS host processor remains in an IHS host processor low-power state, or via an in-band network stack if any IHS host processor is not in an IHS host processor low-power state;
determine whether a discrepancy in device inventory after the accident is an unexpected discrepancy, based, at least in part, on a comparison between a device scan before the accident and a device scan after the accident, and contextual information; and
in response to a determination the discrepancy is unexpected, notify a cloud service of the unexpected discrepancy via at least one active network stack.
15 . The memory device of claim 14 , wherein, the program instructions, upon execution, further cause the EC to increase the second amount of time in response to a subsequent accident detection.
16 . The memory device of claim 15 , wherein the program instructions, upon execution, further cause the EC to select the first amount of time according to the accident handling policy.
17 . The memory device of claim 15 , wherein, the program instructions, upon execution, further cause an Operating System (OS) executed on an IHS host processor to receive an accident indication from the EC when the IHS is awakened by the EC from an IHS low-power state, and wherein the EC is configured to detect the accident when the IHS is in the IHS low-power state based at least in part on the always-on power rail coupled to the EC.
18 . The memory device of claim 17 , wherein the program instructions, upon execution, further cause the EC to select the second amount of time in accordance with the accident handling policy.