Nwave’s console provides the a possibility of device management using a hierarchical structure. It consists of a few objects , each of them represent every of which represents a single level in the hierarchy.
| Table of Contents |
|---|
Resource group
...
Project
A project is the highest level of the hierarchy. It is often used as a means for regional aggregation. For example, if all devices in a project are placed positioned in the single same city, it makes sense to create a resource group project with the name of the city and use this resource group project for registering registration of all of the devices for inside of that project. Also , resource groups can projects may be used for registering registration of Nwave’s base stations and granting user permissions.
Related pages:
...
Zone
Batch Zone is the 2nd second level of the hierarchy. Batches Zones are very useful as means of typical aggregation (grouping by type of location). For example, if one project contains parking sensors on-street parking bays and on multilevel multi-levels car parking, it makes sense to split up them on batches zones “On-Street”, “Multilevel “Multi-levels parking 1”, “Multilevel “Multi-levels parking 2”, “parking lot near WallMart” and so on.
The most important feature of batches zones is the a possibility of setting up data routing. Nwave is able to push data to client’s services using HTTP and RabbitMQ protocols. For setting up sending data using one of these ways you need to create a route specified to batcha zone.
Related pages:
Creating RabbitMQ route
Group
The group Group is the 3rd third level of the hierarchy. Groups are means of adjacency aggregation (adjoining spots or very close proximity). For example, if there is a need necessity to analyse analyze parking occupancy data of multilevel multi-levels car parking by levels, you can register a group for each every level and keep devices in inside of them. Also , Nwave use uses groups for algorithms of to calculation of realtime real-time availability of parking bays. Groups also can be used for setting up HTTP and RabbitMQ routes.
Related pages:
Creating RabbitMQ route
...
Position
The place Position is the lowest hierarchy level. Places Positions are static mounting points on the map. Places Positions have a lot of properties. The place Position is used to keep information about device’s location. It preserves location information whether device is placed positioned there or not. Users can choose the most successful locations for device placing devices positioning on the map, and then go there and place position their devices. If there is a need necessarily to change a device (upgrade, for example), the place position will keep it’s IDs and client’s services will recognise recognize it like as before, irrespective of the real device ID.
Related pages:
Creating placeposition;
Device binding.
Device
The device Device is the an object which represents a real device in Nwave’s console. It is used to keep information about device ID, warranty, device firmware and device monitoring. Devices have to be bound to places positions for device messages to be processed. If Nwave cloud receives data from a freefreeb(unbound) device, the data is ignored.
Related pages:
Binding device;
Device monitoring.