KR101240096B1 - Management method for java application in mobile communication terminal - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

The present invention relates to a Java application of a mobile communication terminal.

2. The technical problem to be solved by the invention

The present invention distinguishes between a general folder and a Java application which is an execution unit in a mobile communication terminal, and manages the Java application as a physical physical file structure to move the Java applications to the mobile communication terminal and the external memory without going through an intermediate step. The present invention provides a method of managing a Java application of a mobile communication terminal, which enables the mobile terminal to restore a Java application to a state in which the mobile application is inter-moveable when the power of the mobile terminal is cut off during mutual movement to an external memory. has exist.

3. Summary of the Solution of the Invention

The present invention provides a method for managing a Java application of a mobile communication terminal, the process of inputting a folder from a network or an external memory to the mobile communication terminal, and a process of checking whether the input folder is a Java application. And, as the input folder is identified as a Java application, attaching a specific identifier after the name of the Java application, physically distinguishing from the general folder, and performing a predetermined function.

4. Important uses of the invention

The present invention is used for the Java application management method of the mobile communication terminal.

 Mobile Terminals, Java Applications, Management, Folders

Description

MANAGEMENT METHOD FOR JAVA APPLICATION IN MOBILE COMMUNICATION TERMINAL}

1A is an exemplary diagram illustrating a file structure in which a conventional Java application is stored.

FIG. 1B is an exemplary diagram showing file contents in a Java application in FIG. 1A; FIG.

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

3 is a flowchart illustrating a process of distinguishing a general folder from a Java application according to an embodiment of the present invention.

4 is an exemplary diagram illustrating a file structure in which a general folder and a Java application are physically divided according to an embodiment of the present invention.

5 is a view illustrating an exemplary embodiment of a general folder and a Java application in a mobile communication terminal according to an embodiment of the present invention.

6A to 6B are exemplary views illustrating menus when a general folder and a Java application of FIG. 5 are selected.

7 is a flowchart illustrating a process of changing a file structure of a general folder and a Java application according to an embodiment of the present invention.

8 is a flowchart illustrating a process of recovering a file when power is cut off while a file structure of a Java application is changed according to an exemplary embodiment of the present invention.

The present invention relates to a Java application of a mobile communication terminal, and more particularly, to a Java application management method of a mobile communication terminal that physically distinguishes a Java application from a general folder.

Recently, the functions of mobile communication terminals are diversifying. Accordingly, in addition to voice call processing, which is a function of a mobile communication terminal, additional functions such as SMS transmission, phone book, schedule management, calculator, phone book, and game, and internet browsing are added. It is used.

These functions are determined and released in advance from the production of the mobile communication terminal, and similar functions and different functions are classified according to the model of the mobile communication terminal and thus cannot satisfy the different tastes of users using the mobile communication terminal. .

In order to improve such disadvantages, a platform for providing a dynamic environment for a mobile terminal such as a GVM (General Virtual Machine) application, a JAVA application, and a BREW binary application environment (BREW) application. ) Is being developed.

The GMB application and the Brew application are in C language, and the Java application can be stored in the user's mobile terminal using the application application written in the Java language through the data service of the mobile terminal. Programs include games, location information, securities, karaoke, and e-books.

The largest user base among these platforms is the Java application platform, and the latest mobile communication terminal supports the Java application platform by default. Downloading and running Java applications is done through the following process.

Select a Java application link from a server on a network using a browser of a mobile communication terminal, run a Java Application Manager program (JAM), and download a Java Application Manager file (JAD) from the server. .

The contents of the Java application manager file are analyzed to determine the location of the Java application file existing on the network. The Java application file is downloaded to the mobile terminal and stored in the storage area of the mobile terminal.

The application is run by running a Java virtual machine to execute Java application files using the Java application manager program.

Meanwhile, the execution unit of the Java application stored in the mobile communication terminal through the network is not a file but a folder. Therefore, there is no physical distinction between a folder containing general files or applications and a Java application that is a unit of execution.

1A is an exemplary diagram illustrating a file structure in which a conventional Java application is stored, and FIG. 1B is an exemplary diagram illustrating file contents in a Java application in FIG. 1A.

As shown in FIG. 1A, a conventional Java application is physically identical to a regular folder. These folders are the actual unit of execution for Java applications. In this case, the folder (Folder) is an English name, also called a file folder (File Folder), and refers to a place for easily storing files.

