JP2009087361A - System and method of creating and communicating with component-based wireless application - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system of creating wireless component applications and communicating with them, and a method. <P>SOLUTION: Mobile communication devices communicate with a web service via a wireless network, and the Internet, and optionally communicates with a message-map service. Each wireless component application is executed by a component framework on one of the mobile communication devices, and comprises data components, presentation components, message components, and workflow components. The component framework executes the component application in an application container. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

This application relates generally to wireless communications, and more particularly to software for mobile communications devices.

Today, the number of mobile communication devices such as mobile phones, PDAs with wireless communication capabilities, and two-way pagers is constantly increasing. Software application utilities running on these mobile communication devices are also increasing. For example, a mobile phone
An application that searches for weather in a range of cities may be included, and a PDA may include an application that allows a user to buy groceries. These software applications effectively take advantage of the mobility and connectivity to these wireless networks to provide timely and useful services to users regardless of where they are. However, due to the limitations of mobile communication device resources (eg memory) and the complexity of distributing data wirelessly to mobile communication devices, developing applications for mobile communication devices remains a difficult and time consuming task. It is.

Currently, mobile communication devices are configured to communicate with web services via Internet-based browsers and / or native applications.
Browsers have the advantage of being configurable to work cross-platform for a variety of different devices, but they also have the disadvantage of requiring pages from web services (screen definitions in HTML), Prevent the persistence of data contained in the screen. A further disadvantage of browsers is that the screen is rendered at run time, which can be resource intensive. Native applications have the advantage that application programs that are relatively optimized for each runtime environment are provided by developing specific types of mobile devices. However, since native applications are not platform independent, they require the development of multiple versions of the same application, and are relatively large in size, which has the disadvantage of placing a burden on the memory resources of the mobile device. What is needed is an application program that can be executed on a web service client having a wide range of runtime environments and that consumes less resources on the mobile device.

The systems and methods disclosed herein provide a component-based application environment that at least partially eliminates or mitigates the disadvantages described above.

Current application programs cannot be configured to run on clients with a wide range of runtime environments and can consume undesirably more mobile device resources. A browser is an application program that has the disadvantage of requesting a page from a web service (screen definition in HTML), which hinders the persistence of data contained in the screen. A further disadvantage of browsers is that the screen is rendered at runtime, which can be resource intensive. Native applications are a further example of current application programs, but they are not platform independent, so they require the development of multiple versions of the same application and are relatively large in size, burdening the mobile device's memory resources Has the disadvantage of imposing.

In contrast to current application programs, a system is provided for creating and communicating with wireless component applications. The system includes a mobile communication device that communicates with a web service via a wireless network, the Internet, and / or a message map service as needed. Each wireless component application has a set of components expressed in a structured definition language and a set of instructions that are executed by the component framework on one of the mobile communication devices. This component can include one or more data components, presentation components, message components, and / or workflow components. The component framework executes component applications in the application container. The application container provides access to common framework services including one or more of communication services, screen services, persistence services, access services, provisioning services, and utility services. A message can be sent from the component application to the message map service, which uses the application message map to convert the message into the format required by the web service and send the message to the web service. The response to this message can be sent to the message map service, converted to the format required by the component application, and sent to the component application.

Further, the system for creating and communicating with the wireless component application also provides a method for deploying and communicating with the wireless component application. The method includes deploying a wireless component application on a mobile communication device and deploying a message map on a message map service. The method may further include sending the message to a message map service, in one example, which uses the message map to convert the message into the format required by the web service before the message map service uses the message map service. Send a message to a web service. The method can further include sending a response from the web service to the message map service, the message map service converting the message to the format required by the wireless component application and sending the message to the wireless component application. Send.

In the present application, a mobile communication device configured to provide an executable version of a component application program received from a server over a network is provided. This program has a plurality of components including metadata descriptors expressed in a structured definition language. The mobile device comprises an infrastructure means for executing an executable version, an interface means connected to the infrastructure means and configured for communication with an executable version by a user of the device, connected to the infrastructure means, and connected to a network Communication means configured to communicate with the infrastructure means, and framework means configured to interface the executable version to the infrastructure means and to provide a client runtime environment for the executable version.

The present application further provides a computer program product for providing an executable version of a component application program on a mobile communication device. This program has a plurality of components including metadata descriptors expressed in a structured definition language. The computer program product includes a computer readable medium, a component framework module stored on the computer readable medium to interface an executable version to a device infrastructure including a processor and associated memory, and a metadata descriptor. An application container module connected to the component framework module for generating an executable version and hosting a client runtime environment for the obtained executable version.

The present application further provides a method for providing an executable version of a component application program on a mobile communication device. The method includes receiving a plurality of components representing a component application program including a metadata descriptor expressed in a structured definition language from a server via a network, and an application container of the device for the program. Loading a metadata descriptor into an application container for hosting the client runtime environment and generating an executable version from the metadata descriptor to be executed in the client runtime environment of the device.

The present application further provides a mobile communication device configured to provide an executable version of a component application program received from a server via a network. This program has a plurality of components including metadata descriptors expressed in a structured definition language. The mobile device is a device infrastructure for operating the mobile device, the device infrastructure including a processor and associated memory for executing the executable version, and an input device and output configured to communicate with the executable version A user interface having a device and connected to the device infrastructure, a communication device connected to the device infrastructure and configured to connect to a wireless transceiver to communicate with the network, and an executable version interface to the device infrastructure And a component framework configured to provide a client runtime environment for the executable version.

These and other features will become more apparent in the following detailed description with reference to the accompanying drawings.

