Concealing loss of distributed simultaneous localization and mapping (SLAM) data in edge cloud architectures
Embodiments of systems and methods for concealing loss of Simultaneous Localization and Mapping (SLAM) data in edge cloud architectures are described. In some embodiments, a method may include: receiving SLAM data usable to produce a first map of a physical space for a first HMD; in response to a portion of the SLAM data being lost or corrupt, retrieving a first landmark detected in previous SLAM data with a first confidence value; receiving, from a second IHS coupled to a second HMD, a second landmark usable to produce a second map for the second HMD, where the second landmark has a second confidence value; in response to the first and second landmarks overlapping, selecting one of the first or second landmark with greatest confidence value; and producing the first map using the selected landmark.
1. An Information Handling System (IHS), comprising:
a processor; and
a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, cause the IHS to:
receive Simultaneous Localization and Mapping (SLAM) data usable to produce a first map of a physical space for a first Head-Mounted Display (HMD);
in response to a determination that at least a portion of the SLAM data is lost or corrupt, retrieve a first landmark detected in previous SLAM data, wherein the first landmark has a first confidence value;
select a second HMD over another HMD based upon at least one of: (i) a latency parameter associated with a second IHS coupled to the second HMD meeting a latency requirement of the first HMD, (ii) a computation parameter associated with the second IHS meeting a computation requirement of the first HMD, or (iii) a speed of movement the first HMD;
receive, from the second IHS, a second landmark usable to produce a second map of the physical space for the second HMD, wherein the second landmark has a second confidence value, and wherein the second IHS comprises: a co-located IHS, an edge server, or a cloud server;
in response to a determination that the first and second landmarks overlap, select the first landmark in response to the first confidence value being greater than the second confidence value, or select the second landmark in response to the second confidence value being greater than the first confidence value; and
produce the first map using the selected landmark.
2. The IHS of claim 1 , wherein the SLAM data comprises landmark data found in a Region of Interest (ROI) within an infrared (IR) or near-IR (NIR) frame captured via a camera mounted on the first HMD.
3. The IHS of claim 1 , wherein to determine that the first and second landmarks overlap, the program instructions, upon execution, further cause the IHS to determine that the first landmark and the second landmark are separated by a threshold distance.
4. The IHS of claim 3 , wherein to determine that the first landmark and the second landmark are separated by the threshold distance, the program instructions, upon execution, further cause the IHS to transform a first coordinate location of the first landmark based in part upon a pose of the first HMD.
5. The IHS of claim 3 , wherein to determine that the first landmark and the second landmark are separated by the threshold distance, the program instructions, upon execution, further cause the IHS to transform a second coordinate location of the second landmark based in part upon a pose of the second HMD.
6. A hardware memory having program instructions stored thereon that, upon execution by an Information Handling System (IHS), cause the IHS to:
receive Simultaneous Localization and Mapping (SLAM) data usable to produce a first map of a physical space for a first Head-Mounted Display (HMD);
in response to a determination that at least a portion of the SLAM data is lost or corrupt, retrieve a first landmark detected in previous SLAM data, wherein the first landmark has a first confidence value;
select a second HMD over another HMD, wherein the second HMD is coupled to a second IHS and wherein the other HMD is coupled to another IHS, in response to a location of the second IHS in an edge cloud architecture satisfying a requirement of the first HMD;
receive, from the second IHS, a second landmark usable to produce a second map of the physical space for the second HMD, wherein the second landmark has a second confidence value;
in response to a determination that the first and second landmarks overlap, select the first landmark in response to the first confidence value being greater than the second confidence value, or select the second landmark in response to the second confidence value being greater than the first confidence value; and
produce the first map using the selected landmark.
7. The hardware memory of claim 6 , wherein the second IHS is a co-located server in response to the first HMD having a first latency requirement, wherein the second IHS is an edge server in response to the first HMD having a second latency requirement, or wherein the second IHS is a cloud server in response to the first HMD having a third latency requirement.
8. The hardware memory of claim 6 , wherein the second IHS is a co-located server in response to the first HMD having a first compute requirement, wherein the second IHS is an edge server in response to the first HMD having a second compute requirement, or wherein the second IHS is a cloud server in response to the first HMD having a third compute requirement.
9. The hardware memory of claim 6 , wherein the second IHS is a co-located server in response to the first HMD moving with a first speed, wherein the second IHS is an edge server in response to the first HMD moving with a second speed smaller than the first speed, or wherein the second IHS is a cloud server in response to the first HMD moving with a third speed smaller than the second speed.
10. The hardware memory of claim 6 , wherein to determine that the first and second landmarks overlap, the program instructions, upon execution, further cause the IHS to determine that the first landmark and the second landmark are separated by a threshold distance.
11. The hardware memory of claim 10 , wherein to determine that the first landmark and the second landmark are separated by the threshold distance, the program instructions, upon execution, further cause the IHS to:
transform a first coordinate location of the first landmark based in part upon a pose of the first HMD; and
transform a second coordinate location of the second landmark based in part upon a pose of the second HMD.
12. A method, comprising:
receiving Simultaneous Localization and Mapping (SLAM) data usable to produce a first map of a physical space for a first Head-Mounted Display (HMD);
in response to a determination that at least a portion of the SLAM data is lost or corrupt, retrieving a first landmark detected in previous SLAM data, wherein the first landmark has a first confidence value;
selecting a second HMD over another HMD, wherein the second HMD is coupled to a second IHS and wherein the other HMD is coupled to another IHS, in response to a location of the second IHS in an edge cloud architecture satisfying a requirement of the first HMD;
receiving, from the second IHS, a second landmark usable to produce a second map of the physical space for the second HMD, wherein the second landmark has a second confidence value;
in response to a determination that the first and second landmarks overlap, selecting the first landmark in response to the first confidence value being greater than the second confidence value, or selecting the second landmark in response to the second confidence value being greater than the first confidence value; and
producing the first map using the selected landmark.
13. The method of claim 12 , wherein the second IHS is a co-located server in response to the first HMD having a first latency requirement, wherein the second IHS is an edge server in response to the first HMD having a second latency requirement less strict than the first latency requirement, or wherein the second IHS is a cloud server in response to the first HMD having a third latency requirement less strict than the second latency requirement.
14. The method of claim 12 , wherein the second IHS is a co-located server in response to the first HMD having a first compute requirement, wherein the second IHS is an edge server in response to the first HMD having a second compute requirement greater than the first compute requirement, or wherein the second IHS is a cloud server in response to the first HMD having a third compute requirement greater than the second compute requirement.
15. The method of claim 12 , wherein the second IHS is a co-located server in response to the first HMD moving with a first speed, wherein the second IHS is an edge server in response to the first HMD moving with a second speed smaller than the first speed, or wherein the second IHS is a cloud server in response to the first HMD moving with a third speed smaller than the second speed.
16. The method of claim 12 , wherein the second IHS is a co-located server in response to the first landmark having moved with a first speed, wherein the second IHS is an edge server in response to the first landmark having moved with a second speed smaller than the first speed, or wherein the second IHS is a cloud server in response to the first landmark having moved with a third speed smaller than the second landmark.