FIG. 1B shows the file contents in a folder of the "Frogger" Java application of the Java application shown in FIG. 1A.

As shown in FIG. 1B, the "Frogger" Java application is composed of Frogger.jad, Frogger.jar files, gameicon.png, and i.png image files.

As such, in the related art, a general folder containing a general file and a Java application, which is an execution unit, are physically identical and cannot be distinguished from each other.

Accordingly, the conventional mobile communication terminal logically distinguishes a Java application from a general folder. However, performing such functions as creating, moving, copying, and renaming regular folders and moving, copying, and renaming Java applications did not change physically, but only logically.

In fact, after performing the functions mentioned above, if you look at the file structure of regular folders and Java applications in the storage area, there is no physical change.

In other words, even if the file path name or name is changed, the physical path name and name are not changed. Only the logical management files that manage regular folders change.

In addition, in the conventional mobile communication terminal, when managing Java applications, Java applications and general folders are logically managed, so that files and folders may be managed in some way without knowing the unique logical structure applied to a specific mobile communication terminal. I don't know if it's managed.

Therefore, when Java applications are stored in an external memory such as a universal serial bus (USB) memory or a multi-media card (MMC), they cannot be used in a conventional mobile communication terminal. In order to use Java applications in a conventional mobile communication terminal, first, whenever an external memory such as a USB memory or an MMC is connected to the mobile communication terminal, Java applications stored in the external memory are changed into a physical structure used in the mobile communication terminal. Only when the Java file is moved between the external memory and the mobile terminal, the Java applications can be used in the mobile terminal.

Alternatively, the mobile terminal creates a new law for a Java application stored in an external memory and generates a logical file for it, each time the mobile terminal is connected to the external memory, a logical file is generated, and each time the connection is released. When the logical file is deleted, Java applications can be moved between the external memory and the mobile communication terminal so that the Java applications can be used in the mobile communication terminal.

However, both of the above methods have a problem that they are inefficient by using Java applications stored in an external memory in the mobile communication terminal.

The present invention has been proposed to solve the above problems, and distinguishes a Java application which is a general folder from an execution unit in a mobile communication terminal, manages a Java application in a physical physical file structure, and manages the Java application with the mobile communication terminal. When moving to external memory, it is possible to move without going through an intermediate step, and when the power of the mobile communication terminal is cut off while moving to external memory, the mobile communication is restored to a state capable of performing mutual movement again. The purpose is to provide a Java application management method of the terminal.

According to an aspect of the present invention, there is provided a Java application management method of a mobile communication terminal, the process of inputting a folder from a network or an external memory to the mobile communication terminal, and the input folder is a Java application ( Java application), and as the input folder is identified as a Java application, attaching a specific identifier after the name of the Java application, physically distinguishing it from a general folder, and performing a predetermined function. .

Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings. In addition, in describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

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

Referring to FIG. 2, the mobile communication terminal includes a display unit 201, a key input unit 202, a transceiver 203, a storage unit 204, a control unit 205, a voice processing unit 206, and a connection unit 207. do.

Looking at the configuration of the mobile communication terminal in more detail, first, the connection unit 207 connects the mobile communication terminal and the external memory. In an embodiment of the present invention, the mobile communication terminal is connected to the external memory through the connection unit 207 to perform functions such as moving, copying, and renaming a Java application stored in the external memory.

Here, the external memory includes a universal serial bus (USB) memory or a multi-media card (MMC). The connection unit 207 may be formed of a USB connector (Universal Serial Bus Connector) and a serial connector (Serial Connector). If a short range wireless communication module such as Bluetooth is provided in the mobile communication terminal and the external memory, the mobile communication terminal and the external memory are wirelessly connected to perform functions such as moving, copying, and renaming Java applications stored in the external memory. can do.

The display unit 201 may be formed of a liquid crystal display (LCD) or the like, and displays a receiver's telephone number, a caller's telephone number, image data, text data, and the like. In addition, the display unit 201 displays the general folder and the Java application under the control of the control unit 205 in the embodiment of the present invention, and displays the general folder and the menu of the Java application according to the user's selection.

The key input unit 202 has a key matrix structure (not shown) and includes a character key, numeric keys, and various function keys to output a key input signal corresponding to a key input by a user to the controller 205.

The transceiver 203 receives a call from the outside or attempts to connect a call. The transceiver 203 transmits various data to the mobile communication system through an antenna under the control of the controller 205 and controls the data received from the mobile communication system. Forward to 205. In an embodiment of the present invention, the transceiver 203 receives a Java application from a server on a network and delivers it to the controller 205.

