KR20080022934A - Application framework system for distribution and migration of application - Google Patents

Abstract

An application framework system for distributing and migrating an application in a ubiquitous environment is provided to support a platform independent application to users, share computing resources by using a distribution MVC(Model, View and Controller) model, and guarantee migration to the users in the unique environment. An MVC/UAML(Ubiquitous Application Markup Language) manager(210) manages a model, a view, and a controller, and parses/manages UMAL defining the model, the view, and the controller by including a model manager(212), a view manager(214) and a controller manager(216). A service manager(220) operates and manages an automatic update service and migration service of the model, the view, and the controller. A runtime manager(230) manages a life cycle related to loading, executing, and terminating an application, and stores/manages information of the model, the view, and the controller. An event manager transfers a message and data among the model, the view, and the controller. A network manager(250) transfers the message generated from the application to other frameworks and devices.

Description

Application framework system for distribution and mobility of applications in ubiquitous environment

1 is a block diagram showing the configuration of an application framework system for the distribution and mobility of applications in the ubiquitous environment according to the present invention.

Figure 2 is a block diagram showing the configuration of an application framework for the distribution and mobility of applications in a ubiquitous environment.

3 is a sequence diagram for passing data between a view of an application and a controller.

4 is a sequence diagram in which views are migrated.

The present invention relates to ubiquitous technology, and more particularly, to an application framework system for the distribution and mobility of applications in a ubiquitous environment.

Traditional computing environments are static environments in which a user directly uses a device in front of a particular computing device. The ubiquitous environment is a dynamic and intelligent environment in which all computing devices in adjacent spaces cooperate with each other to help the user's convenience and work even if the user does not recognize the computing device.

The ubiquitous space, which is created by combining physical and electronic space, enables real-time collaboration of various devices and applications and services on various platforms. The services existing under such environment are not only mixed in various ways, but the information provision method must be determined and changed at runtime according to the target of the service.

This ubiquitous environment leads to the diversification of the environment in which an application can be executed, which requires a change in the method of developing an application that is statically developed depending on a specific existing environment. However, it is difficult for application developers to predict in which environment the application they write will run at the time of developing the application, and even if it is predicted, it is difficult to develop a different version of the application for each environment.

Inferencing such as service selection and situation for the user is also an important factor in the ubiquitous space, but the point of contact with the user, that is, the interaction with the user who can directly see, hear and feel is also important. If the service cannot be provided due to the difficulty of application development due to the complexity of the system and the diversity of the environment, it will be a big obstacle in establishing a ubiquitous environment. Recently, researches on application frameworks for ubiquitous computing environments have been actively conducted, and PIMA, Gaia, and Aura are representative.

The Platform-Independent Model for Application (PIMA) project is based on IBM's T.J. Research from the Watson Research Center suggests that fundamental changes to current mobile computing devices, applications, and bite environments are needed, with new vision that devices should be considered portals, applications as tasks, and physical environments as computing environments. However, PIMA lacks the integration of applications running in various environments and the definition of functionality as a framework.

Gaia is a project at Illinois University to develop an infrastructure for ubiquitous applications, based on three main elements: a component-based middleware operating system, an application model for building ubiquitous, and a scripting language for combining component-based applications. . The application model defined by Gaia applies the MVC model to the active space environment, but has problems in terms of collaboration between active spaces and integration of spaces outside of this space.

Aura is a project at Carnegie Mellon University, a framework for user mobility in a ubiquitous environment that acts as a proxy for mobile users. However, Aura lacks support for how to develop applications efficiently in a ubiquitous environment.

The technical task of the present invention is to provide a platform-independent application to the user in the ubiquitous environment, to share the computing resources using a distributed MVC model and to ensure the mobility to the user application framework for the distribution and mobility of the application in the ubiquitous environment To provide a system.

Application framework for the distribution and mobility of the application in the ubiquitous environment according to the present invention for achieving the above technical problem, the distribution and mobility of the application consisting of a model, view and controller (MVC) in the ubiquitous environment An application framework for managing the model, views and controllers, and MVC for parsing and managing the Ubiquitous Application Mark-up Language (UAML) defining the models, views and controllers, and UAML management unit; A service manager for driving and managing an automatic update service and a migration service of the model, view and controller; A runtime manager that manages a life cycle related to loading execution and termination of the application and maintains and manages information of the model, view, and controller; An event manager for transmitting messages and data between the models, views, and controllers; And a network manager for delivering a message generated in the application to another framework or device.

The MVC and UAML management unit, the model management unit for managing the model, and delivers events related to the model; A view manager for managing the view and delivering an event related to the view; A controller manager for managing the controller and delivering an event related to the controller; And a UAML management unit for parsing and managing the UAML.

The UAML defines the purpose and meta information of the application, the definition of the MVC component, execution environment requirements of the MVC component, the format definition of an event for data exchange between MVC components, and a data storage location of the application. It includes at least one of the definition and the migration policy definition.

The service manager may include a migration service execution unit that executes migration of the application; An automatic update service execution unit executing automatic update of the application framework; And a runtime service binder that binds to the web service when the application is executed.

The runtime management unit may include runtime application information for maintaining and managing information related to an application currently running; And runtime routing information that maintains location information where the MVC component of the running application is present.

The event manager may include a message generator configured to generate an XML-based message for an event for message transmission between the MVC components; And a message transfer unit configured to transfer the message generated by the message generator to the MVC components.

Preferably, the view uses Macromedia Flash.

Application framework system for the distribution and mobility of the application in the ubiquitous environment according to the present invention for achieving the above technical problem, the distribution of the application consisting of the model, view and controller (MVC; Model and View and Controller) in the ubiquitous environment An application framework system for mobility, comprising: a plurality of devices including an application and an application framework; An application server for storing an application to be distributed to the device; And a message broker for transferring messages and data between the plurality of devices and the application server and between the plurality of devices, wherein the application framework manages the model, view and controller, respectively, An MVC and UAML manager that parses and manages a Ubiquitous Application Mark-up Language (UAML) defining views and controllers; A service manager for driving and managing an automatic update service and a migration service of the model, view and controller; A runtime manager that manages a life cycle related to loading execution and termination of the application and maintains and manages information of the model, view, and controller; An event manager for transmitting messages and data between the models, views, and controllers; And a network manager for delivering a message generated in the application to another framework or device.

In order to fully understand the present invention, the operational advantages of the present invention, and the objects achieved by the practice of the present invention, reference should be made to the accompanying drawings which illustrate preferred embodiments of the present invention and the contents described in the accompanying drawings.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. For each figure, like reference numerals denote like elements.

1 is a block diagram illustrating a configuration of an application framework system for distribution and mobility of an application in a ubiquitous environment according to the present invention. The application framework system includes a plurality of devices 100-1, 100-2, .. , 100-n), application server 150 and message broker 180.

The device-1 100-1 includes an application 110 and an application framework 120. The application 110 includes a model 112, which is a data object, and a view showing model data on a screen. 114 and a Controller 116 that processes operations or changes data.

In an embodiment of the present invention, to support a platform independent view, Macromedia Flash, which is currently used in various environments as well as the web, is adopted. Here, the platform refers to an environment in which an application can be executed, and is a concept that manages an operating system (OS), middleware, and devices.

With Flash, there is no need to consider the display size of the device. Developers can focus on coding controllers and models, and UI (User Interface) designers can focus on the user interface, allowing for clear separation of tasks.

The application framework 120 develops an application once so that it can be operated not only on a specific platform but also on various platforms, and can be executed even when a running application is used between devices existing in a space. Refers to a middleware system that supports the distribution and execution of each component.

The application framework 120 resides on the operating system of various devices, including mobile devices. Applications developed in an application framework environment can run on any device on which the application framework exists.

The distributed MVC (Model, View and Controller) model of the application framework 120 according to the present invention ensures independence between the model 112, the view 114 and the controller 116 so that each component is Provide an environment that can be developed independently. Therefore, professional UI designers develop views, and programmers develop controllers and models to increase application specialization, which can reduce development time.

The distributed MVC model may be separately disposed in consideration of computing environments of various devices disposed in the ubiquitous environment. For example, when the computing resource of the device on which the application is executed is insufficient, it may be performed by moving a controller that performs a complex operation to a computing resource-rich device around. In addition, applications can collaborate across frameworks so that when a user moves from one space to another, they can migrate to the application frameworks that exist on the most appropriate device.

