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

Description

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

In recent years, there have been services that provide a combination of multiple functions (scanning, printing, mail delivery, etc.). For example, there are services that perform predetermined processing on electronic files (image files) generated by scanning and then deliver the files via email. Furthermore, there is already a technology (hereinafter referred to as an application creation tool) that allows the creation of an application that executes such a series of processes without specialized knowledge such as programming.

However, with conventional application creation tools, it may be difficult to maintain parameter settings when the application is changed.

For example, in a case where a user has already used a created application and a change is made to the application, a conventional application creation tool resets the user's setting values for the application to default values. In such cases, conventional app creation tools require the user to set the settings again or use a dedicated tool to restore the settings in order to return the user's settings to the state before changes were made to the application. It was necessary to create a program and distribute it to users.

An information processing system, an information processing device, an information processing method, and a program according to the present invention aim to solve the above-mentioned problems. That is, the information processing system, information processing device, information processing method, and program according to the present invention solve the above-mentioned problem by maintaining parameter settings even when an application is changed.

In order to solve the above-mentioned problems and achieve the objects, the present invention provides an information processing system including a device and a server, in which when an application is changed, the server changes the parameters of the application before the change and changes. a correspondence receiving unit that accepts the specification of a subsequent parameter correspondence, and a setting value for each user of the first parameter before the change of the application, according to the correspondence received by the correspondence receiving unit; A setting unit is provided that sets a setting value of a second parameter that is a parameter after the application has been changed and is associated with the first parameter.

According to the present invention, even if an application is changed, parameter settings can be maintained.

FIG. 1 is a diagram illustrating an example of a configuration of an information processing system according to the first embodiment. FIG. 2 is a diagram showing an example of the hardware configuration of the server and PC of the first embodiment. FIG. 3 is a diagram showing an example of the hardware configuration of the MFP according to the first embodiment. FIG. 4 is a diagram illustrating an example of the functional configuration of the server according to the first embodiment. FIG. 5 is a diagram showing a sequence for changing parameter settings in the first embodiment. FIG. 6 is a diagram showing an example of parameter setting values before change. FIG. 7 is a diagram illustrating an example of a parameter mapping creation screen. FIG. 8 is a diagram illustrating an example of changed parameter settings. FIG. 9 is a diagram illustrating an example of parameters for which the user has determined that there is no need to maintain the set values. FIG. 10 is a diagram showing a sequence for changing parameter settings according to the second embodiment. FIG. 11 is a diagram showing an example of a parameter mapping creation screen. FIG. 12 is a diagram illustrating an example of a UI for associating parameters. FIG. 13 is a diagram illustrating an example of a UI for associating parameters. FIG. 14 is a diagram illustrating an example of a UI for associating parameters. FIG. 15 is a diagram illustrating an example of a UI for associating parameters. FIG. 16 is a diagram illustrating an example of a UI for associating parameters. FIG. 17 is a diagram illustrating an example of a UI for associating parameters. FIG. 18 is a diagram showing an example of a screen for integrating applications. FIG. 19 is a diagram showing a sequence for integrating applications according to the fourth embodiment. FIG. 20 is a diagram showing a sequence of using applications after integration according to the fourth embodiment. FIG. 21 is a diagram illustrating an example of association of setting values. FIG. 22 is a diagram showing an example of parameter setting values before and after integration. FIG. 23 is a diagram illustrating an example of parameters before and after integration in which setting values are not maintained in the information processing system of the fourth embodiment. FIG. 24 is a diagram showing an example of a screen for dividing an application. FIG. 25 is a diagram showing a sequence for dividing an application according to the fifth embodiment. FIG. 26 is a diagram showing a sequence of using divided applications in the information processing system of the fifth embodiment. FIG. 27 is a diagram illustrating an example of association of setting values in the information processing system of the fifth embodiment. FIG. 28 is a diagram illustrating an example of parameters before and after division in which the set values are not maintained in the information processing system according to the fifth embodiment. FIG. 29 is a diagram illustrating an example of a screen for changing applications in a many-to-many manner in the information processing system of the fifth embodiment. FIG. 30 is a functional block diagram of the information processing system according to the embodiment.

Embodiments of an information processing system, an information processing apparatus, an information processing method, and a program will be described in detail below with reference to the accompanying drawings.

(First embodiment)
Fig. 1 is a diagram showing an example of the configuration of an information processing system according to a first embodiment. As shown in Fig. 1, the information processing system 1 includes a server 10 and devices 20 connected to the server 10 via a communication network. The devices 20 include a multifunction peripheral (MFP) 20a and a PC 20b. In the following description, the MFP 20a and the PC 20b may be referred to as the devices 20 without distinction.

FIG. 2 is a diagram showing an example of the hardware configuration of the server and PC of the first embodiment. Here, the hardware configuration of the server 10 will be explained. The PC 20b may have the same hardware configuration as the server 10. As shown in FIG. 2, the server 10 can be a computer. As shown in FIG. 2, the server 10 includes a CPU 1001, a ROM 1002, a RAM 1003, an HD 1004, an HDD (Hard Disk Drive) controller 1005, a display 1006, and an external device connection interface (Interface) 1008. The server 10 also includes a network interface 1009, a data bus 1010, a keyboard 1011, a pointing device 1012, a DVD-RW (Digital Versatile Disk Rewritable) drive 1014, and a media interface 1016.

