Claims:ProdyoVidhi Ref.: TCL0010IN
What is claimed is:
1. A navigation platform (101) comprising:
a first receiver (161) configured to receive a geographical landscape data from a map database (160), wherein the geographical landscape data comprises 3-dimentional landscape indicatives corresponding to a location wherein the location is indicated by latitude, longitude and altitude;
a second receiver (171) configured to receive a network availability data from a network availability database (170), wherein the network availability data comprises network signal strength indicatives corresponding to the location wherein the location is indicated by latitude, longitude and altitude; and
a flight controller (119) configured to adaptively determine one or more flight paths for an Unmanned Aerial Vehicle (UAV) operation based on the geographical landscape data and the network availability data, and the flight controller (119) is further configured to enable adaptive selection of one of the flight paths and remotely controlled navigation of a UAV (195) to execute the UAV-operation,
wherein the UAV-operation is indicated by a registration data comprising a telemetry data of the UAV, an operation data indicative of the UAV-operation, and a pilot data indicative of identity of a pilot.
2. The navigation platform of claim 1 wherein the navigation platform (101) is configured to receive real-time update of the network availability data from the UAV during the UAV-operation and the flight controller is configured to adaptively adjust the one or more flight paths based on the updated the network availability data.
3. The navigation platform of claim 1 wherein the navigation platform (101) comprises a map server (113) configured to receive the geographical landscape data, the network availability data, and the registration data and the map server is configured to validate the registration data/ feasibility of the UAV-operation.
4. The navigation platform of claim 3 wherein the map server (113) is configured to adaptively update the network availability data based on the real-time update of the network availability data received from the UAV during the UAV-operation.
5. The navigation platform of claim 1 wherein the flight controller (119) comprises:
a registration module (115), wherein the registration module is configured to receive the registration data;
a flight data engine (111) configured to adaptively determine one or more possible flight paths for the UAV-operation; and
a security module (117) configured to enable secure communication to and from the navigation platform.
6. The navigation platform of claim 1 wherein the navigation platform is coupled to an interface (135) via a console (120), wherein the interface (135) is configured to remotely control the UAV to execute the UAV-operation and to provide the registration data.
7. The navigation platform of claim 6 wherein the interface comprises: a pilot interface (130), and an aggregator interface (140), wherein the pilot interface (130) provides the pilot data and the aggregator interface provides the telemetry data and the operation data.
8. The navigation platform of claim 1 wherein the geographical landscape data includes an auxiliary data received from an auxiliary database (180), wherein the auxiliary data comprises one or more set of data indicative of meteorological data, air traffic data, charging pod location data corresponding to the location.
9. The navigation platform of claim 1 wherein the geographical landscape data includes a regulatory data received from a regulatory database (150), wherein the regulatory data comprises one or more set of data indicative of flying regulations governing the location.
10. The navigation platform of claim 1 wherein the network availability data is indicative of availability of a terrestrial communication network.
11. The navigation platform of claim 1 wherein the network availability data is indicative availability of any one of: a cellular network, a GSM/CDMA network, and a 3G/4G/5G/LTE/LORA network.
12. A method (300) of navigation of an Unmanned Aerial Vehicle (UAV) comprising:
receiving a registration data indicative on an UAV-operation, wherein the registration data comprising a telemetry data of the UAV, an operation data indicative of the UAV-operation, and a pilot data indicative of identity of a pilot and validating the registration data;
receiving a geographical landscape data, wherein the geographical landscape data is indicative of 3-dimentional landscape corresponding to a location wherein the location is indicated by latitude, longitude and altitude;
receiving a network availability data, wherein the network availability data comprises indicative network signal strength at the location wherein the location is indicated by latitude, longitude and altitude; and
adaptively determining one or more flight paths for the UAV-operation based on the geographical landscape data and the network availability data and enabling adaptive selection of one of the flight paths and enabling remotely controlled navigation of the UAV to execute the UAV-operation.
13. The method of claim 12 wherein the method includes receiving receive real-time update of the network availability data from the UAV during the UAV-operation and adaptively adjusting the one or more flight paths based on the updated the network availability data.
14. The method of claim 13 wherein the method includes adaptively updating the network availability data based on real-time update of the network availability data received from the UAV during the UAV-operation.
15. The method of claim 12 wherein receiving the geographical landscape data includes receiving an auxiliary data wherein the auxiliary data comprises one or more set of data indicative of meteorological data, air traffic data, charging pod location data corresponding to the location.
16. The method of claim 12 wherein receiving the geographical landscape data includes receiving a regulatory data, wherein the regulatory data comprises one or more set of data indicative of flying regulations governing the location.
17. The method of claim 12 wherein receiving the network availability data includes receiving data indicative of availability of a terrestrial communication network at the location.
18. The method of claim 12 wherein receiving the network availability data is indicative availability of any one of: a cellular network, a GSM/CDMA network, a 3G/4G/5G/LTE/LORA network.
19. A method of making a navigation platform (101) comprising:
providing a first receiver (161) configured to receive a geographical landscape data from a map database (160), wherein the geographical landscape data comprises 3-dimentional landscape indicatives corresponding to a location wherein the location is indicated by latitude, longitude and altitude;
providing a second receiver (171) configured to receive a network availability data from a network availability database (170), wherein the network availability data comprises signal strength indicatives corresponding to the location wherein the location is indicated by latitude, longitude and altitude; and
providing a flight controller (119) configured to adaptively determine one or more flight paths for an Unmanned Aerial Vehicle (UAV) operation based on the geographical landscape data and the network availability data and to enable adaptive selection of one of the flight paths and enable remotely controlled navigation of an UAV to execute the UAV-operation,
wherein the UAV-operation is indicated by registration data comprising telemetry data of the UAV, an operation data indicative of the UAV-operation, and pilot data indicative of identity of a pilot.
20. The method of claim 19 wherein the method includes configuring the navigation platform to receive real-time update of the network availability data from the UAV during the UAV-operation and to adaptively adjust the one or more flight paths based on the updated the network availability data.
21. The method of claim 19 wherein the method includes providing a map server (113) wherein the map server is configured to receive the geographical landscape data and the network availability data the registration data and the map server is configured to validate the registration data.
22. The method of claim 22 wherein the method includes configuring the map server (113) to adaptively update the network availability data based on real-time update of the network availability data received from the UAV during the UAV-operation.
23. The method of claim 19 wherein providing the flight controller comprises:
providing a registration module (115), wherein the registration module is configured to receive the registration data;
providing a flight data engine (111) configured to adaptively determine one or more possible flight paths for the UAV-operation; and
providing a security module (117) configured to enable secure communication to and from the navigation platform.
24. The method of claim 19 wherein the method includes coupling the navigation platform to an interface (135) via a console (120), wherein the interface (135) is configured to remotely control the UAV to execute the UAV-operation and to provide the registration data.
25. The method of claim 24 wherein the interface comprises: a pilot interface (130), and an aggregator interface (140), wherein the pilot interface (130) provides the pilot data and the aggregator interface provides the telemetry data and the operation data.
26. The method of claim 19 wherein the geographical landscape data includes an auxiliary data received from an auxiliary database, wherein the auxiliary data comprises one or more set of data indicative of meteorological data, air traffic data, charging pod location data corresponding to the location.
27. The method of claim 19 wherein the geographical landscape data includes a regulatory data received from a regulatory database (150), wherein the regulatory data comprises one or more set of data indicative of flying regulations governing the location.
28. The method of claim 19 wherein the network availability data is indicative of availability of a terrestrial communication network.
29. The method of claim 19 wherein the network availability data is indicative availability of any one of: a cellular network, a GSM/CDMA network, and a 3G/4G/5G/LTE/LORA network.
Dated this the 23rd day of January 2018
K. Pradeep
Of ProdyoVidhi
Agent for the Applicant
Registration Number: IN/PA-865
ProdyoVidhi Ref.: TCL0010IN , Description:ProdyoVidhi Ref.: TCL0010IN
“NAVIGATION SYSTEM AND METHOD THEREOF”
TECHNICAL FIELD
[001] The subject matter relates to a navigation system and a method thereof. More specifically, it relates to a navigation platform for the navigation system and method thereof. Even more specifically, it relates to the navigation platform for navigation of Unmanned Aerial Vehicles (UAVs) and the method thereof. More specifically the subject matter relates to the navigation platform configured to suggest an optimal flight path for navigation of the UAVs.
BACKGROUND
[002] UAVs have a number of applications in everyday life. Such applications vary from high-end military applications of surveillance/exploration, to entertainment applications such as clicking pictures and recording videos. Military UAV-operations deploy high end satellite communication technologies. High end sophisticated satellite communication system based UAV-operations are extremely expensive, skill and technology intensive, but are more reliable. Whereas for the purpose of entertainment applications, for example clicking pictures and recording videos, less expensive and easily available technologies such as wifi, radio spectrum are just sufficient and relatively cost effective, but limited by range of operation and are less reliable. In recent past drones or UAVs have attracted attention towards their commercial applications such as pick-up-and-delivery, surveillance etc. However, attempts to deploy UAVs on commercial scales have faced challenges in taking-off because of limitation of flying range of the UAVs, unreliability and cost. Therefore there is a need of a system and method that overcomes the above and other limitations.