Referring to FIG. 1, a communication system 10 includes a mobile communication device 100 for interacting with one or more web services provided by a web server 106 via a connected wireless network 102 and the Internet 104. Each mobile device 100 is
During the communication with the web service of the web server 106, the request / response message 105 is transmitted and received. The mobile device 100 may request / receive in the form of message header information and associated data content (eg, requesting and receiving product prices and availability from an online merchant).
By using the response message 105, it operates as a web client of the web service. The web server 106 may use the client application program 302 (see FIG. 2) of the mobile device 100 to satisfy the appropriate request / response message 105.
Communicate with the application server 110 via various protocols (eg, but not limited to HTTP and component APIs) for presenting relevant business logic (methods). The application program 302 of the mobile device 100 can use the business logic of the application server 110 in the same manner as calling a method for a certain object (or function). In addition,
The mobile device 100 is connected to one or more web servers 10 via the wireless network 102.
6 and related application servers 110. In addition, the mobile device 100 may bypass the web server 106 by being directly connected to the application server 110 as necessary.

Referring to FIG. 2, the mobile communication device 100 is a device such as, but not limited to, a mobile phone, a PDA, a two-way pager, or a dual mode communication device (see FIG. 9). Mobile device 100 includes a wireless transceiver 200 connected to device infrastructure 204 via connection 218. During operation of the mobile device 100, the wireless transceiver 200 is
By means of an appropriate radio channel (eg RF or IR link), the radio network 102
So that the mobile devices 100 can communicate with each other and the wireless network 1
02 can communicate with an external system (for example, the web server 106), and can adjust the request / response message 105 between the client application program 302 and the servers 106 and 110 (see FIG. 1). The wireless network 102 is a request / response message 105 between the device and an external system connected to the wireless network 102.
Supports the transmission of data within. The wireless network 102 is connected to the mobile communication device 100.
And voice communication between devices outside the wireless network 102 may be supported. The wireless network 102 may use a wireless data transmission protocol such as, but not limited to, DataTAC, GPRS, or CDMA.

Referring again to FIG. 2, the mobile device 100 is connected to the device infrastructure 204 via connection 222 to interact with a user (not shown).
Also have. User interface 202 includes one or more user input devices such as, but not limited to, a QWERTY keyboard, keypad, track wheel, stylus, and a user output device such as an LCD screen display. If the screen is touch sensitive, the display can also be used as a user input device controlled by the device infrastructure 204. The user of the mobile device 100 uses the user interface 202 to further use the system 10 (FIG. 1) used by the client application program 302 of the component framework 206 described below.
Request / response message message 105 via reference).

Referring back to FIG. 2, the operation of the mobile communication device 100 is enabled by the device infrastructure 204. The device infrastructure 204 includes a computer processor 208 and an associated memory module 210. The computer processor 208 manipulates the operation of the wireless transceiver 200, the user interface 202 and the component framework 206 of the mobile communication device 100 by executing relevant instructions. Related instructions are provided by an operating system and client application program 302 located in the memory module 210. The device infrastructure 204 is
A computer readable storage medium 212 connected to the processor 208 may be included for providing instructions to the processor and / or for loading / updating the client application program 302 to the memory module 210. The computer readable medium 212 may include hardware and / or software such as a magnetic disk, a magnetic tape, an optically readable medium (eg, CD-ROM or DVD-ROM), a memory card, and the like. In any case, computer readable medium 212 may take the form of a small disk, floppy diskette, cassette, hard disk drive, solid state memory card, or RAM disposed within memory module 210. Note that the computer-readable medium 212 in the above example can be used alone or in combination.

Referring again to FIG. 2, the component framework 206 of the mobile device 100 is connected to the device infrastructure 204 by connection 220. The component framework 206 provides a native runtime environment for the client application program 302, as well as the functionality and device infrastructure 2 of the mobile device 100 of the processor 208.
04 is an interface to the related operating system. The component framework 206 provides a runtime environment that preferably provides a controlled, safe and stable environment on the mobile device 100 in which the component application program 302 within the application container 300 is executed. The application container 300 is a client application program 30.
2 can be called a smart host container for 2 and can serve to parse message metadata (eg, for message 105 (see FIG. 1)) and update the representation of metadata in memory module 210. .

The component framework 206 is a client application program 3
02 also provides a framework service 304 (a standard set of general services such as, but not limited to, communication, screen, data persistence, security, etc.). The application program 302 has a communication 214 with the application container 300 that coordinates the communication 216 with the framework service 304. The framework service 304 of the component framework 206 coordinates communication with the device infrastructure 204 via the connection 220. Accordingly, access to the device infrastructure 204, user interface 202, and wireless transceiver 200 is handled by the component framework 20.
6 is provided to the client application program 302. In addition, the application container 300 can control and verify all access to the component framework 206 communications 214, 216 to and from the client application program 302, so that the client application program 302 can access the appropriate virus. It is possible to have resistance. A part of the operating system of the device infrastructure 204 (see FIG. 2) can represent the application container 300.

Referring again to FIG. 2, the client runtime environment of the component framework 206 is preferably capable of generating, hosting and executing a client application program 302 (in the form of a component application (see below)) from the metadata definition. Furthermore, as a specific function of the component framework 206,
Language support, memory allocation adjustment, networking, data management during I / O operations, graphics adjustments on the output device of the user interface 202 via the device infrastructure 204, core object oriented classes and files / supports for them
May include providing access to the library. Examples of runtime environments implemented by the component framework 206 are Microsoft's Common Language Runtime (CLR) and Sun Microsy
Java (registered trademark) Runtime Environment (Java (registered trademark) Runtime Enviro)
nment: JRE) and the like, but is not limited thereto. The runtime environment of the component framework 206 supports the basic functions of the client application program 302 on the mobile device 100. Examples of basic functions include the web server 106
Provision of a communication function for transmitting the message 105 to the web service (see FIG. 1), and a user for supplying data parts to the output message 105 (message for the service) of the web service of the web server 106 (see FIG. 1) Providing data input function on the input device according to the provision of data presentation or output function on the output device for web service response (received message) or uncorrelated notification of the web server 106 (see FIG. 1); Includes provision of a data storage service for maintaining local client data in the memory module 210 and provision of a scripting language execution environment for coordinating the operation of the application component 408 (see FIG. 3) of the client application program 302. This But, but it is not limited to these.