For example, if a user uses device-1 100-1 and then another device-2 100-2, the application framework 120 may change the state of the application 100 to another device-2 ( 100-2) using the migration service to the application framework (not shown). This allows the application to perform tasks continuously as the user moves.

The application server 150 provides a program manager 160 for providing information about a program and transmitting UAML and program files according to a user's request of the devices 100-1, 100-2, ..., 100-n; It includes an application storage unit 170 for storing the application.

The device 100-1 with the application framework 120 may easily download an application from the application server 150 through the message broker 180, and a new version of the application may be developed to apply the application server 150. ), The application framework 120 automatically checks the version and downloads the latest application when executing the application, greatly simplifying the update procedure.

Application framework 120 describes Ubiquitous Application, which describes meta-level applications to support the retrieval and loading of applications required by the user, the distributed execution of the components of the application, the migration policy of each component, automatic updates, and the like. Mark-up Language: Ubiquitous application markup language.

The UAML defines the purpose and meta-information of the application, the definition of the MVC component, the execution environment requirements of the MVC component (eg device performance), the format definition of events for the exchange of data between the MVC components, and the data of the application. Describe the storage definition and migration policy definition.

2 is a block diagram illustrating the configuration of an application framework for application distribution and mobility. The application framework 120 includes an MVC and UAML manager 210, a service manager 220, a runtime manager 230, and an event. The manager 240 and the network manager 250 are included.

The MVC and UAML manager 210 manages a model, a view, and a controller, respectively, and parses and manages a UAML defining a model, a view, and a controller.

The MVC and UAML manager 210 manages a model and delivers events related to the model, a model manager 212, a view manager 214 that manages a view and delivers events related to the view, an controller and an event related to a controller. It includes a controller manager 216 for transmitting the UAML manager 218 to parse and manage the UAML.

The UAML manager 218 includes a UAML parser 219 for parsing UAML information which is meta information for managing an application. The UAML management unit 218 validates the parsed UAML information and, if there is no error, converts the UAML information into information necessary for the application framework and provides the converted information.

The service manager 220 drives and manages various services required by an application framework system or an application. The service manager 220 is a system service used directly by the application framework system. The service manager 220 drives and manages an automatic update service and a migration service of models, views, and controllers.

To this end, the service management unit 220 includes a migration service execution unit 222 that executes the migration of the application, and an automatic update service execution unit 224 that executes the automatic update of the application framework.

In the ubiquitous environment, the static service binding scheme is not suitable because the types of services may be different for each location where the application is executed. In the application framework according to the present invention, a service specification is defined and a pluggable service insertion structure. It supports the provision of services suitable for the ubiquitous environment. To this end, the service manager 220 includes, for example, a runtime service binder 226 that can bind to a web service according to a service standard provided by an application framework to support a web service.

The runtime manager 230 manages a life cycle related to loading execution and termination of an application, and maintains and manages information of a model, a view, and a controller. Application lifecycle management involves the installation and deployment of applications, and further manages the execution and termination of applications to support the management of the lifecycle associated with the deployment, installation, execution, termination, and deletion of applications.

The runtime management unit 230 includes runtime application information 232 for maintaining and managing information related to a currently running application, and runtime routing information 234 for maintaining location information at which an MVC component of a running application exists. . Location information is represented by logical location information according to the naming rules defined in the application framework. The logical location information corresponds to the physical IP address or channel name of the middleware and the mapping table for routing is maintained.

The event manager 240 transfers messages and data between models, views, and controllers. The event manager 240 generates and delivers various events issued by applications and application frameworks. The application framework is a message-driven system. All events that occur in the application framework are generated and delivered as XML-based messages. The event manager 240 analyzes the header of each event and delivers the message to the system event queue 242 of the application module or framework of the destination to which the message should be delivered.

In addition, the event manager 240 transmits the message generated by the message generator 244 and the message generator 244 to generate the event for the message transfer between the MVC components to the MVC components 244 to the MVC components. It includes a message transfer unit 246.

