US20090271501A1 - System and Method for Building and Execution of Platform-Neutral Generic Services' Client Applications - Google Patents

Abstract

A system and method of building component applications are provided. Component applications are executed on terminal devices, which communicate with a schema-based service via a network and the Internet. The component applications comprise data components, presentation components, and message components, which are written a structured definition language such as XML code. The component applications further comprise workflow components which can be written as a series of and are embedded in the XML code.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
• This application is a continuation application of U.S. patent application Ser. No. 10/745,120 filed Dec. 23, 2003 which claims the benefit of U.S. provisional 60/1436,011, filed Dec. 26, 2002, the entire disclosure of which is herein incorporated by reference, and further claims the benefit of U.S. provisional 60/1503,665, filed Sep. 17, 2003, the entire disclosure of which is herein incorporated by reference.
BACKGROUND
• This application relates generally to communication of services over a network to a device.
• There is a continually increasing number of terminal devices in use today, such as mobile telephones, PDAs with wireless communication capabilities, personal computers, self service kiosks and two-way pagers. Software applications which run on these devices increase their utility. For example, a mobile phone may include an application which retrieves the weather for a range of cities, or a PDA may include an application that allows a user to shop for groceries. These software applications take advantage of the connectivity to a network in order to provide timely and useful services to users. However, due to the restricted resources of some devices, and the complexity of delivering large amounts of data to the devices, developing software applications for a variety of devices remains a difficult and time-consuming task.
• Currently, devices are configured to communicate with Web Services through Internet based Browsers and/or native applications. Browsers have the advantage of being adaptable to operate on a cross-platform basis for a variety of different devices, but have a disadvantage of requesting pages (screen definitions in HTML) from the Web Service, which hinders the persistence of data contained in the screens. A further disadvantage of Browsers is that the screens are rendered at runtime, which can be resource intensive. Native applications have the advantage of being developed specifically for the type of device platform, thereby providing a relatively optimized application program for each runtime environment. However, native applications have disadvantages of not being platform independent, thereby necessitating the development multiple versions of the same application, as well as being relatively large in size, thereby taxing the memory resources of the device. Further, application developers need experience with programming languages such as Java and C++ to construct these hard coded native applications. There is a need for application programs that can be run on client devices having a wide variety of runtime environments, as well as having a reduced consumption of device resources.
• The systems and methods disclosed herein provide a component based application environment to obviate or mitigate at least some of the above presented disadvantages.
SUMMARY
• Current application programs are not adaptable to be run on clients having a wide variety of runtime environments, and can undesirably consume too much of device resources. Browsers are an application program that have a disadvantage of requesting pages (screen definitions in HTML) from a Web Service, which hinders the persistence of data contained in the screens. A further disadvantage of Browsers is that the screens are rendered at runtime, which can be resource intensive. Native applications are a further example of current application programs which have disadvantages of not being platform independent, thereby necessitating the development multiple versions of the same application, as well as being relatively large in size, thereby taxing the memory resources of the device. Contrary to current application programs, a system of building and executing platform neutral generic schema defined services through component applications is provided. The system comprises component applications which execute on the devices, which communicate with network service via a network such as the Internet. The component applications comprise one or more data components, presentation components, and/or message components, which are written in a structured definition language such as XML code. The component applications can further comprise workflow components which contain a series of instructions such as written in a subset of ECMAScript, and, in certain implementations, can be embedded in the XML code. A method of building component applications is also provided. The method comprises steps of creating data components, creating presentation components, and creating message components. The data, presentation, and message components can be written in a structured definition language such as XML. The method further comprises tying together the data, presentation, and message components with workflow components written in a scripting language such as ECMAScript or a subset of ECMAScript.
• A method of interacting with a schema-defined service by a terminal device over a network is provided herein. The method comprising sending from the wireless device a request network message to the web service to establish communication between the web service and the wireless device; receiving at the wireless device a component application in response to the request network message, the component application program comprising a plurality of components: a first set of the components having metadata descriptors expressed in a structured definition language having a number of pre-defined elements representing specific attributes of a resource of the wireless device defining how a runtime environment of the wireless device configures the component application program; and a second set of the components being expressed as a series of scripted instructions coupled to the metadata descriptors defining a workflow of the component application program the workflow comprising a workflow component for defining an action to be performed when messages arrive at the wireless device; the components being configured for provisioning by a runtime environment of the wireless device, the runtime environment to produce an executable version of the component application program configuring the wireless device as a client of the web service; wherein the execution of the executable version facilitates a subsequent exchange of data over the wireless network between the web service and the wireless device.
• A wireless device configured for interacting over a wireless network with a web service using an executable version of a component application program comprising a plurality of components is disclosed. The wireless device comprising a device infrastructure for operating the wireless device comprising a processor and an associated memory for executing the executable version; a user interface coupled to the device infrastructure having an input device and an output device configured for communication with the executable version; a network connection interface coupled to the device infrastructure and configured for communicating with the network; and a runtime environment for processing the component application program to generate the executable version for configuring the device as a client of the web service, the runtime environment configured for processing a first set of the components having metadata descriptors expressed in a structured definition language having a number of pre-defined elements representing specific attributes of a resource of the wireless device for defining configuration information of the component application program and a second set of the components being expressed as a series of scripted instructions coupled to the metadata descriptors for defining a workflow of the component application program, the workflow component defining an action to be performed when messages arrive at the wireless device; wherein the execution of the executable version facilitates a subsequent exchange of data over the wireless network between the web service and the wireless device.
• A computer program product for configuring a terminal device for interacting over a network with a schema-based service using an executable version of a component application including a plurality of components is also provided. The computer program product comprises: a computer readable medium; a runtime environment module stored on the computer readable medium for coordinating execution of the executable version for configuring the device as a client of the service, the runtime environment configured for interaction with a first set of the components having descriptors expressed in a structured definition language and a second set of the components being expressed as a series of instructions; wherein the execution of the executable version provides for a subsequent exchange of information over the network between the service and the device.
• In addition, a server configured for providing a schema-based service for interacting with a terminal device over a network is disclosed. The server comprises: a network interface for receiving a request network message to establish communication between the service and the device; a component application program coupled to the network interface for sending in response to the request network message, the component application program including a plurality of components, a first set of the components having descriptors expressed in a structured definition language and a second set of the components being expressed as a series of instructions, the components being configured for provisioning by a runtime environment of the device to produce an executable version of the component application program configuring the device as a client of the service; wherein execution of the executable version provides for a subsequent exchange of information over the network between the service and the device.
• A terminal device configured for interacting over a network with a schema-based service using an executable version of a component application program including a plurality of components is also disclosed. The device comprises; an infrastructure means for operating the device to execute the executable version; a user interface means coupled to the infrastructure means configured for communication with the executable version; a network interface coupled to the device infrastructure and configured for communicating with the network; and a runtime means for coordinating execution of the executable version for configuring the device as a client of the service, the runtime means configured for interaction with a first set of the components having descriptors expressed in a structured definition language and a second set of the components being expressed as a series of instructions; wherein the execution of the executable version provides for a subsequent exchange of information over the network between the service and the device.
BRIEF DESCRIPTION OF THE DRAWINGS
• These and other features will become more apparent in the following detailed description in which reference is made to the appended drawings wherein:
• FIG. 1 is a block diagram of a network system;
• FIG. 2 is a block diagram of a generic terminal device ofFIG. 1;
• FIG. 3 is a block diagram of a component framework of the device ofFIG. 2;
• FIG. 4 is a block diagram of a component application program ofFIG. 2;
• FIG. 4ashows a representative application packaging and hosting model for the system ofFIG. 1;
• FIG. 4bis a model of a client runtime of the device ofFIG. 1;
• FIG. 5 is a flowchart illustrating a method of building the wireless component application ofFIG. 4;
• FIG. 6 is a flowchart of a method for communicating between the device and a schema defined service ofFIG. 1;
• FIG. 7 shows an example method of implementing the component application program ofFIG. 4;
• FIG. 8 shows a further example method of implementing the component application program ofFIG. 4; and
• FIG. 9 is a block diagram of a further example of the device ofFIG. 1.
DESCRIPTIONNetwork System
• Referring toFIG. 1, anetwork system10 comprises a plurality of genericterminal devices100 for interacting with one or more generic schema defined services provided by anetwork server106, via a coupled Wide Area Network (WAN)104 such as but not limited to the Internet. These genericterminal devices100 can be such as but not limited topersonal computers116,wireless devices101, PDAs, self-service kiosks and the like. The generic services provided by theserver106 can be Web Services and/or other services such as but not limited to SQL Databases, IDL-based CORBA and RMI/IIOP systems, Legacy Databases, J2EE, SAP RFCs, and COM/DCOM components. Further, thesystem10 can also have agateway server112 for connecting thedesktop terminals116 via a Local Area Network (LAN)114 to theserver106. Further, thesystem10 an also have awireless network102 for connecting thewireless devices101 to the WAN104. It is recognized that other devices and computers (not shown) could be connected to theweb server106 via the WAN104 and associated networks other than as shown inFIG. 1. The genericterminal devices100,wireless devices101 andpersonal computers116 are hereafter referred to as thedevices100 for the sake of simplicity. Web services are selected for the following description of thesystem10, for the sake of simplicity. However, it is recognized that other generic schema defined services could be substituted for the web services, if desired. Further, thenetworks102,104,112 of thesystem10 will hereafter be referred to as thenetwork104, for the sake of simplicity.
• Referring again toFIG. 1, thedevices100 transmit and receive requests/response messages105, respectively, when in communication with the web services of theserver106. Thedevices100 can operate as web clients of the web services by using the requests/response messages105 in the form of message header information and associated data content, for example requesting and receiving product pricing and availability from an on-line merchant. The web service is an example of a system with which client application programs302 (seeFIG. 2) on thecommunication devices100 interact via thewireless network104 in order to provide utility to users of thecommunication devices100. Themessages105 sent between thecommunication devices100 and the web service could traverse a message-map service (not shown) which converts themessages105 between the differing formats used by thedevices100 and the web service.
• For satisfying the appropriate requests/response messages105, theweb server106 can communicate with anapplication server110 through various protocols (such as but not limited to HTTP and component API) for exposing relevant business logic (methods) to client application programs302 (seeFIG. 2) once provisioned on thedevices100. Theapplication server110 can also contain theweb server106 software, such that theweb server106 can be considered a subset of theapplication server110. Theapplication programs302 of thedevice100 can use the business logic of theapplication server110 similarly to calling a method on an object (or a function). It is recognized that theclient application program302 can be downloaded/uploaded in relation to theapplication server110, through themessages105 via thenetwork104, directly to thedevices100. It is further recognized that thedevices100 can communicate with one ormore web servers106 and associatedapplication servers110 via thenetworks104. It is also recognized that thedevices100 could be directly coupled to theapplication servers110, thereby bypassing theweb servers106, if desired.
Server Environment
• Referring toFIG. 1, theweb server106 providesinformation messages105 which are used by the client application programs302 (seeFIG. 2) on thedevices100. Alternatively, or in addition, theweb server106 may receive and use theinformation messages105 provided by theclient application programs302 executed on thedevices100, or perform tasks on behalf ofclient application programs302 executed on thedevices100. The web service can be defined as a software service of theweb server106, which can implement an interface such as expressed using Web Services Description Language (WSDL) registered in Universal Discovery Description and Integration (UDDI) in a web services registry, and can communicate throughmessages105 withclient devices100 by being exposed over thenetwork104 through an appropriate protocol such as the Simple Object Access Protocol (SOAP). In some implementations, SOAP is a specification that defines the XML format for themessages105, including a well-formed XML fragment enclosed in SOAP elements. Other parts of SOAP specify how to represent program data as XML and how to use SOAP to do Remote Procedure Calls (RPC). These optional parts of SOAP are used to implement RPC-style applications where aSOAP request message105 containing a callable function, and the parameters to pass to the function, is sent from theclient device100, and theserver106 returns theresponse message105 with the results of the executed function. SOAP also supports document style applications where theSOAP message105 is a wrapper around an XML document. A further optional part of SOAP defines the HTTP binding (i.e. header), whereas some SOAP implementations support MSMQ, MQ Series, SMTP, or TCP/IP transport protocols. Alternatively, the web service may use other known communication protocols,message105 formats, and the interface may be expressed in other web services languages than described above.
• In general, web services come as a replacement for legacy Browser-based and Client-Server TCP/IP connected infrastructure and applications. Originally started as a generic machine-to-machine (M2M) communication protocol, web services are becoming a standard for any service-to-service (S2S) or service to consumer (S2C) communications. Based on a set of standard protocols (e.g. WSDL, SOAP, UDDI), web services can provide a platform neutral communication pipe, for example XML-based, that can support synchronous and/orasynchronous communication messages105. Thesystem10 ofFIG. 1 relates preferably to the S2C model and deals with the consumer of the web service operating from some genericterminal device100. Accordingly, the services supplied by theserver106 are utilized by the user of thedevices100 over thenetwork104.
Client Environment
• Referring toFIG. 2, thecomponent applications302 are transmitted via thenetwork104 and loaded into amemory module210 of adevice infrastructure204 of thedevice100. Alternatively, thecomponent applications302 may be loaded via a serial connection, a USB connections, or a short-range wireless communication system such as IR, 802.11(x) Bluetooth™ (not shown). Once loaded onto thedevice100, thecomponent applications302 can be executed by acomponent framework206 on thedevice100, which converts thecomponent applications302 into native code, which is executed by aprocessor208 in thedevice infrastructure204. Alternatively, thecomponent applications302 may be executed as native code or interpreted by another software module or operating system on thedevice100. In any event, thecomponent applications302 are run in a terminal runtime environment provided by thedevice100.
• Referring again toFIG. 1, the client runtime environment provided by thedevices100 can be configured to make thedevices100 operate as web clients of the web services (of the web server106). It is recognized that the client runtime environment can also make thedevices100 clients of any other generic schema-defined services supplied by theserver106. The client runtime environment of thedevices100 is preferably capable of generating, hosting and executing the client application programs302 (which are in the form of component applications—seeFIG. 4 and description herein below) on thedevice100. Further, specific functions of the client runtime environment can include such as but not limited to support for language, coordinating memory allocation, networking, management of data during I/O operations, coordinating graphics on an output device of thedevices100 and providing access to core object oriented classes and supporting files/libraries. Examples of the runtime environments implemented by thedevices100 can include such as but not limited to Common Language Runtime (CLR) by Microsoft and Java Runtime Environment (JRE) by Sun Microsystems.
• The terminal runtime environment of thedevices100 preferably supports the following basic functions for the resident executable versions of the client application programs302 (seeFIG. 2), such as but not limited to:
• provide a communications capability to sendmessages105 to the Web Services of theweb server106 ormessages105 to any other generic schema defined services connected via thenetwork104 to thedevices100;
• provide data input capabilities by the user on an input device of thedevices100 to supply data parts for Web Services' outgoing messages105 (messages to the service) of theweb server106;
• provide data presentation or output capabilities for Web Services' response messages105 (incoming messages) or uncorrelated notifications of theweb server106 on the output device;
• provide data storage services to maintain local client data in the memory module210 (seeFIG. 2) of thedevice100; and provide an execution environment for a scripting language for coordinating operation of theapplication components400,402,404,406 (seeFIG. 4) of theclient application programs302.
• Referring toFIGS. 2,4 and4a, the client runtime (for example provided by the component framework206) loads the metadata contained in thecomponent400,402,404,406 definitions and the builds the executable version of theapplication program302 on thedevice100, via anapplication container300. For example, there are two operational models for client runtime: template-based native execution and metadata-based execution. With the template-based native execution model the runtime hosts data, message, andscreen templates500 pre-built on thedevice100 using the native code. When theapplication program302 definition is loaded, the client environment provided by thecomponent framework206 fills thetemplates500 with metadata-defined parameters from thecomponents400,402,404 and builds the executableclient application program302 in the native format. The workflow script (for example ECMAScript) of theworkflow component406 could be either converted to native code or executed using an appropriate script interpreter502 (e.g., ECMAScript Interpreter) to anative code redirector504, where theredirector504 interprets calls to the scripting language into operations on native components through anative runtime engine506. With the metadata-based execution, the runtime environment of thecomponent framework206 either keepscomponent400,402,404,406 definitions in XML (for example), which are parsed during execution time or uses native representation of XML (for example) nodes. During execution, thenative runtime engine506 operates on definitions of thecomponents400,402,404,406 rather than on native component entities. It is recognized that the template based approach can be more performance efficient over the metadata based execution, but can require a more sophisticated execution environment and more memory resources.
• Therefore, the native client terminal runtime environment provides an interface for theclient application programs302 to thedevice100 functionality of theprocessor208 and associated operating system of thedevice infrastructure204. The runtime environment preferably supplies a controlled, secure and stable environment on thedevice100, in which thecomponent application programs302 execute. The runtime environment provisions the definitions of thecomponents400,402,404,406 to create the actual web client specific for eachrespective device infrastructure204 of thedevices100. It is recognized for the sake of simplicity that the following description hereafter will refer to the client runtime environment being provided by thecomponent framework206, as an example only.
Communication Device
• Referring to again toFIG. 2, thedevices100 are devices such as but not limited to mobile telephones, PDAs, two-way pagers or dual-mode communication devices (seeFIG. 9). Thedevices100 include anetwork connection interface200, such as a wireless transceiver or a wired network interface card or a modem, coupled viaconnection218 to adevice infrastructure204. Theconnection interface200 is connectable during operation of thedevices100 to thenetwork104, such as to thewireless network102 by wireless links (e.g., RF, IR, etc.), which enables thedevices100 to communicate with each other and with external systems (such as the web server106) via thenetwork104 and to coordinate the requests/response messages105 between theclient application programs302 and theservers106,110 (seeFIG. 1). Thenetwork104 supports the transmission of data in the requests/response messages105 between devices and external systems, which are connected to thenetwork104. Thenetwork104 may also support voice communication for telephone calls between thedevices100 and devices which are external to thenetwork104. A wireless data transmission protocol can be used by thewireless network102, such as but not limited to DataTAC, GPRS or CDMA.
• Referring again toFIG. 2, thedevices100 also have auser interface202, coupled to thedevice infrastructure204 byconnection222, to interact with a user (not shown). Theuser interface202 includes one or more user input devices such as but not limited to a QWERTY keyboard, a keypad, a trackwheel, a stylus, a mouse, a microphone and the user output device such as an LCD screen display and/or a speaker. If the screen is touch sensitive, then the display can also be used as the user input device as controlled by thedevice infrastructure204. Theuser interface202 is employed by the user of thedevice100 to coordinate the requests/response message messages105 over the system10 (seeFIG. 1) as employed byclient application programs302 of acomponent framework206, further described below.
• Referring again toFIG. 2, operation of thedevice100 is enabled by thedevice infrastructure204. Thedevice infrastructure204 includes thecomputer processor208 and the associatedmemory module210. Thecomputer processor208 manipulates the operation of thenetwork interface200, theuser interface202 and thecomponent framework206 of thecommunication device100 by executing related instructions, which are provided by an operating system andclient application programs302 located in thememory module210. Further, it is recognized that thedevice infrastructure204 can include a computerreadable storage medium212 coupled to theprocessor208 for providing instructions to the processor and/or to load/updateclient application programs302 in thememory module210. The computerreadable medium212 can include hardware and/or software such as, by way of example only, magnetic disks, magnetic tape, optically readable medium such as CD/DVD ROMS, and memory cards. In each case, the computerreadable medium212 may take the form of a small disk, floppy diskette, cassette, hard disk drive, solid state memory card, or RAM provided in thememory module210. It should be noted that the above listed example computerreadable mediums212 can be used either alone or in combination.
Component Framework of Device
• Referring again toFIG. 2, thecomponent framework206 of thedevice100 is coupled to thedevice infrastructure204 by theconnection220. The client runtime environment thedevice100 is provided by thecomponent framework206, and is preferably capable of generating, hosting and executing the client application programs302 (which are in the form of component applications—see below) from meta-data definitions. Therefore,component framework206 provides the native client runtime environment for theclient application programs302 and is an interface to thedevice100 functionality of theprocessor208 and associated operating system of thedevice infrastructure204. Thecomponent framework206 provides the runtime environment by preferably supplying a controlled, secure and stable environment on thedevice100, in which thecomponent application programs302 execute in anapplication container300, for example. Theapplication container300 can be referred to as a smart host container for theclient application program302, and can be responsible for analyzing message meta-data (of themessages105—seeFIG. 1) and for updating the representation of the meta-data in thememory module210.
• Referring toFIG. 3, thecomponent framework206 can be used to execute the client application programs302 (such as Web Service client applications) within the terminal runtime environment and can support access to Web Service operations of theweb servers106 and associated application servers110 (seeFIG. 1), via the request/response messages105. Thecomponent application programs302 comprise software applications which are executed by thecomponent framework206. Thecomponent framework206 creates theapplication container300 for eachcomponent400,402,404,406 (seeFIG. 4) of theapplication program302, each time that thecomponent application program302 is executed. Theapplication container300 loads thecomponents400,402,404,406 of theapplication program302 and can create native code which is executed by theprocessor208 in thedevice infrastructure204. Thecomponent framework206 therefore provides thehost application containers300 for provisioning the definitions of thecomponents400,402,404,406 to create the actual web client specific for eachrespective device infrastructure204 of thecommunication devices100,116. The application container can provision thecomponent application302 as per the template-based native execution and metadata-based execution models as described above.
• Referring again toFIG. 3, thecomponent framework206 can also provide framework services304 (a standard set of generic services) to theclient application programs302, in the event certain services are not included as part of thecomponents400,402,404,406 (seeFIG. 4) or received as separate components (not shown) as part of thecomponent application program302. Theapplication program302 hascommunications214 with theapplication container300, which coordinatescommunications216 with theframework services304, as needed. The framework services304 of thecomponent framework206 coordinate communications via theconnection220 with thedevice infrastructure204. Accordingly, access to thedevice infrastructure204,user interface202 andnetwork interface200 is provided to theclient application programs302 by thecomponent framework206. In addition, theclient application programs302 can be suitably virus-resistant, since theapplication containers300 can control and validate all access of thecommunications214,216 of thecomponent framework206 to and from theclient application programs302. It is recognized that a portion of the operating system of the device infrastructure204 (seeFIG. 2) can represent theapplication container300.
• Referring again toFIG. 3, the below describedcomponents400,402,404,406 (seeFIG. 4) of theapplication program302, once provisioned on thecommunication device100,116 are given access to the predefined set offramework services304 by theapplication containers300 of thecomponent framework206. The framework services304 include such as but not limited to acommunication service306, apresentation service308, apersistence service310, anaccess service312, aprovisioning service314 and autility service316. Thecommunication service306 manages connectivity between thecomponent application programs302 and theexternal system10, such as themessages105 and associated data sent/received in respect to the web service (by the communication service306) on behalf of thecomponent applications302. Thepresentation service308 manages the representation of thecomponent application programs302 as they are output on the output device of the user interface202 (seeFIG. 2). Thepersistence service310 allows thecomponent application programs302 to store data in the memory module210 (seeFIG. 2) of thedevice infrastructure204. Theaccess service312 provides thecomponent application programs302 access to other software applications which are present on thecommunication device100,116. Theprovisioning service314 manages the provisioning of software applications on thecommunication device100,116. Application provisioning can include requesting and receiving new and updatedcomponent application programs302, configuringcomponent application programs302 for access to services which are accessible via thenetwork104, modifying the configuration ofcomponent application programs302 and services, and removingcomponent application programs302 and services. Theutility service316 is used to accomplish a variety of common tasks, such as performing data manipulation in the conversion of strings to different formats.
• It is recognized that theframework services304 of thecommunication device100 can provide functionality to thecomponent application programs302, which can include the services described above. As a result, thecomponent application programs302 can have access to the functionality of thecommunication device100 without having to implement it. Thecomponent framework206 of the device100 (seeFIG. 2) has only preferably one copy of the code which implements these services present in theframework services304, regardless of the number ofcomponent application programs302 which are present, thereby minimizing code duplication of the framework services304. Further, unlike ordinary applications where all service requests or service API calls are programmed by developers in the native code, thecomponent definitions400,402,404 andworkflow406 describe service requests using a structured definition language such as XML and the set of instructions such as ECMAScript. The structured definition language provides a non-procedural definition of the application'suser interface202, persistent storage and communications with the Web Service, while the instructions provide the procedural component linkage. The Client runtime environment interprets thesedefinitions400,402,404 into the native calls to supported services.
Component Application Program
• Referring toFIG. 2, the Web Service (for example)client application programs302 are executed within the terminal runtime environment of thecomponent framework206 and support access to Web Service operations provided by the server106 (seeFIG. 1). WSDL and SOAP protocol definitions clearly imply a messages/data pattern. In a WSDL Web Service definition, the operations are defined using the notion of messages and data parts, which are used to define the Web Serviceclient application programs302 as a set of therelated data400 and themessage404 components (seeFIG. 4).
• Referring toFIG. 4, a block diagram of thecomponent application program302 comprises thedata components400, thepresentation components402 and themessage components404, which are coordinated byworkflow components406 throughcommunications214 with theapplication container300. The structured definition language can be used to construct thecomponents400,402,404 as a series of metadata records, which consist of a number of pre-defined elements representing specific attributes of a resource such that each element can have one or more values. Each metadata schema typically has defined characteristics such as but not limited to; a limited number of elements, a name of each element, and a meaning for each element. Example metadata schemas include such as but not limited to Dublin Core (DC), Anglo-American Cataloging Rules (AACR2), Government Information Locator Service (GILS), Encoded Archives Description (EAD), IMS Global Learning Consortium (IMS), and Australian Government Locator Service (AGLS). Encoding syntax allows the metadata of thecomponents400,402,404 to be processed by the device infrastructure204 (seeFIG. 2), and encoding schemes include such as but not limited to XML, HTML, XHTML, XSML, RDF, Machine Readable Cataloging (MARC), and Multipurpose Internet Mail Extensions (MIME).
• Referring again toFIG. 4, thedata components400 define data entities which are used by thecomponent application program302. Examples of data entities whichdata components400 may describe are orders, users, and financial transactions.Data components400 define what information is required to describe the data entities, and in what format the information is expressed. For example, thedata component400 may define such as but not limited to an order which is comprised of a unique identifier for the order which is formatted as a number, a list of items which are formatted as strings, the time the order was created which has a date-time format, the status of the order which is formatted as a string, and a user who placed the order which is formatted according to the definition of another one of thedata components400. Since data parts (elements) are usually transferred frommessage105 tomessage105 according to Web Services choreography rules, preferably there is persistence ofdata components400.Data components400 may be dynamically generated according to Web Service(s) choreography definitions (if available) or defined by the application designer based on complex type definitions and/or message correlation information.
• Referring again toFIG. 4, themessage components404 define the format of messages used by thecomponent application program302 to communicate with external systems such as the web service. For example, one of themessage components404 may describe such as but not limited to a message for placing an order which includes the unique identifier for the order, the status of the order, and notes associated with the order.Message component404 definitions written in the structured definition language can uniquely represent (and map to) WSDL messages, and can be generated dynamically at runtime. Accordingly, the dynamic generation can be done for the component definitions forclient application messages105, and associated data content, from standard Web Service metadata in the definition language used to express the web service interface, for example such as but not limited to WSDL and BPEL.Web Services messages105 are defined within the context of operation and there is defined correlations between themessage components404 in thecomponent application program302 definition. This correlation could be done using predefined message parameters and/or throughseparate workflow components406, as further defined below.
• Referring again toFIG. 4, thepresentation components402 define the appearance and behavior of thecomponent application program302 as it displayed by theuser interface202. Thepresentation components402 can specify GUI screens and controls, and actions to be executed when the user interacts with thecomponent application302 using theuser interface202. For example, thepresentation components402 may define screens, labels, edit boxes, buttons and menus, and actions to be taken when the user types in an edit box or pushes a button. The majority of Web Service consumers use a visual presentation of Web Service operation results, and therefore provide the runtime environment on theirdevices100 capable of displaying user interface screens.
• Referring toFIGS. 1,4 and4b, it is recognized that in the above described clientcomponent application program302 definitions hosting model, thepresentation components402 may vary depending on the client platform and environment of thedevice100. For example, in some cases Web Service consumers do not require a visual presentation. The application definition of thecomponents400,402,404,406 of thecomponent application program302 can be hosted in a Web Service registry in ametadata repository700 as a bundle of platform-neutral data400,message404,workflow406 component descriptors with a set of platform-specific presentation component402 descriptors for various predefined client runtimes (i.e.specific component frameworks206—seeFIG. 2). When the discovery ordeployment request message105 is issued the client type should be specified as a part of thisrequest message105. In order not to duplicate data, message, and workflow metadata while packagingcomponent application programs302 for different client platforms of thedevices100, application definitions can be hosted on the application server110 (for example) as a bundle of platform-neutral component definitions linked with different sets ofpresentation components403a,403b,403c, representing the different supporteduser interfaces202 of thedevices100. It is also recognized that astandard presentation component402 can be used in the event thespecific device100 is not explicitly supported, thereby providing at least a reduced set of presentation features. When a user makes a discovery ordownload request message105, the client runtime type of thedevices100 is validated and the proper bundle is constructed for delivery by theweb server106 to thedevice100 over thenetwork104. For those Web Service consumers, theclient application programs302 could contain selectedpresentation components403a,b,clinked with thedata400 andmessage404 components through theworkflow components406, thereby providing a customizedcomponent application302.
• Referring again toFIG. 4, theworkflow components406 of thecomponent application program302 define processing that occurs when an action is to be performed, such as an action specified by apresentation component402 as described above, or an action to be performed when messages105 (seeFIG. 1) arrive from thesystem10. Presentation workflow andmessage105 processing are defined by theworkflow components406. Theworkflow components406 are written as a series of instructions in a programming language or a scripting language, such as but not limited to ECMAScript, and can be compiled into native code and executed by theapplication container300, as described above. An example of theworkflow components406 may be to assign values to data, manipulate screens, or send themessage105. Theworkflow component406 supports a correlation between themessages105 and defines application flow as a set of rules for operations on theother components400,402,404. Multiple workflow components can be defined with respect to a givenapplication program302. Such additional workflow components, similar to themultiple presentation components403a,403b,403c, can define differing work flows based upon different supported capabilities or feature ofparticular devices100.
• ECMA (European Computer Manufacturers Association) Script is a standard script language, wherein scripts can be referred to as a sequence of instructions that is interpreted or carried out by another program rather than by the computer processor. Some other example of script languages are Perl, Rexx, VBScript, JavaScript, and Tcl/Tk. The scripting languages, in general, are instructional languages that are used to manipulate, customize, and automate the facilities of an existing system, such as thedevices100. In such systems, useful functionality is already available through the user interface202 (seeFIG. 2), and the scripting language is a mechanism for exposing that functionality to program control. In this way, thedevice100 is said to provide the host runtime environment of objects and facilities which completes the capabilities of the scripting language.
• Specifically, EMCAScript is an object-oriented programming language for performing computations and manipulating computational objects within the host runtime environment. ECMAScript can be used as a Web scripting language, providing a mechanism to performserver106,110 computation as part of the Web-based client-server architecture of the system10 (seeFIG. 1). ECMAScript provides core scripting capabilities for a variety of host runtime environments, and therefore the core scripting language can be considered platform neutral for a number of particular host runtime environments. The component framework206 (seeFIG. 2) can provide the ECMAScript host runtime environment for client-side computation of thedevices100, such as but not limited to; objects that represent windows, menus, pop-ups, dialog boxes, text areas, anchors, frames, history, cookies, and input/output. Further, the host runtime environment of thecomponent framework206 provides a means to attach scripting code to events such as but not limited to change of focus, page and image loading, unloading, error, and abort, selection, form submission, and mouse actions. The scripting code appears within theworkflow components406, combines user interface elements and fixed and computed text and images, and is reactive to user interaction on theuser interface202. The web server106 (seeFIG. 1) provides a different host environment for server-side computation including objects representing requests, clients, and files, and mechanisms to lock and share data. By using the client side and server side scripting together, it is possible to distribute computation between theclient devices100 and theservers106,110 while providing a customizeduser interface202 for the Web-basedcomponent application programs302.
• ECMAScript also defines a set of built-in operators which may not be, strictly speaking, functions or methods. ECMAScript operators include such as but not limited to various unary operations, multiplicative operators, additive operators, bitwise shift operators, relational operators, equality operators, binary bitwise operators, binary logical operators, assignment operators, and the comma operator. ECMAScript syntax resembles Java syntax, however, ECMAScript syntax is relaxed to enable it to serve as an easy-to-use scripting language for developers. For example, a variable in ECMAScript is not required to have its type declared nor are types associated with properties, and defined functions are not required to have their declarations appear textually before calls to them. It is recognized that in a class-based object-oriented programming language, in general, state is carried by instances, methods are carried by classes, and inheritance is only of structure and behavior. In ECMAScript, the state and methods are carried by objects, and structure, behavior, and state are all inherited.
Component Application Program Example
• Accordingly, referring toFIG. 4, theclient application programs302 can be defined as a set of platform-neutral component definitions, namely fordata400 andmessage404 components, andpresentation components402 using XML (or any other suitable structured definition language). Theworkflow components406 can be defined using ECMAScript (or any other suitable platform-neutral scripting language). The client runtime environment of the component framework206 (seeFIG. 2) can generate component templates based on meta-definitions, as further described below, when thecomponents400,402,404,406 of thecomponent application program302 are provisioned on thedevice100. With a large variety of terminal runtime environments, the cross-platform standards such as XML or ECMAScript can be used to define application component metadata instead of pre-building thecomponent application programs302. This delayed binding can allow generic application definitions of thecomponent application programs302 to be run on a wide variety of terminal system environments, represented by variousdifferent devices100.
• Expressing thedata400,message404, andpresentation402 components using XML or its derivatives, and theworkflow component406 using the ECMAScript language or its subset, can allow an application developer to abstract the Web Service client from any specific platform or environment and implement in principle “develop once run everywhere” applications. The following example shows how a Web Servicesclient application program302 could be expressed using a structured definition language, such as but not limited to XML, and a platform neutral scripting/programming language, such as but not limited to ECMAScript, defined components:
ExampleXML Data Components400

