FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
[SEE SECTION 10, RULE 13]
A METHOD FOR DELIVERING PRODUCTS USING AN UNMANNED AERIAL VEHICLE (UAV)
ASTEROID MOTORS PVT. LTD.
AN INDIAN RESIDENT HAVING ADDRESS AT
B 1107 ANNEXE SOCIETY, OPP. GOLD’S GYM, MAGARPATTA, HADAPSAR,
PUNE, INDIA 411028
THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF INVENTION
[0001] The present disclosure relates generally to a product delivery method and system and more particularly relates to a product delivery to high rise/ multi stories buildings, low rise buildings/ bungalows, any other building’s structure or on ground using unmanned aerial vehicles (UAVs) or drones.
BACKGROUND OF THE INVENTION
[0002] Drones are also known as Unmanned Aerial Vehicles (UAV), which were previously limited to use in military applications are now rapidly getting utilised in industrial, research and consumer markets. Many big and small companies’ package and delivers items and/or group of items (e.g., apparel, books, food, groceries, medicines, etc.) together for variety of purposes, such as e-commerce, food delivery, groceries delivery or any company or business which package items and deliver to their users for fulfilling their orders. Typically package items are packed in boxes or bags to be shipped to any residence or users’ location. Physical delivery of goods to user’s location has been improving over the years, with some big and small businesses attempting to minimize delay between user placing an order to getting it delivered with companies providing same day delivery or next day delivery and in some cases 30 minutes delivery. The package delivery to the user is being done by a traditional method which is human delivering to user’s location (e.g., A delivery person goes to pick up location, picks package, comes by their shipping carrier, which can be two wheeler, three wheeler or four wheeler vehicle which is driven by the delivering person or the driver to user’s location after picking up the packages from ware house or business location) and then delivery person may hand over the delivery package to the user or deliver near to user’s

door or gate, which is a long process, time consuming and not cost effective. And in order to provide same day delivery or next day delivery or in some cases 30 minutes delivery, companies have to create small sized warehouses or dark houses in all the areas where fast deliveries are provided, which also adds up cost in the operations of delivery.
OBJECT
[0003] Primary object of the present invention is to deliver packages (e.g., apparel, books, food, groceries, medicines etc.) in or to high rise/ multi stories buildings, low rise buildings/ bungalows, any other buildings structure or on ground to users, safely and securely using Unmanned Aerial Vehicles (UAV) or drones with identifying or defining delivery locations according to the three dimensional (3D) building model maps data or two dimensional (2D) building footprints data, geographic coordinates (e.g., latitude, longitude and altitude) of all the predefined points including delivery package pick up location and users delivery location.
[0004] Another objective is to use 2D building footprints and 3D buildings model from map data to locate and identify the exact location of delivery package pick up points and drop off points of users in maps. 2D or 3D buildings model in maps may be also integrated in mobile application in user interface for showing live location or progress of their drone delivery orders.
[0005] Another objective is to collect and store data (e.g., latitude, longitude and altitude) on server of all pre-defined geographic points in 2D or 3D geographic maps developer(s) for easy, safer, accurate and efficient drone deliveries.
[0006] Another objective is to define drone path for all the drone to travel

from pickup points to delivery/ deliveries points or to any common points or charging points elevated from ground. Server with geographic coordinates, including latitude, longitude, altitude and area of pre-defined drone delivery paths/ lanes. Pre-defined drone delivery paths are created from pickup locations to delivery locations for faster, safer possible deliveries and for avoiding any collision of drones making deliveries. Drone paths may be defined on the bases of maximum drone flight altitude allowed in particular area, usual weather data in area of pickup location and drop off location of user, after avoiding trees, wires or any other objects etc. More than one path may be created in layers for drones to travel, which may be used for different payload capacity of drones. Top layer/ path may be assigned for drones with payload capacity of 5 to 7 kgs, second path for payload capacity of 2 to 3 kgs, one alternate path above the top layer and one another alternate path below the second path for drones to switch lanes/ paths in case of multiple drones travelling on the same route).
SUMMARY
[0007] This summary is provided to introduce concepts related to a method for delivering products using Unmanned Aerial Vehicle (UAV). This summary is neither intended to identify essential features of the present invention nor intended to determine or limit the scope of the present invention.
[0008] In an embodiment of the present invention, a method and system for product delivery using Unmanned Aerial Vehicle (UAV) is disclosed. The method includes generating, by the processor, one or more paths to be traversed by a UAV based on one or more parameters. One or more parameters comprise maximum UAV flight altitude allowed in an area and

weather data of the area, other UAV in the area, a start point and an end point. One or more paths are in layers, UAV associated with different payload capacity of UAV. A time required to traverse for each of the one or more paths is computed by the processor. Navigating, by the processor, the UAV over a path selected from the one or more paths based on comparison of the time required to traverse to deliver the product at user’s location.
[0009] The system for delivering products using Unmanned Aerial Vehicle (UAV) comprises a generating module, coupled with the processor. The generating module generates one or more paths to be traversed by a UAV based on one or more parameters. The one or more Parameters comprise maximum UAV (116) flight altitude allowed in an area and weather data of the area, other UAV in the area, a start point, and an end point. One or more paths are in layers, UAV (116) associated with different payload capacity of UAV (116). A computing module is coupled with the processor. The computing module computes a time require to traverse for each of the one or more paths. A navigating module is coupled with the processor. The navigating module navigates the UAV over a path selected from the one or more paths based on comparison of the time require to traverse to deliver the product at user’s location.
BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS
[0010] The foregoing detailed description of embodiments is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the disclosure, there is shown in the present document example constructions of the disclosure; however, the disclosure is not limited to the specific methods and apparatus disclosed in the document and the drawings.

[0011] Figure 1 illustrates a schematic block diagram of a drone, in accordance with an implementation of the present disclosure.
[0012] Figure 2 illustrates an example block diagram of the system for drone deliveries in high rise/ multi stories buildings, low rise buildings or any other building’s structure in accordance with an implementation of the present disclosure.
[0013] Figure 3 illustrates an example overall schematic view of drone deliveries in high rise/ multi stories buildings, low rise buildings or any other buildings structure in two dimensional and three-dimensional geographic maps, including drones and drone delivery paths in accordance with an implementation of the present disclosure.
[0014] Figure 4 illustrates an example perspective view of two-dimensional representation of three-dimensional buildings model and objects (trees, towers and wires) in accordance with an implementation of the present disclosure.
[0015] Figure 5 illustrates an example top-down view of buildings footprints and objects in two dimensional geographic maps in accordance with an implementation of the present disclosure.
[0016] Figure 6 illustrates an example perspective view of buildings model and objects, with highlighting one building model and its dimensions in accordance with an implementation of the present disclosure.
[0017] Figure 7 illustrates an example perspective view of buildings model and objects, with highlighting one building model, floor separating lines, its dimensions and drone delivery pads in accordance with an implementation of the present disclosure.

[0018] Figure 8 illustrates an example perspective view of buildings model and objects, with highlighting one building model with floor separating lines, its dimensions and drone delivery pads, and one other building model, its dimensions without floor separating lines, and drone delivery pads in accordance with an implementation of the present disclosure.
[0019] Figure 9(A) illustrates an example perspective view of buildings model and objects, with highlighting one building model, floor separating lines, its dimensions, drone delivery pads, drone delivery path and a drone in accordance with an implementation of the present disclosure.
[0020] Figure 9(B) illustrates an example side cross sectional view of detailed multi layered drone delivery paths/ lanes, including side cross section of building model in accordance with an implementation of the present disclosure.
[0021] Figure 10 illustrates an example top-down cross section view of a building with building buffer zone rectangle/ lines, drone delivery check points around the building in accordance with an implementation of the present disclosure.
[0022] Figure 11 illustrates an example front cross section view of a building including common building buffer zone rectangle lines, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (23), floor check points, drone delivery pads, drone delivery pads check points, buffer zone rectangles/ line(s) dimension and building dimensions in accordance with an implementation of the present disclosure.
[0023] Figure 12 illustrates an example side cross section view of a building, including common building buffer zone rectangle line, common building check points elevated or at a distance from building, floor buffer zone

rectangles/ line(s) (23), floor check points, drone delivery pads, delivery pads check points, buffer zone rectangles/ line(s) dimension and building dimensions in accordance with an implementation of the present disclosure.
[0024] Figure 13 illustrates an example perspective cross section view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s), floor check points, drone delivery pads (only on some floors where users registered), delivery pads check points, buffer zone rectangles/ line(s) dimension, floor separating rectangles/ lines and building dimensions in accordance with an implementation of the present disclosure.
[0025] Figure 14 illustrates an example perspective cross section view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (pre-defined on all the floors), floor check points (pre-defined on all the floors), drone delivery pads (on register users’ floors/ flats), delivery pads check points, buffer zone rectangles/ line(s) dimensions, floor separating rectangles/ lines and building dimensions in accordance with an implementation of the present disclosure.
[0026] Figure 15 illustrates an example perspective cross section view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (pre-defined on all the floors), floor check points (only on some floors where users registered), drone delivery pads (on register users’ floors/ flats), delivery pads check points, buffer zone rectangles/ line(s) dimensions, floor separating rectangles/ lines and

building dimensions in accordance with an implementation of the present disclosure.
[0027] Figure 16 illustrates an example perspective view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (pre-defined on all the floors), floor check points (pre-defined on all the floors), drone delivery pads (on register users’ floors/ flats), delivery pads check points, buffer zone rectangles/ line(s) dimensions, floor separating rectangles/ lines, drone delivery paths/ lanes, drone, drone delivery package and building dimensions in accordance with an implementation of the present disclosure.
[0028] Figure 17 illustrates an example perspective view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check points (only on some floors/ flats where users registered), drone delivery pads (on register users’ floors/ flats), delivery pads check points, buffer zone rectangles/ line(s) dimensions, floor separating rectangles/ lines with drone carrying drone delivery package on drone delivery paths/ lanes and building dimensions in accordance with an implementation of the present disclosure.
[0029] Figure 18 illustrates an example perspective view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check points (only on some floors/ flats where users registered), drone delivery pads (on register users’ floors/ flats), delivery pads check points, buffer zone rectangles/ line(s) dimensions (length and width), floor separating