SUMMARY
[003] It is therefore, one of the objects of the subject matter to provide a system and method that overcomes the above and other limitations. The subject matter provides a navigation system and a method thereof that solves the above and other problems. The subject matter provides a navigation platform that uses existing terrestrial network system for UAV-operation that increases range and reliability of the UAV-operation substantially to enable its use on commercial scale. The terrestrial communication system includes cellular, 4G/3G/LTE and similar networks such as LORA, 5G etc. The subject matter also provides features to remove challenges associated with the employment of the terrestrial communication system for UAV-operations. The navigation platform provides determining one or more optimal path based on geographical landscape data and network availability data that takes into account availability of network and geographical landscape at given longitude, latitude and altitude. Furthermore, present subject matter enables execution of UAV-operations on mass scale while complying with the flying regulations, by providing aggregator interfaces, pilot interfaces and regulator interface. The subject matter not only provides a solution for UAV applications that is a cost effective but also enables relatively long range flying possibilities. The subject matter also enables optimal flight path selection for a UAV-operation based on network, weather, telemetry data etc. The subject matter also enables real-time updation of optimal path and selection thereof.
[004] According to one aspect, the present subject matter provides a navigation platform comprising: a first receiver configured to receive a geographical landscape data from a map database, wherein the geographical landscape data comprises 3-dimentional landscape indicatives corresponding to a location wherein the location is indicated by latitude, longitude and altitude; a second receiver configured to receive a network availability data from a network availability database, wherein the network availability data comprises network signal strength indicatives corresponding to the location wherein the location is indicated by latitude, longitude and altitude; and a flight controller configured to adaptively determine one or more flight paths for an Unmanned Aerial Vehicle (UAV) operation based on the geographical landscape data and the network availability data, and the flight controller is further configured to enable adaptive selection of one of the flight paths and remotely controlled navigation of a UAV to execute the UAV-operation, wherein the UAV-operation is indicated by a registration data comprising a telemetry data of the UAV, an operation data indicative of the UAV-operation, and a pilot data indicative of identity of a pilot. In one embodiment, the navigation platform is configured to receive real-time update of the network availability data from the UAV during the UAV-operation and the flight controller is configured to adaptively adjust the one or more flight paths based on the updated the network availability data. In a second embodiment, the navigation platform comprises a map server configured to receive the geographical landscape data, the network availability data, and the registration data and the map server is configured to validate the registration data/ feasibility of the UAV-operation. In a third embodiment, the map server is configured to adaptively update the network availability data based on the real-time update of the network availability data received from the UAV during the UAV-operation. In a fourth embodiment, the flight controller comprises: a registration module, wherein the registration module is configured to receive the registration data; a flight data engine configured to adaptively determine one or more possible flight paths for the UAV-operation; and a security module configured to enable secure communication to and from the navigation platform. In a fifth embodiment, the navigation platform is coupled to an interface via a console, wherein the interface is configured to remotely control the UAV to execute the UAV-operation and to provide the registration data. In a sixth embodiment, the interface comprises: a pilot interface, and an aggregator interface, wherein the pilot interface provides the pilot data and the aggregator interface provides the telemetry data and the operation data. In a seventh embodiment, the geographical landscape data includes an auxiliary data received from an auxiliary database, wherein the auxiliary data comprises one or more set of data indicative of meteorological data, air traffic data, charging pod location data corresponding to the location. In an eighth embodiment, the geographical landscape data includes a regulatory data received from a regulatory database, wherein the regulatory data comprises one or more set of data indicative of flying regulations governing the location. In a ninth embodiment, the network availability data is indicative of availability of a terrestrial communication network. In a tenth embodiment, the network availability data is indicative availability of any one of: a cellular network, a GSM/CDMA network, and a 3G/4G/5G/LTE/LORA network.
[005] According to a second aspect, the subject matter provides a method of navigation of an Unmanned Aerial Vehicle (UAV) comprising: receiving a registration data indicative on an UAV-operation, wherein the registration data comprising a telemetry data of the UAV, an operation data indicative of the UAV-operation, and a pilot data indicative of identity of a pilot and validating the registration data; receiving a geographical landscape data, wherein the geographical landscape data is indicative of 3-dimentional landscape corresponding to a location wherein the location is indicated by latitude, longitude and altitude; receiving a network availability data, wherein the network availability data comprises indicative network signal strength at the location wherein the location is indicated by latitude, longitude and altitude; and adaptively determining one or more flight paths for the UAV-operation based on the geographical landscape data and the network availability data and enabling adaptive selection of one of the flight paths and enabling remotely controlled navigation of the UAV to execute the UAV-operation. In one embodiment, the method includes receiving receive real-time update of the network availability data from the UAV during the UAV-operation and adaptively adjusting the one or more flight paths based on the updated the network availability data. In a second embodiment the method includes adaptively updating the network availability data based on real-time update of the network availability data received from the UAV during the UAV-operation. In a third embodiment, receiving the geographical landscape data includes receiving an auxiliary data wherein the auxiliary data comprises one or more set of data indicative of meteorological data, air traffic data, charging pod location data corresponding to the location. In a fourth embodiment, receiving the geographical landscape data includes receiving a regulatory data, wherein the regulatory data comprises one or more set of data indicative of flying regulations governing the location. In a fifth embodiment, receiving the network availability data includes receiving data indicative of availability of a terrestrial communication network at the location. In a sixth embodiment, receiving the network availability data is indicative availability of any one of: a cellular network, a GSM/CDMA network, a 3G/4G/5G/LTE/LORA network.
[006] According to a third aspect, the subject matter provides another method of making a navigation platform comprising: providing a first receiver configured to receive a geographical landscape data from a map database, wherein the geographical landscape data comprises 3-dimentional landscape indicatives corresponding to a location wherein the location is indicated by latitude, longitude and altitude; providing a second receiver configured to receive a network availability data from a network availability database, wherein the network availability data comprises signal strength indicatives corresponding to the location wherein the location is indicated by latitude, longitude and altitude; and providing a flight controller configured to adaptively determine one or more flight paths for an Unmanned Aerial Vehicle (UAV) operation based on the geographical landscape data and the network availability data and to enable adaptive selection of one of the flight paths and enable remotely controlled navigation of an UAV to execute the UAV-operation, wherein the UAV-operation is indicated by registration data comprising telemetry data of the UAV, an operation data indicative of the UAV-operation, and pilot data indicative of identity of a pilot. In one embodiment, the method includes configuring the navigation platform to receive real-time update of the network availability data from the UAV during the UAV-operation and to adaptively adjust the one or more flight paths based on the updated the network availability data. In a second embodiment, the method includes providing a map server wherein the map server is configured to receive the geographical landscape data and the network availability data the registration data and the map server is configured to validate the registration data. In a third embodiment, the method includes configuring the map server to adaptively update the network availability data based on real-time update of the network availability data received from the UAV during the UAV-operation. In a fourth embodiment, providing the flight controller comprises: providing a registration module, wherein the registration module is configured to receive the registration data; providing a flight data engine configured to adaptively determine one or more possible flight paths for the UAV-operation; and providing a security module configured to enable secure communication to and from the navigation platform. In a fifth embodiment, the method includes coupling the navigation platform to an interface via a console, wherein the interface is configured to remotely control the UAV to execute the UAV-operation and to provide the registration data. In a sixth embodiment, the interface comprises: a pilot interface, and an aggregator interface, wherein the pilot interface provides the pilot data and the aggregator interface provides the telemetry data and the operation data. In a seventh embodiment, the geographical landscape data includes an auxiliary data received from an auxiliary database, wherein the auxiliary data comprises one or more set of data indicative of meteorological data, air traffic data, charging pod location data corresponding to the location. In an eighth embodiment, the geographical landscape data includes a regulatory data received from a regulatory database, wherein the regulatory data comprises one or more set of data indicative of flying regulations governing the location. In a ninth embodiment, the network availability data is indicative of availability of a terrestrial communication network. In a tenth embodiment, the network availability data is indicative availability of any one of: a cellular network, a GSM/CDMA network, and a 3G/4G/5G/LTE/LORA network.
[007] According to a fourth aspect, the present subject matter also provides a UAV and a method of making thereof, wherein the UAV is configured for receiving control and command from the navigation platform via a terrestrial network. The UAV is coupled to an onboard detector configured to detect signal strength of the terrestrial network and provide a real-time update/provide indicatives of the signal strength to the navigation platform of the present subject matter.
BRIEF DESCRIPTION OF DRAWINGS
[008] The subject matter is now described with reference to the accompanying figures, in that:
[009] FIG. 1 shows a schematic diagram of a navigation system according an embodiment of the present subject matter;
[0010] FIG. 2 shows a more detailed schematic diagram of a navigation platform of the navigation system according an embodiment of the present subject matter; and
[0011] FIG.3 shows a more detailed schematic diagram of a method according an embodiment of the present subject matter.
DETAILED DESCRIPTION
[0012] For a commercially successful application of UAVs, it is important that the operation is relatively cheaper, easily available, reliable and have reasonable range of operation. For the commercial effectiveness, mass-scale operations of UAVs are essential. The mass scale operations must not only be optimal in terms of cost and efficiency but also must be in compliance with all the safety and other regulations. Further, small UAV such as drone have only limited capacity to carry power/batteries therefore long flights for these UAVs are not practically possible. These and other limitations disable the UAV’s commercial use. Especially in payload delivery and other similar operations using UAV are not practically possible because of the above limitations. The subject matter provides a solution to the above and other problems. The present subject matter provides a navigation system that would not only enable the UAVs to fly beyond the visual line of sight but also, ensure that the drones/UAVs remain most effective in their operation by ensuring that they not only comply with Civil Aviation regulatory requirements but also address the power requirements for long flights.
[0013] The subject matter provides use of wireless communications system that is available on ground and is not dependent on satellite communication. Therefore avoiding expenses in utilization of satellite and skilled hours required for the same. The subject matter deploys terrestrial communications system for command and control of the UAV/drone. The terrestrial communication for the purpose of the present subject matter includes the wireless terrestrial communication systems. Such terrestrial communication systems may include but are not limited to 4G/3G /LTE/CDMA/GSM/5G/LORA communication systems. The subject matter provides determining the flight path in conjunction with flying altitude and geo-coordinates and continuous network availability in the flight path for the drone/UAV operation.
[0014] However, deploying terrestrial communications systems such as 4G/3G /LTE/CDMA for drone/UAV operation on commercial level is challenging because, the data indicative of the network availability of the terrestrial communications systems at a defined altitude of operation, at which the commercial UAVs are expected to fly, is somewhat questionable. Though often, the network signals are available at the desired altitudes, however data indicatively of the network signal strength is not available (which is required for reliability of an UAV-operation). This is because on an average no terrestrial communication network provider requires availability of network at such heights. The subject further provides solution for this problem, by adaptively adjusting flight path according to the network availability at a desirable altitude.
[0015] By reasonably enabling flights at such altitudes the subject matter provides an opportunity to adaptively checking (detecting) and confirming signal strength and build a more reliable data of network availability at different locations each location being identified by longitude, latitude and altitude. The present subject matter not only provides map servers that are adaptively updated and flight data engine that adaptively advises one or more optimal flight paths based on above variables, but also, provides interface that may be accessed by more than one entity for engaging UAVs in a UAV-operation. In some examples, such interfaces may include a pilot interface, wherein a pilot may access the navigation platform and fly an UAV through the navigation platform of the navigation system. In some other examples, the interface may be used by one or more UAV aggregators. Such UAV aggregators may be multiple independent parties supplying UAVs for any operation. A pilot from the pilot interface may select or be provided an UAV registered by an aggregator for a UAV-operation. In one example, the interface may be provided to regulatory agencies. The regulatory agencies may engage in ensuring that any or all the UAV-operations, conducted using the navigation platform, are in compliance with the regulatory requirements. More advantages and details of the navigation system according to the subject matter shall become further clear from the description of the FIG.s below.
[0016] FIG. 1 shows a schematic diagram of a navigation platform 101 of a navigation system according an embodiment of the present subject. FIG. 1 shows the navigation platform 101, a flight controller 119, a map database 160, a first receiver 161, a network availability database 170, and a second receiver 171.
[0017] According to this embodiment, the navigation platform 101 comprises the first receiver 161, the second receiver 171 and a flight controller 119. The first receiver 161 is coupled to the map database 160. The second receiver 171 is coupled to the network availability database 170. The operation of the navigation platform 101 may be understood as follows.
[0018] In some embodiments, the navigation platform 101 may receive geographical landscape data from the map database 160 via the first receiver 161. The map database 160 comprises 3-dimensional maps providing details of latitude, longitude and altitude of a region. The geographical landscape data comprises 3-dimentional landscape indicatives corresponding to a location indicated by latitude, longitude and altitude. In one example, the map database 160 may be commercial databases such as Google MapsTM, AirmapTM, UGCSTM etc.
[0019] In some embodiments, the navigation platform 101 may receive a network availability data from the network availability database 170 via the second receiver 171. The network availability data comprises network signal strength indicatives in a given region. The network availability data also provide signal strength indicatives corresponding to the location. The location is indicated by latitude, longitude and altitude. It shall become clear, after reading this specification, that the network availability data is indicative of availability of a terrestrial communication network. In some examples, the network availability data is indicative of availability of a cellular network e.g. GSM/CDMA network.
[0020] In some examples, the network platform 101 is provided with the flight controller 119. The flight controller 119 is configured to adaptively determine one or more possible flight paths for an Unmanned Aerial Vehicle (UAV) operation based on the geographical landscape data and the network availability data. The flight controller 119 is further configured to enable adaptive selection of one of the flight paths and enable remotely controlled navigation of an UAV to execute the UAV-operation. It shall become clear to a person, after reading this specification, that the UAV-operation is indicated by a registration data comprising a telemetry data of the UAV, an operation data indicative of the UAV-operation, and a pilot data indicative of identity of a pilot. In one example, the navigation platform 101 is configured to check and validate the registration data. More details of the subject matter shall become clear with reference to the following discussion.
[0021] FIG. 2 shows a more detailed a schematic diagram of the navigation system 100 according an embodiment of the present subject. The navigation system 100 includes the navigation platform 101, the flight controller 119, the map database 160, the first receiver 161, the network availability database 170, and the second receiver 171.The FIG. 2 further shows a flight data engine 111, a map server 113, a registration module 115, a security module 117 a console 120, an interface 135, a pilot interface 130, an aggregator interface 140, auxiliary interfaces 131 and 141 , a regulator interface 150, an auxiliary database 180, a terrestrial communication network 190 and UAVs 195-1, 195-2, 195-3, and 195-4 (collectively and severally referred to as “UAVs 195” or “UAV 195”), charging pods 185-1, 185-2, 185-3, and 185-4 (collectively and severally referred to as “charging pods 185” or “charging pod 185”).
[0022] In one example, the navigation system 100 may have following construction. The navigator platform 101 is coupled to the console 120, the regulator interface 150, the map database 160, the network availability database 170, the auxiliary database 180 and the terrestrial communication network 190. The navigation platform 101 may comprises the map server 113 and the flight controller 119. The flight controller 119 may comprise the flight data engine 111, the regulator module 115, and the security module 117. The console 120 is coupled to the interface 135. The interface 135 may comprise the pilot interface 130, the aggregator interface 140 and the auxiliary interfaces 131 and 141. The UAVs 195 may fly in a region covered by the terrestrial communication network 190 and the changing pods 185-1 through 185-4 may reside in the region covered by the terrestrial communication network 190.
[0023] The navigation system 100 is configured to enable execution of a UAV-operation. In one example, the console 120 enables access of the navigation platform 101 to the interfaces 135 and thereby enables remotely controlled execution of the UAV-operation through the interface 135. The console 120 may be configured on a cloud based solution. In one example, the console 120 may be a web portal. The interface 135 may include a number of parties. While the interface 135 enables access and communication between the navigation platform 101 and parties of interest, should also be clear that in some other examples, the party of interest may directly communicate with the navigation platform 101, an example of regulator interface 150 is shown in FIG. 2.
[0024] In some examples, the interface 135 includes the pilot interface 130, the aggregator interface 140 or any other interface to a party of interest. It shall become clear to a person after reading this specification, that the pilot interface 130, the aggregator interface 140 or any other interface to a party of interest do not need to be collocated in one premises and may be geographically spaced apart. It shall become clear to a person, after reading this specification that interface 135 may include a number of auxiliary interfaces shown by dashed blocks 131 and 141. Through these auxiliary interferes 131 and 141 other parties of interest such as a customer who wishes to order an UAV-operation for delivery of a payload may access the navigation platform 101 and place an order. In some other examples, through auxiliary interferes 131 and 141 a regulatory agency may access the navigation platform 101 and issue instructions or guidelines or control one or more UAV-operations. The auxiliary interfaces 131 and 141 may also include one or more of service providers, such as map database providers, metrological data providers, network availability database providers, or any other agency or party of interest (Not shown).
[0025] In one example, the interface 135 enables registration of the UAVs 195 via the aggregator interface 140. The aggregator interface 140 enables an aggregator to log her credentials and provide details to the navigation platform 101 for registration of the UAVs 195 in the registration module 115 at the navigation platform 101. The details inputted by the aggregator may be called the UAV registration details, thereby contributing in the registration data of the registration module 115. The aggregator interface 140 may provide a telemetry data, an operation data indicative of the UAV-operation to the registration module 115. The telemetry data include number of UAVs available, type of UAVs, payload capacity, battery capacity, and make, model, load carrying capacity, battery charge status, or other data specific to the UAV. The operation data may include origin and destination of the operation or any other data that is relevant for the purpose of execution of the UAV-operation. In some examples, the aggregator may also provide information relating to available pilots such as those pilots who may shortly become available to undertake a next UAV-operation based on status of an ongoing UAV-operation. In some other examples, navigation platform 101 may autonomously fly the UAV 195 without any assistance of the pilot. In some examples, one pilot may fly a number of UAVs 195. In some other examples, one or more of the UAVs 195 may be partially autonomously flown by the navigation platform 101 and role of the pilot is limited or minimal. In some examples, the aggregator interface 140 may receive data relevant for flight operation from a number of UAV vendor agencies. Thereby effectively aggregating UAV vendor agencies. It shall become clear to a person, after reading this specification, that the UAV vendor agencies may be independent UAV services companies approved for conducting UAV-operations in a region and may also include multiple independent pilots. In some examples, the aggregator interface 140 may receive details of the pilots available to fly, thereby effectively aggregating the available pilots. The details provided by the aggregator interface 140 may be called the aggregator registration details. In some examples, the aggregator interface 140 may include Input/Output (IO) devices such as joy stick, or flying controls configured to fly any class of UAVs, a keyboard, a display, a mouse etc.
[0026] In one example, the interface 135 enables registration of the pilots via the pilot interface 130. Thereby providing a pilot data indicative of identity of a pilot of the registration data to the registration module 115. The pilot interface 130 enables a pilot to log his credentials and provide details to the navigation platform 101. The details inputted by the pilots may be called the pilot registration details. The pilot data may also include details of the pilot license of the pilot, flying experience and pilot’s expertise in flying type of the UAV and any other data that may be relevant for the purpose of the UAV-operation and for the navigation platform 101 to assign the pilot a UAV 195 to fly. In one example, the pilot interface 130 may include Input/Output (IO) devices such as joy stick, or flying controls configured to fly any class of UAVs, a keyboard, a display, a mouse etc.
[0027] For avoidance of any doubt, the interface for the UAV pilots is referred to as the pilot interface 130 and the interface for aggregators is referred to as the aggregator interface 140. The aggregator interface 140 may be located where the UAV are physically located or may have access and controls of the UAV and corresponding telemetry data of UAVs. It shall become clear to a person, after reading this specification that there may be more than one pilot interface 130 and aggregator interface 140.
[0028] In some examples, the console 120 receives data and command signals via the interface 135 and provides it to the navigation platform 101 and vice-versa. In some examples, the data and command signals are received from the pilot interface 130. In some other examples, the data and command signals are received from the aggregator interface 140. In some other example both the pilot interface 130 and aggregator interface 140 substantially simultaneously provide data and command signals to the console 120. The console 120 provides the data and command signals to the navigation platform 101. In another example, the console 120 receives data and command signals from the navigation platform 101 and provides the same to the interface 135. It shall become clear to a person, after reading this specification, that the console 120 may receive the data, maps and flight paths from the navigation platform 101 and transmit them to the pilot interface 130 and the aggregator interface 140 or other parties of interest. In some examples, the pilot may select one of the flight paths provided by the navigation platform 101 and engage with the navigation platform 101 and thereby the aggregator interface 140 to execute the UAV-operation.
[0029] Some of the features of the navigation platform 101 shall become clearer to a person, after reading this specification. Some such features include the following. In some embodiments, the navigation platform 101 may receive real-time update of the geographical landscape data. The real-time updates may be received from the map database 160 or may be received from a UAV. In some other examples, the navigation platform 101 may be coupled to the map database 160 directly (as shown) or through the console 120 or via the interface 135 (Not shown). The 3-dimensional maps are synthesized and utilized by the navigation platform 101 in determining the flight paths of the UAVs 195.
[0030] FIG. 2 show the regulator interface 150 coupled to the navigation platform 101. It shall become clear to a person, after reading this specification, that in some examples, the regulator interface 150 may be a part of the interface 135. The regulator interface 150 be controlled and operated by one or more regulatory agencies, including but not limited to Civil Aviation Department, military or other regulatory agency. From the regulator interface 150 the navigation platform 101 may received inputs regarding airspace availability and fly/no-fly zones collectively known as regulatory inputs for further processing in the navigation platform 101. In some examples, the navigation platform 101 may provide real-time flight details the regulator interface 150. In one example, the regulator interface 150 may include ability to control flight path, or dynamically alter no-fly zones, and approve or disapprove any selected flight path for a drone operation. In some other examples, the regulator interface 150 may enable a regulator to log her credentials and provide details to the navigation platform 101 that may relate to the identity, authority and level of control that the regulator may exercise. The details provided by the regulator interface 150 may be called the regulator registration details. The aggregator interface 140 may include Input/Output (IO) devices such as joy stick, or flying controls configured to fly any class of UAVs, a keyboard, a display, a mouse etc. In one example, the regulator interface 150 may receive details of the pilots flying UAVs 195.
[0031] The navigation platform 101 receives the network availability data, relating to availability of network coverage from the network availability database 170. In one example, the navigation platform 101 may receive the geographical landscape data from the map database 160. The flight controller 119 determines one or more flight paths for the UAV-operation based on the network availability data and the geographical landscape data. The network availability data and the geographical landscape data are multi-dimensional in nature. For example, the geographical landscape data has information regarding geographical landscape at a location identified by longitude, latitude and altitude. Similarly, the network availability data has information regarding network/signal strength a/the location identified by longitude, latitude and altitude. This feature enables a number of advantages. While this feature ensures that the flight path for a UAV-operation remains within a region having reasonable network coverage that no-UAV may be allowed to fly in a zone/region which does not have the reasonable network. The reasonable network coverage may be defined by a minimal signal strength required for controlling a UAV 195 over the network. Because, network availability in the flight path of the UAV 195 has been assured, the network may now be used for controlling the UAV-operation thereby increasing considerably range of the UAV-operation beyond the line of sight at up to an extend the reasonable network coverage is available.
[0032] In one example, the UAVs 195 are configured to detect signal strength during the operation at a location identified by latitude, longitude and altitude. The detected signal strength is communicated to the navigation platform 101 as a real-time update of the network availability data. The navigation platform 101 is configured to receive the real-time update from the UAV 195 during the UAV-operation. The flight controller 119 is configured to adaptively adjust the one or more flight paths based on the updated the network availability data. Further, the map server 113 is configured to adaptively update the network availability data based on the real-time update.
[0033] FIG. 2 shows the network availability database 170 coupled to the navigation platform 101. It shall become clear, after reading this specification, that in some examples, the network availability database 170 may be coupled to the navigation platform 101 through the console 120 or through the interface 135. The network availability database 170 comprises 3-dimensional landscape strength of wireless network. In one example, the terrestrial communication network 190 is a 3G/4G/5G/LTE/LORA, network.
[0034] In one embodiment, the navigation platform 101 may be coupled to the auxiliary database 180. FIG. 2 show the auxiliary database 180 coupled to the navigation platform 101. It shall become clear, after reading this specification, that in some examples, the auxiliary database 180 may be coupled to the navigation platform 101 through the console 120 or through the interface 135. The auxiliary database 180 may provide one or more set of auxiliary data to the navigation platform 101. The data set may relate to a number of variables desirable for determining an optimal flight path, including but not limited to, meteorological data, air traffic data, location of charging pods 185 and their availability. The location of charging pods 185 and their availability is required for identifying flight paths with facilities for recharging of batteries of a UAV 195, if so required. The location of charging pods 185 is within the terrestrial communication network 190. The various data provided by the auxiliary database 180 are synthesized and utilized in the navigation platform 101 in determining the flight paths of the UAVs 195 by the flight controller 109.
[0035] The terrestrial communication network 190 provides a wireless network connection between the UAV 195 and the navigation platform 101. The navigation platform 101 is configured to establish communication between the console 120 and the UAVs 195 using the terrestrial communication network 190 and/or cloud based internet solutions. The navigation platform 101 is further configured to simultaneously receive the telemetry data and position data such as Global Positioning System (GPS) data from the UAV 195 while the UAV 195 is in flight, through the terrestrial communication network 190 and transmit them to the console 120. From the console 120, the real-time flight path followed by the UAV 195 in flight is transmitted to the pilot interface 130 and the aggregator interface 140.
[0036] The flight path determination by the navigation platform 101 may be understood as follows. The navigation platform 101 receives inputs from the interface 135 that is the pilot interface 130, the aggregator interface 140 etc. via the console 120 and determines origin and destination of a UAV-operation and determines if appropriate a UAV 195 and qualified pilot is available or not to execute a UAV-operation. The navigation platform 101 is configured to check and validate the registration data. The registration data include UAV registration details and pilot registration details. In one example, the map server 113 is configured to check and validate the registration data for initial approval the UAV-operation. If the UAV-operation is approved that the map server 113 may provide map details along with geographical landscape data and network availability data corresponding to the approved UAV-operation to the flight controller 119. The geographical landscape data includes the auxiliary data received from the auxiliary database 180. Such auxiliary data may include one or more set of data indicative of Subscriber identity Module (SIM) card, meteorological data, air traffic data, charging pod location data corresponding to the location. Effectively, the flight controller 119, the navigation platform 101 further determines one or more flight paths based on the data made available by the regulator interface 150, the map database 160, the network availability database 170, and the auxiliary database 180. More specifically the flight data engine 111 of the flight controller 119 determines the one or more flight paths based on the data made available by the map server 113. In some examples, the SIM card data is received from the aggregator interface 140 at the navigation platform 101. In some examples, the SIM card data is part of the registration data received at the navigation platform 101 from the aggregator interface 140.
[0037] The flight paths are then presented to the pilot interface 130 via the console 120. The pilot may then select any one of the flight path and execute the UAV-operation. While the UAV-operation is being executed a real-time feedback may be provided to the navigation platform 101 and/or regulator interface 150 regarding the terrestrial communication network availability, no-fly zone, etc. Details of such feedback have been discussed previously. The map server 113 may be updated in view of the feedback received from the UAV 195. In one example, the map server 113 may update network availability data based on the feedback and the map server 113 may provide the updated data to the flight data engine 111. In another example, the flight data engine 111 may determine the one or more flight paths based on the updated data made available by the map server 113 .The navigation platform 101 may adaptively update and flight path and advise the pilot interface 130 about more suitable or alternative flight path.
[0038] Further, the navigation platform 101 receives the regulatory inputs from the regulator interface 150. The navigation platform 101 acquires relevant 3-dimensional map data from the map database 160, relevant to the requirements of a flight between a specified origin and destination. This 3-D map data may be called selected map data. Further, the navigation platform 101 is configured to compare the selected map data and regulatory inputs in order to confirm the availability of air space for the flight between origin and destination. If the air space according to the selected map data is not available, the flight path generation is aborted and a corresponding message is outputted by the navigation platform 101 on the pilot interface 130 and the aggregator interface 140.
[0039] The navigation platform 101 is configured to check the enabling conditions of the flight of any one or more of the UAV 195 from the auxiliary database 180. The enabling conditions that are to be checked and verified are meteorological data, air traffic data and the data relating to charging pods 185 such as locations and their availability. If the electrical charging of on-board batteries of the UAV 195 is likely to be required during a UAV-operation the one or more flight paths are determined by the flight data engine 111 based on the data relating to charging pods 185 such as their locations and their availability. Charging pods 185 may also be referred to as charging platforms. The selected and verified map data is obtained after meeting all the conditions. The navigation platform 101 is configured to use the selected and verified map data to generate one or more flight paths. The generated flight paths are presented to the pilot through the pilot interface 130, and in some examples to the aggregator interface 140 or other relevant interfaces such as regulator interface 150. The navigation platform 101 is configured to receive one of the paths manually selected by the pilot and aggregator in agreement with each other.
[0040] Once the flight path is selected, the navigation platform 101 is configured to establish communication between the UAV 195 and the pilot interface 130. A secured channel may be established using the security module 117. The UAV 195 is now ready to be controlled by the pilot through the flying controls available in the pilot interface 130. The UAV 195 is flown from the origin to the destination at the specified height. Location, height and a few other telemetry parameters that are useful in monitoring the UAV 195 while in flight are received by the navigation platform 101 through the terrestrial communication network 190. The selected flight path and the track of the UAV 195 while in flight are displayed on the pilot interface 130 and the aggregator interface 140 it may also be displayed on the regulator interface 150.
[0041] The present subject matter also provides options for unforeseen or emergency situations during a UAV-operation. Such unforeseen or emergency situation may arise due to loss of communication between the navigation system 100 or very poor signal strength for communication resulting in a possibility of getting the UAV 195 disconnected from the command and control of the navigation platform 101. In the event of reduction of signal strength below a pre-determined threshold level, the navigation platform 101 is configured to sense the possibility of an emergency situation and adaptively change over to one of the alternate flight paths already selected and kept in a priority list. In another possibility, the navigation platform 101 prior to undertaking the UAV-operation provides predetermined locations to the UAV 195. The predetermined locations are determined based on the network availability data showing acceptable signal strength. The UAV 195 may be configured auto fly to one of the closest predetermined location in the event of loss of communication between the navigation system 101. In some examples, the predetermined locations may be the locations of the charging pods 185.
[0042] The present subject matter also provides a method 300 of navigating a UAV. FIG. 3 shows a schematic diagram of the method 300. It shall become clear to a person, after reading this specification, that the method 300 may be practiced at the navigation system 100 of FIG. 2; even more specifically the method 300 may be practiced using the navigation platform 101 of FIG. 1 or FIG. 2. Further it shall become clear, after reading this specification, that for practising the method 300 one or more features of the navigation system 100 may be remotely located and physical collocation of any feature is not a limitation for practising the subject matter. For more clarity and better understanding the method 300 is being described with reference to the FIG. 3 and FIG. 2.
[0043] According to the method 300, at block 301, a registration data may be received at the navigation platform 101. The registration data may be received from the interfaces 135 such as the pilot interface 130 and the aggregator interface 140. The registration data may be received at the registration module 115. The registration data is indicative on an UAV-operation and may comprising a telemetry data of the UAV 195, an operation data indicative of the UAV-operation, and a pilot data indicative of identity of a pilot. In some examples, the registration module 115 may have a capability to validate the registration data by comparing the data stored in the registration module 115 and received the registration data, for example, pilot credentials etc.
[0044] At block 303, a geographical landscape data and a network availability data may be received at the navigation platform 101. More specifically, the geographical landscape data and the network availability data may be received at the map server 113 of the navigation platform 101. In one possibility, the geographical landscape data may be received from the map database 160. In one possibility, the network availability data may be received from the network availability database 170. The geographical landscape data is indicative of 3-dimentional landscape corresponding to a location. The network availability data comprises network signal strength indicatives at the location. The location is indicated by latitude, longitude and altitude.
[0045] Block 313 shows more detailed aspects of the block 303 according to an embodiment of the method 300. At block 313 along with the geographical landscape data a number of other data sets (called auxiliary data) may also be received. Each data set may be received from a different data provider or agency. For example, the auxiliary data may include indicatives of meteorological data that may be received from a meteorological data provider. In another example, the auxiliary data may include indicatives of air traffic data that may be received from an air traffic controller. In another example, the auxiliary data may include indicatives of charging pod location and their instantaneous availability. Similarly, the geographical landscape data may include a regulatory data, the regulatory data comprises one or more set of data indicative of flying regulations governing the location for example no-fly zones etc. In some examples, the map server 113 may validate the registration data. In that the map server 113 may compare availability of a pilot with credentials to fly the UAV 195 or execute the UAV-operation. In some other examples, the map server 113 may determine feasibility of the UAV-operation based on UAV-operation details, such as origin and/or designation of the UAV-operation being in no fly zone.
[0046] Block 323 shows more detailed aspects of the block 303 according to an embodiment of the method 300. At block 323 the network availability data may be received. The network availability data may be received from a service provider at the map server 113. The network availability data is indicative of strength of network signals at the location. In one aspect, the network availability data includes data indicative of availability of any available terrestrial communication network, a cellular network, a GSM/CDMA network like, but not limited to 3G/4G/LTE/5G/LORA network.
[0047] At block 305, the navigation platform 101 may determine one or more possible flight paths for the UAV-operation based on the geographical landscape data, the network availability data and the registration data. More specifically, the flight data engine 111 may determine the flight paths. At this block 303, the flight paths may be presented to the pilot who may select one of the flight paths for the UAV-operation and navigate the UAV 195 to execute the UAV-operation. The flight paths may be presented to the pilot via the console 120 to the pilot interface 130. The pilot may after selecting the desired flight path remotely fly the UAV 195 using the navigation platform 101. Thereby, at block 303 adaptive selection of one of the flight paths remotely controlled navigation of the UAV195-1 to 195-4 to execute the UAV-operation is enabled.
[0048] Block 315, shows more detailed aspects of the block 305 according to an embodiment of the method 300. At block 315, the method provides adaptive determination of flight paths based on based on instantaneous the geographical landscape data and the network availability data, and the auxiliary data corresponding to the location. For enabling adaptive determination of flight paths, the method 300 provides for receiving real-time update of the network availability data. In one possibility, the real-time updates may be received from the UAV 195 during the UAV-operation. In some other possibility, the real-time updates may be received from UAVs 195 that are flying in close vicinity of the location. In some other possibility, the real-time updates may be received from the network availability database 170. Based on the real-time updates, the one or more flight paths may be adaptively adjusted by the flight data engine 111. In one possibility adaptively adjusted the one or more flight paths may be presented to the pilot at the pilot interface 130 by the navigation platform 101 through the console 120, thereby enabling adaptive selection of one of the flight paths by the pilot and enabling remotely controlled navigation of the UAV to execute the UAV-operation. In one possibility the map server 113 maybe updated based on the real-time updates. In one example, the flight data engine 111 extrapolates instantaneous real-time updates of signal strength received within a period of time from an UAV 195 and determines reducing, increasing and/or stable signal strength pattern in a given direction and accordingly updates the flight path of the UAV 195 based on the pattern.
[0049] Block 325, shows more detailed aspects of the block 305 according to an embodiment of the method 300. At block 325, a secure communication channel may be established for communicating data to and from the network platform 101. In some examples, the security module 117 may be employed for establishment of the secure communication channel.
[0050] The present subject matter also provides a method of making the navigation platform 101 of FIG. 2 for navigating a UAV 195 to execute a UAV-operation. It shall become clear to a person, after reading this specification that the method may be further extended to manufacture the navigation system 100 of FIG. 2. The navigation platform 101 may be manufactured by providing the first receiver 161, the second receiver 171 and the flight controller 119 and configuring them as enable features discussed with reference to FIG. 2. Further, the navigation platform 101 may be provided with the map server 113 and the flight controller 119 may be provided with the flight data engine 111, the registration module 115, and the security module 117. The navigation platform 101 is further configured to engage with the console 120 and the console 120 is coupled to the interfaces 135 to enable communication between the navigation platform 101 and the aggregator interface 140/pilot interface 130.
[0051] The present subject matter also provides a UAV 195. The UAV 195 is configured for receiving control and command from the navigation platform 101 via a terrestrial network. The UAV 195 may have a slot to mount SIM card. The UAV 195 has a network signal strength detector to detect signal strength of the terrestrial network and provide a real-time update/provide indicatives of the signal strength to the navigation platform 101.
[0052] The following shall become clear, after reading this specification. The subject matter may be practiced in a manner different than what is discussed herein without departing from the spirit and scope of this specification. The embodiments discussed herein are susceptible to modifications and alternative embodiments. The drawings may not be to the scale, and/or emphasize some features and some others may be omitted. The subject matter may describe some features using terminologies in singular forms "a", "an", and "the" but these features also include plural references unless the context clearly expressly dictates otherwise. Use of reference numerals in claims (in parentheses) and other parts of specification are solely for the purpose of meeting the official requirements and/or clarity and are no way limiting the scope of the subject matter. All embodiments, modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter without regards whether such embodiments are discussed herein or not are also covered. Some proprietary terms and/or expression, including trademarks/trade-names or other copyrighted subject matter may have been used in this specification. The applicant(s) acknowledge(s) the ownership of the proprietary subject matter and any inadvertent omission in acknowledgement is unintentional and without any malicious intention.

ProdyoVidhi Ref.: TCL0010IN