JP6852550B2 - Information processing equipment, merging method and program - Google Patents

Description

The present invention relates to information processing devices, merging methods and programs.

Conventionally, an information processing device such as a multifunction device cooperates with a server on an intranet that centrally manages an address book such as an LDAP (Lightweight Directory Access Protocol) server or Active Directory to display an address book managed by the server. , A technique for synchronizing with an address book managed by an information processing device is known (see, for example, Patent Document 1).

In such a technique, generally, an address book is acquired from a server on an intranet, an address book is acquired from an information processing device, both address books are merged, and the merged address book is registered in the information processing device. By installing software having such a function in the information processing device, the server on the intranet that manages the address book and the information processing device are linked.

By the way, in recent years, cloud services that manage information such as address books on the Internet have also been provided, but in such cloud services that manage information such as address books on the Internet, for each service, Generally, specifications such as data management format and acquisition format (protocol) are different.

Therefore, when linking a cloud service that manages information such as an address book on the Internet with an information processing device, as described above for each cloud service so that all cloud services that may be linked can be supported. It is necessary to develop software, and various costs such as human cost and monetary cost are incurred.

The present invention has been made in view of the above circumstances, and provides an information processing device, a merging method, and a program capable of linking with a plurality of cloud services that manage information with different specifications while suppressing costs. The purpose.

In order to solve the above-mentioned problems and achieve the object, the information processing apparatus according to one aspect of the present invention corresponds to a plurality of clouds that manage a first information composed of a plurality of records. A plurality of first information acquisition units capable of acquiring the first information in a manner corresponding to the cloud, and a second information acquisition unit for acquiring second information composed of a plurality of records. If, on the second information acquired by the second information acquiring section among the plurality of records included in the acquired first information by one of the plurality of first information acquiring unit A merge unit that merges one or more records that do not correspond to any of the plurality of included records into the second information, and processing based on the merge information in which the first information and the second information are merged. The merge unit includes a processing unit for performing the above, and the merge unit is a record included in the first information and the second information, and whether or not the records whose data is guaranteed to be unique match. The presence or absence of the above correspondence is determined by.

According to the present invention, it is possible to link with a plurality of cloud services that manage information with different specifications while suppressing costs.

FIG. 1 is a block diagram showing an example of the configuration of the information processing system of the present embodiment. FIG. 2 is a block diagram showing an example of the hardware configuration of the information processing apparatus of the present embodiment. FIG. 3 is a block diagram showing an example of the hardware configuration of the cloud server of the present embodiment. FIG. 4 is a block diagram showing an example of the functional configuration of the information processing apparatus of the present embodiment. FIG. 5 is a diagram showing an example of the workflow information creation screen of the present embodiment. FIG. 6 is a diagram showing an example of an address book for one person in the first information of the present embodiment. FIG. 7 is a diagram showing an example of an address book for one person in the second information of the present embodiment. FIG. 8 is a diagram showing an example of conversion information of the present embodiment. FIG. 9 is a diagram showing an example of the merge result (merge information) of the present embodiment. FIG. 10 is a diagram showing an example of the address book synchronization setting screen of the present embodiment. FIG. 11 is a sequence diagram showing an example of the flow of the processing procedure of the present embodiment. FIG. 12 is a sequence diagram showing an example of the flow of the procedure of the synchronous processing of the present embodiment. FIG. 13 is a flowchart showing an example of the flow of the procedure of the merge process of the present embodiment. FIG. 14 is a diagram showing an example of an address book for one person in the first information of the first modification. FIG. 15 is a flowchart showing an example of the flow of the procedure of the merge process of the modified example 1. FIG. 16 is a diagram showing an address book managed by the cloud server. FIG. 17 is a sequence diagram showing an example of the operation procedure of the information processing system of the modified example. FIG. 18 is a sequence diagram showing an example of the flow of the procedure for synchronizing the shared address book of the modified example. FIG. 19 is a diagram showing an example of the workflow indicated by the workflow information of the synchronous processing of the shared address book of the modified example. FIG. 20 is a sequence diagram showing an example of the operation procedure of the information processing system of the modified example. FIG. 21 is a diagram showing an example of account information managed by the information processing device. FIG. 22 is a sequence diagram showing an example of the flow of the procedure for synchronizing the personal address book of the modified example. FIG. 23 is a diagram showing an example of the workflow indicated by the workflow information of the synchronization processing of the personal address book of the modified example. FIG. 24 is a flowchart showing an operation example of the execution control unit of the modified example.

Hereinafter, embodiments of the information processing apparatus, the merging method, and the program according to the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a block diagram showing an example of the configuration of the information processing system 1 of the present embodiment. As shown in FIG. 1, the information processing system 1 includes an information processing device 10, a user terminal 20, a mobile terminal 30, and a cloud server 40-1 to 40-n (n is a natural number of 2 or more). ..

The information processing device 10 and the user terminal 20 are connected to the intranet 2, and the cloud servers 40-1 to 40-n are connected to the Internet 4. Further, the intranet 2 and the Internet 4 are connected to each other via a firewall 3. That is, in the present embodiment, the information processing device 10 and the user terminal 20 are communicably connected to the cloud servers 40-1 to 40-n via the intranet 2, the firewall 3, and the Internet 4.

The mobile terminal 30 can be connected to the Internet 4 by using a telephone line such as 3G or 4G or Wi-Fi (registered trademark), and communicates with the cloud servers 40-1 to 40-n via the Internet 4. Can be connected as possible.

The intranet 2 may be a LAN (Local Area Network) or a WAN (Wide Area Network). The network composed of the intranet 2, the firewall 3, and the Internet 4 may be configured by wire, may be configured wirelessly, or may be configured by using both in combination.

In the present embodiment, the information processing device 10 will be described by taking as an example an image forming device such as a multifunction device (MFP: Multifunction Peripheral) or a facsimile machine, but the present invention is not limited thereto. The multifunction device has at least two functions of a copying function, a printing function, a scanner function, and a facsimile function.

FIG. 2 is a block diagram showing an example of the hardware configuration of the information processing apparatus 10 of the present embodiment. As shown in FIG. 2, the information processing device 10 of the present embodiment includes an ADF (Auto Document Feeder) 101, a scanner unit 102, a paper output tray 103, a display panel 104, and a paper feed table. The 105, the print engine 106, the output tray 107, the network I / F 108, and the controller 110 are provided.

