JP6447288B2 - Electronic device, information processing system, control method, and program - Google Patents

Description

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

  There is known a system including a main body (main body unit) of an embedded device and an operation unit serving as an operation platform of application software (hereinafter, simply referred to as “app”) that operates on the embedded device.

  Apps that run on the operation unit do not often complete their functions alone, and often provide services to users as a part of the system in cooperation with external modules of the network. In some cases, the application itself has a server function and receives a request from a remote application that operates on a PC (personal computer) or the like to provide a service. Patent Document 1 proposes an access control system for accessing a home device connected to a home network from a remote terminal arranged in an external network.

  However, in a system using an application having the server function as described above, the convenience for the user may be reduced. For example, even when connected to an app, there are cases where the power is turned off to save power, or access is not permitted, such as during an operation unit update.

  The present invention has been made in view of the above, and an object thereof is to provide an electronic device, an information processing system, a control method, and a program that can improve user convenience.

In order to solve the above-described problems and achieve the object, the present invention is an operation platform for an application having a server function, and includes an operation unit that receives an operation input, and a main body unit that operates according to the operation input. The main body unit is provided for a receiving unit that receives a request from an external device, a content of the request, and an operation state of the electronic device . A request control unit that controls supply of electric power .

  According to the present invention, it is possible to improve user convenience.

