Alcatel-Lucent XML Web Services White Paper

Abstract: This white paper presents the Alcatel-Lucent XML Web Services with an introduction to web services technology and a quick description of each Alcatel-Lucent XML Web Services.

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

1/17

Note: This White Paper corresponds to the Alcatel-Lucent XML Web Services Release 3.0.

TABLE OF CONTENTS

1

INTRODUCTION

3

2

WEB SERVICES AND SERVICE ORIENTED ARCHITECTURE OVERVIEW

4

2.1 2.2 2.3 2.4 3

WEB SERVICES : THE ACTORS. WEB SERVICES : THE CORE SPECIFICATIONS. WSDL SOAP

ALCATEL-LUCENT XML WEB SERVICES 3.1 ALCATEL-LUCENT XML WEB SERVICES ARCHITECTURE 3.2 ALCATEL-LUCENT WEB SERVICES. 3.2.1 MY PHONE WEB SERVICES. 3.2.2 MY MESSAGING WEB SERVICES 3.2.3 MY ASSISTANT WEB SERVICES 3.2.4 MY MANAGEMENT WEB SERVICES 3.3 ALCATEL-LUCENT XML SERVICES: MY IP TOUCH XML SERVICES 3.3.1 OVERVIEW 3.3.2 ARCHITECTURE 3.3.3 AVAILABLE SERVICES

4

CONCLUSION

ESD/ CSBU/eBCA

5 5 6 6 6 7 8 8 10 11 11 12 12 13 15 17

14/05/09 8AL020043132DMASA_Ed4

2/17

1 INTRODUCTION The "Real Time Enterprise" concept is becoming a reality: more demanding customers, employees always on, faster decisions, shorter response time, faster actions… In this new business environment, enterprises want to improve their business agility and get their business up and running faster. That requires: o o o o

Better integration of communication applications in their business processes, Quick reuse of existing services, Reduction of the development time of e-business projects, Reduction in the overall cost of IT system integration.

In parallel, new technologies such as XML (Extended Mark up Language) represent an outstanding opportunity for innovation: o o

Unified Communication supporting both voice and data integration, Internet programming model becoming a new reference for an enormous developer base.

This technology shift will allow to: o o o o

Rethink approach to communications in terms of interactions between persons/resources, Design applications independent from platforms/OS, Develop new services: merging voice, web, mobile, interactive communication, And ultimately, integrate real-time communication within business processes.

XML Web services are the corner stone that allows the integration of communication applications within business processes. Alcatel-Lucent has designed its Enterprise solutions especially for XML Web Services integration. Alcatel-Lucent's approach is articulated in three main dimensions:


Offer a new comprehensive set of XML Web services

Through XML Web services, key features from our communication suite can be exported to External Applications. These key features are coming from Alcatel-Lucent OmniPCX (OmniPCX Enterprise and OmniPCX Office), OmniTouch Unified Communication and IP Touch terminals. Alcatel-Lucent XML Web services are structured in 2 families*: 

Application Phone XML Services - My IP Touch XML Services



Communication Web Services -

ESD/ CSBU/eBCA

My My My My

Phone Web Services Assistant Web Services Messaging Web Services Management Web Services

14/05/09 8AL020043132DMASA_Ed4

3/17

*Note: All Services are not available in every OmniPCX product version. For more details please see the features list.
Reinforce our support to developers and Application Partners By providing them with: o o o




Easy access to Alcatel-Lucent XML Web services (e.g.: free download for all) Strong technical support (e.g.: e-testing for program members), Complete certification to verify the application inter-working with Alcatel-Lucent platforms and then an active promotion through Alcatel-Lucent distribution networks.

Open the Alcatel-Lucent environment to new categories of developers