Accordingly, with reference to FIG. 2, the component framework 206 executes the client application program 302 (web service client application) in a runtime environment and uses the web server 1 via the request / response message 105.
Used to support access to 06 web service operations and associated application server 110 (see FIG. 1). The component application program 302 includes a software application executed by the component framework 206. Each time the component application program 302 is executed, the component framework 206 creates an application container 300 for each component (for example, 400, 402, 404, 406 (see FIG. 3)) of the application program 302. The application container 300 is a component of the application program 302 (for example, 400, 402, 404, 406).
Can be loaded to create native code that is executed by the processor 208 in the device infrastructure 204. Accordingly, the component framework 206 creates a real web client specified in each device infrastructure 204 of the communication device 100 to
, 402, 404, 406, etc., provide a host application container 300.

With reference to FIG. 3, a block diagram of the component application program 302 can include a data component 400, a presentation component 402 and / or a message component 404, which are in communication with the application container 300 via workflow 214 406. Adjusted by.

The data component 400 defines a data entity used by the component application program 302. Examples of data entities that the data component 400 can describe are orders, users, and financial transactions. Data component 400 defines what information is needed to describe the data entity and in what format the information is represented. For example, the data component 400 may include an order consisting of a unique identifier for an order formatted as a number, an item list formatted as a string,
An order creation time having a date-time format, an order status formatted as a string, and an ordering user formatted according to the definition of another data component 400 may be defined, but are not limited thereto.

Message component 404 defines the format of the message used by component application program 302 to communicate with an external system (eg, web service 106). For example, one of the message components 404 may describe a message for ordering including, but not limited to, a unique identifier for the order, the status of the order, notes associated with the order, and the like.

The presentation component 402 defines the appearance and behavior of the component application program 302 displayed by the user interface 202. The presentation component 402 can specify a GUI screen and a control unit (control), and an action to be executed when the user interacts with the component application 302 using the user interface 202. For example, the presentation component 402 may define screens, labels, edit boxes, buttons and menus, and actions that occur when a user enters a character in the edit box or presses a button.

Workflow component 40 of component application program 302
6 defines processing that occurs when an action (eg, an action specified by the above-described presentation component 402 or an action executed when the message 105 (see FIG. 1) from the system 10 arrives) is executed. To do. Screen workflow and message processing are defined by the workflow component 406. The workflow component 406 is written in a programming language or scripting language such as, but not limited to ECMAScript, and can be compiled into native code and executed by the application container 300 as described above. Examples of the workflow component 406 include those that assign values to data, those that operate screens, and those that send messages.

In the hosting model defined by the client component application program 302 described above, the presentation component 402 (see FIG. 3) can vary depending on the client platform and environment of the mobile device 100 (see FIG. 1). For example, a web service consumer may not require a visual presentation. Component 40 of component application program 302
0, 402, 404, 406 application definitions include platform neutral data component 400, message component 404, workflow component 406 descriptors and various pre-defined client runtimes (ie, specific component frameworks). 206) can be hosted in the web service registry as a bundle with a set of platform specific presentation component 402 descriptors. When a discovery or deployment request message 105 (see FIG. 1) is issued, the client type should be specified as part of this request message 105. When packaging component application programs 302 for multiple different client platforms of communication device 100, application definitions are linked with multiple different sets of presentation components 402 to avoid duplicating data, messages and workflow metadata. As a platform-neutral component definition bundle, it can be hosted on the application server 110 (for example). When a user issues a discovery or download request message 105, the type of client runtime of the communication device 100 is verified and an appropriate bundle for delivery to the device 100 via the wireless network 102 is configured by the web server 106. In some cases, the workflow component 406 may be managed and deployed in a platform specific representation, in which case it takes advantage of the known processing power of a particular platform, is more efficient and An enhanced component application program 302 can be provided.

Thus, referring to FIG. 3, the client application program 302 includes a data component 400 and message component 404 using a set of platform neutral component definitions (ie, XML (or any other suitable structured definition language)), and Definition for the presentation component 402). The workflow component 406 can be defined using ECMAScript (or any other suitable platform neutral scripting language). Component 400 of component application program 302,
When 402, 404, and 406 are supplied to the communication device 100, the client runtime environment of the component framework 206 (see FIG. 2) can generate a component template based on the meta definition (described further below). In a wide range of runtime environments, instead of building the component application program 302 in advance, XML and EC
Define application component metadata using a cross-platform standard such as MAScript. This delayed binding allows the generic application definition of the component application program 302 to be executed in a wide range of system environments represented by various different communication devices 100.

Expressing the data component 400, the message component 404, and the presentation component 402 using XML or its derivatives;
By representing the workflow component 406 using the Script language or a subset thereof, application developers can insulate web service clients from any particular platform or environment, in principle “everywhere once developed. An "executable" application can be realized. The following example uses a component defined by a structured definition language, such as but not limited to XML, and a platform neutral script / programming language, such as but not limited to ECMAScript, to provide a web service client application Program 302
Shows how can be expressed.

Example of data component 400 in XML

Example of XML message component 404

An example of an XML presentation component 402

Example of workflow component 406 by ECMAScript

Referring to FIG. 4, the component 400 of the application program 302 described above.
, 402, 404, and 406 are provided to a predetermined set of framework services 304 by the application container 300 of the component framework 206 once supplied to the communication device 100. The framework service 304 includes a communication service 306, a screen service 308, a persistence service 310, and an access service 31.
2, provisioning service 314, utility service 316 and the like.

With reference to FIGS. 1 and 4, the communication service 306 manages connectivity between the component application program 302 and the external system 10 (eg, the web service 106). For example, the communication service 3 on behalf of the component application 302
As a result, the message 105 is transmitted to the web service 106. The communication service 306 receives the data of the message 105 from the web service 106 and distributes the data to the component application 302. Data received by the communication service 306 may include a synchronous response to a request made by the component application program 302 and asynchronous data pushed to the mobile communication device 100 by the web service 106. The communication service 306 also manages connectivity when the mobile communication device 100 is disconnected from the wireless network 102. When the mobile communication device 100 is in an area not covered by the wireless network 102, or when the wireless transceiver is unavailable, the mobile communication device 100 is disconnected from the wireless network.
When the mobile communication device 100 is in disconnected mode, messages sent by the component application 302 are queued by the communication service 306,
When the mobile communication device 100 reconnects to the wireless network 102, the message can be transmitted.