Among these, the CPU 1001 controls the operation of the server 10 as a whole. The ROM 1002 stores programs used to drive the CPU 1001, such as IPL. The RAM 1003 is used as a work area for the CPU 1001. The HD 1004 stores various data such as programs. The HDD controller 1005 controls reading or writing of various data to the HD 1004 under the control of the CPU 1001. The display 1006 displays various information such as a cursor, menu, window, characters, or images. The external device connection interface 1008 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory or a printer. A network interface 1009 is an interface for data communication using a communication network. The data bus 1010 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 1001 shown in FIG. 2.

Further, the keyboard 1011 is a type of input means that includes a plurality of keys for inputting characters, numerical values, various instructions, and the like. The pointing device 1012 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. A DVD-RW drive 1014 controls reading and writing of various data to a DVD-RW 1013, which is an example of a removable recording medium. Note that it is not limited to DVD-RW, but may be DVD-R or the like. A media interface 1016 controls reading or writing (storage) of data to a recording medium 1015 such as a flash memory.

FIG. 3 is a diagram showing an example of the hardware configuration of the MFP according to the first embodiment. As shown in FIG. 3, the MFP 20a includes a controller, a short-range communication circuit 2020, an engine control section 2030, an operation panel 2040, and a network interface 2050.

Among these, the controller includes a CPU 2001, a system memory (MEM-P) 2002, a north bridge (NB) 2003, and a south bridge (SB) 2004, which are the main parts of the computer. Further, the controller includes an ASIC (Application Specific Integrated Circuit) 2006, a local memory (MEM-C) 2007 which is a storage unit, an HDD controller 2008, and an HD 2009 which is a storage unit. The controller has a configuration in which the NB 2003 and the ASIC 2006 are connected through an AGP (Accelerated Graphics Port) bus 2021.

Among these, the CPU 2001 is a control unit that performs overall control of the MFP 20a. NB2003 is a bridge for connecting CPU2001, MEM-P2002, SB2004, and AGP bus 2021. The NB 2003 includes a memory controller, a PCI (Peripheral Component Interconnect) master, and an AGP target that control reading and writing from and to the MEM-P 2002.

The MEM-P 2002 consists of a ROM 2002a, which is a memory for storing programs and data that realizes each function of the controller, and a RAM 2002b, which is used to expand the programs and data, and is used as a drawing memory when printing the memory. Note that the program stored in the RAM 2002b may be provided as an installable or executable file recorded on a computer-readable recording medium such as a CD-ROM, CD-R, or DVD.

SB2004 is a bridge for connecting PCI devices and peripheral devices to NB2003. The ASIC 2006 is an IC (Integrated Circuit) for image processing that includes hardware elements for image processing. The ASIC 2006 has the role of a bridge that connects the AGP bus 2021, PCI bus 2022, HDD 2008, and MEM-C 2007, respectively. This ASIC 2006 includes a PCI target, an AGP master, an arbiter (ARB) that forms the core of the ASIC 2006, and a memory controller that controls the MEM-C 2007. In addition, the ASIC 2006 is a PCI unit that transfers data via a PCI bus 2022 between a plurality of DMACs (Direct Memory Access Controllers) that rotate image data using hardware logic, etc., a scanner unit 2031, and a printer unit 2032. Equipped with Note that the ASIC 2006 may be connected to a USB (Universal Serial Bus) interface or an IEEE1394 (Institute of Electrical and Electronics Engineers 1394) interface.

MEM-C2007 is a local memory used as a copy image buffer and code buffer. The HD 2009 is a storage for storing image data, font data used during printing, and forms. The HD 2009 controls data reading or writing to the HD 2009 under the control of the CPU 2001. The AGP bus 2021 is a bus interface for a graphics accelerator card that speeds up graphics processing. The AGP bus 2021 allows high-throughput direct access to the MEM-P 2002 to speed up graphics accelerator cards.

Further, the short-range communication circuit 2020 includes a short-range communication circuit 2020a. The short-range communication circuit 2020 is a communication circuit such as NFC or Bluetooth (registered trademark).

Further, the engine control section 2030 includes a scanner section 2031 and a printer section 2032. The operation panel 2040 also includes a panel display section 2040a such as a touch panel that displays current setting values, a selection screen, etc., and accepts input from the operator, as well as setting values for conditions related to image formation such as density setting conditions. An operation panel 2040b is provided, which includes a numeric keypad for accepting instructions, a start key for accepting copy start instructions, and the like. The controller controls the entire MFP 20a, for example, controls drawing, communication, input from the operation panel 2040, and the like. The scanner section 2031 or the printer section 2032 includes image processing sections such as error diffusion and gamma conversion.

Note that the MFP 20a can sequentially switch and select the document box function, copy function, printer function, and facsimile function using the application switching key on the operation panel 2040. The MFP 20a enters the document box mode when the document box function is selected, and enters the copy mode when the copy function is selected. Further, the MFP 20a enters the printer mode when the printer function is selected, and enters the facsimile mode when the facsimile mode is selected.