rectangles/ lines with drone carrying drone delivery package on common building check point of common building buffer zone rectangle/ line(s) and building dimensions in accordance with an implementation of the present disclosure.
[0030] Figure 19 illustrates an example perspective view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check points (only on some floors/ flats where users registered), drone delivery pads (on register users’ floors/ flats), delivery pads check points, buffer zone rectangles/ line(s) dimensions (length and width), floor separating rectangles/ lines with drone carrying drone delivery package on floor buffer zone check point of floor buffer zone rectangle/ line(s) and building dimensions in accordance with an implementation of the present disclosure.
[0031] Figure 20 illustrates an example perspective enlarged view of figure 18, including building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check point (only on some floors/ flats where users registered), drone delivery pad (on register users’ floors/ flats), delivery pads check point (Herein, for detailed example one drone delivery pad with one delivery check point is shown), floor separating rectangles/ lines with drone carrying delivery package on floor buffer zone check point of floor buffer zone rectangle/ line(s), building dimensions, one or more delivery pad barcodes on drone delivery pad, one or more wall barcode(s) may be sticked or kept on building in accordance with an implementation of the present disclosure.
[0032] Figure 21 illustrates an example perspective enlarged view of a building, including common building buffer zone rectangle, common

building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check points (only on some floors/ flats where users registered), drone delivery pad (on register users’ floors/ flats), delivery pads check point (Herein, for detailed example one drone delivery pad with one delivery check point is shown), buffer zone rectangles/ line(s) dimensions (length and width), building dimensions, floor separating rectangles/ lines with drone carrying drone delivery package on floor buffer zone check point of floor buffer zone rectangle/ line(s), one or more delivery pad barcodes on drone delivery pad (for example, four barcodes), where number of barcodes depend on requirement of drone to land, barcodes are used to navigate drone to land drone precisely in process of drone to land in centre of drone delivery pad, one or more wall barcode(s) may be sticked or kept on building for drones to identify exact location of drone delivery pad on building in accordance with an implementation of the present disclosure.
[0033] Figure 22 illustrates an example perspective enlarged view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check points (only on some floors/ flats where users registered), drone delivery pad (on register users’ floors/ flats), delivery pads check point (Herein, for detailed example one drone delivery pad with one delivery check point is shown), buffer zone rectangles/ line(s) dimensions (length and width), building dimensions, floor separating rectangles/ lines with drone carrying drone delivery package horizontally near/ in front of drone delivery pad check point from floor buffer zone check point of floor buffer zone rectangle/ line(s), one or more delivery pad barcodes on drone delivery pad (for example, four barcodes), where number of barcodes

depend on requirement of drone to land, barcodes are used navigate drone to land drone precisely in process of drone to land in centre of drone delivery pad, one or more wall barcode(s) may be sticked or kept on building for drones to identify exact location of drone delivery pad on building in accordance with an implementation of the present disclosure.
[0034] Figure 23 illustrates an example perspective enlarged view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check points (only on some floors/ flats where users registered), drone delivery pad (on register users’ floors/ flats), delivery pads check point (Herein, for detailed example one drone delivery pad with one delivery check point is shown), buffer zone rectangles/ line(s) dimensions (length and width), building dimensions, floor separating rectangles/ lines with drone carrying drone delivery package on delivery pad check point of on drone delivery pad, one or more delivery pad barcodes on drone delivery pad (for example, four barcodes), where number of barcodes depend on requirement of drone to land, barcodes are used navigate drone to land drone precisely in process of drone to land in centre of drone delivery pad, one or more wall barcode(s) may be sticked or kept on building for drones to identify exact location of drone delivery pad on building in accordance with an implementation of the present disclosure.
[0035] Figure 24 illustrates an example perspective enlarged view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check points (only on some floors/ flats where users registered), drone delivery pad (on register users’ floors/ flats), delivery pads check point

(Herein, for detailed example one drone delivery pad with one delivery check point is shown), buffer zone rectangles/ line(s) dimensions (length and width), building dimensions, floor separating rectangles/ lines with drone carrying drone delivery package on way to return to common building buffer zone check point from delivery pad check point (from the same route drone came by) after dropping delivery package, one or more delivery pad barcodes on drone delivery pad (for example, four barcodes), where number of barcodes depend on requirement of drone to land, barcodes are used navigate drone to land drone precisely in process of drone to land in centre of drone delivery pad, one or more wall barcode(s) may be sticked or kept on building for drones to identify exact location of drone delivery pad on building in accordance with an implementation of the present disclosure.
[0036] Figure 25 illustrates an example perspective enlarged view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check points (only on some floors/ flats where users registered), drone delivery pad (on register users’ floors/ flats), delivery pads check point (Herein, for detailed example one drone delivery pad with one delivery check point is shown), buffer zone rectangles/ line(s) dimensions (length and width), building dimensions, floor separating rectangles/ lines with drone carrying drone delivery package returned to common building buffer zone check point from delivery pad check point (from the same route drone came by) after dropping delivery package, one or more delivery pad barcodes on drone delivery pad (for example, four barcodes), where number of barcodes depend on requirement of drone to land, barcodes are used navigate drone to land drone precisely in process of drone to land in

centre of drone delivery pad, one or more wall barcode(s) may be sticked or kept on building for drones to identify exact location of drone delivery pad on building in accordance with an implementation of the present disclosure.
[0037] Figure 26 illustrates an example perspective enlarged view of a building, including common building buffer zone rectangle, common building check points elevated or at a distance from building, floor buffer zone rectangles/ line(s) (only on some floors/ flats where users registered), floor check points (only on some floors/ flats where users registered), drone delivery pad (on register users’ floors/ flats), delivery pads check point (Herein, for detailed example one drone delivery pad with one delivery check point is shown), buffer zone rectangles/ line(s) dimensions (length and width), building dimensions, floor separating rectangles/ lines with drone carrying drone delivery package on the way returning to pick up point, charging point or any other point defined by server from delivery pad check point after dropping delivery package, one or more delivery pad barcodes on drone delivery pad (for example, four barcodes), where number of barcodes depend on requirement of drone to land, barcodes are used navigate drone to land drone precisely in process of drone to land in centre of drone delivery pad, one or more wall barcode(s) may be sticked or kept on building for drones to identify exact location of drone delivery pad on building in accordance with an implementation of the present disclosure.
[0038] Figure 27 illustrates an example block diagram of system for drone in accordance with an implementation of the present disclosure.
[0039] Figure 28 illustrates an example flow chart for the drone of Figure 27 in accordance with an implementation of the present disclosure.

[0040] Figure 29 illustrates an example block diagram of system for server in accordance with an implementation of the present disclosure.
[0041] Figure 30 illustrate an example flow chart for the server of Figure 29 in accordance with an implementation of the present disclosure.
[0042] Figure 31 illustrates graphical user interface representation of mobile device and its display, including building model integrated with mobile app user interface, delivery information, user’s building location and a drone on its way to deliver a delivery package, in accordance with an implementation of the present disclosure.
[0043] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present invention. Similarly, it will be appreciated that any flow charts, flow diagrams, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
DETAILED DESCRIPTION
[0044] The various embodiments of the present invention provide a system and method for delivering products using UAV. In the following description, for purpose of explanation, specific details are set forth in order to provide an understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these details.
[0045] One skilled in the art will recognize that embodiments of the present invention, some of which are described below, may be incorporated into a number of systems. However, the systems and methods are not limited to the specific embodiments described herein. Further, structures and devices

shown in the figures are illustrative of exemplary embodiments of the present invention and are meant to avoid obscuring of the present invention.
[0046] Furthermore, connections between components and/or modules within the figures are not intended to be limited to direct connections. Rather, these components and modules may be modified, re-formatted or otherwise changed by intermediary components and modules.
[0047] References in the present disclosure to “one embodiment” or “an embodiment” mean that a particular feature, structure, characteristic, or function described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
[0048] This invention disclosure describes system and methods for utilising unmanned aerial vehicle (UAV) or may be referred to as a drone, two-dimensional or three-dimensional (2D or 3D) building models in geographic maps and geographic coordinates (e.g., latitude, longitude and altitude) to facilitate deliveries to users.
[0049] The invention is described below with the help of examples and is not intended to limit described invention or use of the described invention. It is also understood that purpose of description herein, specific dimensions or physical characteristics relating to the invention in description and figures disclosed are not to be considered as limiting, unless the claims specifically state otherwise.
[0050] Some embodiments of this disclosure, illustrating all its features, will now be discussed in detail. The words "comprising," "having," "containing," and "including," and other forms thereof, are intended to be

equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise. Although any system and methods for recommending one or more products to the buyer, similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present disclosure, the exemplary, system and methods are now described. The disclosed embodiments for enabling selective access to enterprises applications are merely examples of the disclosure, which may be embodied in various forms.
[0051] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. For example, although the present disclosure will be described in the context of a system and a method for recommending one or more products to the buyer, one of ordinary skill in the art will readily recognize that the method and system can be utilized in any situation where there is need to deliver packages to customer’s location. Thus, the present disclosure is not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0052] Figure 1 illustrates an exemplary block diagram depicting a drone 116, according to an exemplary implementation of the present invention. The computer implemented system 102 includes a network 104 a plurality of user devices 106 (106-1, 106-2, 106-3, 106-4), a database 207 and a server 110.
[0053] The network 104 interconnects the user devices (106), the database 207 and the server 110 with the drone 116. The network 104 includes wired