Alcatel-Lucent wants to develop a vast pool of Web developers around its solutions. Alcatel-Lucent will address new categories of partners, such as independent software vendors, integrators, and Web developers as well as end-user customers who have in-house Web developers or Webmasters. In the remaining part of this paper: Section “Web Services and Service Oriented Architecture overview“ is an introduction to standards and general architecture. These are common concepts which have made possible the vendor independent emerging SOA. The main effect of these standards is that developers don’t have to understand them in detail because most of their tools have integrated this work and present Web services “as easy as a simple click in a checkbox”. Section “Alcatel-Lucent XML Web Services” is a presentation of the Alcatel-Lucent openness architecture and the collection of Services it provides.

2 WEB SERVICES AND SERVICE ORIENTED ARCHITECTURE OVERVIEW Numerous definitions of Web Services exist, each of them contains a reference to the Web, the human user being replaced by an application and HTML substituted by XML. Web Services need to define an infrastructure to exchange messages. A service must describe the messages that it sends and the messages it accepts. These messages must be routed and their workflow could be described by a choreography. An application may be interested in discovering available services. As all these information are transported on networks, security is an important point. Transaction, reliability and asynchronicity are concepts which have to be studied to obtain a global Service Oriented Architecture (SOA). Web Services invocation involves data structures and method calls using XML syntax. These XML streams are exchanged using standard transport protocols and retrieved on the server end. The communication's endpoint is an address in a URL format. Each technology involved in this process is based on standard and built with publicly described elements. This ensures vendor, platform and language independence. Based on the web technology, Web Services inherits its loosely coupled aspect. None of the underlying elements are vendor dependant, and each one can be replaced by another standard compliant element. Web services can also be compared to client/server technology like DCOM, RMI or Corba. The main asset of Web Services is their open standardized description.

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

4/17

A consumer of a web services is not dependant of the producer of this service. If a consumer wants to change its platform or its language, it’s just a question of development tool, the consumer hasn’t to ask or wait for any adaptation from the producer. Even the tools are widely available, avoiding any platform vendor dependencies.

2.1 WEB SERVICES : THE ACTORS. Three different actors are involved in the Web services process. o The service provider provides an application server and publishes the services via a WSDL file. o The developer discovers the service (1) by computing the WSDL file; his favorite development tool will generate automatically all the glue between its own application and the web services (2). o The end user, when using the final delivered application, will invoke the Web service (3+4). This will happen transparently for him, only standard protocols are involved in this invocation.

3rd Party Developer

XML Web Services server OmniPCX Communication Server

1

WSDL

2

4 Sdk 3rd party

application

3

2.2 WEB SERVICES : THE CORE SPECIFICATIONS. To reach vendor independence, Web services have been described on a standardized manner. This is the work of a W3C working groups who define WSDL and SOAP and an OASIS group in charge of UDDI. The Web Services Description Language (WSDL) is the standard language used to describe a service. WSDL is used to write the contract between the producer and the consumer of the service. Having a WSDL description, the developer will use his favorite Web Service tool and make it produce all the glue needed to connect to the described Web Service. The Simple Object Access Protocol (SOAP) is a standardized protocol to transport the exchanged data between the two endpoints. It uses XML technologies to define an extensible messaging framework providing a message construct that can be exchanged over a variety of underlying protocols (HTTP, SMTP…). When a WSDL contains definition linked to the use of SOAP, state of the art tools are able to generate automatically all the needed source code. Universal Description, Discovery and Integration (UDDI) provides a standard mechanism for a producer to publish his Web Service and for a consumer to discover it. UDDI is itself a Web service. WSDL, SOAP and UDDI are the main foundations of the Service Oriented Architecture (SOA), which includes the Web Services concept, but this is only the first step of SOA. Security, orchestration, transaction are other aspects to be considered in a complete SOA. ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

5/17

Another important work is the interoperability and the WS-I workgroup, which ensure the common understanding of these standards. Note : Web services and SOA are set of standards. Most of them are still in draft and can evolve. WSDL and SOAP are the core of this technology and can be used today for computer to computer exchange. More ambitious targets are described in SOA, mainly in the workflow perspectives.