• 	<data name=″Order″>

  	<item name=″orderId″ type=″Number″ key=“true”/>
  	<item name=“items″ type=″String“ array=″true″/>
  	<item name=″user″ comp=″true″ compName=″User″/>

  <item name=″orderStatus″ type=″String″/>

  	</data>
  	...

ExampleXML Message Components404

• 	<msg name=“ordConfirmation″ type=”response”
  	action=“mhConfirmation″>

  	<part name=“orderId″ type=″String“/>
  	<part name=“status″ type=″String“/>

  	</msg>
  	...

ExampleXML Presentation Components402

• 	<screen name=″scrConfirmation″ title=“Order Confirmation″
  	param=″Order″>

  	<layout type=″vertical″>
  	<widget type=″label″ value=″Order Confirmation Result:″/>

  < widget type=″edit″ value=″@Order.orderStatus″/>

  	</layout>
  	...

  <menu>

  	<item label=″Continue″ navigate=″@scrMain″/>
  	...

  </menu>

  	</screen>
  	...

ExampleECMAScript Workflow Components406

• 	<actions>

  <function name=”mhConfirmation”>

  	key = ordConfirmation.orderId;
  	order = Order.get(key);
  	order.orderStatus = ordConfirmation.status;
  	scrConfirmation.display(order);

  	</function>
  	...

  	</actions>