Further, the network interface 2050 is an interface for data communication using a communication network. PCI bus 2022 electrically connects short-range communication circuit 2020 and network interface 2050 to ASIC 2006 .

FIG. 4 is a diagram illustrating an example of the functional configuration of the server according to the first embodiment. Here, the server 10 is an example of an information processing device. As shown in FIG. 4, the server 10 includes a web service processing section 11, a portal service section 12, an application data management section 13, and an input/output service processing section 14.

The web service processing unit 11 is a module that configures a web application screen based on data stored in the input/output service processing unit 14 and requests the input/output service processing unit 14 to execute processing. Note that in the following explanation, the application may be abbreviated as an application.

The web service processing unit 11 includes a screen configuration unit 111 and an application execution unit 112. The screen configuration unit 111 configures a web application screen based on the information acquired from the input/output service processing unit 14. The application execution unit 112 executes processing in response to requests from users.

The portal service unit 12 provides the user with a UI for application development by displaying it via the browser 21 of the device 20, and performs new registration and changes of the application in accordance with the user's operations. The application here is, for example, an application that connects various processes (components) and executes one flow.

The portal service section 12 includes a UI providing section 121 and an application registration section 122. The UI providing unit 121 provides a predetermined UI to the user via the browser of the device 20 based on the screen content of the portal screen information 16. The application registration unit 122 receives a request from a user and registers the generated application in the input/output service processing unit 14 via the UI. As an application to be registered in the input/output service processing unit 14, a web application executed on the web may be registered.

The application data management unit 13 manages data related to applications. The data regarding the application includes parameters and setting values for each parameter. The application data management section 13 includes a UI providing section 131 and an application data registration section 132. A method for managing parameters and set values will be described later.

The input/output service processing section 14 includes an application management section 141 and an input/output logic processing section 142. The application management unit 141 stores and manages the processing contents of the application as application information 15. The input/output logic processing unit 142 receives an application execution request and executes the flow. The input/output logic processing unit 142 executes a flow by combining the OCR 171, file conversion 172, etc. of the component 17.

FIG. 5 is a sequence diagram for changing parameter settings in the first embodiment. As shown in FIG. 5, the device 20 first obtains an application management screen display request from the user via the browser 21 (step S101). The device 20 requests the UI providing unit 121 of the portal service unit 12 to obtain an application management screen via the browser 21 (step S102).

The UI providing unit 121 generates an application management screen (step S103). Then, the UI providing unit 121 provides the generated application management screen to the browser 21 (step S104). The device 20 displays an application management screen via the browser 21 (step S105).

Next, the device 20 obtains a request to change the released application from the user via the browser 21 (step S106). At this time, the device 20 acquires information on the original app and information on the app after the change based on the user's operation. The device 20 requests the UI providing unit 121 to change the released application via the browser 21 (step S107). The UI providing unit 121 requests the application registration unit 122 to change the released application (step S108).

The application registration unit 122 requests the application management unit 141 of the input/output service processing unit 14 to obtain application information (step S109). The application management unit 141 acquires application information (step S110), and returns the acquisition result to the application registration unit 122 (step S111). Further, the application registration unit 122 returns the obtained result to the UI providing unit 121 (step S112). Then, the UI providing unit 121 returns the obtained result to the device 20 (step S113). The device 20 displays a parameter mapping creation screen via the browser 21 (step S114).

The device 20 acquires the pre-change parameters and post-change parameters of the app created by the user based on the parameter association creation screen (step S115), and also acquires a parameter association registration request (step S116). The browser 21 requests the UI providing unit 121 to register the parameter association (step S117). The UI providing unit 121 requests the app registration unit 122 to register the parameter association (step S118). Furthermore, the app registration unit 122 requests the app data registration unit 132 of the app data management unit 13 to register the parameter association (step S119).

The application data registration unit 132 changes the parameter setting values of each user who uses the application according to the association created by the user in step S116 (step S120). The application data registration unit 132 returns the change result to the application registration unit 122 (step S121). The application registration unit 122 returns the change result to the UI providing unit 121 (step S122). The UI providing unit 121 returns the change result to the browser 21 (step S123). The device 20 displays the change result via the browser 21 (step S124).

Here, it is assumed that the application parameters before and after changes by the user are as follows.
·Change before
FlowControl.CustomParameters2.TextParameters (type: string, default: "")
FlowControl.CustomParameters3.NumberParameters (type: number, default: 0)
OCR.ExecuteOCR.OutputFileFormat (type: string, default: "PDF")
GoDrive.UploadFile.FolderId (type: string, default: "Root")
・After change
FlowControl.CustomParameters2.BooleanParameters (type: boolean, default: true)
FlowControl.CustomParameters3.TextParameters (type: string, default: "")
OCR.ExecuteOCR.OutputFileFormat (type: string, default: "PDF")
GoDriveV2.UploadFile.FolderId (type: string, default: "Root")

