KR20040046674A - Mobile application server for various mobile devices - Google Patents

Abstract

PURPOSE: A mobile application server for supporting various wireless terminals is provided to convert an HTTP mobile application request into a mobile request, and to execute a mobile application by parsing the mobile request, then to transmit executed results to a terminal, thereby reducing cost of wireless Internet service application development and maintenance. CONSTITUTION: A mobile request generator(20) generates a mobile request. A mobile engine(30) calls a handler for executing a mobile application, executes contents, and transmits the contents to a mobile terminal. A Java view handler(40) searches the mobile application corresponding to the mobile request to execute the mobile application, and stores a mobile response. An MSP view handler(50) searches the mobile application corresponding to the mobile request to execute the mobile application, and stores a mobile response. A profile manager(60) finds out information on the mobile terminal by parsing the mobile request. A session manager(70) generates a session for the mobile application and the mobile response, and manages the session. A component manager manages a life period of the mobile application. A contents converter(90) converts the contents, and transmits the contents to the mobile engine(30).

Description

Mobile application server and its method for supporting various wireless terminals {Mobile application server for various mobile devices}

The present invention relates to an application server capable of providing a wireless Internet service, and more particularly, to a mobile application, which is an intermediate type of content that can be commonly serviced to various types of mobile terminals such as mobile phones and PDAs. And it relates to a mobile application server and a method for supporting a variety of wireless terminals that can support this.

As is known, the demand for a new type of mobile service is increasing according to the change of mobile environment by the advance of mobile terminal technology and wireless internet technology. The figure is expected to increase exponentially to 130,000 in 2003.

In addition, existing providers of wired Internet services are expanding their coverage into wireless areas, for example, by adding message processing systems that can send messages to mobile terminals in application servers that can provide wired Internet services. It has limited support for mobile services.

Meanwhile, conventional technologies for supporting such mobile services include content conversion technology for converting content suitable for various mobile terminals to support mobile services, data synchronization technology for data matching between mobile terminals and server-side databases, and wired data. Mobile groupware technology, message processing systems such as SMS (Short Message Service) and MMS (Multimedia Message Service) are being developed to extend groupware to mobile environments.

However, the conventional mobile service support technologies as described above have disadvantages of insufficient functions for wired / wireless integrated services, and not middleware functions for mobile business services.

Therefore, in order to effectively provide a wireless Internet service, it is absolutely necessary to research a mobile application server that can easily develop a new service and effectively manage the life cycle of the mobile application without knowledge of a mobile terminal. .

The mobile application server is an application server that can develop and operate a business service that can be used in a wireless environment using a mobile terminal. The mobile application server can easily develop distributed component logic without knowledge of a complicated infrastructure of the wireless environment. It is a server-side middleware that can efficiently manage the life cycle of the developed logic, and the wireless Internet service supported by this mobile application server is a mobile service that can overcome the constraints of the wireless mobile terminal and the intermittent disconnection of the mobile communication network.

An example of a wireless Internet application supported by the mobile application server may be an example of extending an existing electronic commerce service. In the case of the existing wired Internet service, a desired product can be searched and ordered using a PC terminal connected by wired LAN or wireless LAN, but the mobile application server uses not only a PC connected by LAN but also various mobile terminals such as a mobile phone and a PDA. Provides services to make e-commerce more convenient.

As such, when the mobile application server enables electronic commerce in a wired / wireless integrated environment using various mobile terminals as well as a PC, a service may be provided regardless of the terminal type and the network. For example, a user may use a laptop connected to a wireless LAN in a company to search for a product to be ordered or use a CDMA PDA to place a searched product in a shopping cart. You can order and pay using. In addition, the delivery can be confirmed by using a personal computer connected to the high-speed communication network after arriving at home.

In particular, unlike the known web application server, the mobile application server does not have an internationally recognized industry standard, and research organizations and related studies also propose individual system structures. In other words, although there are separate standards such as software running environment of mobile terminal, Access Gateway, SMS, MMS, J2EE, .NET, Workflow, etc., it is a standard for overall framework of mobile application server and related functions. Does not exist.

