Due to the cost I will not be able to construct a network of bluetooth and Internet enabled nodes, and dot them around a town center, or the country. Time constraints also hinder any full trials I would have liked to have run of the system. For this reason I propose to create an animation and series of diagrams designed to show how the system would work, after that is I have decided the exact details.
Profile management:
The website is going to be where people update and manage their profile so it will need to be easy to use and work seamlessly with the profile database. For example MySQL (a database management system) and php (a programming language) work well together, and are used in countless instances of websites which store user profiles.
There shouldn't just be one server storing the profiles, but multiple server, in different locations. This ensures that in the event of server crashing data is not lost, and the system still operates. Servers could be configured to mirror the central server, the contents being relayed to other lesser servers, which would then be used by the nodes to retrieve the profiles. In my opinion, and in an ideal world It would be best to keep node servers and site server separated. This means that any one server is either primarily writing data (website server saving profiles) or reading data (node servers sending profiles). If this were the case then the servers could be configured to their specific task.
Central servers would have to have redundant backup servers running, so that even if one crashed the entire system didn't grind to a halt.
Here is my neat and final representation of profile management:
