JP6885152B2 - Information processing system, information processing device, information processing method, and information processing program - Google Patents

Description

The present invention relates to an information processing system, an information processing device, an information processing method, and an information processing program.

Among the companies that sell devices in a global environment, there are companies that set up bases in each region and develop application programs (hereinafter, simply referred to as "apps") that operate on the devices in each base. For example, device users have different tastes among regions such as Europe, North America, and Japan, and it is required to develop an application that can provide services suitable for each region.

The apps developed at each site are managed by the system installed at each site and sold within the site.

However, the tastes of users are not always completely different between regions, and similar requests may be requested by customers. In such a case, an application having the same function may be duplicately developed at a plurality of bases, which may lead to a decrease in development efficiency from the viewpoint of the entire company.

The present invention has been made in view of the above points, and an object of the present invention is to improve the diversion of a program developed for each region regarding equipment.

Therefore, in order to solve the above problems, the first information processing device , the second information processing device, and a plurality of information processing devices including the first information processing device and the second information processing device and a network are used. An information processing system including a third information processing device connected to the information processing device , wherein the first information processing device includes a first storage unit for storing a program developed in a first region and the first storage unit. A receiving unit that receives a program developed in the second region, which is stored in the information processing apparatus 2, via a network, a program stored in the first storage unit, and a receiving unit that receives the program. containing one or more programs selected by the user from among the programs, have a, a generation unit for generating a sales unit of said program, to said third information processing apparatus, acquires login information from the terminal For the authentication unit that authenticates the user based on the information processing unit, the acquisition unit that acquires the program based on the import request acquired from the terminal, and the information processing device corresponding to the base to which the user belongs among the plurality of information processing devices. And the transmitter that transmits the program acquired by the acquisition unit
To have a.

It is possible to improve the diversion of programs developed in each region regarding equipment.

It is a figure which shows the structural example of the information processing system in embodiment of this invention. It is a figure which shows the hardware configuration example of the application server in embodiment of this invention. It is a figure which shows the functional configuration example of the application server and the shared server in embodiment of this invention. It is a sequence diagram for demonstrating an example of the processing procedure of the release process of an application. It is a figure which shows the structural example of the user information storage part. It is a figure which shows the display example of a portal screen. It is a figure which shows the display example of the development top screen. It is a figure which shows the configuration example of the application information storage part. It is a figure which shows the display example of the application list screen. It is a figure which shows the structural example of the asset information storage part. It is a sequence diagram for demonstrating an example of the processing procedure of the import process of an application. It is a figure which shows the display example of the asset list screen. It is a figure which shows the display example of the asset detail screen. It is a figure which shows the display example of the import completion screen. It is a sequence diagram for demonstrating an example of a process procedure of a package creation process. It is a sequence diagram for demonstrating an example of a process procedure of a package creation process. It is a figure which shows the display example of the customer management menu screen. It is a figure which shows the structural example of the package information storage part. It is a figure which shows the display example of a package list screen. It is a figure which shows the display example of the package new creation screen. It is a figure which shows the display example of the application selection screen. It is a figure which shows the configuration example of the license definition storage part. It is a figure which shows the display example of the license definition list screen. It is a figure which shows the display example of the license definition creation screen. It is a figure which shows the display example of the package creation completion screen. It is a figure which shows the display example of the license definition edit screen. It is a sequence diagram for demonstrating an example of the process procedure of the application initial data creation process. It is a figure which shows the display example of the editing application selection screen. It is a figure which shows the display example of the initial data edit screen. It is a sequence diagram for demonstrating an example of the processing procedure of the package editing process. It is a figure which shows the display example of a package basic setting screen. It is a figure which shows the display example of the package structure edit screen. It is a figure which shows the display example of the application addition screen. It is a figure which shows the display example of the initial data selection screen. It is a sequence diagram for demonstrating an example of a process procedure of a package installation process. It is a figure which shows the display example of the customer search screen. It is a figure which shows the structural example of the customer information storage part. It is a figure which shows the display example of the customer list screen. It is a figure which shows the display example of the customer information screen. It is a figure which shows the display example of a package selection screen. It is a figure which shows the display example of the license definition selection screen. It is a figure which shows the configuration example of the license storage part. It is a figure which shows the display example of the package addition completion screen. It is a sequence diagram for demonstrating an example of the processing procedure executed at the time of using an application. It is a figure which shows the display example of the initial screen. It is a figure which shows the display example of the license invalidation screen. It is a figure which shows the display example of an application screen.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a configuration example of an information processing system according to an embodiment of the present invention. The information processing system 1 is constructed across a plurality of bases (base A, base B, etc.) of a company (hereinafter, referred to as "company R") that uses the information processing system 1. Each base is set up for each sales area of products manufactured by Company R. The base is also a development and sales base of an application program (hereinafter referred to as "application") that operates on the image forming apparatus 40 manufactured by the company R. For example, bases may be set up in each region such as North America, Europe, and Japan. In addition, if it is in Japan, bases may be set up in more detailed areas such as each region or prefecture.

Each base includes an application server 10, one or more user terminals 30, one or more image forming devices 40, and the like. These are connected via a network such as the Internet. When the reference is limited to the application server 10, the user terminal 30, and the image forming apparatus 40 of the base A, "a" is added to the end of these codes. Similarly, when the reference is limited to the application server 10, the user terminal 30, and the image forming apparatus 40 of the base B, "b" is added to the end of these codes. When the bases are not distinguished, "a" and "b" are not added to each code.

Each image forming apparatus 40 is an image forming apparatus manufactured and sold by the company R, and is installed in the customer of the company R. Each image forming apparatus 40 can communicate with the application server 10 of the base to which the image forming apparatus 40 belongs.

The application server 10 is one or more computers used for developing and executing an application related to the image forming apparatus 40, creating and deploying a package, and the like. A package is a collection of one or more apps organized by a certain classification or criterion. In the present embodiment, the application is sold in package units. Therefore, a package is a unit of sale for an app.

In this embodiment, the application is configured by connecting programs called components. Therefore, the substance of the application is the information in which the connection relationship of the components (hereinafter referred to as "flow") and the setting information for each component are defined. The component is a componentized program and is executed on the application server 10. For example, a component that executes OCR (Optical Character Recognition) on image data (hereinafter referred to as "OCR component"), a component that authenticates a user, and a component that distributes data to cloud storage or the like (hereinafter, "distribution"). There are "components") and so on. For example, when an application composed of an OCR component and a distribution component is installed in the image forming apparatus 40 and the image forming apparatus 40 is instructed to execute the application, the image forming apparatus 40 scans the image data from the original. Is transmitted to the application server 10 of the base to which the image forming apparatus 40 belongs. The application server 10 executes the components that make up the application. That is, the application server 10 executes OCR on the image data and distributes the text data generated by the OCR to the cloud storage.

The user terminal 30 is a terminal used by the user of the information processing system 1. The user of the information processing system 1 is a person who develops an application, creates a package, sells the application to a customer, and basically belongs to the company R. A PC (Personal Computer), a smartphone, a tablet terminal, or the like may be used as the user terminal 30.

The application server 10 and the user terminal 30 of each base can communicate with the shared server 20 via a network such as the Internet.

The shared server 20 is one or more computers that execute processing for enabling sharing of applications and packages individually developed or created at each base across bases. Hereinafter, when an application and a package are not distinguished, they are referred to as "assets".