The network manager 250 delivers a message generated in the application to another framework or device. The network manager 250 may support interworking with various event messages or other sensors generated in an application by interworking with various middlewares existing under the application framework 120.

In a ubiquitous environment, various network infrastructures exist, and it is impossible to know what kind of network is used in an environment in which an application is executed at runtime. Therefore, in order to adapt adaptively to the ubiquitous environment, it must be able to support various network protocols and be able to select and bind which network protocol to transmit data at runtime.

To this end, the network manager 250 includes a runtime message broker binder 252 capable of binding a network adapter required at runtime. The network manager also includes a socket adapter 254, an infobus adapter 256, and other message broker adapter 258 that can connect to various networks.

3 shows a sequence diagram for data transfer between a view and a controller in a distributed MVC model.

When the event generated in the view 114 is input (S300), the view manager 214 passes through (S302), and passes to the event manager 240 (S304). The event manager 240 is generated as an event message (S306) and is transmitted to the network manager 250 (S308). The network manager 250 selects a message broker that is currently communicable (S310), and delivers a message to the target device to be delivered through the message broker 180 (S312) (S314).

When the target device receives the message through the message broker 180 (S316) (S318), when the network manager 250 delivers the received message to the event manager 240 (S320), the event manager 240 sends an event. The controller manager 216 transmits the data to the controller manager 216 (S322), and the controller manager 216 finds an appropriate controller (S324) and calls the controller 116 (S326).

The controller 116 transmits the calculated value to the controller manager 216 (S328), and the controller manager 216 transmits the calculated value to the event manager 240 (S330). The message is delivered through the network manager 250 and the message broker 180 (S332 to S338), and is delivered to the view manager 214 (S240). When the view 114 receives the event from the view manager 214 (S342), it shows the value calculated by updating the view (S344).

4 shows a sequence diagram in which views are migrated.

When an event occurs due to the movement of the user (S400), the runtime manager 230 requests a service from the service manager 220 (S402), and the service manager 220 finds a suitable service (S404).

When the service manager 220 requests a service from the migration service execution unit 222 (S406), the migration service execution unit 222 executes the migration service (S408). The migration service execution unit 222 delivers a message to the view manager 214 to obtain the state of the view (S410), and the view manager 214 finds the view (S412) and delivers the message to the view 114. (S414). The view 114 stores the view state (S416), and passes a message indicating the view state to the migration service execution unit 222 via the view manager 214 (S418) (S420).

The migration service execution unit 222 transmits a message for closing the view 114 through the view manager 214 (S422) (S424).

When the migration service execution unit 222 transmits a message to the event management unit 240 to create a new view (S426), the event management unit 240 passes the network management unit and the message broker to the event management unit 440 of the other device. Deliver the message (S428).