and wireless networks. Examples of the wired networks include a Wide Area Network (WAN) or a Local Area Network (LAN), a client-server network, a peer-to-peer network, and so forth. Examples of the wireless networks include Wi-Fi, a Global System for Mobile communications (GSM) network, and a General Packet Radio Service (GPRS) network, an enhanced data GSM environment (EDGE) network, 802.5 communication networks, Code Division Multiple Access (CDMA) networks, or Bluetooth networks.
[0054] In the present implementation, the database 207 may be implemented as enterprise database, remote database, local database, and the like. The database 207 may be located within the vicinity of the drone 116 or may be located at different geographic locations as compared to that of the drone 116. Further, the database 207 may themselves be located either within the vicinity of each other, or may be located at different geographic locations. Furthermore, the database 207 may be implemented inside the drone 116 and the database 207 may be implemented as a single database 207.
[0055] In one embodiment, the drone 116 may include at least one processor 121, an input/output (I/O) interface 122, and a memory 117. The at least one processor 121 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 121 is configured to fetch and execute computer-readable instructions stored in the memory 117.
[0056] The I/O interface 122 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 122 may allow the drone 116 to interact with
the user directly or through the client devices 106. Further, the I/O interface
122 may enable the drone 116 to communicate with other computing
devices, such as web servers and external data servers (not shown). The I/O
interface 122 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 122 may include one or more ports for
connecting a number of devices to one another or to another server.
[0057] The memory 117 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 non- volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The memory 117 may include modules 124 and data 126.
[0058] The modules 124 include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. In one implementation, the modules 124 may include a generating module 128, a computing module 130, a navigating module 132 and other modules 134. The other modules 134 may include programs or coded instructions that supplement applications and functions of the drone 116. The modules 124 described herein may be implemented as software modules that may be executed in the cloud-based computing environment of the drone 116.
[0059] The data 126, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 124. The data 126 may also include a system data 136, and other data 138. The other data 138 may include data generated as a result of the

execution of one or more modules in the other modules 134. The detailed description of the modules 124 along with other components of the drone 116 is further explained by referring to figures 1.
[0060] In one implementation, at first, a user may use the user device 106 to access the drone 116 via the I/O interface 122. The user may register themselves using the I/O interface 122 in order to use the drone 116. In one aspect, the user may access the I/O interface 122 of the drone 116 for delivering products to the user, the drone 116 may employ the plurality of modules 124 i.e., generating module 128, a computing module 130, a navigating module 132 and other modules 134. The detailed working of the plurality of modules 124 is described below.
[0061] The drone 116 is also referred as UAV 116 in the present disclosure. The generating module 128, is coupled with the processor 121. The generating module 128 generates the information of one or more paths to be traversed by a drone or UAV 116 based on one or more parameters. The one or more parameters comprise maximum UAV 116 flight altitude allowed in an area and weather data of the area, other UAV 116 in the area, a start point, and an end point. One or more paths are in layers, UAV 116 associated with different payload capacity of UAV 116. The computing module 130 is coupled with the processor 121. The computing module 130 computes the time required to traverse for each of the one or more paths. The navigating module 132 is coupled with the processor 121. The navigating module 132 navigates the UAV 116 over a path selected from one or more paths based on comparison of the time require to traverse to deliver the product at user’s location. For navigating the UAV 116, first the product is loaded by the processor 121 on the UAV 116. The UAV 116 take off by the processor 121 and enroots to the user’s delivery point consisting of common building check points 28. The exact delivery location of the

product is identified by the processor 121 where the product needs to be drop off or delivered. The UAV 116 is travelled by the processor 121 horizontally to common building check points 28. The UAV 116 is travelled by the processor 121 vertically to common building check points 28 to deliver or drop off the product to be delivered.
[0062] Figure 2 illustrate an example block diagram of the system 901 for drone deliveries in high rise/ multi stories buildings, low rise buildings or any other building’s structure. The system 901 includes developer system 208 (map developer 207 and server 110), network 203, computer 106-3, drone 116 and mobile device 106-1. Developer system 208 includes server 110 and one or more map developers’ databases 207. The term database or maps database further refers to set of data or maps data stored in one or more storage mediums. The database of developer system may consist geographic data including two dimensional or three-dimensional maps data, building structures, textures, colours, geographic drone delivery path points data, pre-defined drone delivery paths/ lanes data, information of deliveries, etc.
[0063] Server 110 may handle all the deliveries information, defines coordinates for drone delivery paths/ lanes, identifies fastest route to delivery location, send navigation command(s) to drones to operate, keeps checking the entire process from user placing an order to order getting delivered at user’s delivery location safely and securely, notifies on computer display if any error comes up in the process of deliveries.
[0064] Network 203 may work as a medium where developer system 208, computer 106-3, drone 116 and mobile device 106-1 are coupled. The phrase “coupled” means one or more components of system 901 directly or indirectly connected, which may be through hardware or software. Software may coordinate various commands such as logistics, safety

aspects of the drones, for maintenance and to keep checking on operations of drone deliveries.
[0065] Computer 106-3 may be used as a medium for a connected network of the entire drone deliveries operations, which displays the entire process through a software on screen at monitoring facilities. Developer system is connected to network and network is connected to computer, which is further connected to drones and mobile devices. Server 110 handles and keep checking the entire process from user placing orders to orders getting delivered at users’ drop off location, which is also monitored by person at one or multiple process/ operations monitoring facilities through computers. If in case any error comes up, the server 110 notifies on computer(s) display at monitoring facilities, after which the drone delivery operation may be handled manually by a person through computer(s).
[0066] Drone 116, which is also referred in the invention as unmanned aerial vehicle (UAV) may have two or more propeller/ spinning blades used to lift from ground by forcing air downwards, back side or in any other directions. Drones 116 may be used for various purposes such as delivery of goods, search and rescue, agriculture surveying, firefighting, communication relay, surveillance and monitoring etc. Drones (UAV) 116 may get navigation commands and other delivery information from developer system 208 or server 110 through network for drones to operate and make deliveries to users’ locations.
[0067] Mobile device 106-1 may use for showing deliveries information to users through application(s) on display, such as to order goods, live tracking of drone deliveries, to make online payments, to know exact location of users, etc. Mobile device(s) are connected to network through which transfer of all the information get done.

[0068] All the components of system 901 may be further described or explained in written with drawings.
[0069] Figure 3 illustrate an example overall schematic view 109 of drone deliveries in high rise/ multi stories building 112, low rise building 114 or any other building structures in two dimensional and three-dimensional geographic maps. Three dimensional maps with building models and other objects (e.g., trees, towers, wires, vehicles, etc.) may be created from manual modelling, mesh data, photogrammetry, stereophotogrammetry etc. Textured and/ or colours may be applied on 3D building models. Building models, for example 112 and 114 may be used to identify and define delivery location on server 110 from map database. Geographic coordinates (e.g., latitude, longitude and altitude) are defined from the three-dimensional geometry of building model in map database which may be stored or registered in map data base while registering the user location for the first time. The building models dimensions may be measured with light detection and ranging (LIDAR) device. The figure 109 also includes trees 107, which counts as obstacles for drones, drones 116, delivery packages mounted on drones 715 which may carry goods (e.g., apparel, books, food, groceries, medicines, etc.) and drone delivery path/ lanes 712, pre-defined drone delivery paths are created from pickup locations to delivery locations for faster, safer possible deliveries and for avoiding any collision of drones making deliveries on server 110 with help of map developer’s data. Herein, “path/ layers” refers to imaginary network of paths created in two dimensional or three-dimensional maps, which may be elevated from ground for drones to travel from pick up point to users’ delivery locations. Drone paths/ layers may be defined on the bases of maximum drone flight altitude allowed in any particular area, usual weather data in area of pickup

location and drop off location of user, after avoiding trees, wires or any other objects etc.
[0070] Figure 4 illustrate an example perspective view of two-dimensional representation of three-dimensional maps 109, buildings model 112 and 114, trees 107, towers 118, and wires 120. Towers and wires are pre-defined and shown in 2D or 3D maps along with building models. Tower 118 and wires 120 are defined as obstacles on server 110, which helps while making pre-defined drone delivery paths/ lanes to avoid any collision, for making fast and safe drone deliveries.
[0071] Figure 5 illustrate an example top-down view 102 of buildings footprints 112 and 114 and objects/ trees 107 in two dimensional geographic maps.
[0072] Figure 6 illustrate an example perspective view of buildings model 112 and trees 107, tower 118 and wires 120 as objects in 702, with highlighting one building model 112 and its dimensions. For example, herein this invention description, dimensions for building model 112 are defined with length 705, width 703 and height 701. (e.g., Length 705 may be 102 ft., width 703 may be 65 ft., height 701 may be 203 ft.). The dimensions of the building model(s) 112 are defined for precision drone 116 deliveries or for drones 116 to travel accurately to users’ drone delivery locations. Herein, “building(s) model 112 dimensions” refers to dimensions for building model 112, which are defined with length 705, width 703 and height 701, distance between two floor lines or height of one floor 726. For example, length 705 may be 102 ft., width 703 may be 65 ft., height 701 may be 203 ft., distance between two floor lines or height of one floor may be 10 ft.)
[0073] Server 110 may define or calculate dimensions of building model(s) 112 with the help of map developer(s) 207 data or can be defined/ enter

manually of each building models 112 by a person on computer(s) 204 or can be combination of both, dimensions from map developer(s) data 207 and manually by person on computer(s) 204.
[0074] Figure 7 illustrate an example perspective view 702 of buildings model 112 and objects 107, with highlighting one building model 112, floor separating lines 704, its dimensions (length 705, width 703 and height 701, distance between two floor lines or height of one floor 726). For example, length 705 may be 102 ft., width 703 may be 65 ft., height 701 may be 203ft., distance between two floor lines or height of one floor may be 10 ft.) and drone delivery pads 708, herein, “drone delivery pads” 708 refers to delivery pads, which could be rectangle, square or in any shape and built out of any kind of materials, where drones 116 can land and delivery goods. Herein, “drone delivery pads” 708 can also be sticker or any kind of platform where drone(s) 116 can land and deliver goods. Drone delivery pads 708 may be stationary or automatic (connected to electricity) or both (stationary and connected to electricity).
[0075] The floor lines 704 are defined for the purpose of separating floors in building model(s) 112. The floor separating lines 704 are imaginary lines defined on server 110 in map developer(s) data 207. Server 110 may define or place floor separating lines 704 on building model(s) 112 based on the data of total floors in any building in real and dimensions of building(s) or can be defined/ enter manually of each building models 112 by a person on computer(s) 204 or can be combination of both, dimensions of the building and data of total floors in any building(s) from map developer(s) data 207 and manually by person on computer(s) 204.
[0076] Server 110 may pre-define spot for drone delivery pads 708 on floors on the bases of dimensions of building models 112 and floor separating lines 704 or can be defined/ enter manually of each building models 112 by a

person on computer(s) 204 or can be combination of both, dimensions of the building and data of total floors of any building(s) from map developer(s) data 207 and manually by person on computer(s) 204. Server 110 may pre-define/ show drone delivery pad 708 on all the floors/ flats on building model 112 so whenever new user register for drone delivery services, after fitting of drone delivery pad 708or giving it to any new users, the drone delivery pad 708 gets activated and accept/open for drone deliveries, or server 110 may just show drone delivery pads on floors/ flats of building model, where users are registered and when new user registers, the drone delivery pads 708shows up there on their floor/ flats in three dimensional maps.
[0077] Figure 8 illustrate an example perspective view 702 of buildings model 112 and object (tree) 107, with highlighting one building model 112 with floor separating lines 704, its dimensions and drone delivery pads 708, and one other building model 113 with its dimensions (length 719, width 720 and height 716. (e.g., Length 719 may be 102 ft., width 720 may be 65 ft., height 716 may be 203 ft.), without floor separating lines 704 on building model 113, and drone delivery pads 718. Floor separating lines 704 may be there or may not be in some cases (e.g., if not needed on some building models (e.g., 113) which does not require floor separating lines 704). Drone delivery pads 718 may be defined or shown on building model (e.g., 113) without floor separating lines (e.g., 704) on floors/ flats.
[0078] Figure 9(A) illustrate an example perspective view 707 of buildings model 112 and object (tree) 107, with highlighting one building model 112, floor separating lines 704, building dimensions, drone delivery pads 708, drone delivery path 712, drone 116 with delivery package 715. Server 110 may pre-define or create drone delivery paths/ lanes for drones 116 to travel from pick up points of good to user’s delivery locations (on drone

delivery pads 708) or to any common points or charging points elevated from ground for faster, safer possible deliveries and for avoiding any collision of drones 116 while making deliveries. Drone paths 712 may be automatically defined/ created on the bases of maximum drone 116 flight altitude allowed/ permitted in particular area, usual weather data in area of pickup location and drop off location of user, after avoiding trees 107, towers 118, wires 120 or any other objects etc. or drone delivery paths/ lates are made manually on server 110 by a person on computer.
[0079] Figure 9(B) illustrate an example side cross sectional view 706 including multi layers of paths 712 described in Figure 8(a), side cross section of building model 112 and dimensions (height 701 and width 703) of building model 112. Server 110 may define or create one or more than one paths 712 for drones 116 to travel, which may be used for different payload capacity of drones 116, to change lanes/ paths 712 in some instances such as other drone/s 116 travelling on same route, because of different weather conditions (e.g., wind speed or rain, etc.) or in any other cases where drones 116 have to change paths/ lanes. For example, top layer/ path 712 a may be assigned for drones 116 with payload capacity of 5 to 7 kgs, second path 712 b for payload capacity of 2 to 3 kgs, one alternate path 712 c above the top layer and another one alternate path/ layer 712 d below the second path for drones to switch lanes/ paths in case of multiple drones travelling on the same routes).
[0080] Figure 10 illustrate an example top-down cross section view 401 of a building 112 with building buffer zone lines (rectangle with lines) 29, drone delivery check points 22 and 28 around the building 112. Server 110 may define/ create buffer zone around building 112 which is at some distance from building 112. The building buffer zone may be in any shape (rectangle for rectangle buildings, square for square buildings, round for

round buildings, etc.) For example, from building 112, a parallel line 20 of rectangle buffer zone 29 to length 705 is defined 15 ft. away (21) from building length 705 on both the side of building 112 and the same way a parallel line 25 of rectangle buffer zone 29 to width 703 is defined 10 ft. away (26) from building width 703 on both the side of building 112. The rectangle buffer zone 29 created with length 122 ft., width 95 ft. as compared to building 112 dimensions (length 102 ft., width 65 ft.), where buffer zone (e.g., 29 and 23) dimensions may be larger in some areas or smaller in some areas. The buffer zone in shape of rectangles 29 are defined parallel on all the floors (in centre of all the floors/ between the centre of any or every two floor separating lines 704.
[0081] Server 110 may also define or create check points (22 and 28) on buffer zone rectangle 29 lines for drones to navigate/ travel. Once drone 116 reach or check one point it travels to other points for making drone deliveries of goods 715 precisely to user’s locations. Rectangle buffer zone 29 is common buffer zone rectangle, which is elevated at some distance from building height 701. Once drone 116 reaches to any point of common building buffer zone 29 (specific point on buffer zone rectangle is defined by server 110 and command is given to drone 116), drone travels in vertical or horizontal directions and reach to users’ floor points. Check point(s) 28 on common buffer zone rectangle 29 are common building 112 check points 28. Check points on buffer zone rectangles between two floor separation lines are floor check points 22. Herein, “common building 112 buffer zone rectangle 29” may referred as common building buffer zone rectangle/ line(s) 29, and buffer zone rectangles 23 between two floor separation lines 704” may referred as floor buffer zone rectangles/ line(s) 23. Herein, “check points 28 on common building 112 buffer zone rectangle 29” may referred as common check points or common building check points 28 and “check

points 22 on buffer zone rectangles 23 between two floor separation lines 704” may referred as floor check points 22.
[0082] Figure 11 illustrate an example front cross section view 401 of a building 112, including common building buffer zone rectangle 29-line, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23, floor check points 22, drone delivery pads 708, drone delivery pads check points 27, buffer zone rectangles/ line(s) dimension 20 and building 112 dimensions. Server 110 may define/ create common building buffer zone rectangles/ line(s) 29, which may be elevated or at distance 24 from building 112 height (e.g., 25 ft. and 228 ft. from ground 729 including building height 701, which is 203 ft.), common building check points (which are defined by server 110 or entered manually by a person on computer 106-3 on common building buffer zone rectangles/ line(s) 29. Drone delivery pads check points’ 27 location (latitude, longitude and altitude) may defined or stored on server 110 manually by a person from mobile device 106-1 at the time of new registration of users, may be defined by server 110 automatically or may be combination of both defined or stored by a person on computer 106-3 and/ or pre-defined and stored by server 110 automatically with the help of map developers’ data 207. Once drone 116 reaches to common building check point(s) 28, drone 116 may travel vertically downwards to floor check points 22. When drone 116 reaches to floor check point(s) 22, drone 116 may travel to drone pads check point(s) 27 for delivering goods 715 on drone delivery pads 708. After drone 116 may go back/ return to pick up point from the same route it came from or may be go to other location after returning to common building check points 28.
[0083] Figure 12 illustrate an example side cross section view 401 of a building 112, including common building buffer zone rectangle 29-line,

common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23, floor check points 22, drone delivery pads 708, delivery pads check points 27, buffer zone rectangles/ line(s) dimension 25 and building 112 dimensions.
[0084] Figure 13 illustrate an example perspective cross section view 401 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23, floor check points 22, drone delivery pads 708 (only on some floors where users registered), delivery pads check points 27, buffer zone rectangles/ line(s) dimension (20 and 25), floor separating rectangles/ lines 704 and building 112 dimensions.
[0085] Figure 14 illustrate an example perspective cross section view 401 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (pre-defined on all the floors), floor check points 22 (pre-defined on all the floors), drone delivery pads 708 (on register users’ floors/ flats), delivery pads check points 27, buffer zone rectangles/ line(s) dimensions (20 and 25), floor separating rectangles/ lines 704 and building 112 dimensions. Server 110 may pre-define/ show floor buffer zone rectangles/ lines 704 on all the floors/ flats on building model 112 for making the process of registering new users’ easier and faster. Server 110 may also pre-define/ show drone delivery pad 708 on all the floors/ flats on building model 112 so whenever new user register for drone delivery services, after fitting of drone delivery pad 708 or giving it to any new users, the drone delivery pad 708 gets activated and accept/open for drone deliveries, or server 110 may just show drone delivery pads on floors/ flats of building model 112, where users are

registered and when new user registers, the drone delivery pads 708 shows up there on their floor/ flats in three dimensional maps.
[0086] Figure 15 illustrate an example perspective cross section view 401 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (pre-defined on all the floors), floor check points 22 (only on some floors where users registered), drone delivery pads 708 (on register users’ floors/ flats), delivery pads check points 27, buffer zone rectangles/ line(s) dimensions (20 and 25), floor separating rectangles/ lines 704 and building 112 dimensions.
[0087] Server 110 may define/ store a unique identification number, geographic coordinates (e.g., latitude, longitude and altitude) and other data (e.g., customers’ drone delivery pad identification numbers, names, addresses, etc.) automatically with help of map developers data or/and defined/ stored manually by a person in computer 106-3 to each and all the check points (of 22, 27 and 28), through which the check points are identified while server 110 defines a route for drone deliveries to users’ locations. Common building check points 28 on common building buffer zone rectangle 29 may be identified by two sides (length 20 and width 25). On lines of length 20 of common building buffer zone rectangle 29, four common building check points 28 are defined (402a, 402b, 402c and 402d) for drones 116 to travel on front or/ and back sides of the building 112 and On lines of width 25 of common building buffer zone rectangle 29, four common building check points 28 are defined (405a, 405b, 405c and 405d) for drones 116 to travel on left or/ and right sides of the building 112. Floor check points 22 on floor buffer zone rectangles/ line(s) 23 may be identified by two sides (length 20 and width 25). On lines of length 20 of floor buffer

zone rectangle 29, four floor check points 22 are defined. Herein the figure 15, taking example of front side so three floor check points are defined on 23 of different floors (407a, 407b and 407c) for drones 116 to travel on front side (drone 116 may also travel on back side when the floor check points 22 ore defined on floor buffer zone rectangles/ lines 23) of the building 112. On lines of width 25 of floor buffer zone rectangle 29, four floor check points 22 may also be defined if needed on the building 112. Drone delivery pads check points 27 on floor buffer zone rectangles/ line(s) 23 may be identified on all the delivery pads 708 fitted or given to users’ drone delivery location 409a, 409b, 409c. Drone delivery pads check points 27 location may be entered/ stored manually by a person to computer 106-3 or mobile device 106-1 on server 110 with using with light detection and ranging (LIDAR) device, global positioning system (GPS) or any other device to measure accurate geographic coordinates (e.g., latitude, longitude and altitude). Drone delivery pads may be fitted on users drone delivery location (in users’ balcony, which maybe fitted on wall or on the floor) 27 after checking all the clearance for drone 116 to travel safely without any obstacles coming in way.
[0088] Figure 16 illustrate an example perspective view 714 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (pre-defined on all the floors), floor check points 22 (pre-defined on all the floors), drone delivery pads 708 (on register users’ floors/ flats), delivery pads check points 27, buffer zone rectangles/ line(s) dimensions (length 20 and width 25), floor separating rectangles/ lines 704, drone delivery paths/ lanes 712, drone 116, drone delivery package 715 and building 112 dimensions.

[0089] Figure 17 illustrate an example perspective view 714 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats where users registered), floor check points 22 (only on some floors/ flats where users registered), drone delivery pads 708 (on register users’ floors/ flats), delivery pads check points 27, buffer zone rectangles/ line(s) dimensions (length 20 and width 25), floor separating rectangles/ lines 704 with drone 116 carrying drone delivery package 715 on drone delivery paths/ lanes 712 and building 112 dimensions. Server 110 may send navigation command to drone 116 after getting order request for drone delivery. Server 110 may navigate drone to first travel to pick up point, where drone pick up delivery package(s) 715 (e.g., apparel, books, food, groceries, medicines, etc.), after picking up delivery package 715, drone may travel on pre-defined paths/ lanes 712 to common building check points 28 of common building buffer zone rectangle/ lines 29, after reaching to common building check point 28, drone may travel vertically downwards or may travel horizontally first to other common building check point 28 of common building buffer zone rectangle/ lines 29 and then drone may travel vertically downwards to floor check points 22 on floor buffer zone rectangles/ line(s) 23, after drone 116 reaches to floor check points, drone 116 may travel to drone delivery check points 27 on drone delivery pads 708 for making drone deliveries and leaving delivery good(s) 715 on drone delivery pads 708.
[0090] Figure 18 illustrate an example perspective view 714 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats

where users registered), floor check points 22 (only on some floors/ flats where users registered), drone delivery pads 708 (on register users’ floors/ flats), delivery pads check points 27, buffer zone rectangles/ line(s) dimensions (length 20 and width 25), floor separating rectangles/ lines 704 with drone 116 carrying drone delivery package 715 on common building check point 28 (402a) of common building buffer zone rectangle/ line(s) 29 and building 112 dimensions.
[0091] Figure 19 illustrate an example perspective view 714 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats where users registered), floor check points 22 (only on some floors/ flats where users registered), drone delivery pads 708 (on register users’ floors/ flats), delivery pads check points 27, buffer zone rectangles/ line(s) dimensions (length 20 and width 25), floor separating rectangles/ lines 704 with drone 116 carrying drone delivery package 715 on floor buffer zone check point 22 (407a) of floor buffer zone rectangle/ line(s) 23 and building 112 dimensions.
[0092] Figure 20 illustrate an example perspective enlarged view 710 of figure 18, including building 112, floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats where users registered), floor check point 22 (only on some floors/ flats where users registered), drone delivery pad 708 (on register users’ floors/ flats), delivery pads check point 27 (Herein, for detailed example one drone delivery pad 708 with one delivery check point 27 is shown 409a),floor separating rectangles/ lines 704 with drone 116 carrying delivery package 715 on floor buffer zone check point 22 (407a) of floor buffer zone rectangle/ line(s) 23, building 112 dimensions, one or more delivery pad barcodes 711 on drone delivery pad 708 (for example,

four barcodes), where number of barcodes depend on requirement of drone 116 to land, barcodes are used navigate drone to land drone 116 precisely in process of drone 116 to land in centre of drone delivery pad 708, one or more wall barcode(s) 721 may be sticked or kept on building 112 for drones to identify exact location of drone delivery pad 708 on building 112 and to prevent unauthorised deliveries. In one embodiment, ArUco markers are used on drone delivery pad 708 for guiding the drones for precision landing. In another embodiment, Infrared (IR) beacons are used on drone delivery pad 708 to navigate the drones for precision landing.
[0093] Figure 21 illustrate an example perspective enlarged view 710 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats where users registered), floor check points 22 (only on some floors/ flats where users registered), drone delivery pad 708 (on register users’ floors/ flats), delivery pads check point 27 (Herein, for detailed example one drone delivery pad 708 with one delivery check point 27 is shown 409a), buffer zone rectangles/ line(s) dimensions (length 20 and width 25), building 112 dimensions, floor separating rectangles/ lines 704 with drone 116 carrying drone delivery package 715 on floor buffer zone check point 22 (407a) of floor buffer zone rectangle/ line(s) 23, one or more delivery pad barcodes 711 on drone delivery pad 708 (for example, four barcodes), where number of barcodes depend on requirement of drone 116 to land, barcodes are used navigate drone to land drone 116 precisely in process of drone 116 to land in centre of drone delivery pad 708, one or more wall barcode(s) 721 may be sticked or kept on building 112 for drones to identify exact location of drone delivery pad 708 on building 112.

