KR20090011150A - System and method for installing application, and mobile communication terminal used therein - Google Patents

Abstract

An application installation system, a method thereof, and a mobile communications terminal for sharing a class module used in a java application are provided to minimize that the same class modules are stored in the mobile terminal. A mobile terminal is connected to a server according to an application obtaining request(S10-S13). A JAD file corresponding to the application is downloaded from the server(S14). It confirms whether to include the common class module through the JAD file(S15). In case application includes the common class module, it is confirmed whether the common class module is already stored(S16,S17). If the common class module is already stored, the JAR file corresponding to application is downloaded(S18-S20).

Description

System and method for installing application, and Mobile communication terminal used therein}

The present invention relates to an application installation system and method that can commonly use class modules commonly included in a plurality of Java applications, and a mobile communication terminal used therein.

In general, a mobile communication terminal is a personal mobile communication services terminal, a personal digital assistant (PDA), a smart phone, a next generation mobile communication terminal (International Mobile Telecommunication 2000: IMT-). 2000), and refers to a terminal that can be implemented by a person, such as a wireless LAN terminal, and implement various functions using application programs including wireless communication.

Recently, with the development of the Internet and multimedia data technology, a content provider (CP) that provides various contents such as multimedia communication, network games, and video games has emerged. There is an increasing number of mobile subscribers who want to use applications of various services.

One such application, the Java MIDlet (hereinafter, referred to as a middlelet) collectively refers to applications written according to the Mobile Information Device Profile (MIDP) standard, becomes a component of the Java 2 Micro Edition (J2ME) execution environment. This middlelet is designed to operate in a mobile communication terminal, and is executed and controlled by a Java virtual machine.

In a mobile communication terminal, a middlelet generally consists of a Java Application Descripotor (JAD) file that lists information about the middlelet, and a compressed Java Archive (JAR) file of class modules describing commands. do.

On the other hand, the middlelets released by a communication provider or a content provider (CP) include a class module (hereinafter, referred to as a common class module) designed to be commonly used to support the same user interface (UI) or the same function in many cases.

These common class modules are included in each JAR file of the corresponding middlelet if they are not stored in the OEM form in the mobile communication terminal or not in the J2ME standard. However, the mobile communication terminal has a limited downloadable size (or available memory size). Therefore, there is a problem in that memory resources are wasted when the same classes are repeatedly stored in multiple middlelets. In addition, if you need to upgrade a commonly used class module, it is inconvenient to upgrade all the middlelets that include the common class module, respectively.

Accordingly, an object of the present invention is to solve the problems of the prior art as described above, to provide an application installation system and method that can be used in common to a common class module in a number of applications, and to provide a mobile communication terminal used therein There is.

Application installation method of a mobile communication terminal according to the present invention for achieving the above object is a process of connecting to the server according to the application acquisition request, downloading the JAD file corresponding to the application from the server, through the JAD file Checking whether the common class module of the application is included; if the application includes the common class module; checking whether the common class module is already stored; and if the common class module is already stored And downloading a JAR file corresponding to the application.

In addition, the mobile communication terminal according to the present invention analyzes a connection processing unit for accessing a server according to an application acquisition request, a file processing unit for obtaining a JAD file and a JAR file corresponding to the application in the server, and the obtained JAD file And a common class module processing unit for checking whether the common class module is included in the application and acquiring the common class module from the server when there is no pre-stored common class module according to a check result.

In addition, the application installation method according to the present invention, the mobile terminal is connected to the server via the network in response to the application acquisition request, a JAD file transmission process of transmitting a JAD file corresponding to the application to the mobile terminal,

A process of acquiring a common class module for analyzing the JAD file transmitted by the mobile communication terminal and acquiring a common class module in response to the analysis result, and transmitting a JAR file in which a JAR file corresponding to the application is transmitted to the mobile communication terminal It characterized in that it comprises a process.

In addition, the application installation system according to the present invention is a server for providing a JAD file, a common class module and a JAR file corresponding to the application in accordance with an application request, and access the server to obtain the JAD file and JAR file, And a mobile communication terminal for acquiring the common class module corresponding to the analysis result by analyzing the JAD file.

An application installation system and method according to the present invention, and a mobile communication terminal used therein, separately generate and use a common class module commonly used by a plurality of middlelets. Therefore, since the same class modules can be minimized to be repeatedly stored in the mobile communication terminal, the capacity of the storage unit can be used more efficiently. In addition, when the upgrade of the common class module is required, it is possible to minimize the time required for the upgrade because only the common class module can be upgraded without upgrading all the middlelets as in the prior art.

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

Prior to the description of the present invention, the terms or words used in the specification and claims described below should not be construed as being limited to the ordinary or dictionary meanings, and the inventors should consider their own invention in the best way. For the purpose of explanation, it should be interpreted as meaning and concept corresponding to the technical idea of the present invention on the basis of the principle that it can be appropriately defined as the concept of term. Therefore, the embodiments described in the present specification and the configuration shown in the drawings are only the most preferred embodiments of the present invention, and do not represent all of the technical idea of the present invention, and various equivalents may be substituted for them at the time of the present application. It should be understood that there may be water and variations.

On the other hand, the application (application) described in this embodiment refers to all the application programs stored and executed in the mobile communication terminal, and more specifically refers to the Java MIDlet (Java MIDlet).

Hereinafter, in describing the embodiments, descriptions of technical contents which are well known in the technical field to which the present invention belongs and are not directly related to the present invention will be omitted. In addition, detailed description of components having substantially the same configuration and function will be omitted.

For the same reason, some components in the accompanying drawings are exaggerated, omitted, or schematically illustrated, and the size of each component does not entirely reflect the actual size.

1 is a block diagram schematically illustrating an application installation system according to an embodiment of the present invention.

Referring to FIG. 1, the application installation system 10 according to the present invention downloads an application (or middlelet; MIDlet) that the mobile communication terminal 100 wants to acquire from an application server 50 (hereinafter referred to as a server). A method of storing in 100 is used.

Here, the middlelet according to the present invention includes a JAD file, a JAR file, and a common class module. A JAD file is a file that lists information about the middlelet. A JAR file is a file in which class modules describing commands are compressed. Also, a common class module is a file in which class modules are compressed in the same way as a JAR file. However, a common class module refers to a file in which a plurality of class modules commonly used in one or more middlelets are compressed, not a class module used only in one specific middlelet. do. Therefore, the JAR file according to the present invention is composed of only the class modules other than the class modules included in the common class module.

The server 50 according to the present embodiment is generally constructed by a communication provider or a content provider (CP), and according to a request of the mobile communication terminal 100, the corresponding middlelet, that is, a JAD file, a JAR file, and a common class module. To transmit to the mobile communication terminal (100).

The wireless communication network 20 is used as a path for the mobile communication terminal 100 to access the server 50 to download the middlelet. That is, the mobile communication terminal 100 accesses the over-the-air server 60 through the wireless communication network 20, and connects to the server 50 providing the corresponding application to the server 50 via the wireless communication network 20. Will communicate.

The mobile communication terminal 100 accesses the server 50 according to a user's request, downloads and stores a middlelet, and executes the middlelet on the mobile communication terminal 100 according to a user's execution request. Looking at the mobile communication terminal 100 according to an embodiment of the present invention in more detail as follows.

2 is a block diagram schematically illustrating a structure of a mobile communication terminal according to an embodiment of the present invention.

2, the mobile communication terminal 100 according to the present embodiment includes a wireless communication unit 130, an audio processing unit 140, a key input unit 160, a display unit 150, a storage unit 170, and a controller ( 190).

The wireless communication unit 130 performs a function of transmitting and receiving corresponding data for wireless communication of the mobile communication terminal 100. The wireless communication unit 130 may include an RF transmitter for upconverting and amplifying a frequency of a transmitted signal, and an RF receiver for low noise amplifying and downconverting a received signal. In addition, the wireless communication unit 130 may receive data through a wireless channel, output the data to the controller 190, and transmit data output from the controller 190 through a wireless channel.

The audio processor 140 includes a coder (Coder / Decoder). The codec may include a data codec for processing packet data and the like and an audio codec for processing an audio signal such as voice. Therefore, the audio processor 140 converts the digital audio data received by the controller 190 through the wireless communication unit 130 into an analog audio signal through an audio codec and outputs the speaker to the speaker, and the analog audio signal input from the microphone. Is converted into digital audio data through an audio codec and provided to the controller 190.

The display unit 150 visually provides a menu of the mobile communication terminal 100, user data input by the user, function setting information, and various information to the user. The display unit 150 may be formed of a liquid crystal display (LCD). In this case, the display unit 150 may include a control device for controlling the liquid crystal display, a video memory capable of storing image data, an element of the liquid crystal display, and the like. Meanwhile, when the LCD is implemented by using a touch screen method, the screen of the display unit 150 may be operated as an input unit.

The key input unit 160 receives a user's operation signal for controlling the mobile communication terminal 100 and transmits it to the controller 190. To this end, the key input unit 160 according to the present exemplary embodiment includes a control key (not shown) for operation control and a plurality of numeric keys (not shown) for inputting letters and numbers.

