The registration is the process by which a user subscribe to a service, in this case, to the mF2C System. In mF2C, when talking about registration, reference is made to the creation of a user account that allows to access to the pool of resources and services offered in the whole mF2C environment. Since the registration is a requirement to join to the mF2C network, it can be said that it is the first interaction that users have with the system.

On the other hand, the identification is the set of techniques and procedures aiming at managing the identifiers of a given set of entities. In the scope of this work, special attention is given to the management of the identities of the users and the devices they use in the mF2C network. An effective management of both sets of identifiers will allow a better management of the available network resources, for example through the implementation of machine learning algorithms aiming at predicting the offer and demand in a given period of time and zone. In the same way, a proper identification of users in system will facilitate the tasks of detecting and stopping malicious behavior in the network.

All accounts created and activated will gain access to the dashboard. From there, users will be able to download the docker-compose file (a YAML file that defines multi-container apps). The docker-compose file includes two environment variables in the identification section: the mF2C username and password. these variables are used to read from the host computer the user credentials, thus, user should export them before executing the agent.

Using the user credentials, the identification module will acquire both, the IDKey (aka user identifier) and the deviceID the first time that the agent is executed in a new device. Both identifiers will be assigned by a support Webservice and will be made available for the other agent modules.

Figure 1 shows the sequence diagram and the interactions between the identification module, the registration Webpage and the support Webservice.

The following links redirect to each of the three components previously described. More detailed information about the usage, inputs and outputs can be found in each of the links:

• Registration Website. Dashboard from where users will create their user accounts and download the docker-compose file that will deploy the agent in their devices.
• Support Webservice. Web service responsible for assigning unique identifiers to both users and devices.
• Identification Module. Module responsible for obtaining and sharing the user and the device IDs with other modules within the agent.