2.3 WSDL Web Services Definition Language (WSDL) is the key definition in the Web Services oriented architecture. The WSDL is an XML format for describing network services in a platform-independent fashion. A WSDL document must contain enough information for a consumer of a service to build a request and to analyze the response when invoking this service. WSDL is a standardized description of the web services, which can be processed from any plate-form and with any conformant tool. The wide acceptance of WSDL is the main success factor of Web services. The WSDL is probably the most important element when checking the conformance between the Web Service to consume and the development platform. Developer must ensure that the content of the WSDL document provided by the producer of the web service are compatible with the WS tools they have. First the version of WSDL must be checked. WSDL 1.1 is submitted (by a group including contributors from IBM, MicroSoft, HP, Intel, SAP, Oracle…) to W3C on March 2001. This is the most widely deployed version. WSDL 1.2 renamed WSDL 2.0 is in progress since 2002.

2.4 SOAP SOAP is a messaging protocol, which provides a mechanism to exchange messages between two applications. SOAP defines how to construct a message, how to exchange a message and a model for processing the messages. The binding with the underlying transport protocol is also described. SOAP version 1.2 is a W3C recommendation since June 2003. SOAP version 1.1 was already available for a few years. SOAP defines a message as being a SOAP envelope including a SOAP header and a SOAP body. The SOAP body must contain the Payload and the SOAP header is used to process the message. The transport protocol binding describes how to use the selected protocol to transport the SOAP envelope. SOAP 1.1 and SOAP 1.2 define a normative binding with HTTP. SOAP describes a binding framework for vendors to bind with most of the current protocols. Data serialization in the payload is done by encoding the data in XML. Two main approaches of encoding exist : either SOAP is used to exchange general messages or SOAP is used to implement a RPC mechanism and the encoding is specified by a specific SOAP RPC representation. Note : SOAP is not linked only to HTTP. Any transport protocol can be used to carry the soap envelope. Data Encoding is the key point for automatic source code generation by development tools.

3 ALCATEL-LUCENT XML WEB SERVICES Alcatel-Lucent XML Web Services are a suite of powerful services delivered to the developers to take benefit of the Alcatel-Lucent communication solution. Each service is defined inside a global XML Web Services framework coherence, easing the developer to mix them and so increase the efficiency of his own application. ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

6/17

The XML Web Services framework concentrates global concerns for security, authentication, licensing and routing when invoking an Alcatel-Lucent XML Web services. The XML Web Services framework is built around the enterprise users, and takes care of the global services topology. The developer doesn’t need to do more than assemble services with his application and deliver them to the users. Users only have to authenticate themselves and don’t have to be aware of the complexity of the existing communication infrastructure. The XML Web Services framework leverages the emerging Service Oriented Architecture to expose and publish the Alcatel-Lucent XML Web Services suite. By using such open technology, an application can evolve without external constraint linked to the use of the Alcatel-Lucent framework. IP Touch terminals XML Services are only presentation services provided to an external application. Those services (display information and get action prompts by the user), although integrated in the XML Web Services framework for security, authentication, licensing… are not defined using WSDL and SOAP as the remaining Alcatel-Lucent Web Services.

3.1 ALCATEL-LUCENT XML WEB SERVICES ARCHITECTURE The Alcatel-Lucent XML Web Services are a set of solution to be used by application to interact with an Alcatel-Lucent PCX communication system. It is built on Alcatel-Lucent XML Web Services framework. The Alcatel-Lucent XML Web Services framework contains a Web Services ready container able to manage security, authentication and license for the published services. The Alcatel-Lucent XML Web Services framework is managed with a powerful web based management. This management tool is used to define the users of the Alcatel-Lucent communication system and allows the administrator to dispatch selectively access to the Web services by allocating services licenses. Core functionality of the Alcatel-Lucent XML Web Services framework allows developers and their applications to obtain the WSDL contracts for each subset of services with a single HTTP GET request. These WSDL are also available in the SDK package. The Web services implementation uses an AXIS Soap Toolkit embedded in a TOMCAT servlet runner. As web services are a way to present services to the outside world, servlet is the appropriate technology for it.