Accordingly, the present applicant has developed a mobile application server and a method for developing a mobile application, which is an intermediate type of content that can be commonly serviced to various types of mobile terminals, such as a mobile phone and a PDA, and supporting the same. The objective is to develop a mobile application, which is an intermediate form of content that can be commonly serviced to various types of mobile terminals such as cell phones and PDAs, to manage its life cycle, and to automatically identify the characteristics and constraints of the mobile application. The mobile terminal requested by the terminal is displayed in a form that can be displayed, and for this purpose, the HTTP mobile application request received from the mobile terminal as a client is converted into a mobile request, and then the parsed mobile request is parsed. After running, the execution result of the mobile terminal The present invention provides a mobile application server and a method for supporting a variety of wireless terminals to be transmitted to the terminal in accordance with the type.

A mobile application server for supporting various wireless terminals to achieve the object of the present invention, the mobile request generation unit for receiving a mobile HTTP request from a plurality of mobile terminals of the client from a known HTTP web server and generates a mobile request; A mobile engine for interpreting the mobile request, calling a handler to execute a mobile application which is intermediate content corresponding to the request, and executing the mobile application to transmit the converted content to the mobile terminal; A Java view handler which, when called by the mobile engine, finds and executes a mobile application corresponding to the mobile request in a DB that stores an intermediate view of a Java view and an MSP view; An MSP view handler that, when called by the mobile engine, locates and executes a mobile application corresponding to the mobile request in a DB that stores an intermediate view of a Java view and an MSP view; A profile manager which parses a mobile request transmitted through the mobile engine and finds information about a mobile terminal which is a client that has transmitted the mobile request; Find and manage sessions that may be in mobile requests delivered through the mobile engine, or create and manage sessions for mobile applications and mobile responses when requesting sessions from mobile applications executed by the Java view handler and MSP view handler A session manager; A component manager which manages a life cycle of a mobile application executed by the Java view handler and the MSP view handler; And converting the content obtained by the Java view handler and the MSP view handler by executing the mobile application to the mobile terminal which is the client that sent the mobile request, by using the information about the mobile terminal which is the client found by the profile manager. Consists of the content conversion unit to deliver.

The mobile application method for supporting various wireless terminals to achieve the object of the present invention, the mobile application server receives a mobile application request from a plurality of mobile terminals that are clients through a known HTTP web server and converts it into a mobile request Wow; Analyzing, by the mobile application server, a mobile request to retrieve a mobile application; Generating content by executing the mobile application when the mobile application server is found; Analyzing, by the mobile application server, the mobile request to find out attributes of the client; Converting the content generated by the mobile application server according to a client attribute found by analyzing a mobile request; And transmitting, by the mobile application server, the mobile content to the client by analyzing the mobile request and converting the content according to the client.

1 is a block diagram showing a mobile application server according to the present invention,

2 is a block diagram illustrating a mobile request generation unit;

3 is a block diagram showing a session management unit;

4 is a configuration diagram illustrating a component manager;

5 is a block diagram showing a content conversion unit;

6 is a flowchart illustrating a mobile application method according to the present invention.

<Description of the symbols for the main parts of the drawings>

10: HTTP web server 20: mobile request generator

21: application request receiver 22: application request queue

23: Application Request Processor 30: Mobile Engine

30a: DB 40: Java View Handler

50: MSP View Handler 60: Profile Manager

70: session manager 71,72,73; Session handler

74: storage controller 80: component conversion unit

81, 82, 83: application management unit 90: content conversion unit

91: annotation processor 92: profile collector

93: Profile Aggregator

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 to 5, the mobile request generator 20 receives an HTTP mobile application request from a plurality of mobile terminals that are clients from a known HTTP web server 10 and generates a mobile request.

The mobile application request receiving unit 21 of the mobile request generation unit 20 receives an HTTP mobile application request from a plurality of mobile terminals that are clients from the HTTP web server 10 and sends a socket to the mobile application request queue 22. Save it.

The application request processor 23 of the mobile request generation unit 20 generates a mobile application request using a socket stored in the mobile application request queue 22.