1 and 4 again, the screen service 308 is connected to the user interface 2.
Component application program 3 displayed on the output device 02 (see FIG. 2)
Manage the visual representation of 02. Visual representations can include images, graphical user interface (GUI) controls and windows, and text. Screen service 308
Manages the screen stack that controls what the user sees on the output device of the device infrastructure 204.

Referring again to FIGS. 1 and 4, the persistence service 310 includes a component application program 302 that the memory module 210 of the device infrastructure 204 (see FIG. 2).
To be able to store data. The persistence service 310 transparently provides database operations to the component application program 302. In addition, the runtime environment of the component framework 206 facilitates actions performed on the metadata (ie, XML data) content of the message 105, thereby providing data persistence.

Referring again to FIGS. 1 and 4, the access service 312 provides the component application program 302 with access to other software applications residing on the mobile communication device 100. For example, the access service 312 accesses the component application program 302 to a software application for sending an e-mail, a software application for making a call, or contact information stored in the memory module 210 (see FIG. 2). Access to software applications (but not limited to) may be enabled. Access to other software applications on the communication device 100 can be provided in a secure manner. The access service 312 also allows other software applications residing on the mobile communication device 100 to access the component application program 302. The other software program may be a part of the operating system of the device infrastructure 204 (see FIG. 2).

Referring again to FIGS. 1 and 4, the provisioning service 314 manages the provisioning (supply) of software applications on the mobile communication device 100. Application provisioning requests and receives new and updated component application programs 302 and provides access to services accessible via the wireless network 102.
2, modifying the configuration of the component application program 302 and the service, and deleting the component application program 302 and the service. Provisioning service 314 performs the steps necessary to provision a software application on behalf of component application program 302.

Referring back to FIGS. 1 and 4, the component application program 302 uses the utility service 316 to accomplish various common tasks. For example,
The utility service 316 can execute data operations such as converting a character string into a different format on behalf of the component application program 302, for example.

Note that the framework service 304 of the communication apparatus 100 provides the component application program 302 with functionality including the services described above. As a result, the component application program 302 has access to the functionality of the communication device 100 without having to implement the functionality of the communication device 100. Framework service 30
The functionality provided by 4 is the core functionality that exists in the majority of typical wireless applications, so each hard-coded wireless application currently available is
Undesirably, it includes code for implementing some or all of the services described above. For example, if there are 10 hard-coded wireless applications on a typical mobile device, the current known technology is the same for implementing services such as GUI display, access to wireless networks, etc. There will be 10 copies of the code.

On the other hand, the component framework 206 of the mobile communication device 100 (see FIG. 2) has one copy of the code that implements these services existing in the framework service 304, regardless of the number of component application programs 302 that exist. It is preferable because it only has. Since the code duplication of the framework service 304 is minimized, the size of the component application program 302 can be reduced compared to currently available hard-coded applications. In this manner, the memory consumed by the component application program 302 can be reduced, and the time required for transmission via the wireless network 102 can be reduced. This allows the component application program 302 to be optimized for use on the mobile communication device 100 that is typically subject to memory and processing capacity constraints. Furthermore, software application developers do not have to spend time and effort to implement any functionality provided by the framework services 304 of the component framework 206.

The client runtime of component framework 206 is component 4
The metadata included in the definitions of 00, 402, 404, and 406 is loaded, and an executable version of the application program 302 that can be executed on the communication apparatus 100 via the application container 300 is constructed. For example, 2 for the client runtime
There are three behavior models: template-based native execution and meta-database execution. In the template-based native execution model, the runtime hosts data, message and screen templates that are pre-built on the communication device 100 using native code. When the application program 302 definition is loaded,
The client environment provided by the component framework 206 embeds parameters defined by metadata in a template and constructs an executable client application program 302 in a native format. The workflow script (eg, ECMAScript) of the workflow component 406 may be converted to native code, or an interpreter for a native code redirector (
For example, it may be performed using ECMAScript) for native code.
In this case, the redirector translates calls to the script language into operations on the native component. In the execution of the meta-database, the runtime environment of the component framework 206 keeps the component 400, 402, 404, 406 definitions in a representation format such as XML and either parses them at runtime, or (for example) the XML node's Use native representation. During execution, the native runtime engine
Components 400, 402, 404, 40, not native component entities
6 Manipulate definitions. Note that the template-based approach can be more performance efficient than meta-database execution, but can require a more complex execution environment and more memory resources.

Before each component application 302 is loaded into the mobile communication device 100, the workflow component 406 is converted into native code or intermediate format (eg, Ja
va (registered trademark) bytecode). This intermediate format is then converted into native code on the mobile communication device 100. Compiling the workflow component 406 before the workflow component 406 is loaded into the mobile communication device 100 means that the code comprising the workflow component 406 need only be translated on the mobile communication device 100 at one level. Helps to ensure. Alternatively, the workflow component 406 may be loaded into the mobile communication device 100 as code written in a translated language, which is processed by an interpreter on the mobile communication device 100 prior to conversion to native code. Is done. Alternatively, the workflow component 406 may be composed of code written in any compiled or translated language.

To create a component application 302 that has access to the framework services 304 described above and that takes advantage of operating in a mobile environment to provide utilities to the user, an application developer can create a component as described above. Can be created. XML (eXtensible Markup Lang) for data component 400, presentation component 402 and message component 404
uage), and ECMAScript for workflow component 406,
Standard techniques can be used. These components are executed by the component framework 206 within the application container 300. The component framework 206 executes the workflow component 406 and translates the presentation component 402, the data component 400, and the message component 404 using the framework service 304 described above. This application development model is useful for minimizing the expertise required of application programmers and minimizing the time required to create a software application for mobile communication device 100. Furthermore, once the components are created, they can be reused in multiple component applications 302, making development even easier.

