JP2003256211A - Application providing system recording medium and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an application having only a function necessary for a user. <P>SOLUTION: A program module divided for every function of an application is stored in a module storage means 1a of a server 1. The transmission request of the program module necessary for a user to prepare an application is inputted to a transmission request input means 2a of a client 2. The transmission request is transmitted to a server 1 by a request transmission means 2b. A module extraction means 1b of the server 1 extracts the program module whose transmission is requested from the module storage means 1a. The extracted program module is transmitted to a client 2 by a module transmission means 1c. A module storage means 2c of the client 2 stores the transmitted program module. An execution means 2d executes the program module (application) stored in the module storage means 2c. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an application providing system, a recording medium and a program, and more particularly to an application providing system, a recording medium and a program for providing an application via a network.

[0002]

2. Description of the Related Art Currently, there is a service for providing an application to a mobile terminal device via an open communication network such as the Internet.

In such an application providing service, an application provider develops and manages an application that meets the needs of a user having a mobile terminal device. The user connects the mobile terminal device to the communication network and downloads the application required by the user from the server of the provider.

[0004]

However, in such an application providing service, the provider creates and provides an application having various functions in order to reflect the needs of many users. Therefore, there is a problem in that even a function unnecessary for a certain user may be included in the application.

Further, there is a problem in that it is necessary to newly create or change an application that does not meet the needs of the user, and the management load of application development is heavy.

The present invention has been made in view of the above circumstances, and an object thereof is to provide an application providing system which provides an application having only a function required by a user.

It is another object of the present invention to provide an application providing system that reduces the management burden of application development.

[0008]

According to the present invention, in order to solve the above problems, in an application providing system for providing an application via a network, a module storage means for storing a program module divided for each function of the application is provided. A server having module extracting means for extracting a program module requested to be transmitted to create a desired application from the module storing means, and module transmitting means for transmitting the program module extracted by the module extracting means, Transmission request input means for inputting the transmission request, request transmission means for transmitting the transmission request to the server, module storage means for storing a program module transmitted from the module transmission means, and the module Application providing system is provided, characterized in that it comprises execution means for executing a program module stored in Lumpur storing means, and a client having a.

According to such an application providing system, the client receives a request to send a program module necessary for creating a desired application. The client transmits a transmission request to the server, and the server transmits the transmission-requested program module to the client. This makes it possible to provide an application having only the functions required by the user.

Further, since the module storage means stores the program module divided for each function of the application, the management load of application development is reduced.

[0011]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a principle diagram for explaining the principle of the present invention. As shown in the figure, the server 1 and the client 2 are connected via a network 3. The server 1 is composed of a module storage means 1a, a module extraction means 1b, and a module transmission means 1c. The client 2 is composed of transmission request input means 2a, request transmission means 2b, module storage means 2c, and execution means 2d. A user who uses the client 2 receives a program module divided for each function of the application from the server 1 via the network 3 in order to realize a desired application on the client 2.

The module storage means 1a of the server 1 stores the program module divided for each function of the application. Program modules of forms A1, A2, ..., Buttons B1, B2, ..., Communications C1, C2, ... Are stored in the module storage means 1a. The forms A1, A2, ... Have a function of displaying, for example, a quadrangular screen as a “base” on the display screen of the client 2. Buttons B1, B2
... is displayed on the forms A1, A2, ..., For example, when the button of the client 2 corresponding to the button B1 is pressed, communication C1, C2, ...
・ Call. The communication C1 has a function of transferring certain data stored in the client 2 to a specific server not shown in FIG. The communication C2 has a function of receiving data from a specific server.

The module extracting means 1b extracts the program module requested to be transmitted from the client 2 from the module storing means 1a. Module transmission means 1c
Sends the program module extracted by the module extracting means 1b to the client 2 via the network 3.

Transmission request input means 2a of the client 2
Is input by the user with a transmission request for a program module required to create a desired application.

The request transmission means 2b is a transmission request input means 2
The transmission request of the program module input in a is transmitted to the server 1. The module storing means 2c is the server 1
Stores the program module sent from.

The executing means 2d is a module storing means 2c.
Execute the program module stored in. Less than,
The operation of the principle diagram of FIG. 1 will be described.

Assume that an application is created that transfers the data stored in the client 2 to a specific server. The user inputs a transmission request for the form A1, the button B1, and the program module of the communication C1 to the transmission request input means 2a.

The request transmission means 2b sends a transmission request for the form A1, the button B1, and the program module of the communication C1 to the server 1 via the network 3. The module extracting means 1b of the server 1 uses the form A1, the button B1, and the communication C1 requested by the client 2 for transmission.
The program module is extracted from the module storage means 1a.

The module transmission means 1c has a form A1, a button B1, which are extracted from the module storage means 1a.
And the program module of the communication C1 is transmitted to the client 2 via the network 3.

The program modules of the form A1, the button B1, and the communication C1 transmitted from the module transmitting means 1c are the module storing means 2c of the client 2.
Stored in. That is, the client 2 stores an application for transferring certain data to a specific server when the button B1 on the form A1 is operated.

The executing means 2d is a module storing means 2c.
The application (program module) stored in is executed, and certain data stored in the client 2 is transferred to a specific server.

As described above, the client requests the server having the program module divided for each function of the application to send the program module required for creating a desired application. The server sends the requested program module to the client. This makes it possible to provide an application having only the functions required by the user.

By adding or changing the program module in the module storage means 1a, it is not necessary to newly create or change an application for an application that does not meet the needs of the user. It is possible to reduce the management load of application development for newly creating and changing applications.

The first embodiment of the present invention will be described in detail below. FIG. 2 is a configuration diagram showing a configuration example of the first embodiment of the present invention. As shown in the figure, the server 10 and the mobile terminal devices 20a, 20b, 20c, ...
Are connected via the Internet 30.

The server 10 stores program modules divided for each function of the application. The server 10 includes mobile terminal devices 20a, 20b, 20c, ...
The program module requested to be transmitted from the device is transmitted to the mobile terminal devices 20a, 20b, 20c, .... The server 10 is managed by an application provider who provides an application.

Mobile terminal devices 20a, 20b, 20c, ...
.. requests the server 10 to send the program module, and receives the program module that requested the sending.
A user who uses the mobile terminal devices 20a, 20b, 20c, ... Is required to implement the mobile terminal devices 20a, 20b, 20c ,.
It connects to the server 10 via the Internet 30, requests the server 10 to send a program module, and receives it. In this way, the user obtains (creates) a desired application from the application provider.

FIG. 3 is a block diagram showing an example of the hardware configuration of the application providing system, (a) is a block diagram of a server, and (b) is a block diagram of a portable terminal device.

The server 10 shown in FIG. 3A has a CPU (C
The entire apparatus is controlled by an entral processing unit) 10a. A RAM (Random Access Memory) 10b, a hard disk drive (HDD) 10c, a graphic processor 10d, an input interface 10e, and a communication interface 10f are connected to the CPU 10a via a bus 10g.

The RAM 10b temporarily stores at least part of an OS (Operating System) program and an application program to be executed by the CPU 10a. Further, the RAM 10b stores various data necessary for the processing by the CPU 10a.

The HDD 10c includes a portable terminal device 20a,
20b, 20c, ... Stores program modules divided for each function of the application requested to be transmitted. The HDD 10c also stores an OS and application programs.

A monitor 10h is connected to the graphic processing device 10d. Graphic processor 10d
Monitors the image according to the instruction from the CPU 10a.
It is displayed on the display screen of 0h. Input interface 10
A keyboard 10i and a mouse 10j are connected to e. The input interface 10e is the keyboard 1
0i and mouse 10j send signals from bus 10
It is transmitted to the CPU 10a via g.