The event manager 440 allows the view manager 414 to generate the view 314 through the view manager 414 (S432). In addition, when the migration service execution unit 222 transmits a message for setting the current state of the view to the event management unit 240 (S434), the event management unit 240 passes through the network management unit and the message broker event management unit ( The message is forwarded to step 440 (S436).

The event manager 440 passes through the view manager 414 (S438) and causes the view 314 to set the current state (S440). When the view 314 recovers the view state (S442), the view service unit 414, the event manager 440, and the event manager 240 transmits a message indicating that the view state is restored to the migration service execution unit 222. If so, the migration service execution unit 222 transfers a message indicating that the migration service is completed to the runtime management unit 230 (S452).

Although a preferred embodiment of the present invention has been described in detail above, those skilled in the art to which the present invention pertains can make various changes without departing from the spirit and scope of the invention as defined in the appended claims. It will be appreciated that modifications or variations may be made. Accordingly, modifications to future embodiments of the present invention will not depart from the technology of the present invention.

According to the present invention, it is possible to develop an application that supports mobility of an application through a distributed MVC model and supports efficient functions such as utilization of distributed computing resources. In addition, the use of messages in Flash and XML formats makes it easy to develop platform-independent applications. In addition, it is easy to distribute and update the application, and it is possible to reduce coding work because there is no need to write code for migration and distributed execution when developing an application in a ubiquitous environment.

Claims (14)

In the application framework for the distribution and mobility of the application consisting of the model, view and controller (MVC) in the ubiquitous environment, An MVC and UAML manager that manages the models, views, and controllers respectively, and parses and manages a Ubiquitous Application Mark-up Language (UAML) defining the models, views, and controllers; A service manager for driving and managing an automatic update service and a migration service of the model, view and controller; A runtime manager that manages a life cycle related to loading execution and termination of the application and maintains and manages information of the model, view, and controller; An event manager for transmitting messages and data between the models, views, and controllers; And Application framework for the distribution and mobility of the application, characterized in that it comprises a network management unit for transmitting a message generated in the application to another framework or device. According to claim 1, MVC and UAML management unit, A model manager for managing the model and delivering an event related to the model; A view manager for managing the view and delivering an event related to the view; A controller manager for managing the controller and delivering an event related to the controller; And Application framework for distribution and mobility of the application comprising a UAML management unit for parsing and managing the UAML. The method of claim 1, wherein the UAML, Definition of the purpose and meta information of the application, definition of the MVC component, execution environment requirements of the MVC component, format definition of events for data exchange between MVC components, data storage location definition and migration policy of the application An application framework for distribution and mobility of an application, characterized in that it comprises at least one of the definitions. The method of claim 1, wherein the service management unit, A migration service execution unit that executes migration of the application; An automatic update service execution unit executing automatic update of the application framework; And And a runtime service binder that binds with the web service when the application is executed. The method of claim 1, wherein the runtime management unit, Runtime application information for maintaining and managing information related to currently running applications; And An application framework for distribution and mobility of an application, comprising runtime routing information that maintains location information where the MVC component of a running application is present. The apparatus of claim 1, wherein the event manager comprises: a message generator configured to generate an event based on an extensible mark-up language (XML) based message for message transmission between the MVC components; And And a message transfer unit configured to transfer the message generated by the message generator to the MVC components. The method of claim 1, wherein the view, Application framework for distributed and mobile applications, characterized by using Macromedia Flash. In the application framework system for the distribution and mobility of the application consisting of the model, view and controller (MVC) in the ubiquitous environment, A plurality of devices including an application and an application framework; An application server for storing an application to be distributed to the device; And A message broker for transferring messages and data between the plurality of devices and an application server and between the plurality of devices, The application framework, An MVC and UAML manager that manages the models, views, and controllers respectively, and parses and manages a Ubiquitous Application Mark-up Language (UAML) defining the models, views, and controllers; A service manager for driving and managing an automatic update service and a migration service of the model, view and controller; A runtime manager that manages a life cycle related to loading execution and termination of the application and maintains and manages information of the model, view, and controller; An event manager for transmitting messages and data between the models, views, and controllers; And Application framework system for distribution and mobility of the application, characterized in that it comprises a network management unit for transmitting a message generated in the application to another framework or device. According to claim 8, MVC and UAML management unit, A model manager for managing the model and delivering an event related to the model; A view manager for managing the view and delivering an event related to the view; A controller manager for managing the controller and delivering an event related to the controller; And Application framework system for distribution and mobility of the application comprising a UAML management unit for parsing and managing the UAML. The method of claim 8, wherein the UAML, Definition of the purpose and meta information of the application, definition of the MVC component, execution environment requirements of the MVC component, format definition of events for data exchange between MVC components, data storage location definition and migration policy of the application An application framework system for distribution and mobility of an application comprising at least one of the definitions. The method of claim 8, wherein the service management unit, A migration service execution unit that executes migration of the application; An automatic update service execution unit executing automatic update of the application framework; And And a runtime service binder that binds to the web service when the application is executed. The method of claim 8, wherein the runtime management unit, Runtime application information for maintaining and managing information related to currently running applications; And An application framework system for distribution and mobility of an application, comprising runtime routing information that maintains location information where MVC components of a running application are present. The method of claim 8, wherein the event management unit, A message generator to generate an event for message transmission between the MVC elements as an XML based extensible mark-up language (message); And And a message transfer unit configured to transfer the message generated by the message generator to the MVC components. The method of claim 8, wherein the view, An application framework system for the distribution and mobility of applications characterized by using Macromedia Flash.

Images