FIG. 2 is a diagram showing a hardware configuration example of the application server according to the embodiment of the present invention. The application server 10 of FIG. 2 has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, and the like, which are connected to each other by a bus B, respectively.

The program that realizes the processing on the application server 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed in the auxiliary storage device 102 from the recording medium 101 via the drive device 100. However, the program does not necessarily have to be installed from the recording medium 101, and may be downloaded from another computer via the network. The auxiliary storage device 102 stores the installed program and also stores necessary files, data, and the like.

The memory device 103 reads and stores the program from the auxiliary storage device 102 when the program is instructed to start. The CPU 104 executes the function related to the application server 10 according to the program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.

The shared server 20 may also have the same hardware as in FIG.

FIG. 3 is a diagram showing a functional configuration example of the application server and the shared server according to the embodiment of the present invention.

In FIG. 3, the application server 10 includes an application development management unit 11, a base asset management unit 12, a package management unit 13, a customer information management unit 14, a device management unit 15, a component execution unit 16, and the like. Each of these parts is realized by a process of causing the CPU 104 to execute one or more programs installed in the application server 10. The application server 10 also has an application information storage unit 121, an application storage unit 122, a package information storage unit 123, a customer information storage unit 124, a device information storage unit 125, a task information storage unit 126, a component information storage unit 127, and a license definition. The storage unit 128, the license storage unit 129, and the like are used. Each of these storage units can be realized by using, for example, an auxiliary storage device 102, a storage device that can be connected to the application server 10 via a network, or the like.

The application development management unit 11 supports the development of applications at the base. The application information, which is the bibliographic information of the developed application, is stored in the application information storage unit 121. The substance of the application is stored in the application storage unit 122.

The base asset management unit 12 imports applications developed at other bases, releases (publishes) applications developed at the bases, and the like. Importing an application means receiving an entity of an application at another base and storing it in the application storage unit 122.

The package management unit 13 supports the creation and editing of packages. The package information, which is information about the created package, is stored in the package information storage unit 123.

The customer information management unit 14 registers customer information in the customer information storage unit 124, searches for customer information from the customer information storage unit 124, and the like. The customer information storage unit 124 stores customer information of customers at the base to which the application server 10 belongs. In the present embodiment, the customer means a customer for the company R. For example, the user of the image forming apparatus 40 is a customer.

The device management unit 15 manages each image forming apparatus 40 used by the customer at the base. For example, the device management unit 15 executes a process for installing a package for each of the image forming devices 40. Information about each image forming apparatus 40 used by the customer in the base is stored in the device information storage unit 125. The task information storage unit 126 stores information related to device management tasks such as which package should be installed for which customer's image forming apparatus 40. The device management unit 15 manages the image forming apparatus 40 based on the information.

The component execution unit 16 controls the execution of the components constituting the application selected as the execution target in the image forming apparatus 40. Information about each component is stored in the component information storage unit 127.

On the other hand, the shared server 20 has an authentication unit 21, a portal unit 22, an asset management unit 23, an import unit 24, and the like. Each of these parts is realized by a process of causing the CPU 104 to execute one or more programs installed on the shared server 20. The shared server 20 also uses the user information storage unit 211, the asset information storage unit 212, and the base information storage unit 213. Each of these storage units can be realized by using, for example, an auxiliary storage device of the shared server 20, a storage device that can be connected to the shared server 20 via a network, or the like.

The authentication unit 21 authenticates a user who attempts to log in to the information processing system 1. The user information storage unit 211 stores information about each user of the information processing system 1.

The portal unit 22 provides a virtual environment that serves as an entrance to the information processing system 1.

The asset management unit 23 manages the assets that are permitted to be published to other bases among the assets developed for each base. Information about such assets is stored in the asset information storage unit 212.

The import unit 24 executes a process for making the application registered in the asset information storage unit 212 available at a base other than the registration source base.

Information about each base is stored in the base information storage unit 213. For example, the base information storage unit 213 stores the IP address and the like of the application server 10 of each base.

The license definition storage unit 128 stores license definition information (hereinafter referred to as “license definition”) related to the package. Multiple license definitions can be generated for one package.

The license storage unit 129 stores license data issued to the purchaser of the package based on the license definition.

Hereinafter, the processing procedure executed in the information processing system 1 will be described. FIG. 4 is a sequence diagram for explaining an example of the processing procedure of the release processing of the application. FIG. 4 describes a case where the processing procedure is executed for the base A, but the processing procedure can be similarly executed at other bases as well.

In the initial state of FIG. 4, the user terminal 30a displays a login screen for the shared server 20. When the user name and password are input to the login screen, the user terminal 30a transmits a login request including the user name and password to the shared server 20 (S101).

When the authentication unit 21 of the shared server 20 receives the login request, the authentication unit 21 collates the user name and password included in the login request with the user name and password stored in the user information storage unit 211, and the user. Is authenticated (S102).

FIG. 5 is a diagram showing a configuration example of the user information storage unit. In FIG. 5, the user information storage unit 211 stores a user name, password, name, affiliation base, and the like for each user.

The user name is identification information for each user. The password is the correct password for the username. The name is the user's name. The affiliation base is the identification information of the base to which the user related to the user name belongs (hereinafter, referred to as "base ID").

When the authentication is successful, the portal unit 22 generates a portal screen (S103) and returns the portal screen to the user terminal 30a (S104). The user terminal 30a displays the portal screen (S105).

FIG. 6 is a diagram showing a display example of the portal screen. As shown in FIG. 6, the portal screen 510 includes a menu 511. The menu 511 includes menu items according to the work purpose of the user. When releasing an application managed by the application server 10a, "application development" is selected.

When "application development" is selected in the menu 511, the user terminal 30a transmits a development top screen acquisition request to the application server 10a set as a link destination for "application development" (S106). ). That is, the portal unit 22 sets the link to the application server 10 corresponding to the affiliation ID of the logged-in user to "application development" of the menu 511 and generates the portal screen 510.

The application development management unit 11 of the application server 10a returns the development top screen to the user terminal 30a in response to the reception of the acquisition request (S107). The user terminal 30a displays the development top screen (S108).

FIG. 7 is a diagram showing a display example of the development top screen. In FIG. 7, the development top screen 520 includes buttons 521 to 523 and the like. Button 521 is a button for receiving a flow creation instruction or the like. Button 522 is a button for accepting registration or update of a component. Button 523 is a button for accepting screen settings and the like of the application.

When the button 521 or the button 523 is selected, the user terminal 30a transmits a request for acquiring the application list to the application server 10a (S109). The application development management unit 11 of the application server 10a acquires a list of application information from the application information storage unit 121 in response to the acquisition request (S110).

FIG. 8 is a diagram showing a configuration example of the application information storage unit. As shown in FIG. 8, in the application information storage unit 121, the application ID, name, icon, function category, developer, supported language, outline, registration date and time, paid / free, charge, and disclosure range are provided for each application. App information including etc. is stored.

The application ID is identification information for each application. In the present embodiment, the application ID is identification information that can identify each application across a plurality of bases. Such identification information can be easily generated at each base by including, for example, the base ID as a part of the application ID.

