KR20160121989A - Mobile Application Server for ios and Android support - Google Patents

Mobile Application Server for ios and Android support Download PDF

Info

Publication number
KR20160121989A
KR20160121989A KR1020150051945A KR20150051945A KR20160121989A KR 20160121989 A KR20160121989 A KR 20160121989A KR 1020150051945 A KR1020150051945 A KR 1020150051945A KR 20150051945 A KR20150051945 A KR 20150051945A KR 20160121989 A KR20160121989 A KR 20160121989A
Authority
KR
South Korea
Prior art keywords
mobile
request
mobile application
session
application
Prior art date
Application number
KR1020150051945A
Other languages
Korean (ko)
Inventor
박대권
Original Assignee
(주)픽쳐스
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by (주)픽쳐스 filed Critical (주)픽쳐스
Priority to KR1020150051945A priority Critical patent/KR20160121989A/en
Publication of KR20160121989A publication Critical patent/KR20160121989A/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/181—Transcoding devices; Rate adaptation devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a mobile application server and a method thereof for supporting various wireless terminals, and a mobile application, which is an intermediate type content that can be commonly served to various types of mobile terminals such as a mobile phone, a PDA, life cycle of the mobile terminal. The mobile application automatically finds the characteristics and constraints of the terminal and displays it in a form that the terminal can display. To this end, the HTTP mobile application request received from the mobile terminal, ), Parses the converted mobile request to execute the mobile application requested by the terminal, and then transfers the execution result to the terminal in accordance with the type of the mobile terminal. Accordingly, Based on the development and maintenance of wireless Internet service application for Has the advantage of being able to not only reduce costs, but more convenient in a wireless Internet environment provides a variety of wireless Internet services efficiently to different types of devices.

Figure pat00001

Description

Mobile application server for iOS and Android support {Mobile Application Server for iOS and Android support}

technology for mobile application servers for iOS and Android support.

The present invention relates to an application server capable of providing a wireless Internet service, and it is an object of the present invention to develop a mobile application, which is an intermediate form content that can be commonly served to mobile terminals of various device types, To a mobile application server and a method thereof for supporting a terminal.

As is well known, the demand for a new type of mobile service is increasing due to the mobile environment change due to the advancement of the mobile terminal technology and the wireless Internet technology. The number of the domestic wireless Internet service companies was 2400 in 2001 It is expected to increase exponentially to 130,000 in 2003.

In addition, the existing wired Internet service providers are expanding the service area to a wireless area. For example, by adding a message processing system capable of sending a message to a mobile terminal to an application server capable of providing an existing wired Internet service Limited mobile service support.

Conventional technologies for supporting such mobile services include a content converter for converting a content suitable for a variety of mobile terminals to support a mobile service, a data synchronization technique for matching data between a mobile terminal and a server-side database, A mobile groupware technology for expanding groupware into a mobile environment, a message processing system such as an SMS (Short Message Service) and an MMS (Multimedia Message Service) are being developed.

However, since the conventional mobile service supporting technologies as described above are focused on specific functions, the functions for wired / wireless integrated services are insufficient and the middleware functions for mobile business services are not provided integrally.

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

The mobile application server is an application server capable of developing and operating a business service that can be used in a wireless environment using a mobile terminal, and can easily develop distributed component logic without knowledge of a complicated infrastructure related to the wireless environment. The middleware is a server - side middleware that can efficiently manage the life cycle of the developed logic. The wireless Internet service supported by the mobile application server is a mobile service that can overcome intermittent disconnections of the wireless mobile terminal and the restriction of the wireless mobile terminal.

An example of a wireless Internet application supported by the mobile application server is a case in which an existing electronic commerce service is extended. In the case of the existing wired Internet service, a desired product can be searched and ordered using a PC terminal connected to a wired LAN or a wireless LAN. However, in the mobile application server, various mobile terminals such as a mobile phone, a PDA, And provides a service for performing electronic commerce more conveniently.