The mobile engine 30 interprets the mobile request, calls a handler to execute a mobile application such as a Java view and an MSP view, which are intermediate forms of the content, and executes the mobile application to convert the content. Send to the mobile terminal.

When the Java view handler 40 is called by the mobile engine, the Java view handler 40 searches for and executes a mobile application corresponding to the mobile request in the DB 30a which stores the Java view and the MSP view, which are intermediate forms of content, and stores the mobile response. .

When the MSP view handler 50 is called by the mobile engine 30, the mobile response corresponding to the mobile request is found by executing a mobile application corresponding to the mobile request in the DB 30a which stores the Java view and the MSP view, which are intermediate forms of content. Save it.

The profile manager 60 parses the mobile request transmitted through the mobile engine 30 to find out information about the mobile terminal that is the client that transmitted the mobile request.

The profile manager 60 manages terminal characteristic information and terminal user information, such as memory, screen size, keyboard type, etc. of the mobile terminal. Particularly, the characteristic information of the terminal is obtained when a mobile application request of the terminal is received at the server side. The header information UAProf (User Agent Profile) is analyzed and stored in the profile repository. This property information can be updated by the system administrator using a separate profile editing tool.

The session manager 70 finds and manages a session that may be in a mobile request transmitted through the mobile engine 30 or manages a session in a mobile application executed by the Java view handler 40 and the MSP view handler 50. When requested, a session is created and managed for the mobile application and the mobile response.

The session manager 70 finds a session in the mobile request delivered through the mobile engine 30 and sets a session and session ID in the mobile request and the mobile response so that the session can be used later.

When the session manager 70 requests a session in the mobile application executed by the Java view handler 40 and the MSP view handler 50, the session manager 70 may obtain a mobile application name from the mobile application context, which is information about the mobile application stored in the mobile request. The session handlers 71, 72, and 73 manage sessions for the mobile application and set the session and session ID in the mobile application and the mobile response.

The session handlers 71, 72, and 73 use the storage controller 73 to re-use sessions already stored in memory, thereby improving the performance of the mobile application server.

The component manager 80 manages a life cycle of the mobile application executed by the Java view handler 40 and the MSP view handler 50.

The component manager 80 creates an instance set for the mobile bean in each mobile application at the initial stage of operation, and then increases the number of instances stored in memory as the mobile application request increases, and the mobile application request is As it decreases, it manages the life cycle of mobile applications by reducing the number of unnecessary instances.

The component manager 80 manages a life cycle of mobile beans in each mobile application by a plurality of application managers 81, 82, and 83 classified by mobile applications.

The content conversion unit 90 requests the content obtained by executing the mobile application by the Java view handler 40 and the MSP view handler 50 by using the information about the mobile terminal that is the client found by the profile manager 60. It is converted to fit the mobile terminal that is the client that transmits the transfer to the mobile engine 30.

The annotation processor 91 of the content converter 90 uses predefined clipping information, annotation information indicating importance according to the type of the mobile terminal, and device profile information of the mobile terminal which is a client found by the profile manager 60. Thus, the Java view handler 40 and the MSP view handler 50 select a specific content from the mobile response obtained by executing the mobile application to create a document.

The profile collector 92 of the content converter 90 extracts document profile information from the device profile information of the mobile terminal, which is the client found by the profile manager 60, and the document generated by the annotation processor 91.

The profile aggregator 93 of the content converter 90 cuts the document into pieces according to the characteristics of tag filtering, tag conversion, and the mobile terminal using attribute values in the device profile information and document profile information. By performing division, the annotation processor 91 converts a document generated by selecting only specific content from the mobile response and delivers the document to the mobile engine 30.

The mobile application server for supporting various wireless terminals according to the present invention configured as described above operates as follows.

First, the mobile application server receives a mobile application request from a plurality of mobile terminals as a client through a known HTTP web server 10 (S10) and converts it into a mobile request to generate a mobile request for the mobile application request (S10). S20).

In this step (S10, S20), the mobile request generation unit 20 of the mobile application server receives the HTTP mobile application request from the web server 10 through a known AJP protocol module (not shown) to generate a mobile request do.

