Xmpp Web Service for Total VideoConference

[edit] What is Total VideoConference?

The goal of “Total Videoconference” can be resumed in the following steps:

1. When some person accesses the videoconference room, a presence sensor detects him.
2. The system checks the calendar of this person and checks if there is a planned event in short and where.
   In this case, a videoconference is planned at a certain hour with a customer in the videoconference room.
3. The customer’s videoconference number is retrieved from the contacts of this person.
4. A videoconference with the customer is established automatically at the scheduled time.

Total VideoConference is based on the orchestration of several Web Services using WS-BPEL. BPEL is the standard language defining structures to write and orchestrate business processes.It defines a set of basic control structures like conditions or loops as well as elements to invoke web services and receive messages from them.

[edit] Goal of the Xmpp Web Service

We have several orchestrated web services to fulfil our purpose. One of this web services is the Xmpp Web Service.It is responsible for sending the location of the detected bluetooth device to the location server locserver@osami.tid.es via xmpp. The information sent is formatted as an XML file, having the same structure defined by the DTD file provided by Telefonica i+d on the Osami Media Wiki.

To realise the xmpp connections the web service uses an own java client using the java Smack API directly. Once the xmpp location server response is received, our system can continue the normal work flow and the video conference could take place.

If the desired response from the server is not received, the TotalVideoConference service is interrupted. In other words, the response received from the location server acts as a necessary permission for the performance of our service.