As described above, when electronic commerce can be performed in a wired / wireless integrated environment using various mobile terminals as well as a PC in the mobile application server, services can be provided regardless of the terminal type and the network. For example, a user can search for a product to be ordered using a laptop connected to a wireless LAN in a company, or store a product retrieved using a CDMA PDA in a shopping cart, and a CDMA mobile phone You can order and pay by using. Also, after arriving at home, you can check the delivery using a personal computer connected to the high-speed network.

Particularly, in the case of the mobile application server, unlike the known web application server, there is no internationally recognized industry standard, and research institutes and related studies also propose individual system structures. In other words, there are individual standards such as software operating environment of mobile terminal, access gateway, SMS, MMS, J2EE, .NET, work flow, etc. However, standard of mobile application server overall framework and related functions Is not present.

Accordingly, the present applicant has developed a mobile application server and its method capable of developing and supporting a mobile application, which is an intermediate form content that can be commonly served to various types of mobile terminals such as a mobile phone, a PDA, The goal is to develop and manage the life cycle of a mobile application, which is an intermediate form of content that can serve common types of mobile terminals such as mobile phones and PDAs, In order to do so, the terminal displays the HTTP mobile application request received from the mobile terminal, which is the client side, into a mobile request, parses the converted mobile request, And then transmits the execution result to the mobile terminal Mobile application for a wide range of wireless terminal according to the type of support to change to send to the device to provide a server and a method thereof.

In order to achieve the above object, the mobile application server for supporting various wireless terminals includes: a mobile request generation unit for receiving a HTTP mobile application request from a plurality of mobile terminals, which are clients, from a known HTTP web server to generate a mobile request; A mobile engine for interpreting the mobile request and calling a handler that executes a mobile application that is an intermediate type content corresponding to the request, and executing the corresponding mobile application to transmit the converted content to the mobile terminal; A Java view handler for locating and executing a mobile application corresponding to the mobile request in a DB storing intermediate views of Java view and MSP view when called by the mobile engine; An MSP view handler for searching for and executing a mobile application corresponding to the mobile request in a DB storing intermediate views of JavaView and MSP views when the mobile engine is called by the mobile engine; A profile manager for parsing a mobile request transmitted through the mobile engine and obtaining information on a mobile terminal that is a client that has transmitted the mobile request; When a session is requested from the mobile application executed by the Java view handler and the MSP view handler, a session for the mobile application and the mobile response is generated and managed A session management unit;

A component manager for managing a life cycle of the mobile application executed by the Java view handler and the MSP view handler; And the Java view handler and the MSP view handler convert the content obtained by executing the mobile application into a mobile terminal, which is a client that has transmitted the mobile request, using the information about the mobile terminal, which is the client, And a content conversion unit for transmitting the content.

In order to achieve the object of the present invention, there is provided a mobile application method for supporting various wireless terminals, comprising: receiving a mobile application request from a plurality of mobile terminals, which are clients through a known HTTP web server, Wow; The mobile application server analyzing a mobile request to search for a mobile application; Generating a content by executing the mobile application when the mobile application server searches for the mobile application; Analyzing a mobile request by the mobile application server and determining an attribute of the client; Analyzing the content generated by the mobile application server and converting the content into a client attribute according to the analyzed client request; And analyzing the mobile request by the mobile application server and transmitting the converted content to the client.

As described above, the mobile application server and the method for supporting various wireless terminals according to the present invention can develop mobile applications that are medium type contents that can be commonly served to various types of mobile terminals such as mobile phones, PDAs, And manages the life cycle. The mobile application automatically finds the characteristics and constraints of the terminal and displays it in a form that the terminal can display. To this end, the HTTP mobile application request received from the mobile terminal, Mobile request, and then parses the converted mobile request to execute the mobile application requested by the terminal. Then, the execution result is transmitted to the terminal by changing the execution result according to the type of the mobile terminal. Therefore, To develop and maintain a wireless Internet service application for Not only the cost can be reduced but also various wireless Internet services can be provided in various types of terminals more conveniently and efficiently in the wireless Internet environment.

The present invention is not limited to the above-described embodiments, and various modifications and changes may be made without departing from the scope of the following claims It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