The AJP protocol module is implemented by the mod_jk.dll Apache plug-in module, which is an AJP connector used for interworking with the HTTP web server 10 and the Tomcat web server, and according to the HTTP web server 10 and the present invention. Used as a module for interworking mobile application servers. Indeed, a mobile application related request among JSP or servlet requests entered into the HTTP web server 10 is transmitted to the mobile application server according to the present invention using port 8009 of the AJP protocol module.

In addition, the mobile application generated by the mobile request generation unit 20 has an interface for accessing information on the mobile terminal serving as a client, parameters for the mobile application request, header information delivered through the mobile application request, and the like. Therefore, when a mobile application request comes in port 8009 by the AJP protocol module, the application request receiving unit 21 of the mobile request generating unit 20 stores a socket in the application request queue 22. The application request processor 23 then generates a mobile request from the mobile application request of the mobile terminal which is the client transmitted via the AJP protocol module using the socket stored in the application request queue 22.

After the mobile request is generated as described above, the mobile application server searches for the mobile application by analyzing the mobile request (S30).

In this step (S30), the mobile engine 30 interprets the mobile request and calls a handler to execute a mobile application such as a Java view and an MSP view, which are intermediate forms of content corresponding to the request. Therefore, the Java view handler 40 and the MSP view handler 50 find the Java view and the MSP view, which are mobile applications corresponding to the mobile request, in the DB 30a, respectively.

After searching for the mobile application as described above, if there is a searched mobile application, the mobile application server executes the corresponding mobile application to generate content (S40).

In this step (S40), while executing the Java view which is the mobile application found by the Java view handler 40 to store the mobile response, the mobile response by executing the MPS view, which is the mobile application found by the MSP view handler 50 And store the clipping information previously defined by the annotation processor 91 of the content converter 90, the annotation information indicating the importance according to the type of the mobile terminal, and the client found by the profile manager 60. Using the device profile information, the Java view handler 40 and the MSP view handler 50 select a specific content from a mobile response obtained by executing a mobile application to create a document.

In this case, the profile collector 92 of the content converter 90 extracts document profile information from the device profile information of the mobile terminal which is the client found by the profile manager 60 and the document generated by the annotation processor 91. do.

After generating the content by executing the mobile application as described above, the mobile application server analyzes the mobile request to find the properties of the client (S50), the generated content to the client properties found by analyzing the mobile request After the conversion is made (S60), the converted content is transmitted to the corresponding client (S70).

In this step (S50, S60, S70), the profile aggregator 93 of the content conversion unit 90 finds the property value in the device profile information and the document profile information extracted by the profile collector 92, and then the annotation processor. Tag filtering, tag conversion, and document dividing into several pieces according to the characteristics of the mobile terminal are performed on the document generated by selecting only specific content from the mobile response, and the document is converted into the document. 30).

As described above, the mobile application server and the method for supporting various wireless terminals according to the present invention develop a mobile application which is an intermediate type of content that can be commonly serviced to various types of mobile terminals such as mobile phones, PDAs, and the like. It manages the life cycle and automatically shows the mobile application's features and constraints and displays them in a form that the corresponding device can display.For this purpose, the mobile application requests the HTTP mobile application request received from the mobile terminal as a client. After converting to Mobile Request, the mobile request requested is parsed and the mobile application requested by the terminal is executed, and then the execution result is changed according to the type of the mobile terminal and transmitted to the terminal. Follow the wireless Internet service application development and maintenance for In addition to reducing the cost, it is advantageous in providing various wireless Internet services to various types of terminals more conveniently and efficiently in a wireless Internet environment.

What has been described above is only one embodiment for implementing a mobile application server and a method for supporting various wireless terminals according to the present invention, the present invention is not limited to the above-described embodiment, the scope of the claims Without departing from the gist of the present invention claimed in the present invention, anyone of ordinary skill in the art will have the technical spirit of the present invention to the extent that various modifications can be made.

Claims (8)