• Referring toFIG. 4, as given above, it can be seen that themessage components404 relay the required data for the input and output of themessages105. The correspondingdata components400 coordinate the storage of the data in the memory module210 (seeFIG. 2) of thedevice100 for subsequent presentation on the user interface202 (seeFIG. 2) by thepresentation components402. Theworkflow components406 coordinate the transfer of data between thedata400,presentation402, andmessage404 components.
• There are a number of potential advantages to the component application model as described above. For example, there is a minimized need for a mediator in the service protocol between client runtime and service endpoint. Unlike browser-based applications that require a Web Server to host additional components (e.g. servlets, JSP, ASP, etc.) to connect HTML pages data/requests with a service endpoint, the component application model allows end-to-end direct connectivity between the client runtime of thedevice100 and the service endpoint using Web Service (on the server106) message component definitions.
• Further, the component application model combines the simplicity of browser-based applications with the efficiency of native application execution. Unlike browser applications, rendering screens at runtime is minimized as thewhole application302 definition is downloaded preferably at once and the client runtime environment can generate a native representation of application screens. Additionally, requesting of pages (screen definitions in HTML) from the server is minimized, as the component application model architecture is based onmessage components404 that contain data.
• Further, the component application architecture can provide a relatively small application download size (consisting of component definitions only) as compared to hard coded native applications, and an effective data storage and persistence model. The client runtime is capable of storing and updating atomic data entities directly vs. manipulating rendered presentations such as HTML pages for browser applications.
• Further, the component application architecture can provide a platform-neutral model. Unlike native applications uniquely developed for a specific client runtime, theapplications302 built using widely adopted standards such as XML and ECMAScript could be reused on a large variety of platforms and truly implement the principle “write once run everywhere”. Further, the combination of non-procedural and procedural application definitions can greatly reduce programming time and effort.
Operation of Component Application Model
• FIG. 5 is a flowchart illustrating a method of building thewireless component application302 for subsequent communication over thenetwork104 to thedevice100. Referring as well toFIG. 3, the method begins withstep600 of creating thedata components400 for defining data entities such as users and orders. The method continues withstep602 of creatingpresentation components402 for defining user-interface elements such as screens, buttons, menus and images. The method continues withstep604 of creatingmessage components402 for defining messages formats which are sent to external systems such as web services on the server106 (seeFIG. 1). Thecomponents400,402,404 are expressed in the structured definition language such as but not limited to one based on XML. The method concludes withstep606 of tying together thedata400,presentation402 andmessage404 components withworkflow components406 in order to define the behavior of theapplication302. Theworkflow components406 are written based on a scripting language such as a subset of ECMAScript, which is described above. The method of building awireless component application302 may include fewer or more steps that those shown inFIG. 5.
• Referring toFIGS. 1 and 6,operation800 of the interaction between thedevices100 and the web service of theweb server106 is shown. The web service receives802 therequest message105 requesting that thedevice100 begin communications with the web service. The web service uploads804 the requiredcomponents400,402,404,406 (if any) of thecomponent application302 to thedevice100, in order to support subsequent information exchange between the web service and thedevice100. The device receives the transmittedcomponent application302 and proceeds to provision806 thecomponents400,402,404,406 by the runtime environment, in order to configure the device as a web client of the web service, by producing an executable version of thecomponent application302. The user of thedevice100inputs808 data into the user interface202 (seeFIG. 2) of thedevice100 for subsequent sending810 to the web service as arequest message105 for receiving web service operations. The web service processes therequest message105 and sends812 theappropriate response message105 including data for subsequent output on theuser interface202. Thedevice100 receives814 themessage105 containing the data and the executable version of thecomponent application302 outputs the data appropriately on theuser interface202.Further data exchange816 is performed between thedevice100 and the web service as per above, or the exchange is terminated818 and the executable version of thecomponent application302 is either saved in the memory210 (seeFIG. 2) or is deleted from the runtime environment as desired.
• Referring toFIGS. 1,3 and7, for example,operation900 shows when thedevice100 receives902 theresponse message105 containing message data, theappropriate workflow component406 interprets904 the data content of themessage105 according to theappropriate message component404. Theworkflow component406 then processes906 the data content and inserts910 the data into the correspondingdata component400 forsubsequent storage912 in the memory module210 (seeFIG. 2). Further, if needed, theworkflow component406 also inserts908 the data into theappropriate presentation component402 forsubsequent display914 on the user interface202 (seeFIG. 2).
• Referring toFIGS. 1,3 and8operation1000 showsdata input1002 for an action, such as pushing a button or selecting a menu item, which the user performed1003 on a user-interface element through the user interface202 (seeFIG. 2). Therelevant workflow component406 interprets1004 the input data according to theappropriate presentation component404 and creates 1006 data entities which are defined by theappropriate data components400. Theworkflow component406 then populates1010 thedata components400 with the input data provided by the user forsubsequent storage1012 in the memory module210 (seeFIG. 2). Further, theworkflow component406 also inserts1008 the input data into theappropriate message component404 for subsequent sending1014 of the input data as data entities to the web service in themessage105, as defined by themessage component404.
• It is recognized thatcomponent applications302 which are created using the methods described above can require less time to create than hard coded applications, since thecomponent applications302 do not use full programming languages, but rather use standards-based technologies such as XML and ECMAScript, which are comparatively simple and easy to learn. The methods can result incomponent applications302 in which the user-interface202 and the definition of the data are decoupled. This decoupling allows for modification of anycomponent400,402,404,406 in thecomponent application302 without affecting and requiring substantial changes toother components400,402,404,406 in theapplication302, and thus can facilitate maintenance of thecomponent applications302, including modification and updating of thecomponent applications302 on thedevice100.
• FIG. 9 is a block diagram of a dual-modemobile communication device710, which is a further example of thedevice100 ofFIGS. 1 and 6. The dual-modemobile communication device710 includes atransceiver711, amicroprocessor738, adisplay722,Flash memory724,RAM memory726, auxiliary input/output (I/O)devices728, aserial port730, akeyboard732, aspeaker734, amicrophone736, a short-rangewireless communications sub-system740, and may also includeother device sub-systems742. Thetransceiver711 preferably includes transmit and receiveantennas716,718, areceiver712, atransmitter714, one or morelocal oscillators713, and adigital signal processor720. Within theFlash memory724, the dual-modemobile communication device710 preferably includes a plurality ofsoftware modules724A-724N that can be executed by the microprocessor738 (and/or the DSP720), including avoice communication module724A, adata communication module724B, and a plurality of otheroperational modules724N for carrying out a plurality of other functions.
• The dual-modemobile communication device710 is preferably a two-way communication device having voice and data communication capabilities. Thus, for example, the dual-modemobile communication device710 may communicate over a voice network, such as any of the analog or digital cellular networks, and may also communicate over a data network. The voice and data networks are depicted inFIG. 9 by thecommunication tower719. These voice and data networks may be separate communication networks using separate infrastructure, such as base stations, network controllers, etc., or they may be integrated into a single wireless network.
• Thecommunication subsystem711 is used to communicate with the voice anddata network719, and includes thereceiver712, thetransmitter714, the one or morelocal oscillators713 and may also include theDSP720. TheDSP720 is used to send and receive signals to and from thetransmitter714 andreceiver712, and is also utilized to receive control information from thetransmitter714 and to provide control information to thereceiver712. If the voice and data communications occur at a single frequency, or closely-spaced set of frequencies, then a singlelocal oscillator713 may be used in conjunction with thetransmitter714 andreceiver712. Alternatively, if different frequencies are utilized for voice communications versus data communications, then a plurality oflocal oscillators713 can be used to generate a plurality of frequencies corresponding to the voice anddata networks719. Although twoantennas716,718 are depicted inFIG. 9, the dual-modemobile communication device710 could be used with a single antenna structure. Information, which includes both voice and data information, is communicated to and from thecommunication module711 via a link between theDSP720 and themicroprocessor738. The detailed design of thecommunication subsystem711, such as frequency band, component selection, power level, etc., is dependent upon thecommunication network719 in which the dual-modemobile communication device710 is intended to operate. For example, a dual-modemobile communication device710 intended to operate in a North American market may include acommunication subsystem711 designed to operate with the Mobitex™ or DataTAC™ mobile data communication networks and also designed to operated with any of a variety of voice communication networks, such as AMPS, TDMA, CDMA, PCS, etc., whereas adevice710 intended for use in Europe may be configured to operate with the General Packet Radio Service (GPRS) data communication network and the GSM voice communication network. Other types of data and voice networks, both separate and integrated, may also be utilized with the dual-modemobile communication device710.
• Depending upon the type of network ornetworks719, the access requirements for the dual-modemobile communication device710 may also vary. For example, in the Mobitex and DataTAC data networks, mobile devices are registered on the network using a unique identification number associated with each device. In GPRS data networks, however, network access is associated with a subscriber or user of a mobile device. A GPRS device typically requires a subscriber identity module (“SIM”), which is required in order to operate a dual-mode mobile communication device on a GPRS network. Local or non-network communication functions (if any) may be operable, without the SIM, but a dual-mode mobile communication device will be unable to carry out any functions involving communications over thedata network719, other than any legally required operations, such as 911 emergency calling.
• After any required network registration or activation procedures have been completed, the dual-modemobile communication device710 may then send and receive communication signals, including both voice and data signals, over the network719 (or networks). Signals received by theantenna716 from thecommunication network719 are routed to thereceiver712, which provides for signal amplification, frequency down conversion, filtering, channel selection, etc., and may also provide analog to digital conversion. Analog to digital conversion of the received signal allows more complex communication functions, such as digital demodulation and decoding to be performed using theDSP720. In a similar manner, signals to be transmitted to thenetwork719 are processed, including modulation and encoding, for example, by theDSP720 and are then provided to thetransmitter714 for digital to analog conversion, frequency up conversion, filtering, amplification and transmission to the communication network719 (or networks) via theantenna718. Although asingle transceiver711 is shown inFIG. 9 for both voice and data communications, it is possible that the dual-modemobile communication device710 may include two distinct transceivers, a first transceiver for transmitting and receiving voice signals, and a second transceiver for transmitting and receiving data signals.
• In addition to processing the communication signals, theDSP720 also provides for receiver and transmitter control. For example, the gain levels applied to communication signals in thereceiver712 andtransmitter714 may be adaptively controlled through automatic gain control algorithms implemented in theDSP720. Other transceiver control algorithms could also be implemented in theDSP720 in order to provide more sophisticated control of thetransceiver711.
• Themicroprocessor738 preferably manages and controls the overall operation of the dual-modemobile communication device710. Many types of microprocessors or microcontrollers could be used here, or, alternatively, asingle DSP720 could be used to carry out the functions of themicroprocessor738. Low-level communication functions, including at least data and voice communications, are performed through theDSP720 in thetransceiver711. Other, high-level communication applications, such as avoice communication application724A, and adata communication application724B may be stored in theFlash memory724 for execution by themicroprocessor738. For example, thevoice communication module724A may provide a high-level user interface operable to transmit and receive voice calls between the dual-modemobile communication device710 and a plurality of other voice devices via thenetwork719. Similarly, thedata communication module724B may provide a high-level user interface operable for sending and receiving data, such as e-mail messages, files, organizer information, short text messages, etc., between the dual-modemobile communication device710 and a plurality of other data devices via thenetwork719. In the dual-modemobile communication device710, acomponent framework206 as described above may also be implemented as a software module or application, or incorporated into one of thesoftware modules724A-724N.
• Themicroprocessor738 also interacts with other dual-mode mobile communication device subsystems, such as thedisplay722,Flash memory724, random access memory (RAM)726, auxiliary input/output (I/O)subsystems728,serial port730,keyboard732,speaker734,microphone736, a short-range communications subsystem740 and any other dual-mode mobile communication device subsystems generally designated as742.
• Some of the subsystems shown inFIG. 9 perform communication-related functions, whereas other subsystems may provide resident or on-device functions. Notably, some subsystems, such askeyboard732 anddisplay722 may be used for both communication-related functions, such as entering a text message for transmission over a data communication network, and device-resident functions such as a calculator or task list or other PDA type functions.
• Operating system software used by themicroprocessor738 is preferably stored in a persistent store such asFlash memory724. In addition to the operating system, which controls all of the low-level functions of the dual-modemobile communication device710, theFlash memory724 may include a plurality of high-level software application programs, or modules, such as avoice communication module724A, adata communication module724B, an organizer module (not shown), or any other type ofsoftware module724N. TheFlash memory724 also may include a file system for storing data. These modules are executed by themicroprocessor738 and provide a high-level interface between a user of the dual-mode mobile communication device and the mobile device. This interface typically includes a graphical component provided through thedisplay722, and an input/output component provided through the auxiliary I/O728,keyboard732,speaker734, andmicrophone736. The operating system, specific dual-mode mobile communication device software applications or modules, or parts thereof, may be temporarily loaded into a volatile store, such asRAM726 for faster operation. Moreover, received communication signals may also be temporarily stored toRAM726, before permanently writing them to a file system located in thepersistent store724.
• Anexemplary application module724N that may be loaded onto the dual-modemobile communication device710 is a personal information manager (PIM) application providing PDA functionality, such as calendar events, appointments, and task items. Thismodule724N may also interact with thevoice communication module724A for managing phone calls, voice mails, etc., and may also interact with the data communication module for managing e-mail communications and other data transmissions. Alternatively, all of the functionality of thevoice communication module724A and thedata communication module724B may be integrated into the PIM module.
• TheFlash memory724 preferably provides a file system to facilitate storage of PIM data items on the dual-modemobile communication device710. The PIM application preferably includes the ability to send and receive data items, either by itself, or in conjunction with the voice anddata communication modules724A,724B, via thewireless network719. The PIM data items are preferably seamlessly integrated, synchronized and updated, via thewireless network719, with a corresponding set of data items stored or associated with a host computer system, thereby creating a mirrored system for data items associated with a particular user.
• The dual-modemobile communication device710 may also be manually synchronized with a host system by placing the dual-modemobile communication device710 in an interface cradle, which couples theserial port730 of the dual-modemobile communication device710 to the serial port of the host system. Theserial port730 may also be used to enable a user to set preferences through an external device or software application, or to downloadother application modules724N for installation. This wired download path may be used to load an encryption key onto the dual-modemobile communication device710, which is a more secure method than exchanging encryption information via thewireless network719.
• Additional application modules724N may be loaded onto the dual-modemobile communication device710 through thenetwork719, through an auxiliary I/O subsystem728, through theserial port730, through the short-range communications subsystem740, or through any othersuitable subsystem742, and installed by a user in theFlash memory724 orRAM726. Such flexibility in application installation increases the functionality of the dual-modemobile communication device710 and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using the dual-modemobile communication device710.
• When the dual-mode device710 is operating in a data communication mode, a received signal, such as a text message or a web page download, will be processed by thetransceiver711 and provided to themicroprocessor738, which will preferably further process the received signal for output to thedisplay722, or, alternatively, to an auxiliary I/O device728. A user of the dual-modemobile communication device710 may also compose data items, such as email messages, using thekeyboard732, which is preferably a complete alphanumeric keyboard laid out in the QWERTY style, although other styles of complete alphanumeric keyboards such as the known DVORAK style may also be used. User input to the dual-modemobile communication device710 is further enhanced with a plurality of auxiliary I/O devices728, which may include a thumbwheel input device, a touchpad, a variety of switches, a rocker input switch, etc. The composed data items input by the user may then be transmitted over thecommunication network719 via thetransceiver711.
• When the dual-modemobile communication device710 is operating in a voice communication mode, the overall operation of the dual-modemobile communication device710 is substantially similar to the data mode, except that received signals are preferably be output to thespeaker734 and voice signals for transmission are generated by amicrophone736. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on the dual-modemobile communication device710. Although voice or audio signal output is preferably accomplished primarily through thespeaker734, thedisplay722 may also be used to provide an indication of the identity of a calling party, the duration of a voice call, or other voice call related information. For example, themicroprocessor738, in conjunction with the voice communication module and the operating system software, may detect the caller identification information of an incoming voice call and display it on thedisplay722.
• A short-range communications subsystem740 is also included in the dual-modemobile communication device710. For example, the short-range communications subsystem740 may include an infrared device and associated circuits and components, or a short-range wireless communication module such as a Bluetooth™ module or an 802.11 module to provide for communication with similarly-enabled systems and devices. Those skilled in the art will appreciate that “Bluetooth” and 802.11 refer to sets of specifications, available from the Institute of Electrical and Electronics Engineers (IEEE), relating to wireless personal area networks and wireless LANs, respectively.
• Although the disclosure herein has been drawn to one or more exemplary systems and methods, many variations will be apparent to those knowledgeable in the field, and such variations are within the scope of the application. For example, although XML and a subset of ECMAScript are used in the examples provided, other languages and language variants may be used to definecomponent applications302.