The storage unit 170 stores an application program required for operating a function according to an exemplary embodiment of the present invention, content to be downloaded, and user data generated by the user. The storage unit 170 may include a data area and a program area.

The data area is an area in which user data according to the use of the mobile communication terminal 100 is stored, and digital content data (eg, a music file, a video file, etc.) may be stored.

The program area may be an application required for an operating system (OS) for booting the mobile communication terminal 100, other options of the mobile communication terminal 100, for example, a music play function, an image or video play function, and the like. Save the program. When activating each function according to a user request, each function is provided through corresponding application programs under the control of the controller 190. In addition, the storage unit 170 may temporarily store user data (music file, still image, video) generated during the execution of an application program according to a playback function such as music, video, or the like. May contain a buffer.

In addition, the program area of the storage unit 170 according to the present exemplary embodiment stores a middlelet, that is, an application transmitted from the server 50, that is, a JAD file, a JAR file, and a common class module.

The controller 190 controls the overall operation of the mobile communication terminal 100 and the signal flow between the internal blocks of the mobile communication terminal 100. That is, the control unit 190 may be configured between the components of the mobile communication terminal 100 including the wireless communication unit 130, the audio processing unit 140, the display unit 150, the key input unit 160, and the storage unit 170. Control signal flow.

The controller 190 performs each function of the mobile communication terminal 100 according to an input signal input from the key input unit 160, and displays information such as a current state and a user menu according to the performance of the function through the display unit 150. Display.

In addition, the controller 190 according to an embodiment of the present invention accesses the server 50 in accordance with the application acquisition request to obtain files corresponding to the corresponding middlelet. To this end, the controller 190 according to the present exemplary embodiment includes a connection processor 192, a file processor 194, and a common class module processor 196.

When the application acquisition request is input from the user, the access processing unit 192 accesses the server 50 that provides the corresponding midlet through the wireless communication unit 130.

The file processor 194 obtains a JAD file and a JAR file corresponding to the middlelet selected by the user, and stores the JAD file and the JAR file in the storage unit 170.

The common class module processor 196 analyzes the JAD file acquired by the file processor 194 and checks whether the corresponding middlelet uses the common class module. When the common class module is used according to the check result, it is checked whether the common class module exists in the storage unit 170. If the check result does not exist, the common class module is obtained from the server 50 and stored in the storage unit 170.

Next, the application installation method according to the present invention will be described in detail with reference to the following embodiments. The configuration of the above-described application installation system 10 will also be clearer from the following description of the application installation method.

3 is a flowchart schematically illustrating an application installation method according to an embodiment of the present invention, and FIG. 4 is a diagram schematically showing a JAD file according to an embodiment of the present invention.

1 to 4, the method for installing an application according to the present embodiment is first performed from step S10 in which power is supplied to the mobile communication terminal 100 and enters an idle state according to a normal operation.

Next, a process S11 is performed in which an application acquisition request is received by the mobile communication terminal 100 in the standby state. Herein, the application acquisition request refers to a request for the user to download the middlelet to the mobile communication terminal 100 in order to execute a specific middlelet in the mobile communication terminal 100. Meanwhile, a process for charging (user authentication, etc.) may be included in the process of downloading the middlelet. However, this process is already known technology and is not directly related to the present invention, a description thereof will be omitted.

When the application acquisition request is received, the connection processing unit 192 of the controller 190 performs an S13 process of accessing the server 50 providing the corresponding midlet. In the present embodiment, when the application acquisition request is received from the user for convenience of description, the case in which the server 50 is connected is described as an example. However, the present invention is not limited thereto, and first accesses the server 50 according to a user's request, and then displays the information provided by the server 50 (such as obtainable middlelet information) to the user, thereby allowing the user to select a specific application. Various applications are possible, such as selecting one.

In addition, in the present embodiment, the connection processing unit 192 will be described as an example of connecting to the server 50 for providing an application via the OTA server 50 through the wireless communication unit 130. However, the present invention is not limited thereto, and various applications are possible, such as accessing the server 50 through a wired communication network.

When the mobile communication terminal 100 is connected to the server 50 through the S13 process, after the mobile communication terminal 100 downloads the JAD file, the process S14 is performed. First, the file processor 194 of the mobile communication terminal 100 requests the server 50 to transmit the corresponding middlelet. Accordingly, the server 50 first transmits the JAD file of the corresponding middlelet to the mobile communication terminal 100.