[0094] Figure 22 illustrate an example perspective enlarged view 710 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats where users registered), floor check points 22 (only on some floors/ flats where users registered), drone delivery pad 708 (on register users’ floors/ flats), delivery pads check point 27 (Herein, for detailed example one drone delivery pad 708 with one delivery check point 27 is shown 409a), buffer zone rectangles/ line(s) dimensions (length 20 and width 25), building 112 dimensions, floor separating rectangles/ lines 704 with drone 116 carrying drone delivery package 715 travel horizontally near/ in front of drone delivery pad check point 27 (409a) from floor buffer zone check point 22 (407a) of floor buffer zone rectangle/ line(s) 23, one or more delivery pad barcodes 711 on drone delivery pad 708 (for example, four barcodes), where number of barcodes depend on requirement of drone 116 to land, barcodes are used navigate drone to land drone 116 precisely in process of drone 116 to land in centre of drone delivery pad 708, one or more wall barcode(s) 721 may be sticked or kept on building 112 for drones to identify exact location of drone delivery pad 708 on building 112.
[0095] Figure 23 illustrate an example perspective enlarged view 710 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats where users registered), floor check points 22 (only on some floors/ flats where users registered), drone delivery pad 708 (on register users’ floors/ flats), delivery pads check point 27 (Herein, for detailed example one drone delivery pad 708 with one delivery check point 27 is shown 409a), buffer zone rectangles/ line(s) dimensions (length 20 and

width 25), building 112 dimensions, floor separating rectangles/ lines 704 with drone 116 carrying drone delivery package 715, one or more delivery pad barcodes 711 on drone delivery pad 708 (for example, four barcodes), where number of barcodes depend on requirement of drone 116 to land, barcodes are used navigate drone to land drone 116 precisely in process of drone 116 to land in centre of drone delivery pad 708, one or more wall barcode(s) 721 may be sticked or kept on building 112 for drones to identify exact location of drone delivery pad 708 on building 112.
[0096] One check point may be defined just in front of drone delivery pad 708/ pad check point 409a on floor buffer zone rectangles/ line(s) 23 by server 110 or may be defined/ entered manually by a person on mobile device 106-1 and/or computer 106-3 when any new user gets registered and drone pads get installed or floor check points may be defined/ relocated in front of drone delivery pad 708 while registering new users. Drone 116 may begin to travel horizontally near/ in front of drone delivery pad check point 27 (409a) from floor buffer zone check point 22 (407a) of floor buffer zone rectangle/ line(s) 23 and may verify the user with wall barcode 721, after which drone 116 may look for drone delivery pad 708 with help of pad barcodes 711, sensors and/ or camera(s) and deliver goods as in delivery package 715 on drone delivery pad 708.
[0097] Figure 24 illustrate an example perspective enlarged view 710 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats where users registered), floor check points 22 (only on some floors/ flats where users registered), drone delivery pad 708 (on register users’ floors/ flats), delivery pads check point 27 (Herein, for detailed example one drone delivery pad 708 with one delivery check point 27 is

shown 409a), buffer zone rectangles/ line(s) dimensions (length 20 and width 25), building 112 dimensions, floor separating rectangles/ lines 704 with drone 116 carrying drone delivery package 715, one or more delivery pad barcodes 711 on drone delivery pad 708 (for example, four barcodes), where number of barcodes depend on requirement of drone 116 to land, barcodes are used navigate drone to land drone 116 precisely in process of drone 116 to land in centre of drone delivery pad 708, one or more wall barcode(s) 721 may be sticked or kept on building 112 for drones to identify exact location of drone delivery pad 708 on building 112. After making delivery or leaving delivery goods 715 on drone delivery pad 708, drone 116 may go back/ return from delivery pad check point 27 (409a) to floor check points 22 (407a) on floor buffer zone rectangles/ line(s) 23 to common building check points 28 (402a) on common building buffer zone rectangle/ lines 29.
[0098] Figure 25 illustrate an example perspective enlarged view 710 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats where users registered), floor check points 22 (only on some floors/ flats where users registered), drone delivery pad 708 (on register users’ floors/ flats), delivery pads check point 27 (Herein, for detailed example one drone delivery pad 708 with one delivery check point 27 is shown 409a), buffer zone rectangles/ line(s) dimensions (length 20 and width 25), building 112 dimensions, floor separating rectangles/ lines 704 with drone 116 carrying drone delivery package 715, one or more delivery pad barcodes 711 on drone delivery pad 708 (for example, four barcodes), where number of barcodes depend on requirement of drone 116 to land, barcodes are used navigate drone to land drone 116 precisely in process of

drone 116 to land in centre of drone delivery pad 708, one or more wall barcode(s) 721 may be sticked or kept on building 112 for drones to identify exact location of drone delivery pad 708 on building 112. After making delivery or leaving delivery goods 715 on drone delivery pad 708, drone 116 may go back/ return from to floor check points 22 (407a) on floor buffer zone rectangles/ line(s) 23 to common building check point 28 (402a) on common building buffer zone rectangle/ lines 29.
[0099] Figure 26 illustrate an example perspective enlarged view 710 of a building 112, including common building buffer zone rectangle 29, common building check points 28 elevated or at a distance 24 from building 112 (e.g., 25 ft.), floor buffer zone rectangles/ line(s) 23 (only on some floors/ flats where users registered), floor check points 22 (only on some floors/ flats where users registered), drone delivery pad 708 (on register users’ floors/ flats), delivery pads check point 27 (Herein, for detailed example one drone delivery pad 708 with one delivery check point 27 is shown 409a), buffer zone rectangles/ line(s) dimensions (length 20 and width 25), building 112 dimensions, floor separating rectangles/ lines 704 with drone 116 carrying drone delivery package 715, one or more delivery pad barcodes 711 on drone delivery pad 708 (for example, four barcodes), where number of barcodes depend on requirement of drone 116 to land, barcodes are used navigate drone to land drone 116 precisely in process of drone 116 to land in centre of drone delivery pad 708, one or more wall barcode(s) 721 may be sticked or kept on building 112 for drones to identify exact location of drone delivery pad 708 on building 112. After making delivery or leaving delivery goods 715 on drone delivery pad 708, drone 116 may go back/ return from common building check point 28 (402a) on common building buffer zone rectangle/ lines 29 to pre-defined drone delivery path / lanes 712. After making delivery or leaving delivery goods

on drone delivery pad 708, drone 116 may go back/ return to pick up point from the same route it came from or may be go to other location or to any location navigated/ defined by server 110 after returning to common building check points 28.
[00100] Figure 27 illustrate an example block diagram of system for drone 116 of the system of Figure 1. The drone 116 includes sensors 504, cameras 501, GPS 502, IMU 505, image processing module 507, memory 117, communication system 506, navigation system 501, microphone 516, display 503, motors 521, EPS 519, power supply 509, processor 121 and flight controller 514. Additional, fewer or different components may be possible for drone (UAV) 116.
[00101] The sensors 504 may include, vision sensors, ultrasonic sensors, infrared sensors, gyroscope sensor, accelerometer, barometric sensors, inertia measurement sensor, tilt sensors, magnetic sensors or magnetometer, sensor for gimble image stabilization. Additionally, few or different sensors may be used in drone 116.
[00102] Cameras 501 may be used to identify exact delivery location of the package where it needs to be drop off or delivered, which may be drone delivery pad, sticker, any kind of a platform. While drone makes deliveries and when drone 116 is on its route to make drone deliveries, cameras may check for any person or unexpected object in building’s 112 balcony or in specific radius near drone delivery pad 708 (e.g., 6 feet, 20 feet, etc.). Camera feed or live camera feed data may be sent to server 110 for purpose such as security, safety, etc.
[00103] Global positioning system (GPS) 502 may be used and integrated to other components on drone 116 to perform operations such as to provide navigations, autonomous flight, to hold position of drone 116. GPS 502 may be used to navigate autonomously or manually to different geographic

coordinates, which may be pre-defined in maps developers’ data (for example, to pick up point(s), to travel on drone delivery paths/ lanes 712, building buffer zone rectangles/ lines 29 or/and 23, check points 28, 22, 27 and to other points which may be predefined by or on server 110) for drone(s) to travel and make drone deliveries.
[00104] IMUs 505 may work as essential components in operation of unmanned aerial system (UAV) or drone 116 system. IMUs 505 may be used for attitude and heading reference system (AHRS) for measurement of roll, pitch and yaw, control stabilisation, correction, guidance, measurement, testing and mobile mapping. Silicon MEMS (micro-electro-mechanical system), fiber optic gyro (FOG), ring laser gyro (RLG), quartz MEMS or any other type of IMUs may be used in drones116.
[00105] Image processing module 507 may be used for various operations such as, to identify or detect any objects coming in way or in specific radius of drone 116, to photogrammetry on aerial imaginary, to distinguish different objects, surveillance, to improve quality of captured camera feed data, image analysis, etc.
[00106] Memory 117 may include one or more than one of random-access memory (RAM), read only memory (ROM), a flash memory, electronic erasable program read only memory or any other type of memory. Memory 511 may be a volatile memory or non-volatile memory. Memory 117 may be fixed or removable, for example secured digital (SD) memory card from drone 116.
[00107] Communication system 506 may include any usable connection. Usable connection may be one in which physical and/or logical communications, signals sent and/ or received. Usable connection may include a physical interface, data interface and/ or electric interface.

Communication interface may be used as in any wired or wireless connections.
[00108] Navigation system 501 may be used for locating or detecting location of drones, to send navigation command to drones from pick up location to users’ drone delivery locations to returning routes based on orders and routing requests. Navigation system may decode and follow routes as in pre-defined paths/ lanes sent by server 110 on the bases of maximum drone flight altitude allowed in any particular area, usual weather data in area of pickup location and drop off location of user, after avoiding trees 107, towers 118, wires 120 or any other objects etc.
[00109] Speaker 516 may use for sound reproduction. Speaker may be used for converting electrical energy to acoustical energy to generate sound which is radiated in air. Speake may be used by server 110, person from monitoring facilities to communicate a message. When drone 116 is on a route to deliver delivery package to user’s delivery location, drone 116 may check for any person or unexpected object in building’s 112 balcony or in specific radius near drone delivery pad 708 (e.g., 6 feet, 20 feet, etc.) for users’ safety and drone security. If any person or user identified in specific radius then the drone 116 may ask the person to clear specific radius mentioned above, or if any unexpected object is identified which is in path to drop off or deliver the package 715 then drone 116 may ask to clear the path by moving the object or by clearing the specific area with using speaker mounted on the drone while the drone is at distance from the user delivery pad 708 location or in front of drone delivery pad 708.
[00110] Display 503 may be light emitting diode (LED), liquid crystal display (LCD), thin film transistor (TFT), organic light emitting diode (OLED), active-matrix organic light emitting diode (AMOLED) or any other known or later developed display. Display 503 may be used for showing

battery percentage, animation, to show a message or for any other requirement.
[00111] Motors 521 may be direct current (DC) brushless motors (BLDC), alternating current (AC) brushless motors (BLAC)/ permanent magnet synchronous motors (PMSM), servo motors or any other kind of electric motors, which may convert electrical energy to mechanical energy. Motors may be used on drone to which propellers/ spinning blades gets fitted because of which drone 116 lifts from ground by forcing air downwards, back side or in any other directions.
[00112] Electronic speed controller (ESC) 519 may be used for controlling speed of motors 521 and propellers, which controls speed of drone. ESC 519 may allow flight controller 517 to control and adjust speed of electric motors 521 mounted on drones 116. Flight controller 517 may send signals to ESC 519 to raise or lower voltage to motors 521 as required by flight controller 517. Signals from flight controller to ESC 519 may be same for all motors on drone 116 or separate ESCs 519 may be mounted for separate signals for separate motors 521 as required.
[00113] Power supply 509 or energy source of drone 116 may be used to provide power to all relevant system in drone 116. Lithium polymer (Li-Po), lithium ion (Li-ion), lithium air (Li-air), lithium sulphur (Li-S), solar cells and/ or any other type of battery may be used for power supply to drone 116.
[00114] Processor 121 may be used for achieving good stability and performance, drone 116 system need to be able to read data from sensors 504, analyse, process the data, control speed of motors 521 and other drone 116 functions to manage in real time such as on board processing of camera feed images/ videos, GPS 502 navigation, wirelessly transfer of data on server 110 to monitoring facilities, continuously or periodically