Claims (20)

1. A method of interacting with a web service by a wireless device over a wireless network, the method comprising:

sending from the wireless device a request network message to the web service to establish communication between the web service and the wireless device;

receiving at the wireless device a component application in response to the request network message, the component application program comprising a plurality of components:

a first set of the components having metadata descriptors expressed in a structured definition language having a number of pre-defined elements representing specific attributes of a resource of the wireless device defining how a runtime environment of the wireless device configures the component application program; and

a second set of the components being expressed as a series of scripted instructions coupled to the metadata descriptors defining a workflow of the component application program the workflow comprising a workflow component for defining an action to be performed when messages arrive at the wireless device; the components being configured for provisioning by a runtime environment of the wireless device, the runtime environment to produce an executable version of the component application program configuring the wireless device as a client of the web service;

wherein the execution of the executable version facilitates a subsequent exchange of data over the wireless network between the web service and the wireless device.

2. The method according toclaim 1, wherein the runtime environment provides an interface for the executable version to the functionality of a processor and an associated operating system of an infrastructure of the wireless device and is provided by a component framework providing a set of common services to component applications.

3. The method accordingclaim 2, wherein the executable version of the component application executes in an application container, which is a part of component framework.

4. The method according toclaim 3, wherein the runtime environment is configured for implementing capabilities comprising any of: provide communications for sending a network message to the service, provide data input by a user of the device for supplying data content for a network message associated with the service, provide data presentation in response to a network message associated with the service, provide data storage services for maintaining local client data in a memory of the device, and/or provide an execution environment for a programming language for coordinating operation of the components in the executable version.