A mobile request generation unit for receiving an HTTP mobile application request from a plurality of mobile terminals which are clients from a known HTTP web server and generating a mobile request; A mobile engine for interpreting the mobile request, calling a handler to execute a mobile application which is intermediate content corresponding to the request, and executing the mobile application to transmit the converted content to the mobile terminal; A Java view handler which, when called by the mobile engine, finds and executes a mobile application corresponding to the mobile request in a DB that stores an intermediate view of a Java view and an MSP view; An MSP view handler that, when called by the mobile engine, searches for and executes a mobile application corresponding to the mobile request in a DB that stores an intermediate view of a Java view and an MSP view; A profile manager which parses a mobile request transmitted through the mobile engine and finds information about a mobile terminal which is a client that has transmitted the mobile request; Find and manage sessions that may be in mobile requests delivered through the mobile engine, or create and manage sessions for mobile applications and mobile responses when requesting sessions from mobile applications executed by the Java view handler and MSP view handler A session manager; A component manager which manages a life cycle of a mobile application executed by the Java view handler and the MSP view handler; And Using the information about the mobile terminal, the client found by the profile manager, the content obtained by executing the mobile application by the Java view handler and the MSP view handler is converted to the mobile terminal which is the client that sent the mobile request and delivered to the mobile engine. Content conversion unit to say Mobile application server for supporting a variety of wireless terminals, characterized in that consisting of. The method of claim 1, wherein the mobile request generation unit A mobile application request receiving unit for receiving HTTP mobile application requests from a plurality of mobile terminals that are clients from a known HTTP web server and storing sockets in a mobile application request queue; And An application request processor generating a mobile application request using a socket stored in the mobile application request queue Mobile application server for supporting a variety of wireless terminals, characterized in that consisting of. The method of claim 1, wherein the session management unit The mobile application server for supporting a variety of wireless terminals, characterized in that the session and the session ID is set in the mobile request and the mobile response to find the session in the mobile request delivered through the mobile engine for later use. The method of claim 1, wherein the session management unit When a mobile application executed by the Java view handler and the MSP view handler requests a session, the mobile application name is managed from the mobile application context, which is information about the mobile application stored in the mobile request, to manage the session for the mobile application. A mobile application server for supporting a variety of wireless terminals, characterized in that for setting the session and session ID in the mobile application and the mobile response using the session handler. The method of claim 4, wherein the session handler is Mobile application server for supporting a variety of wireless terminal, characterized in that if there is a session already stored in the memory by using a storage controller. The method of claim 1, wherein the component management unit Initially, after creating instances set up for mobile beans in each mobile application, the number of instances stored in memory increases as mobile application requests increase, and the number of unnecessary instances as mobile application requests decreases. Managing the life cycle of mobile applications by reducing the, and the life cycle of the mobile bean in each mobile application is managed by a plurality of application managers classified by mobile applications, mobile application server for supporting various wireless terminals. The method of claim 1, wherein the content conversion unit A mobile device obtained by executing the mobile application by the Java view handler and the MSP view handler using predefined clipping information, annotation information indicating importance according to the type of the mobile terminal, and device profile information of the mobile terminal which is a client found by the profile manager. An annotation processor for generating a document by selecting only specific content in response; A profile collector for extracting document profile information from device profile information of a mobile terminal which is a client found by the profile manager and a document generated by the annotation processor; And Tag filtering, tag conversion, and document segmentation, which cuts the document into pieces according to the characteristics of the mobile terminal using the attribute values in the device profile information and the document profile information, allows the annotation processor to select only specific content from the mobile response. Profile aggregator that converts the created document and delivers it to the mobile engine Mobile application server for supporting a variety of wireless terminals, characterized in that consisting of. Receiving, by the mobile application server, a mobile application request from a plurality of mobile terminals which are clients through a known HTTP web server, and converting the mobile application request into a mobile request; Analyzing, by the mobile application server, a mobile request to retrieve a mobile application; Generating content by executing the mobile application when the mobile application server is found; Analyzing, by the mobile application server, the mobile request to find out attributes of the client; Converting the content generated by the mobile application server according to a client attribute found by analyzing a mobile request; And The mobile application server analyzing the mobile request and transmitting the converted content to the corresponding client to the corresponding client Mobile application method for supporting a variety of wireless terminals, characterized in that consisting of.