FIG. 1 is a block diagram illustrating an example of the overall configuration of the information processing system according to the embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of the MFP according to the embodiment. FIG. 3 is a diagram illustrating an example of the software configuration of the MFP according to the embodiment. FIG. 4 is a diagram for explaining an example of an application that operates on the operation unit. FIG. 5 is a diagram for explaining another example of an application that operates on the operation unit. FIG. 6 is a block diagram illustrating a more detailed configuration of the MFP according to the embodiment. FIG. 7 is a sequence diagram illustrating an example of a request control process according to the embodiment. FIG. 8 is a sequence diagram illustrating another example of the request control process according to the embodiment. FIG. 9 is a sequence diagram illustrating another example of the request control process according to the embodiment. FIG. 10 is an explanatory diagram illustrating a hardware configuration example of the client and the server according to the embodiment.

  Exemplary embodiments of an electronic apparatus, an information processing system, a control method, and a program according to the present invention will be explained below in detail with reference to the accompanying drawings.

  Hereinafter, an example will be described in which an electronic device is realized as a multifunction peripheral (MFP) having at least two functions among a copy function, a printer function, a scanner function, and a fax function. In addition to the multifunction peripheral, the present invention may be applied to an image forming apparatus such as a copying machine, a printer, a scanner device, and a fax device. The applicable electronic device is not limited to the image forming apparatus, and can be applied to any device as long as the electronic device includes a main body unit and an operation unit.

  FIG. 1 is a block diagram illustrating an example of the overall configuration of the information processing system according to the present embodiment. As shown in FIG. 1, the information processing system has a configuration in which an MFP 1, a client 400, and a server 300 are connected via a network 30. In FIG. 1, each device is shown one by one, but a plurality of each device may be provided.

  The network 30 can be any network form such as the Internet. The network 30 may be a wireless network or a wired network.

  The MFP 1 includes an operation unit 20 that receives an operation input, and a main body unit 10 that operates according to the operation input. The client 400 is a device such as a PC (personal computer). The client 400 includes an application (remote application) that accesses an application that operates on the operation unit 20 or the like of the MFP 1. The server 300 is a device that provides a Web service or the like.

  Next, an example of the hardware configuration of the MFP 1 will be described. FIG. 2 is a diagram illustrating an example of a hardware configuration of the MFP 1 according to the embodiment. The main body 10 implements various functions such as a copy function, a scanner function, a fax function, and a printer function. The operation unit 20 receives information (operation input) according to a user operation. Note that accepting a user operation is a concept including accepting information (including a signal indicating a coordinate value of a screen) input according to the user operation.

  The main body 10 and the operation unit 20 are connected to each other via a connection I / F (interface) 16, a dedicated communication path 40, and a connection I / F 26. The communication path 40 can use, for example, the USB (Universal Serial Bus) standard, but may be of any standard regardless of whether it is wired or wireless.

  The main body 10 performs an operation according to the operation received by the operation unit 20. The main unit 10 can also communicate with an external device such as the client 400, and can also perform an operation according to an instruction (such as a print instruction) received from the external device.

  First, the hardware configuration of the main body 10 will be described. As shown in FIG. 2, the main body unit 10 includes a CPU 11, a ROM 12, a RAM 13, an HDD (hard disk drive) 14, a communication I / F 15, a connection I / F 16, and an engine unit 17. The CPU 11, ROM 12, RAM 13, HDD 14, communication I / F 15, connection I / F 16, and engine unit 17 are connected to each other via a system bus 18.

  The CPU 11 comprehensively controls the operation of the main body unit 10. The CPU 11 uses the RAM 13 as a work area (work area) and executes a program stored in the ROM 12 or the HDD 14 to control the overall operation of the main body unit 10. The above-described copy function, scanner function, fax function, printer function, etc. Implement various functions.

  The communication I / F 15 is an interface for connecting to the network 30. The connection I / F 16 is an interface for communicating with the operation unit 20 via the communication path 40.

  The engine unit 17 is hardware that performs general-purpose information processing and processing other than communication for realizing a copy function, a scanner function, a fax function, and a printer function. For example, the engine unit 17 includes a scanner (image reading unit) that scans and reads an image of a document, a plotter (image forming unit) that performs printing on a sheet material such as paper, and a fax unit that performs fax communication. . The engine unit 17 may further include hardware for realizing specific options such as a finisher for sorting printed sheet materials and an ADF (automatic document feeder) for automatically feeding a document.

  Next, the hardware configuration of the operation unit 20 will be described. As shown in FIG. 2, the operation unit 20 includes a CPU 21, a ROM 22, a RAM 23, a flash memory 24, a communication I / F 25, a connection I / F 26, an operation panel 27, an external connection I / F 28, Is provided. The CPU 21, ROM 22, RAM 23, flash memory 24, communication I / F 25, connection I / F 26, operation panel 27, and external connection I / F 28 are connected to each other via a system bus 29.

  The CPU 21 comprehensively controls the operation of the operation unit 20. The CPU 21 uses the RAM 23 as a work area (work area) and executes a program stored in the ROM 22 or the flash memory 24 to control the operation of the entire operation unit 20 and information (image) according to the input received from the user. ) Display and other functions.

  The communication I / F 25 is an interface for connecting to the network 30. The connection I / F 26 is an interface for communicating with the main body 10 via the communication path 40.

  Operation panel 27 accepts various inputs in accordance with user operations and displays various types of information (for example, information in accordance with accepted operations, information indicating the operation status of MFP 1, information indicating setting status, etc.). . In this example, the operation panel 27 is configured by a liquid crystal display device (LCD) having a touch panel function, but is not limited thereto. For example, an organic EL display device equipped with a touch panel function may be used. Furthermore, in addition to or instead of this, an operation unit such as a hardware key and a display unit such as a lamp may be provided.

  The external connection I / F 28 is an interface for connecting to an IC card reader or the like, for example.

  Next, the software configuration of the MFP 1 will be described. FIG. 3 is a diagram illustrating an example of a software configuration of the MFP 1 according to the embodiment. As illustrated in FIG. 3, the main body unit 10 includes an application layer 101, a service layer 102, and an OS layer 103. The entities of the application layer 101, the service layer 102, and the OS layer 103 are various software stored in the ROM 12, the HDD 14, and the like (see FIG. 2). Various functions are provided by the CPU 11 executing these software.

  The software of the application layer 101 is an application for operating a hardware resource and providing a predetermined function. Examples of the application include a copy application for providing a copy function, a scanner application for providing a scanner function, a fax application for providing a fax function, and a printer application for providing a printer function. .

  The software of the service layer 102 is software that is interposed between the application layer 101 and the OS layer 103 and provides an interface for using hardware resources included in the main body unit 10 for the application. More specifically, it is software for providing a function of accepting an operation request for a hardware resource and arbitrating the operation request. As an operation request received by the service layer 102, a request such as reading by a scanner or printing by a plotter can be considered.

  Note that the interface function by the service layer 102 is provided not only to the application layer 101 of the main body unit 10 but also to the application layer 201 of the operation unit 20. That is, the application layer 201 (application) of the operation unit 20 can also realize a function using hardware resources (for example, the engine unit 17 in FIG. 2) of the main body unit 10 through the interface function of the service layer 102.

  The software of the OS layer 103 is basic software (operating system) for providing a basic function for controlling hardware included in the main body unit 10. The software of the service layer 102 converts a hardware resource use request from various applications into a command interpretable by the OS layer 103 and passes the command to the OS layer 103. Then, when the command is executed by the software of the OS layer 103, the hardware resource performs an operation according to the request of the application.

  Similarly, the operation unit 20 includes an application layer 201, a service layer 202, and an OS layer 203. The application layer 201, the service layer 202, and the OS layer 203 included in the operation unit 20 are similar to the main body unit 10 in terms of the hierarchical structure. However, the functions provided by the applications in the application layer 201 and the types of operation requests that can be accepted by the service layer 202 are different from those of the main body unit 10. The application of the application layer 201 may be software for operating a hardware resource included in the operation unit 20 to provide a predetermined function, but mainly includes a function (copy function, scanner function, fax function) included in the main body unit 10. This is software for providing a UI (user interface) function for performing an operation and display related to (function and printer function).

  In the present embodiment, the software of the OS layer 103 of the main body unit 10 and the software of the OS layer 203 of the operation unit 20 are different from each other in order to maintain the independence of functions. That is, the main body 10 and the operation unit 20 operate independently of each other with different operating systems. For example, it is possible to use Linux (registered trademark) as software of the OS layer 103 of the main body unit 10 and Android (registered trademark) as software of the OS layer 203 of the operation unit 20.

  As described above, in MFP 1, main unit 10 and operation unit 20 operate with different operating systems. Therefore, communication between main unit 10 and operation unit 20 is not inter-process communication within a common apparatus. This is done as communication between different devices. Examples of communication between different devices include an operation (command communication) for transmitting information received from the operation unit 20 (contents of instructions from the user) to the main unit 10 and an operation for the main unit 10 to notify the operation unit 20 of an event Etc. Here, the function of the main unit 10 can be used by the operation unit 20 performing command communication to the main unit 10. The event notified from the main unit 10 to the operation unit 20 includes an operation execution status in the main unit 10, information set in the main unit 10, and the like.

  In the embodiment, the power supply to the operation unit 20 is performed from the main body unit 10 via the communication path 40, but the power control of the operation unit 20 is performed separately from the power control of the main body unit 10 (independently). You can do it).

  In the above-described embodiment, the main body unit 10 and the operation unit 20 operate independently of each other with different operating systems. However, the present invention is not limited thereto, and for example, the main body unit 10 and the operation unit 20 operate with the same operating system. It may be a form to do. Further, the main body 10 and the operation unit 20 may be configured integrally. For example, the hardware configuration of the main body unit 10 and the operation unit 20 does not need to be separated as shown in FIG. 2, and the functions of the main body unit 10 and the operation unit 20 are realized on one hardware configuration. Good.

  Next, an example of an application that operates on the operation unit 20 will be described. FIG. 4 is a diagram for explaining an example of an application that operates on the operation unit 20. The example of FIG. 4 shows a form in which the application of the operation unit 20 receives the service by accessing the main body unit 10 or the server 300 as a client. In addition, about the same structure as said each figure, the same code | symbol is attached | subjected and description is abbreviate | omitted.

  As illustrated in FIG. 4, the server 300 includes an H / W 303, an OS 302, and a web application 301. The H / W 303 is hardware such as a CPU, ROM, RAM, memory, communication I / F, and display. The OS 302 is basic software for providing a basic function for controlling the H / W 303. The web application 301 is application software that provides a web service.

  The main unit 10 includes hardware (H / W) 104, an OS layer 103, a service layer 102, a standard copy application 101a, and a standard scan application 101b. The H / W 104 corresponds to, for example, the hardware configuration in the main body unit 10 described with reference to FIG. The standard copy application 101a and the standard scan application 101b correspond to the above-described copy application and scanner application, for example.

  In this example, the operation unit 20 includes hardware (H / W) 204, an OS layer 203, a service layer 202, and applications 201a and 201b. The H / W 204 corresponds to, for example, the hardware configuration in the operation unit 20 described with reference to FIG. The applications 201a and 201b use functions (services) of the main unit 10 and the Web application 301 by transmitting a request to the service layer 102 of the main unit 10 and a request to the Web application 301 of the server 300. When transmitting a request to the server 300, the main unit 10 may transmit a request from the applications 201a and 201b by using a NAT (Network Address Translation) function or a proxy server function.

  FIG. 5 is a diagram for explaining another example of an application that operates on the operation unit 20. The example of FIG. 5 illustrates a form in which the application of the operation unit 20 has a server function similar to that of the Web application 301, for example, and receives a request from a remote application operating on the client 400 to provide a service. In addition, about the same structure as said each figure, the same code | symbol is attached | subjected and description is abbreviate | omitted.

  As illustrated in FIG. 5, the client 400 includes an H / W 403, an OS 402, and a remote application 401. The H / W 403 is hardware such as a CPU, ROM, RAM, memory, communication I / F, and display. The OS 402 is basic software for providing a basic function for controlling the H / W 403. The remote application 401 is application software that accesses the operation unit 20 and uses a service.

  In this example, the operation unit 20 includes an H / W 204, an OS layer 203, a service layer 202, and an application 201c. The application 201c is application software having a server function such as a Web server. An external application such as the remote application 401 accesses the application 201 c via the network port of the main body unit 10.