.

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

1 to 5, the mobile request generation unit 20 receives an HTTP mobile application request from a plurality of mobile terminals, which are clients, from a known HTTP web server 10 to generate a mobile request.

The mobile application request receiving unit 21 of the mobile request generation unit 20 receives a 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 .

The application request processor 23 of the mobile request generation unit 20 generates a mobile application request using the 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 content corresponding to the request, executes the corresponding mobile application, To the corresponding mobile terminal.

When the Java view handler 40 is called by the mobile engine, the Java view handler 40 finds and executes the mobile application corresponding to the mobile request in the DB 30a storing the Java view and MSP view, which are intermediate contents, and stores the mobile response .

When the MSP view handler 50 is called by the mobile engine 30, the MSP view handler 50 finds and executes the mobile application corresponding to the mobile request from the DB 30a storing the Java view and the MSP view, Save the response.

The profile management unit 60 parses the mobile request transmitted through the mobile engine 30 and obtains information on the mobile terminal, which is a client that has transmitted the mobile request.

The profile management unit 60 manages characteristic information of the terminal and terminal user information such as memory, screen size, keyboard type, etc. of the mobile terminal. In particular, the characteristic information of the terminal is stored at the time when the mobile application request of the terminal is accepted The UAProf (User Agent Profile), which is the header information, is analyzed and stored in the profile repository. The feature information can be updated by the system administrator using a separate profile editing tool.

The session management unit 70 manages a session in the mobile application that is transmitted through the mobile engine 30 or manages a session in the mobile application executed by the Java view handler 40 and the MSP view handler 50 When required, it creates and manages a session for the mobile application and the mobile response.

The session management unit 70 establishes a session and a session ID in a mobile request and a mobile response so that the session management unit 70 can find and use a session in a mobile request transmitted through the mobile engine 30.

When the session is requested in the mobile application executed by the Java view handler 40 and the MSP view handler 50, the session management unit 70 acquires a mobile application name from the mobile application context, which is information about the mobile application stored in the mobile request, And establishes a session and a session ID in the mobile application and the mobile response using the session handlers 71, 72, and 73 for managing the session for the corresponding mobile application.

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

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

The component management unit 80 generates an instance set for a mobile bean in each mobile application at the initial stage of driving, increases the number of instances stored in the memory as the mobile application request increases, And manages the lifecycle of the mobile application by reducing the number of unnecessary instances as it decreases.

The component management unit 80 manages the life cycle of the mobile bean in each mobile application by a plurality of application management units 81, 82, and 83 classified according to the mobile application.

The content conversion unit 90 converts the content obtained by executing the mobile application by the Java view handler 40 and the MSP view handler 50 using the information about the mobile terminal, which is the client found in the profile management unit 60, And transmits the converted data to the mobile engine 30.

The annotation processor 91 of the content conversion unit 90 uses the predefined clipping information, the annotation information indicating the importance according to the type of the mobile terminal, and the device profile information of the mobile terminal, which is the client found in the profile management unit 60 The Java view handler 40 and the MSP view handler 50 form a document by selecting only specific content from the mobile response obtained by executing the mobile application.

The profile collector 92 of the content conversion unit 90 extracts the device profile information of the mobile terminal which is the client found in the profile management unit 60 and the document profile information from the document generated by the annotation processor 91.

The profile aggregator 93 of the content conversion unit 90 uses the attribute values in the device profile information and the document profile information to perform a tag filtering, a tag conversion, and a document And the annotation processor 91 converts the document selected only for the specific content in the mobile response and transmits the converted document to the mobile engine 30.

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

First, the mobile application server receives a mobile application request from a plurality of mobile terminals, which are clients, through a known HTTP web server 10, converts the mobile application request into a mobile request, and generates a mobile request for the mobile application request S20).

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

The AJP protocol module is implemented by a 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. The HTTP web server 10 and the It is used as a module for interworking mobile application server. Actually, a request related to a mobile application in a JSP or a Servlet request coming into the HTTP web server 10 is transmitted to the mobile application server according to the present invention using the port 8009 of the AJP protocol module.