My Management Web Services My Phone Web Services My Messaging Web Services My Assistant Web Services

SOAP Toolkit (AXIS)

Servlet Engine (Tomcat)

XML WS Interactive framework

Runtime

Services

Layer IMS PMS OTS UDAS CRS Infrastructure ESD/ CSBU/eBCA

Layer

14/05/09 8AL020043132DMASA_Ed4

Infrastructure

7/17

Omni PCX & Voice mail IMS -> My Messaging Web Services PMS -> PBX Management Server (My Management Web Services) OTS -> Open Telephony Server (My Phone Web Services) UDAS -> Universal Directory Access Server (My Phone Web Services) CRS -> Call Routing Server (My Assistant Web Services)

3.2 ALCATEL-LUCENT WEB SERVICES. As already mentioned, Alcatel-Lucent XML Web Services framework comes with a set of Services allowing application to interact with the Alcatel-Lucent communication solution. Access to Web Services is restricted by a license. Web Services are described with their WSDL contract. As part of the Alcatel-Lucent XML Web Services framework, Web Services are invoked after authentication by login a framework session. The authentication must be done with a framework user identity. Available Web Services are :    

My Phone Web Services, My Messaging Web Services, My Assistant Web Services, My Management Web Services,

My Phone Web Services allow, to an external application, to handle user’s calls on his phone set and to configure a subset of parameters of this phone set. Those parameters define the behavior of the phone set. My Messaging Web Services allow to interact with an user’s voice mail. My Assistant Web Services allow to manage Call Routing capability of an user. My Management Web Services allow to configure a subset of parameters of an user’s phone set. Those parameters are modified when assigning a phone set to an employee. Note: All Services are not available in every product version. For more details please see the features list of each product.

3.2.1 MY PHONE WEB SERVICES. Supported phones sets range from Alcatel-Lucent reflexes Sets, wireless DECT and PWT, to analog sets, used in business mode. Specific restrictions must be checked in the sdk documentation. My Phone Web Services are made of 3 subsets of features: • • •

Call control Services : to manage calls on the user’s business phone set Phone Set Programming Services : to customize the behaviour of the user’s phone set and to customize the phone set associated resources Advanced phone Services : to access OmniPCX Directories and to manage user’s nomad mode and user’s Call Log information

3.2.1.1 Call control Services

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

8/17

Call control Services allow to control calls on the user’s business phone set. Available features are :       

Make a call Take an incoming call Clear a call Make a conference with two calls (3 parts) Transfer a call Dial a DTMF Record the current call

These features can be used to manage the phone set call control for a user in a business context. A business application can extract from its customer database a phone number to be dialed and call it by using Make a Call. A mouse click or a button pressed can be associated to a Take an incoming call request. Complex Pin code can be played from a secured application towards an interactive server by using the Dial a DTMF On a more intensive use case of a phone set, when multiple calls become more usual, a finest supervision of the phone set will be required. This is obtained by receiving the call progress information. Call progress information are available with specifics messages described in the contract WSDL. To receive these information, the application must subscribes to these notifications and give as parameter a server url ready to receive SOAP requests as defined in the above WSDL contract. Each Call progress information is referenced with a Call reference. Each Call progress information contains :    

The phone number of the other party The name of the other party The state of the call The associated data if existing in the correlator

Call state is an enumeration :  Init  Ringing incoming  Ringing Outgoing  Active  Held  Conferenced  Recording  Waiting  Dialing  Releasing  Unknown The 3rd party application must follows the calls state to be able to use selectively a feature like transfer when more than 2 calls are existing. Call progress information subscribing is used to implement a popup information on incoming call. My Phone Web Services offer also the possibility 



To associate a correlator data (call reference managed by external application) to each call. The associated call reference is used by external application to retrieve the context of the call (for example associated CRM data) To manage the user’s Personal Phone Book