FIG. 6 is a diagram showing an example of parameters before change. Assume that the parameter settings before the change were as shown in FIG. 6. At this time, as shown in FIG. 7, the device 20 receives the parameter mapping settings set by the user via the parameter mapping creation screen displayed on the browser 21. Then, the portal service unit 12 changes the parameters of each user who uses the application according to this association. FIG. 8 is a diagram showing an example of changed parameters. The parameter setting values after the change are as shown in FIG. 8.

Here, as shown in FIG. 7, the correspondence between the parameters before and after the change can be expressed in JSON format. The key in the JSON format data is the identifier of the parameter before change, and the value corresponding to the key is the identifier of the parameter after change.

In the example of FIG. 7, the parameter before the change, "FlowControl.CustomParameters3.NumberParameters," and the parameter after the change, "FlowControl.CustomParameters2.BooleanParameters," are not associated. In this way, the information processing system of the first embodiment may not create an association for parameters for which the user has determined that the setting value does not need to be maintained.

Figure 9 shows an example of a parameter whose setting value the user has determined does not need to be maintained. If the parameter setting value is not maintained before and after a change using this embodiment, the parameter setting value after the change will be as shown in Figure 9. In other words, the portal service unit 12 discards the setting values of parameters other than the parameter "OCR.ExecuteOCR.OutputFileFormat" whose key matches exactly before and after the change. The portal service unit 12 that discards the setting value does not specify the setting value as shown in Figure 9, but replaces it with a specified initial value when the application is executed.

In this way, in the information processing system of the first embodiment, when an application is changed, the portal service unit 12 receives from the device 20 a designation for associating the application's parameters before and after the change. . According to the correspondence received by the portal service unit 12, the application data management unit 13 converts the setting value for each user set in the first parameter before the application change into the first parameter after the application change. The setting value of the second parameter associated with the first parameter is set. In the first embodiment, the portal service section 12 functions as a correspondence reception section. Further, the application data management section 13 functions as a setting section. As a result, when changing the parameter name or selectable parameters of a created application, the information processing system of the first embodiment can receive a correspondence between the parameters of the application before the change and the application after the change. Screens can be provided to app developers. Therefore, the information processing system of the first embodiment can support the development of an application that can appropriately take over setting values for each user.

(Second embodiment)
A second embodiment will be described. In the following description, unless otherwise specified, it is assumed that the basic configuration and functions of each embodiment are the same as those of the first embodiment. Each embodiment will be explained mainly regarding the differences from the first embodiment.

In the second embodiment, the application registration unit 122 automatically associates parameters. Further, the device 20 displays on the browser 21 a UI for checking the automatically performed association and making manual corrections, thereby providing the user with the UI.

The application registration unit 122 can associate parameters with similar names before and after the change based on the Levenshtein distance or the like. Consider that the application registration unit 122 searches for a parameter similar to the parameter "GoDrive.UploadFile.FolderId (type: string, default: "Root")" before change. At this time, the changed parameter "OCR.ExecuteOCR.OutputFileFormat (type: string, default: "PDF")" has almost no matches with the search source parameter, and it is predicted that the Levenshtein distance will increase. can. Therefore, it cannot be said that the parameters before the change and the searched parameters are similar.

On the other hand, the changed parameter "GoDriveV2.UploadFile.FolderId (type: string, default: "Root")" is simply the string "V2" added to the parameter to be searched, so the Levenshtein distance can be predicted to be smaller, and can be said to be similar.

For example, the application registration unit 122 associates the parameter P after the change with the parameter before the change using the following logic.
(1) The application registration unit 122 uses a list of parameters existing in the application before change as candidates for association.
(2) The application registration unit 122 excludes from candidates parameters that have already been associated with parameters (other than P) that exist in the changed application.
(3) When a parameter whose type matches P exists in the candidates, the application registration unit 122 excludes a parameter whose type does not match P from the candidates.
(4) The application registration unit 122 associates with P the candidate whose parameter name has the smallest Levenshtein distance with P among the candidates.

After the association is made by the application registration unit 122, the UI providing unit 121 displays a screen as shown in FIG. 11 on the browser 21 of the device 20, which displays a message indicating that the association has been automatically made. FIG. 11 is a diagram showing an example of a parameter mapping creation screen.

FIG. 10 is a sequence diagram for changing parameter settings according to the second embodiment. As shown in FIG. 10, the device 20 first obtains a request from the user to display an application management screen on the browser 21 (step S201). The device 20 requests the UI providing unit 121 of the portal service unit 12 to obtain an application management screen via the browser 21 (step S202).

The UI providing unit 121 generates an application management screen (step S203). Then, the UI providing unit 121 provides the generated application management screen to the browser 21 (step S204). The device 20 displays an application management screen (step S205).

Next, the device 20 obtains a request to change the released application from the user via the browser 21 (step S206). At this time, the user inputs the information of the application to be changed and the information of the application to be changed. The device 20 requests the UI providing unit 121 to change the released application (step S207). The UI providing unit 121 requests the application registration unit 122 to change the released application (step S208).

The application registration unit 122 requests the application management unit 141 of the input/output service processing unit 14 to obtain application information (step S209). The application management unit 141 obtains the application information (step S210) and returns the obtained result to the application registration unit 122 (step S211).

