Abstract: In one aspect, a method of confirming identity of an entity is disclosed. The method comprises receiving a plurality of items for delivery to an address, obtaining, from the items, information regarding an entity associated with the items and the address, and delivering the items to the address. The method may also comprise identifying an expected identity of the entity, receiving a request to confirm an identity of the entity using third-party identity verification via a user interface, and determining, based on the information regarding the entity, a confidence score for the expected identity. The method may further comprise determining whether the confidence score is greater than or equal to the threshold value and generating a response to the request. The method may additionally comprises displaying the response via the user interface.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: An information handling system may include at least one processor; and a storage resource having an element manager stored thereon. The information handling system may be configured to: establish, via the element manager, an information handling system cluster, wherein the information handling system cluster includes the information handling system as a first node and at least one other information handling system as a second node; configure the first node and the second node to communicatively couple to a storage array via a network and use the storage array as a primary storage volume for the information handling system cluster; and migrate the element manager to execute from the storage array.

Abstract: In one aspect, a method of confirming identity of an entity is disclosed. The method comprises receiving a plurality of items for delivery to an address, obtaining, from the items, information regarding an entity associated with the items and the address, and delivering the items to the address. The method may also comprise identifying an expected identity of the entity, receiving a request to confirm an identity of the entity using third-party identity verification via a user interface, and determining, based on the information regarding the entity, a confidence score for the expected identity. The method may further comprise determining whether the confidence score is greater than or equal to the threshold value and generating a response to the request. The method may additionally comprises displaying the response via the user interface.

Abstract: An information handling system may include at least one processor; and a storage resource having an element manager stored thereon. The information handling system may be configured to: establish, via the element manager, an information handling system cluster, wherein the information handling system cluster includes the information handling system as a first node and at least one other information handling system as a second node; configure the first node and the second node to communicatively couple to a storage array via a network and use the storage array as a primary storage volume for the information handling system cluster; and migrate the element manager to execute from the storage array.

Abstract: Disclosed systems and methods include or support a message logging service in which, responsive to receiving an event message generated by a business function, the message is logged in accordance with a message severity, one or more severity level attributes of the system, and one or more message logging criterion. Responsive to determining the message severity meets a first criterion, the message may be routed to and saved within a first persistent log file. Responsive to determining the message severity satisfies a second criterion, the message may be temporarily stored to a FIFO message queue, for possible inclusion in a second persistent log file. A health monitoring service for monitoring application programs corresponding to various business functions, upon detecting a degraded health state of a business function, may cause messages stored in the message queue to be dumped to a second persistent log file.

Abstract: Disclosed systems and methods may retrieve a base image of a plugin for a hyperconverged infrastructure (HCl) platform and create a Docker image for an HCl platform plugin based, in part, on the base image. The HCl platform plugin enables an extended function not native to the HCl platform. Disclosed methods may include registering the Docker image within an HCl platform instance running on an HCl appliance associated with a customer, and saving the Docker image to a Docker image repository within the HCl platform instance. The extended HCl platform function may be any suitable function including, as an illustrative example, a function for provisioning a third party storage device within the HCl platform. Disclosed method steps may be performed by an independent third party developer that lacks authorized access to an HCl platform instance.

Abstract: An information handling system may include at least one processor and a memory. The information handling system may be configured to maintain a plurality of folders in a central management system, wherein each folder is a data structure having one or more hosts associated therewith; and in response to an instruction to move a particular host from a first folder to a second folder: un-associate the particular host from the first folder; associate the particular host with the second folder; and transmit a notification regarding the movement to a local management system of a satellite information handling system; wherein the local management system is configured to update a local data structure regarding the movement.

Abstract: Disclosed systems and methods for centrally managing distributed edge server resources may create a host folder, associate the host folder with an element manager, add one or more edge servers to the host folder, and manage the one or more edge servers with an edge server management system running in the applicable instance of the element manager. The host folder may be created from either a server manager UI or from an element manager UI. An edge server may be added to a host folder by invoking a UI of the element manager UI. Managing the one or more edge servers may include performing health monitoring of the edge servers as well as version checking and upgrading of the edge servers. An edge server agent may be deployed in the edge server to receive change events published by the edge server and redirect the change events to an element manager system.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: A system 100 for autonomous vehicle operation can include: a low-level safety platform 130; and can optionally include and/or interface with any or all of: an autonomous agent 102, a sensor system, a computing system 120, a vehicle communication network 140, a vehicle control system 150, and/or any suitable components. The system functions to facilitate fallback planning and/or execution at the autonomous agent. Additionally or alternatively, the system can function to transition the autonomous agent between a primary (autonomous) operation mode and a fallback operation mode.

Abstract: In one aspect, a method of confirming identity of an entity is disclosed. The method comprises receiving a plurality of items for delivery to an address, obtaining, from the items, information regarding an entity associated with the items and the address, and delivering the items to the address. The method may also comprise identifying an expected identity of the entity, receiving a request to confirm an identity of the entity using third-party identity verification via a user interface, and determining, based on the information regarding the entity, a confidence score for the expected identity. The method may further comprise determining whether the confidence score is greater than or equal to the threshold value and generating a response to the request. The method may additionally comprises displaying the response via the user interface.