By now, you should be familiar with the different choices of beacon profiles, iBeacon and Eddystone. You can always refer them back to working with third party beacons. Both iBeacon and Eddystone protocols transmit a set of proximity sensing identifiers which you can use to conveniently name and identify the beacons distinctly in your venue, no matter how large or small.
This article walks through, via an iBeacon example the best practice to configure a beacon network deployment. The key considerations focus on ease-of-use and organization.
UUID is iBeacon's proximity identifier to distinguish BLE devices in your network. Tags shipped from Fathom™ or beacons from a 3rd party beacon vendor usually come with a common UUID. Commonly speaking, UUID should be representative of your network infrastructure of BLE devices in your organization. The network should be in your control and away from outside access. For example in a retail environment, the 3-story shopping mall in which thousands of beacons are deployed share the same UUID.
UUID is a 128-bit hexadecimal value.
Major is an unsigned integer values between 1 and 65535. The rule of thumb is to use unique Major value for logical grouping. Going back to the retail example, the Major values can be assigned to individual floors or areas in the mall.
Minor is an unsigned integer values between 1 and 65535. Minor value should be indicative of each beacon under your organization and under a particular group. For example, one hundred beacons on 3rd floor of the mall can be assigned Minor values 1 to 100.
In the Fathom Control system, you can view and modify the UUID, Major and Minor values for the Tags. Modification for those values of 3rd party beacons can be done with the vendors' applications.
In this venue, you can see that the UUID and the Major values are uniform across the three beacons which are deployed on the same infrastructure and physically on the same building floor. The Minor value uniquely identify each of the beacons.
Once you determine the logical structure of your beacon network and assign the iBeacon profile for each Tag or beacon, you can distinctly identify them through the search bar in Fathom Control. You then can find them through the Devices list and/or locate them on the Venue map.
In conclusion, here is an example to a beacons network hierarchy and allocation of its respective iBeacon profiles.