The network I / F 108 is an interface for the information processing device 10 to perform communication via the intranet 2, and examples thereof include an Ethernet (registered trademark) and a USB (Universal Bus) interface. The network I / F 108 can communicate by, for example, the TCP / IP protocol. The network I / F 108 also functions as an interface for executing facsimile transmission when the information processing apparatus 10 functions as a facsimile. Therefore, the network I / F 108 is also connected to the telephone line.

The controller 110 controls each part of the information processing device 10, and includes a CPU (Central Processing Unit) 111, a ROM (Read Only Memory) 112, a RAM (Random Access Memory) 113, and an ASIC (Application Specific Integrated Circuit). ) 114 and an HDD (Hard Disk Drive) 115.

The CPU 111 executes a program stored in the ROM 112, the HDD 115, or the like using the RAM 113 as a work area. As a result, the CPU 111 controls the operation of the entire information processing device 10. Specifically, the CPU 111 controls the drive of the scanner unit 102 to realize the scan operation, or controls the drive of the print engine 106 to realize the print operation.

Further, the CPU 111 displays information on the display panel 104 and notifies the CPU 111 of the information input via the display panel 104. Further, the CPU 111 receives information from the outside or transmits information to the outside via the network I / F 108.

The ASIC 114 generates drawing information based on the image information to be printed out. This drawing information is information for drawing an image to be formed by the print engine 106 in the image forming operation. Further, the ASIC 114 processes the imaging data (scan data) input from the scanner unit 102 to generate image data. This image data is stored in the HDD 115 as a result of the scanner operation, or is output to the outside by facsimile transmission or the like via the network I / F 108.

Since the information processing device 10 of the present embodiment has the above-described configuration, for example, the document is scanned to capture image data, and the captured image data is subjected to data processing according to a program. Can be done.

Returning to FIG. 1, the cloud servers 40-1 to 40-n are server devices that manage the address book on the Internet, additionally register the address book, or provide the address book to the outside in response to an external request. Each can be realized by one or more computers. In the present embodiment, the cloud servers 40-1 to 40-n are operated by different operating entities, and the specifications such as the address book data management format and acquisition format (protocol) are different from each other as an example. I will explain, but it is not limited to this. In the following description, when it is not necessary to distinguish between the cloud servers 40-1 to 40-n, they may be simply referred to as the cloud server 40.

FIG. 3 is a block diagram showing an example of the hardware configuration of the cloud server 40 of the present embodiment. As shown in FIG. 3, the cloud server 40 includes a control device 401 such as a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit), and a main storage device such as a ROM (Read Only Memory) and a RAM (Random Access Memory). 402, auxiliary storage device 403 such as HDD (Hard Disk Drive) and SSD (Solid State Drive), display device 404 such as display, input device 405 such as keyboard and mouse, and communication device 406 such as communication interface. , And has a hardware configuration using a normal computer.

The control device 401 realizes a function of managing an address book on the Internet by executing a program stored in the ROM of the main storage device 402, the auxiliary storage device 403, or the like using the RAM of the main storage device 402 as a work area. ..

Returning to FIG. 1, the user terminal 20 is a terminal device for making various settings for the information processing device 10, and examples thereof include, but are limited to, a PC (Personal Computer) and a smart device. is not it.

The mobile terminal 30 additionally registers an address book with the cloud server 40, and includes, but is not limited to, smart devices and mobile phones.

The hardware configuration of the user terminal 20 and the mobile terminal 30 can be realized by the same configuration as the cloud server 40.

FIG. 4 is a block diagram showing an example of the functional configuration of the information processing device 10 of the present embodiment. As shown in FIG. 4, the information processing apparatus 10 includes a creation unit 120, a workflow storage unit 130, a setting unit 140, an execution control unit 150, an address book storage unit 160, and a function execution unit 170. .. The creation unit 120, the setting unit 140, the execution control unit 150, and the function execution unit 170 can be realized by, for example, the CPU 111, the RAM 113, the network I / F 108, and the like. The workflow storage unit 130 and the address book storage unit 160 can be realized by, for example, HDD 115 or RAM 113.

The creation unit 120 creates workflow information in which one or more components to be executed and the execution order are defined, and stores the workflow information in the workflow storage unit 130. A component is software that has been made into parts (part-by-part), and by combining a plurality of components, it is possible to generate software (application) that executes a desired function. That is, the workflow information defines the combination of components required to execute the desired function and the execution order thereof.

Since the substance of the component is held by the execution control unit 150, which will be described later, it is not necessary to include the substance of the component to be executed in the workflow information. In the workflow information, one or more components to be executed and the execution order may be defined by using information that can identify the component to be executed (for example, the ID of the component to be executed).

The creation unit 120 generates, for example, the workflow information creation screen as shown in FIG. 5, and creates the workflow information based on the operation input from the user. In the example shown in FIG. 5, a list of component information indicating a component is displayed in the left column of the screen, and the user selects the component information of one or more components to be executed from the list of component information. (By dragging and dropping), arrange them in the order of execution in the right column of the screen. As a result, the creation unit 120 creates the workflow information. Here, it is defined to execute four components in this order: acquisition of address book from cloud A, acquisition of address book from information processing device, merge processing of both address books, and registration of address book after merge. It is the workflow information.

In the present embodiment, the workflow information creation screen is provided to the user terminal 20 or the like as a Web UI, and the user inputs an operation for creating the workflow information on the workflow information creation screen displayed on the user terminal 20. It is supposed to be done, but it is not limited to this. For example, the workflow information creation screen may be provided as a service on the cloud, or may be provided as a tool on the information processing device 10.

The setting unit 140 sets the workflow information created by the creation unit 120 and stored in the workflow storage unit 130 in the execution control unit 150. In the present embodiment, a case where the workflow information created by the creation unit 120 is stored in the workflow storage unit 130 will be described as an example, but the present invention is not limited to this, and the workflow information is fixed in advance (default). Workflow information) may be stored.

The execution control unit 150 holds a plurality of types of components, and based on the workflow information set by the setting unit 140, executes one or more components to be executed from among the held plurality of types of components in the execution order. Execute with.

In the following, the target function executed based on the workflow information is a function of synchronizing the address book managed by the cloud server 40 with the address book managed by the information processing device 10 (specifically, information processing). A function of merging the address book managed by the cloud server 40 with the address book managed by the device 10 and updating the address book managed by the information processing device 10) will be explained as an example. However, it is not limited to this. Further, the workflow information set by the setting unit 140 is described as the above-mentioned acquisition of the address book from the cloud A, acquisition of the address book from the information processing device, merge processing of both address books, and registration of the address book after the merge. The case where the workflow information is defined to execute the four components in this order will be described as an example, but the present invention is not limited to this.

The execution control unit 150 holds, for example, each component included in the list of component information described with reference to FIG. 5 as a plurality of types of components. However, as described above, in the present embodiment, the case where the target function executed based on the workflow information is the function of synchronizing the address book managed by the cloud server 40 will be described as an example. In No. 4, only the first information acquisition unit 1511-1151-n, the second information acquisition unit 152, the merge unit 153, and the processing unit 154 are illustrated as the components held by the execution control unit 150.

The component of acquiring the address book from the cloud A, which is defined in the workflow information, corresponds to the first information acquisition unit 151-1, and the component of acquiring the address book from the information processing device is the second information. It corresponds to the acquisition unit 152, the component of merging processing of both address books corresponds to the merging unit 153, and the component of registering the address book after merging corresponds to the processing unit 154.

First, the execution control unit 150 executes the first information acquisition unit 151-1 based on the workflow information (acquisition of the address book from the cloud A) set by the setting unit 140. As a result, the first information acquisition unit 151-1 is a cloud corresponding to the first information acquisition unit 151-1 among the plurality of cloud servers 40-1 to 40-n that manage the first information. The first information is acquired from a certain cloud server 40-1 in a manner corresponding to the cloud server 40-1.

The first information is information about an address book managed by the cloud server 40, and is composed of a plurality of records. Specifically, the first information is information composed of an address book of a plurality of people, and the address book for one person is composed of a unit called a record.

The first information acquisition unit 151-1 is a component prepared for acquiring the first information from the cloud server 40-1, and is a specification of the cloud server 40-1 (data management format and acquisition format (protocol). )) Performs the acquisition operation. In the present embodiment, the first information acquisition unit 151-1 uses WebApi provided by the cloud server 40-1 (by making a request) to meet the specifications of the cloud server 40-1. The acquisition operation is performed, but the acquisition operation is not limited to this.

FIG. 6 is a diagram showing an example of an address book (record) for one person in the first information of the present embodiment. In the example shown in FIG. 6, the address book (record) for one person in the first information indicates id which is a record identifier, name indicating a name (kanji), nameKana indicating a name (kana), and a telephone number. It is composed of a phoneNum, a faxNum indicating a fax number, and an email indicating an e-mail address.

In the present embodiment, since it is not defined in the workflow information, it is not executed by the execution control unit 150, but the first information acquisition unit 151-2-151-n each manages a plurality of first information. The first information can be acquired from the cloud servers 40-2 to 40-n, which are the corresponding clouds, among the cloud servers 40-1 to 40-n, in a manner corresponding to the cloud server 40.

As described above, in the present embodiment, since the information acquisition component dedicated to the cloud server 40 is prepared for each cloud server 40, specifications such as a data management format and an acquisition format (protocol) are provided for each cloud server 40. Even if they are different, we can handle them. In particular, in the present embodiment, since the software is prepared not for each function but for each component, it is not necessary to develop the software for realizing the function of synchronizing the address book for each cloud server 40. Since it is only necessary to develop the difference part (only the acquisition part whose specifications are different for each cloud server 40), it is possible to manage information with different specifications while suppressing various costs such as human costs and monetary costs. Cooperation becomes possible.

Subsequently, the execution control unit 150 executes the second information acquisition unit 152 based on the workflow information (acquisition of the address book from the information processing device) set by the setting unit 140. As a result, the second information acquisition unit 152 acquires the second information.

The second information is information about an address book managed by the information processing apparatus 10, and is composed of a plurality of records. Specifically, the second information is information composed of an address book of a plurality of people, and the address book for one person is composed of a unit called a record.

In the present embodiment, since the second information is stored in the address book storage unit 160, the second information acquisition unit 152 acquires the second information from the address book storage unit 160.

FIG. 7 is a diagram showing an example of an address book (record) for one person in the second information of the present embodiment. In the example shown in FIG. 7, the address book (record) for one person in the second information indicates id which is an identifier of the record, name indicating the name (kanji), phoneticName indicating the name (kana), and a telephone number. It is configured to include a phoneNumber, a faxNumber indicating a fax number, and a mailAddress indicating an e-mail address.

Subsequently, the execution control unit 150 executes the merge unit 153 based on the workflow information (merge process of both address books) set by the setting unit 140. As a result, the merge unit 153 has the first information acquired by the first information acquisition unit 151-1 of the first information acquisition units 1511-15-1n and the second information acquisition unit 152. Merge with the second information obtained by. Specifically, the merging unit 153 selects one or more records that do not correspond to (match) any of the plurality of records included in the second information among the plurality of records included in the first information. Merge into information. Whether or not there is a correspondence (match) may be determined by whether or not the e-mail address, name, telephone number, or a combination thereof, whose data is guaranteed to be unique, match each other.

Further, as is clear from FIGS. 6 and 7, the information processing device 10 and the cloud server 40 often manage the same elements with different attributes (labels). For example, in the examples shown in FIGS. 6 and 7, the cloud server 40 manages the name (kana) with the attribute (label) named nameKana, but the information processing apparatus 10 manages the name (kana) with the attribute (phoneticName). It is managed by label).

Therefore, the merging unit 153 holds the conversion information (table) as shown in FIG. 8, and uses this conversion information when merging the records included in the first information into the second information. Then, the attributes (labels) of the elements constituting the record are converted into the attributes (labels) of the elements constituting the record included in the second information and merged. The conversion information shown in FIG. 8 is information showing the correspondence relationship of what kind of name (label) each device manages the same element. The conversion information (table) shown in FIG. 8 may be stored in a storage device such as HDD 115 in advance. As a result, even if the records included in the first information are merged with the second information, the attributes (labels) of the elements that make up the records included in the first information can be changed to the records included in the second information. It can correspond to the attribute (label) of the constituent element.