The application registration unit 122 generates a parameter association based on the obtained result (step S212). For example, the application registration unit 122 performs the association according to the above logic. The application registration unit 122 returns the results of the association to the UI providing unit 121 (step S213). Then, the UI providing unit 121 returns the association result to the browser 21 (step S214). The device 20 displays a screen for checking and modifying the associated parameters via the browser 21 (step S215).

The device 20 confirms and corrects the correspondence between the application parameters before and after the change made by the user via the browser 21 as necessary (step S216), and requests the registration of the parameter correspondence. Acquire (step S217). The device 20 requests the UI providing unit 121 to register the parameter association via the browser 21 (step S218). The UI providing unit 121 requests the application registration unit 122 to register the parameter association (step S219). Further, the application registration unit 122 requests the application data registration unit 132 of the application data management unit 13 to change the setting value (step S220).

In response to the request, the application data registration unit 132 changes the set value of the parameter according to the association registered in step S217 (step S221). The application data registration unit 132 returns the change result to the application registration unit 122 (step S222). The application registration unit 122 returns the change result to the UI providing unit 121 (step S223). The UI providing unit 121 returns the change result to the browser 21 (step S224). The browser 21 displays the change result (step S225).

In this way, the application data management unit 13 changes the setting value of the first parameter to the first parameter among the changed parameters of the application whose type matches the first parameter. The Levenshtein distance is set to the setting value of the second parameter that is the minimum.

(Third embodiment)
In the third embodiment, the UI providing unit 121 provides a UI that allows the user to associate parameters before and after change through an intuitive operation. FIGS. 12 to 17 are diagrams showing examples of UIs for associating parameters.

First, after automatically associating parameters using the method of the second embodiment, the UI providing unit 121 provides a UI as shown in FIG. 12. As shown in FIGS. 13 and 14, the UI providing unit 121 changes the correspondence between parameters when the user drags and drops the edges (vertices) of edges connecting objects corresponding to each parameter. . In the example of FIG. 13, the cells of the table correspond to objects.

Furthermore, as shown in FIG. 15, when the user drags and drops one end of a side into an area where no object of any parameter exists, the UI providing unit 121 deletes the correspondence indicated by the side.

In this way, the UI providing unit 121 provides a UI that allows the first parameter to be associated with the second parameter by manually moving the object on the screen that corresponds to each parameter.

The UI providing unit 121 can provide a UI that displays objects corresponding to each parameter and edges between the objects in a manner according to the plausibility of the association between the objects. As shown in FIG. 16, the UI providing unit 121 may change the thickness of the sides and the size of the ends depending on the degree of similarity between parameters. For example, the UI providing unit 121 makes the sides thicker and the areas of the ends larger as the Levenshtein distance between parameter names becomes smaller.

Note that the smaller the Levenshtein distance, the greater the plausibility. Therefore, if the Levenshtein distance is D, the plausibility can be expressed as 1/D or -D.

Further, when the cursor points to an object corresponding to each parameter, the UI providing unit 121 provides a UI that displays information regarding the object pointed with the cursor. The example in FIG. 17 is a display example of the explanation of the parameter "GoDriveV2.UploadFile.FolderId (type: string, default: "Root")". Further, the UI providing unit 121 may display candidates for the parameter setting values before the change or the parameter setting values after the change.

(Fourth embodiment)
As a fourth embodiment, an example will be described in which a plurality of applications are integrated into one application. For example, according to the fourth embodiment, multiple apps with the same function but different storage services, such as ``Scan to Go Drive'' or ``Scan to Box,'' can be used with ``Scan to Go Drive'' or ``Scan to Box,'' which has a storage selection function. You can change it to a new app called "Storage".

Figure 18 is a diagram showing an example of a screen for integrating applications. As shown in Figure 18, the screen for integrating applications displays check boxes for specifying multiple sources of applications to be changed (migrated) and a pop-up for creating parameter associations for each checked application.

The example in FIG. 18 is an example in which device 20, in response to a user operation, is attempting to replace the "Scan to Go Drive" app and "Scan to Box" app that are already in use with the "Scan to Storage" app that is being created. Also, the example in FIG. 18 is an example in which device 20 is setting up to link the parameters of the "Scan to Go Drive" app to one of the parameters of "Scan to Storage" in order to maintain the user's settings during this replacement. Also, device 20 is configured not to replace the "Scan to Mail" app with the "Scan to Storage" app.

FIG. 19 is a diagram showing a sequence for integrating applications according to the fourth embodiment. As shown in FIG. 19, the device 20 first obtains a request from the user to display an application management screen to the browser 21 (step S301). The device 20 requests the UI providing unit 121 of the portal service unit 12 to obtain an application management screen via the browser 21 (step S302).

The UI providing unit 121 generates an application management screen (step S303). Then, the UI providing unit 121 provides the generated application management screen to the browser 21 (step S304). The device 20 displays an application management screen (step S305).