Referring to FIGS. 1 and 5, an operation 800 of the component application program 302 model is shown. The user of the mobile device 100 contacts the web service and then requests the selected application program 302 from the web service by sending a request message 105 over the network 102 at 802. The appropriate web server 106 sends a request message 105 to the appropriate application server 110 and then sends a set of component definitions in the response message 105 to the mobile device 100 over the network 102 at 804. The response message 105 is X
A component application program 302 in the form of a series of data components 400 including a metadata descriptor expressed in a structured definition language such as but not limited to ML, a message component 404 and a presentation component 402 (see FIG. 3) . The response message 105 also includes a workflow component 406 that includes a descriptor expressed in a programming / script language, such as but not limited to ECMAScript. At 806, the mobile device 100 provides a runtime environment to the application program 302 via the component framework 206 (see FIG. 2), thereby responding to the interacted web service at 808 using the execution model. A web client is created on the mobile device 100 and provides definitions for the components 400, 402, 404, 406 of the application program 302. The supplied application program 302 coordinates the access of the mobile device 100 by the message 105 via the network 102 using the framework service 304 (see FIG. 2). A user of the mobile device 100 interacts with the supplied application program 302 via the user interface 202.

The component application model described above further facilitates the development of wireless applications because the component application 302 can be visually created using an integrated development environment (IDE) not shown. IDE is a software application that allows application developers to quickly create the above-described components using a GUI that presents the developer with a visual representation of the components. The presentation component 402, the data component 400, and the message component 404 are:
Shown in tree view. Developers can drag and drop components
Add them to the component application 302. When an icon representing the presentation component 402 is clicked, the presentation component 40
The editor for designing 2 is opened. Links between presentation components 402 are visually represented, and clicking on these links edits the workflow component 406 that defines the screen workflow. Presentation component 40
2 is designed with an interface that includes a representation of the mobile communication device 100 in which the component application 302 is executed. Menu items are represented, and clicking on them defines a workflow component 406 that is executed upon selection of those menu items. Message component 404 can be visually mapped to data component 400. The message component 404 can also be visually associated with the web service 106 message.
Can be created based on the web service 106 message defined by WSDL or the like.

6 and 7, a further example of the system 10 is the message map service 1
A message communication system using 08 is included. Also shown are a web service on the web server 106, a communication service 306, a component framework 206, and the mobile communication device 100. Other elements are not shown for simplicity.

The wireless network 102 is connected to the Internet 104 and the mobile communication device 100.
However, the data of the message 107 to / from the system connected to the Internet 104 can be transferred. The connection between the wireless network 102 and the Internet 104 is a device connected to the wireless network 102 (for example, the mobile communication device 100).
Internet gateway (not shown) that allows data to flow from a system connected to the Internet 104 (eg, a web service).

The web service on the web server 106 provides information used by the software application 302 (see FIG. 2) on the mobile communication device 100. Alternatively, or in addition, the web service may receive and use information provided by a software application on the mobile communication device 100 or the mobile communication device 10
The task may be performed on behalf of a software application on 0. The web service implements an interface with the software application 302 on the mobile communication device 100 that can be expressed using Web Services Description Language (WSDL), and uses an appropriate communication protocol such as SOAP (Simple Object Access Protocol). Communicate with the client system. Alternatively, the web service may use other known protocols.

A web service is a wireless network that allows software applications on the mobile communication device 100 to provide utilities to users of the mobile communication device 100.
02 and an example of a system that interacts via the Internet 104. A message 107 transmitted between the mobile communication device 100 and the web service passes through the message map service 108. The message map service 108 creates the message 105 by converting the message 107 from a format usable by the software application on the mobile communication device 100 to a format required by the web service. Once the 107 message from one of the mobile communication devices 100 has been converted to the appropriate format, the message map service 108 sends the message 105 to the web service. Similarly, once the message or response 105 from the web service has been converted to the required format, the message map service 108 sends the message 107 to one of the mobile communication devices 100. For the message map service 108, see FIG.
Will be described in more detail.

Referring to FIG. 7, a component application 302 (see FIG. 2) uses a communication service 306 to communicate a wireless message 502 over the wireless network 102 and the Internet 104 to interact with a web service to exchange information. Send. For example, the wireless message 502 is formatted according to one of the message components 404 (see FIG. 3) defined within the component application 302. For example, a SOAP message 504 is used to access the web service. To resolve the message type differences, the message map service 108 receives the wireless message 502, constructs the corresponding SOAP message 504, and uses the appropriate SOAP protocol to send the web service on the web server 106 to the Internet 104. A SOAP message 504 is transmitted via Similarly, the response message 504 generated by the web service is sent using SOAP to the message map service 108 over the Internet 104, where the response message 504 is formatted according to one of the message components 404. To the wireless communication device 100 and transmitted to the mobile communication device 100 where the component application 302
The wireless message 502 is received by the communication service 306 on behalf of the user.

Referring again to FIG. 7, the message map service 108 includes an application message map 500 for each component application 302 (see FIG. 2). The application message map 500 is a component application 302
Defines how each wireless message 502 received from a web service message is converted into a corresponding web service message, such as a SOAP message 504, and each web service message received from the web service and then transmitted to the component application 302 (For example, a SOAP message 504) defines how the corresponding wireless message 502 is converted. As described above, each wireless message 502 can be formatted according to one of the message components 404 of the component application 302, while each web service message (eg, SOAP message 504).
) Can be formatted according to the web service definition. Message map 500
Specifies which information defined in the definition corresponds to information defined in the message component 404 of the application program 302. These definitions can be encoded in an appropriate format such as WSDL. This mapping is then used to convert messages 502, 504 between these two formats.