In the present embodiment, the merging unit 153 uses the conversion information shown in FIG. 8 to configure the attributes (labels) of the elements that make up the record included in the first information and the record included in the second information. The case of converting to an element attribute (label) has been described as an example, but the present invention is not limited to this, and the first information acquisition unit 151-1 to 151-n may perform the conversion. In this case, when each first information acquisition unit 151 acquires the first information from the cloud server 40, the attribute (label) of the element constituting the record included in the first information is set to the second. It suffices to perform the process of converting the record included in the information into the attribute (label) of the element constituting the element.

FIG. 9 is a diagram showing an example of the merge result (merge information) of the present embodiment. In the example shown in FIG. 8, the second information described in FIG. 7 (address book managed by the information processing device 10) is combined with the first information described in FIG. 6 (managed by the cloud server 40-1). The merged result when merging the existing address book) is shown.

In the present embodiment, the merging unit 153 converts one or more records that do not correspond to any of the plurality of records included in the second information into the second information among the plurality of records included in the first information. The case of merging, that is, the case of merging by adding a new record without overwriting a plurality of records included in the second information has been described as an example, but the merging mode is not limited to this. Instead, a plurality of records included in the second information may be merged in a manner of overwriting.

Such a setting may be set, for example, on the address book synchronization setting screen as shown in FIG. The address book synchronization setting screen shown in FIG. 10 is a screen for making settings related to address book synchronization, and the timing (manual or automatic) for synchronizing the address book and the mode of merging (overwriting). (Presence / absence) etc. can be set.

In the present embodiment, the address book synchronization setting screen is provided to the user terminal 20 or the like as a Web UI, and the user operates to create workflow information on the address book synchronization setting screen displayed on the user terminal 20. It is supposed to be a form of input, but it is not limited to this. For example, the address book synchronization setting screen may be provided as a service on the cloud, or may be provided as a tool on the information processing device 10.

Subsequently, the execution control unit 150 executes the processing unit 154 based on the workflow information (registration of the address book after merging) set by the setting unit 140. As a result, the processing unit 154 performs processing based on the merge information in which the first information and the second information are merged by the merge unit 153. In the present embodiment, the merge information is information about the address book after merging, and the processing unit 154 performs a process of registering the merge information in the address book storage unit 160.

The function execution unit 170 controls to execute the function of the information processing device 10. Examples of the functions included in the information processing apparatus 10 include, but are not limited to, a print function, a scan function, a facsimile function, and a scan to Email function.

In the case of the print function, the function execution unit 170 controls the paper feed table 105 and the print engine 106 by executing the print application, and executes the print function of printing an image on the paper fed from the paper feed table 105. To do. Further, in the case of the scan function, the function execution unit 170 controls the ADF 101 and the scanner unit 102 by executing the scan application, scans the document conveyed from the ADF 101, and acquires the image data of the document. ..

Further, in the case of the facsimile function, the function execution unit 170 executes the facsimile application. As a result, the function execution unit 170 displays the information (second information, merge information) about the address book stored in the address book storage unit 160 on the display panel 104, and gives the user the telephone number of the facsimile transmission destination. To be entered. Then, the function execution unit 170 controls the ADF 101 and the scanner unit 102 to scan the document conveyed from the ADF 101, acquire the image data of the document, and send the image data to the destination input to the user. Facsimile transmission.

Further, in the case of the scan to Email function, the function execution unit 170 executes the scan to Email application. As a result, the function execution unit 170 displays the information (second information, merge information) about the address book stored in the address book storage unit 160 on the display panel 104, and gives the user the e-mail address of the facsimile transmission destination. To be entered. Then, the function execution unit 170 controls the ADF 101 and the scanner unit 102 to scan the document conveyed from the ADF 101, acquire the image data of the document, and send the image data to the destination input to the user. Send by email.

FIG. 11 is a sequence diagram showing an example of the flow of the processing procedure of the present embodiment. In the example shown in FIG. 11, the first information (information about the address book) is registered from the mobile terminal 30 to the cloud server 40, and the information processing device 10 manages the first information (information about the address book) by itself. The case of merging with the second information (information about the address book) and using the information will be described as an example, but the present invention is not limited to this.

First, the mobile terminal 30 receives input of the first information (information about the address book) for registration in the cloud server 40 from the user (step S101), and makes a registration request to the cloud server 40 (step S103).

Subsequently, the cloud server 40 registers the first information (information about the address book) for which the registration request has been made from the mobile terminal 30 in the cloud server 40 (step S105), and notifies the mobile terminal 30 of the registration result (step S105). Step S107).

The processes from steps S101 to S105 may be performed by the user manually inputting the first information using a Web browser or application on the mobile terminal 30, or the image is taken by the mobile terminal 30. This may be performed by performing OCR (Optical Character Recognition) processing on the image of the business card or the like on the cloud server 40 side to extract the first information.

Subsequently, the execution control unit 150 of the information processing apparatus 10 executes the synchronization process at the timing of synchronizing the address books (step S109). As described above, the timing for synchronizing the address book can be set on the address book synchronization setting screen shown in FIG. The details of the synchronization process will be described later.

Subsequently, the function execution unit 170 of the information processing device 10 receives a function execution request from the user (step S111). Here, since the received function execution request is a facsimile function, the function execution unit 170 describes the case of executing the facsimile application as an example, but the present invention is not limited to this.

Subsequently, the function execution unit 170 of the information processing apparatus 10 displays the merge information (information about the address book) stored in the address book storage unit 160 on the display panel 104 (step S113), and transmits the facsimile to the user. Have the user enter the telephone number of the destination (destination) (step S115). Then, when the function execution unit 170 receives the transmission execution request from the user, it controls the ADF 101 and the scanner unit 102 to scan the document conveyed from the ADF 101, acquire the image data of the document, and obtain the image data. Is facsimile-transmitted to the destination input to the user (step S117).

FIG. 12 is a sequence diagram showing an example of the flow of the procedure of the synchronous processing of the present embodiment.

First, the setting unit 140 sets the workflow information stored in the workflow storage unit 130 in the execution control unit 150 (step S201).

Subsequently, the execution control unit 150 makes an execution request to the first information acquisition unit 151-1 based on the workflow information (acquisition of the address book from the cloud A) set by the setting unit 140 (step S203). ..

As a result, the first information acquisition unit 151-1 is a cloud corresponding to the first information acquisition unit 151-1 among the plurality of cloud servers 40-1 to 40-n that manage the first information. The first information (information about the address book) is acquired from a certain cloud server 40-1 in a manner corresponding to the cloud server 40-1 (step S205), and the acquisition result is notified to the execution control unit 150 (step S207). ).

Subsequently, the execution control unit 150 makes an execution request to the second information acquisition unit 152 based on the workflow information (acquisition of the address book from the information processing device) set by the setting unit 140 (step S209).

As a result, the second information acquisition unit 152 acquires the second information (information about the address book) from the address book storage unit 160 (step S211), and notifies the execution control unit 150 of the acquisition result (step S213). ..

Subsequently, the execution control unit 150 makes an execution request to the merge unit 153 based on the workflow information (merge process of both address books) set by the setting unit 140 (step S215).

As a result, the merging unit 153 merges one or more records that do not correspond to any of the plurality of records included in the second information among the plurality of records included in the first information into the second information ( Step S217), the merge result is notified to the execution control unit 150 (step S219). The details of the merge process will be described later.

Subsequently, the execution control unit 150 makes an execution request to the processing unit 154 based on the workflow information (registration of the address book after merging) set by the setting unit 140 (step S221).

As a result, the processing unit 154 performs a process of registering the merge information (information about the address book after the merge) in which the first information and the second information are merged by the merge unit 153 in the address book storage unit 160 (the processing unit 154). Step S223), the merge result is notified to the execution control unit 150 (step S225).

FIG. 13 is a flowchart showing an example of the flow of the procedure of the merge process of the present embodiment. In the example shown in FIG. 13, a case where a plurality of records included in the second information are merged in a manner of adding a new record without overwriting is described as an example, but the present invention is not limited to this.

First, the merging unit 153 acquires an unprocessed record from the first information (information about the address book) acquired by the first information acquisition unit 151-1 (step S301).

Subsequently, the merge unit 153 determines whether or not the record corresponding to the acquired record is included in the second information acquired by the second information acquisition unit 152 (step S303). As described above, this determination may be made based on whether or not the e-mail addresses, names, telephone numbers, or combinations thereof, whose data are guaranteed to be unique, match each other.

Then, when it is included (Yes in step S303), the merging unit 153 uses the conversion information shown in FIG. 8 described above to convert the record, and uses this conversion information to form an element of the record. Convert the attribute (label) to the attribute (label) of the element that constitutes the record included in the second information, add it to the merge target (step S305), and if it is not included (No in step S303), merge. Unit 153 does not perform the process of step S305.

Subsequently, the merge unit 153 repeats the processes of steps S301 to S305 until all the records included in the first information are processed (No in step S307), and processes all the records included in the first information. (Yes in step S307), the record added to the merge target is merged (added) to the second information (step S309).

As described above, in the present embodiment, since the information acquisition component dedicated to the cloud server 40 is prepared for each cloud server 40, specifications such as a data management format and an acquisition format (protocol) are provided for each cloud server 40. Can be handled even if they are different. In particular, in the present embodiment, since the software is prepared not for each function but for each component, it is not necessary to develop the software for realizing the function of synchronizing the address book for each cloud server 40. Since it is only necessary to develop the difference part (only the acquisition part whose specifications are different for each cloud server 40), it is possible to manage information with different specifications while suppressing various costs such as human costs and monetary costs. Cooperation becomes possible.

For example, when the user changes the cloud server 40 that manages the address book used for synchronization, the user acquires the address book from the changed cloud server 40 on the workflow information creation screen shown in FIG. 5 described above. Select the component to perform and create the workflow information.

Further, according to the present embodiment, it is possible to execute a function using an address book registered from a mobile terminal 30 such as a smart device.

Further, according to the present embodiment, since the address book managed by the cloud server 40 is synchronized with the address book of the information processing device 10 to execute the function, even if the network cannot be connected, the cloud is used. It is possible to execute a function using the address book managed by the server 40.

(Modification example 1)
In the above embodiment, the merging unit 153 selects one or more records that do not correspond to any of the plurality of records included in the second information among the plurality of records included in the first information in the order of the latest update date and time. It may be merged with the information of 2.

Generally, the number of records in the address book that can be registered on the information processing apparatus 10 side is not very large. Therefore, among the address books (first information) managed by the cloud 40, all the address books not managed by the information processing device 10 side are the address books managed by the information processing device 10 (second information). When trying to merge with (information), the upper limit is often reached on the way. Therefore, by merging the records with the newest update date and time into the second information as described above, the record with high priority (recently used record) is preferentially managed by the information processing device 10 (address book). It is possible to merge into the second information).

In this case, at least the record of the first information is configured to include the lastAccessData indicating the last update date and time, as shown in FIG. The attribute of the last update date and time is used as it is if it is included in the record of the first information from the stage managed by the cloud server 40, and the attribute of the first information is used at the stage managed by the cloud server 40. If it is not included in the record, it may be added on the information processing apparatus 10 side. Further, the record of the second information may also include the attribute of the last update date and time. In this case, the last update date and time is updated when used by the function execution unit 170.

FIG. 15 is a flowchart showing an example of the flow of the procedure of the merge process of the modified example 1. First, the processes from step S401 to step S407 are the same as the processes from steps S301 to S307 in the flowchart shown in FIG.

Subsequently, when the merge unit 153 processes all the records included in the first information (Yes in step S407), the merge unit sorts the records added to the merge target in the order of the update date and time (step S409), and the update date and time. Is merged (added) with the second information in the order of newest (step S411).

(Modification 2)
In the above embodiment, the synchronization process of the address book has been described as an example, but the synchronization target is not limited to the address book, and can be applied to, for example, bibliographic information. Further, the workflow described in the above embodiment is not limited to the synchronous processing of the address book. For example, the address book managed in the cloud is backed up as CSV (Comma-Separated Values) data to a local server such as an in-house server. It can also be applied to such workflows.

(Modification example 3)
Further, in the above embodiment, the case where the merge unit 153 is realized by one type of component by using the conversion information as shown in FIG. 8 has been described as an example, but the first information and the second information are described. The merge unit 153 (component) may be prepared for each combination (type of cloud server 40). By doing so, the conversion information as shown in FIG. 8 becomes unnecessary.

(Modification example 4)
For example, the above-mentioned first information may be a shared address book that can be referred to by all users, or a personal address book that can be referred to only by a specific user. In the following description, when the first information acquisition units 151-1 to 151-n are not distinguished from each other, it may be referred to as "first information acquisition unit 151".

In this modification, the first information acquisition unit 151 periodically acquires the shared address book from the corresponding cloud server 40. Further, the first information acquisition unit 151 acquires the personal address book from the corresponding cloud server 40 by using the account information for identifying the user after the user is authenticated.

When the shared address book is acquired by the first information acquisition unit 151, the merging unit 153 uses the shared address book and the sharing managed by the information processing device 10 acquired by the second information acquisition unit 152. The second information indicating the address book is merged, and the processing unit 154 performs a process of registering the merged information indicating the merged address book.

When the personal address book is acquired by the first information acquisition unit 151, the merge unit 153 is managed by the personal address book and the information processing device 10 acquired by the second information acquisition unit 152. The second information indicating the personal address book is merged, and the processing unit 154 performs a process of registering the merged information indicating the merged address book.

Further, the first information acquisition unit 151 merges the personal address book acquired from the cloud server 40 with the personal address book that has been authenticated by the user and is managed by the information processing device 10, and provides information. The personal address book is acquired when a certain period of time has elapsed from the completion of the synchronization process for updating the personal address book managed by the processing device 10. That is, the next synchronization process of the personal address book is executed only when a certain period of time has elapsed after the completion of the synchronization process of the personal address book. Hereinafter, the specific contents of this modification will be described.

The basic configuration of each device is the same as that of the above-described embodiment, but the address book storage unit 160 in this modification has a storage area for storing the shared address book and a storage area for storing the personal address book. are doing. In addition, the cloud server 40 manages the shared address book and the personal address book. As shown in FIG. 16, the cloud server 40 has an address book (composed of name, nameKana, phoneNum, faxNum, and email in this example) and a shared address for each id that is an identifier of the record (address book). The type for identifying the book or the personal address book and the account information for identifying the user who has the authority to access the personal address book are managed (stored) in association with each other.

In FIG. 17, a shared address book is registered in the cloud server 40 from the mobile terminal 30, the information processing device 10 acquires the shared address book from the cloud server 40, and the acquired shared address book is managed by itself. It is a sequence diagram which shows an example of the operation procedure of the information processing system 1 in the case of merging and using it with the 2nd information which shows a shared address book.

First, the mobile terminal 30 receives input from the user in the shared address book for registration in the cloud server 40 (step S501), and makes a registration request to the cloud server 40 (step S503).

Subsequently, the cloud server 40 registers the shared address book for which the registration request has been made from the mobile terminal 30 in the cloud server 40 (step S505), and notifies the mobile terminal 30 of the registration result (step S507).

The processes in steps S501 to S505 may be performed by the user manually inputting the shared address book using a Web browser or application on the mobile terminal 30, or may be photographed by the mobile terminal 30. This may be performed by performing OCR (Optical Character Recognition) processing on the image such as a business card on the cloud server 40 side to extract a shared address book.

Subsequently, the execution control unit 150 of the information processing apparatus 10 executes the synchronization processing of the shared address book at the timing of performing the synchronization processing of the shared address book (step S509). As described above, the timing for synchronizing the address book can be set on the address book synchronization setting screen shown in FIG. Details of the shared address book synchronization process will be described later.

Subsequently, the function execution unit 170 of the information processing device 10 receives a function execution request from the user (step S511). Here, since the received function execution request is a facsimile function, the function execution unit 170 describes the case of executing the facsimile application as an example, but the present invention is not limited to this.

Subsequently, the function execution unit 170 of the information processing apparatus 10 displays the merge information (information about the address book) stored in the address book storage unit 160 on the display panel 104 (step S513), and transmits the facsimile to the user. Have the user enter the telephone number of the destination (destination) (step S515). Then, when the function execution unit 170 receives the transmission execution request from the user, it controls the ADF 101 and the scanner unit 102 to scan the document conveyed from the ADF 101, acquire the image data of the document, and obtain the image data. Is facsimile-transmitted to the destination input by the user (step S517).

FIG. 18 is a sequence diagram showing an example of the flow of the procedure of the synchronous processing of the shared address book of this modification (step S509 of FIG. 17).

First, the setting unit 140 sets the workflow information of the synchronous processing of the shared address book stored in the workflow storage unit 130 in the execution control unit 150 (step S601). FIG. 19 is a diagram showing an example of the workflow shown by the workflow information in this case.

Subsequently, the execution control unit 150 makes an execution request to the first information acquisition unit 151 based on the workflow information (see FIG. 19) set by the setting unit 140 (step S603).

As a result, the first information acquisition unit 151 acquires the shared address book from the corresponding cloud server 40 (step S605) and notifies the execution control unit 150 of the acquisition result (step S607).

Subsequently, the execution control unit 150 makes an execution request to the second information acquisition unit 152 based on the workflow information (see FIG. 19) set by the setting unit 140 (step S609).

As a result, the second information acquisition unit 152 acquires the second information (shared address book managed by the information processing device 10) from the address book storage unit 160 (step S611), and executes the acquisition result in the execution control unit. Notify 150 (step S613).

Subsequently, the execution control unit 150 makes an execution request to the merge unit 153 based on the workflow information (see FIG. 19) set by the setting unit 140 (step S615).

When the shared address book acquired from the cloud server 40 does not exist in the shared address book managed by the information processing device 10, the merging unit 153 uses the shared address book acquired from the cloud server 40 and the information processing device 10 The managed shared address book is merged (step S617), and the merged result is notified to the execution control unit 150 (step S619).