Here, the information processing system 1 repeats the following steps S306 to S324 as many times as there are applications to be changed. The device 20 obtains a request to display a parameter association creation screen specified by the user via the browser 21 (step S306). The browser 21 requests the UI providing unit 121 to obtain application information (step S307). The UI providing unit 121 requests the application registration unit 122 to obtain application information (step S308). The application registration unit 122 requests the application management unit 141 to obtain application information (step S309). The application management unit 141 acquires application information (step S310), and returns the acquisition result to the application registration unit 122 (step S311).

The application registration unit 122 returns the obtained result to the UI providing unit 121 (step S312). The UI providing unit 121 returns the obtained result to the browser 21 (step S313). The browser 21 displays a parameter mapping creation screen (step S314). The device 20 acquires the pre-change parameters and the post-change parameters of the application for which the association has been created from the user via the parameter association creation screen (step S315).

The device 20 requests the UI providing unit 121 to register the parameter association via the browser 21 (steps S316 and S317). The UI providing unit 121 requests the application registration unit 122 to register the association of parameters (step S318). The application registration unit 122 requests the application management unit 141 to register the association of parameters (step S319). The application management unit 141 registers the association of parameters (step S320).

The application management unit 141 returns the registration result to the application registration unit 122 (step S321). The application registration unit 122 returns the registration result to the UI providing unit 121 (step S322). The UI providing unit 121 returns the registration result to the browser 21 (step S323). The browser 21 displays the registration result (step S324).

FIG. 20 is a diagram showing a sequence of using applications after integration according to the fourth embodiment. As shown in FIG. 20, when the user requests to start an application via the browser 21 (step S401), the device 20 requests the application data registration unit 132 via the browser 21 to obtain the application screen and settings. request (step S402).

The application data registration unit 132 obtains the reference application ID (step S403). Furthermore, the application data registration unit 132 acquires application settings (step S404). Then, the application data registration unit 132 requests the application management unit 141 to obtain information on the application screen (step S405).

The application management unit 141 acquires the management information of the application (step S406), and notifies the application data registration unit 132 of the change in the application (step S407). At this time, the application management unit 141 returns "301 Moved" indicating that the application has been moved.

Further, the application management unit 141 requests acquisition of application screen information using a new application ID (step S408). The application management unit 141 acquires the management information of the application (step S409), and notifies the acquired screen information of the application to the application data registration unit 132 (step S410).

The application data registration unit 132 acquires the association of parameters (step S411). The application management unit 141 acquires the parameter correspondence (step S412), and returns the acquired correspondence (step S413).

The application data registration unit 132 sets setting values so that the application corresponds to the parameter association (step S414). Further, the application data registration unit 132 updates the referenced application ID in order to prevent parameter association from occurring next time onward (step S415). The application data registration unit 132 returns the application screen and settings to the browser 21 (step S416). The browser 21 displays the application screen (step S417).

FIG. 21 is a diagram illustrating an example of association of setting values. Further, FIG. 22 is a diagram showing an example of parameter setting values before and after integration. By providing the parameter correspondence as shown in FIG. 21, the parameter setting values before and after integration become as shown in FIG. 22, and the setting value of the parameter "storage.service" can be maintained before and after integration.

On the other hand, FIG. 23 is a diagram showing an example of parameters before and after integration when the set values are not maintained. If the parameter mapping as shown in FIG. 21 is not provided, the parameter setting values before and after integration will be as shown in FIG. 23, and the setting value of the parameter "storage.service" will not be maintained before and after integration.

In this way, when a change is made to integrate a plurality of applications into one application, the portal service unit 12 accepts the designation of the correspondence between the parameters before and after the change of one application. The input/output service processing unit 14 converts the setting value set for each user into the first parameter of each of the plurality of applications into the second parameter of one application according to the correspondence received by the portal service unit 12. Set to the set value.

(Fifth embodiment)
The information processing system of the fifth embodiment is an example in which one application is divided into multiple applications. The information processing system of the fifth embodiment uses one application called "Scan to Storage" with a storage selection function, "Scan to Go Drive with Go Keep" or "Scan You can change it to multiple apps such as "to Box with Box Notes".

FIG. 24 is a diagram showing an example of a screen for dividing an application. As shown in FIG. 24, the UI providing unit 121 displays a check box for specifying the change (migration) source of the application and a pop-up that allows setting of multiple change destination applications on the screen for dividing the application.

The example in FIG. 24 is an example in which the "Scan to Storage" application that the user is already using is replaced with the "Scan to Storage" application that is being created. Here, the settings are such that the "Scan to Storage" app can be replaced with the already created "Scan to Box" app. Therefore, the UI providing unit 121 uses a popup that allows you to set change conditions for the "Scan to Storage" application to change the storage service selected by the user to the "Scan to Go Drive" application currently being created or the "Scan to Go Drive" application currently being created. It defines which of the "Scan to Go Drive" apps should be replaced.

In the information processing system of the fifth embodiment, if the user has selected a storage service other than these, or if the user has not selected one yet, it is possible to select a replacement destination at the next startup or next setup. It becomes.

FIG. 25 is a sequence diagram for dividing an application according to the fifth embodiment. As shown in FIG. 25, the device 20 first obtains a request from the user to display an application management screen (step S501). The device 20 requests the UI providing unit 121 of the portal service unit 12 to obtain an application management screen (step S502).