The storage unit 204 stores information for distinguishing a general folder and a Java application that is an execution unit from the mobile communication terminal and the external memory according to an embodiment of the present invention, and various information necessary for controlling the operation of the mobile communication terminal. The Java application received through the transceiver 203 and the Java application stored in the external memory are received from the controller 205 and stored therein.

The controller 205 is a block for processing and controlling functions such as a telephone call, data communication, and a message service of a mobile communication terminal. The controller 205 processes a function for managing a Java application according to the present invention in addition to a normal function.

When the folder is input from the network or the external memory, the controller 205 checks whether the input folder is a Java application. If the checked folder is a Java application, the Java application name is followed by a specific identifier (.jav) to control the general folder from the Java application.

In addition, the controller 205 is connected to the external memory, and when the power of the mobile communication terminal is cut off during the mutual movement between the external memory and the mobile communication terminal controls to restore the Java application to a state capable of performing mutual movement again. .

In addition, the conventional mobile communication terminal is configured to further include a voice processing unit 206 for inputting and outputting voice information through a microphone and a speaker.

3 is an operation flowchart illustrating a process of distinguishing a general folder from a Java application according to an embodiment of the present invention.

Referring to FIG. 3, the controller 205 of the mobile communication terminal is in the standby mode in step 301. If a folder is input from the network or an external memory (302), the controller 205 checks whether the input folder is a Java application (303). In this case, the controller 205 checks whether a folder input from the network or external memory is a general folder or a Java application, and searches whether there is a “.jar” or “.jad” file among the files in the folder input from the network or the external memory. Thus, if there is a ".jar" or ".jad" file, the input folder is a method of confirming that the Java application.

If the input folder is identified as a Java application (304), the control unit 205 attaches a specific identifier (.jav) to the Java application to distinguish it from the general folder (305). If the folder identified in step 303 is identified as a general folder instead of a Java application, the controller 205 does not attach a specific identifier (.jav) to the general folder.

Through this method, the mobile terminal physically distinguishes between a general folder and a Java application among folders input from a network or external memory.

4 is an exemplary diagram illustrating a file structure in which a general folder and a Java application are physically divided according to an embodiment of the present invention.

When a folder is input to a mobile communication terminal from a network or an external memory, the controller 205 checks whether the input folder is a Java application, and if the inputted folder is a Java application, as shown in FIG. A special identifier (.jav) is added to distinguish general folders 401 from Java applications 402.

Referring to FIG. 4, the general folders 401 "abc" and "Gaj" are not attached with a specific identifier (.jav). The Java applications 402, "Caveman.jav", "Gradius.jav", and "PuzzleBobble.jav", have a specific identifier (.jav) attached to distinguish the general folder 401 and the Java applications 402. .

5 is a diagram illustrating an embodiment of a screen showing a general folder and a Java application in a mobile communication terminal according to an embodiment of the present invention.

5 shows a screen for a user to search the contents of the folder "dmv3" stored in the storage unit 204 in the mobile communication terminal. The user searches the contents of the "dmv3" folder by using an input key provided in the mobile communication terminal.

The control unit 205 recognizes the folders 502 attached with a specific identifier (.jav) as a Java application, displays them as a file on the screen of the mobile communication terminal, and moves, deletes, copies, or renames the Java application. In Java application, it functions like a file.

Folders 501 that do not have a specific identifier (.jav) attached are recognized as general folders and perform a function on a folder when moving, deleting, copying, or renaming.

In addition, the general folder 501 indicates the number of folders 503 and the number of documents 504 in the "dmv3" folder. The user can check the contents of the general folder 501 displayed on the screen, so that the number of folders and the number of documents 504 in the general folder 501 can be checked.

6A to 6B are exemplary screen diagrams illustrating menus when a general folder and a Java application of FIG. 5 are selected.

6A illustrates a menu when a user selects a general folder from a "dmv3" folder of a mobile communication terminal. As shown in Fig. 6A, menus of general folders include "1. Open", "2. Create folder", "3. Rename folder", "4. Move to", "5. Copy to", "6. Delete folder "is a menu used when using a general folder.

The user may perform a function of creating, moving, deleting, copying, or renaming a general folder by using the illustrated menu.

