Each ‘Area’ contains a tower in the middle which communicates with drones using EM signals. An area is spherical in shape.
The diagram has the following Entities:
- Make: This entity stores information about the construction of a drone.
- Drone: This entity stores information about a drone in use including its Reg_No., Identity Code, Color, Usage Type, Payload Type etc.
- Owner: This entity stores information about an owner of a drone including its name, organization, identification number
- Area: A geographical area which is around a tower situated at Latitude and Longitude and having a Radius. The entity also stores the rules or patterns of a drone’s Identity Code allowed in the area of a tower.
- Asset: An asset is a camera situated at Latitude and Longitude. It is accesible to a tower at Address. It stores information about the uptime and downtime of a camera
The diagram has the following Relationships:
- IS_OF: Make & Drone: Specifies the make of a drone. A Drone can only have one Make.
- OWNS: Drone & Owner: Specifies the owner of a drone. A Drone can only have one Owner.
- Warns: Area & Owner: Stores details about warnings issued to an owner due to unlawful access by a Drone. Drone_Reg_No at Date, Time.
- Visits: Area & Drone: It stores information about a visit of a Drone to an Area, at Date and Time and if the visit was valid or not.
- Detects: Asset & Drone: It stores inforamaton about detection of a Drone by an Asset at Date and Time .
- Monitors: Asset & Area: It stores inforamtion about which Asset monitors which Area. Under present scheme an Asset monitors1 Area.
- Alarm: Asset & Area: Stores details about an Alarm raised by a tower in an Area due to an unknown drone detected by Asset at Date, Time.
Assumptions: We assume that all the drones flying at any point of time are registered with a central authority and hence can be assigned certain unique identifiers.