5. The method according toclaim 2, further comprising dynamically generating the component descriptors for client application messages and associated data from metadata defined for the service.

6. The method according toclaim 5, further comprising a data component in the first set of component definitions, the data-components for describing a format of the data entities used by the program.

7. The method according toclaim 6, further comprising at least one message component in the first set of component definitions, each message component describing a format of the messages used by the program to communicate over the network with the service.

8. The method according toclaim 7, further comprising a presentation component in the first set of components, the presentation components for defining the appearance and behavior of the component application program as presented on a user interface of the device.

9. The method according toclaim 1, wherein the workflow component in the second set of components defines processing that occurs when an action is to be performed as specified by one of the first set of components.

10. The method according toclaim 2, further comprising executing the executable version by the metadata based execution model, the model configured for keeping the metadata definitions in the structured definition language for parsing during execution.

11. The method according toclaim 2, further comprising executing the executable version by the metadata based execution model, the model configured for using a native representation of structured definition language nodes during execution.

12. The method according toclaim 11, further comprising sending a network message initiated by interaction of a user of the device with a user interface element, the network message comprising data entities created by the workflow component corresponding to the user interface element.

13. The method according toclaim 12, further comprising specifying a client type of the device in the network message for providing the presentation component as platform specific for a predefined runtime environment.