If the MFP 1 has only one IP address, IP resources can be saved and complexity can be reduced. There are the following methods as a method of realizing a mechanism with one IP address:
(1) The destination of the packet arriving at the main unit 10 is converted into the internal IP address of the operation unit 20 and retransmitted (for example, the Linux (registered trademark) iptable and sip6tables functions).
(2) A request (such as an HTTP request) is received by the main body 10 (service layer 102), and the request is retransmitted to an appropriate server according to conditions (reverse proxy). The reverse proxy performs authentication / authorization function, encryption function, load distribution, cache, content compression, speed adjustment, and the like.

  FIG. 5 illustrates an example in which the remote application 401 transmits a request to the application 201 c of the operation unit 20 via the main body unit 10.

  In the configuration as shown in FIG. 5, the following problems (P1) and (P2) may occur when the application 201c is operated.

(P1) Power Mode Control The operation unit 20 is generally used when the user is in the vicinity of the MFP 1. When the user is not near the MFP 1, the operation unit 20 may be in a power-off (system down) state in order to save energy. Even if the power is turned on when connecting (starting) to the application 201c, the user may not be in the vicinity of the MFP 1 and the power may be turned off during the connection. The transition to the power-off state during connection can be prohibited by the application 201c itself using a power mode lock API (Application Programming Interface) or the like. However, in addition to increasing the complexity of the implementation of the application 201c, there is a possibility of forgetting to implement a function prohibited by the application 201c. Furthermore, the use of a special API such as a power mode lock API lowers portability and compatibility with another Web platform (container).