communication with server 110 to coordinate drone flight, power optimization of running energy efficient and if needed camera gimble.
[00115] Flight controller 514 may be used to control and operate drone. Drone 116 travels by accelerating, deaccelerating and rotating by creating speed differences between each of the drone’s motors 521. Calculating movements of drone 116 analysing and filtering data from sensors 504 and estimate safety, durability of a drone flight may all done by algorithm of flight controller -. Flight controller – may use data gathered from all the sensors 504, cameras 501, IMUs 505, image processing module 507 and other drone 116 components from which speed and position of drone 116 may have to change for calculating desire speed for drone’s 116 motors 521, after which flight controller sends desired speed data to ESC(s) 519
[00116] Figure 28 illustrate an example flow chart for operation of the drone system 116 in Figure 27. Additional, fewer or different acts may be used.
[00117] Drone or unmanned aerial vehicle (116) is configured to deliver goods (e.g., apparel, books, food, groceries, medicines, etc.) from pick up locations to users’ locations fast and safely through pre-defined drone delivery paths/ lanes 712. Drone delivery paths may be imaginary network of paths created in two dimensional or three-dimensional maps, which may be elevated from ground for drones to travel from pick up point to users’ delivery locations. Drone 116 may communicate to server 110 for getting navigation command(s) as in routes for drone delivery from pick up location(s) to users’ drone delivery location(s), delivery information, users’ information. Drone(s) 116 may also send live location data and live camera feed data to server 110 for purpose such as security, safety, etc.
[00118] At act S601, after server 110 receive order(s) requests for drone deliveries, server 110 may check for availability of drones 116 to make drone deliveries in particular area from which drone delivery orders requested,

after which server 110 may calculate distance from drones 116 location to users’ location(s) and select fastest route(s) from pre-defined drone delivery routes/ paths 712 (including lanes) for the drone delivery based on the position of drone 116, availability of the drone 116, weather in area of pickup location and drop off location of user data etc. and routing request as a route from pick up location to user’s delivery location as navigation command with location geographic coordinates/ pre-defined points in 2D or 3D maps sent to the drone’s processor/ flight controller.
[00119] At act S603, After the drone gets geographic coordinates as in navigation command, drone 205 confirm location to pick up point for pick¬up of delivery package 715, and if drone 205 is at some other location of particular area (e.g., at some charging point, on the way to return after making any delivery, etc.) then drone 116 may go to pick up location of delivery package 708. After which, the package(s) 715 gets loaded on drone 116, which may be done manually by a person or automatically with autonomous package loading facility at the pickup location. After delivery package 715 gets loaded on drone 116, drone 116 takes off and enroute to the user’s location(s) for delivery on the route/ navigation command sent through server 110 to drone processor/ flight controller.
[00120] At act S605, drone 116 may travel to exact location to user’s delivery location/ building with help of commands from server 110, sensors 504, GPS 502, IMU 505, image processing unit 507, navigation system 501 processor/ flight controller 517 with hardware of drone 116 (e.g., drone hardware, chassis, motors 521, electronic speed controller (ESC) 519 etc.). When drone reaches to floor check point 22 on floor buffer zone rectangle/ lines 23 or in front of drone delivery pad 708, after clearing common building check point 28 on common building buffer zone 29.

[00121] At act S607, drone 116 may check for any person or unexpected object in building’s 112 balcony or in specific radius near drone delivery pad 708 (e.g., 6 feet, 20 feet, etc.) for users’ safety and drone security. If any person or user identified in specific radius then the drone 116 may ask the person to clear specific radius mentioned above, or if any unexpected object is identified which is in path to drop off or deliver the package 715 then drone 116 may ask to clear the path by moving the object or by clearing the specific area with using speaker mounted on the drone while the drone is at distance from the user delivery pad 708 location or in front of drone delivery pad 708.
[00122] At act S609, if the delivery path is not clear for certain time after asking to clear the path for certain number of times (e.g., one, two, three, etc.) the drone communicates with server 110 and may cancel or postpone the drone delivery for particular order and may return to pick up point or any other location (e.g., common delivery point in particular area) as server 110 gives command.
[00123] At S611, drone 116 may look for drone delivery pad, sticker or any kind of a platform 708 for making delivery/ leaving delivery package 715 on drone delivery pad 708 with help of sensors 504, cameras 501, GPS 502, IMU 505, image processing module 507 mounted on drone 116. Drone 116 may scan building barcode 721 for verifying user’s location such as flat address, floor and building 112 number stored in building barcode and then drone 116 may process ahead for making drone delivery on drone delivery pad 708. After reaching on top of drone delivery pad 708, drone 116 may use cameras 501, GPS 502, sensors 504, IMU 505 and image processing module 507 for scanning barcode(s) in process of landing in centre of drone delivery pad 708, after which drone 116 deliver delivery package 715 on drone delivery pad 708.

[00124] At S613, after drone 116 delivers delivery package(s) 715 on drone delivery pad 708, drone 116 may communicates with server 110, after which drone 116 may return to pick up point or any other location as server 110 gives command.
[00125] Figure 29 illustrate an example block diagram of system for server 110 of the system of Figure 1. Server 110 includes network communication 809, Memory 117, processor 121 and power supply 805, which gets data to process from map developers 207 with help of computer 106-3. Additional, fewer or different components may be possible for server 110.
[00126] Memory 117 may include one or more than one of random-access memory (RAM), read only memory (ROM), a flash memory, electronic erasable program read only memory or any other type of memory. Memory 511 may be a volatile memory or non-volatile memory. Memory 511 may be fixed or removable, for example secured digital (SD) memory card from drone 116.
[00127] Server operating system (OS) 803 may be used to provide drone delivery services to large number of clients simultaneously through computer 106-3 or network of computers 204. Server operating system 803 enables and support server tasks such as database servers, mail server, application server, web server etc. One or multiple servers (e.g., traditional servers, rack mounted servers or blade servers) may be used as server operating system 803 (e.g., Microsoft Windows Server 2019, Red Hat Enterprise Linux (RHEL) server, Mac OS X Server) in server system 110.
[00128] Network communication 809 may include any usable connection. Usable connection may be one in which physical and/or logical communications, signals sent and/ or received. Usable connection may include a physical interface, data interface and/ or electric interface.

Communication interface may be used as in any wired or wireless connections.
[00129] Power supply 805 or energy source of server 110 may be used to provide power to all relevant system in server 110. Lead acid, nickel-cadmium (Ni-Cd), Lithium polymer (Li-Po), lithium ion (Li-ion), lithium air (Li-air), lithium sulphur (Li-S), solar cells and/ or any other type of battery may be used for power supply to drone 116. One or multiple batteries (which may be same or different kinds of battery chemistry) may be used in series and/ or parallel for power supply 805 to server system 110.
[00130] Processor 121 may be used for achieving efficiency, performance and managing operations of drone deliveries. Processor 121 may provide instructions and processing power to computer 106-3. Drone management system software on computer 106-3 may need to be able to read data, analyse, process the data and other drone management system software or fleet management system functions to manage drones 116 in real time such as on board processing of camera feed images/ videos, finding fastest routes for drone deliveries from pre-defined paths/ lanes while considering position of drone 116, availability of the drone 116, weather in area of pickup location and drop off location of user, etc. Processor 121 may continuously or periodically communication with server 110 to coordinate drone flights for drone deliveries. Processor 121, memory 117 and network communication further may be connected to computers 204 at monitoring facilities.
[00131] Drone delivery software may be created or developed with lines of code, set of programs, procedure and routine for performing specific tasks (e.g., to manage entire operation of drone deliveries in real time), which is developed to run on computers’ 204 hardware and application programs. Network 203 may work as a medium where developer system 208

(including server 110 and map developers 207), computer 106-3, drone 116 and mobile device 106-1 are coupled. Software may coordinate various commands such as logistics, safety aspects of the drones, for maintenance and to keep checking on operations of drone deliveries. Computer 106-3 may be used as a medium for a connected network of the entire drone deliveries operations, which displays the entire process through a software on screen at monitoring facilities. Drone delivery software 802 may be used to manage entire operations of drone deliveries from users’ placing an order to drone deliveries getting successfully made to users’ locations safely and securely.
[00132] Figure 30 illustrate an example flow chart for operation of the server system 110 in Figure 29. Additional, fewer or different acts may be used. Additional, fewer or different acts may be used.
[00133] Server 110 may be configured to process data (e.g., map developer’s data 207, users’ data, etc.), handle all the deliveries information, defines coordinates for drone delivery paths/ lanes, identifies fastest route to delivery location, send navigation and other command(s) to drones to operate for making drone deliveries fast, safely and securely. Server 110 may keep checking the entire process from users’ placing orders to orders getting delivered at users’ delivery locations safely and securely, notifies on computer display if any error comes up in the process of drone deliveries.
[00134] At act S301, server 110 may identify or create building models 112
in three dimensional maps and other objects (e.g., trees 107, towers 118,
wires 120, vehicles, etc.), which server 110 may create from manual
modelling of buildings, mesh data, photogrammetry,
stereophotogrammetry etc. Textured and/ or colours may be applied on 3D building models 112. Building models, for example 112 and 114 may be used to identify and define delivery location on server 110 from map

database 207. Server 110 may define or calculate dimensions of building model(s) 112 with the help of map developer(s) 207 data or/and can be defined/ enter manually of each building models 112 by a person on computer(s) 204. Geographic coordinates (e.g., latitude, longitude and altitude) are defined from the three-dimensional geometry of building model in map database which may be stored or registered in map data base while registering the user location for the first time. The building models 112 dimensions may be measured with light detection and ranging (LIDAR) device.
[00135] At act S303, geographic coordinates (e.g., latitude, longitude and altitude) of all building models (e.g., 112 and 113), buffer zone rectangles (e.g., 29 and 23), check points (e.g., 28, 27 and 22) and drone delivery paths/ lanes (e.g., 712) are defined from the three-dimensional geometry of building model in map database which may be stored or registered in map data base while registering the user location for the first time.
[00136] Server 110 may define or place floor separating lines 704 on building model(s) 112 based on the data of total floors in any building in real and dimensions of building(s) or/and can be defined/ enter manually of each building models 112 by a person on computer(s) 204.
[00137] Server 110 may pre-define spot for drone delivery pads 708 on floors on the bases of dimensions of building models 112 and floor separating lines 704 or/ and can be defined/ enter manually of each building models 112 by a person on computer(s) 204. Server 110 may pre-define/ show drone delivery pad 708 on all the floors/ flats on building model 112 so whenever new user register for drone delivery services, after fitting of drone delivery pad 708 or giving it to any new users, the drone delivery pad 708 gets activated and accept/open for drone deliveries, or server 110 may just show drone delivery pads on floors/ flats of building