Note that not all the information in the SOAP message 504 needs to be mapped to the information in the corresponding wireless message 502. For example, in the conversion from the wireless message 502 to the SOAP message 504, the application message map 500 may specify a default value provided in the SOAP message 504 when there is no corresponding information in the wireless message 502. Similarly, upon conversion from the SOAP message 504 to the wireless message 502, the SOAP message 504 that does not have a corresponding definition in the wireless message 502.
The information inside is discarded. Therefore, information included in a response from a web service that is not used by the component application 302 may not be transmitted via the wireless network 102. Similarly, information required in a SOAP message 504 sent to the same web service each time the message 504 is sent by the component application 302 is a default value so that redundant information is not sent over the wireless network 102. Is adopted. As a result, the amount of data transmitted via the wireless network 102 can be reduced, congestion of the wireless network 102 is reduced, and the mobile communication device 10
The amount of resources required to process message 502 on 0 can be reduced.

Accordingly, the message map service 108 allows the component application 302 to harmonize with the web service without implementing a web message communication service protocol such as SOAP on the mobile communication device 100. The component application 302 does not need to format the message 502 for the web service,
Also, there is no need to perform any other additional processing to harmonize with the existing web service 106.

Instead of using the message map service 108, the messages 502, 504 may be mapped by the communication service 306 on the mobile communication device 100. In this example, the mobile communication device 100 is installed with software having a web message communication service protocol such as kSOAP having a SOAP protocol definition so that the communication service 306 can directly communicate with the web service 106. In effect, rather than using an intermediate third party to implement the message map service 108, the message 502
Is translated by the mobile device 100.

FIG. 8 is a flowchart illustrating a method of deploying the wireless component application 600 and communicating with the application. As described above, the wireless component application 600 is the component application 302 and includes a data component 400, a presentation component 402, a message component 404, and a workflow component 406 (see FIG. 3).

With reference to FIGS. 6 and 8, the method begins at step 602 where a wireless component application 600 is deployed to the mobile communication device 100. The wireless component application 600 is transmitted to the mobile communication device 100 by radio waves via the wireless network 102. Alternatively, the wireless component application 600 may be loaded into the mobile communication device 100 via a serial connection, a USB link, or a short-range communication system (not shown) such as a Bluetooth ™ or 802.11 network.

Referring again to FIG. 6 and FIG. 8, this method includes the application message map 10.
Proceed to step 604 of deploying 8. As described above, the application message map 108 is used to convert a message from the format used by the wireless component application 600 to the format required by the web service with which the wireless component application 600 is communicating. The application message map 500 (see FIG. 7) is deployed on a dedicated message map service 108 accessible via the Internet 104. Alternatively, the application message map 108 may be deployed directly on the mobile communication device 100. Step 606 executes the wireless component application 600 on the mobile communication device 100. As described above, the application framework 206 (see FIG. 2) on the mobile communication device 100 creates the application container 300 and executes the wireless component application 600 in the container 300, thereby providing the framework service 304. Provides access to the wireless component application 600 of