6B illustrates a menu when a user selects a Java application in the "dmv3" folder of the mobile communication terminal. As shown in Fig. 6B, the Java application menu includes "1. Start", "2. Create folder", "3. Move to", "4. Copy to", "5. Sort by", "6. Rename". ", Which consists of menus used when using Java applications.

The user can perform functions such as starting, moving, copying, and renaming a Java application using the illustrated menu.

When the user requests a change in the file structure, such as moving, deleting, or renaming, from the menu of a Java application, the physical file structure is actually changed.

7 is a flowchart illustrating a process of changing a file structure of a general folder and a Java application according to an exemplary embodiment of the present invention.

Referring to FIG. 7, the mobile communication terminal is connected to an external memory (701). When the user renames, moves, or copies the general folder stored in the mobile terminal and the external memory and the Java application by the user's input (702), the control unit 205 controls the general folder stored in the mobile terminal and the external memory. A startup notification file is generated 703 indicating that the execution of the rename, move, and copy functions of the Java application has started.

When the controller 205 generates a start notification file indicating that the name of the general folder and the Java application has been started for the rename, move, and copy functions, the controller 205 generates a target file generated by renaming, moving, or copying the original file. Create 704. Here, the target file refers to a new file that is changed from the original file to be changed. When the target file is generated, the controller 205 adds the generated target file to the database (DataBase) of the storage unit 204 (705).

When the database addition of the generated target file is completed, the controller 205 generates a completion notification file indicating that the database addition of the generated target file is completed, and deletes the start notification file generated in step 703 (706).

On the other hand, in step 706, since it is not necessary to delete the source files when performing the copy function of the general folder and the Java application, the process after step 706 is omitted when performing the copy function.

In the case where the rename and move function is performed, when the generated start notification file is deleted, the controller 205 deletes the target file added to the database and generates a database deletion completion notification file (707). When the database deletion completion notification file is generated, the control unit 205 deletes the source file and the completion notification file, and deletes the database deletion completion notification file (708).

Through this process, when there is a request for a name change, move, or copy function for a general folder and a Java application stored in a mobile communication terminal and an external memory, the physical file structure can be changed.

In addition, as mentioned above, the execution unit of the Java application stored in the mobile communication terminal and the external memory is a folder. Therefore, if the power is cut off while changing the file structure such as renaming, moving, or copying, it should be restored to a functioning state again. This is because, if the power is cut off while changing the contents of the Java application, it is necessary to manage files by synchronizing with unchanged or changed files, and synchronize with the database. This process is shown in FIG.

8 is a flowchart illustrating a process of recovering a file when power is cut off while a file structure of a Java application is changed according to an exemplary embodiment of the present invention.

As described above, the process of changing the structure of the Java application is largely composed of four steps. The steps include, first, generating a target file, adding the generated target file to the database, and adding the target file to the database. Is completed, deleting the database and deleting the source file. If each step is powered off while performing the file restructuring function, a notification file such as a start notification file, a completion notification file, and a database deletion notification file required for each function (rename, delete, move) for the normal recovery of the Java application. Create them. The generated notification file is restored to a state capable of changing the file structure again when the power is supplied again, and is used for synchronization with the database.

Referring to FIG. 8, when a Java explorer execution signal is input from a user, the controller 205 enters a Java explorer to execute Java explorer (801). If the controller 205 enters the Java explorer, before executing the Java explorer, the controller 205 searches for the notification file (802). The notification file retrieved by the controller 205 may include a start notification file indicating that a Java application has been renamed, moved, and copied, and a completion notification file indicating that each function is completed, and a database deletion completion indicating a database deletion is completed. It consists of a notification file.

If the search result notification file of the notification file of the controller 205 is not confirmed (803), the controller 205 executes Java Explorer (804).

If the notification file is found as a result of the search of the notification file of the controller 205 (803), the controller 205 first searches for the presence or absence of the start notification file (805). As a result of checking whether the start notification file is present, when the start notification file is confirmed (806), the controller 205 deletes the target file generated in step 704 of FIG. 7 (807). Here, the target file represents a new file that is changed from the original source file to be changed. When the deletion of the target file is completed (808), the controller 205 deletes the start notification file generated in step 703 of FIG. 7 (809). If the start notification file is deleted, the control unit 205 executes Java Explorer (804).

On the other hand, if the power of the mobile communication terminal is cut off again while deleting the target file in step 808 and the power is supplied again, the above process is performed again from the beginning.