model, where users are registered and when new user registers, the drone delivery pads 708 shows up there on their floor/ flats in three dimensional maps.
[00138] Server 110 may define/ create buffer zone around building 112 which is at some distance from building 112. The building buffer zone may be in any shape (rectangle for rectangle buildings, square for square buildings, round for round buildings, etc.) For example, from building 112, a parallel line 20 of rectangle buffer zone 29 to length 705 is defined 15 ft. away (21) from building length 705 on both the side of building 112 and the same way a parallel line 25 of rectangle buffer zone 29 to width 703 is defined 10 ft. away (26) from building width 703 on both the side of building 112. The rectangle buffer zone 29 created with length 122 ft., width 95 ft. as compared to building 112 dimensions (length 102 ft., width 65 ft.). The buffer zone in shape of rectangles 29 are defined parallel on all the floors (in centre of all the floors/ between the centre of any or every two floor separating lines 704.
[00139] Server 110 may also define or create check points (22 and 28) on buffer zone rectangle 29 lines for drones to navigate/ travel. Once drone 116 reach or check one point it travels to other points for making drone deliveries of goods 715 precisely to users’ locations. Rectangle buffer zone 29 is common buffer zone rectangle, which is elevated at some distance from building height 701. Once drone(s) 116 reaches to any point of common building buffer zone 29 (specific point on buffer zone rectangle is defined by server 110 and command is given to drone 116), drone travels in vertical or horizontal directions and reach to user’s floor points. Check point(s) 28 on common buffer zone rectangle 29 are common building 112 check points 28. Check points on buffer zone rectangles between two floor separation lines are floor check points 22. Herein, “common building 112

buffer zone rectangle 29” may referred as common building buffer zone rectangle/ line(s) 29, and buffer zone rectangles 23 between two floor separation lines 704” may referred as floor buffer zone rectangles/ line(s) 23. Herein, “check points 28 on common building 112 buffer zone rectangle 29” may referred as common check points or common building check points 28 and “check points 22 on buffer zone rectangles 23 between two floor separation lines 704” may referred as floor check points 22. Drone delivery pads check points’ 27 locations (latitude, longitude and altitude) may defined or stored on server 110 manually by a person from mobile device 106-1 at the time of new registration of users, may be defined by server 110 automatically.
[00140] At S305 act, server 110 may define drone delivery paths/ layers 712 (for drones 116 to travel and deliver packages 715 to users’ locations fast, safely and securely) on bases of maximum drone flight altitude allowed in any particular area, usual weather data in area of pickup location and drop off location of user, after avoiding trees 107, towers 118, wires 120 or any other objects etc. Server 110 may define or create one or more than one paths 712 for drones 116 to travel, which may be used for different payload capacity of drones 116, to change lanes/ paths 712 in some instances such as other drone/s 116 travelling on same route, because of different weather conditions (e.g., wind speed or rain, etc.) or in any other cases where drones 116 have to change paths/ lanes. For example, top layer/ path 712 a may be assigned for drones 116 with payload capacity of 5 to 7 kgs, second path 712 b for payload capacity of 2 to 3 kgs, one alternate path 712 c above the top layer and another one alternate path/ layer 712 d below the second path for drones to switch lanes/ paths in case of multiple drones travelling on the same routes).

[00141] At act S307, when server 110 receive order(s) requests for drone deliveries, server 110 may check for availability of drones 116 to make drone deliveries in particular area from which drone delivery orders requested, after which server 110 may calculate distance from drones location to users’ location(s) and select fastest route(s) 712 from pre-defined drone delivery routes/ paths (including lanes) for the drone delivery based on the position of drone, availability of the drone, weather in area of pickup location and drop off location of user data etc. and routing request as a route from pick up location to user’s delivery location as navigation command with location geographic coordinates/ pre-defined check points in 2D or 3D maps sent to the drone’s processor/ flight controller.
[00142] At act S308, server 110 may collect and store data from drones 116 (for example, flight details of route, technical data, camera live feed, delivery package details, users’ details and fleet details, etc.).
[00143] At act S310, after drone 116 make delivery or leave delivery goods successfully on drone delivery pad 708, server 110 may give command(s) to drone 116 to go back/ return to pick up point from the same route it came from or may give command(s) to other location or to any location after returning to common building check points 28 on common building buffer zone rectangle/ lines 29.
[00144] Figure 31 illustrate an example graphical user interface representation of mobile device 106-1 and its display 902 including, building model 112 integrated with mobile application user interface, delivery information 905 (e.g., drone delivery status, estimated delivery time, etc.), more delivery or other information 908 (e.g., payment details, fleet details, etc.), delivery location tag 907 (for showing delivery location to users) and a drone 116 on its way to deliver a delivery package 715. Additional, fewer or different components and details may be possible for

mobile device 106-1. Format of graphical user interface on mobile device 106-1 mobile application displayed on display 902 of mobile device 106-1 may be different or may have more components or details.
[00145] Mobile device 106-1 may be used by users for using mobile application(s) for getting/ checking delivery information, to place orders, make payment, check drone delivery status, etc. Display 902 of mobile device 106-1 may show animation of drone making delivery of users’ particular order.
[00146] Exemplary embodiments discussed above may provide certain advantages. Though not required to practice aspects of the disclosure, these advantages may include those provided by the following features. [00147] Some embodiments enable a system and a method to provide an intelligent way for delivering packages to customer’s location.
[00148] Although implementations for methods and systems for delivering products using an Unmanned Aerial Vehicle (UAV) 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 of delivering products using an Unmanned Aerial Vehicle (UAV).

We claim:
1. A method for delivering products using an Unmanned Aerial
Vehicle (UAV) (116), wherein the method comprises:
generating, by the processor (121), one or more paths to be traversed by a UAV (116) based on one or more parameters, wherein the one or more parameters comprises maximum UAV (116) flight altitude allowed in an area and weather data of the area, other UAV (116) in the area, a start point, and an end point, wherein one or more paths are in layers, UAV (116) associated with different payload capacity of UAV (116);
computing, by the processor (121), a time require to traverse for each of the one or more paths; and
navigating, by the processor (121), the UAV (116) over a path selected from the one or more paths based on comparison of the time require to traverse to deliver the product at user’s location.
2. The method as claimed in claim 1, wherein the method comprises:
defining, by the processor (121), at least a check point in each of the one or more paths wherein the check points comprises common building check points (28), floor check points (22) and drone delivery pad checkpoints (27), wherein the check points include latitude, longitude and altitude, wherein the check points are defined in three dimensional maps on server (110) as common building check points (28) on common building buffer zone rectangles or lines (29) at distance from building models (112), the floor check points (22) are defined on floor buffer zone rectangles or lines (23) at distance from building models (112), UAV (116) delivery pads (708) and the drone

delivery pad checkpoints (27) are defined on drone delivery pad (708).
3. The method as claimed in claim 1, wherein navigating UAV (116)
comprises:
loading, by the processor (121), the product (715) on the UAV (116);
take off, by the processor (121), of UAV (116) and enrooting to the user’s delivery point consisting of common building check points (28);
identifying, by the processor (121), the exact delivery location of the product (715) where it needs to be drop off or delivered;
travelling, by the processor (121), horizontally to common building check points (28);
travelling, by the processor (121), vertically downward to floor check points (22).
4. A system for delivering products using Unmanned Aerial Vehicle
(UAV) (116), wherein the system comprises:
a generating module (128), coupled with the processor (121), wherein the generating module (128) is configured to generate one or more paths to be traversed by a UAV (116) based on one or more parameters, wherein the one or more Parameters comprise maximum UAV (116) flight altitude allowed in an area and weather data of the area, other UAV (116) in the area, a start point, and an end point, wherein one or more paths are in layers, UAV (116) associated with different payload capacity of UAV (116);

a computing module (130), coupled with the processor (121), wherein the computing module (130) is configured to compute a time require to traverse for each of the one or more paths; and
a navigating module (132), coupled with the processor (121), wherein the navigating module (132) is configured to navigate the UAV (116) over a path selected from the one or more paths based on comparison of the time require to traverse to deliver the product at user’s location.
5. The system as claimed in claim 4, wherein the system comprises:
a defining module, coupled with the processor (121), wherein the defining module is configured to define at least a check point in each of the one or more paths wherein check points comprises common building check points (28) and floor check points (22), wherein the check points includes latitude, longitude and altitude, wherein the check points are defined in three dimensional maps on server (110) as common building check points (28) on common building buffer zone rectangles or lines at distance from building models (112) and floor check points (22) are defined on floor buffer zone rectangles or lines (23) at distance from building models, UAV (116) delivery pads (708).
6. The system as claimed in claim 1, wherein navigating UAV (116)
comprises:
a loading module, coupled with the processor (121), wherein the loading module is configured to load the product (715) on the UAV (116);
a take-off module, coupled with the processor (121), wherein the take-off module is configured to take-off UAV (116) and enrooting to

the user’s delivery point consisting of common building check points (28);
an identifying module, coupled with the processor (121), wherein the identifying module is configured to identify the exact delivery location of the product (715) where it needs to be drop off or delivered;
a travelling module, coupled with the processor (121), wherein the travelling module is configured to travel horizontally to common building check points (28); and
a travelling module, coupled with the processor (121), wherein the travelling module is configured to travel vertically downward to floor check points (22).