The mobile application generated by the mobile request generation unit 20 may include an interface for accessing information about a mobile terminal acting as a client, parameters for a mobile application request, header information delivered through a mobile application request, The application request receiving unit 21 of the mobile request creating unit 20 stores the socket in the application request queue 22 when the mobile application request is received at port 8009 by the AJP protocol module And then the application request processor 23 generates a mobile request from the mobile application request of the mobile terminal which is a client transmitted through 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 analyzes the mobile request and searches for the mobile application (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 contents corresponding to the request, Accordingly, the Java view handler 40 and the MSP view handler 50 search for a Java view and an MSP view, which are mobile applications corresponding to a mobile request, in the DB 30a, respectively.

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

In step S40, the Java view handler 40 executes the Java view, which is a mobile application, to store the mobile response, and executes the MPS view, which is the mobile application found by the MSP view handler 50, Annotation information indicating importance according to the type of the mobile terminal, clipping information predefined by the annotation processor 91 of the content conversion unit 90, and annotation information indicating the importance according to the type of the mobile terminal, The Java view handler 40 and the MSP view handler 50 use the device profile information to create a document by selecting only specific contents from the mobile response obtained by executing the mobile application.

The profile collector 92 of the content conversion unit 90 extracts the device profile information of the mobile terminal and the document profile information from 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 and finds the attribute of the corresponding client (S50). After analyzing the generated content, the mobile application server analyzes the mobile request, (S60), and transmits the converted content to the corresponding client (S70).

The profile aggregator 93 of the content conversion unit 90 obtains the attribute values in the device profile information and the document profile information extracted by the profile collector 92 and outputs the attribute values to the annotation processor 92. In step S50, The mobile terminal 91 performs tag filtering, tag conversion, and document segmentation to cut the document into several pieces according to the characteristics of the mobile terminal, converts the document into a document, 30).

.

Claims (1)