The communication interface 10f is connected to the Internet 30. Communication interface 10f
Is connected to the mobile terminal device 20 via the Internet 30.
Data is transmitted / received to / from a, 20b, 20c, ....

The mobile terminal device 20a shown in FIG.
The entire device is controlled by the CPU 20aa. C
The PU 20aa is connected to the RAM 20a via the bus 20ah.
b, flash ROM (Read Only Memory) 20ac,
ROM 20ad, graphic processing device 20ae, input interface 20af, and communication interface 20
ag is connected.

The RAM 20ab temporarily stores at least part of an OS program and an application program to be executed by the CPU 20aa. Also, RA
The M20ab stores various data required for processing by the CPU 20aa.

The flash ROM 20ac includes the server 1
The program modules divided for each function of the application transmitted from 0 are stored. Flash RO
The M20ac erases the stored program module according to a specific signal from the CPU 20aa. R
The OM 20ad stores an OS and application programs.

A display 20aj is connected to the graphic processor 20ae. The graphic processing device 20ae follows the instruction from the CPU 20aa.
The image is displayed on the display screen of the display 20aj.
The input interface 20af includes touch keys 20ai.
Are connected. The input interface 20af sends a signal sent from the touch key 20ai to the bus 20a.
It is transmitted to the CPU 20aa via h.

The communication interface 20ag is connected to the Internet 30. Communication interface 20
The ag transmits / receives data to / from the server 10 via the Internet 30.

With the above hardware configuration,
The application providing system of this embodiment can be realized. Next, functions of the application providing system according to the first embodiment of the present invention will be described.

FIG. 4 is a functional block diagram of the application providing system according to the first embodiment of the present invention. The user management unit 11 of the server 10 shown in the figure receives the user name input to the mobile terminal device 20a, generates a user No. for the received user name, and transmits the user number to the mobile terminal device 20a. Further, when the user management unit 11 receives the module selection information of the selected program module and the module setting information for determining the operation transmitted from the mobile terminal device 20a, the user information storage unit 14
The selected module table 14a and the module operation table 14b are created in the table, and the received module selection information and module setting information are stored.

The reading unit 12 reads the module information stored in the module information table 13a of the module storage unit 13 in response to a program module transmission request from the mobile terminal device 20a, and transmits the module information to the mobile terminal device 20a.

The module storage unit 13 stores a module information table 13a and a program module group 13b. The module information table 13a stores the module information of each program module of the program module group 13b. Here, the module storage unit 13 and the user information storage unit 14 are, for example, the HDD 10c shown in FIG.
Is.

The charge calculation unit 15 calculates the total charge of the program modules requested to be transmitted. The module extraction unit 16 extracts the program module requested to be downloaded from the mobile terminal device 20a from the program module group 13b and transmits it.

The file creating section 17 creates an operation file from the setting information for setting the operation of the module stored in the module operation table 14b. The operation file is described by a script language.

The authentication unit 18 includes an authentication key and an authentication flag indicating the authority to use the application so that the user who newly downloads the application (program module) can execute the application a predetermined number of times to test the application free of charge. To generate.

The input / output unit 21 of the portable terminal device 20a receives an instruction from the user or displays a screen or the like for prompting the user on the display device. Also, it transmits and receives data to and from the server 10.

The reception module storage unit 23 stores an authentication area 23a for storing user authentication information, a program area 23b for storing a program module downloaded from the server 10, and an operation file for instructing the operation of the program module. It has an operation control area 23c for storing.

The module writing unit 22 is connected to the server 10
Then, a request to send the program module is made to the received program module and the received program module is stored in the program area 23b. The authentication receiving unit 25 stores the user authentication information transmitted from the server 10 in the authentication area 23a.

The execution unit 26 executes the program module stored in the program area 23b in accordance with the authentication information in the authentication area 23a and the operation file stored in the operation control area 23c. Here, the reception module storage unit 23 is, for example, the flash ROM 20 shown in FIG.
The execution unit 26 expands the program module and the operation file in the RAM 20ab and executes the program.

Here, the flow of procedures performed by the user in the entire application providing system will be described. FIG. 5 is a flowchart showing a procedure flow of the user in the application providing system of FIG. The user obtains the application (program module) from the server 10 by the following steps.

[Step S1] The user connects the portable terminal device 20a to the server 10 via the Internet 30. [Step S2] The user inputs to the mobile terminal device 20a whether or not a new application is created. If the application is newly created, the process proceeds to step S3. If not, the process proceeds to step S13.

[Step S3] The user inputs the user name into the portable terminal device 20a. [Step S4] The user selects a program module required to create a desired application from the mobile terminal device 20a.

[Step S5] The user sets, in the mobile terminal device 20a, operation settings for how to operate the selected program module. [Step S6] The user selects steps S4 and S until all the program modules necessary for creating a desired application are selected and the operation is set.
Repeat 5

[Step S7] The user acquires the total amount of money of the selected program module from the portable terminal device 20a. [Step S8] If the total amount of the selected program modules is satisfied, the user inputs an instruction to download the program module into the mobile terminal device 20a. If the total amount is not satisfactory, enter the end instruction.

[Step S9] The user acquires a program module. [Step S10] The user acquires an operation file. [Step S11] The user acquires temporary authentication so that the downloaded application can be tested for free.

[Step S12] The user is the server 10
The program module downloaded from, that is, the application is executed by the mobile terminal device 20a. [Step S13] The user inputs to the mobile terminal device 20a whether or not to perform the formal authentication for officially using the downloaded application. When performing formal authentication, the process proceeds to step S14. If the formal authentication process is not performed, the process proceeds to step S12.

[Step S14] The user is the server 10
Obtain official certification to officially execute the application downloaded from. The specific operation of the application providing system of FIG. 4 in each procedure of the user in the flowchart shown in FIG. 5 will be described below.

