CROSS REFERENCE TO RELATED APPLICATIONS AND PRIORITY
[001] The present application does not claim priority from any patent application.
TECHNICAL FIELD
[002] The present disclosure in general relates to the field of unmanned aerial vehicles such as drones. More particularly, the present disclosure relates to a system and method for facilitating navigational-aid to an unmanned aerial vehicle (UAV).
BACKGROUND
[003] Unmanned Air Vehicles (UAVs), such as drones, perform a major role in defense and industries such as mining. In closed locations such as a mine or indoor industrial premises, these drones may be remotely controlled from a central server. Due to the unavailability of Global Positioning System (GPS) capabilities in such locations, these central servers heavily rely on wireless network techniques such as triangulation for determining the current location of the drones, navigating the drones on a defined pathway, and the like.
[004] In case of network outage, i.e., non-operational connection between the drone and the central server, it may be necessary to ensure that the drone reaches a safe location. Further, in case of natural calamities such as floods or earthquakes, immediate evacuation of the drone from its current location to the safe location may be needed so that there are no damages to the drone equipment.
SUMMARY
[005] This summary is provided to introduce aspects related to device and method for providing real-time navigation assistance to a UAV, further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[006] In one implementation, a system for facilitating navigational-aid to an unmanned aerial vehicle (UAV) is disclosed. The system may include a processor and a memory coupled to the processor. The processor may execute a set of instructions stored in the memory to monitor a network connection between the UAV and a central server connected to the UAV. The processor may further execute the set of instructions to enable maneuvering of the UAV to a predefined distance from ground when the network
3
connection between the UAV and the central sever is non-operational. Further, the processor may execute the set of instructions to decode an identifier associated with a first tag located within a predefined range from a current location of the UAV. The processor may further execute the set of instructions to identify navigational information mapped with the identifier associated with the first tag. Further, the processor may execute the set of instructions to enable the UAV to traverse to a second tag using the navigational information. The second tag may be located within a predefined range of a base location.
[007] In another implementation, a method for facilitating navigational-aid to an unmanned aerial vehicle (UAV) is disclosed. The method may include monitoring, by a processor, a network connection between the UAV and a central server connected to the UAV. The method may further include, enabling, by the processor, maneuvering of the UAV to a predefined distance, from the ground, when the network connection between the UAV and the central server is non-operational. The method may further include decoding, by the processor an identifier associated with a first tag located within a predefined range from a current location of the UAV. The method may further include, identifying navigational information mapped to the identifier associated with the first tag. The method may further include enabling, by the processor, the UAV to traverse to a second tag using the navigational information. The second tag maybe located within a predefined range of the base location.
[008] In yet another implementation, a non-transitory computer readable medium embodying a program executable in a computing device for facilitating navigational-aid to an unmanned aerial vehicle (UAV). The program may include a program code for monitoring a network connection between the UAV and a central sever connected to the UAV. The program may further include a program code for enabling, maneuvering of the UAV to a predefined distance, from the ground, when the network connection between the UAV and the central server is non-operational. Further, the program code may include program code for decoding a first tag located within a predefined range from a current location of the UAV. The program may further include a program code for identifying navigational information mapped with the identifier associated with the first tag. The program may further include program code for enabling the UAV to traverse to a second tag using the navigational information. The second tag may be located within a predefined range of a base location.
4
BRIEF DESCRIPTION OF THE DRAWINGS
[009] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to refer like features and components.
[0010] Figure 1 illustrates a network scenario illustrating a central sever, an UAV, and a system for facilitating navigational aid to the UAV, in accordance with an embodiment of the present disclosure.
[0011] Figure 2 illustrates exemplary detailed workings of the system, in accordance with an embodiment of the present disclosure.
[0012] Figure 3illustrates a method for facilitating navigational-aid to the UAV, in accordance with an embodiment of the present disclosure.
DETAILED DESCRIPTION
[0013] The present systems and methods will now be described more fully hereinafter with reference to the accompanying drawings in which exemplary embodiments of the invention are shown. However, the invention may be embodied in many different forms and should not be construed as limited to the representative embodiments set forth herein. The exemplary embodiments are provided so that this disclosure will be both thorough and complete, and will fully convey the scope of the invention and enable one of ordinary skill in the art to make, use and practice the invention. Like reference numbers refer to like elements throughout the various drawings.
[0014] Referring to Figure 1, a network scenario 100 of a system 102, a UAV 104 and a central server 106 is disclosed, in accordance with an embodiment of the present disclosure. In an implementation, the UAV 104 may be connected to the central server 106 through a network 110. The central server 106 may use one or more techniques to control the UAV 104 during operation of the UAV 104 for different industrial purposes. In an example, the central server 106 may control a navigation of the UAV 104 inside a mine or an underground construction site. In another example, the central server 106 may control surveillance activities assigned to the UAV 104 in defense scenarios. The central sever 106, in one implementation, may track the location information of the UAV 104 through the network 110.
[0015] In one implementation, the network 110 may be a wireless network, a wired network or a combination thereof. The network 110 can be implemented as one of the
5
different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 110 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further the network 110 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.
[0016] In an embodiment, the system 102 may monitor a network connection of the network 110 between the UAV 104 and the central server 106. At times, the network connection between the UAV 104 and the central server 106 may be faulty owing to one or more reasons. Further, in some instances the network connection may be totally non-operational. In such an instance, i.e. when the system 102 detects that the network connection is non-operational; the system 102 may initiate a recovery mode for the UAV 104. In an embodiment, the recovery mode may be initiated by the system 102 so as to enable the UAV 104 to safely navigate from a current location to a base location. Operation of different modules of the system 102, when the recovery mode is initiated, is further explained with reference to Figure 2.
[0017] Figure 2 illustrates the system 102 in accordance with an embodiment of the present disclosure. In one embodiment, the system 102 may include at least one processor 202, an input/output (I/O) interface 204, and a memory 206. The at least one processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor 202 is configured to fetch and execute computer-readable instructions or modules stored in the memory 206.
[0018] The I/O interface 204 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 204 may enable the system 102 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 204 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 204 may include one or more ports for connecting a number of devices to one another or to another server.
6
[0019] The memory 206 may include any computer-readable medium or computer program product known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or nonvolatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, a compact disks (CDs), digital versatile disc or digital video disc (DVDs) and magnetic tapes. The memory 206 may include modules 208 and data 210.
[0020] The modules 208 include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. In one implementation, the modules 208 may include a maneuvering module 212, a navigational-aid module 214 and other modules 216. The other modules 216 may include programs or coded instructions that supplement applications and functions of the system 102.
[0021] The data 210, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 208. The data 210 may also include location data 218 and other data 220. Each of the aforementioned modules is explained in detail in subsequent paragraphs of the specification.
[0022] As described in the foregoing, a recovery mode for the UAV 104 may be initiated by the system 102 once it is detected that the network connection between the UAV 104 and the central server 106 is non-operational. In one example, the network connection may be non-operational due to one or more factors. For instance, the network connection may be non-operational due to a network outage or a natural calamity. In such situations, the central server 106 may lose total control over the operations of the UAV 104. It may thus become highly imperative that the UAV 104 is safely navigated to a base location so as to make sure that the UAV 104 is not damaged.
[0023] Referring back to the figure, the maneuvering module 212 may monitor a connection status of the network 110. In one implementation, the maneuvering module 212 may monitor the connection status on a periodic basis. In the implementation, the processor 202 may send ping requests to the network 110 periodically. In a connected state, the network 110 may transmit responses to these periodic ping requests. The maneuvering module 212 may monitor the responses transmitted from the network 110 and analyze the same to determine the connection status for the network 110.
[0024] If the maneuvering module 212 detects that the connection between the UAV 104and the central server 106 is non-operational, the system 102 may initiate the recovery
7
mode for the UAV 104. In one implementation, the recovery mode may be initiated after a predefined time delay from the connection being detected as non-operational. This may be done in order to ensure that the UAV 104 does not collide with other UAVs in the vicinity. In one example, the predefined time delay may be unique for each UAV depending upon one or more factors such as no. of other UAVs in vicinity, last location status, current time, and the like. In one implementation, information about the predefined time delay may be stored in the location data 218.
[0025] Once the predefined time period elapses and the recovery mode is initiated, the maneuvering module 212 may compare a current distance of the UAV 104, from the ground, to a predefined distance. The predefined distance may be a distance from the ground required for the UAV 104 to reach in order to safely navigate to the base location. In an embodiment, the predefined distance may be set such as to enable the UAV 104 to read one or more tags in a range of the UAV 104 without encountering interference from other tags, as would be described in the subsequent text.
[0026] In an implementation, a sensor 222 inbuilt within the system 102 may calculate the current distance of the UAV104, from the ground, and transmit information regarding the current distance to maneuvering module 212 for the comparison. In an example, the sensor 222 may be an ultrasonic sensor or an infrared sensor.
[0027] In one implementation, if the UAV 104 is not at the predefined distance from the ground, the maneuvering module 212 may enable maneuvering of the UAV 104 to the predefined distance. The maneuvering module 212 may, in an example, may control a rotor system (not shown) of the UAV 104 for moving the UAV 104 to the predefined distance. In another implementation, the maneuvering module 212 may be further configured to maintain the UAV 104 to the predefined distance from the ground till the recovery mode continues.
[0028] Once the UAV 104 reaches the predefined distance from the ground, a scanner 224 may scan an identifier associated with a first tag (not shown) located within a predefined range from the UAV 104.In one example, the first tag may be a Radio Frequency Identification (RFID) tag. In an implementation, the predefined range may be determined based on a frequency range of the first tag. Further, the identifier may contain unique identification information for the first tag, such as serial number, manufacturing ID, and the like.
[0029] The navigational-aid module 214 may decode the identifier of the first tag, scanned by the scanner 224, to identify navigational information mapped with the
8
identifier of the first tag. The navigational-aid module 214 may pull the identifier of the first tag from the scanner 224. Further, the navigational-aid module 214 may search the identifier of the first tag within location data 218 stored in data 210 of the memory 206. The location data 218, in an implementation, may include navigational information associated with one or more tags mapped to respective identifiers of these tags. The navigational-aid module 214 may extract navigational information associated with the first tag by comparing the identifier of the first tag with identifiers already stored in the location data 218. Based on the comparison, the navigational-aid module 214 may extract navigational information mapped to the identifier of the first tag. In an implementation, the navigational information may include current location of the first tag, type of the first tag, location details of a next tag to be traversed to, type of the next tag, and the like.
[0030] Based on the extracted navigational information, the navigational-aid module 214 may enable the UAV 104 to traverse to a second tag (not shown). In an example, the navigational-aid module 214 may analyze navigational information associated with the first tag to identify location details of the second tag. The location details of the second tag may then be transmitted to the maneuvering module 212. The maneuvering module 212 may then enable maneuvering of the UAV104 to reach the second tag. In an embodiment, the second tag may be located within a predefined range of the base location. In another embodiment, the second tag may be a paper-based tag, such as a paper barcode. Use of paper-based tags would make the system 102 cost effective. However, the second tag may be a non-paper based tag, such as an RFID tag or an NFC chip.
[0031] In an embodiment, a first camera 226-1 may determine a current location of the UAV 104 from the second tag. In an implementation, the first camera 226-1 may be a three-dimensional (3D) camera. The first camera 226-1 may be configured to generate one or more 3D images of surroundings of the second tag. These 3D images may be analyzed by the processor 202 to compute the current distance of the UAV 104 from the second tag. The information about the current distance of the UAV 104 from the second tag may be transmitted by the processor 202 to the navigational-aid module 214.
[0032] In another embodiment, a second camera 226-2 may be configured to enable determination of an identifier associated with the second tag. In an example, the second camera may be a two-dimensional (2D) camera. The second camera 226-2 may generate a 2D image of the second tag and transmit it to the processor 202. The processor 202
9
may identify an identifier associated with the second tag, based on the 2D image, and transmit the identifier to the navigational-aid module 214.
[0033] In an implementation, the navigational-aid module 214 may compare the identifier of the second tag to one or more identifiers stored in the location data 218. Based on the comparison, the navigational-aid module 214 may extract location details of the second tag from the location data 218. The location details of the second tag along with the current distance of the UAV 104 from the second tag may then be used to compute the actual current location of the UAV 104, with respect to the base location. The actual current location of the UAV 104 may then be used by the maneuvering module 212 to enable maneuvering of the UAV 104 to the base location.
[0034] As described in the foregoing, navigational information from the first tag may be used to determine location details of the second tag. Once the UAV 104 reaches the second tag, the actual current location of the UAV 104 may be determined in order to maneuver the UAV 104 to the base location. However, a person skilled in the art would appreciate that the present disclosure may also be used for more than two tags. In such a scenario, the system 102 may scan multiple tags iteratively till the UAV 104 reaches the base location.
[0035] Referring now to Figure 3, the method of facilitating navigational-aid to an UAV, in accordance with an embodiment of the present subject matter. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 300 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.
[0036] The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300 or alternate methods. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of
10
explanation, in the embodiments described below, the method 300 may be considered to be implemented in the above described system 102.
[0037] At block 302, a network connection between the UAV and a central server connected to the UAV, may be monitored.
[0038] At block 304, the UAV may be maneuvered to a predefined distance from the ground. The UAV may be maneuvered to the predefined distance when the network connection between the central server and the UAV is non-operational.
[0039] At block 306, an identifier associated with a first tag may be decoded. The first tag may be located within a predefined distance from a current location of the UAV. The first tag may be an RFID tag.
[0040] At block 308, navigational information mapped to the identifier associated with the first tag may be identified. The navigational information may be identified by comparing the identifier of the first tag with pre-stored identifiers associated with other tags.
[0041] At block 310, the UAV may be enabled to traverse to a second tag. The second tag may be located within a predefined range of the base location. Location details extracted from the second tag may be used to maneuver the UAV to the base location.
[0042] Although implementations for methods and systems for identifying relevant test cases have been described in language specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations for facilitating navigational-aid to an UAV.