The JAD file according to the present embodiment includes various information about the corresponding middlelet. Referring to FIG. 4, the JAR file corresponding to the middlelet through the MIDlet-Name field, the MIDlet-jar-URL field, and the like is an 'example.jar' file, and the file 'http://tnb.samsung.com/jar'. You can see that it is located at '/example.jar'.

In addition, the JAD file according to the present embodiment includes common class module related fields.

Common class module related fields according to the present embodiment are fields indicating whether a common class module is used (MIDlet-common-Class field) and fields indicating a URL address of a common class module (MIDlet-common-Class-URL field). ), And a field indicating the version of the common class (MIDlet-common-Class-version field). In the case of the JAD file illustrated in FIG. 4, the common class module used by the corresponding middlelet is 'CommonClass.jar', and the URL address for obtaining such a common class module is 'http://tnb.samsung' '.com / com / common.jar'.

These common class module related fields are not always defined, only when the corresponding middlelet uses the common class module. Therefore, when the JAD file is transmitted from the server 50, the common class module processing unit 196 of the mobile communication terminal 100 analyzes the JAD file to determine whether the common class module is used in the corresponding middlelet. Will be performed.

In the present embodiment, a case in which a common class module is defined using a plurality of common class module related fields is described as an example, but is not limited thereto. That is, various applications are possible such that the contents of all the above fields are included in one common class module related field as follows.

'MIDlet ?? common ?? Class ?? URL: 2.0.0, http://tnb.samsung.com/com/common.jar'

4 illustrates an example in which only one common class module (eg, common.jar) is defined in the JAD file. However, it is also possible to define multiple common class modules as needed.

As a result of the analysis in step S14, when common class module related fields are not defined in the JAD file (S15), the common class module processing unit 196 recognizes that the corresponding middlelet is a middlelet that does not use the common class module. Therefore, the process proceeds to S20 to obtain the JAR file of the middlelet.

On the other hand, when common class module related fields are defined in the JAD file, the common class module processing unit 196 performs an operation S16 of checking whether the corresponding common class module is stored in the storage unit 170. This is to check whether a common class module (eg, common.jar) defined in a JAD file is included among the common class modules previously stored in the storage unit 170. In this process, the common class module processor 196 checks the name of the common class module (for example, common.jar) and the version information (for example, 2.0.0) and stores the common class module defined in the JAD file. Check if it is the same as common class module.

As a result of the check, if the common class module defined in the JAD file is stored in the storage unit 170 (S17), it is not necessary to repeatedly acquire the common class module. Therefore, in this case, the common class module processor 196 skips the process of acquiring the common class module and enters S20 which is a process of acquiring the JAR file.

On the other hand, if there is no common class module defined in the JAD file in the storage unit 170 (S17), the common class module processing unit 196 performs the process S18 to obtain the corresponding common class module. That is, the common class module processor 196 requests a common class module (eg, common.jar) from the server 50, and accordingly, the server 50 transmits the common class module to the mobile communication terminal 100. This is going on.

In the above process, when there are a plurality of common class modules defined in the JAD file, the common class module processing unit 196 acquires and stores all defined common class modules.

At this time, the common class module is stored in another location (separate folder, etc.) to distinguish it from other general JAR files. This is for easier management such as updating or searching for common class modules. However, it is not limited thereto.

If all the common class modules required for the corresponding middlelet are stored in the storage unit 170 through the above process (S19), then the process S20 of obtaining a JAR file corresponding to the middlelet is performed.

In operation S20, the file processor 194 requests a JAR file from the server 50, and the server 50 transmits the corresponding JAR file to the mobile communication terminal 100.

When the file processing unit 194 stores the transferred JAR file in the storage unit 170 (S21), the connection processing unit 192 performs an S22 process of releasing the connection with the server 50, and then ends the application installation process. do.

When the middlelet is installed in the mobile communication terminal 100 through the above-described process, the user can execute the installed middlelet on the mobile communication terminal 100 through an input of an execution request. The process of executing the middlelet first analyzes the JAD file and executes the middlelet by loading the corresponding common class module and the JAR file.

Meanwhile, the common class module according to the present embodiment may be shared by one or more middlelets. Therefore, even if the user deletes one of the middlelets using the common class module, if the other middlelet uses the same common class module, the corresponding common class module is not deleted and is still used.

As described above, the application installation system and method according to the present invention, and the mobile communication terminal used therein separately generates a common class module commonly used by a plurality of middlelets to use it. Therefore, since the same class modules can be minimized to be repeatedly stored in the mobile communication terminal, the capacity of the storage unit can be used more efficiently. In addition, when the upgrade of the common class module is required, it is possible to minimize the time required for the upgrade because only the common class module can be upgraded without upgrading all the middlelets as in the prior art.