Furthermore there are additional notification messages :

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

9/17

• • •

each time there is change of Forward, Overflow, Lock, Do not disturb, Camp on state each time there is a new unanswered call each time there is change of nomadic state

3.2.1.2 Phone Set Programming Services : Phone Set Programming Services allow : - management features to customize the behavior of his phone set - data programming features to customize the phone set physical resources Phone set behavior management features allow to :      

Get these phone set managements current state De/Activate a forward in immediate, busy, no answer, no answer or busy mode Lock / unlock the phone set use De/activate a Do Not Disturb De/activate the overflow toward the associated set in immediate, busy, no answer, no answer or busy mode De/activate Camp On

Data programming features allow to :    

Manage the Speed Dialing Keys (SDK) of the phone set Manage the User Programmable Keys (UPK) of the phone set Define an associated set Change the phone set secret code

3.2.1.3 Advanced phone services Those features allow to consult the OmniPCX Phone Book and a set of LDAP Directory servers configured within OmniTouch Unified Communication environment. Advanced phone services provide also the capability to manage nomad mode of the user and to manage his Call Log information. Nomad mode allows to forward incoming calls to an external PSTN phone (GSM, Home phone…) or to request, from the application windows, an outgoing call from the external PSTN phone with all the cost affected to the user’s business phone.

3.2.2

MY MESSAGING WEB SERVICES

My Messaging Web Services are used to interact with an Alcatel-Lucent Voicemail 4635 or an AlcatelLucent Voice Mail 4645 or VXML voice mail of OmniTouch Unified Communication. The Alcatel-Lucent Voicemail systems are powerful systems, which manage the voice messages for a subscriber. A user can interact via a phone set and is guided either by interactive voice guidance or by phone set display. The phone set could be the user’s business phone or an external PSTN phone In an application context, a user can manage his voice message with an e-mail client and a wave player. To reach a more flexible integration, My Messaging Web Services allow a user to manage his voice messages in an e-mail client and to keep the voice media play or record via the phone set. My Messaging Web Services allow to :    

Play a voice message on the phone (with Pause, resume and stop) Forward the message to another phone set Record a voice message from the phone (with Pause, Resume, stop, play for verify) and Send to one or more persons Delete a voice message

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

10/17



Callback the sender

3.2.3 MY ASSISTANT WEB SERVICES My Assistant Web Services provide, to an external application, the ability to set and review the rules that route incoming calls of an user. The user may choose different routes for each of the following cases: • • •

The user is available for calls The user isn’t available (Do Not Disturb). The user wants to filter his calls (screening) based on the caller number and/or on time of day.

The user chooses the destination terminal for his calls and chooses if he wants to receive all the calls or if he wants to filter them. Otherwise he can choose to be in a not disturb mode. This destination may be one of the following: • •

Office Phone External PSTN phone (Mobile phone, home phone…)

The user may set some additional route destinations to describe its preferences in case of busy calls or not answered calls. When a call is not answered or when the destination is busy, the subscriber may want to route the call to one of the following destinations with the escape rules: • • • •

Voice mail Colleague: This number is a pre-programmed number Other No overflow

If the destination, which belongs to escape rules, cannot be reached or doesn’t answer the exception rule is used. The exception rule is used when for all the routing states, the final destination cannot be reached. The destination (“last issue”) of the exception rule is managed by the administrator. It can be voicemail, or any other destination.

3.2.4 MY MANAGEMENT WEB SERVICES My Management Web Services are designed to help the development of a Global Enterprise Identity Management solution. Such solution is proposed by Alcatel-Lucent partners as Computer Associates or Calendra. My Management Web Services will be progressively enriched in order to allow more and more external applications to interact with the configuration data of Alcatel-Lucent communication systems. When assigning a phone set to an user, external applications use My Management Web Services to manage subscribers of OmniPCX system. It is possible to change:

Name of the subscriber First name of the subscriber Entity identifier Usable in call by name

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

11/17

Language identifier Name of the pickup group Identifier of the cost center Class of service External access class External forwarding class Class of connection Tandem set

External Applications can read the phone book, entities, cost centers, pick-up groups and available languages. Those elements are needed in order to help selecting the correct value for previous parameters.

My Management Web Services allow to manage secondary subscribers and external subscribers of the OmniPCX. Secondary subscribers are users that share the phone set with another user. External subscribers correspond to customers or partners numbers. External subscribers are defined in the speed dialing table of the OmniPCX. My Management Web Services provide also management services identical to Phone Set Programming Services in My Phone Web Services allowing to customize the behavior of the user’s phone set and to customize the phone set associated resources (see 3.2.1.2) Furthermore the list of accessible PCX is available.

3.3 ALCATEL-LUCENT XML SERVICES: MY IP TOUCH XML SERVICES 3.3.1 OVERVIEW My IP Touch XML Services provide means for an application to interact with users of OmniPCX communication servers through their IP Touch terminal. Thanks to this openness, an application is able to take the control of an IP Touch terminal. This lets the application build screens and collect user actions. Screen control is granted when a user activates an application on his terminal. If the user has not activated an application, My IP Touch XML Services still allow the application to issue notifications to the terminal. Example of display built with My IP Touch XML Services :

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

12/17

Applications designed on My IP Touch XML Services are visible from the idle screen of IP Touch terminals, providing easy and direct accessibility. My IP Touch XML Services support on-line help that application users can directly consult from their IP Touch terminals. My IP Touch XML Services don’t allow an application to take control of voice on the IP Touch terminal.

3.3.2 ARCHITECTURE My IP Touch XML Services are provided thanks to the Presentation Server. The Presentation Server integrates an HTTP client, which behaves like a browser. External application is a Web application and is hosted on an HTTP server (any WEB server). One URL pointer to this application is configured into the IP Touch Presentation Server. When a user presses a key that is controlled by the external application, this key press is notified to the IP Touch Presentation Server. This server analyses the user action and forwards it to the application thanks to an HTTP request (GET or POST). The application answers to this request with a document containing XML IP Touch language that describes the new screen to be displayed.

WEB server XML Web Services server OmniPCX Communication Server

2 IP Touch Presentation Server

3

XML IP Touch application

4

1

1 - The key press is notified to IP Touch Presentation Server 2 - HTTP GET or POST to inform the application

IP Touch terminal

3 - HTTP answer with the new display in XML IP Touch language 4 - The display is updated

XML IP Touch language is fully compliant with XML specifications issued by W3C consortium. An exhaustive description of XML IP Touch language can be found in the XML IP Touch Developer’s Guide. The Presentation Server is a piece of software that is in charge of providing openness for any application to interact with the IP Touch range of terminals. This openness lets applications build screens and collect user actions. As shown on the picture below, the Presentation Server does work in close relationship with other elements of the architecture. Furthermore, it relies on mechanisms provided by the call server and the terminals.

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

13/17

W eb application

W eb Application

W eb Application

Ca ll Server

Telephony services

C all Handling

Interface with PRS

CS DB

IP To uch language o ver H T TP

Presenta tion Se rvices Com m . Link

Interface with CS

Presenta tion Se rve r IP Touch Pro to col

IP Touch terminals are designed to handle calls and telephony services, of course. But, they are also intended to interact with other applications. Furthermore, users of IP Touch terminals must be able to launch an application while in conversation. He must also be able to start a new call while in an application. In other words, Telephony and applications are relatively independent from one another. They can be both active at a same time. The operation of Telephony is not be impacted by applications and vice versa. The global architecture reflects this independence. The Call Server provides the call control and Telephony services. The Presentation Server provides the applications.

Call Server Screens built by Telephony are transmitted to IP Touch terminals independently from applications screens.

Presentation Server

Call Control And Telephony services

Application

Application Access to applications

Screens built by applications are transmitted to IP Touch terminals independently from Telephony screens.

Routing

IP Touch Protocol

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

14/17

From a terminal point of view, two flows of commands - both in IP Touch protocol – are received concurrently, one from the Telephony and the other from the Presentation Server. The terminal has however only one display and one keyboard. Therefore, it cannot display both simultaneously. It will then either display the screens coming from the Call Server or the screens coming from the Presentation Server. The decision to display one or another is left to the Call Server and the Presentation Server. They can both control this thanks to a specific command from the IP Touch protocol. To properly handle these 2 flows, IP Touch terminals have implemented different Contexts: • •

One Context is dedicated to the IP Touch protocol commands coming from the Call Server. Another Context is dedicated to the IP Touch protocol commands coming from the Presentation Server.

Each of these Contexts handles a virtual IP Touch terminal. Every commands received are processed but have no physical counterpart (no action on the physical terminal). A mechanism is implemented into the terminal to feed the physical terminal with either the Call Server Context or the Presentation Server Context. The servers dynamically control this mechanism. They can request, at any time, to make the Call Server Context or the Presentation Server Context visible.

3.3.3 AVAILABLE SERVICES My IP Touch XML Services provide, to an external application, means to interact with an user through an IP Touch terminal. Those services allow to display information, collect input and react on navigation key press. XML IP Touch language specifies FORMs. FORMs are templates developers have to fill out. Each FORM addresses a different purpose, offering a broad range of design possibilities. FORMS give an abstract layer to terminal specific models. The FORMs only require the pieces of information to be displayed and a phone number. The IP Touch Presentation Server is responsible for the final rendering. A unique FORM can be used to feed several type of display. FORMs help in reducing application’s complexity. A same code can address all the terminals. Using FORMs also makes the application ready for the future. Indeed, an application using these FORMs will be able to operate on future models of terminals without requiring an upgrade of its software.

3.3.3.1 Display services •

Dashboard: A dashboard is displayed when the terminal is idle. It features a MENU tab where all applications available are listed, providing an easy and efficient way for users to find and activate them.

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

15/17

This dashboard also shows the status of each application into the INFO tab. This tab is displayed on top of the screen when an application updates its status.

• • •

Text Forms : Those forms are used to display textual information on screen. It also offers the ability to put a prompt or hint into the text area and all possible actions in action-buttons. Image Forms : Those forms are used to display a picture on screen Popup Form : This form can be used by an application to display a popup window to inform the user about the good or bad execution of an operation for instance. The notification is displayed in a popup window that is placed over the current screen. It is closed after timeout or when the user presses the Back key.

3.3.3.2 Collect Information services • • • • • •

List Form : This form is used to let the user select one item in a list. Input Forms : Those forms are used to let the user type in data. The data entered can be hidden to allow password seizure. Check Forms : Those forms are used to activate or deactivate, to check or uncheck pieces of data. Radio List Form : This form is used to select one item in a list. Slider Form : This form is used to adjust a level. Select Forms : Those forms present a list of action-buttons to be selected to the user.

3.3.3.3 Navigation keys •

action on navigation keys (Back, Home, up, down, right and left) allows to navigate within external application’s screens

•

Help Key: pressing the Help key. Allow to obtain the information that XML IP Touch application provided within the XML description of the screen.

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

16/17

4 CONCLUSION Alcatel-Lucent has designed its Enterprise solutions based on Open Platform providing Open Interface. XML Web Services are central to this Open Interface Strategy. Those Services, based on Internet Technologies, allow to : •

Reinforce support to developers and Application Partners

•

Open the Alcatel-Lucent environment to new categories of developers such as independent software vendors, integrators, and Web developers as well as end-user customers

Ultimately this broadens Alcatel-Lucent portfolio and allows end customer to easily integrate real-time communication within their business processes.

ESD/ CSBU/eBCA

14/05/09 8AL020043132DMASA_Ed4

17/17