WE CLAIM:
1. A system facilitating navigational-aid to an unmanned aerial vehicle (UAV), the system comprising:
a processor; and
a memory coupled with the processor, wherein the processor executes a plurality of modules stored in the memory, and wherein the plurality of modules comprises:
a maneuvering module configured to:
monitor a network connection between the UAV and a central server connected with the UAV;
enable maneuvering of the UAV to a predefined distance, from the ground, when the network connection between the UAV and the central server is non-operational; and
a navigational-aid module configured to navigate the UAV to a base location by:
decoding an identifier associated with a first tag located within a predefined range from a current location of the UAV;
identifying navigational information mapped to the identifier associated with the first tag; and
enabling the UAV to traverse to a second tag using the navigational information, wherein the second tag is located within a predefined range of the base location.
2. The system of claim 1, wherein the maneuvering module is further configured to maintain the UAV at the predefined distance from the ground till the UAV reaches the base location.
3. The system of claim 1, wherein the maneuvering module enables maneuvering of the UAV to the predefined distance, from the ground, after a predefined time delay from when the network connection between the UAV and the central server is non-operational.
12
4. The system of claim 1, wherein the first tag is an RFID tag and the second tag is a paper-based tag.
5. The system of claim 1, further comprising a sensor configured to calculate a current distance of the UAV from the ground.
6. The system of claim 1, further comprising a scanner configured to scan the identifier associated with the first tag.
7. The system of claim 1, further comprising:
a first camera configured to:
generate a first image to enable determining a current distance of the UAV from the second tag; and
a second camera configured to:
generate a second image to identify an identifier associated with the second tag.
8. The system of claim 7, wherein the first camera is a three-dimensional (3D) camera and the second camera is a two-dimensional (2D) camera.
9. A method for facilitating navigational-aid to an unmanned aerial vehicle (UAV), the method comprising:
monitoring, by a processor, a network connection between the UAV and a central server connected with the UAV;
enabling, by the processor, maneuvering of the UAV to a predefined distance, from the ground, when the network connection between the UAV and the central server is non-operational;
decoding, by the processor, an identifier associated with a first tag located within a predefined range from a current location of the UAV;
identifying, by the processor, navigational information mapped to the identifier associated with the first tag; and
enabling, by the processor, the UAV to traverse to a second tag using the navigational information, wherein the second tag is located within a predefined range of a base location.
13
10. The method of claim 9, further comprising enabling, by the processor, maintaining of the UAV at the predefined distance from the ground till the UAV reaches the base location.
11. The method of claim 9, further comprising enabling, by the processor, maneuvering of the UAV to the predefined distance, from the ground, after a predefined time delay from when the network connection between the UAV and the central server is non-operational.
12. The method of claim 9, further comprising scanning, by the processor, the identifier associated with the first tag.
13. The method of claim 9, wherein the first tag is an RFID tag and the second tag is a paper-based tag.
14. The method of claim 9, further comprising:
determining, by the processor, a current distance of the UAV from the second tag; and
identifying, by the processor, an identifier associated with the second tag.
15. The method of claim 9, further comprising calculating a current distance of the UAV from the ground.
16. A non-transitory computer readable medium embodying a program executable in a computing device for facilitating navigational-aid to an unmanned aerial vehicle (UAV), the program comprising:
a program code for monitoring a network connection between the UAV and a central server connected with the UAV;
a program code for enabling the maneuvering of the UAV to a predefined distance, from the ground, when the network connection between the UAV and the central server is disconnected;
a program code for decoding an identifier associated with a first tag located within a predefined range from a current location of the UAV;
14
a program code for identifying navigational information mapped to the identifier associated with the first tag; and
a program code for enabling the UAV to traverse to a second tag using the navigational information, wherein the second tag is located within a predefined range of a base location.