Subsequently, the execution control unit 150 makes an execution request to the processing unit 154 based on the workflow information (see FIG. 19) set by the setting unit 140 (step S621).

As a result, the processing unit 154 performs a process of registering the merge information merged by the merge unit 153 in the address book storage unit 160 (step S623), and notifies the execution control unit 150 of the merge result (step S625).

In FIG. 20, a personal address book is registered in the cloud server 40 from the mobile terminal 30, the information processing device 10 acquires the personal address book from the cloud server 40, and the acquired personal address book is managed by itself. It is a sequence diagram which shows an example of the operation procedure of the information processing system 1 in the case of merging and using it with the 2nd information which shows a personal address book.

First, the mobile terminal 30 receives input from the user in the personal address book for registration in the cloud server 40 (step S701), and makes a registration request to the cloud server 40 (step S703). For example, when "public / not public" can be selected when registering in the address book, "not public" can be selected and registered.

Subsequently, the cloud server 40 registers the personal address book for which the registration request has been made from the mobile terminal 30 in the cloud server 40 (step S705), and notifies the mobile terminal 30 of the registration result (step S707). Here, when registering the personal address book, the cloud server 40 registers the personal address book in association with the account used when accessing from the mobile terminal 30.

The processes in steps S701 to S705 may be performed by the user manually inputting the personal address book using the Web browser or application on the mobile terminal 30, or may be photographed by the mobile terminal 30. This may be performed by performing OCR (Optical Character Recognition) processing on the image such as a business card on the cloud server 40 side to extract a personal address book.

Subsequently, the information processing device 10 performs a user authentication process (step S709). The authentication process is a process for determining whether or not the user has the authority to use the information processing device 10. For example, the information processing device 10 registers in advance account information for identifying the user for each user who has the usage authority (in this example, only the account is used, but for example, a combination of an account and a password may be used). It is possible to recognize that the user has the authority to use the information processing device 10 (authenticate the user) only when the account information input by the user matches the account information registered in advance. it can.

After the user is authenticated, the execution control unit 150 of the information processing device 10 executes the synchronization process of the personal address book (step S711). The details of the personal address book synchronization process will be described later. The account information for acquiring the personal address book from the cloud server 40 at the time of synchronization processing (account information associated with the address book managed by the cloud server 40 in the cloud server 40) is the information processing device 10. Use the account information of the user logged in to. When the account information for the information processing device and the account information for the cloud server are the same, the account information for the information processing device used in the above-mentioned authentication process can be used as it is. If they are different, for example, as shown in FIG. 21, the information processing device 10 has account information for the cloud server (account and password in this example) as opposed to account information for the information processing device (account only in this example). (Combination) can be linked and managed, and the account information for the cloud server linked to the account information (account information at the time of login) of the authenticated user can also be used.

The processing contents of steps S713 to S719 are the same as the processing contents of steps S511 to S517 of FIG.

FIG. 22 is a sequence diagram showing an example of the procedure flow of the personal address book synchronization process (step S711 in FIG. 20) of this modification.

First, the setting unit 140 sets the workflow information of the synchronization processing of the personal address book stored in the workflow storage unit 130 in the execution control unit 150 (step S801). FIG. 23 is a diagram showing an example of the workflow shown by the workflow information in this case.

Subsequently, the execution control unit 150 makes an execution request to the first information acquisition unit 151 based on the workflow information (see FIG. 23) set by the setting unit 140 (step S803).

As a result, the first information acquisition unit 151 acquires the personal address book associated with the account information for identifying the logged-in user from the corresponding cloud server 40 (step S805), and executes the acquisition result as the execution control unit. Notify 150 (step S807).

Subsequently, the execution control unit 150 makes an execution request to the second information acquisition unit 152 based on the workflow information (see FIG. 23) set by the setting unit 140 (step S809).

As a result, the second information acquisition unit 152 acquires the second information (personal address book managed by the information processing device 10) from the address book storage unit 160 (step S811), and executes the acquisition result in the execution control unit. Notify 150 (step S813).

Subsequently, the execution control unit 150 makes an execution request to the merge unit 153 based on the workflow information (see FIG. 23) set by the setting unit 140 (step S815).

When the personal address book acquired from the cloud server 40 does not exist in the personal address book managed by the information processing device 10, the merging unit 153 uses the personal address book acquired from the cloud server 40 and the information processing device 10 The managed personal address book is merged (step S817), and the merged result is notified to the execution control unit 150 (step S819).

Subsequently, the execution control unit 150 makes an execution request to the processing unit 154 based on the workflow information (see FIG. 23) set by the setting unit 140 (step S821).

As a result, the processing unit 154 performs a process of registering the merge information merged by the merge unit 153 in the address book storage unit 160 (step S823), and notifies the execution control unit 150 of the merge result (step S825).

Further, in this modification, when the synchronization process of the personal address book is performed when the application is used after the user logs in, it is conceivable that the synchronization process is performed even if the personal address book has just been acquired last time. In this case, a heavy process is executed even though there is almost no change in the personal address book after the synchronization process is completed, which causes a problem that the load on the system increases. In order to solve this problem, in this modification, when the synchronization processing of the personal address book is completed, the completion date and time is held in a storage device such as HDD 115, and the synchronization processing is performed only when a certain period of time has elapsed. FIG. 24 is a diagram showing a processing flow in this case.

As shown in FIG. 24, after the user logs in, the execution control unit 150 acquires the completion date and time of the personal address book synchronization process from the storage device (step S901). Next, the execution control unit 150 confirms whether or not a certain time has elapsed (step S902). If the result of step S902 is affirmative (step S902: Yes), the execution control unit 150 executes the synchronization process (step S903). The contents of this processing are as described above. When the synchronization process is completed (step S904: Yes), the execution control unit 150 controls to save the completion date and time in the storage device (step S905).

In the above modified example, after the user is authenticated by the information processing device 10, the personal address book is synchronized by using the account information of the authenticated user. That is, according to this modification, the information processing device 10 that can synchronize not only the shared address book that can be accessed by all users but also the personal address book that can be accessed only when the account information of a specific user is used. Can be provided.