The UI providing unit 121 generates an application management screen (step S503). Then, the UI providing unit 121 provides the generated application management screen to the device 20 (step S504). The device 20 displays an application management screen via the browser 21 (step S505).

Here, the device 20 obtains a request from the user to display a parameter association creation screen (step S506). The device 20 requests the UI providing unit 121 to obtain application information via the browser 21 (step S507). The UI providing unit 121 requests the application registration unit 122 to obtain application information (step S508). The application registration unit 122 requests the application management unit 141 to obtain application information (step S509). The application management unit 141 acquires application information (step S510), and further, the application management unit 141 checks whether the change source application is registered as a change source of another application (step S511). The application management unit 141 returns the acquisition result and the confirmation result to the application registration unit 122 (step S512).

The application registration unit 122 returns the acquisition result and the confirmation result to the UI providing unit 121 (step S513). The UI providing unit 121 returns the obtained result to the device 20 (step S514). The device 20 displays a parameter mapping creation screen and a change condition setting screen via the browser 21 (step S515). The device 20 acquires the parameters of the application before and after the change (step S516) and the settings of the change conditions (step S517), which are associated with each other by the user.

The device 20 also obtains a request for registration of parameter association and change conditions from the user (step S518). The device 20 requests the UI providing unit 121 to register the parameter association and change conditions via the browser 21 (step S519). The UI providing unit 121 requests the application registration unit 122 to register the parameter association and change conditions (step S520). The application registration unit 122 requests the application management unit 141 to register the parameter association and change conditions (step S521). The application management unit 141 registers the association of registered parameters and the change conditions (step S522).

The application management unit 141 returns the registration result to the application registration unit 122 (step S523). The application registration unit 122 returns the registration result to the UI provision unit 121 (step S524). The UI provision unit 121 returns the registration result to the browser 21 (step S525). The browser 21 displays the registration result (step S526).

FIG. 26 is a sequence diagram of using the divided application of the fifth embodiment. As shown in FIG. 26, the device 20 obtains an application activation request requested by the user via the browser 21 (step S601). The device 20 requests the application data registration unit 132 to obtain the application screen and settings via the browser 21 (step S602).

The application data registration unit 132 obtains the reference application ID (step S603). Furthermore, the application data registration unit 132 obtains application settings (step S604). Then, the application data registration unit 132 requests the application management unit 141 to obtain information on the application screen (step S605).

The application management unit 141 acquires the management information of the application (step S606), and notifies the application data registration unit 132 of the change in the application and the change conditions (step S607). Here, the application data registration unit 143 calculates the ID of the new application from the application settings and change conditions (step S608).

Further, the application data registration unit 132 requests acquisition of application screen information using the new application ID (step S609). The application management unit 141 acquires management information of the application (step S610), and notifies the acquired screen information of the application to the application data registration unit 132 (step S611).

The application data registration unit 132 makes a request to obtain a parameter association (step S612). The application management unit 141 acquires the parameter correspondence according to the request (step S613), and returns the acquired correspondence (step S614).

The application data registration unit 132 sets setting values so that the application corresponds to the parameter association (step S615). Further, the application data registration unit 132 updates the referenced application ID in order to prevent parameter association from occurring next time onward (step S616). The application data registration unit 132 returns the application screen and settings to the device 20 (step S617). The device 20 displays the application screen via the browser 21 (step S618).

FIG. 27 is a diagram illustrating an example of association of setting values. Here, the portal service unit 12 can maintain the setting value of the parameter "storage.service" before and after division by providing the parameter correspondence as shown in FIG. On the other hand, FIG. 28 is a diagram showing an example of parameters before and after division when the set values are not maintained. If the portal service unit 12 does not provide the parameter correspondence as shown in FIG. 21, the portal service unit 12 does not maintain the setting value of the parameter "storage.service" before and after the division, as shown in FIG. 28.

In this way, when a change is made to split one application into multiple applications, the portal service unit 12 accepts a specification of the association between the parameters before the change and the parameters after the change of the multiple applications. In accordance with the association accepted by the portal service unit 12, the input/output service processing unit 14 sets the setting value of the first parameter of one application for each user as the setting value of the second parameter of each of the multiple applications.

In the fourth embodiment, the integration of applications is described, and in the fifth embodiment, the division of applications is described, but the applications before and after the change may be many-to-many. FIG. 29 is a diagram showing an example of a screen for changing applications in a many-to-many manner. By using a screen like that in FIG. 29, it is possible to maintain the setting values using a sequence similar to that of the fifth embodiment.

FIG. 30 is a functional block diagram of the information processing system of the first embodiment. FIG. 30 is a functional block diagram in which specific functions are extracted from the functions explained in FIG. 4.

As shown in FIG. 30, when the application is changed, the association receiving unit 12a receives from the device 20 a designation of the association between the parameters of the application before the change and the parameters after the change. Then, the setting unit 13a sets the setting value for each user of the first parameter before the change of the application to the first parameter after the change of the application, according to the correspondence received by the correspondence reception unit 12a. is set to the setting value of the second parameter associated with the parameter.