Application installation system and method according to the present invention as described above, the mobile communication terminal used therein is not limited to the embodiment, various modifications are possible by those skilled in the art within the technical idea of the present invention. . For example, in the present embodiment, a method of acquiring a JAR file after acquiring a common class module is used. However, the present invention is not limited thereto. It is also possible to acquire a common class module after acquiring a JAR file first. In addition, in the present embodiment, a case of installing and executing a Java application has been described as an example. However, the present invention is not limited thereto and may be widely applied to all kinds of applications using a common module.

In addition, the present embodiment exemplifies a case in which an application is installed and executed in a mobile communication terminal. However, in addition to this, any electronic device that can download and use an application from a server can be variously applied.

1 is a block diagram schematically illustrating an application installation system according to an embodiment of the present invention.

2 is a block diagram schematically showing the structure of a mobile communication terminal according to an embodiment of the present invention;

3 is a flowchart schematically illustrating a method for installing an application according to an embodiment of the present invention.

4 schematically illustrates a JAD file according to an embodiment of the present invention.

Claims (19)

An access procedure for accessing a server according to an application acquisition request; A JAD file acquiring process for downloading a JAD file corresponding to the application from the server, JAD file verification process for checking whether the common class module of the application through the JAD file, When the application includes the common class module, a process of checking a common class module to determine whether the common class module is pre-stored, If the common class module is pre-stored, the method of installing an application of a mobile communication terminal comprising the step of obtaining a JAR file for downloading a JAR file corresponding to the application. The method of claim 1, wherein the common class module, An application installation method of a mobile communication terminal, characterized in that the at least one or more of the application is a class module commonly used. The method of claim 2, wherein the JAR file, Application installation method of a mobile communication terminal, characterized in that the file does not include the common class module. The method of claim 2, wherein the JAD file, And a field indicating whether or not the common class module is included and a field indicating a URL address of the common class module. The method of claim 4, wherein the JAD file, And a field indicating version information of the common class module. The method of claim 2, wherein if there is no common class module previously stored in the common class module check process, The method of claim 1, further comprising downloading and storing the common class module. A connection processing unit which accesses a server according to an application acquisition request; A file processing unit for obtaining a JAD file and a JAR file corresponding to the application in the server, and And analyzing the acquired JAD file to determine whether the common class module is included in the application, and if there is no previously stored common class module according to a check result, including a common class module processing unit for obtaining the common class module from the server. Mobile communication terminal, characterized in that. The method of claim 7, wherein the common class module, Mobile communication terminal, characterized in that the at least one class module commonly used by the application. The method of claim 8, wherein the JAR file, Mobile communication terminal, characterized in that the file does not include the common class module. The method of claim 8, wherein the JAD file, And a field indicating whether or not the common class module is included and a field indicating a URL address of the common class module. The method of claim 8, And a storage unit for storing the JAD file, the JAR file, and the common class module. An access process of a mobile communication terminal accessing a server through a network according to an application acquisition request; A JAD file transmission process of transmitting a JAD file corresponding to the application to the mobile communication terminal; A process of acquiring a common class module for analyzing the JAD file transmitted by the mobile communication terminal and acquiring a common class module in response to an analysis result; And a JAR file transfer process in which a JAR file corresponding to the application is transmitted to the mobile communication terminal. The method of claim 12, wherein the common class module, An application installation method, characterized in that the at least one class module commonly used by the application. The method of claim 13, wherein the obtaining of the common class module comprises: Checking whether the application includes a common class (class) module through the JAD file, If the common class module is included, checking whether the common class module is pre-stored, and If there is no pre-stored common class module, the method comprising the step of transmitting the common class module from the server. The method of claim 14, wherein the JAD file, And a field indicating whether or not the common class module is included and a field indicating a URL address of the common class module. A server providing a JAD file, a common class module, and a JAR file corresponding to the application according to an application request; And a mobile communication terminal accessing the server to obtain the JAD file and the JAR file, and analyzing the JAD file to obtain the common class module in response to an analysis result. The method of claim 16, wherein the common class module, Application class system, characterized in that the at least one application is a class module commonly used. The method of claim 17, wherein the mobile communication terminal, The JAD file is analyzed to determine whether the common class module is included in the application. When the application includes the common class module, the common class module is pre-stored. And if there is no module, obtaining the common class module from the server. The method of claim 17, wherein the JAD file, And a field indicating whether or not the common class module is included and a field indicating a URL address of the common class module.

Images