In operation 806, if the start notification file does not exist, the controller 205 searches for the completion notification file (810). When the completion notification file search result and the completion notification file are confirmed (811), the control unit 205 searches the database deletion notification file (812). However, if the completion notification file search result, the completion notification file is not confirmed, the control unit 205 searches for the presence or absence of the notification file again.

When the database deletion notification file is confirmed (813), the controller 205 deletes the source file (814). Here, the source file represents the original file to be changed.

When the source file deletion is completed (815), the control unit 205 deletes the database deletion completion notification file generated in step 707 of FIG. When the deletion of the database deletion completion notification file is completed, the completion notification file generated in step 706 of FIG. 7 is deleted (817). When the completion notification file is deleted, the controller 205 executes Java explorer (804).

If it is determined in step 813 that the database deletion notification file is not confirmed, the controller 205 deletes the target file added to the database (818). When deletion of the target file added to the database is completed (819), a database deletion notification file is generated (820).

If the generated database deletion notification file is confirmed, the controller 205 deletes the source file (814). When the source file deletion is completed (815), the control unit 205 deletes the database deletion completion notification file generated in step 707 of FIG. When the deletion of the database deletion completion notification file is completed, the completion notification file generated in step 706 of FIG. 7 is deleted (817). When the completion notification file is deleted, the controller 205 executes Java explorer (804).

As described above, by generating a notification file while the file structure of the Java application is changed, the file structure of the Java application that is being executed is supplied when power is supplied to the mobile communication terminal even when the mobile terminal is powered off while the file structure of the Java application is changed. You can change it.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the spirit of the present invention for those skilled in the art to which the present invention pertains, and the above-described embodiments and accompanying It is not limited by the drawings.

As described above, the present invention distinguishes between a general folder and a Java application folder which is an execution unit in a mobile communication terminal, and manages a Java application folder as a physical physical file structure, when moving a Java application folder to another external memory. It allows you to move without going through the steps, and if the power of the mobile terminal is cut off while moving to another external memory, restore the Java application to the state where you can perform mutual movement again and use the Java application without any manipulation. It is possible to provide a more efficient service to the user.

Claims (11)

In the mobile terminal manages the Java application, When a folder is input from at least one of a network and an external memory, searching whether a ".jar" to a ".jad" file exists among the files in the input folder; Determining the input folder as the Java application when the “.jar” to “.jad” files exist; And adding a specific identifier to the Java application so as to physically distinguish the Java application from a general folder. delete The method of claim 1, The external memory, Java application management method of a mobile communication terminal comprising a USB (Universal Serial Bus) memory and MMC (Multi-Media Card). The method of claim 1, The Java application, Java application management method of a mobile communication terminal, characterized in that for executing a predetermined function in a folder unit. delete The method of claim 1, Adding a specific identifier to the Java application, And adding ".jav" after the name of the Java application to distinguish it from the general folder. The method of claim 1, And performing at least one of a function of moving, copying, and renaming a general folder and a Java application between the mobile communication terminal and the external memory. The method of claim 7, wherein A process of performing at least one function of moving, copying, and renaming a general folder and a Java application between the mobile communication terminal and the external memory may include: When the general folder and the Java application stored in the mobile terminal and the external memory are selected, a start notification file indicating that the function of the selected general folder and the Java application is started is generated, and then the source files of the selected general folder and the Java application are generated. Creating a target file using Adding the generated target file to a database; When the target file is added to the database, generating a completion notification file indicating that the function is completed, and then deleting the start notification file; Deleting the target notification file added to the database when the start notification file is deleted, and generating a database deletion completion notification file indicating that the deletion of the target file added to the database is completed; And deleting the source file, the completion notification file, and the database deletion completion notification file when the database deletion completion notification file is generated. 9. The method of claim 8, When the power of the mobile communication terminal is cut off while performing the at least one function, After restoring the power of the mobile communication terminal, the notification files are searched, and the general folder and the Java application that are performing the at least one function are executed using the searched notification file to perform the at least one function. Java application management method of the mobile communication terminal further comprising the step of restoring. 9. The method of claim 8, The source file is, Java application management method of the mobile communication terminal, characterized in that the general folder and the Java application to be changed in the mobile communication terminal and the external memory. 9. The method of claim 8, The target file, The Java application management method of the mobile communication terminal, characterized in that the general folder and the new general folder that is changed in the Java application and the general folder to be changed in the mobile communication terminal and the external memory.

Images