Abstract: Example implementations described herein are directed to an embedded edge device and edge/cloud system configured to facilitate seamless connectivity between multi-domain assets for system of system and internet of everything applications. Through the use of a novel horizontally scalable embedded architecture for embedded edge device that can be connected to multi-domain assets to enable seamless connectivity between them, the example implementations can facilitate wireless connections across multi-domain assets to allow overall system of systems and internet of everything applications to improve quality of life.

Abstract: In some examples, one or more computing devices on a network may receive, from a client computing device, one or more inputs for configuring a simulation, the simulation including at least a first simulator and a second simulator. The one or more computing devices may allocate computing resources including at least a first virtual machine for executing at least one of the first simulator or the second simulator. The one or more computing devices may configure a first simulation controller executable on the first virtual machine for controlling execution of the at least one of the first simulator or the second simulator. The first simulation controller may initiate execution of at least one of the first simulator or the second simulator as part of execution of the co-simulation. In some examples, a result of the co-simulation may be sent to the client computing device.

Abstract: Example implementations described herein are directed to systems and methods that include the storage of I/F communication activity during a co-execution and a repeater to reproduce such I/F communication activity. Thus in a subsequent re-execution of the simulation or applications, one or more of the simulations or applications utilized can be replaced with a repeater without requiring the full execution of the simulation or application, thereby saving license usage as well as requiring fewer hardware resources for execution.

Abstract: Example implementations described herein are directed to an embedded edge device and edge/cloud system configured to facilitate seamless connectivity between multi-domain assets for system of system and internet of everything applications. Through the use of a novel horizontally scalable embedded architecture for embedded edge device that can be connected to multi-domain assets to enable seamless connectivity between them, the example implementations can facilitate wireless connections across multi-domain assets to allow overall system of systems and internet of everything applications to improve quality of life.

Abstract: Example implementations described herein are directed to systems and methods that include the storage of I/F communication activity during a co-execution and a repeater to reproduce such I/F communication activity. Thus in a subsequent re-execution of the simulation or applications, one or more of the simulations or applications utilized can be replaced with a repeater without requiring the full execution of the simulation or application, thereby saving license usage as well as requiring fewer hardware resources for execution.

Abstract: In some examples, a system may receive, over a network from a vehicle computing device onboard a vehicle, sensor data for at least one sensed parameter of a vehicle component. The system may determine, based on the sensor data, a damage result indicative of fatigue damage to the vehicle component. Based at least partially on the damage result, the system may send a communication to at least one of the vehicle computing device onboard the vehicle, or a computing device associated with an account associated with the vehicle. In some cases, the damage result may be determined from at least one of accessing a lookup table using the sensor data, or executing a fatigue simulation using sensor data.

Abstract: In some examples, a system may receive, over a network from a vehicle computing device onboard a vehicle, sensor data for at least one sensed parameter of a vehicle component. The system may determine, based on the sensor data, a damage result indicative of fatigue damage to the vehicle component. Based at least partially on the damage result, the system may send a communication to at least one of the vehicle computing device onboard the vehicle, or a computing device associated with an account associated with the vehicle. In some cases, the damage result may be determined from at least one of accessing a lookup table using the sensor data, or executing a fatigue simulation using sensor data.

Abstract: In some examples, one or more computing devices on a network may receive, from a client computing device, one or more inputs for configuring a simulation, the simulation including at least a first simulator and a second simulator. The one or more computing devices may allocate computing resources including at least a first virtual machine for executing at least one of the first simulator or the second simulator. The one or more computing devices may configure a first simulation controller executable on the first virtual machine for controlling execution of the at least one of the first simulator or the second simulator. The first simulation controller may initiate execution of at least one of the first simulator or the second simulator as part of execution of the co-simulation. In some examples, a result of the co-simulation may be sent to the client computing device.