The name is the name of the application and is used for display and the like. The icon is an icon image used for displaying the application. The function category is a category to which the function of the application belongs, and is used for searching the application, for example. Functional categories include scanning, printing, conversion, storage, email, document analysis, construction, manufacturing, medical, and others. Two or more functional categories may be set for one app. The developer is the identification name of the developer of the application. The supported languages are the languages supported by the application (English, Japanese, etc.), and multiple specifications can be specified. The overview is a free-form overview of the app. The registration date and time is the date and time when the application is registered (stored in the application information storage unit 121 and the application storage unit 122). Paid / free is information indicating whether the application is paid or free. The fee is the fee for the paid application. The disclosure range is the range in which the application is allowed to be published. The range is specified by the base or the customer. That is, the disclosure range is a set of base IDs of bases where the application is permitted to be published, customer IDs which are identification information of customers who are permitted to publish the application, and the like. By setting the disclosure range for each application, it is possible to prevent the application from leaking to an area not intended by the user. If there is no value in the disclosure range, it means that the disclosure range is not limited.

In step S110, all the application information stored in the application information storage unit 121 may be acquired. Subsequently, the application development management unit 11 generates an application list screen including a list of acquired application information (S111). Subsequently, the application development management unit 11 returns the application list screen to the user terminal 30a (S112). The user terminal 30a displays the application list screen (S113).

FIG. 9 is a diagram showing a display example of the application list screen. As shown in FIG. 9, a part of the application information is displayed on the application list screen 530 for each application.

When the user selects an application that is permitted to be published to another base and presses the release button 531, the user terminal 30a transmits a release request including the application ID of the selected application to the application server 10a (S114). .. In addition, a plurality of applications may be selected as release targets.

Upon receiving the release request, the application development management unit 11 of the application server 10a acquires the application information corresponding to the application ID included in the release request from the application information storage unit 121 (S115). Subsequently, the application development management unit 11 transmits a release request (publication request) including the acquired application information and the base ID of the base A to the shared server 20 (S116).

Upon receiving the release request, the asset management unit 23 of the shared server 20 stores the application information and the base ID included in the release request in the asset information storage unit 212 (S117).

FIG. 10 is a diagram showing a configuration example of the asset information storage unit. As shown in FIG. 10, the asset information storage unit 212 has an asset ID, a name, an icon, a function category, a developer, a supported language, an outline, a registration date and time, and a fee for each released (published) asset. Store asset information including free of charge, fee, release source and disclosure range.

The asset ID is identification information for each asset. If the asset is an application, the application ID of the application is the asset ID. If the asset is a package, the identification information of the package (hereinafter, referred to as "package ID") is used as the asset ID. The name, icon, function category, developer, supported language, outline, registration date and time, paid / free, and fee are as described in FIG. However, the registration date and time is the date and time stored in the asset information storage unit 212. The release source is the base ID of the base where the asset is released. That is, the base ID received in step S117 is stored as the release source. The disclosure range is the range in which the disclosure of assets is permitted, and the meaning is the same as the disclosure range of the application.

By executing the processing procedure shown in FIG. 4, the application of each base can be referred to from other bases. However, the substance of the released application is not managed by the shared server 20. Therefore, the base B can know the existence of the application released by the base A, but cannot use the application at the base B. In order to make the application available at the base B, it is necessary to take a copy of the application into the base B.

FIG. 11 is a sequence diagram for explaining an example of the processing procedure of the import processing of the application. FIG. 11 describes a process of importing the application released from the base A into the base B by the processing procedure of FIG. Therefore, the processing procedure of FIG. 11 is executed with the instruction of the user of the base B as an opportunity. Further, at the start of FIG. 11, it is assumed that the portal screen 510 (FIG. 6) is displayed on the user terminal 30b. That is, it is assumed that steps S101 to S105 of FIG. 4 have been executed for the user terminal 30b.

When the "asset list" of the menu 511 of the portal screen 510 (FIG. 6) is selected by the user of the base B, the user terminal 30b transmits a request for acquiring the asset list to the shared server 20 (S201). Upon receiving the acquisition request, the asset management unit 23 of the shared server 20 acquires a list of asset information from the asset information storage unit 212 (FIG. 10) (S202). At this time, the acquisition target is the asset information including the base ID of the base B in the disclosure range. Subsequently, the asset management unit 23 generates an asset list screen including the list (S203). Subsequently, the asset management unit 23 returns the asset list screen to the user terminal 30b (S204). The user terminal 30b displays the asset list screen (S205).

FIG. 12 is a diagram showing a display example of the asset list screen. In FIG. 12, the asset list screen 540 includes a list area 541, a filter area 542, and the like. The list area 541 is an area in which a list of asset information is displayed. The filter area 542 is an area for receiving the setting of the filter (narrowing condition) for the asset information to be displayed in the list area 541. In FIG. 12, it is possible to narrow down the display target by the function category, the developer, and paid / free of charge.

When any row (asset information) is selected in the list area 541, the user terminal 30b uses the asset of the asset corresponding to the row (hereinafter referred to as “target asset”) according to the definition of the asset list screen 540. The details screen is displayed (S206).

FIG. 13 is a diagram showing a display example of the asset detail screen. In FIG. 13, the asset detail screen 550 includes a detail area 551, an import button 552, and the like. The detail area 551 is an area for displaying the configuration information of the asset information, which is not displayed in the list area 541 of the asset list screen 540 for the target asset. The import button 552 is a button for receiving an instruction to import the target asset.

When the import button 552 is pressed on the asset detail screen 550, the user terminal 30b transmits an import request including the asset ID of the target asset to the shared server 20 (S207). When the asset management unit 23 of the shared server 20 receives the import request, the asset management unit 23 acquires the release source base ID corresponding to the asset ID included in the import request from the asset information storage unit 212 (S208). Subsequently, the asset management unit 23 transmits a request for acquiring an asset including the asset ID (here, it is assumed to be the application ID) to the application server 10a corresponding to the base ID (S209). The IP address and the like of the application server 10 corresponding to each base ID are stored in the base information storage unit 213.

When the base asset management unit 12 of the application server 10a receives the acquisition request, the base asset management unit 12 acquires the substance of the application corresponding to the application ID included in the acquisition request from the application storage unit 122 and corresponds to the application ID. The application information to be used is acquired from the application information storage unit 121 (S210). Subsequently, the base asset management unit 12 returns the application and the application information to the asset management unit 23 of the sharing server 20 (S211).

When the asset management unit 23 of the shared server 20 receives the application and application information, the asset management unit 23 transmits the application and application information to the application server 10b corresponding to the base to which the login user of the user terminal 30b of the source of the import request belongs (). S212). The base to which the login user belongs can be specified for the login user based on the base ID stored in the user information storage unit 211. Further, the IP address of the application server 10b corresponding to the base ID can be obtained from the base information storage unit 213.

When the base asset management unit 12 of the application server 10b receives the application and the application information, the base asset management unit 12 stores the application in the application storage unit 122 of the application server 10b in association with the application ID included in the application information. The application information is stored in the application information storage unit 121 of the application server 10b (S213). As a result, the application developed at the base A is incorporated into the base B. Subsequently, the base asset management unit 12 of the application server 10b returns a response indicating the completion of importing to the shared server 20 (S214).

In response to the response, the shared server 20 returns the import completion screen to the user terminal 30b (S215). The user terminal 30b displays the import completion screen (S216).

FIG. 14 is a diagram showing a display example of the capture completion screen. In FIG. 14, the capture completion screen 560 includes a message indicating that the capture is completed.

