Setting distribution system, method and information processing device
The setting distribution system addresses the inflexibility in existing systems by delivering setting data with specified function data to automatically switch methods for reflecting setting values across multiple cloud services, enhancing efficiency and flexibility.
Patent Information
- Application Number
- JP2023172943
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-10-04
- Publication Date
- 2025-04-16
AI Technical Summary
Existing systems lack the flexibility to automatically switch between different methods for reflecting setting values across multiple cloud services, which have varying protocols and requirements, leading to inefficiencies and potential service disruptions.
A setting distribution system that includes an information processing device and a source device, where the source device delivers setting data along with function data specifying the necessary functions to reflect the setting values, allowing the information processing device to call only the specified functions to update the settings.
Enables automatic switching of setting value reflection methods based on the protocol used by each cloud service, improving efficiency and flexibility, and ensuring that setting values are accurately and efficiently updated in real-time.
Smart Images

Figure 2025063595000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a setting distribution system, a method, and an information processing device. [Background technology]
[0002] There is known a technology for connecting an information processing device such as an image forming device to a cloud service to improve ease of management, maintainability, etc. Examples of cloud services include a service that receives notifications of various events that occur in an operating information processing device and monitors errors, and a service that periodically collects the status of counters and consumables to perform billing and maintenance. By using these services, the management of information processing devices is made more efficient.
[0003] Conventionally, in order to appropriately improve the efficiency of management of information processing devices, when changing the status of counters, consumables, etc., or device settings, a serviceman had to go to the site to give instructions to change the data to be sent to the cloud. However, Patent Document 1 discloses a technology for remotely issuing instructions to change the data to be sent to the cloud. This eliminates the need for a serviceman to go to the site and give such instructions in front of the information processing device, thereby reducing the labor required for going to the site. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2018-136876 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, there are multiple cloud services that assume that the setting values are rewritten remotely to reduce the labor required for dispatch, and the means for reflecting the setting values in these cloud services are common. Therefore, for example, it is not appropriate to realize a backup service and a remote repair service with the same mechanism. The backup service is executed by default at night when the user is absent, and data volume and data integrity are more important than processing speed. The remote repair service applies a two-way communication protocol to the device during the day when it is in operation, and the procedure is executed in real time with a small amount of data. In general, data volume and processing speed are in a trade-off relationship, so in consideration of the coexistence of multiple services, a mechanism is required that allows flexible switching of the means for reflecting the setting values for each cloud service.
[0006] Therefore, the present invention aims to provide a setting distribution system, method, and information processing device that enables automatic switching of the means for reflecting setting values depending on the protocol used in a system where multiple cloud services coexist, each with functionality that is in a trade-off relationship. [Means for solving the problem]
[0007] In order to solve the above-mentioned problems, the setting distribution system of the present invention is a setting distribution system including an information processing device to which setting data related to settings is distributed, and a distribution source device to which the setting data is distributed, wherein the distribution source device distributes to the information processing device via a network a set of the setting data including a plurality of setting values and function data specifying only at least one function that needs to be called in order to reflect at least one setting value in the information processing device in the information processing device, and the information processing device reflects the setting values included in the setting data in the information processing device by calling only the functions specified by the function data. Effect of the Invention
[0008] According to the present invention, in a system in which multiple cloud services coexist, each with functionality that is in a trade-off relationship, it is possible to automatically switch the means for reflecting setting values depending on the protocol being used. [Brief description of the drawings]
[0009] [Figure 1] 1 is a diagram showing the configuration of a system including an image forming apparatus according to a first embodiment of the present invention. [Diagram 2] 1 is a block diagram showing a configuration of an image forming apparatus according to a first embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram showing relevant software modules according to the first embodiment of the present invention. [Figure 4] 11 is a data flow diagram at the time of import in the configuration according to the first embodiment of the present invention. [Diagram 5] 11 is a data flow diagram at the time of export in the configuration according to the first embodiment of the present invention. [Figure 6] FIG. 2 is a diagram showing a sample of a DB schema according to the first embodiment of the present invention. [Figure 7] FIG. 2 is a diagram showing a sample of an XML schema according to the first embodiment of the present invention. [Figure 8] 3A and 3B are diagrams illustrating an import module management table and an execution management bitmap function according to the first embodiment of the present invention. [Figure 9] 3A to 3C are diagrams showing a high-speed mode designation csv file, an execution management bitmap, and an import data file according to the first embodiment of the present invention. [Figure 10] 1 is a diagram illustrating a hardware configuration of each server constituting a network device management system according to a first embodiment of the present invention. [Figure 11] 1 is a block diagram showing a module configuration of a network device management system and a module configuration of a remote repair service according to the present invention; [Figure 12] FIG. 4 is a basic import sequence diagram according to the first embodiment of the present invention. [Figure 13] FIG. 4 is a basic import sequence diagram according to the first embodiment of the present invention. [Figure 14] FIG. 4 is a basic import sequence diagram according to the first embodiment of the present invention. [Figure 15] FIG. 4 is a basic import sequence diagram according to the first embodiment of the present invention. [Figure 16] 4 is a flowchart of a remote repair service in the first embodiment of the present invention. [Figure 17] 5 is a flowchart showing a process executed by the image forming apparatus according to the first embodiment of the present invention. [Figure 18] 10 is a flowchart showing a process according to a second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] A setting distribution system according to an embodiment includes an information processing device to which setting data relating to settings is distributed, and a distribution source device that distributes the setting data. The distribution source device distributes, via a network, to the information processing device a set of setting data including a plurality of setting values and function data that specifies only at least one function that needs to be called to reflect at least one setting value in the information processing device in the information processing device. The information processing device reflects the setting values included in the setting data in the information processing device by calling only the function specified by the function data.
[0011] When the information processing device receives the setting data, the information processing device may call the function without using the function data, and cause the setting value included in the setting data to be reflected in the information processing device.
[0012] The source device may switch between distributing the setting data in a normal mode in which the setting data is distributed and distributing the setting data in a high-speed mode in which the setting data is distributed faster than in the normal mode, depending on the type of service related to the request for distributing the setting data.
[0013] When the source device distributes the configuration data using the MQTT protocol, the source device may distribute the configuration data in high-speed mode.
[0014] The source device may further execute at least one of a process for specifying the name of the corresponding callback destination, a process for enabling exclusive processing to be executed, and a process for defining the order in which at least one setting value in the information processing device is reflected in the information processing device.
[0015] The method according to the embodiment is a method executed in a setting distribution system including an information processing device to which setting data related to settings is distributed, and a distribution source device to which the setting data is distributed. The distribution source device distributes, via a network, to the information processing device a set of setting data including a plurality of setting values and function data specifying only at least one function that needs to be called to reflect at least one setting value in the information processing device in the information processing device. The information processing device reflects the setting values included in the setting data in the information processing device by calling only the function specified by the function data.
[0016] The information processing device according to the embodiment includes a receiving means and a reflecting means. The receiving means receives a set of setting data including a plurality of setting values and function data specifying only at least one function that needs to be called to reflect at least one of the setting values from a distribution source device via a network. The reflecting means reflects the setting values included in the setting data by calling only the function specified by the function data.
[0017] The method according to the embodiment includes a receiving step and a reflecting step. In the receiving step, a set of setting data including a plurality of setting values and function data specifying only at least one function that needs to be called to reflect at least one setting value is received from a distribution source device via a network. In the reflecting step, the setting value included in the setting data is reflected by calling only the function specified by the function data.
[0018] Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.
[0019] (Overall system configuration for setting value management) FIG. 1 is a system configuration diagram including an image forming apparatus according to a first embodiment of the present invention. Specifically, FIG. 1 shows a general system configuration used for managing settings of the image forming apparatus according to the embodiment of the present invention. The image forming apparatus 001 and the image forming apparatus 002 are copying machines that read an original, process the image, and output the result. In addition, the page description language (PDL) data is image data generated by reading the original by an image forming apparatus other than the image forming apparatus 001 and the image forming apparatus 002, or image data generated by a client computer, and is output via a network 003. Conversely, the image data generated by reading the original by the image forming apparatus 001 or the image forming apparatus 002 is output via the network 003, and is transmitted to, for example, a file server or a mail server.
[0020] The management server 004 is connected to a group of devices 005 to be managed, including the image forming apparatus 001 and the image forming apparatus 002, via a network 003, and performs communication for exporting and importing setting values. For this communication, protocols such as HTTPS (Hyper Text Transfer Protocol Secure), SOAP (Simple Object Access Protocol), FTP (File Transfer Protocol), and MQTT (Message Queuing Telemetry Transport) are used.
[0021] The managed device group 005 illustrates an example in which image forming apparatuses with different configurations are included in the group, meaning that the device configuration is different between the image forming apparatus 001 and the image forming apparatus 002. The managed device group 005 is also connected to a cloud environment 008 via the Internet 006.
[0022] On the cloud environment 007, there are a number of services, such as a network device management system 008, a software distribution cloud service 009, a backup service 010, and a remote repair service 011.
[0023] The remote repair service 011 transmits instructions to each of the management target device group 005 from an instruction operation UI (User Interface) of the remote repair service 011 through the network device management system 008, and controls the configuration of the management target device group 005. Setting values can be exported to the remote repair service 011 and stored therein, and furthermore the stored setting values can be imported into the remote repair service 011. Furthermore, the image forming apparatus 001 can export setting values to a USB (Universal Serial Bus) storage device 012 and import setting values stored in the USB storage device 012, without going through the management server 004, by performing a predetermined operation on the operation panel.
[0024] (Explanation of hard block configuration) 2 is a block diagram showing the configuration of an image forming apparatus according to a first embodiment of the present invention. A controller main unit 100 is a main controller that controls an information processing unit of the image forming apparatus. A controller subunit 101 is a subcontroller that controls an image processing unit of the image forming apparatus. The controller main unit 100 and the controller subunit 101 are connected by a bus via a bus bridge 116.
[0025] The CPU 108 executes software stored in the FLASH ROM 110 or the HDD 111. The CPU 108 also performs overall control of each device connected to a system bus 115. The FLASH ROM 110 and the HDD 111 are used as storage areas not only for programs but also for image data and user settings.
[0026] The RAM 109 functions as a main memory, a work area, etc. of the CPU 108. The operation unit I / F 112 draws on an LCD panel 104 provided in the image forming apparatus. In addition, at least one of the operation buttons 103 and the touch panel 103 may be connected to the operation unit I / F 112.
[0027] The network I / F 113 is integrated with an LCD (Liquid Crystal Display) panel and controls the input of instructions by an operator. The network I / F 113 is also a network interface card (NIC) and exchanges data bidirectionally with other network devices or file servers via the LAN 102. The external serial I / F is an external storage interface (USB) that connects an external device such as a memory media reader or an IC (Integrated Circuit) card reader and exchanges data bidirectionally.
[0028] Next, the components of the sub-controller 101 will be described. The printer 106 is realized by, for example, an electrophotographic method or an inkjet method, and prints on paper. The scanner 105 reads images printed on paper. In many cases, the scanner 105 is equipped with an automatic document feeder (not shown) as an option, and can automatically read multiple pages of documents. The printer 106 and the scanner 105 exchange control signals with the CPU 117 through a device interface 120. The CPU 117 comprehensively controls each device connected to a system bus 127. An image input from the scanner 105 is input as a read image to the RAM 118 through a scanner image processing unit 121.
[0029] The memory image processing unit 123 processes the image on the RAM 118 of the image forming apparatus and outputs it to the RAM 118. Image processing includes processes such as rotation, magnification, color space conversion, grayscale conversion, synthesis, encoding, and decoding. After the image on the RAM 118 is processed by the memory image processing unit 123, the CPU 117 stores the image in the RAM 118 in the FLASH ROM 110 and HDD 111 on the main controller via the bus bridge 116.
[0030] Furthermore, the CPU 2117 reads out images stored 106 in the FLASH ROM 110 and HDD 111 on the main controller to the RAM 118 via the bus bridge 116, and outputs the images to the printer 106 via the printer image processing unit 122. The scanner image processing unit 121 and the printer image processing unit 122 execute processes including color space conversion, movement, color adjustment, density control, delay amount control, and the like.
[0031] A raster image processor (RIP) 119 develops the PDL code on the RAM 2118 into a bitmap image and outputs it to the RAM 2118. An SRAM 124 inputs and outputs non-volatile data at high speed to and from the CPU 2117. A modem 125 is connected to the public line 107 and performs modulation and demodulation associated with fax image input and output.
[0032] (Explanation of the import service operation overview) Fig. 3 is a diagram showing related software modules according to the first embodiment of the present invention. Specifically, Fig. 3 shows a system configuration of an import service according to this embodiment. This system is implemented in a managed device 005 including an image forming apparatus 001 and an image forming apparatus 002.
[0033] First, a network import service is requested, and processing related to the network import unit will be described. Here, it is assumed that the import data to be processed is setting data including address book data, department management data, and device setting data.
[0034] The import service requester 301 is a side that transmits device settings. The import service provider 300 is a side that receives device settings. The import service requester 301 and the import service provider 300 communicate with a network device management system 008 in a cloud environment 007 via the Internet 006 or an intranet 302. In this communication, a protocol such as HTTPS (Hyper Text Transfer Protocol Secure), SOAP (Simple Object Access Protocol), FTP (File Transfer Protocol), or MQTT (Message Queuing Telemetry Transport) is used. Here, a diagram is used to explain communication using SOAP messages via the intranet 302, but communication is not limited to the intranet and may be on the Internet 006.
[0035] After the HTTP server 303 and SOAP server 304 interpret the request message, CGI 306 for the process corresponding to that message is started. Network import module 307 receives and processes the request. SOAP server 304 starts device setting import CGI 306 in accordance with the service request. The started CGI causes network import module 307 to store the received device setting file in temporary area 320, and then waits for a response that secondary storage is complete. This device setting file is in a compressed format that combines multiple XML files.
[0036] After the primary storage is completed, a secondary storage process is requested to the device setting management unit 308. The device setting management module 309 reads the compressed data from the temporary area 320 and performs a decompression process. If the decompression process is successful, the import file policy database 310 is initialized. If the initialization is successful, a process is started in which the obtained XML (Extensible Markup Language) is parsed and the items of the obtained setting item names are registered in the corresponding import file policy database 310. Then, the machine identification information included in the XML is obtained. If the machine identification information is successfully obtained, the machine identification information of the executing machine is obtained and the range of reflection (reflection level) is determined.
[0037] After the range of reflection is determined, the device setting management module 309 registers all remaining setting items contained in the XML in the import file policy database 310. Items that could not be reflected in the policy database are registered in a setting reflection history (not shown). After this item is registered in the setting reflection history, the device setting management module 309 notifies the previously registered import processing unit 313 of the range of reflection (reflection level) together with the item.
[0038] The device setting management module 309 returns a response of completion of secondary storage to the source of the import request. Upon receiving the notification, the import module group 321 of the group of the control import processing unit 313 performs tertiary storage to utilize the input device settings for control. Upon receiving the notification, the import module group 321 obtains the setting value and reflection policy that match the setting item name to be processed from the secondarily stored setting reflection policy database 310. Then, if the reflection policy is greater than the notified reflection level, the import module group 321 registers it in the high-speed setting management DB (Database) 322 for control.
[0039] The following shows examples of import modules constituting the import module group 321. The device setting import module 314 reads only the device setting data group one by one and registers it in the control device setting DB 315. The department management setting import module 316 reads only the department management setting data group and registers it in the control department management setting DB 317. The address book import module 318 reads only the address book setting data group and registers it in the control address book DB 319.
[0040] In this embodiment, an import module that issues a notification is identified from among the import module group 321 of the import processing unit 313 by referring to an import module management table 701 described later. After the import module is identified, the execution of the import process is controlled by an execution management bitmap function 702. Note that, although this embodiment describes the identification of an import module, the present invention is not limited to this and may be applied to the identification of an export module.
[0041] Fig. 4 is a data flow diagram at the time of import in the configuration according to the first embodiment of the present invention. Specifically, Fig. 4 shows a data flow diagram that typifies the flow of data after the primary store at the time of import in the configuration of Fig. 3. First, the policy DB is initialized when the import process starts. An import XML file 401 acquired by the network import unit 307 or the USB import module 312 at the time of import is stored in the policy DB 301 by the device setting management module 309. At this time, a key with a name not described in the policy DB 301 is not written even if it is described in the XML 401. Also, even if there is a difference between the size and type information described in the XML and the size and information in the policy DB 301, it is not written.
[0042] When storing of data in the policy DB 301 is completed, the device setting management module 309 notifies each application 402 in the device of an import command. For example, when storing of data in the policy DB 301 is completed, the device setting management module 309 notifies an import command to the device setting import module 314, the department management setting import module 316, and the address book import module 318. At this time, an import level calculated based on the information written in the XML is notified. The calculation of this import level will be described in detail later.
[0043] Each application retrieves its own data from the policy DB 301 and compares the notified level with the level information in the meta-information described for each key inside the policy DB 301. As a result, only those determined to be writable are written to the original storage 403, etc., more specifically, the device setting DB 315, department management setting DB 317, address book DB 319, etc. shown in FIG.
[0044] Fig. 5 is a data flow diagram at the time of export in the configuration according to the first embodiment of the present invention. Specifically, Fig. 5 shows a schematic diagram at the time of export. First, the policy DB is initialized when the export process starts. Each application 402 etc. that receives an export instruction from the device setting management module 309 reads its own management data from its own storage 403 etc. and writes it to the policy DB 310. At this time, all items that can be exported are written to the DB without any particular consideration of policies etc.
[0045] After all applications have written data to the policy DB 301, the device setting management module 309 converts this data into XML. Furthermore, at this time, the device identification information is obtained from the device and written as additional information to the XML file 401. This becomes the basis for the level information at the time of import. The XML file 401 with all the information written in it is taken out of the device and exported, and becomes the input XML file for the flow explained in FIG. 4.
[0046] 6 and 7 are diagrams showing a sample of a DB schema according to the first embodiment of the present invention. A conceptual structure 606 of setting value data is composed of keys having a hierarchical structure, and each leaf has a structure having data.
[0047] A DB table schema 601 has a relational DB structure with KeyID as the relation key. A key list table 602 shows the key structure and meta information, and describes the key name definition and meta information. The key list table 602 has a tree-like hierarchical structure. This hierarchical structure is expressed by a parent ID indicating the parent hierarchy. In this example, the meta information is expressed as a 32-bit bit string, and in this embodiment, level information and the like are specified in the form of bit assignment.
[0048] The value list table 603 shows the contents of the data, and holds information showing the actual data value, data size, and data type. In this embodiment, no value is entered in the value in the initial state. The value range table 604 holds information on the range of data that can be set to the value as supplementary information.
[0049] 7A, tags and elements are created in the XML file 605. This is an example, and the information in the DB can be expressed almost as it is in XML.
[0050] Fig. 8 is a diagram showing an import module management table and an execution management bitmap function according to the first embodiment of the present invention. Fig. 9 is a diagram showing a high-speed mode designation csv file, an execution management bitmap, and an import data file according to the first embodiment of the present invention.
[0051] The import module management table 701 manages all the import module group 321 of the import processing unit 313. The import module name is the function name of the import module constituting the import module group. For example, the import module management table 701 indicates a registered state for the device setting import module 314 when the function name of the device setting import module 314 is "Application A". Alternatively, the import module management table 701 indicates a registered state for the department management setting import module 316 when the function name of the department management setting import module 316 is "Application B". Alternatively, the import module management table 701 indicates a registered state for the address book import module 318 when the function name of the address book import module 318 is "Application C".
[0052] The handle ID is a unique ID issued in the order of registration in the import module management table, and makes it possible to identify the import module. The execution mode indicates the import / export execution mode, and is defined as "normal" if import and export control is supported, and is defined as "importOnly" if the import module supports only import control. The conceptual structure 606 of the setting value data is a key list that is a list of setting items handled by the import module, and is composed of keys having a hierarchical structure.
[0053] The addresses of the callback functions are addresses in the memory spaces of the device setting import module 314, department management setting import module 316, and address book import module 318, and are managed, for example, in hexadecimal numbers. In the column with high-speed mode specified, if the CSV file with high-speed mode specified contains the function name of the device setting import module 314, it will be marked with "O". CSV file 703 with high-speed mode specified shows an example in which the function name of the device setting import module 314 is written, and is made into a zip file together with the XML file 401 as import data file 705.
[0054] The execution management bitmap function 702 is in a state in which all handle IDs and addresses of callback functions of the import module group 321 of the import processing unit 313 are registered when the image forming apparatus 001 is started up. The execution of the import process is controlled by referring to the execution management bitmap function 702 and sequentially calling the addresses of the callback functions of the import module group 321 that are registered.
[0055] In this embodiment, if a CSV file 703 with high-speed mode specified is detected in a zip file during import execution, the CSV file is parsed and the contents of the import module management table 701 and the execution management bitmap function 702 are rewritten. After the contents of the execution management bitmap function 702 are rewritten, they become the contents of the execution management bitmap function 704, and only the address of the callback function of the device setting import module 314 of the import module group 321 is called.
[0056] Fig. 10 is a diagram showing the hardware configuration of each server constituting the network device management system according to the first embodiment of the present invention. Specifically, Fig. 10 shows the module configuration of the network device management system 008 and the remote repair service 011. The network device management system 008 is positioned as one of the import service requesters 301 that transmits device settings.
[0057] The remote repair service 011 is configured by connecting a storage means 805 , an input means 807 , an output means 808 , a communication control means 809 , a storage medium driving means 810 , etc. to a control means 801 via a bus line 711 .
[0058] The control means 801 is composed of a CPU 802, a ROM 804, a RAM 803, etc. The CPU 802 performs various calculations, information processing, and overall control of the bundle pool server according to a predetermined program. The ROM 804 is a read-only storage device, and stores basic programs, data, parameters, etc. for operating the remote repair service 011. The RAM 803 is a randomly accessible storage device, and provides, for example, a working area when the CPU 802 manages bundles.
[0059] The storage means 805 is a readable / writable storage medium, for example, a large-capacity hard disk, and is provided with a program storage unit 806. The program storage unit 806 stores an OS (Operating System) and other programs. The input means 807 is composed of input devices such as a keyboard and a mouse. The output means 808 is composed of output devices such as a display device and a printer. The storage medium driving means 810 is a driving device for driving a removable storage medium to read and write data. The communication control means 809 is a functional unit for communicating with the image forming apparatus 101, other terminals, server devices, etc. via the Internet.
[0060] Fig. 11 is a block diagram showing the module configuration of the network device management system and the module configuration of the remote repair service of the present invention. Specifically, Fig. 11 is a diagram showing the software configuration of each server that constitutes the network device management system 008 or the remote repair service 011. The network device management system 008 is positioned as one of the import service requesters 301 that transmits device settings.
[0061] First, a block diagram of the network device management system 008 will be described. Programs on the network device management system 008 run on a WWW server program, and a user who operates a task controls the program via a WWW browser program on a client PC (not shown). An overall control unit 900 of the network device management system 008 is a module that controls the entire system. The overall control unit 900 of the network device management system 008 distributes control to a device management unit 901, a device search unit 902, a WEB service control unit 903, a customer information management unit 904, a task management unit 905, and other modules as necessary.
[0062] The device management unit 901 is a functional module that controls the execution of processes for obtaining and setting information for the device 120 to be managed.
[0063] The device search unit 902 is a functional module that controls the execution of a process for detecting multi-function devices connected to a network.
[0064] The WEB service control unit 903 is a functional module for transmitting and receiving various information in XML format to and from the devices to be managed, including the processing of each module of the device management unit 901 and device search unit 902 and other setting information.
[0065] The contract information management unit 904 is a functional module for managing and linking the managed devices and their customer information.
[0066] The task management unit 905 is a functional module for managing various services that operate on the network device management system 008, and for linking other tasks and devices to be managed.
[0067] The content management unit 906 is a functional module for managing various services operating on the network device management system 008, managing the content handled by other tasks, and linking the managed devices.
[0068] The database unit 907 is a functional module for storing information on each module of the device management unit 901, the device search unit 902, the Web service control unit 903, the contract information management unit 904, and the task management unit 905, as well as the results of their execution, various setting information, history information, and the like.
[0069] A set of firmware applicable to image forming apparatuses is stored in the firmware pool 908. The firmware pool 908 is mainly managed and controlled by the content management unit 906.
[0070] The bundle pool 909 stores the entities of bundles that can be installed in the image forming apparatus and is mainly managed and controlled by the content management unit 906.
[0071] The entities of setting values that can be imported to the image forming apparatus are stored in the setting value pool 910. The setting value pool 910 is mainly managed and controlled by the content management unit 906.
[0072] Next, a block diagram showing the module configuration of the remote repair service 011 will be described.
[0073] The instruction operation UI unit 920 is a UI for specifying an instruction sheet to be transmitted to the image forming apparatus 101 .
[0074] The instruction transmission / reception unit 921 is a module that transmits an instruction sheet designated by the instruction operation UI unit 920 to the image forming apparatus 101. In addition, the instruction transmission / reception unit 921 receives the result of the instruction sheet executed by the image forming apparatus 101.
[0075] The execution history management unit 922 is a module that stores and manages executed instructions.
[0076] The execution history UI unit 923 displays the instruction sheet managed by the execution history management unit 922 on the UI.
[0077] The distribution reservation management unit 924 is a functional module for managing distribution data and linking the managed devices. Information on the managed devices is acquired by accessing the database unit 907 via the network device management system 008. The distribution reservation management unit 924 also has a function that enables the registration of distribution reservations based on the contract period and the type of distribution data.
[0078] When the delivery reservation management unit 924 receives a request with the firmware version as input from the image forming apparatus 101, the delivery reservation management unit 924 accesses the firmware pool 908 via the network device management system 008. Then, the delivery reservation management unit 924 transmits the entity of the firmware 250 to the image forming apparatus 101.
[0079] The same is true for the bundle pool 909, where the distribution reservation management unit 924 accesses the bundle pool 909 via the network device management system 008 in response to a request from the image forming apparatus 101 using the bundle ID and version as input. Then, the distribution reservation management unit 924 transmits the entity of the bundle to the image forming apparatus 101.
[0080] The same is true for the setting value pool 910, where the distribution reservation management unit 924 accesses the setting value pool 910 via the network device management system 008 in response to a request from the image forming apparatus 101, and transmits the actual setting value to the image forming apparatus 101.
[0081] The instruction book generation unit 925 uses the information held in the distribution reservation management unit 924 to display the instruction book configuration on the UI.
[0082] A cancel execution unit 926 cancels an instruction sheet in an execution status. A setting value specification management DB 927 is a DB referenced for generating an edit screen for setting values, and corresponds to the import module management table 701.
[0083] 12 to 15 are diagrams showing a basic import sequence in the first embodiment of the present invention. Specifically, Fig. 12 to 15 are flowcharts showing an outline of a basic import sequence in the device setting management module 309. The device setting management module 309 is processed on the CPU 108.
[0084] First, in step S1001, the policy DB is initialized. This resets all values that have been written up to that point and the archive bit 701. As a result, the DB is in a state where only key names, types, sizes, and statically defined meta information exist, and no values are entered.
[0085] In step S1002, the XML file in the import data file 705 is stored.
[0086] In step S1003, the contents of the XML file are parsed and the data is written to the policy DB, thereby performing secondary storage.
[0087] In step S1004, the import level is determined based on the received XML and the state of the own device performing the import operation.
[0088] In step S1005, import module management table 701 is referenced to identify the import module that issues the notification from import module group 321 of import processing unit 313.
[0089] In step S1006, an import instruction is issued to an import module such as the application 402 specified together with the import level.
[0090] In step S1007, the operation of reflecting the changes in the original storage 403 of each module is carried out.
[0091] FIG. 13 illustrates the procedure for reflecting XML data in the policy DB in step S1003 in the import flow of the device setting management module 309 described above.
[0092] The XML file is expressed as a hierarchical key structure in which tags having values are represented as shown in 605. In step S1101, this is parsed in sequence.
[0093] In step S1102, the relevant key is interpreted.
[0094] In step S1103, it is confirmed whether or not a key with the same name exists in the policy DB, and if not, the next item is parsed in step S1101.
[0095] If it is confirmed that a key with the same name exists in the policy DB, then in step S1104 the value defined for that key in the XML file is obtained and converted into a form that can be written to the policy DB.
[0096] In step S1105, it is confirmed whether the data structure matches the size already defined in the DB, and if the size is invalid, the item is not written and the process proceeds to parsing the next item in step S1.
[0097] If the type and size information match, the value of the corresponding item is actually written to the policy DB in step S1106. At this time, the archive bit of the meta information is changed to 1.
[0098] In step S1107, if writing of all items is completed, the process ends. If there is a next item, the process continues from 1101 to parse the next item and continue writing data to the policy DB.
[0099] FIG. 14 is a sequence diagram of the import level determination described in step S1004 in the import flow of the device setting management module 309.
[0100] In step S1201, the model management number and machine management number that are written in XML, have been exported, and are the source of the import are obtained.
[0101] In step S1202, the model management number and unit management number of the device itself are obtained from within the device. The level is determined from these four pieces of information.
[0102] In step S1203, it is determined whether the model management number described in the XML matches the model management number of the device itself. If it is determined that the model management number described in the XML matches the model management number of the device itself, the process proceeds to step S1204. On the other hand, if it is determined that the model management number described in the XML does not match the model management number of the device itself, the process proceeds to step S1205.
[0103] In step S1204, since it is determined in step S1203 that the devices are the same model, the device identification numbers are compared. If it is determined in step S1204 that the device identification numbers do not match, the process proceeds to step S1206. On the other hand, if it is determined in step S1204 that the device identification numbers match, the process proceeds to step S1207.
[0104] In step S1205, it is determined that the import is from another model, and the import level is set to 3.
[0105] In step S1206, import level 2 is set.
[0106] In step S1207, import level 1 is set.
[0107] 15 shows a detailed sequence of data expansion of each data management application module described in step S1006 in the import flow of the device setting management module 309. This sequence is a processing flow of the control import processing unit 313, and runs on the CPU 108. This sequence may be called sequentially in the same task, or may be executed in multiple tasks simultaneously, but is executed the same number of times as there are data management applications such as application 402 present in the device.
[0108] In step S1301, the import level is confirmed, which was determined in step S1004 of the sequence described in FIG.
[0109] In step S1302, the data management application module imports all of the data for which it is responsible, and repeats the process of step S1302 until all of the data for which it is responsible has been imported.
[0110] In step S1303, one of the items in charge is queried to the DB to confirm whether or not the value is secondarily stored in the policy DB. Specifically, this confirmation is performed by checking whether the archive bit 701 is set. If it is confirmed in step S1303 that the value is not secondarily stored, the process proceeds to the next step. On the other hand, if it is confirmed in step S1303 that the value is secondarily stored, the process proceeds to step S1304.
[0111] In step S1304, the data is acquired and the import level information is confirmed from the meta information of the key defined in the policy DB.
[0112] In step S1305, the import level of the XML is compared with the import level of the key to determine whether import is possible. For example, if the meta information defined in the key is "key level 1 = backup and restore in the same individual permitted" and the XML description is "import level 3 = import from a different model", permission is not granted, so the item is not imported and the process proceeds to the next item. Alternatively, if "key level 3 = import and export between different models permitted" and the XML is "import level 1 = backup and restore in the same individual", permission is granted and the process proceeds to step S1306.
[0113] In step S1306, writing is performed in the local storage.
[0114] Fig. 16 is a flowchart of the remote repair service in the first embodiment of the present invention. The process shown in Fig. 16 is positioned as one of the import service requesters 301 on the side of transmitting device settings, which is a process flow assuming a case where a push notification is started by attaching an MQTT protocol capable of bidirectional communication in a cloud service. The process shown in Fig. 16 is executed by the CPU 802 of the remote repair service 011 on the network device management system 008.
[0115] In step S1401, the import data file 705 is edited.
[0116] In step S1402, it is confirmed whether the type of protocol used by the service is MQTT.
[0117] In step S1403, if it is determined in step S1402 that the type of protocol used by the service is MQTT, the process proceeds to step S1404. On the other hand, if it is determined in step S1402 that the type of protocol used by the service is not MQTT, the process proceeds to step S1405.
[0118] In step S1404, the function name of the import module of the edited setting item to be imported is written to the high-speed mode specified csv file 703. The function name of the import module is identified by referring to the setting value specification management DB 927, which corresponds to the import module management table 701.
[0119] In step S1405, XML data is generated that includes a key list of the edited setting items to be imported.
[0120] In step S 1407 , the XML data and the csv file 703 specifying the high-speed mode are zip-compressed to generate an import data file 705 , which is then attached to the instruction sheet and transmitted to the image forming apparatus 101 .
[0121] In step S1402, the condition for determining whether or not to generate the CSV file 703 with the high-speed mode specified is not limited to the type of protocol, but may be based on a management table for each statically managed service.
[0122] Fig. 17 is a flowchart showing a process executed by the image forming apparatus according to the first embodiment of the present invention. Specifically, Fig. 17 shows details of step S1005 in the import flow executed by the device setting management module 309. The process shown in Fig. 17 is executed by the CPU 108.
[0123] In step S1501, it is confirmed whether or not the csv file 703 with the high-speed mode specified is present in the import data file 705. If it is confirmed that the csv file 703 with the high-speed mode specified is present in the import data file 705, the process proceeds to step S1502.
[0124] In step S1502, a list of function names of the import modules described in the csv file is obtained.
[0125] In steps S1503 and S1504, import module management table 701 is searched for the number of times equal to the number of function names of the listed import modules.
[0126] In step S1505, the import module management table 701 It is determined whether the module names match. If it is determined that the import module names in the import module management table 701 match, the process proceeds to step S1506. On the other hand, if it is determined that the import module names in the import module management table 701 do not match, the process returns to step S1504.
[0127] In step S1506, the handle ID is obtained.
[0128] In step S1507, the contents of the execution management bitmap function 702 are rewritten. Then, the process returns to step S1503. In step 1501, it is confirmed whether or not the csv file 703 with the high-speed mode specified exists in the import data file 705. If the csv file 703 with the high-speed mode specified does not exist, the process proceeds to step 1508 and ends. The function names written in the csv file 703 with the high-speed mode specified may be processed in order from the top, or the import process may be processed in parallel. After step 1508, the process continues to step S1006 shown in FIG. 12.
[0129] As described above, according to the first embodiment, it is possible to call only the addresses of some of the callback functions in the import module group 321 according to the protocol used by the cloud service and the contents of the execution management bitmap function 704. This realizes high-speed reflection processing. Also, since the method is selected according to the protocol used by the cloud service, it becomes possible to select an appropriate setting value reflection method according to the required specifications of the cloud service, rather than a uniform method for all services. Therefore, it becomes possible to switch between setting value reflection methods more flexibly than before.
[0130] Second Embodiment In the first embodiment, the process of calling only the addresses of some of the callback functions in the import module group 321 according to the contents of the execution management bitmap function 704 has been described. However, there was a similar problem not only with the import process sequence but also with the exclusive sequence. In the normal mode that does not include the csv file 703 with the high-speed mode specified, all the callback functions are called and the exclusive process is executed since it is assumed that the import is performed in bulk. In the function that claims the integrity of the data, such as the backup service 010, the default is to execute it at night when the user is absent, and the operation specification should basically lock all device operations, so there is no problem.
[0131] However, the remote repair service 011 has a problem that the target data cannot be flexibly rewritten remotely because of the extra guard. For example, if someone opens the authentication screen on the device using the remote UI, the authentication callback destination returns an exclusive error, so that even if the image quality setting unrelated to the authentication is to be imported, it cannot be imported. In addition, since it is not known which callback destination returns an exclusive error first, it is not possible to identify a countermeasure from the cause of the error. The process flow on the device side that solves this problem will be described with reference to the flowchart in FIG. 18. FIG. 18 is a flowchart showing the process according to the second embodiment.
[0132] Steps 1601 to 1605 are similar to steps 1501 to 1505 in the flowchart according to the first embodiment, and therefore a description thereof will be omitted.
[0133] In step 1606, before actually importing the settings, an exclusive process is performed to check whether the setting values are in a state where they can be safely rewritten. However, at this time, the contents of the execution management bitmap function 702 have already been rewritten according to the contents of the CSV file 703 specifying the high-speed mode. Therefore, it becomes possible to apply exclusive process by calling only the addresses of some of the callback functions in the import module group 321 with reference to the execution management bitmap function 704. Regarding the exclusive process, the function names written in the specified CSV file 703 may be processed in order from the top, or may be processed in parallel.
[0134] The processing from step 1607 to step 1608 is similar to the processing from step 1506 to step 1507 according to the first embodiment, and therefore a description thereof will be omitted.
[0135] As described above, according to the second embodiment, the exclusive processing is not uniform but selective depending on the data. Also, when the exclusive processing is performed on the function names described in the csv file 703 with the high-speed mode specified in order from the top, it becomes easy to identify the cause of the exclusive error and to deal with it remotely.
[0136] The present invention includes the following inventions that appropriately combine the above-mentioned features.
[0137] (Configuration 1) A setting distribution system including an information processing device to which setting data related to settings is distributed, and a distribution source device to which the setting data is distributed, wherein the distribution source device distributes to the information processing device via a network a set of the setting data including a plurality of setting values and function data specifying only at least one function that needs to be called in order to reflect at least one setting value in the information processing device in the information processing device, and the information processing device reflects the setting values included in the setting data in the information processing device by calling only the functions specified by the function data.
[0138] (Configuration 2) The setting distribution system according to configuration 1, characterized in that, when the information processing device receives the setting data, the information processing device calls a function without using the function data and reflects the setting value included in the setting data in the information processing device.
[0139] (Configuration 3) The setting distribution system according to the first or second configuration, characterized in that the distribution source device switches between distributing the setting data in a normal mode in which the setting data is distributed and distributing the setting data in a high-speed mode in which the setting data is distributed faster than in the normal mode, depending on a type of service related to a request to distribute the setting data.
[0140] (Configuration 4) 4. The setting distribution system according to claim 3, wherein the source device distributes the setting data in the high-speed mode when distributing the setting data using an MQTT protocol.
[0141] (Configuration 5) The setting distribution system according to any one of configurations 1 to 4, characterized in that the distribution source device further executes at least one of a process for specifying a name of a corresponding callback destination, a process for enabling execution of exclusive processing, and a process for defining an order in which at least one setting value in the information processing device is reflected in the information processing device.
[0142] (Method 1) A method executed in a setting distribution system including an information processing device to which setting data related to settings is distributed, and a distribution source device to which the setting data is distributed, characterized in that the distribution source device distributes to the information processing device via a network a set of the setting data including a plurality of setting values and function data specifying only at least one function that needs to be called to reflect at least one setting value in the information processing device in the information processing device, and the information processing device reflects the setting values included in the setting data in the information processing device by calling only the functions specified by the function data.
[0143] (Configuration 6) An information processing device comprising: a receiving means for receiving from a source device via a network a set of setting data including a plurality of setting values and function data that specifies only at least one function that needs to be called to reflect at least one setting value; and a reflecting means for reflecting the setting values included in the setting data by calling only the function specified by the function data.
[0144] (Method 2) A method comprising: receiving, via a network from a source device, a set of setting data including a plurality of setting values and function data that specifies only at least one function that needs to be called to reflect at least one setting value; and reflecting the setting values included in the setting data by calling only the function specified by the function data.
[0145] <Other embodiments> The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a recording medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit for implementing one or more of the functions, such as an ASIC (Application Specific Integrated Circuit).
[0146] The above describes preferred embodiments of the present invention. However, the present invention is not limited to the above-described embodiments. In other words, the present invention includes embodiments in which various modifications have been made based on the gist of the present invention, and these embodiments are not excluded from the scope of the present invention. [Explanation of symbols]
[0147] 001,002 Image forming device 004 Management Server 005 Managed Devices 006 Internet 007 Cloud Environment 008 Network Device Management System 009 Software distribution cloud service 010 Backup Service 011 Remote Repair Service
Claims
1. A setting and distribution system including an information processing device that is a destination of setting data related to settings, and a distribution source device that is a distribution source of the setting data, the source device distributes, via a network, to the information processing device, a set of the setting data including a plurality of setting values and function data specifying only at least one function that needs to be called in order to reflect at least one setting value in the information processing device in the information processing device; the information processing device reflects the setting values included in the setting data in the information processing device by calling only the functions specified by the function data; A setting distribution system comprising:
2. When the information processing device receives the setting data, the information processing device calls a function without using the function data, and causes a setting value included in the setting data to be reflected in the information processing device.
2. The setting distribution system according to claim 1.
3. the source device switches between distributing the setting data in a normal mode in which the setting data is distributed and distributing the setting data in a high-speed mode in which the setting data is distributed faster than in the normal mode, depending on a type of service related to a request for distributing the setting data.
3. The setting distribution system according to claim 1 or 2.
4. When the source device distributes the configuration data using the MQTT protocol, the source device distributes the configuration data in the high-speed mode.
4. The setting distribution system according to claim 3.
5. The source device further executes at least one of a process of specifying a name of a corresponding callback destination, a process of enabling execution of an exclusive process, and a process of defining an order in which at least one setting value in the information processing device is reflected in the information processing device.
2. The setting distribution system according to claim 1.
6. A method executed in a configuration distribution system including an information processing device that is a distribution destination of configuration data related to configuration, and a distribution source device that is a distribution source of the configuration data, comprising: the source device distributes, via a network, to the information processing device, a set of the setting data including a plurality of setting values and function data specifying only at least one function that needs to be called in order to reflect at least one setting value in the information processing device in the information processing device; the information processing device reflects the setting values included in the setting data in the information processing device by calling only the functions specified by the function data; A method comprising:
7. a receiving means for receiving, via a network from a distribution source device, a set of setting data including a plurality of setting values and function data that designates only at least one function that needs to be called in order to reflect at least one of the setting values; a reflecting means for reflecting a setting value included in the setting data by calling only a function designated by the function data; An information processing device comprising:
8. receiving, via a network from a source device, a set of setting data including a plurality of setting values and function data that specifies only at least one function that needs to be called to reflect at least one of the setting values; By calling only the functions designated by the function data, the setting values included in the setting data are reflected. A method comprising:
Citation Information
Patent Citations
Monitoring device, method and program
JP2018136876A