(P2) Access control There is no access control method according to the state and settings of the MFP 1. For example, it is assumed that the application 201c transfers a large-scale scan image scanned by the main body unit 10 to itself via a connection cable or the like. In such a case, it is desirable for the application 201c to guarantee a certain transfer rate. However, for example, if a transmission request for a large amount of data is sent from the client 400 to the application 201c during the transfer of the scanned image, there is a possibility that transfer at a constant transfer rate cannot be realized. Further, for example, it may be necessary to suppress access to the application 201c, such as during an update of the operation unit 20. Note that the update includes system data (such as an address book) of the operation unit 20, an update via a network such as a system and a module, and an update using the SD card of the operation unit 20. In such a case, a response (status code or the like) indicating that the service cannot be used should be returned to the request from the client 400, but there is no guarantee that the operation unit 20 is operating in such a state. Further, the application 201c may not be able to respond to the request retransmitted from the reverse proxy. In that case, the reverse proxy must wait until the timeout, and cannot know why the application 201c failed to respond. This is not efficient and an appropriate status code is not returned to the client 400.

  Therefore, when the MFP 1 of the present embodiment receives a request from the client 400, the MFP 1 controls processing for the request according to the content of the request, the state of the devices (the main body unit 10 and the operation unit 20), settings, and the like. Thereby, the problems such as the above (P1) and (P2) can be solved and user convenience can be improved.

  FIG. 6 is a block diagram showing a more detailed configuration of the MFP 1 according to the present embodiment. In addition, about the same structure as said each figure, the same code | symbol is attached | subjected and description is abbreviate | omitted. As shown in FIG. 6, the main body unit 10 of the MFP 1 includes an external connection unit 651, a request control unit 652, a resource management unit 653, a power supply control unit 654, a container 660, the HDD 14, and a setting storage unit 671. .

  The setting storage unit 671 stores various setting information for the MFP 1. The setting storage unit 671 may be realized by the HDD 14 or the like, or a storage medium other than the HDD 14 may be used.

  The external connection unit 651 performs network processing (physical layer to transport layer) of the main body unit 10. For example, the external connection unit 651 accepts a request from the client 400 (reception unit), and passes the accepted request to the request control unit 652. The external connection unit 651 receives a response from the request control unit 652 and returns it to the client 400. When the external connection unit 651 receives a request from the client 400 while the main body unit 10 is in a system stopped state, the external connection unit 651 energizes the main body unit 10 using the request as a trigger.

  A resource management unit 653 manages resources of the MFP 1. For example, the resource management unit 653 periodically notifies the request control unit 652 of information (resource information) related to the resource. The request control unit 652 may access the resource management unit 653 to acquire resource information.

  The power control unit 654 controls power supply to the operation unit 20 and the HDD 14.

  The container 660 includes applications 662a and 662b and an application management unit 661. The applications 662a and 662b are Web applications that operate on the main body unit 10, for example. If there is no need to distinguish between the applications 662a and 662b, the application 662 may be simply referred to as an application 662. The application management unit 661 performs installation, uninstallation, status confirmation, and the like of an application that operates on the main body unit 10 such as the application 662.

  The request control unit 652 controls processing for the request according to the content of the request, the state of the device, and the setting information stored in the setting storage unit 671. Details of the control processing by the request control unit 652 will be described later.

  The external connection unit 651, the request control unit 652, the resource management unit 653, and the power supply control unit 654 can be realized as functions of the service layer 102 or the OS layer 103 in FIG. 3, for example. The container 660 can be realized as a function of the application layer 101 in FIG.

  The operation unit 20 includes an operation unit system 630, a container 610, and a media management unit 620. The operation unit system 630 is a system serving as a base of the operation unit 20, and corresponds to, for example, the OS layer 203 and the service layer 202 in FIG. The operation unit system 630 may have a function of returning the power supply during energy saving.

  The container 610 includes applications 612a and 612b and an application management unit 611. The applications 612a and 612b are Web applications that operate on the operation unit 20, for example. The application management unit 611 performs installation, uninstallation, status confirmation, and the like of applications that operate on the operation unit 20 such as the applications 612a and 612b. The container 610 can be realized as a function of the application layer 201 in FIG. 3, for example. If there is no need to distinguish between the applications 612a and 612b, the application 612 may be simply referred to as an application 612.

  The media management unit 620 performs connection with the external medium 700 such as an SD card, transmission / reception of information to / from the external medium 700, and the like. The external medium 700 is used for updating the operation unit 20, for example. The media management unit 620 can be realized as a function of the application layer 201 or the service layer 202 in FIG.

  Hereinafter, the function of the request control unit 652 will be further described. For example, when the request destination (URL: Uniform Resource Locator or the like) is the application (application 612) of the operation unit 20, the request control unit 652 energizes the operation unit 20 through the power supply control unit 654. Note that when the operation unit 20 is already energized and when the destination of the request is an application (application 662) in the main body unit 10, control to energize the operation unit 20 is not necessary. The operation unit 20 and the main body unit 10 are connected by a power / signal line (communication path 40) such as USB. The power control unit 654 of the main body unit 10 can perform power control of the operation unit 20 on the device side as a host.

  The request control unit 652 receives a notification (connection possible notification or connection impossible notification) indicating “connectable” or “not connectable” from the operation unit system 630, so that the application 612 can be connected. It can be recognized whether it is in a state where it cannot be connected. The state incapable of connection includes, for example, a state in which the operation unit 20 is not energized, a state immediately after energization, a state immediately before the system is stopped, and a state in which the system is being updated.

  The request control unit 652 prohibits power-off of the operation unit 20 (power mode lock) at least during request processing. For example, the request control unit 652 first prohibits power-off of the main body unit 10 that has received the request information. If the destination of the request information is the application 612, the request control unit 652 also prohibits the operation unit 20 from being turned off. The request control unit 652 prohibits power-off of the main body unit 10 and the operation unit 20 by using, for example, a power mode lock API. When the process of the application 612 is completed, the request control unit 652 releases the power mode lock as necessary. The power supply mode lock can be performed by the application 612 using the API or the like of the operation unit system 630. However, when the request control unit 652 executes the power mode lock, the complexity of mounting the application 612 can be reduced.

  Further, the request control unit 652 performs system mode lock at least during processing of the request of the application 612. For example, the request control unit 652 prevents the system update of the main body unit 10 and the operation unit 20 and the update of the system information such as the setting information and the address book during the processing of the application 612. Conversely, when a request to the application 612 occurs while the above-described system update processing is being executed, the request control unit 652 returns information (503 (Service Unavailable) or the like) indicating that the application 612 cannot be used. May be.

  Further, the request control unit 652 dynamically processes the request according to the state of the device. For example, when the resource usage rate of the transmission path (communication path 40) by the main unit 10 and the operation unit 20 (hereinafter also simply referred to as a system) or the application 662 exceeds a certain value, the request is retransmitted to the application 612. If the resource usage rate falls below a certain value, the request is resent. The resource management unit 653 measures the usage status of such resources, and notifies the request control unit 652 of the resource information according to changes in the resources.

  The system, the application 662 and the application 612 can share (simultaneously) the resources of the communication path 40. However, the overall system efficiency may be reduced due to the desire to prioritize transmission of the system or application 662 or the influence of switching overhead due to sharing.

  There is also a method of causing the system to preferentially use resources by lowering the priority of the process or thread that redirects the request to the application 612 without holding the request retransmission. There is also a method of providing a lock function for system resources and holding the request when the lock function cannot be used. When it is desired to secure the resources used by both the application 612 and the system, such as the CPU (CPU 11, CPU 21), RAM (RAM 13, RAM 23), and communication path 40, for a certain period of time, the request control unit 652 locks the system resources, And unlock.

  The request control unit 652 has an API for setting setting information related to request control. The set setting information is stored in the setting storage unit 671. For example, setting information such as not transferring when the usage rate of the communication path 40 exceeds 80% is stored.

  The request control unit 652 knows the URL published by the application 612. Therefore, the application management unit 611 notifies the request control unit 652 of the URL that the application 612 discloses at the time of installation and uninstallation. When the URL published by the application 612 is dynamically changed, the application management unit 611 notifies the request control unit 652 of the URL when the URL is published. The request control unit 652 sends an error (NG) response to the application management unit 611 when another application that discloses the same URL has already been installed or is being executed. Upon receiving the error response, the application management unit 611 performs appropriate measures such as failure to install the application 612.

  The application 612 can set a request redirection destination for the request control unit 652. For example, when the request URL is “/ opepane / app1”, the application 612 can set “/ machine / app1” as a redirect destination. The redirect destination information can also be set via the API for setting the above setting information, and is stored in the setting storage unit 671.

  The request control unit 652 has a timeout time indicating a time until timeout. For example, when there is no response from the application 612 beyond the timeout time, the request control unit 652 disconnects communication with the application 612 and returns an error to the client 400.

  Next, request control processing by the information processing system of the present embodiment configured as described above will be described. FIG. 7 is a sequence diagram illustrating an example of a request control process according to the present embodiment. FIG. 7 shows an example of processing in the case of controlling the supply of power in response to a request. In FIG. 7, it is assumed that the operation unit 20 is in a power-off state because the operation unit 20 has not been used for a certain period of time.

  The client 400 transmits a request for any application in the MFP 1 (step S101). The external connection unit 651 receives the transmitted request and transmits it to the request control unit 652 (step S102). If the main body unit 10 is stopped, the external connection unit 651 energizes the main body unit 10 using the request as a trigger.

  The request control unit 652 confirms the content (URL or the like) of the request, and determines whether the access destination (redirect destination) is the application 612 or the application 662 (step S103). If the URL does not correspond to any of them, an error (404 (Not Found) in the case of HTTP) is returned to the client.

  The request control unit 652 locks the power supply mode of the main body unit 10 (step S104) and locks the system mode (step S105). Thereby, the power-off of the main-body part 10 and system-related operation are prohibited. The request control unit 652 may cause the power control unit 654 to execute the power mode lock. Further, the request control unit 652 may cause another module that manages the system to execute the system mode lock.

  When the URL of the access destination is a URL published by the application 612, the following processing from step S106 to step S122 is executed. The request control unit 652 redirects the request to the application 612. At this time, if the operation unit 20 is in a power-off state, the following processing from step S106 to step S114 is executed.

  The request control unit 652 sends an instruction for power operation (energization of the operation unit 20) to the power control unit 654 (step S106). When the operation unit 20 is energized, the power control unit 654 returns information (acceptance OK) indicating that the operation unit 20 is energized (step S107). If it cannot be accepted for some reason, such as a hardware failure, the power supply control unit 654 returns information (acceptance NG) indicating that it cannot be accepted. In the case of acceptance NG, the request control unit 652 may perform a fixed number of retries. If power cannot be supplied after a predetermined number of retries, the request control unit 652 returns a status code and a message indicating a system error to the client 400.

  If the HDD 14 is not energized, the power supply control unit 654 energizes (step S108). As a result, the physical disk (HDD 14) that takes time until the use is resumed can be energized first, and the application 612 can be made available immediately after the resume. In addition, the power supply control unit 654 instructs the operation unit system 630 to perform energization processing (step S109).

  The operation unit system 630 restarts the application 612 via the application management unit 611 (Steps S110 and S111). The application management unit 611 transmits a notification that the operation unit 20 is connectable (connection possible notification) to the request control unit 652 (step S112). The request control unit 652 receives a connectable notification from the operation unit system 630. The request control unit 652 waits for a predetermined time after receiving the acceptance OK for the power operation. When a connection enable notification cannot be received within a certain time, a status code and a message indicating that an error has occurred are returned to the client 400.

  When resumed, the application 612 receives a notification that the HDD 14 is available through the application management unit 611 (steps S113 and S114).

  The request control unit 652 locks the power mode and system mode of the operation unit 20 and restricts the operation (steps S115 and S116). There may be a plurality of types of system mode locks. For example, there are types such as locking firmware updates, locking app installs and updates, and locking system data updates. Which system mode is to be locked is set by setting information in the setting storage unit 671, for example.

  The request control unit 652 transmits (redirects) the request to the application 612 (step S117). The main unit 10 and the operation unit 20 are connected by an internal network (communication path 40). At the time of redirection, the request control unit 652 notifies the application 612 together with the network information (IP address, subnet, etc.) of the external connection unit 651. This is because the network information that can be connected from the client 400 is required when the application 612 creates a link or the like of a Web page.

  The application 612 processes the request (step S118) and returns a response (such as an HTTP response) to the request control unit 652 (step S119). The request control unit 652 sets response information (for example, HTTP status code “200 OK”) (step S120).

  The request control unit 652 releases the lock between the power mode and the system mode of the operation unit 20 (steps S121 and S122). The request control unit 652 unlocks the power supply mode and the system mode of the main body unit 10 (steps S123 and S124).

  The request control unit 652 returns a response to the client 400 via the external connection unit 651 (steps S125 and S126).

  FIG. 8 is a sequence diagram illustrating another example of the request control process according to the present embodiment. FIG. 8 shows an example of processing in the case of controlling access to the operation unit 20 according to the request and the state of the MFP 1.

  It is known that the request control unit 652 receives a notification that connection is possible in advance (step S201) and can connect to the application 612.

  Steps S202 to S208 are the same as Steps S101 to S105, Step S115, and Step S116 in FIG.

  The resource management unit 653 periodically notifies the resource information to the request control unit 652 (step S209). The request control unit 652 may access the resource management unit 653 to acquire resource information (step S210). The resource information is information representing the current resource usage status, such as information representing resource usage (resource usage) and information representing resource usage (resource usage). Information other than this may be used as resource information.

  The request control unit 652 confirms the request content (size, etc.), setting information, and resource information, and whether or not the request can be redirected to the application 612, that is, whether or not the requested application 612 is allowed to be executed. Determine whether. When the request can be transmitted to the application 612, the request control unit 652 transmits the request to the application 612 (step S211). The application 612 processes the request (step S212), and returns a response (such as an HTTP response) to the request control unit 652 (step S213). The request control unit 652 sets response information to be returned to the client 400 (for example, HTTP status code “200 OK”) (step S214).

  If the request cannot be transmitted to the application 612, the request control unit 652 may repeat step S209 and step S210 until the timeout time elapses or until the number of retries is reached. If it is determined that the request cannot be finally transmitted, the request control unit 652 may return information indicating that the execution of the application 612 is not permitted to the client 400. For example, the request control unit 652 sets information (503 (Service Unavailable) or the like) indicating that the application 612 cannot be used as response information to be returned to the client 400 (step S215).

  Steps S216 to S221 are the same as steps S121 to S126 in FIG.

  Note that the request control process in FIG. 8 shows a process when the URL of the request is addressed to the application 612. When the request URL is the application 662 of the main body unit 10, the resource of the communication path 40 may not be taken into consideration.

  FIG. 9 is a sequence diagram illustrating another example of the request control process according to the present embodiment. FIG. 9 shows an example of access control while the module of the operation unit 20 is being updated. For example, it is assumed that a request for the application 612 is received during the update of a module such as the application management unit 611 of the operation unit 20.

  For example, the operation unit system 630 uses the media management unit 620 to check information on the external media (steps S301 and S302). For example, when the data of the external medium 700 such as an SD card is data that affects system operation such as update data of the application 612, the media management unit 620 responds to an inquiry from the operation unit system 630 in response to an inquiry from the system operation. Is notified that the data is subject to restrictions.

  The operation unit system 630 may notify the request control unit 652 that an operation restriction (for example, updating of a module in the operation unit 20) occurs. For example, when the module of the operation unit 20 is being updated, the operation unit system 630 transmits information (such as an event) indicating that the module is being updated to the request control unit 652 (step S303).

  On the other hand, when the data in the SD card is not related to the update of the operation unit system 630 or the application 612, the media management unit 620 informs the operation unit system 630 that the data is not related to the system operation. return. In this case, the request control unit 652 is not notified because there is no restriction. The operation unit system 630 can know that an external medium 700 such as an SD card has been inserted.

  Accordingly, the request control unit 652 can know in advance that the module of the operation unit 20 is being updated and the request cannot be redirected to the application management unit 611 of the operation unit 20. This is not the only way to know that a request cannot be redirected. For example, it may be determined that the request cannot be redirected by detecting that the system mode lock of the operation unit 20 fails.

  Steps S304 to S306 are the same as steps S101 to S103 in FIG.

  In this example, since the request cannot be redirected to the operation unit 20, the request control unit 652 sets information indicating that the application 612 cannot be used (eg, 503 (Service Unavailable)) as response information to be returned to the client 400 (step S307).

  When the URL of the access destination is a URL published by the application 662 of the main body unit 10, the following processing from step S308 to step S315 is executed.

  The request control unit 652 locks the power mode and the system mode of the main body unit 10 and restricts the operation (steps S308 and S309). The request control unit 652 transmits (redirects) the request to the application 662 (step S310). The application 662 processes the request (step S311), and returns a response (such as an HTTP response) to the request control unit 652 (step S312). The request control unit 652 sets response information (for example, HTTP status code “200 OK”) (step S313). The request control unit 652 unlocks the power supply mode and the system mode of the main body unit 10 (steps S314 and S315).

  Steps S316 to S317 are the same as steps S125 to S126 in FIG.

  As described above, in this embodiment, processing for a request is controlled according to the content of the request from the outside, the state of the device, the setting, and the like. For example, in the power supply mode control, when the request is for an application of the operation unit, the operation unit is energized, and then the power mode is locked so that the system does not go down, and the request is redirected to the application of the operation unit. For example, in access control, it is determined whether the application of the operation unit should communicate according to the status of the system resources such as the CPU, memory, and communication band, and the state of the operation unit. Redirect the request to the app. Such control can improve user convenience.

  Next, the hardware configuration of the client 400 and the server 300 according to the present embodiment will be described with reference to FIG. FIG. 10 is an explanatory diagram illustrating a hardware configuration example of the client 400 and the server 300 according to the present embodiment.

  The client 400 and the server 300 according to the present embodiment are connected to a control device such as a CPU (Central Processing Unit) 1001, a storage device such as a ROM (Read Only Memory) 1002 and a RAM (Random Access Memory) 1003, and a network. A communication I / F 1004 for performing communication and a bus 1011 for connecting each unit.

  Programs executed by the client 400 and the server 300 according to the present embodiment are provided by being incorporated in advance in the ROM 1002 or the like.

  A program executed by the client 400 and the server 300 according to the present embodiment is a file in an installable format or an executable format, and is a CD-ROM (Compact Disk Read Only Memory), a flexible disk (FD), a CD-R ( It may be configured to be recorded on a computer-readable recording medium such as a Compact Disk Recordable (DVD) or a DVD (Digital Versatile Disk) and provided as a computer program product.

  Furthermore, the program executed by the client 400 and the server 300 according to the present embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. The program executed by the client 400 and the server 300 according to this embodiment may be configured to be provided or distributed via a network such as the Internet.

  The program executed by the client 400 and the server 300 according to the present embodiment can cause a computer to function as each unit of the client 400 and the server 300 described above. In this computer, the CPU 1001 can read a program from a computer-readable storage medium onto a main storage device and execute the program.

DESCRIPTION OF SYMBOLS 10 Main-body part 20 Operation part 30 Network 40 Communication path 101a Standard copy application 101b Standard scan application 300 Server 400 Client 610 Container 611 Application management part 612a, 612b Application 620 Media management part 630 Operation part system 651 External connection part 652 Request control part 653 Resource management unit 654 Power supply control unit 660 Container 661 Application management unit 662a, 662b Application 671 Setting storage unit 700 External media

JP 2012-222678 A

Claims (4)

An operation platform for an application having a server function, an electronic device including an operation unit that receives an operation input and a main body unit that operates according to the operation input,
The main body is
A receiving unit for receiving a request from an external device;
A request control unit that controls supply of power to the operation unit that is requested for processing according to the content of the request and the operating state of the electronic device;
Electronics. Information that includes an operating device for an application having a server function, an electronic device including an operation unit that receives an operation input, a main body unit that operates according to the operation input, and an external device connected to the electronic device. A processing system,
The main body is
A receiving unit for receiving a request from the external device;
A request control unit that controls supply of power to the operation unit that is requested for processing according to the content of the request and the operating state of the electronic device;
Information processing system. An operation platform for an application having a server function, a control method executed by an electronic device including an operation unit that receives an operation input and a main body unit that operates according to the operation input,
The main body unit receives a request from an external device;
A request control step in which the main body controls the supply of power to the operation unit requested to be processed according to the content of the request and the operating state of the electronic device.
Control method. An operating platform for an application having a server function, and a computer provided in the main body of an electronic device including an operation unit that receives an operation input and a main body that operates according to the operation input.
A receiving unit for receiving a request from an external device;
A request control unit that controls supply of power to the operation unit that is requested to process according to the content of the request and the operating state of the electronic device,
Program to function as.

Images