Next, the creation of the package will be described. 15 and 16 are sequence diagrams for explaining an example of the processing procedure of the package creation process. FIG. 15 describes an example in which a package is created at the base B. Therefore, the processing procedure of FIG. 15 is executed with the instruction of the user of the base B as an opportunity. Further, in the initial state of FIG. 15, it is assumed that the portal screen 510 (FIG. 6) is displayed on the user terminal 30b. That is, it is assumed that steps S101 to S105 of FIG. 4 have been executed for the user terminal 30b.

When the "customer information" of the menu 511 is selected by the user of the base B, the user terminal 30b displays the customer management menu screen with respect to the application server 10b set as the link destination for the "customer information". The acquisition request is transmitted (S301). That is, the portal unit 22 sets the link to the application server 10 corresponding to the affiliation ID of the logged-in user in the "customer information" of the menu 511 to generate the portal screen 510.

Upon receiving the acquisition request, the customer information management unit 14 of the application server 10b returns the customer management menu screen to the user terminal 30b (S302). The user terminal 30b displays the customer management menu screen (S303).

FIG. 17 is a diagram showing a display example of the customer management menu screen. In FIG. 17, the customer management menu screen 570 includes links 571-574.

When the link 574 is selected, the user terminal 30b transmits a request for acquiring the package list to the application server 10b (S304). The package management unit 13 of the application server 10b acquires a list of package information from the package information storage unit 123 in response to the acquisition request (S305).

FIG. 18 is a diagram showing a configuration example of the package information storage unit. As shown in FIG. 18, the package information storage unit 123 stores package information including a package ID, a package name, a description, an application ID group, a disclosure range, a license control, and the like for each package. The name is the name of the package. The description is about the package. The application ID group is a set of application IDs of each application constituting the package. The disclosure range is the disclosure range of the package. The license control is information indicating the effectiveness of the license control of the package. That is, the license control is information indicating whether or not the package is subject to license control. License control takes a valid or invalid value. Valid indicates that the package is subject to license control. Invalid indicates that the package is not subject to license control.

In step S305, all the package information stored in the package information storage unit 123 may be acquired. Subsequently, the package management unit 13 generates a package list screen including a list of acquired package information (S306). Subsequently, the package management unit 13 returns the package list screen to the user terminal 30b (S307). The user terminal 30b displays the package list screen (S308).

FIG. 19 is a diagram showing a display example of the package list screen. In FIG. 19, the package list screen 580 includes a package list area 581, a create button 582, and the like. In the package list area, the package name and description are displayed for each package. The create button 582 is a button for receiving an instruction to create a new package.

When the create button 582 is pressed by the user, the user terminal 30b transmits a package creation request to the application server 10b (S309). The package management unit 13 of the application server 10b returns a new package creation screen to the user terminal 30b in response to the request (S310). The user terminal 30b displays the package new creation screen (S311).

FIG. 20 is a diagram showing a display example of a new package creation screen. In FIG. 20, the package new creation screen 590 includes a package information input area 591, a next button 592, and the like. The package information input area 591 is an area for receiving input such as a package name, description, license control, and disclosure range of a newly created package. Regarding the disclosure range, it is possible to select the method of specifying the disclosure range. FIG. 20 shows an example in which "Publication designated by base" is selected, and check boxes are arranged for each base. Therefore, in this case, the disclosure range can be specified by the base. As another designation method, for example, there is "customer designated disclosure". In this case, the disclosure range is specified by inputting one or more customer IDs.

When the package information is input to the package information input area 591 and the next button 592 is pressed, the user terminal 30b transmits the input package information to the application server 10b (S312).

When the package management unit 13 of the application server 10b receives the package information, the package management unit 13 stores the package information. Subsequently, the package management unit 13 acquires a list of application information from the application information storage unit 121 of the application server 10b (S313). Subsequently, the package management unit 13 transmits a request for acquiring a list of asset information to the shared server 20 (S314). The acquisition request includes the base ID of the base B. In response to the acquisition request, the asset management unit 23 of the shared server 20 displays a list of asset information including the base ID of the base B in the disclosure range (that is, disclosure to the base B is permitted) from the asset information storage unit 212. It is acquired (S315) and the list is returned to the application server 10b (S316).

Upon receiving the list, the package management unit 13 of the application server 10b generates an application selection screen based on the list and the list of application information acquired in step S313 (S317). Specifically, an application selection screen including each application managed by the application server 10b and each application published to each base on the shared server 20 as options is generated. Subsequently, the package management unit 13 returns the application selection screen to the user terminal 30b (S318). The user terminal 30b displays the application selection screen (S319).

FIG. 21 is a diagram showing a display example of the application selection screen. In FIG. 21, the application selection screen 610 includes application information of each application as an option. Here, the options include the application information managed in the base B and the application information published in the shared server 20. Further, the application information managed in the base B also includes the application information fetched from the base A by executing the processing procedure of FIG. Therefore, in the present embodiment, it is possible to create a package including not only the application developed at the base B but also the application developed at another base.

When one or more applications are selected by the user and the creation button 611 is pressed, the user terminal 30b transmits the application ID group of each selected application to the application server 10b (S320). The package management unit 13 of the application server 10b adds the received application ID group to the package information stored in step S312, and stores the package information after the addition of the application ID group in the package information storage unit 123 (S321). ). At this time, the package management unit 13 generates a new package ID and assigns the package ID to the package information. The package related to the package information newly stored in the package information storage unit 123 is hereinafter referred to as "target package".

Here, when the application ID group received in step S320 includes an application ID (hereinafter, referred to as "shared application ID") that is not stored in the application information storage unit 121 of the application server 10b. That is, when the application ID of the asset information acquired from the shared server 20 is included, step S331 and subsequent steps are executed. This is because the substance of the application constituting the package is automatically imported into the application server 10b.

In step S331, the base asset management unit 12 of the application server 10b transmits an acquisition request for the application including the shared application ID to the shared server 20 (S331). The asset management unit 23 of the shared server 20 executes an application acquisition process with respect to the shared application ID (S332). The application acquisition process is a process corresponding to steps S209 to S211 in FIG. That is, the substance of the application and the application information of the application are acquired from the release source of the application related to the shared application ID.

Subsequently, the asset management unit 23 transmits the application and the application information to the application server 10b (S333). When the base asset management unit 12 of the application server 10b receives the application and the application information, the base asset management unit 12 stores the application in the application storage unit 122 of the application server 10b in association with the application ID included in the application information. The application information is stored in the application information storage unit 121 of the application server 10b (S334). Note that steps S333 and S334 are the same processes as steps S212 and S213 in FIG.

Subsequently, when the license control of the target package is enabled, the processing procedure of FIG. 16 is executed. In step S341 of FIG. 16, the package management unit 13 of the application server 10b acquires a list of license definitions stored in the license definition storage unit 128 of the application server 10b.

FIG. 22 is a diagram showing a configuration example of the license definition storage unit. As shown in FIG. 22, the license definition storage unit 128 stores a license definition ID, a license definition name, a valid period, a package ID, a valid state, and the like for each license definition. The license definition ID is identification information for each license definition. The license definition name is the name of the license definition. The validity period is the validity period of the license issued based on the license definition. In the present embodiment, the validity period can be set to be monthly (1 to 60 months), daily (1 to 30 days), or unlimited. However, the validity period may be set based on the period of a year or another unit. The package ID is the package ID of the package to which the license definition is applied. The valid state is information indicating the validity of the license definition. That is, the valid state takes a valid or invalid value. Valid indicates that license data can be issued using the license definition. Invalid means that license data cannot be issued using the license definition.

