## 3 Methodology
### Technical Components (Used Technology)  
A brief technical description of the system is found below, see Figure 2.  
* Backend + API REST: The system backend will have an Application Programming Interface available, that centralizes and coordinates all systems actions from the server side. Such API is able to provides an interface for the communication. For the frontend initially, the project use Python, Django and Tastypie.
* Webapp: The web portal for the professional management is implemented by using HTML5, CSS3, JavaScript, jQuery and possibly Twitter Bootstrap. The communication with this part is managed by the output objects from the API.
* AppAndroid: AppAndroid for the user is installed in the device connected to the TV (set top-box) and/or smartphone, they are linked to the API with communication objects (possibly JSON) same way as the Webapps does.  
* Database Server (Backend): The database is a relational one, initially MySQL, although the structure might change to a BI model depending on the number of signals to be stored for any user. This is located in a dedicated stand-alone server and accepts Secure-Shell connections (ssh command line utility). In the future, we might consider the option to migrate to a SQL Server (stand-alone) server depending on the growth of data and the needs for storing it.
* Communication Server: The communication server will keep track of the communication flow and logs the activity between the different components. Elastix technology is a good candidate as it allows VoIP, PBX emails and twits and it does not rely on external sources to process and modulate the calls. Elastix also uses SIP as standard interactive multimedia calls such as video, voice o messaging.  
The Client is sending a Session Initiation Protocol (SIP) package to the User Agent Client (UAC) that will initiate the User Server Agent (UAS).  
The Proxy server SIP Proxys will reroute the SIP to the UAS and returns the SIP to the UAC. Any request can go through different proxy servers to the UAS for allocating and redirecting server to locate the user and to notify to the rest of the components. This process is the ideal way of communication, although we might consider different alternatives. The system also provides a logging server that logs the physical address. The physical and logical address is associated in a routing table located in the logging server. Internet calls will use SIP, Android client ImsDroid (Open source software), Client Html5 SIP and Server WebRTC2 SIP. For signal processing in the communication server we use an experimental simulation of a massive parallel bioinspired system, which will allow to work on new approach for mobile computing. Initially will try P-system [8] architecture in conventional hardware.  
The methods can be applicable in an integrated platform of visual and communication devices. The hardware components for the system agents are:  
* Dedicated server for training the Computer vision mode: Desktop Server 2 GPU units for training a Convolutional Neural Network (CNN).
* Standby Server part: Remote server for logging communication messages and to synchronize the system
* Professional module: Video camera, Smart device
* User module: Video camera, Boxes, TV or any other domestic smart device, smartphone  
Figure 2: The architecture of the system. All actions are performed via API Rest calls to server (blue icon).  
The target system requires an internet connection and as many user modules as patients who will to use the system, see Figure 3.