14. The method according toclaim 13, wherein the network message is configured according to the message component for comprising the data entities based on the structured definition language.

15. The method according toclaim 12, further comprising receiving a response network message comprising message data related to the data entities, the response network message configured for subsequent presentation of the message data on a user interface of the device, wherein the message data is formatted based on the structured definition language.

16. The method according toclaim 2, wherein the set of common services include one or more of:

a communication service;

a presentation service;

a persistence service;

an access service;

a provisioning service; and

an utility service.

17. The method according toclaim 8, wherein each message component uniquely maps to a message described by a schema-definition of the service.

18. The method according toclaim 7, wherein the workflow component supports a correlation between messages.

19. The method according toclaim 2, wherein the workflow component defines application flow through a set of rules for operations on the first set of components.

20. A wireless device configured for interacting over a wireless network with a web service using an executable version of a component application program comprising a plurality of components, the wireless device comprising;

a device infrastructure for operating the wireless device comprising a processor and an associated memory for executing the executable version;

a user interface coupled to the device infrastructure having an input device and an output device configured for communication with the executable version;

a network connection interface coupled to the device infrastructure and configured for communicating with the network; and

a runtime environment for processing the component application program to generate the executable version for configuring the device as a client of the web service, the runtime environment configured for processing a first set of the components having metadata descriptors expressed in a structured definition language having a number of pre-defined elements representing specific attributes of a resource of the wireless device for defining configuration information of the component application program and a second set of the components being expressed as a series of scripted instructions coupled to the metadata descriptors for defining a workflow of the component application program, the workflow component defining an action to be performed when messages arrive at the wireless device;

wherein the execution of the executable version facilitates a subsequent exchange of data over the wireless network between the web service and the wireless device.

Images