6 and 8, once the wireless component application 600 is executed on the mobile communication device 100, the method proceeds to step 608, where the wireless component application 600 sends a wireless message 502 to an external web service. It is determined whether this is desired. The wireless component application 600 may request web data from the web service, transfer data to the web service, or request the web service to perform an action on behalf of the wireless component application 600. Send a message 502 to the service. If it is determined that there are no more messages 502 transmitted by the wireless component application 600, the method ends at step 610. Message 5 to send
If there is 02, the method proceeds to step 612 composing the message 502 to be sent. The message 502 is sent to the message component 404 (
(See FIG. 3). Next, the communication service transmits a message 502 via the wireless network 102.

Referring again to FIGS. 6 and 8, in step 614, the message 502 is sent over the wireless network 102 and the Internet 104 to the message map service 108.
Received. Next, the message map service 108 uses the application message map 500 deployed in step 604 to convert the message 502 to the SOAP format. The application message map 500 identifies which part of the SOAP format required by the web service corresponds to each part of the message 502 from the wireless component application 600. In step 616, the converted message 504 is sent to the web service over the Internet 104 using the SOAP protocol. Alternatively, in step 614, the message 502 is converted to a SOAP format using the application message map 500 located on the mobile communication device 100, and then in step 616, the wireless network 102 and the Internet 104 are transmitted using the kSOAP protocol. May be sent directly to the web service.

Referring again to FIGS. 6 and 8, once the message 504 is received by the web service, the method proceeds to step 618, where the web service constructs a response to the message 504. The SOAP format response is sent over the Internet 104 to the message map service 108, where the response is converted in step 620 to the radio format 502 required by the radio component application 600. The required radio format is defined in one of the message components 404 (see FIG. 3) included in the radio component application 600. The message map service 108 then sends a response to the wireless component application 600 over the Internet 104 and the wireless network 102 at step 622. Alternatively, the web service may send a SOAP response message 504 directly to the mobile communication device 100, where the SOAP response message 504 is sent in step 620.
The application message map 50 existing on the mobile communication device 100.
0 is used to convert to the required format. Next, the converted message 502
Is provided to the wireless component application 600 at step 622. The method then proceeds to step 608 where it is determined whether there are more messages 502 to send. If there is no message 502, the method ends at step 610. Note that the steps involved in deploying and communicating with the wireless component application 600 may include fewer or more steps than shown in FIG.

FIG. 9 is a block diagram of a dual mode mobile communication device 710, which is a further example of the device 100 of FIGS. The dual mode mobile communication device 710 includes a transceiver 711, a microprocessor 738, a display 722, and a flash memory 7.
24, RAM memory 726, auxiliary input / output (I / O) device 728, serial port 730,
It includes a keyboard 732, a speaker 734, a microphone 736, a short-range wireless communication subsystem 740, and may further include other device subsystems 742. The transceiver 711 preferably includes transmit / receive antennas 716, 718, a receiver 712, a transmitter 714, one or more local oscillators 713, and a digital signal processor 720. The dual mode mobile communication device 710 includes a microprocessor 7 in the flash memory 724.
Multiple software modules 7 that can be executed by Windows 38 (and / or DSP 720)
24A to 724N, preferably this software module 724A to 724N
Includes a voice communication module 724A, a data communication module 724B, and other operational modules 724N for performing other functions.

The dual mode mobile communication device 710 is preferably a two-way communication device having voice and data communication functions. Thus, for example, the dual-mode mobile communication device 710 may communicate via a voice network such as any analog or digital cellular network, or may communicate via a data network. In FIG. 9, the voice and data network is represented by a communication tower 719. These voice and data networks may be separate communication networks using separate infrastructure (eg, base stations, network controllers, etc.) or may be integrated into a single wireless network.

The communication subsystem 711 is used to communicate with the voice and data network 719 and includes a receiver 712, a transmitter 714, one or more local oscillators 713, and a DSP 72.
0 may be included. The DSP 720 is used to transmit / receive signals to / from the transmitter 714 and the receiver 712, and receives control information from the transmitter 714 to receive the receiver 71.
2 is also used to provide control information. A single local oscillator 713 may be used in conjunction with the transmitter 714 and receiver 712 when voice and data communications are performed at a single frequency or a set of closely spaced frequencies. Alternatively, when different frequencies are used for voice communication and data communication, a plurality of local oscillators 713 can be used to generate a plurality of frequencies corresponding to the voice and data network 719. Although two antennas 716, 718 are shown in FIG. 9, the dual mode mobile communication device 710 may be used with a single antenna structure. Information including voice and data information
Communicated to / from communication module 711 via the link between 720 and microprocessor 738. The detailed design (frequency band, component selection, power level, etc.) of the communication subsystem 711 depends on the communication network 719 on which the dual mode mobile communication device 710 is intended to operate. For example, a dual-mode mobile communication device 710 intended to operate in the North American market is designed to operate on Mobitex ™ and DataTAC ™ mobile data communication networks and includes AMPS, TDMA, CDMA, PCS, etc. A communication subsystem 711 designed to operate on any of a variety of voice communication networks may be included. On the other hand, a device 710 intended for use in Europe may be configured to operate in a general packet radio service (GPRS) data communication network and a GSM voice communication network. Other types of data and voice networks (whether separate or integrated) may be used with the dual mode mobile communication device 710.

Depending on the type of one or more networks 719, the access requirements of the dual mode mobile communication device 710 may also vary. For example, in the Mobitex and DataTAC data networks, mobile devices are registered with the network using a unique identification number associated with each device. However, in a GPRS data network, network access is associated with a mobile device subscriber or user. GPRS devices typically require a subscriber identity module (SIM). This is required to operate a dual mode mobile communication device over a GPRS network. Although local or non-network communication functions (if any) can operate without a SIM, the dual mode mobile communication device is capable of other than any legally required operation, such as an emergency call to 911.
None of the functions can be performed, including communication via the data network 719.

After completing any required network registration or activation procedure, the dual mode mobile communication device 710 may send and receive communication signals, including voice and data signals, via one or more networks 719. The signal received by antenna 716 from communication network 719 is sent to receiver 712, which provides signal amplification, frequency down conversion, filtering, channel selection, etc., and also provides analog-to-digital conversion. Good. By converting the received signal from analog to digital, more complicated communication functions such as digital demodulation and decoding performed using the DSP 720 are possible. Similarly, the signal transmitted to the network 719 is subjected to processing by the DSP 720 (including modulation and coding, for example) before digital-analog conversion, frequency up-conversion, filtering,
Supplied to transmitter 714 for amplification and transmission to one or more communication networks 719 via antenna 718. Although a single transceiver 711 for voice and data communication is shown in FIG. 9, the dual mode mobile communication device 710 includes two separate transceivers (a first transceiver and a data signal for sending and receiving voice signals). Second for sending and receiving
Of transceivers).

The DSP 720 provides control of the receiver and transmitter in addition to processing the communication signal. For example, the gain level applied to the communication signals of receiver 712 and transmitter 714 is DSP 720.
May be adaptively controlled by an automatic gain control algorithm implemented in. Other transceiver control algorithms may be implemented in the DSP 720 to provide more complex control of the transceiver 711.

Microprocessor 738 preferably manages and controls the overall operation of dual mode mobile communication device 710. Here, many types of microprocessors or microcontrollers may be used, or a single DSP 720 may be used to perform the functions of the microprocessor 738. Low level communication functions, including at least data and voice communications, are performed by the DSP 720 of the transceiver 711. Other high level communication applications (eg, voice communication application 724A and data communication application 724B) may be stored in flash memory 724 for execution by microprocessor 738. For example, the voice communication module 724A may provide a high level user interface operable to send and receive voice calls between the dual mode mobile communication device 710 and a plurality of other voice devices over the network 719. . Similarly, the data communication module 724B transmits and receives data (eg, email messages, files, organizer information, short text messages, etc.) between the dual mode mobile communication device 710 and a plurality of other data devices over the network 719. A high level user interface operable to do so may be provided. In the dual mode mobile communication device 710, the component framework 206 described above may be implemented as a software module or application, or may be incorporated into one of the software modules 724A-724N.

The microprocessor 738 includes, for example, a display 722, a flash memory 724,
A random access memory (RAM) 726, an auxiliary input / output (I / O) subsystem 728,
With other dual-mode mobile communication device subsystems such as serial port 730, keyboard 732, speaker 734, microphone 736, short-range communication subsystem 740 and any other dual-mode mobile communication device subsystem generally indicated at 742 make a conversation.

Some of the subsystems shown in FIG. 9 perform communication-related functions, and other subsystems may provide built-in functions or on-device functions. Note that some subsystems such as the keyboard 732 and the display 722 have communication-related functions such as input of text messages transmitted via the data communication network, computers, task lists or other PDs.
It may be used for both functions built into the apparatus such as A-type functions.