(program)
The program executed by the information processing apparatus 10 of the above embodiment and the modified example is a file in an installable format or an executable format, and is a CD-ROM, a CD-R, a memory card, a DVD (Digital Versatile Disk), or a flexible disk. It is stored and provided in a computer-readable storage medium such as (FD).

Further, the program executed by the information processing apparatus 10 of the above-described embodiment and the modified example may be provided by storing it on a computer connected to a network such as the Internet and downloading it via the network. Further, the program executed by the information processing apparatus 10 of the above-described embodiment and the modified example may be provided or distributed via a network such as the Internet. Further, the program executed by the information processing apparatus 10 of the above-described embodiment and the modified example may be provided by incorporating it in a ROM or the like in advance.

The program executed by the information processing apparatus 10 of the above-described embodiment and the modified example has a modular configuration for realizing each of the above-described parts on a computer. As actual hardware, for example, the CPU reads a program from the ROM onto the RAM and executes the program, so that each of the above functional units is realized on the computer.

The above embodiments and modifications are presented as examples, and are not intended to limit the scope of the invention. The new embodiment can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments are included in the scope and gist of the invention, and are included in the scope of the invention described in the claims and the equivalent scope thereof.

1 Information processing system 2 Intranet 3 Firewall 4 Internet 10 Information processing device 20 User terminal 30 Mobile terminal 40-1 to 40-n (40) Cloud server 120 Creation unit 130 Workflow storage unit 140 Setting unit 150 Execution control unit 151-1 to 151-n 1st information acquisition unit 152 2nd information acquisition unit 153 Merge unit 154 Processing unit 160 Address book storage unit 170 Function execution unit

Japanese Unexamined Patent Publication No. 2014-149781

Claims (10)

A plurality of first information capable of acquiring the first information from a corresponding cloud among a plurality of clouds that manage the first information composed of a plurality of records in a manner corresponding to the cloud. Acquisition department and
A second information acquisition unit that acquires a second information composed of a plurality of records,
Among the plurality of records included in the first information acquired by any one of the plurality of first information acquisition units, the second information acquired by the second information acquisition unit is included. A merge section that merges one or more records that do not correspond to any of the plurality of records into the second information.
A processing unit that performs processing based on merged information in which the first information and the second information are merged is provided .
The merging unit determines whether or not there is a correspondence depending on whether or not the records included in the first information and the second information and whose data is guaranteed to be unique match. Information processing device. The information processing device according to claim 1, wherein the merging unit determines whether or not there is a correspondence based on whether or not the unique combinations of data match. The merge unit selects one or more records that do not correspond to any of the plurality of records included in the second information among the plurality of records included in the first information, in the order of newest update date and time. The information processing apparatus according to claim 1 or 2 , which is merged with information. The first information and the second information are information related to an address book.
The merge information is information about the address book after merging, and is
The information processing device according to any one of claims 1 to 3, wherein the processing unit performs a process of registering the merge information. The first information is a shared address book that can be referred to by all users, or a personal address book that can be referred to only by a specific user.
The first information acquisition unit is
Obtain the shared address book on a regular basis
After authenticating the user, the personal address book is acquired by using the account information for identifying the user.
The information processing device according to claim 4. When the shared address book is acquired by the first information acquisition unit,
The second information acquisition unit acquires the second information indicating the shared address book managed by the information processing apparatus, and the merge unit acquires the information acquired by the first information acquisition unit. The shared address book and the second information acquired by the second information acquisition unit are merged, and the processing unit performs a process of registering the merged information indicating the merged address book.
When the personal address book is acquired by the first information acquisition unit,
The second information acquisition unit acquires the second information indicating the personal address book managed by the information processing apparatus, and the merge unit acquires the information acquired by the first information acquisition unit. The personal address book and the second information acquired by the second information acquisition unit are merged, and the processing unit performs a process of registering the merged information indicating the merged address book.
The information processing device according to claim 5. The first information acquisition unit is
The individual managed by the information processing device by merging the personal address book acquired from the cloud with the personal address book that has been authenticated by the user and is managed by the information processing device. When a certain period of time has passed since the synchronization process for updating the address book is completed, the personal address book is acquired.
The information processing device according to claim 5 or 6. The plurality of first information acquisition units, the second information acquisition unit, the merge unit, and the processing unit are components, respectively.
A setting unit that sets workflow information that defines one or more components to be executed and the execution order,
An execution control unit that executes one or more components to be executed in the execution order based on the workflow information is provided.
In the workflow information, at least one of the plurality of first information acquisition units, the second information acquisition unit, the merge unit, and the processing unit are defined as one or more components to be executed. Any one of claims 1 to 7, wherein the execution order is at least one of the plurality of first information acquisition units, the second information acquisition unit, the merge unit, and the processing unit. The information processing device described in. From the corresponding cloud among the plurality of clouds that manage the first information composed of a plurality of records , at least one of the plurality of first information acquisition units is the first in a manner corresponding to the cloud. The first acquisition step to acquire information and
A second acquisition step in which the second information acquisition unit composed of a plurality of records acquires the second information, and
The second of the plurality of records included in the first information acquired by any one of the plurality of first information acquisition units, the merge unit is acquired by the second information acquisition unit. A merge step of merging one or more records that do not correspond to any of the plurality of records included in the information into the second information.
A processing step in which the processing unit performs processing based on the merge information in which the first information and the second information are merged.
A merge methods, including,
The merge step determines the presence or absence of the correspondence based on whether or not the records included in the first information and the second information and whose data is guaranteed to be unique match. , How to merge. A plurality of first information capable of acquiring the first information from a corresponding cloud among a plurality of clouds that manage the first information composed of a plurality of records in a manner corresponding to the cloud. Acquisition department and
A second information acquisition unit that acquires a second information composed of a plurality of records,
Among the plurality of records included in the first information acquired by any one of the plurality of first information acquisition units, the second information acquired by the second information acquisition unit is included. A merge section that merges one or more records that do not correspond to any of the plurality of records into the second information.
A program for operating a computer as a processing unit that performs processing based on merged information in which the first information and the second information are merged .
The merging unit determines whether or not there is a correspondence depending on whether or not the records included in the first information and the second information and whose data is guaranteed to be unique match. ,program.

Images