US2022350626A1PendingUtilityA1
Device navigational maps for connected devices
Est. expiryFeb 2, 2036(~9.5 yrs left)· nominal 20-yr term from priority
G06F 16/904G06F 11/3684G06F 9/453G06F 11/3006G06F 11/3696G06F 11/302G06F 9/4451G06F 9/455
65
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
Described herein is a method for creating and utilizing device navigational maps. The device navigational maps are modeled using directed graphs that contain detailed information of all components on the connected devices. An application systematically scans through the entire connected device and builds a detailed data model of the connected device, which is used as the navigational map.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method for creating a navigational map for a connected device, comprising:
scanning the connected device to retrieve structural layout, hardware information and software information of the connected device; generating vertices and edges from the scanned connected device, wherein each vertex encapsulates data for a connected device component and each edge defines actions needed to move between a pair of vertices; building a navigational map from the generated vertices and edges; and storing the navigational map in a database.
2 . The method of claim 1 , further comprising:
receiving an inquiry from a user; providing a list of screens responsive to the inquiry; retrieving an applicable navigational map; computing a path between a start screen and a destination screen using the retrieved navigational map retrieved in response to selection of the destination screen; and navigating the path on the connected device using the navigational map.
3 . The method of claim 2 , wherein navigating the path further comprises:
executing commands on the connected device to move along the path.
4 . The method of claim 3 , further comprising:
monitoring a current screen against the retrieved navigational map; and matching the current screen with the retrieved navigational map.
5 . The method of claim 1 , further comprising:
modifying the retrieved navigational map with screens not present in the retrieved navigational map; and updating a navigational map in the database corresponding to the retrieved navigational map.
6 . The method of claim 1 , further comprising:
setting a depth level for a predetermined set of connected device components, wherein scanning is completed upon reaching a designated depth level.
7 . The method of claim 1 , further comprising:
creating a queue of unvisited vertices, wherein the queue is updating during scanning of the connected device; for each vertex:
determining other unvisited vertices that can be reached;
creating a query vertex for each unvisited vertex;
determining if the query vertex already exists in the navigational map;
creating a new edge if the query vertex does not exist; and
decrementing the queue when all vertices for a depth level is complete.
8 . The method of claim 7 , wherein all links and scrollable elements are checked to determine existence of the other unvisited vertices.
9 . A system for creating a navigational map for a connected device, comprising:
a database; and a navigation map builder, wherein when the navigation map builder is connected to a connected device, the navigation map builder:
scans the connected device to retrieve structural layout, hardware information and software information of the connected device;
generates vertices and edges from the scanned connected device, wherein each vertex encapsulates data for a connected device component and each edge defines actions needed to move between a pair of vertices;
builds a navigational map from the generated vertices and edges; and
stores the navigational map in the database.
10 . The system of claim 9 , further comprising:
a navigation map service connected to the connected device, the navigation map service further comprising a search engine, a navigation engine, and a remote command executor, wherein when the navigation map service receives an inquiry from a user:
the search engine receives the inquiry and provides a list of screens responsive to the inquiry;
the navigation map service retrieves an applicable navigational map;
the navigation engine computes a path between a start screen and a destination screen using the retrieved navigational map retrieved in response to selection of the destination screen; and
the navigation map service navigates the path on the connected device using the navigational map.
11 . The system of claim 10 , wherein the remote command executor executes commands on the connected device to move along the path.
12 . The system of claim 11 , wherein the navigation map service further comprises a screen monitor, the screen monitor monitoring a current screen against the retrieved navigational map and matches the current screen with the retrieved navigational map.
13 . The system of claim 9 , wherein the navigation map service further comprises a navigational map extender, the navigational map extender modifying the retrieved navigational map with screens not present in the retrieved navigational map and updating a navigational map in the database corresponding to the retrieved navigational map.
14 . The system of claim 9 , wherein the navigation map builder sets a depth level for a predetermined set of connected device components, and wherein scanning is completed upon reaching a designated depth level.
15 . The system of claim 10 , wherein the navigation map builder:
creates a queue of unvisited vertices, wherein the queue is updating during scanning of the connected device; for each vertex:
determines other unvisited vertices that can be reached;
creates a query vertex for each unvisited vertex;
determines if the query vertex already exists in the navigational map;
creates a new edge if the query vertex does not exist; and
decrements the queue when all vertices for a depth level is complete.
16 . The system of claim 15 , wherein all links and scrollable elements are checked to determine existence of the other unvisited vertices.Join the waitlist — get patent alerts
Track US2022350626A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.