Claim 1.
A mobile request generator for generating a mobile request by receiving an HTTP mobile application request from a plurality of mobile terminals which are clients from a known HTTP web server;
A mobile engine for interpreting the mobile request and calling a handler that executes a mobile application that is an intermediate type content corresponding to the request, and executing the corresponding mobile application to transmit the converted content to the mobile terminal;
A Java view handler for locating and executing a mobile application corresponding to the mobile request in a DB storing intermediate views of Java view and MSP view when called by the mobile engine;
An MSP view handler for searching for and executing a mobile application corresponding to the mobile request in a DB storing intermediate views of JavaView and MSP views when the mobile engine is called by the mobile engine;
A profile manager for parsing a mobile request transmitted through the mobile engine and obtaining information on a mobile terminal that is a client that has transmitted the mobile request;
When a session is requested from the mobile application executed by the Java view handler and the MSP view handler, a session for the mobile application and the mobile response is generated and managed A session management unit;
A component manager for managing a life cycle of the mobile application executed by the Java view handler and the MSP view handler; And
The Java view handler and the MSP view handler convert the content obtained by executing the mobile application to the mobile terminal, which is a client that has transmitted the mobile request, using the information about the mobile terminal, which is the client,
And a content conversion unit for transmitting the generated content to the mobile engine.
[Claim 2]
The method of claim 1, wherein the mobile request generation unit
A mobile application request receiving unit for receiving an HTTP mobile application request from a plurality of mobile terminals that are clients from a known HTTP web server and storing the socket in a mobile application request queue; And
And an application request processor for generating a mobile application request using the socket stored in the mobile application request queue.
[Claim 3]
The apparatus of claim 1, wherein the session management unit
Wherein a session and a session ID are set in a mobile request and a mobile response so that a session in a mobile request transmitted through the mobile engine can be found and used.
[Claim 4]
The apparatus of claim 1, wherein the session management unit
When the mobile application executed by the Java view handler and the MSP view handler requests a session, it obtains the mobile application name from the mobile application context, which is information about the mobile application stored in the mobile request,
And setting a session and a session ID in a mobile application and a mobile response using a session handler for managing the session.
[Claim 5]
5. The method of claim 4, wherein the session handler
And the session is reused if there is a session already stored in the memory using the storage controller.
[Claim 6]
The method of claim 1, wherein the component management unit
The number of instances stored in the memory increases as the number of mobile application requests increases and the number of unnecessary instances increases as mobile application requests decrease Wherein the life cycle of the mobile bean in each mobile application is managed by a plurality of application management units classified by the mobile application. .
[Claim 7]
The apparatus of claim 1, wherein the content conversion unit
The Java view handler and the MSP view handler using the predefined clipping information, the annotation information indicating the importance according to the type of the mobile terminal, and the device profile information of the mobile terminal,
An annotation processor for selecting a specific content from a mobile response obtained by executing a mobile application and creating a document;
A profile collector for extracting device profile information of a mobile terminal, which is a client found by the profile management unit, and document profile information from a document generated by the annotation processor; And
Performing tag filtering, tag conversion, and document segmentation to cut the document into several pieces according to characteristics of the mobile terminal, using the attribute values in the device profile information and the document profile information, so that the annotation processor
And a profile aggregator for converting a document selected only for specific contents and transmitting the converted document to the mobile engine.
[Claim 8]
Receiving a mobile application request from a plurality of mobile terminals that are clients through a known HTTP web server and converting the received mobile application request into a mobile request;
The mobile application server analyzing a mobile request to search for a mobile application;
Generating a content by executing the mobile application when the mobile application server searches for the mobile application;
Analyzing a mobile request by the mobile application server and determining an attribute of the client;
Analyzing the content generated by the mobile application server and converting the content into a client attribute according to the analyzed client request;
And
And analyzing the mobile request by the mobile application server and transmitting the converted content to the client, to the corresponding client.
KR1020150051945A 2015-04-13 2015-04-13 Mobile Application Server for ios and Android support KR20160121989A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020150051945A KR20160121989A (en) 2015-04-13 2015-04-13 Mobile Application Server for ios and Android support

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020150051945A KR20160121989A (en) 2015-04-13 2015-04-13 Mobile Application Server for ios and Android support

Publications (1)

Publication Number Publication Date
KR20160121989A true KR20160121989A (en) 2016-10-21

Family

ID=57257118

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020150051945A KR20160121989A (en) 2015-04-13 2015-04-13 Mobile Application Server for ios and Android support

Country Status (1)

Country Link
KR (1) KR20160121989A (en)

Similar Documents

Publication Publication Date Title
JP6559802B2 (en) Device identifier dependent operation processing for packet-based data communication
US9009599B2 (en) Technique for handling URLs for different mobile devices that use different user interface platforms
CN111045833B (en) Interface calling method and device
CN102694701A (en) Testing method and system based on message
WO2021023149A1 (en) Method and apparatus for dynamically returning message
CN107766509B (en) Method and device for static backup of webpage
CN112507005B (en) Method and device for processing message
CN111756847B (en) Method and device for supporting https protocol by website
CA3061623C (en) File sending in instant messaging applications
CN111770161B (en) https sniffing jump method and device
WO2021093673A1 (en) E-mail sending method, apparatus and device, and computer-readable storage medium
JP2014505299A (en) Method and apparatus for processing microweb log messages
CN108959294B (en) Method and device for accessing search engine
KR100461730B1 (en) Mobile application server for various mobile devices
CN113127335A (en) System testing method and device
CN102957749B (en) A kind of for providing the method for information, device and equipment
CN114896244A (en) Method, device and equipment for configuring database table and computer readable medium
CN102130842A (en) Instant communication method, device and system
KR20160121989A (en) Mobile Application Server for ios and Android support
CN110740046B (en) Method and device for analyzing service contract
CN113779018A (en) Data processing method and device
CN110866002B (en) Method and device for processing sub-table data
CN104794165A (en) Page display method, device and system
CN112650601B (en) Method, apparatus, device, storage medium, and program for opening applet across hosts
JP2002342213A (en) Method of providing contents