The operating system software used by the microprocessor 738 is preferably stored on a persistent storage device such as flash memory 724. In addition to the operating system that controls all of the low level functions of the dual mode mobile communication device 710, the flash memory 724 includes a plurality of high level software application programs or modules (eg, a voice communication module 724A, a data communication module 724B, an organizer module). (Not shown), or any other type of software module 724N). The flash memory 724 may include a file system for storing data. These modules are executed by the microprocessor 738 and provide a high level interface between the user of the dual mode mobile communication device and the mobile device. This interface typically includes graphics components provided via display 722 and auxiliary I / O 728.
, A keyboard 732, a speaker 734, and an input / output component provided via a microphone 736. To speed up the operation, the operating system, certain dual mode mobile communications device software applications or modules, or portions thereof, may be temporarily loaded into volatile storage such as RAM 726. Further, received communication signals may also be temporarily stored in RAM 726 before they are permanently written to the file system in persistent storage 724.

An exemplary application module 724N that may be loaded into the dual-mode mobile communication device 710 is a personal information manager (PIM) application that provides PDA functionality (eg, calendar events, appointments and task items, etc.). This module 724N may interact with the voice communication module 724A to manage phone calls, voicemails, etc., and may interact with the data communication module to manage email communications and other data transmissions. Alternatively, all of the functionality of the voice communication module 724A and the data communication module 724B may be integrated into the PIM module.

The flash memory 724 preferably provides a file system to facilitate storage of PIM data items on the dual mode mobile communication device 710. The PIM application preferably includes the ability to send and receive data items over the wireless network 719, either alone or in cooperation with the voice communication module 724A and the data communication module 724B. The PIM data items are preferably seamlessly integrated, synchronized and updated via the wireless network 719, and a corresponding set of data items is stored or associated with the host computer system so that a specific user Create a mirror system for the data item associated with.

The dual mode mobile communication device 710 is manually synchronized with the host system by placing the dual mode mobile communication device 710 in an interface cradle that connects the serial port 730 of the dual mode mobile communication device 710 to the serial port of the host system. Also good. The serial port 730 is used by the user for selection setting via an external device or software application, and other application modules 7.
It may be used to allow download to install 24N. This wired download path may be used to load the encryption key into the dual mode mobile communication device 710. This is a safer method than exchanging encrypted information over the wireless network 719.

Additional application modules 724N may be connected via the network 719, via the auxiliary input / output subsystem 728, via the serial port 730, via the short-range communication subsystem 740, or any other suitable subsystem 742. May be loaded onto the dual mode mobile communication device 710 and installed in the flash memory 724 or RAM 726 by the user. Such application installation flexibility increases the functionality of the dual-mode mobile communication device 710 and may provide enhanced on-device functionality, communication-related functionality, or both. For example, a secret communication application may enable electronic commerce functions and other similar financial transactions performed using the dual mode mobile communication device 710.

When the dual mode device 710 is operating in the data communication mode, received signals (eg, text messages and web page downloads) are processed by the transceiver 711 and provided to the microprocessor 738. Microprocessor 738 preferably further processes the received signal for output to display 722 or output to auxiliary input / output device 728. The user of the dual mode mobile communication device 710 can use the keyboard 73
2 may be used to configure data items such as e-mail messages. Keyboard 732
Is preferably a full alphanumeric keyboard laid out in QWERTY style, but other styles of full alphanumeric keyboard, such as what is known as DVORAK style, may be used. User input to the dual mode mobile communication device 710 is further enhanced by a plurality of auxiliary input / output devices 728 that may include thumbwheel input devices, touchpads, various switches, rocker input switches, and the like. The configured data item entered by the user may then be transmitted via the communication network 719 by the transceiver 711.

When the dual mode mobile communication device 710 is operating in the voice communication mode, the overall operation of the dual mode mobile communication device 710 is substantially the same as in the data mode, except that the received signal is output to the speaker 734 and transmitted. The audio signal to be generated is preferably generated by a microphone 736. Further, another voice input / output subsystem (for example, a voice message recording subsystem) may be mounted on the dual mode mobile communication device 710. Audio signal output is preferably achieved primarily through speaker 734, but display 722 is used to provide an indication of caller identification information, duration of voice call or other voice call related information. May be. For example, the microprocessor 738 may work with the voice communication module and operating system software to detect caller identification information for incoming voice calls and display it on the display 722.

The dual mode mobile communication device 710 also includes a short range communication subsystem 740. For example, the short-range communication subsystem 740 may include an infrared device and associated circuitry and components to provide communication with systems and devices having similar functions, or a Bluetooth ™ module, A short-range wireless communication module such as an 802.11 module may be included. "Bluetooth" (trademark) and 802
. Those skilled in the art will appreciate that 11 refers to a set of specifications for wireless personal area networks and wireless LANs, each available from the Institute of Electrical and Electronics Engineers (IEEE).

The above description is directed to one or more exemplary systems and methods. Many variations will be apparent to those skilled in the art and such variations are within the scope of this application. For example, while the above example describes a web service that implements the SOAP protocol, the web service may be any source of information that can access the mobile communication device, and may implement a different communication protocol.

The disclosure herein relates to one or more exemplary systems and methods, but to those skilled in the art without departing from the spirit and scope of the invention as outlined in the claims appended hereto. Various modifications are obvious.

1 is a block diagram of a communication system. FIG. 2 is a block diagram of the mobile communication device of FIG. 1. It is a block diagram of the component application program of FIG. FIG. 4 is a block diagram of the component framework of FIG. 3. 3 is a flowchart of an exemplary operation of the mobile device of FIG. 2 is a further example of the communication system of FIG. It is a block diagram of the message communication system using the message map service of FIG. 7 is a flowchart illustrating a method for operating a wireless component application of the communication device of FIG. 6. FIG. 3 is a block diagram of a further example of the mobile communication device of FIG.

Claims (1)

  A method for providing an executable version of a wireless component application program (302) on a mobile communication device (100), the method described herein.

Images