In step S341, all license definitions stored in the license definition storage unit 128 may be acquired.

Subsequently, the package management unit 13 generates a license definition list screen including a list of acquired license definitions (existing license definitions) (S342). Subsequently, the package management unit 13 returns the license definition list screen to the user terminal 30b (S343). The user terminal 30b displays the license definition list screen (S344).

FIG. 23 is a diagram showing a display example of the license definition list screen. In FIG. 23, the license definition list screen 750 includes a license definition list area 751, a creation button 752, a button 753, and the like. In the license definition list area, the license definition ID, validity period, validity status, etc. are displayed for each existing license definition. The create button 752 is a button for receiving an instruction to create a new license definition.

When the create button 752 is pressed by the user, the user terminal 30b transmits a license definition creation request to the application server 10b (S345). The package management unit 13 of the application server 10b returns the license definition creation screen to the user terminal 30b in response to the request (S346). The user terminal 30b displays the license definition creation screen (S347).

FIG. 24 is a diagram showing a display example of the license definition creation screen. In FIG. 24, the license definition creation screen 760 includes a license definition input area 761 and a button 762. The license definition input area 761 is an area for receiving input of values of each item constituting the license definition.

When the license definition is input to the license definition input area 761 and the button 762 is pressed, the user terminal 30b transmits the input license definition to the application server 10b (S348).

Upon receiving the license definition, the package management unit 13 of the application server 10b stores (registers) the license definition in the license definition storage unit 128 (S349). The package ID of the target package is set in the package ID of the license definition.

Subsequently, the package management unit 13 returns the package creation completion screen to the user terminal 30b (S350). The user terminal 30b displays the package creation completion screen (S351).

FIG. 25 is a diagram showing a display example of the package creation completion screen. As shown in FIG. 25, the package creation completion screen 770 displays a message indicating that the package creation is completed. If the license control of the target package is "invalid", steps S350 and S351 are executed following step S334 of FIG.

As is clear from the fact that a plurality of license definition IDs are associated with the same package ID in FIG. 22, a plurality of license definitions may be created for one package. That is, step S344 and subsequent steps may be executed a plurality of times for the same package.

By the way, as shown in the balloon of FIG. 23, when the button 753 of the license definition list screen 750 is pressed, the menu 754 is displayed. Menu 754 is a menu for accepting an operation for the license definition selected (checked) in the license definition list area 751.

For example, when "deletion" is selected, the user terminal 30b transmits a deletion request including the license definition ID of the selected license definition to the application server 10b. The package management unit 13 of the application server 10b deletes the license definition related to the license definition ID from the license definition storage unit 128.

When "valid" or "invalid" is selected, the user terminal 30b transmits a request for changing the valid state including the license definition ID of the selected license definition to the application server 10b. The package management unit 13 of the application server 10b changes the valid state of the license definition related to the license definition ID in the license definition storage unit 128 to the selected state (“valid” or “invalid”).

When "Edit" is selected, the user terminal 30b displays the license definition edit screen.

FIG. 26 is a diagram showing a display example of the license definition edit screen. In FIG. 26, the license definition edit screen 780 includes a license definition edit area 781, a button 782, and the like. The license definition editing area 781 is an area for displaying the value of each item constituting the license definition selected in the license definition list area 751 of the license definition list screen 750 and accepting the change of the value. When the license definition is changed for the license definition editing area 781 and the button 762 is pressed, the user terminal 30b transmits the changed license definition to the application server 10b. As a result, the same processing procedure as in step S349 or later is executed, and the selected license definition change is reflected in the license definition storage unit 128.

As described above, in the present embodiment, since the license definition can be defined for each package, the license definition can be generated according to the business form of the customer. Further, since the license definition can be created by the navigation style in the process of the package creation process, the license definition can be generated at the same time when the product designer designs the package (product). Moreover, since a plurality of license definitions can be generated for one package, various business models can be supported.

Subsequently, the processing procedure executed when the link 573 is selected on the customer management menu screen 570 (FIG. 17) will be described.

FIG. 27 is a sequence diagram for explaining an example of the processing procedure of the application initial data creation process.

When the link 573 of the customer management menu screen 570 (FIG. 17) is selected, the user terminal 30b transmits a request for editing the application initial data to the application server 10b (S401). The initial application data refers to data including the name of the application, an icon, and setting information for each component constituting the application, and constitutes a part of the substance of the application. "Initial" means "default". That is, the data including the setting information created as the default setting at the time of creating the application is the initial data.

The package is created with a certain degree of clarification of the target customer, such as for the industry. In this case, it is possible to create a product that is more attractive to the customer by using the name and icon of the app as terms that match the business of the customer targeted by the package, rather than simply indicating the function of the app. it can. Therefore, in the present embodiment, it is possible to edit the initial data of each application.

The application development management unit 11 of the application server 10b acquires a list of application information from the application information storage unit 121 in response to the editing request (S402). Subsequently, the application development management unit 11 generates an editing application selection screen for selecting an application for which the initial data is to be edited from the list (S403). Subsequently, the application development management unit 11 returns the editing application selection screen to the user terminal 30b (S404). The user terminal 30b displays the editing application selection screen (S405).

FIG. 28 is a diagram showing a display example of the editing application selection screen. As shown in FIG. 28, the icons of each application managed in the base B are arranged in a selectable state on the editing application selection screen 620.

When any of the applications is selected by the user, the user terminal 30b transmits a request for acquiring initial data including the application ID of the selected application to the application server 10b (S406). When the application development management unit 11 of the application server 10b receives the acquisition request, the application development management unit 11 acquires the initial data of the application corresponding to the application ID included in the acquisition request from the application storage unit 122 (S407). Subsequently, the application development management unit 11 generates an initial data editing screen for accepting editing of the initial data (S408). Subsequently, the application development management unit 11 transmits the initial data editing screen to the user terminal 30b (S409). The user terminal 30b displays the initial data editing screen (S410).

FIG. 29 is a diagram showing a display example of the initial data editing screen. As shown in FIG. 29, the content of the current initial data is shown on the initial data editing screen 630. When the button 631 is pressed by the user, a screen for accepting setting changes of each item (icon, name, setting information, etc.) of the initial data is displayed. The user edits the initial data via the screen.

When the user inputs an instruction to complete editing of the initial data, the user terminal 30b transmits the edited initial data and the application ID of the application whose initial data is to be edited to the application server 10b (S411). .. The application development management unit 11 of the application server 10b associates the initial data with the application corresponding to the application ID among the applications stored in the application storage unit 122 (S412). As a result, new initial data is associated with the application. That is, a plurality of initial data can be associated with one application. Which of the multiple initial data is valid can be selected for each package.

By the way, even if the package is created once, if the package configuration does not meet the market requirements, it is expected that the product power of the package will be improved by changing the apps that make up the package and the initial data of each app. It may be possible to do so. In consideration of such a case, in the present embodiment, it is possible to edit the configuration of the package.

FIG. 30 is a sequence diagram for explaining an example of the processing procedure of the package editing process. In the initial state of FIG. 30, it is assumed that the package list screen 580 (FIG. 19) is displayed on the user terminal 30b.

Each package name displayed in the package list area 581 of the package list screen 580 (FIG. 19) has a link to a package edit request. When one of the package names is selected by the user, the user terminal 30b makes an application for editing the package including the package ID of the package corresponding to the selected package name (hereinafter, referred to as "target package"). It is transmitted to the server 10b (S501). When the package management unit 13 of the application server 10b receives the edit request, the package management unit 13 acquires the package information corresponding to the package ID included in the edit request from the package information storage unit 123 (S502). Subsequently, the package management unit 13 generates a package basic setting screen based on the package information (S504). Subsequently, the package management unit 13 returns the package basic setting screen to the user terminal 30b. The user terminal 30b represents the package basic setting screen (S505).

FIG. 31 is a diagram showing a display example of the package basic setting screen. In FIG. 31, the package basic setting screen 640 includes a package name input area 641 and an explanatory input area 642. In each of these areas, the package name or description set for the target package is displayed.

When the package name or description is edited and the button 643 is pressed by the user, the user terminal 30b transmits the edited package name and description to the application server 10b (S506). Even if the editing is not performed, when the button 643 is pressed, the package name and the description displayed in the package name input area 641 and the explanation input area 642 are transmitted to the application server 10b.

The package management unit 13 of the application server 10b stores the received package name and description. Subsequently, the package management unit 13 acquires the application information corresponding to each application ID constituting the application ID group included in the package information of the target package from the application information storage unit 121 (S507). Subsequently, the package management unit 13 generates a package configuration edit screen based on the application information (S508). Subsequently, the package management unit 13 returns the package configuration edit screen to the user terminal 30b (S509). The user terminal 30b displays the package configuration edit screen (S510).

FIG. 32 is a diagram showing a display example of the package configuration edit screen. In FIG. 32, the package configuration edit screen 650 displays a list of application information of each application included in the target package. On the package configuration edit screen 650, it is possible to delete or change the setting information for each application.

Here, when the button 651 is pressed, the user terminal 30b transmits an application addition request to the application server 10b (S511). Upon receiving the additional request, the package management unit 13 of the application server 10b acquires a list of application information from the application information storage unit 121 (S512). Subsequently, the package management unit 13 generates an application addition screen in which each application information included in the acquired list is a candidate for addition to the package (S513). The application information of the application already included in the target package may be excluded from the addition candidates. Further, the same process as in steps S314 to S316 of FIG. 15 may be executed, and the application information published on the shared server 20 may be included in the additional candidates. Subsequently, the package management unit 13 returns the application addition screen to the user terminal 30b (S514). The user terminal 30b displays the application addition screen (S515).

FIG. 33 is a diagram showing a display example of the application addition screen. In FIG. 33, the application addition screen 660 displays a list of application information of each application that is a candidate for addition to the target package.

When any one or more application information is selected on the application addition screen 660 and the button 661 is pressed, the user terminal 30b transmits the application ID corresponding to the selected application information to the application server 10b (S516). .. When the package management unit 13 of the application server 10b receives the application ID, the package management unit 13 stores the application ID.

Subsequently, the package management unit 13 acquires the initial data of the application (hereinafter, referred to as “additional application”) related to the application ID from the application storage unit 122 (S517). For apps that have multiple initial data associated with them, multiple initial data will be acquired. Subsequently, the package management unit 13 generates an initial data selection screen for selecting valid initial data for the additional application in the target package (S518). Subsequently, the package management unit 13 returns the initial data selection screen to the user terminal 30b (S519). The user terminal 30b displays the initial data selection screen (S520).

FIG. 34 is a diagram showing a display example of the initial data selection screen. In FIG. 34, the initial data selection screen 670 displays a list of initial data associated with the additional application. Initial data may be created for each language, for example, for English or Japanese.

When any of the initial data is selected from the list and the button 671 is pressed, the user terminal 30b transmits the selected initial data to the application server 10b (S521). Upon receiving the initial data, the package management unit 13 of the application server 10b updates the package information stored in the package information storage unit 123 regarding the target package (S522). Specifically, the package name and description are updated with the package name and description received in step S506. Further, the application ID received in step S516 is added to the application ID group. Further, the initial data received in step S521 is associated with the package information. When the deletion of any of the applications is instructed on the package configuration edit screen 650, the application ID of the application is deleted from the application ID of the package information of the target package.

Subsequently, the processing procedure when the package is installed in the customer's image forming apparatus 40 will be described. FIG. 35 is a sequence diagram for explaining an example of the processing procedure of the package installation process. In the initial state of FIG. 35, it is assumed that the customer management menu screen 570 (FIG. 17) is displayed on the user terminal 30b.

When the link 572 on the customer management menu screen 570 (FIG. 17) is selected, the user terminal 30b transmits a customer information edit request to the application server 10b (S601). The customer information management unit 14 of the application server 10b returns the customer search screen to the user terminal 30b in response to the editing request (S602). The user terminal 30b displays the customer search screen (S603).

FIG. 36 is a diagram showing a display example of the customer search screen. In FIG. 36, the customer search screen 680 has a search condition input area for searching customer information. For example, it is possible to search by customer name, customer ID, or the like.

When the search condition is input and the button 681 is pressed, the user terminal 30b transmits a search request including the search condition to the application server 10b (S604). The customer information management unit 14 of the application server 10b searches the customer information storage unit 124 for customer information that matches the search condition (S605).

FIG. 37 is a diagram showing a configuration example of the customer information storage unit. In FIG. 37, the customer information storage unit 124 stores the customer ID, password, customer name, usage status, registration category, registrant, country, purchase package, issued license ID, and the like for each customer at the base.

The customer ID is identification information for each customer. The password is a password for the customer ID. The customer name is the name of the customer. The usage status is the usage status of each application or image forming device 40 by the customer. The registration category is a category related to the registration of customer information. The registrant is a registrant of customer information. Country is the name of the country in which the customer is located. The purchased package is a list of package IDs of the package purchased by the customer. The issued license ID is identification information of the license data issued for the purchased package.

Subsequently, the customer information management unit 14 generates a customer list screen including a list of the searched customer information (S606). Subsequently, the customer information management unit 14 returns the customer list screen to the user terminal 30b (S607). The user terminal 30b displays the customer list screen (S608).

FIG. 38 is a diagram showing a display example of the customer list screen. In FIG. 38, the customer list screen 690 displays a list of customer information that matches the search conditions.

When the user selects any one of the customer information, the user terminal 30b displays the customer information screen according to the definition of the customer list screen 690 (S609). Hereinafter, the customer related to the selected customer information is referred to as a "target customer".

FIG. 39 is a diagram showing a display example of the customer information screen. In FIG. 39, the customer information screen 710 includes a customer information area 711, a purchase package information area 712, and the like. In the customer information area 711, customer information of the target customer excluding the purchase package is displayed. In the purchase package information area 712, package information is displayed for each package ID included in the purchase package of the customer information of the target customer. In the example of FIG. 39, the package information is not displayed because the target customer has no purchase record of the package.

Subsequently, when the user presses the package addition button 713, the user terminal 30b transmits a package selection request to the application server 10b (S610). The customer information management unit 14 of the application server 10 acquires a list of package information from the package information storage unit 123 in response to the request (S611). Subsequently, the customer information management unit 14 generates a package selection screen including the list (S612). Subsequently, the customer information management unit 14 returns the package selection screen to the user terminal 30b (S613). The user terminal 30b displays the package selection screen (S614).

FIG. 40 is a diagram showing a display example of the package selection screen. In FIG. 40, the package selection screen 720 displays a list of packages. Note that FIG. 40 shows an example in which one package is sold at the base B.

When the user selects the package purchased by the customer and the button 721 is pressed, the user terminal 30b transmits the customer ID of the target customer and the package ID of the selected package to the application server 10b (S615).

The customer information management unit 14 of the application server 10b stores the package ID in the purchase package of the record corresponding to the customer ID in the customer information storage unit 124 (FIG. 37) (S616). Subsequently, the customer information management unit 14 acquires a license definition whose valid state is “valid” from the license definition storage unit 128 among the license definitions related to the package ID (S617). When a plurality of package IDs are received, a license definition is acquired for each package ID. However, the license definition is not acquired for the package for which license control is invalid.

Subsequently, the customer information management unit 14 generates a license definition selection screen based on the acquired license definition (S618). Subsequently, the customer information management unit 14 returns the license definition selection screen to the user terminal 30b (S619). The user terminal 30b displays the license definition selection screen (S620).

FIG. 41 is a diagram showing a display example of the license definition selection screen. In FIG. 41, the license definition selection screen 790 displays the license definition name and the validity period of each license definition associated with the package for each package selected on the package selection screen 720. Each license definition for one package can be selected by a radio button.

Although FIG. 40 shows an example in which only one package is displayed, FIG. 41 shows an example in which three packages are selected for convenience. Of these, for the third package (“selection package C”), the license definition as a selection candidate is not displayed because the license control is invalid.

When the user selects one of the license definitions for each package, the user terminal 30b sets the customer ID of the target customer, the package ID of each package, and the license definition ID of the license definition selected for each package as an application server. It is transmitted to 10b (S621).

The customer information management unit 14 of the application server 10b stores the customer ID and each package ID in the task information storage unit 126 in association with each other (S622). Subsequently, the customer information management unit 14 executes a license issuance process for each of the packages (S623).

In the license issuance process, first, license data is generated based on the license definition related to the license definition ID received for each package ID. The generated license data is stored in the license storage unit 129.

FIG. 42 is a diagram showing a configuration example of the license storage unit. In FIG. 42, the license storage unit 129 stores the issued license data. Each license data includes a license ID, a license definition ID, a usage start date, a usage end date, a state, and the like. The license ID is identification information for each license. The license definition ID is a license definition ID of the license definition corresponding to the license data. The usage start date is the date when the usage of the license data is started. For example, the date on which step S622 is executed may be set as the usage start date. The usage end date is the date when the usage of the license data ends. The usage end date is determined based on the validity period of the license definition corresponding to the license data, starting from the usage start date. The status is information indicating the validity of the license data. That is, the license data is valid during the period from the start date of use to the end date of use, and is invalid during the other period.

The customer information management unit 14 also adds the license ID of each license data stored in the license storage unit 129 to the issued license ID of the record corresponding to the target customer in the customer information storage unit 124 (FIG. 37). As a result, the license issuance process is completed.

Subsequently, the customer information management unit 14 returns the package addition completion screen to the user terminal 30b (S624). The user terminal 30b displays the package addition completion screen (S625).

FIG. 43 is a diagram showing a display example of the package addition completion screen. In FIG. 43, the package addition completion screen 800 includes a message indicating that the addition of the package (acceptance of the installation instruction to the image forming apparatus 40) is completed.

After that, at an arbitrary timing, the device management unit 15 attaches the image forming device 40b corresponding to the customer ID stored in the task information storage unit 126 to the task information storage unit 126 in association with the customer ID. Each application constituting the package related to the stored package ID is transmitted (S626).

Each image forming device 40b corresponding to the customer ID can be specified by referring to the device information storage unit 125. That is, the device information storage unit 125 stores identification information and the like of each image forming apparatus 40b used by the customer related to the customer ID in association with the customer ID. Further, the arbitrary timing may be, for example, the timing at which a request or inquiry from the corresponding image forming apparatus 40b occurs. Further, each application constituting the package can be specified based on the application ID group stored in the package information storage unit 123 in association with the package ID of the package.

Upon receiving each of the applications, the image forming apparatus 40b that has received the transmission of the application installs the application in the image forming apparatus 40b (S627).

Subsequently, a processing procedure executed when any customer uses the application in the image forming apparatus 40 will be described.

FIG. 44 is a sequence diagram for explaining an example of a processing procedure executed when the application is used. FIG. 44 describes a case where the customer of the base B operates the image forming apparatus 40b.

For example, when the operator inputs the customer ID and password to the image forming apparatus 40b in order to use the application, the image forming apparatus 40b transmits a request for acquiring the initial screen including the customer ID and the password to the application server 10b ( S701).

The component execution unit 16 of the application server 10b authenticates the customer ID and password (S702). Specifically, if the record including the customer ID and password is stored in the customer information storage unit 124, the authentication succeeds, and if not, the authentication fails. If the authentication fails, the component execution unit 16 returns a response indicating the authentication failure. In this case, the image forming apparatus 40b displays the login screen and waits for the input of the customer ID and password. On the other hand, if the authentication is successful, the component execution unit 16 generates an initial screen (S703). On the initial screen, icons of each application included in the purchase package associated with the successfully authenticated customer ID and stored in the customer information storage unit 124 are arranged. Each application included in the purchase package can be specified in the package information storage unit 123 (FIG. 18) based on the application ID group corresponding to the package ID of the purchase package. The icon of each application can be specified by referring to the application information storage unit 121 (FIG. 8).

Subsequently, the component execution unit 16 returns the generated initial screen to the image forming apparatus 40b (S704). The image forming apparatus 40b displays the initial screen on the operation panel (S705).

FIG. 45 is a diagram showing a display example of the initial screen. As shown in FIG. 45, an icon is displayed for each application on the initial screen 810.

When the icon of any of the applications is selected on the initial screen 810, the image forming apparatus 40b transmits the customer ID, the package ID of the package to which the application belongs, and the application ID of the application to the application server 10b (S706). )
The component execution unit 16 of the application server 10b executes a license check for the application (S707). Specifically, the component execution unit 16 acquires a license ID stored in the customer information storage unit 124 (FIG. 37) as an issued license ID associated with the customer ID. The component execution unit 16 confirms the following (1) and (2) for the license ID.
(1) The state in which the license ID is stored in the license storage unit 129 (FIG. 42) is "valid".
(2) Regarding the license definition related to the license definition ID associated with the license ID and stored in the license storage unit 129 (FIG. 42), the package ID stored in the license definition storage unit 128 (FIG. 22) is Must match the received package ID.

If both (1) and (2) are satisfied, the license is determined to be valid. If at least one of (1) and (2) is not satisfied, the license is determined to be invalid.

When the license is invalid, the component execution unit 16 returns a response notifying that the license is invalid to the image forming apparatus 40b (S708). In this case, the image forming apparatus 40b superimposes the license invalid screen on the initial screen 810 and displays it (S709).

FIG. 46 is a diagram showing a display example of the license invalidation screen. As shown in FIG. 46, the license invalidation screen 820 displays a message indicating that the application cannot be used because the license is invalid.

On the other hand, when the license is valid, the component execution unit 16 returns the screen of the application related to the application ID received in step S706 (hereinafter, referred to as “application screen”) to the image forming apparatus 40b (S710). The image forming apparatus 40b displays the application screen on the operation panel (S711).

FIG. 47 is a diagram showing a display example of the application screen. The application screen 830 shown in FIG. 47 is a screen of an application that distributes image data scanned from a document by the image forming apparatus 40b to a predetermined folder. Therefore, the application screen 830 includes a reading setting for scanning, an area for selecting a delivery destination folder, and the like.