In the embodiment, the portal service section 12 functions as a correspondence reception section. Further, the application data management section 13 functions as a setting section. Further, the parameter information 13b is held in a predetermined storage area provided in the server 10 or the like.

Each function of the embodiments described above can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to execute each function using software, such as a processor implemented using an electronic circuit. In addition, the "processing circuit" in this specification refers to an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), or a conventional Includes devices such as circuit modules.

The devices described in the examples are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein. As such, server 10 may include multiple computing devices, such as a server cluster. The plurality of computing devices communicate with each other via any type of communication link, including a network or shared memory, to perform the processes disclosed herein. Similarly, device 20 may include multiple computing devices that communicate with each other.

Additionally, server 10 and device 20 can be configured to share the disclosed processing steps, eg, FIG. 1, in various combinations. For example, a process performed by a given unit may be performed by device 20. Similarly, the functions of a given unit can be performed by device 20. Further, each element of the server 10 and the device 20 may be combined into one server device, or may be divided into a plurality of devices.

Note that the device 20 may be any device other than an MFP or a PC as long as it has a communication function. The device 20 is, for example, an output device such as a PJ (Projector), an IWB (Interactive White Board: a whiteboard having an electronic blackboard function capable of mutual communication), a digital signage, a HUD (Head Up Display) device, or an industrial A machine or an imaging device or a sound collection device or a medical device or a networked home appliance or a car (Connected Car) or a notebook PC (Personal Computer) or a mobile phone or a smartphone or a tablet terminal or a game console or a PDA (Personal Digital Assistant) or a digital camera or a wearable. It may be a PC or a desktop PC.

1 Information processing system 10 Server 11 Web service processing section 12 Portal service section 13 Application data management section 14 Input/output service processing section 15 Application information 16 Portal screen information 17 Component 111 Screen composition section 112 Application execution section 121 UI provision section 122 Application registration Section 131 UI providing section 132 Application data registration section 141 Application management section 142 Input/output logic processing section 171 OCR
172 File conversion

Japanese Patent Application Publication No. 2018-014079

Claims (10)

An information processing system comprising a device and a server,
The server is
a correspondence receiving unit that receives, when an application is changed, a specification of a correspondence between the parameters of the application before the change and the parameters after the change;
In accordance with the association received by the association acceptance unit, the setting value for each user of the first parameter before the change of the application is set as the first parameter after the change of the application. a setting section configured to set a set value of the associated second parameter;
An information processing system equipped with The setting unit sets the setting value of the first parameter to one of the changed parameters of the application whose type matches the first parameter, according to the association received by the association receiving unit. 2. The information processing system according to claim 1, wherein the second parameter is set to a setting value that has a minimum Levenshtein distance between the first parameter and the first parameter. Claim 1, further comprising a UI providing unit that provides a UI that allows the first parameter and the second parameter to be associated with each other by manually moving an object on the screen corresponding to each parameter. The information processing system described in . The information processing system according to claim 1, further comprising a UI providing unit that provides a UI that displays objects corresponding to each parameter and edges between the objects in a manner according to the plausibility of the correspondence between the objects. 2. The information processing system according to claim 1, further comprising a UI providing unit that, when a cursor is pointed at an object corresponding to each parameter, provides a UI that displays information regarding the object pointed at by the cursor. When a change is made to integrate a plurality of applications into one application, the association accepting unit accepts a specification of an association between parameters before change and parameters after change of the one application,
The setting unit sets a setting value for each user of a first parameter of each of the plurality of applications to a setting of a second parameter of the one application according to the association received by the association receiving unit. The information processing system according to claim 1, wherein the information processing system is set to a value. the association receiving unit receives, when a change is made to divide one application into a plurality of applications, a designation of association between parameters before the change and parameters after the change for the plurality of applications;
The information processing system according to claim 1, characterized in that the setting unit sets a user-specific setting value of a first parameter of the one application to a setting value of a second parameter of each of the multiple applications in accordance with the association accepted by the association accepting unit. a correspondence receiving unit that receives from a device a specification of a correspondence between the parameters of the application before the change and the parameters after the change when the application is changed;
In accordance with the association received by the association acceptance unit, the setting value for each user of the first parameter before the change of the application is set as the first parameter after the change of the application. a setting unit configured to set a set value of the associated second parameter;
An information processing device comprising: An information processing method executed by an information processing device, the method comprising:
When an application is changed, a correspondence receiving step of accepting from a device a specification of a correspondence between the parameters of the application before the change and the parameters after the change;
In accordance with the association received in the association acceptance step, the setting value for each user of the first parameter before the change of the application is set as the first parameter after the change of the application. a setting step of setting a set value of the associated second parameter;
An information processing method characterized by comprising: A program executed on an information processing device,
When an application is changed, a correspondence receiving step of accepting from a device a specification of a correspondence between the parameters of the application before the change and the parameters after the change;
In accordance with the correspondence received in the correspondence reception step, the setting value for each user of the first parameter before the change of the application is set as the first parameter after the change of the application. a setting step of setting a set value of the associated second parameter;
A program that causes a computer to execute

Images