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

Abstract

PROBLEM TO BE SOLVED: To improve versatility of a program developed for each area regarding an apparatus.SOLUTION: An information processing system includes a first information processing device and a second information processing device. The first information processing device includes: a first storage unit for storing programs developed in a first area; a reception unit for receiving programs stored in the second information processing device and developed in a second area via a network; and a generation unit for generating a sales unit of programs including the programs stored in the first storage unit and one or more programs selected by a user among the programs received by the reception unit.SELECTED DRAWING: Figure 3

Description

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

  Among companies that sell devices in a global environment, there are companies that establish bases in each region and develop application programs (hereinafter simply referred to as “apps”) that operate on the equipment for each base. This is because, for example, device users have different preferences among regions such as Europe, North America, and Japan, and it is necessary to develop an application that can provide services according to each region.

  Apps developed at each site are managed by a system installed at each site and sold within the site.

  However, the user's preference is not necessarily completely different between regions, and a similar request may be requested from a customer. In such a case, an application having the same function is developed repeatedly at a plurality of bases, which may cause a reduction in development efficiency from the viewpoint of the entire company.

  This invention is made in view of said point, Comprising: It aims at improving the applicability of the program developed for every area regarding an apparatus.

  In order to solve the above problem, an information processing system including a first information processing apparatus and a second information processing apparatus, wherein the first information processing apparatus is a program developed in a first region. A first storage unit for storing, a reception unit for receiving a program developed in the second region, which is stored in the second information processing apparatus, via a network, and stored in the first storage unit And a generating unit that generates a sales unit of the program including one or more programs selected by the user from among the programs received by the receiving unit.

  It is possible to improve the applicability of programs developed for each region in terms of 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 structural example of the application server in embodiment of this invention. It is a figure which shows the function structural example of the application server and shared server in embodiment of this invention. It is a sequence diagram for demonstrating an example of the process sequence of an application release process. It is a figure which shows the structural example of a user information storage part. It is a figure which shows the example of a display of a portal screen. It is a figure which shows the example of a display of a development top screen. It is a figure which shows the structural example of an application information storage part. It is a figure which shows the example of a display of an application list screen. It is a figure which shows the structural example of an asset information storage part. It is a sequence diagram for demonstrating an example of the process sequence of an application taking-in process. It is a figure which shows the example of a display of an asset list screen. It is a figure which shows the example of a display of an asset detailed screen. It is a figure which shows the example of a display of an acquisition completion screen. It is a sequence diagram for demonstrating an example of the process sequence of a package creation process. It is a sequence diagram for demonstrating an example of the process sequence of a package creation process. It is a figure which shows the example of a display of a customer management menu screen. It is a figure which shows the structural example of a package information storage part. It is a figure which shows the example of a display of a package list screen. It is a figure which shows the example of a display of a package new creation screen. It is a figure which shows the example of a display of an application selection screen. It is a figure which shows the structural example of a license definition memory | storage part. It is a figure which shows the example of a display of a license definition list screen. It is a figure which shows the example of a display of a license definition creation screen. It is a figure which shows the example of a display of a package creation completion screen. It is a figure which shows the example of a display of a license definition edit screen. It is a sequence diagram for demonstrating an example of the process sequence of the production process of application initial data. It is a figure which shows the example of a display of an edit application selection screen. It is a figure which shows the example of a display of an initial data edit screen. FIG. 11 is a sequence diagram for explaining an example of a processing procedure of a package editing process. It is a figure which shows the example of a display of a package basic setting screen. It is a figure which shows the example of a display of a package structure edit screen. It is a figure which shows the example of a display of an application addition screen. It is a figure which shows the example of a display of an initial data selection screen. It is a sequence diagram for demonstrating an example of the process sequence of a package installation process. It is a figure which shows the example of a display of a customer search screen. It is a figure which shows the structural example of a customer information storage part. It is a figure which shows the example of a display of a customer list screen. It is a figure which shows the example of a display of a customer information screen. It is a figure which shows the example of a display of a package selection screen. It is a figure which shows the example of a display of a license definition selection screen. It is a figure which shows the structural example of a license memory | storage part. It is a figure which shows the example of a display of a package addition completion screen. It is a sequence diagram for demonstrating an example of the process sequence performed at the time of utilization of an application. It is a figure which shows the example of a display of an initial screen. It is a figure which shows the example of a display of a license invalid screen. It is a figure which shows the example of a display of an application screen.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating 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 that uses the information processing system 1 (hereinafter referred to as “company R”). Each base is provided for each sales region of products manufactured by the 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, a base may be provided for each region such as North America, Europe, and Japan. Moreover, if it is in Japan, a base may be provided for every more detailed region, such as every region or every prefecture.

  Each base includes an application server 10, one or more user terminals 30, and one or more image forming apparatuses 40. These are connected via a network such as the Internet. In addition, when referring to the application server 10 at the site A, the user terminal 30, and the image forming apparatus 40, “a” is added to the end of these codes. Similarly, when referring to the application server 10 at the site B, the user terminal 30, and the image forming apparatus 40, “b” is added to the end of these codes. When the bases are not distinguished, “a” and “b” are not given to each code.

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

  The application server 10 is one or more computers used for developing and executing an application relating to the image forming apparatus 40, creating and deploying a package, and the like. A package is a set of one or more apps grouped according to a certain classification or standard. In the present embodiment, sales of applications are performed on a package basis. Therefore, a package is a sales unit of an application.

  In the present embodiment, an application is configured by connecting programs called components. Therefore, the entity of the application is information in which component connection relationships (hereinafter referred to as “flows”) and 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 performs OCR (Optical Character Recognition) on image data (hereinafter referred to as “OCR component”), a component that performs user authentication, and a component that distributes data to cloud storage (hereinafter referred to as “distribution”) Component ")). For example, when an application including an OCR component and a distribution component is installed in the image forming apparatus 40 and execution of the application is instructed in the image forming apparatus 40, the image forming apparatus 40 scans image data scanned from a document. Is transmitted to the application server 10 at the site to which the image forming apparatus 40 belongs. The application server 10 executes components that constitute the application. That is, the application server 10 performs OCR on the image data, and distributes text data generated by the OCR to the cloud storage.

  The user terminal 30 is a terminal used by a 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, or sells an 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 at 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 making it possible to share an application or a package developed or created individually at each site across the sites. Hereinafter, when an application and a package are not distinguished, they are referred to as “assets”.

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

  A program for realizing processing in 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 from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. However, the program need not be installed from the recording medium 101 and may be downloaded from another computer via a network. The auxiliary storage device 102 stores the installed program and also stores necessary files and data.

  The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The CPU 104 executes functions related to the application server 10 in accordance with a 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 that shown in FIG.

  FIG. 3 is a diagram illustrating a functional configuration example of the application server and the shared server in the embodiment of the present invention.

  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 units is realized by processing that one or more programs installed in the application server 10 cause the CPU 104 to execute. The application server 10 also includes 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 using, for example, the auxiliary storage device 102 or a storage device that can be connected to the application server 10 via a network.

  The application development management unit 11 supports application development at the base. Application information that is bibliographic information of the developed application is stored in the application information storage unit 121. The application entity is stored in the application storage unit 122.

  The base asset management unit 12 loads an application developed at another base, releases (publishes) an application developed at the base, and the like. Incorporation of an application means receiving an application entity at another site and storing it in the application storage unit 122.

  The package management unit 13 supports creation and editing of packages. Package information that 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 site 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 on each image forming apparatus 40. Information regarding 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 on device management tasks such as which package should be installed in 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 performs execution control of components that constitute an application selected as an execution target in the image forming apparatus 40. The component information storage unit 127 stores information regarding each component.

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

  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 regarding 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 assets that are permitted to be disclosed to other bases among the assets developed for each base. The asset information storage unit 212 stores information related to such assets.

  The capturing unit 24 executes processing for making it possible to use the application registered in the asset information storage unit 212 at a base other than the registration base.

  The base information storage unit 213 stores information regarding each base. For example, the base information storage unit 213 stores the IP address of the application server 10 at each base.

  The license definition storage unit 128 stores license definition information about the package (hereinafter referred to as “license definition”). A plurality of 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, a processing procedure executed in the information processing system 1 will be described. FIG. 4 is a sequence diagram for explaining an example of a processing procedure of an application release process. In FIG. 4, the case where the processing procedure is executed with respect to the base A will be described, but the processing procedure can be executed similarly at other bases.

  In the initial state of FIG. 4, a login screen to the shared server 20 is displayed on the user terminal 30a. 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).

  Upon receiving the login request, the authentication unit 21 of the shared server 20 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 illustrating a configuration example of the user information storage unit. In FIG. 5, the user information storage unit 211 stores a user name, a password, a name, a 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 user name. The name is the name of the user. The affiliation base is identification information (hereinafter referred to as “base ID”) of the base to which the user associated with the user name belongs.

  If 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 illustrating 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 corresponding to the user's work purpose. When releasing an application managed in 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 generates a portal screen 510 by setting a link to the application server 10 corresponding to the affiliation ID of the logged-in user in “application development” of the menu 511.

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

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

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

  FIG. 8 is a diagram illustrating a configuration example of the application information storage unit. As shown in FIG. 8, the application information storage unit 121 stores, for each application, an application ID, name, icon, function category, developer, supported language, overview, registration date / time, paid / free, charge, and disclosure range. Application information including such as 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 sites. Such identification information can be easily generated at each site, for example, by including the site ID as 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 an application. The function category is a category to which an application function belongs, and is used, for example, for searching for an application. Functional categories include scan, print, conversion, storage, email, document analysis, construction, manufacturing, medical, and others. Two or more function categories may be set for one application. The developer is an identification name of the developer of the application. The supported language is a language (English, Japanese, etc.) supported by the application, and a plurality of designations are possible. The outline is an outline of the application described in a free format. The registration date / time is the date / time when the application was 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 a fee for the app that is charged. The disclosure range is a range in which the application is permitted to be disclosed. The range is specified by a base or a customer. In other words, the disclosure range is a set of a base ID of a base where application publication is permitted, or a customer ID which is identification information of a customer permitted to publish an application. Since the disclosure range can be set for each application, it is possible to prevent the application from leaking to an area not intended by the user. A state where there is no value in the disclosure range indicates that there is no restriction on the disclosure range.

  In step S110, all 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 an application list screen to the user terminal 30a (S112). The user terminal 30a displays an application list screen (S113).

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

  When the user selects an application that is permitted to be released to another site 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). . A plurality of applications may be selected as release targets.

  When receiving the release request, the application development management unit 11 of the application server 10a acquires 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).

  When 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 illustrating 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, a fee / charge for each released (published) asset. Asset information including free of charge, fee, release source, release range, etc. is stored.

  The asset ID is identification information for each asset. If the asset is an app, the app ID of the app 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, overview, registration date / time, paid / free, and fee are as described in FIG. However, the registration date / time is the date / time stored in the asset information storage unit 212. The release source is a base ID of a base from which the asset is released. That is, the base ID received in step S117 is stored as the release source. The release range is a range in which the release of the asset is permitted, and its meaning is the same as the release range of the application.

  By executing the processing procedure shown in FIG. 4, the application at each site can be referred to from other sites. However, the substance of the released application is not managed by the shared server 20. Therefore, the site B can know the existence of the application released by the site A, but cannot use the app at the site B. In order to make the application available at the site B, a copy (copy) of the application needs to be taken into the site B.

  FIG. 11 is a sequence diagram for explaining an example of the processing procedure of the application loading process. In FIG. 11, a process of taking an application released from the site A by the processing procedure of FIG. Therefore, the processing procedure of FIG. 11 is executed in response to an instruction from the user at the site B. 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 in FIG. 4 have been executed for the user terminal 30b.

  When the user at the site B selects “asset list” in the menu 511 on the portal screen 510 (FIG. 6), the user terminal 30b transmits an asset list acquisition request 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 asset to be acquired is 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 illustrating 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 where a list of asset information is displayed. The filter area 542 is an area for receiving a filter (squeezing condition) setting for asset information to be displayed in the list area 541. In FIG. 12, display objects can be narrowed down by function category, developer, and paid / free.

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

  FIG. 13 is a diagram illustrating a display example of the asset detail screen. In FIG. 13, the asset detail screen 550 includes a detail area 551, a capture button 552, and the like. The detailed area 551 is an area in which configuration information of asset information that is not displayed in the list area 541 of the asset list screen 540 is displayed for the target asset. The capture button 552 is a button for accepting a capture instruction for the target asset.

  When the capture button 552 is pressed on the asset details screen 550, the user terminal 30b transmits a capture request including the asset ID of the target asset to the shared server 20 (S207). When receiving the import request, the asset management unit 23 of the shared server 20 acquires a 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 an asset acquisition request including the asset ID (here, the application ID is assumed) to the application server 10a corresponding to the base ID (S209). Note that the IP address of the application server 10 corresponding to each site ID is stored in the site information storage unit 213.

  Upon receiving the acquisition request, the base asset management unit 12 of the application server 10a acquires the application entity corresponding to the application ID included in the acquisition request from the application storage unit 122 and supports the application ID. The application information to be acquired is acquired from the application information storage unit 121 (S210). Subsequently, the base asset management unit 12 returns the application and application information to the asset management unit 23 of the shared 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 site to which the logged-in user of the user terminal 30b that is the transmission source of the capture request belongs ( S212). The base to which the login user belongs can be specified based on the base ID stored in the user information storage unit 211 for the login user. Further, the IP address of the application server 10b corresponding to the base ID can be acquired from the base information storage unit 213.

  Upon receiving the application and application information, the base asset management unit 12 of the application server 10b 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 site A is taken into the site B. Subsequently, the base asset management unit 12 of the application server 10b returns a response indicating completion of capture to the shared server 20 (S214).

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

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

  Subsequently, creation of a 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 illustrates an example in which a package is created at the site B. Therefore, the processing procedure of FIG. 15 is executed in response to an instruction from the user at the site B. 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 in FIG. 4 have been executed for the user terminal 30b.

  When “customer information” in the menu 511 is selected by the user at the site B, the user terminal 30b displays the customer management menu screen on the application server 10b set as the link destination for “customer information”. An acquisition request is transmitted (S301). That is, the portal unit 22 generates a portal screen 510 by setting a link to the application server 10 corresponding to the affiliation ID of the logged-in user in “Customer information” of the menu 511.

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

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

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

  FIG. 18 is a diagram illustrating 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, license control, and the like for each package. The name is the name of the package. The description is a description about the package. The application ID group is a set of application IDs of the applications that make up 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 a package is a target for license control. The 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 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 illustrating a display example of a package list screen. In FIG. 19, a package list screen 580 includes a package list area 581 and a create button 582. In the package list area, the package name and description are displayed for each package. The creation button 582 is a button for accepting a new package creation instruction.

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

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

  When 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 receiving the package information, the package management unit 13 of the application server 10b 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 an asset information list acquisition request 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, from the asset information storage unit 212, a list of asset information that includes the base ID of the base B in the disclosure range (that is, permitted to be disclosed to the base B). Obtain (S315), and return the list to the application server 10b (S316).

  When 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 is generated that includes, as options, each application managed in the application server 10b and each application published to each base in the shared server 20. 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 illustrating a display example of the application selection screen. In FIG. 21, an application selection screen 610 includes application information of each application as options. Here, the options include application information managed at the site B and application information published on the shared server 20. Further, the application information managed at the site B includes application information taken from the site A by executing the processing procedure of FIG. Therefore, in the present embodiment, it is possible to create a package including not only an application developed at the base B but also an 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. Note that a package related to package information newly stored in the package information storage unit 123 is hereinafter referred to as a “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 application entity constituting the package is automatically taken into the application server 10b.

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

  Subsequently, the asset management unit 23 transmits the application and application information to the application server 10b (S333). Upon receiving the application and application information, the base asset management unit 12 of the application server 10b 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). Steps S333 and S334 are the same processing as steps S212 and S213 in FIG.

  Subsequently, when the license control of the target package is valid, the processing procedure of FIG. 16 is executed. In step S341 in 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 illustrating 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 valid period is a valid period of a license issued based on the license definition. In the present embodiment, any one of monthly units (1 to 60 months), daily units (1 to 30 days), or unlimited can be set as the effective period. However, the valid period may be set based on a year unit or another unit period. The package ID is a package ID of a 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 indicates 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 illustrating a display example of the license definition list screen. 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, a license definition ID, a valid period, a valid state, and the like are displayed for each existing license definition. The creation button 752 is a button for accepting an instruction for creating a new license definition.

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

  FIG. 24 is a diagram illustrating a display example of a license definition creation screen. 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 accepting input of the value 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).

  When 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). Note that the package ID of the target package is set in the package ID of the license definition.

  Subsequently, the package management unit 13 returns a 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 illustrating a display example of a package creation completion screen. As shown in FIG. 25, the package creation completion screen 770 displays a message indicating that the package creation has been completed. If the license control of the target package is “invalid”, steps S350 and S351 are executed following step S334 in FIG.

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

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

  For example, when “delete” is selected, the user terminal 30b transmits a delete 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 valid state change 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 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 a license definition edit screen.

  FIG. 26 is a diagram illustrating a display example of the license definition editing screen. In FIG. 26, the license definition editing screen 780 includes a license definition editing area 781 and a button 782. 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 in 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 that after step S349 is executed, and the change of the selected license definition is reflected in the license definition storage unit 128.

  In this way, in this embodiment, since the license definition can be defined for each package, the definition of the license according to the form of the customer's business can be generated. Further, since the license definition can be created in the navigation style during the package creation process, the license definition can be generated when the product designer designs the package (product). In addition, since a plurality of license definitions can be generated for one package, various business models can be handled.

  Next, a 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 a processing procedure of application initial data creation processing.

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

  A package is created by clarifying a target customer to some extent, such as for an industry. In this case, it is possible to create products that are more attractive to customers by using terms that match the customer's business that the package targets, rather than simply indicating the function of the app. it can. Therefore, in the present embodiment, the initial data of each application can be edited.

  In response to the editing request, the application development management unit 11 of the application server 10b acquires a list of application information from the application information storage unit 121 (S402). Subsequently, the application development management unit 11 generates an editing application selection screen for selecting an application to be edited for initial data 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 illustrating a display example of the editing application selection screen. As shown in FIG. 28, on the editing application selection screen 620, the icons of the applications managed at the site B are arranged in a selectable state.

  When one of the apps is selected by the user, the user terminal 30b transmits an initial data acquisition request including the app ID of the selected app to the app server 10b (S406). When receiving the acquisition request, the application development management unit 11 of the application server 10b acquires 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 illustrating a display example of the initial data editing screen. As shown in FIG. 29, the initial data editing screen 630 shows the contents of the current initial data. When the button 631 is pressed by the user, a screen for accepting a setting change of each item (icon, name, setting information, etc.) of the initial data is displayed. The user edits the initial data via the screen.

  When an instruction to complete editing of the initial data is input by the user, the user terminal 30b transmits the edited initial data and the application ID of the application that is the editing target of the initial data 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 plurality of initial data is valid can be selected for each package.

  By the way, even if a package is created once, if the package configuration does not meet market demands, it is expected that the product power of the package will be improved by changing the applications that make up the package and the initial data of each application. There are cases where you can. In consideration of such a case, in the present embodiment, the package configuration can be edited.

  FIG. 30 is a sequence diagram for explaining an example of a processing procedure of package editing processing. 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 sends 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 transmits to the server 10b (S501). When receiving the edit request, the package management unit 13 of the application server 10b acquires 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 a package basic setting screen to the user terminal 30b. The user terminal 30b displays 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 a description input area 642. In each of these areas, a package name or description already 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 when the editing is not performed, when the button 643 is pressed, the package name and description displayed in the package name input area 641 and the description 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 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 editing screen based on the application information (S508). Subsequently, the package management unit 13 returns a package configuration edit screen to the user terminal 30b (S509). The user terminal 30b displays the package configuration editing screen (S510).

  FIG. 32 is a diagram illustrating a display example of the package configuration editing screen. In FIG. 32, the package configuration editing screen 650 displays a list of application information of each application included in the target package. On the package configuration editing screen 650, it is possible to delete or change 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). When receiving the addition 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 set as a candidate for addition to the package (S513). Note that the application information of the application already included in the target package may be excluded from the addition candidates. Further, processing similar to steps S314 to S316 in FIG. 15 may be executed, and the application information published in 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 illustrating 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 one or more pieces of application information are selected on the application addition screen 660 and the button 661 is pressed, the user terminal 30b transmits an application ID corresponding to the selected application information to the application server 10b (S516). . When receiving the application ID, the package management unit 13 of the application server 10b stores the application ID.

  Subsequently, the package management unit 13 acquires initial data of an application related to the application ID (hereinafter referred to as “additional application”) from the application storage unit 122 (S517). A plurality of initial data is acquired for an application associated with a plurality of initial data. Subsequently, the package management unit 13 generates an initial data selection screen for selecting initial data to be valid 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. Note that initial data may be created for each language, for example, for English or Japanese.

  When any 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). When 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 deletion of any application is instructed on the package configuration editing screen 650, the application ID of the application is deleted from the application ID of the package information of the target package.

  Next, a 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 a processing procedure of package installation processing. 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 request for editing customer information to the application server 10b (S601). In response to the editing request, the customer information management unit 14 of the application server 10b returns a customer search screen to the user terminal 30b (S602). The user terminal 30b displays the customer search screen (S603).

  FIG. 36 is a diagram illustrating a display example of a customer search screen. 36, the customer search screen 680 has a search condition input area for searching for 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 illustrating a configuration example of a customer information storage unit. In FIG. 37, a customer information storage unit 124 stores a customer ID, password, customer name, usage status, registration category, registrant, country, purchase package, issued license ID, and the like for each customer at the site.

  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 apparatus 40 by the customer. The registration category is a category related to customer information registration. The registrant is a registrant of customer information. Country is the name of the country where the customer is located. The purchase package is a list of package IDs of packages that have been purchased by the customer. The issued license ID is identification information of license data issued for the purchased package.

  Subsequently, the customer information management unit 14 generates a customer list screen including a list of 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 illustrating a display example of a customer list screen. In FIG. 38, a customer list screen 690 displays a list of customer information that matches the search conditions.

  When the user selects any one piece of customer information, the user terminal 30b displays a 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 “target customer”.

  FIG. 39 is a diagram showing a display example of a customer information screen. In FIG. 39, a 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 excluding the purchase package is displayed for the target customer. 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, since the target customer has no purchase record of the package, no package information is displayed.

  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). In response to the request, the customer information management unit 14 of the application server 10 acquires a list of package information from the package information storage unit 123 (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 illustrating a display example of a package selection screen. In FIG. 40, a package selection screen 720 displays a list of packages. Note that FIG. 40 shows an example in which one package is sold at the site B.

  When the user selects a package purchased by the customer and presses the button 721, 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, from the license definition storage unit 128, a license definition whose valid state is “valid” among the license definitions associated with the package ID (S617). When a plurality of package IDs are received, a license definition is acquired for each package ID. However, no license definition is acquired for a 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. 41, for each package selected on the package selection screen 720, the license definition selection screen 790 displays the license definition name and validity period of each license definition associated with the package. Each license definition for one package can be selected by a radio button.

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

  When the user selects one of the license definitions for each package, the user terminal 30b displays 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 on the application server. 10b (S621).

  The customer information management unit 14 of the application server 10b stores the customer ID and each package ID in association with each other in the task information storage unit 126 (S622). Subsequently, the customer information management unit 14 executes a license issuance process for each package (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 illustrating a configuration example of the license storage unit. In FIG. 42, the license storage unit 129 stores issued license data. Each license data includes a license ID, a license definition ID, a use start date, a use end date, a status, 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 use start date is the date when the use of the license data is started. For example, the date on which step S622 is executed may be the use start date. The use end date is the date when the use of the license data ends. The use end date is determined based on the validity period of the license definition corresponding to the license data, starting from the use 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 use start date to the use end date, and invalid during other periods.

  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 ends.

  Subsequently, the customer information management unit 14 returns a 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 illustrating a display example of a package addition completion screen. In FIG. 43, a package addition completion screen 800 includes a message indicating that the addition of a package (accepting an installation instruction to the image forming apparatus 40) has been completed.

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

  Each image forming apparatus 40b corresponding to the customer ID can be specified with reference to the device information storage unit 125. That is, the device information storage unit 125 stores identification information of each image forming apparatus 40b used by the customer related to the customer ID in association with the customer ID. The arbitrary timing may be, for example, a timing when a request or inquiry from the corresponding image forming apparatus 40b is generated. Moreover, each application which comprises a package can be specified based on the application ID group currently matched with package ID of the said package and memorize | stored in the package information storage part 123. FIG.

  Upon receiving the application, the image forming apparatus 40b receives the application and installs the application in the image forming apparatus 40b (S627).

  Next, a processing procedure executed when any customer uses an 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 an application is used. FIG. 44 illustrates a case where the customer at the site B operates the image forming apparatus 40b.

  For example, when the operator inputs a customer ID and password to use the application to the image forming apparatus 40b, the image forming apparatus 40b transmits an initial screen acquisition request including the customer ID and 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 a record including the customer ID and password is stored in the customer information storage unit 124, the authentication is successful, and if not, the authentication fails. When the authentication fails, the component execution unit 16 returns a response indicating the authentication failure. In this case, the image forming apparatus 40b displays a login screen and waits for input of a customer ID and a password. On the other hand, when the authentication is successful, the component execution unit 16 generates an initial screen (S703). On the initial screen, an icon of each application included in the purchase package stored in the customer information storage unit 124 in association with the customer ID that has been successfully authenticated is 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 with reference 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 any app icon 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 app belongs, and the app ID of the app to the app server 10b (S706). )
The component execution unit 16 of the application server 10b performs a license check for the application (S707). Specifically, the component execution unit 16 acquires a license ID associated with the customer ID and stored in the customer information storage unit 124 (FIG. 37) as an issued license ID. The component execution unit 16 confirms the following (1) and (2) for the license ID.
(1) The state of the license ID stored in the license storage unit 129 (FIG. 42) is “valid”.
(2) For the license definition related to the license definition ID stored in the license storage unit 129 (FIG. 42) in association with the license ID, 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.

  If 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 displays the license invalidation screen superimposed on the initial screen 810 (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 an application screen (hereinafter referred to as “application screen”) related to the application ID received in step S706 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 illustrating a display example of the application screen. An application screen 830 shown in FIG. 47 is an application screen 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 distribution destination folder, and the like.

  In this way, license management is performed for each application, thereby preventing each application from being used indefinitely. In addition, since the usage status of packages and applications by each customer can be easily understood, for example, the cost recovery status can be easily understood.

  As described above, according to the present embodiment, an application developed individually at each site can be taken into another site. At the other base, a package including the application can be created. Therefore, the applicability of the program developed for each region regarding the device can be improved.

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

  In the present embodiment, the application server 10b is an example of a first information processing apparatus. The application server 10a is an example of a second information processing apparatus. The shared server 20 is an example of a third information processing apparatus. The application storage unit 122 is an example of a first storage unit. The base asset management unit 12 is an example of a reception 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, with regard to claims 8 to 10, the application server 10a is an example of a first information processing apparatus. The application server 10b is an example of a second information processing apparatus. 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 reception unit and a list transmission unit. The capturing 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.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

DESCRIPTION OF SYMBOLS 1 Information processing system 10 Application server 11 Application development management part 12 Base asset management part 13 Package management part 14 Customer information management part 15 Equipment management part 16 Component execution part 20 Shared server 21 Authentication part 22 Portal part 23 Asset management part 24 Capture part 30 User terminal 40 Image forming apparatus 100 Drive apparatus 101 Recording medium 102 Auxiliary storage apparatus 103 Memory apparatus 104 CPU
105 interface device 121 application information storage unit 122 application 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 212 Asset information storage unit 213 Base information storage unit B bus

JP 2011-1000022 A

Claims (13)

An information processing system including a first information processing device and a second information processing device,
The first information processing apparatus includes:
A first storage unit for storing a program developed in the first region;
A receiving unit for receiving a program developed in the second region 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 a user from among the programs received by the reception unit;
An information processing system comprising: A third information processing device connected to the first information processing device and the second information processing device via a network;
The third information processing apparatus
A second storage unit that stores identification information of a program selected as a publication target for another region from among the programs stored in the second information processing apparatus;
The receiver is
Among 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, the second information When there is identification information stored in the storage unit, a program related to the identification information is received via a network.
The information processing system according to claim 1. The receiver is
Receiving a program related to the identification information stored in the second storage unit via a network, and storing the program in the first storage unit;
The information processing system according to claim 2. The second storage unit stores information indicating an area where the program is permitted to be associated with the identification information of the program,
The receiving unit includes, among the identification information stored in the second storage unit, identification information selected by a user from a list of identification information of programs permitted to be released to the first region. When there is identification information stored in the second storage unit, a program related to the identification information is received via a network.
The information processing system according to claim 2 or 3, The first information processing apparatus includes:
A transmission unit for transmitting the sales unit to a device connected via a network;
The information processing system according to claim 1, wherein the information processing system is an information processing system. The generation unit generates license definition information for the sales unit, and stores the definition information in association with the sales unit in a third storage unit.
The information processing system according to claim 1, wherein the information processing system is an information processing system. License data is generated for a purchaser of the sales unit based on the definition information generated for the sales unit, and the license data is stored in a fourth storage unit in association with the purchaser's identification information. A second generator to
The information processing system according to claim 6, further comprising: A first storage unit for storing a program developed in the first region;
A receiving unit for receiving a program developed in the second region stored in another 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 a user from among the programs received by the reception unit;
An information processing apparatus comprising: An information processing apparatus having a first storage unit that stores a program developed in the first region,
A reception procedure for receiving a program developed in the second region stored in another information processing apparatus via a network;
A generation procedure for generating a sales unit of the program, including a program stored in the first storage unit, and one or more programs selected by a user from among the programs received in the reception procedure;
The information processing method characterized by performing. In an information processing apparatus having a first storage unit for storing a program developed in the first region,
A reception procedure for receiving a program developed in the second region stored in another information processing apparatus via a network;
A generation procedure for generating a sales unit of the program, including a program stored in the first storage unit, and one or more programs selected by a user from among the programs received in the reception procedure;
An information processing program for executing Program identification information, which is program identification information developed in the first region and stored in the first information processing apparatus, and region identification information, which is identification information of the first region, A receiving unit that receives a public request from the first information processing apparatus;
A storage unit for storing the program identification information and the region identification information received by the reception unit in association with each other;
In response to a request from a terminal belonging to the second region, a list of program identification information stored in the storage unit is generated, and a list transmission unit that transmits the list to the terminal;
When receiving the program identification information selected from the list in the terminal, 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 for acquiring a program related to the program identification information and transmitting the program to the second information processing apparatus corresponding to the second region;
An information processing apparatus comprising: Program identification information, which is program identification information developed in the first region and stored in the first information processing apparatus, and region identification information, which is identification information of the first region, A receiving procedure for receiving a public request from the first information processing apparatus;
A storage procedure for storing the program identification information and the region identification information received in the reception procedure in association with each other in a storage unit;
In response to a request from a terminal belonging to the second area, a list transmission procedure for generating a list of program identification information stored in the storage unit and transmitting the list to the terminal;
When receiving the program identification information selected from the list in the terminal, 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 the program identification information and transmitting the program to the second information processing apparatus corresponding to the second region;
An information processing method characterized in that the information processing apparatus executes. Program identification information, which is program identification information developed in the first region and stored in the first information processing apparatus, and region identification information, which is identification information of the first region, A receiving procedure for receiving a public request from the first information processing apparatus;
A storage procedure for storing the program identification information and the region identification information received in the reception procedure in association with each other in a storage unit;
In response to a request from a terminal belonging to the second area, a list transmission procedure for generating a list of program identification information stored in the storage unit and transmitting the list to the terminal;
When receiving the program identification information selected from the list in the terminal, 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 the program identification information and transmitting the program to the second information processing apparatus corresponding to the second region;
An information processing program for causing an information processing apparatus to execute.

Images