By managing the license for each application in this way, it is possible to prevent unlimited use of each application. In addition, since it is easy for each customer to grasp the usage status of the package and the application, for example, the cost recovery status can be easily grasped.

As described above, according to the present embodiment, the application individually developed at each base can be imported into another base. At the other base, a package containing the application can be created. Therefore, it is possible to improve the diversion of programs developed in each region regarding equipment.

In the present embodiment, the case where the image forming apparatus 40 is an example of the device has been described, but the present embodiment may be applied to other devices such as a projector, an electronic blackboard, and a video conferencing system.

In the present embodiment, the application server 10b is an example of the first information processing device. The application server 10a is an example of the second information processing device. The shared server 20 is an example of a third information processing device. The application storage unit 122 is an example of the first storage unit. The base asset management unit 12 is an example of a receiving unit. The package management unit 13 is an example of a generation unit. The asset information storage unit 212 is an example of a second storage unit. The device management unit 15 is an example of a transmission unit. The license definition storage unit 128 is an example of a third storage unit. A customer is an example of a purchaser. The license storage unit 129 is an example of a fourth storage unit. The customer information management unit 14 is an example of a second generation unit.

However, regarding claims 8 to 10, the application server 10a is an example of the first information processing device. The application server 10b is an example of the second information processing device. The shared server 20 is an example of an information processing device. The asset information storage unit 212 is an example of a storage unit. The asset management unit 23 is an example of a receiving unit and a list transmitting unit. The import unit 24 is an example of a program transmission unit. The application ID (asset ID) is an example of program identification information. The base ID is an example of area identification information.

Although the examples of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications are made within the scope of the gist of the present invention described in the claims.・ Can be changed.

1 Information processing system 10 App server 11 App development management department 12 Base asset management department 13 Package management department 14 Customer information management department 15 Equipment management department 16 Component execution department 20 Shared server 21 Authentication department 22 Portal department 23 Asset management department 24 Import department 30 User terminal 40 Image forming device 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 Interface device 121 App information storage unit 122 App storage unit 123 Package information storage unit 124 Customer information storage unit 125 Device information storage unit 126 Task information storage unit 127 Component information storage unit 128 License definition storage unit 129 License storage unit 211 User information storage unit Department 212 Asset Information Storage Department 213 Base Information Storage Department B Bus

Japanese Unexamined Patent Publication No. 2011-100226

Claims (10)

A first information processing apparatus, a second information processing apparatus, the third information which is connected via a plurality of information processing devices and network including a first information processing apparatus and the second information processing apparatus An information processing system that includes a processing device
The first information processing device is
A first storage unit that stores programs developed in the first area,
A receiver that receives a program developed in the second area, which is stored in the second information processing apparatus, via a network.
A generation unit that generates a sales unit of the program, including a program stored in the first storage unit and one or more programs selected by the user from the programs received by the reception unit.
Have a,
The third information processing device is
An authentication unit that authenticates the user based on the login information obtained from the terminal,
An acquisition unit that acquires a program based on an import request acquired from the terminal, and an acquisition unit.
A transmission unit that transmits a program acquired by the acquisition unit to the information processing device corresponding to the base to which the user belongs among the plurality of information processing devices.
The information processing system characterized by have a. The third information processing device is
It has a second storage unit that stores the identification information of the program selected as a disclosure target to other areas from the programs stored in the second information processing device.
The receiver
The second item is included in the identification information of the program stored in the first storage unit and the identification information selected by the user from the list of identification information stored in the second storage unit. When there is identification information stored in the storage unit, the program related to the identification information is received via the network.
The information processing system according to claim 1, wherein the information processing system is characterized by the above. The receiver
A program related to the identification information stored in the second storage unit is received via the network and stored in the first storage unit.
2. The information processing system according to claim 2. In the second storage unit, information associated with the identification information of the program and indicating the area where the publication of the program is permitted is stored.
The receiving unit receives the identification information selected by the user from the list of the identification information of the programs permitted to be disclosed to the first area among the identification information stored in the second storage unit. When there is identification information stored in the second storage unit, the program related to the identification information is received via the network.
The information processing system according to claim 2 or 3, wherein the information processing system is characterized by the above. The first information processing device is
It has a transmitter that transmits the sales unit to a device connected via a network.
The information processing system according to any one of claims 1 to 4, wherein the information processing system is characterized by the above. The generation unit generates license definition information for the sales unit, associates the definition information with the sales unit, and stores the definition information in a third storage unit.
The information processing system according to any one of claims 1 to 5, wherein the information processing system is characterized by the above. License data is generated for the purchaser of the sales unit based on the definition information generated for the sales unit, and the license data is associated with the identification information of the purchaser and stored in the fourth storage unit. Second generator,
6. The information processing system according to claim 6. An information processing device that is connected to multiple information processing devices via a network.
The program identification information, which is the identification information of the program developed in the first area and stored in the first information processing device among the plurality of information processing devices, and the area, which is the identification information of the first area. A receiving unit that receives a request for disclosure of the program from the first information processing device, including identification information, and a receiving unit.
A storage unit that stores the program identification information and the area identification information received by the reception unit in association with each other.
An authentication unit that authenticates the user based on the login information obtained from the terminal,
Response to a request from the terminal, generates a list of program identification information stored in the storage unit, and the list transmitting unit that transmits the list to the terminal,
When the terminal receives the program identification information selected from the list, the first information processing apparatus corresponding to the area identification information stored in the storage unit in association with the program identification information. A program transmission unit that acquires a program related to program identification information and transmits the program to the information processing device corresponding to the base to which the user belongs among the plurality of information processing devices.
An information processing device characterized by having. Information processing devices that are connected to multiple information processing devices via a network
The program identification information, which is the identification information of the program developed in the first area and stored in the first information processing device among the plurality of information processing devices, and the area, which is the identification information of the first area. A receiving procedure for receiving the disclosure request of the program from the first information processing device, including the identification information, and
A storage procedure in which the program identification information and the area identification information received in the reception procedure are associated and stored in the storage unit, and
An authentication procedure that authenticates the user based on the login information obtained from the terminal,
A list transmission procedure for generating a list of program identification information stored in the storage unit and transmitting the list to the terminal in response to a request from the terminal.
When the terminal receives the program identification information selected from the list, the first information processing apparatus corresponding to the area identification information stored in the storage unit in association with the program identification information. A program transmission procedure for acquiring a program related to program identification information and transmitting the program to the information processing device corresponding to the base to which the user belongs among the plurality of information processing devices.
An information processing method characterized by executing. For information processing devices that are connected to multiple information processing devices via a network
The program identification information, which is the identification information of the program developed in the first area and stored in the first information processing device among the plurality of information processing devices, and the area, which is the identification information of the first area. A receiving procedure for receiving the disclosure request of the program from the first information processing device, including the identification information, and
A storage procedure in which the program identification information and the area identification information received in the reception procedure are associated and stored in the storage unit, and
An authentication procedure that authenticates the user based on the login information obtained from the terminal,
Response to a request from the terminal, generates a list of program identification information stored in the storage unit, and a list transmission step of transmitting the list to the terminal,
When the terminal receives the program identification information selected from the list, the first information processing apparatus corresponding to the area identification information stored in the storage unit in association with the program identification information. A program transmission procedure for acquiring a program related to program identification information and transmitting the program to the information processing device corresponding to the base to which the user belongs among the plurality of information processing devices.
An information processing program characterized by executing.

Images