4 in steps S1 and S2 of FIG.
The operation of the functional block diagram of the application providing system will be described. When the mobile terminal device 20a is connected to the server 10 via the Internet 30, the input / output unit 21 of the mobile terminal device 20a determines whether or not a new application is created on the display device (display 20aj shown in FIG. 3). Displays a screen for accepting from the user. The input / output unit 21 receives a new application creation from the user (when the touch key 20ai shown in FIG. 3 corresponding to the displayed button is pressed, or the pointer is placed on the button displayed on the screen, Change the screen to one that accepts the user's username.

The operation of the functional block diagram of the application providing system of FIG. 4 in step S3 of FIG. 5 will be described. A screen for accepting the input of the user name is displayed on the display device of the mobile terminal device 20a. Figure 6
An example of a screen displayed on the mobile terminal device, (a) is a user name input screen, and (b) is a user confirmation screen.

As shown in FIG. 6A, on the user name input screen 40a, "user name input" prompting the user to input a user name is displayed. Further, a text box 40b for inputting a user name is displayed. Also, an OK button 40c and a cancel button 40d are displayed. Figure 6
In (a), "○ X Co., Ltd." is entered in the text box 40b.

When the OK button 40c is operated, the input / output unit 21 of the portable terminal device 20a causes the text box 40
The user name “○ × Co., Ltd.” entered in b is stored in the server 10
To the user management unit 11.

The user management section 11 includes a portable terminal device 20a.
When the user name is received from, the user number is issued. Here, it is assumed that the user No. '9001001' has been issued. The user management unit 11 issues the issued user No. 90
01001 'is transmitted to the mobile terminal device 20a.

The input / output unit 21 of the mobile terminal device 20a uses the user number '9001001' sent from the server 10.
Is displayed on the display device. As shown in FIG. 6B, the user confirmation screen 41a displays user No. '9001001'. Also, an OK button 41b and a cancel button 41c are displayed. The user confirms the user confirmation screen 4
Check your user name from 1a, and confirm the user No. 900
1001 'is acquired.

O displayed on the user confirmation screen 41a
When the K button 41b is operated, the input / output unit 21 requests the server 10 to transmit the module information. The reading unit 12 of the server 10 receives the module information transmission request and transmits the module information of the module information table 13a stored in the module storage unit 13 to the mobile terminal device 20a.

The operation of the functional block diagram of the application providing system of FIG. 4 in step S4 of FIG. 5 will be described. The input / output unit 21 of the mobile terminal device 20a is
The module information of the module information table 13a is received. Here, the module information stored in the module information table 13a will be described. FIG. 7 is a diagram showing an example of information stored in the module information table, (a) is a module information table, and (b) is an explanatory diagram illustrating parameter information. As shown in FIG. 7A, in the module information table 13a, “identification No.” given to each program module, “module name” of the program module divided for each function of the application, program size of the program module. "Size" (unit is mega), "Unit price" indicating the program module fee, "Parameter information" indicating the function of the program module, and "Usage limit number" indicating the number of times the program module can be tested free of charge Is stored.

Here, "module name""menu1" and "menu 2" are the module names of the program modules for displaying the functions and commands of the program in a list for easy viewing. "Module name"'input form 1', 'input form 2', screen display format (base)
Is the module name of the program module that displays the screen. "Module Name"'Print Form 1'is
This is the module name of the input form specialized for the print function.

The "parameter information" is represented in the format X-X1, X2, X3, X4 as shown in FIG.
"X" indicates "S" indicating static control,
An identifier of "B" indicating a button control, "I" indicating an input control, and "L" indicating a list control is entered.

The static control means a function of controlling the position and size of characters displayed on a menu or form. A button control is a function that controls the position and size of a button displayed on a menu or form. An input control is a function that controls the position and size of a text box displayed on a menu or form. The list control is a function that controls the position and size of a list box that displays a hierarchical structure such as files displayed on a menu or form.

Numerical values indicating the starting X coordinate and the starting Y coordinate are entered in'X1 'and'X2'. The start X-coordinate and the start Y-coordinate are coordinates on the display screen and indicate the position of a certain point of the program module displayed on the display screen. For example, the origin of the coordinates is set at the upper left corner on the screen of the display device. The start X coordinate and the start Y coordinate indicate the position of the upper left corner of the rectangular button.

Numerical values indicating the width and height of the displayed program module are entered in'X3 'and'X4'. What is width?
For example, the distance from the upper left corner to the upper right corner of the button described above. The height is, for example, the distance from the upper left corner to the lower left corner of the button described above.

In the example shown in FIG. 7A, the program module of "module name"'menu1'has a program size of "8" mega, and the charge is "50" yen. In addition, as parameter information, 'S-1, 1,
10,3 ',' B-5,5,7,3 ', a function to display a character in a range of width 10 and height 3 at a position of start X coordinate 1 and start Y coordinate 1 and start It has a function of displaying a button having a width of 7 and a height of 3 at the position of the X coordinate 5 and the start Y coordinate 5.

When the input / output unit 21 of the mobile terminal device 20a receives the module information in the module information table 13a, it displays the "module name" included in the module information on the display device. FIG. 8 is an example of a screen displayed on the mobile terminal device, where (a) is a module selection screen and (b) is a module confirmation screen.

As shown in FIG. 8A, "module name"'menu1''menu2''input form 1''print form 1'is displayed on the module selection screen 42a. In addition, the module selection screen 42a,
Scroll buttons 42b, 42c for scrolling the screen
Is displayed. When the scroll buttons 42b and 42c are operated, the screen is scrolled and other module names are displayed. In addition, the module selection screen 42a,
An OK button 42d and an end button 42e are displayed.

The module name of the program module to be downloaded is selected from the module names displayed on the module selection screen 42a, and the OK button 42d is selected.
When is operated, the input / output unit 21 requests the server 10 to send a program module corresponding to the selected “module name”. The reading unit 12 of the server 10 reads the program module requested to be transmitted from the program module group 13b of the module storage unit 13 and transmits the program module to the mobile terminal device 20a.

The input / output unit 21 of the mobile terminal device 20a previews the screen of the received program module.
On the module confirmation screen 43a shown in FIG. 8B, a screen preview when the module name'menu 1'is selected is displayed. Also, a setting button 43b and an end button 43c are displayed.

The input / output unit 21 displays the module confirmation screen 43.
When the setting button 43b displayed in a is operated, the screen changes to a screen for setting the operation of the selected program module.

The input / output unit 21 of the portable terminal device 20a will be described below.
The operation of will be described using a flowchart. Figure 9
7 is a flowchart showing a flow of module selection processing. The input / output unit 21 is the OK button 4 shown in FIG.
1b is operated to execute the following processing.

[Step S21] The input / output unit 21 of the portable terminal device 20a receives the module information in the module information table 13a and displays the module selection screen 42a on the display device.

[Step S22] The input / output unit 21 selects the module name from the module selection screen 42a
When the K button 42d is operated, the process proceeds to step S23.
When the end button 42e is operated, the module selection process ends.

[Step S23] The input / output unit 21 downloads the program module corresponding to the selected module name from the server 10 and displays the module confirmation screen 43a on the display device.

[Step S24] When the setting button 43b on the module confirmation screen 43a is operated, the input / output unit 21 proceeds to step S25. When the end button 43c is operated, the process proceeds to step S21.

[Step S25] The input / output unit 21 performs an operation setting process for the program module whose screen is previewed. The operation of the functional block diagram of the application providing system of FIG. 4 in steps S5 and S6 of FIG. 5 will be described.

The mobile terminal device 20a has the setting button 4 displayed on the module confirmation screen 43a shown in FIG. 8B.
When 3b is operated, the process proceeds to the process of setting the operation of the program module whose screen is previewed.

FIG. 10 shows an example of a screen displayed on the mobile terminal device. (A) is an operation list screen, (b) is an operation setting screen, and (c) is a function setting screen. As shown in FIG. 10A, the input / output unit 21 of the mobile terminal device 20a displays an operation list screen 44a showing an operation list of the selected program module on the display device. Operation list screen 44a
Is a list of operations when the "module name""menu1" is selected. In the operation list screen 44a, when "form load" for setting the operation when the program module of "menu 1" is displayed on the display screen and the program module of "menu 1" are displayed on the display device, The'S1 control 'for setting the character displayed on the menu and the'B1 control' for setting the button displayed on the menu are displayed. These displays are displayed based on the received module information of the module information table 13a.

In the input / output unit 21, the operation desired to be set is selected from the operation list screen 44a, and the setting button 44b is set.
When is operated, the screen changes to the function list screen. Figure 1
As shown in 0 (b), the function list screen 45a showing the function list of the program module is displayed on the display device of the mobile terminal device 20a. The function list screen 45a is a function list when "form load" is selected. On the function list screen 45a, a "file REA" showing a function for reading a file when a "form load" is performed.
D ',' screen display 'showing the function of displaying the screen on the form is displayed. That is, "module name"
The program module of'Menu 1'reads a file when'Form load 'is done,
It has the function of displaying a certain screen.

If the file to be read is to be changed when the "form load" is performed, "file READ" on the function list screen 45a is selected and the function button 45b is operated. Further, when it is desired to change the screen displayed when the "form load" is performed, "screen display" is selected and the function button 45b is operated.

When the S1 control or B1 control is selected, the characters displayed in'menu 1 ',
The display position, display size, display content of the button, processing to be performed when the button is operated, and the like are set.

When the function button 45b is operated, FIG.
As shown in (c), the function setting screen 46a for setting a specific function when the program module operates is displayed on the display device of the mobile terminal device 20a.
The function setting screen 46a is a function list when "file READ" is selected on the function list screen 45a. When the user wants to change the file to be read, the changed file name is written in the area 46b. Also, if you want to change the function of'Form load 'to write file instead of reading file,' File WRITE '
Select. When you have made the desired settings, the setting button 46c
To operate.

When the setting button 46c is operated, the input / output unit 21 sends the setting information of the set program module to the user management unit 11 of the server 10. The user management unit 11 creates a selection module table 14a and a module operation table 14b that store the received setting information in the user information storage unit 14. In addition, the input / output unit 21
Changes the display screen to the operation list screen 44a.

When the operation setting is completed and the end button 44c of the operation list screen 44a is operated, the screen returns to the module selection screen 42a shown in FIG. 8A. The above operation is repeated until the user selects the program module and finishes the operation setting.

FIG. 11 is a selection module table. In the selection module table 14a shown in the figure, the "user No." of the user who selected the program module,
Information on "identification No.", "module name", "unit price", "size", and "use limit number" of the selected program module is stored. Selection module table 1
4a is created for each user who wants to download a program module, and the selection module table 1
4a shows the setting information of the program module selected by the user of "User No"'9001001'.

FIG. 12 is a module operation table. In the module operation table 14b shown in the figure, the "user No." of the user who selected the program module,
"Identification No.", "Module Name", "Function No." of the selected program module, set "Function Name",
Information on “display position”, “display size”, “display content”, “function”, “function parameter 1”, and “function parameter 2” is stored. Module operation table 14
b is generated for each user who tries to download the program module, and the module operation table 14
In b, a part of the setting information of the program module selected by the user of “User No” '9001001' is shown (the blank indicates that there is no data to be stored).

FIG. 13 is a flow chart showing the flow of the module setting process. The input / output unit 21 is shown in FIG.
The end button 43c of the module confirmation screen 43a shown in (b) is operated to execute the following processing.

[Step S31] The input / output unit 21 of the portable terminal device 20a displays the operation list screen 44a of the selected program module. [Step S32] The input / output unit 21 displays the operation list screen 44.
When the operation to be set is selected from a and the setting button 44b is operated, the process proceeds to step S33. When the end button 44c is operated, the module operation setting is ended (FIG. 8).
(Returns to the module selection screen 42a of (a)).

[Step S33] The input / output unit 21 displays the function list screen 45a of the selected operation. [Step S34] The input / output unit 21 displays the function list screen 45.
When the function is selected from a and the function button 45b is operated, the process proceeds to step S35. When the return button 45c on the function list screen 45a is operated, the process proceeds to step S31.

[Step S35] In the input / output unit 21, the function setting is performed from the function setting screen 46a, and the setting button 46
When c is operated, the setting information of the program module is transmitted to the server 10, and the process proceeds to step S31.

Next, in step S7 of FIG.
The operation of the functional block diagram of the application providing system will be described. When the user selects and sets the program module (end button 4 in FIG. 8A)
2e is operated), the mobile terminal device 20a input / output unit 2
1 requests the server 10 to calculate the total amount of money for the selected program module. The charge calculation unit 15 of the server 10 requests the calculation of the total amount of money and selects the selected module table 1 stored in the user information storage unit 14.
The total price of the selected program modules is calculated from the "unit price" of 4a. The charge calculation unit 15 transmits the calculated total amount to the mobile terminal device 20a.

The input / output unit 21 of the mobile terminal device 20a displays the total amount of money received from the charge calculation unit 15 of the server 10 on the display device. FIG. 14 is an example of a screen displayed on the mobile terminal device, in which (a) is a charge display screen and (b) is a download confirmation screen.

On the application fee screen 47a shown in FIG. 14A, the program module selected by the user and the total amount thereof are displayed. Also, a confirmation button 47
b, a cancel button 47c is displayed. When the user confirms the content displayed on the application fee screen 47a and operates the confirmation button 47b, the input / output unit 21 of the mobile terminal device 20a confirms the download of the program module whose display screen is shown in FIG. 14 (b). Screen 48a
Transition to.

The operation of the fee calculation unit 15 of the server 10 will be described below with reference to a flowchart. FIG. 15 is a flowchart showing the flow of the total amount calculation processing. When the user selects and sets the program module, the charge calculation unit 15 executes the following process.

[Step S41] The fee calculation unit 15 of the server 10 receives a request for calculating the total amount of the program modules selected by the user from the mobile terminal device 20a. [Step S42] The fee calculation unit 15 selects the selection module table 14a stored in the user information storage unit 14.
Calculate the total price of the program module selected from the'Unit price '.

[Step S43] The fee calculation section 15 transmits the calculated total amount of program modules to the portable terminal device 20a. Next, the operation of the functional block diagram of the application providing system of FIG. 4 in steps S8 and 9 of FIG. 5 will be described.

When the confirmation button 48b shown in FIG. 14B is operated, the module writing unit 22 of the mobile terminal device 20a requests the server 10 to download the program module.

When a program module download request is issued, the module extraction unit 16 of the server 10 acquires one "module name" from the selected module table 14a stored in the user information storage unit 14. Then, the program module corresponding to the "module name" is extracted from the program module group 13b of the module storage unit 13. The module extraction unit 16 downloads the extracted program module to the mobile terminal device 20a.

The module extracting section 16 repeats the operations of acquiring the “module name”, extracting the program module, and downloading until all the “module names” stored in the selected module table 14a are acquired and downloaded.

The module writing unit 22 of the mobile terminal device 20a downloads the program module from the server 10. The module writing unit 22 checks whether or not the downloaded program module has been downloaded with correct data. For example, a checksum or the like is performed. If it is not downloaded correctly, an error is transmitted to the module extraction unit 16 of the server 10.

When the program module is properly downloaded, the module writing unit 22 acquires the program size of the program module. In addition, the module writing unit 22 includes a receiving module storage unit 23.
The size of the empty area of the program area 23b is acquired.

The module writing section 22 compares the size of the program module with the size of the empty area of the program area of the receiving module storage section 23. If the size of the program module is larger than the size of the free area, the module writing unit 22 reports an error to the server 10.
Send to. When the size of the program module is smaller than the empty area, the module writing unit 22 stores the program module in the empty area of the program area 23b.

Further, the module writing unit 22 checks whether the program module has been correctly written in the program area. For example, the program size of the program module to be written is compared with the program size of the program module actually written in the program area.

When the program module is written correctly, the module writing unit 22 makes a download request for the next program module to the server 10. If it is not written correctly, an error is transmitted to the module extraction unit 16.

When receiving an error from the module writing unit 22, the module extracting unit 16 downloads the same program module to the portable terminal device 20a.
The operations of the module extracting unit 16 of the server 10 and the module writing unit 22 of the mobile terminal device 20a will be described below with reference to flowcharts. FIG. 16 is a flow chart showing the flow of program module download processing in the server.

[Step S51] The module extraction unit 16 of the server 10 checks whether or not there is a program module transmission request from the mobile terminal device 20a. If there is a transmission request, the process proceeds to step S52.

[Step S52] Module Extracting Unit 16
Ends the step S53 if there is a “module name” to be read (not downloaded) in the selected module table 14a, otherwise ends the download process.

[Step S53] Module Extracting Unit 16
Is the program module group 13 of the module storage unit 13 that corresponds to the program module corresponding to the “module name”.
Extract from b.

[Step S54] Module Extracting Unit 16
Displays the extracted program module in the mobile terminal device 20.
a, and the process proceeds to step S51. FIG. 17 is a flowchart showing the flow of the program module download process in the mobile terminal device.

[Step S61] The module writing unit 22 of the mobile terminal device 20a receives the program module from the server 10. [Step S62] The module writing unit 22 checks whether the program module has been downloaded correctly. If it is downloaded correctly, the process proceeds to step S63. If it is not downloaded correctly, the process proceeds to step S69.

[Step S63] The module writing unit 22 acquires the program size of the received program module. [Step S64] The module writing unit 22 acquires the size of the free area of the program area of the receiving module storage unit 23.

[Step S65] The module writing unit 22 compares the size of the program module with the size of the empty area. If the program size of the program module is smaller than the free area, the process proceeds to step S66. If the program size of the program module is larger than the free area, the process proceeds to step S69.

[Step S66] The module writing unit 22 writes the received program module in the empty area of the receiving module storage unit 23. [Step S67] The module writing unit 22 checks whether the program module has been correctly written in the empty area of the receiving module storage unit 23. If it is written correctly, the process proceeds to step S68. If it is not written correctly, the process proceeds to step S69.

[Step S68] The module writing section 22 makes a transmission request for the next program module. [Step S69] The module writing unit 22 transmits an error to the server 10.

Next, the operation of the functional block diagram of the application providing system of FIG. 4 in step S10 of FIG. 5 will be described. When all the program modules selected by the user are downloaded to the mobile terminal device 20a, the file creation unit 17 of the server 10 reads the module operation information from the module operation table 14b of the user information storage unit 14. The file creating unit 17 analyzes the read module operation information, converts it into a script language, and creates an operation file. File creation section 1
Step 7 repeats reading the module operation information, converting the script language, and creating the operation file until all the module operation information in the module operation table 14b is read.

FIG. 18 is a diagram showing the contents of the operation file. The module operation information of the module operation table 14b is converted into a script language as shown in FIG. The operation file will be described below within the range shown in FIG.

The module name of the program module selected by the user is described between <Module> and </ Module>. <Menu 1> and </ Menu 1
Between <>, tags <Load>, </ Load>, for specifying the operation of the program module of Menu 1
<B1 Control>, </ B1 Control
> Is described. Between <Load> and </ Load>, when the program module of menu 1 is form-loaded, the Must. Dat
There is a description to read the file. Also, there is a description indicating the size of the character "Title" and the display position. In addition, an instruction to display a button is described, the size and position of the button, and an instruction of a character to be displayed in the frame of the button are described. <B1 Contr
Between ol> and </ B1 Control>, an instruction to call the module of the input form 1 when the button on the menu 1 is operated is described.

<Input form 1> and </ input form 1
Between <>, tags <Load>, </ Load>, for specifying the operation of the program module of Menu 1
<B1 Control>, </ B1 Control
> Is described. Between <Load> and </ Load>, the instruction to display the button when the program module of the input form 1 is form-loaded is described, and its size, display position, and display in the button frame The instruction of the character to be written is described. <B1Contr
Between ol> and </ B1 Control>, there is a description of an instruction to return to the program module of menu 1 when a button on input form 1 is operated.

The file creating section 17 sends the created operation file to the file writing section 24 of the portable terminal device 20a. The file writing unit 24 checks whether or not the received operation file has been correctly received. For example, a checksum or the like is performed. When the file is not correctly received, the file creating unit 17 is notified of the error.

When the action file is correctly received, the file writing unit 24 acquires the file size of the action file. Further, the size of the free area of the operation control area 23c of the reception module storage unit 23 is acquired.

The file writing section 24 compares the file size of the operation file with the size of the free area of the operation control area 23c of the receiving module storage section 23. When the file size is larger than the size of the free area, the file writing unit 24 sends an error to the file creating unit 17. When the size of the operation file is smaller than the free area, the operation file is stored in the free area 23c of the operation control area.

Further, the file writing unit 24 checks whether the operation file has been correctly written in the operation control area 23c. For example, the size of the motion file written is compared with the file size of the motion file actually written in the motion control area 23c.

If the action file was written correctly,
The fact that the operation file has been normally transferred is transmitted to the file creating unit 17. When the file is not correctly received, the file creating unit 17 is notified of the error.

When the file creating section 17 receives an error from the file writing section 24, it again sends the operation file to the portable terminal device 20a. The operations of the file creation unit 17 of the server 10 and the file writing unit 24 of the mobile terminal device 20a will be described below with reference to flowcharts. FIG. 19 is a flowchart showing the flow of operation file transmission processing in the server. When the download of the program module is completed, the file creation unit 17 of the server 10 executes the following processing.

[Step S71] The file creating section 17 of the server 10 checks whether or not the module operation table 14b has module information to be converted into the script language. If there is module information to be converted into the script language, the process proceeds to step S72. If there is no module operation information to be converted, the process proceeds to step S73.

[Step S72] File creating unit 17
Converts the module operation information into a script language and writes it in the operation file. [Step S73] The file creation unit 17 sends the operation file to the mobile terminal device 20a.

FIG. 20 is a flow chart showing the flow of the operation file receiving process in the portable terminal device.
[Step S81] The file writing unit 24 of the mobile terminal device 20a receives the operation file from the server 10.

[Step S82] File Writing Unit 2
4 checks whether or not the operation file has been correctly received. If it is correctly received, the process proceeds to step S83, and if it is not correctly received, the process proceeds to step S89.

[Step S83] File Writing Unit 2
4 acquires the file size of the received operation file. [Step S84] The file writing unit 24 acquires the size of the free area of the operation control area 23c of the receiving module storage unit 23.

[Step S85] File Writing Unit 2
4 compares the size of the operation file with the size of the free area. If the file size is smaller than the free area, the process proceeds to step S86. If the file size is larger than the free area, the process proceeds to step S89.

[Step S86] File Writing Unit 2
4 writes the received operation file in the free area of the operation control area of the reception module storage unit 23. [Step S87] The file writing unit 24 stores the operation file in the operation control area 23 of the reception module storage unit 23.
It is checked whether the data has been correctly written in the empty area of c.
If it is written correctly, the process proceeds to step S88. If it is not written correctly, the process proceeds to step S89.

[Step S88] File Writing Unit 2
4 indicates that the server 10 has received the operation file normally.
Notify to. [Step S89] The file writing unit 24 sends an error to the server 10.

When the operation file is transferred from the server 10 to the mobile terminal device 20a, the server 10 generates a temporary authentication key and a temporary authentication flag, and transfers the temporary authentication key and the temporary authentication flag to the mobile terminal device 20a.

Next, the operation of the functional block diagram of the application providing system of FIG. 4 in step S11 of FIG. 5 will be described. The authentication unit 18 of the server 10 allows the user who newly downloads the application (program module) to execute the application a predetermined number of times for testing, so that the user who has created (downloaded) the new application, The usage fee of the application is paid to the application provider, and a temporary authentication key and a temporary authentication flag for identifying a user who can execute the application indefinitely are generated.

The authentication section 18 stores the temporary authentication key and the temporary authentication flag in the user table 14c of the user information storage section 14. FIG. 21 is a diagram showing a user table of the server. In the user table 14c, the "user No" given to the user, the "user name" of the user, the "authentication flag" indicating whether the user is a temporary registrant or an official registrant, and the user is given to the user. The “authentication key” is stored. Temporary authentication key '12 is assigned to "User No."'9001001', which newly downloaded the application.
23-25C-S45W 'and a temporary authentication flag' 0 'are stored.

After the temporary authentication key and the temporary authentication flag have been stored in the user table 14c, the authentication unit 18 acquires the free usage count of the downloaded application. The authentication unit 18 acquires the minimum number of times of limited use stored in the selection module table 14a as the number of times of free use. From the selection module table 14a shown in FIG. 11, the number of free use of "user No."'9001001' is "20".

The authentication unit 18 transmits the temporary authentication key, the temporary authentication flag, and the free use count to the mobile terminal device 20a. The authentication receiving unit 25 of the mobile terminal device 20a receives the "authentication flag", the "authentication key", and the number of times of free use, and checks whether or not they have been correctly received. For example, a checksum or the like is performed. If it is not correctly received, the error is notified to the authentication unit 18 of the server 10.

When the "authentication key", the "authentication flag", and the free usage count are correctly received, the authentication receiving unit 25
The “authentication key”, the “authentication flag”, and the number of times of free use are stored in the user table of the authentication area 23 a of the reception module storage unit 23. FIG. 22 is a diagram showing a user table of the mobile terminal device. In the user table 23aa, a "user No" assigned to the user, an "authentication flag" indicating whether the user is a temporary registrant or an official registrant,
The “authentication key” given to the user, the “free usage count” indicating the number of times the application can be tested free of charge, and the “current execution count” at which the downloaded application is executed are stored. "User No."'9001001', which newly downloaded the application,
The temporary authentication key “1223-25C-S45W” and the temporary authentication flag “0” are stored.

Further, the authentication receiving unit 25 checks whether the “authentication key”, the “authentication flag”, and the “free use count” are correctly written in the authentication area of the receiving module storage unit 23. For example, the data size of the "authentication key", "authentication flag", and "free usage count" that are written, and the "authentication key", "authentication flag", and "free usage count" that are actually written in the authentication area Compare the data sizes.

When the “authentication key”, the “authentication flag”, and the “free use count” are written correctly, the authentication receiving unit 25 indicates that the information has been normally received by the authentication unit 18 of the server 10.
Notify to. If it is not written correctly, the error is notified to the authentication unit 18.

When the authentication unit 18 of the server 10 receives the error from the module writing unit 22, the authentication unit 18 again sends the "authentication key", the "authentication flag", and the "free use count" to the portable terminal device 20a.

The operations of the authentication unit 18 of the server 10 and the authentication reception unit 25 of the mobile terminal device 20a will be described below with reference to a flowchart. FIG. 23 is a flowchart showing the flow of generation and transfer processing of the temporary authentication key, the temporary authentication flag, and the free usage count in the server.

[Step S91] Authentication Unit 1 of Server 10
8 generates a temporary authentication flag and a temporary authentication key. [Step S92] The authentication unit 18 stores the generated temporary authentication key and temporary authentication flag in the user table 14c of the user information storage unit 14.

[Step S93] The authentication section 18 obtains from the selected module table 14a the number of times of use limitation of the program module downloaded by the user, and obtains the minimum number of times as the number of times of free use of the application.

[Step S94] The authentication section 18 transmits the temporary authentication key, the temporary authentication flag, and the number of times of free use to the portable terminal device 20a. FIG. 24 is a flowchart showing the flow of generation and transfer processing of the temporary authentication key, the temporary authentication flag, and the free use count in the mobile terminal device.

[Step S101] Portable terminal device 20a
The authentication receiving unit 25 receives the temporary authentication key, the temporary authentication flag, and the free use count from the server 10. [Step S102] The authentication receiving unit 25 checks whether or not the temporary authentication key, the temporary authentication flag, and the free usage count have been correctly received. If it is correctly received, the process proceeds to step S103, and if it is not correctly received, the process proceeds to step S106.

[Step S103] The authentication receiving section 25
The received temporary authentication key, temporary authentication flag, and free usage count are stored in the authentication area 23a of the reception module storage unit 23.

[Step S104] The authentication receiving section 25
It is checked whether the temporary authentication key, the temporary authentication flag, and the number of times of free use are correctly written in the empty area of the operation control area 23c of the receiving module storage unit 23. If it is written correctly, the process proceeds to step S105, and if it is not written correctly, the process proceeds to step S106.

[Step S105] The authentication receiving section 25
The server 10 is notified that the temporary authentication key, the temporary authentication flag, and the free use count have been normally received. [Step S106] The authentication receiving unit 25 transmits an error to the server 10.

Next, the operation of the functional block diagram of the application providing system of FIG. 4 in step S12 of FIG. 5 will be described. When the downloaded application is executed by the user's operation, the execution unit 26 of the mobile terminal device 20a causes the reception module storage unit 2 to operate.
The authentication flag of the user table 23aa of No. 3 is acquired.
If the authentication flag is “1”, the execution unit 26 executes the downloaded application according to the script language description of the operation file stored in the operation control area 23c.

When the authentication flag is "0", the execution unit 26
Acquires the current execution count from the user table 23aa and adds "1". The execution unit 26 acquires the usage limit number of times from the user table 23aa of the authentication area and compares it with the current number of executions to which “1” is added. If the number of executions to which "1" is added is larger than the number of times of use limitation, the execution unit 26
Does not execute the application. If the number of executions to which "1" is added is less than or equal to the number of free usages, the execution unit 26
Rewrites the current execution count and executes the downloaded application according to the script language description of the operation file stored in the operation control area 23c.

The operation of the execution unit 26 of the mobile terminal device 20a will be described below with reference to a flowchart. FIG. 25 shows
6 is a flowchart showing a flow of application execution processing.

[Step S111] Portable terminal device 20a
The execution unit 26 of the user table 23 of the authentication area 23a
Acquire the authentication flag from aa. [Step S112] The execution unit 26 proceeds to step S113 if the acquired authentication flag is a temporary authentication flag. If it is the official authentication flag, the process proceeds to step S117.

[Step S113] The execution section 26 obtains the current execution count from the user table 23aa and sets it to "1".
Is added. [Step S114] The execution unit 26 uses the user table 2
The usage limit number is acquired from 3aa.

[Step S115] The execution section 26
Compare the current execution count that has been incremented by "1" with the usage limit count. If the number of current executions added by "1" is larger than the number of times of use limitation, the process is terminated. If the number of current executions that has been incremented by "1" is less than or equal to the use limit number, step S11
Go to 6.

[Step S116] The executing section 26
The current execution count, which is incremented by "1", is stored in the user table 23a.
Store in a. [Step S117] The execution unit 26 determines that the operation control area 23
Read the action file stored in c.

[Step S118] The execution section 26 executes the application stored in the program area according to the script language described in the operation file.

Next, the operation of the functional block diagram of the application providing system of FIG. 4 in steps S13 and S14 of FIG. 5 will be described. The authentication receiving unit 25 of the mobile terminal device 20 a uses the “user N” of the user table 23 aa stored in the authentication area of the receiving module storage unit 23.
“O” is transmitted to the server 10.

The authentication section 18 of the server 10 indicates that "user N
It receives "o" and confirms whether the received "user No" is stored in the user table 14c. When the “user No” is stored in the user table 14c, the authentication unit 18 generates a formal authentication key and a formal authentication flag,
Store in the user table 14c. Furthermore, the authentication unit 18
Sends the formal authentication key and the formal authentication flag to the mobile terminal device 20a.

The authentication receiving section 25 of the portable terminal device 20a is
Receives the formal authentication key and formal authentication flag, and checks if the formal authentication key and formal authentication flag are received correctly. For example, a checksum or the like is performed. If received correctly, the authentication receiving unit 25 displays the reception module storage unit 23.
The received formal authentication key and formal authentication flag are stored in the user table 23aa in the authentication area 23a.

Further, the authentication receiving section 25 checks whether the formal authentication key and the formal authentication flag are correctly written in the authentication area 23a. For example, the data size of the formal authentication key and the formal authentication flag written is compared with the data size of the temporary authentication key and the temporary authentication flag actually written in the authentication area 23a.

The operations of the authentication unit 18 of the server 10 and the execution unit 26 of the mobile terminal device 20a will be described below with reference to the flowcharts. FIG. 26 is a flowchart showing the flow of a process of generating a formal authentication key and a formal authentication flag in the server.

[Step S131] The authentication section 18 of the server 10 receives the user number from the portable terminal device 20a. [Step S132] The authentication unit 18 confirms whether or not the received user number is stored in the user table 14c of the user information storage unit 14. User table 14c
If the user number is stored in step S133,
If not stored, the process ends.

[Step S133] The authentication section 18 generates a formal authentication key and a formal authentication flag. [Step S134] The authentication unit 18 stores the generated formal authentication key and formal authentication flag in the user table 14c.

[Step S135] The authentication section 18 sends the generated formal authentication key and formal authentication flag to the portable terminal device 20.
Send to a. FIG. 27 is a flowchart showing the flow of a formal authentication key and formal authentication flag reception process in the mobile terminal device.

[Step S141] Portable Terminal Device 20a
The authentication receiving unit 25 receives the formal authentication key and the formal authentication flag from the server 10. [Step S142] The authentication receiving unit 25 checks whether the formal authentication key and the formal authentication flag have been correctly received. If received correctly, the process proceeds to step S143, and if not received correctly, step S146.
Go to.

[Step S143] The authentication receiving section 25
The received formal authentication key and formal authentication flag are written in the authentication area 23a of the reception module storage unit 23. [Step S144] The authentication receiving unit 25 checks whether the formal authentication key and the formal authentication flag are correctly written in the authentication area 23a of the receiving module storage unit 23. If it is written correctly, the process proceeds to step S145, and if it is not written correctly, the process proceeds to step S146.

[Step S145] The authentication receiving section 25
The server 10 is notified that the formal authentication key and the formal authentication flag have been normally received. [Step S146] The mobile terminal device 20a transmits an error to the server 10.

As described above, in the present embodiment, the required program module is downloaded from the server 10 to the portable terminal device 20a so that the application can be executed. Therefore, the application having only the function required by the user can be provided. Will be able to offer.

Also, the application provider does not need to newly create or change an application in order to meet new needs of the user, and may create or change a program module having a function corresponding to user needs. , The management burden of application development can be reduced.

Also, by displaying the total amount of program modules to be downloaded on the mobile terminal device 20a, the user can consider adding or deleting a function, and provide a better service to the user. be able to.

Further, the user who newly downloaded the application (program module) can execute the application for a predetermined number of times free of charge, and the better service can be provided to the user.

It should be noted that, with the above-described application providing system, for example, an application for executing a product inspection work, an ordering work, and an inventory work is installed in the mobile terminal device 20a.
Can be achieved with. By the way, depending on the user, there are cases where the processing of the inventory work is not necessary. In this case, only the program module that can implement the processing of product inspection work and ordering work may be downloaded from the server.

Next, a second embodiment of the present invention will be described. The configuration example and the hardware configuration according to the second embodiment of the present invention are the same as the configuration example and the hardware configuration according to the first embodiment shown in FIGS. 2 and 3, and a description thereof will be omitted.

FIG. 28 is a functional block diagram of an application providing system according to the second embodiment of the present invention. In this figure, portions corresponding to those in FIG. 4 are designated by the same reference numerals, and description thereof will be omitted. The second embodiment differs from the first embodiment in that when the revision notifying unit 19 is added to the server 10 and the program module is revised, the fact is notified to the user. Further, the modification rewriting unit 27 is added to the mobile terminal device 20a to receive the modified program module and rewrite the program module before the modification to the modified program module, which is different from the case of the first embodiment. . For other configurations, first
This is the same as the case of the above embodiment.

The operation of the functional block diagram of FIG. 28 will be described below. Assume that there is a revision of the program module. The revised program module is stored in the program module group 13b of the module storage unit 13. After the revision, the user sets the mobile terminal device 20a to the server 10
When the connection is connected to the server, the revision notification unit 19 of the server 10 notifies the revision rewriting unit 27 of the mobile terminal device 20a that the program module has been revised.

Upon receiving the notification that the program module has been revised, the revision rewriting unit 27 receives the certification area 23.
user N stored in the user table 23aa of a
o is transmitted to the revised edition rewriting unit 27.

The revision notifying section 19 receives the received user number.
It is confirmed whether the same user No. as the above is stored in the selected module table 14a. If the selected module table 14a has the same user number, it is confirmed from the selected module table 14a whether or not the user has downloaded the program module before revision corresponding to the revised program module. If the user has received the program module before revision, the revision notification unit 19
The revision information of the program module is displayed on the mobile terminal device 20a.
Send to.

The revised edition rewriting unit 27 displays the received revised information on the display device. When the revision rewriting unit 27 receives a download request for a revised program module from the user, it issues a download request for the revised program module to the server 10.

The revision notifying section 19 extracts the revised program module from the program module group 13b and downloads it to the portable terminal device 20a. The revision rewriting unit 27 rewrites the program module before revision stored in the program area 23b into the revised program module.

Here, the rewriting of the revised program module and the pre-revised program module on the memory will be specifically described. FIG. 29 is a transition state diagram for explaining rewriting of a program module in the memory. (A) is a download state, (b) is a program module expansion state, (c) is a program module deletion state, and (d) is a program module. Shows the write state of.

As shown in FIG. 29A, the revised program module is stored in the RAM 20ab. When the revised program module is stored in the RAM 20ab, all the program modules stored in the program area of the flash ROM 20ac are stored in FIG.
It is copied to the RAM 20ab as shown in (b). Then, the program area of the flash ROM 20ac is initialized.

Thereafter, the program module before revision contained in the program module copied to the RAM 20ab is deleted as shown in FIG. 29 (c). Further, as shown in FIG. 29D, the revised program module stored in the RAM 20ab and the program module in which the program module before the revision is deleted are copied to the flash ROM 20ac. In this way, the program module is rewritten.

The operations of the revision notification unit 19 of the server 10 and the revision rewriting unit 27 of the portable terminal device 20a will be described below with reference to the flowcharts. FIG. 30 is a flowchart showing the flow of the program module revision process in the server.

[Step S151] The revision notifying section 19 of the server 10 notifies that there is a revision of the program module. [Step S152] The revision notification unit 19 receives the user number from the mobile terminal device 20a.

[Step S153] The revision notifying section 19
It is confirmed whether the same user number as the received user number is stored in the selection module table 14a, and it is checked whether the user is downloading the program module before revision. If the program module before revision is downloaded, the process proceeds to step S154.
If not downloaded, the process ends.

[Step S154] The revision notifying section 19
The revision information of the revised program module is transmitted to the mobile terminal device 20a. [Step S155] The revision notifying unit 19 receives from the mobile terminal device 20a whether or not there is a download request for the revised program module. If there is a download request, the process proceeds to step S156. If there is no download request, the process ends.

[Step S156] The revision notifying section 19
It is extracted from the revised program module group 13b and transmitted to the mobile terminal device 20a. FIG. 31 is a flowchart showing the flow of the revision process of the program module in the mobile terminal device.

[Step S161] Portable terminal device 20a
The revision rewriting unit 27 of sends the user No. stored in the receiving module storage unit 23 to the server 10. [Step S162] The revision rewriting unit 27 uses the server 1
If the revision information is received from 0, the process proceeds to step S163, and if not, the process ends.

[Step S163] Revision rewriting unit 27
Displays the revision information on the display device. [Step S164] When a request for downloading the revised program module is received from the user, the process proceeds to step S164. If the download request is not accepted, the process ends.

[Step S165] Revised version rewriting section 27
Receives the revised program module from the server 10 and rewrites the pre-revised program module stored in the program area 23b with the revised program module.

As described above, in this embodiment, when the program module is revised, the revision information is transmitted to the portable terminal device 20a, so that a better service can be provided to the user.

If a fee is charged for downloading the revised program module, the fee calculation unit 15
By the mobile terminal device 20a
May be notified. In addition, the authentication unit 18 may add a temporary authentication so that the application (program module) can be tested.

The above processing functions can be realized by a computer. In that case, the server 10,
The processing contents of the functions that the mobile terminal device 20a should have are described in a program recorded in a computer-readable recording medium. Then, by executing this program on a computer, the above processing is realized on the computer. Computer-readable recording media include magnetic recording devices and semiconductor memories.
For distribution in the market, CD-ROM (Compact Di
sk Read Only Memory) or a flexible disk to store the program in a portable recording medium for distribution,
It can be stored in a storage device of a computer connected via a network and transferred to another computer via the network. When the program is executed by a computer, the program is stored in a hard disk device in the computer, loaded into the main memory and executed.

[0200]

As described above, in the present invention, the client requests the server having the program module divided for each function of the application to send the program module necessary for creating a desired application. The server sends the requested program module to the client. This makes it possible to provide an application having only the functions required by the user.

Further, by newly creating or changing the program module divided for each function of the application, it becomes possible to reduce the management load of the application development.

[Brief description of drawings]

FIG. 1 is a principle diagram illustrating the principle of the present invention.

FIG. 2 is a configuration diagram showing a configuration example of a first exemplary embodiment of the present invention.

FIG. 3 is a block diagram showing a hardware configuration example of an application providing system, FIG. 3A is a block diagram of a server, and FIG. 3B is a block diagram of a mobile terminal device.

FIG. 4 is a functional block diagram of an application providing system according to the first embodiment of the present invention.

5 is a flowchart showing a procedure of a user in the application providing system of FIG.

FIG. 6 is an example of a screen displayed on a mobile terminal device,
(A) is a user name input screen, (b) is a user confirmation screen.

FIG. 7 is a diagram showing an example of information stored in a module information table, in which (a) is a module information table;
(B) is an explanatory view explaining parameter information.

FIG. 8 is an example of a screen displayed on a mobile terminal device,
(A) is a module selection screen, (b) is a module confirmation screen.

FIG. 9 is a flowchart showing a flow of module selection processing.

FIG. 10 is an example of a screen displayed on a mobile terminal device,
(A) is an operation list screen, (b) is an operation setting screen,
(C) is a function setting screen.

FIG. 11 is a selection module table.

FIG. 12 is a module operation table.

FIG. 13 is a flowchart showing a flow of module setting processing.

FIG. 14 is an example of a screen displayed on a mobile terminal device,
(A) is a charge display screen, (b) is a download confirmation screen.

FIG. 15 is a flowchart showing a flow of total amount calculation processing.

FIG. 16 is a flowchart showing a flow of a program module download process in the server.

FIG. 17 is a flowchart showing a flow of a program module download process in the mobile terminal device.

FIG. 18 is a diagram showing the contents of an operation file.

FIG. 19 is a flowchart showing a flow of a process of transmitting an operation file in the server.

FIG. 20 is a flowchart showing a flow of an operation file reception process in the mobile terminal device.

FIG. 21 is a diagram showing a user table of a server.

FIG. 22 is a diagram showing a user table of the mobile terminal device.

FIG. 23 is a flowchart showing the flow of generation and transfer processing of a temporary authentication key, a temporary authentication flag, and the number of times of free use in the server.

FIG. 24 is a flowchart showing a flow of generation and transfer processing of a temporary authentication key, a temporary authentication flag, and a free use count in the mobile terminal device.

FIG. 25 is a flowchart showing the flow of application execution processing.

FIG. 26 is a flowchart showing the flow of a process of generating a formal authentication key and a formal authentication flag in the server.

FIG. 27 is a flowchart showing a flow of a process of receiving a formal authentication key and a formal authentication flag in the mobile terminal device.

FIG. 28 is a functional block diagram of an application providing system according to a second embodiment of the present invention.

FIG. 29 is a transition state diagram for explaining rewriting of a program module on a memory, (a) is a download state, (b) is a program module expansion state, and (c).
Shows a program module deletion state, and (d) shows a program module writing state.

FIG. 30 is a flowchart showing the flow of a program module revision process in the server.

FIG. 31 is a flowchart showing the flow of a program module revision process in the mobile terminal device.

[Explanation of symbols]

1,10 server 1a module storage means 1b Module extraction means 1c module transmission means 2 clients 2a Transmission request input means 2b Request transmission means 2c module storage means 2d execution means 11 User Management Department 12 Read-out section 13 module storage 14 User information storage 15 Charge calculator 16 module extractor 17 File creation department 18 Authentication Department 19 Revision notice section 20a, 20b, 20c Mobile terminal device 21 Input / output section 22 Module writing section 23 Receiving module storage 24 File writing section 25 Authentication receiver 26 Execution Department 27 Revised rewriting section

Claims (10)

[Claims] 1. In an application providing system for providing an application via a network, a module storage unit for storing a program module divided for each function of the application, and a program module requested to be transmitted in order to create a desired application. A module extractor for extracting from the module storage means, a module transmitter for transmitting the program module extracted by the module extractor, a transmission request input means for inputting the transmission request, and A request transmitting means for transmitting a transmission request to the server, a module storing means for storing a program module transmitted from the module transmitting means, and a program module stored in the module storing means are implemented. Application providing system characterized by comprising an execution unit, and a client having a, a to. 2. Charge information is added to the program module stored in the module storage means, and the server has a charge calculating means for calculating the total amount of the program modules requested to be transmitted from the charge information. The application providing system according to claim 1, further comprising: a display unit configured to receive and display the total amount of money. 3. The use count information is added to the program module stored in the module storage means, and the server transmits the minimum use count information among the program modules requested to be transmitted. The client may further include means, the client may further include use count information receiving means for receiving the minimum use count information, and the executing means may execute the program module for the use count indicated in the minimum use count information. The application providing system according to claim 1. 4. The server further comprises an operation file creating means for creating an operation file based on operation specifying information specifying an operation of the program module requested to be transmitted, and the client is The system further comprises input operation information input means, transmission means for transmitting the operation designation information, and operation file reception means for receiving the operation file, and the execution means executes the program module according to the operation file. The application providing system according to claim 1, wherein: 5. The application providing system according to claim 4, wherein the operation file is described in a script language. 6. The server further comprises revision information transmission means for transmitting revision information when the program module stored in the module storage means is revised, and the client receives the revision information. The application providing system according to claim 1, further comprising: a revision information display unit that displays the revision information. 7. A module storage unit for storing a program module, which stores a program module divided for each function of an application, and a module extraction unit, for extracting a program module requested to be transmitted to create a desired application from the module storage unit. And a module transmitting means for transmitting the program module extracted by the module extracting means to a transmission request source, and a computer-readable recording medium recording a program for causing the function to function. 8. A module storage means for storing a program module for a computer, which is divided for each function of an application, and a module extraction for extracting a program module requested to be transmitted to create a desired application from the module storage means. And a program for functioning as means and module transmission means for transmitting the program module extracted by the module extraction means to a transmission request source. 9. A transmission request input means for inputting a transmission request of a program module required for creating a desired application to a computer, and a program module in which the transmission request is divided for each function of the application. A request transmitting unit for transmitting to a server for storing, a module storing unit for storing a program module transmitted from the server, and an executing unit for executing the program module stored in the module storing unit, for performing the functions. A computer-readable recording medium recording a program. 10. A computer, comprising: a transmission request input means for inputting a transmission request of a program module required to create a desired application; and a program module in which the transmission request is divided for each function of the application. A request transmitting unit for transmitting to a server for storing, a module storing unit for storing a program module transmitted from the server, and an executing unit for executing the program module stored in the module storing unit, for performing the functions. program.