Next I sat down and highlighted the steps which a user would experience when they came in range of a node.
Assumptions:
-The node has downloaded a recent copy of the registered users MAC address. This table of addresses should be updated hourly.
-The users have their bluetooth devices turned on and they are discoverable.
-The users are lingering at a node for at least a minute.
Steps:
1.Detection, the node detects that a new device has come into range, and requests the MAC address of the new device.
2.Profile acquisition, the address is sent to the node. If the address is registered the node connects to the profile server which attempts to retrieve the profile to send to the node.
3.Profiles comparison, the node receives the profile and compares the keywords with those already stored. It then stores the new profile.
4.Message users, if the node detects a common interest it will send a vCard message to the devices concerned if they are still in range.
5.User messages, having received their message the users can send one of their own, either to the node requesting a full profile in a format suitable for their device, or to the user they have a connection with.
6.Communication, the users concerned talk face to face about the interest.
Steps 1 – 3 are compulsory, occurring whenever any bluetooth enabled device comes in range of a node.
Steps 4 only occurs if the node detects a common interest between the users.
Step 5 and 6 are up to the users, so are optional.
Nodes would have to have enough processing power and storage capacity to store several profiles. Whilst a bluetooth connection can only communicate with up to 7 devices the node should have the capacity to store profiles for many more, as it will not be using the bluetooth to connection to communicate with devices constantly.
Lastly, here is my neat and final representation of the information flow:
