JP6668601B2 - Apparatus, image forming apparatus, information processing method, information processing program, and information processing system - Google Patents

Description

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

  In recent years, many functions have been added to Web browsers. Along with this, web applications that provide solutions using HTML (HyperText Markup Language) / CSS (Cascading Style Sheet) / JAVA (registered trademark) scripts are increasing. Such movements are spreading not only in personal computer devices (PCs) but also in the field of smart devices.

  Japanese Patent Application Laid-Open No. 2011-141684 discloses an image forming apparatus that stores an HTML file in which a job flow is described in a Web browser and provides the HTML file to a user.

  However, unlike a web browser provided in a personal computer device, it is difficult to add a function to a web browser provided in a smart device without updating browser software. Further, it is difficult for a Web browser provided in a smart device to add a function by installing a plug-in developed by a user. The image forming apparatus disclosed in Patent Document 1 has the same problem.

  SUMMARY OF THE INVENTION The present invention has been made in view of the above-described problems, and provides an apparatus, an image forming apparatus, an information processing method, an information processing program, and an information processing system that can easily add functions without updating a program of the apparatus. For the purpose of providing.

In order to solve the above-described problems and achieve the object, the present invention provides a Web application provided by a server device on a network, which requests execution of predetermined processing, or a Web application downloaded from a server device. A device including a Web browser for requesting an application to execute a predetermined process , wherein the Web application requests the Web browser for a connection status of an NFC device connected to the device. An interface unit, an execution unit that is additionally installed in the device and executes an additional program capable of acquiring the connection status of the NFC device connected to the device, and a connection status of the NFC device connected to the device acquired by the additional program And a second interface unit for notifying the Web browser of the By transmitting and receiving information between the web application and the web browser via the first interface unit and transmitting and receiving information between the web browser and the execution unit via the second interface unit, The Web application acquires the connection status of the NFC device acquired by the additional program via the first interface unit and the second interface unit .

  ADVANTAGE OF THE INVENTION According to this invention, there exists an effect that a function can be easily added, without updating the program of an apparatus.

FIG. 1 is a hardware configuration diagram of the MFP and the server device according to the embodiment. FIG. 2 is a software configuration diagram for implementing a function expansion operation of a Web browser provided in the MFP according to the embodiment. FIG. 3 is a sequence diagram showing a standard operation flow of the Web application, the Web browser, and the additional script. FIG. 4 is a flowchart illustrating a flow of processing a request for a script general-purpose API by a Web browser. FIG. 5 is a diagram illustrating a software configuration for enabling use of an NFC device that is not supported by the Web browser. FIG. 6 is a sequence diagram illustrating a flow in which the Web application acquires the connection status of the NFC device. FIG. 7 is a sequence diagram illustrating a flow of notifying a change in the connection status of the NFC device. FIG. 8 is a sequence diagram illustrating a flow of notifying a plurality of Web applications that the connection status of the NFC device has been changed.

  Hereinafter, a multifunction peripheral (MFP) according to an embodiment to which the present invention is applied will be described as an example. The application of the present invention to an MFP is only an example, and the present invention may be applied to any electronic device that has a Web browser.

  FIG. 1 is a hardware configuration diagram of an MFP 1 according to an embodiment, which is an example of a device. As shown in FIG. 1, the MFP 1 includes a main body 10 having various functions such as a copy function, a scanner function, a facsimile function, and a printer function, and an operation unit 20 that receives an input corresponding to a user operation. The main body 10 and the operation unit 20 are communicably connected to each other via a dedicated communication path 30. The communication path 30 may use, for example, a USB (Universal Serial Bus) standard, but may use an arbitrary standard regardless of whether it is wired or wireless. Further, the main body 10 may have one function or a plurality of functions among image forming functions such as a copy function, a scanner function, a facsimile function, and a printer function.

  As the operation unit 20, an electronic device that can execute complete information processing by itself can be used. As an example, as the operation unit 20, an information processing terminal (smart device) such as a smartphone or a tablet terminal can be used. In this case, the smart device used as operation unit 20 functions as the operation unit of MFP 1.

  More specifically, the smart device used as the operation unit 20 is detachably connected to the MFP 1 instead of the operation panel conventionally fixed and installed as the operation unit dedicated to the MFP 1. That is, the smart device used as the operation unit 20 is installed integrally with the MFP 1 while being detachable (separable) at a predetermined position such as a position where the operation panel of the MFP 1 is arranged. Therefore, the smart device and the MFP 1 used as the operation unit 20 may be grasped as one device. When the smart device as the operation unit 20 is detached from the MFP 1, the smart device performs wireless communication with the MFP 1, such as Bluetooth (registered trademark), Wi-Fi (registered trademark), or infrared communication, as an operation unit of the MFP 1. Function. Although the operation unit 20 of the MFP 1 is detachable from the main body 10 as described above, the operation unit 20 may be fixed to the main body 10.

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

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

  The CPU 11 totally controls the operation of the main body 10. The CPU 11 controls the overall operation of the main body 10 by executing a program stored in the ROM 12 or the HDD 14 using the RAM 13 as a work area (work area), and performs the above-described copy function, scanner function, facsimile function, printer function, and the like. To realize various functions.

  The communication I / F 15 is an interface for communicating with an external device such as a client PC (personal computer) on the network 40 or a Web server device 37 which is an example of a server device. The connection I / F 16 is an interface for communicating with the operation unit 20 via the communication path 30. In FIG. 1, the communication path 30 is illustrated in a wired manner, but the operation unit 20 is provided to be attachable to and detachable from the main body 10 of the MFP 1 as described above. Therefore, it is understood that when the operation unit 20 is attached to the MFP 1, the communication path 30 functions as a wired communication path, and when the operation unit 20 is removed from the MFP 1, the communication path 30 functions as a wireless communication path. I want to.

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

  Next, a hardware configuration of the operation unit 20 will be described. As shown in FIG. 1, 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, and an operation panel 27. Connected to each other.

  The CPU 21 controls the operation of the operation unit 20 as a whole. The CPU 21 controls the operation of the entire operation unit 20 by executing a program stored in the ROM 22 or the flash memory 24 using the RAM 23 as a work area (work area).

  Further, for example, a Web browsing application program (Web browsing AP) is stored in a storage unit such as the ROM 22. The CPU 21 realizes the Web browser 19 by executing the Web browsing AP. The Web browser 19 performs a browsing operation or the like in cooperation with a Web application 39 stored in a storage unit such as the HDD 34 of the Web server device 37. As will be described in detail later, the MFP 1 of the embodiment can easily add a function to the Web browser 19 of the operation unit 20 without updating the browser software. The Web application 39 is an example of a first program. The web browser 19 is an example of a second program.

  In this example, it is assumed that the Web browsing AP is stored in the ROM 22 of the operation unit 20 of the MFP 1 or the like. However, the Web browsing AP may be stored in a storage unit on the main body 10 side of the MFP 1, such as the ROM 12, the RAM 13, or the HDD 14. In this case, the Web browser 19 is realized by the CPU 11 of the main body 10 executing the Web browsing AP stored in the ROM 12 or the like.

  The communication I / F 25 is an interface for communicating with the Web server device 37 on the network 40, for example. The connection I / F 26 is an interface for communicating with the main unit 10 via the communication path 30.

  The operation panel 27 includes a liquid crystal display (LCD) having a touch sensor. The operation panel 27 receives various inputs according to the operation of the user, and displays various information such as information corresponding to the received input, information indicating the operation status of the MFP 1, and information indicating the setting state. Note that the operation panel 27 may be configured by an organic EL display device having a touch sensor. Further, in addition to or instead of this, an operation unit such as a hardware key or a display unit such as a lamp may be provided.

  Next, the Web server device 37 connected to the MFP 1 via the network 40 includes a CPU 31, a ROM 32, a RAM 33, an HDD 34, and a communication I / F 35, as shown in the hardware configuration diagram of FIG. . The CPU 31 to the communication I / F 35 are mutually connected via a system bus 38. In a storage unit such as the HDD 34, a Web application 39 developed by an application developer and a third vendor of the manufacturer of the MFP 1 that provides a solution to a user is stored. The Web application 39 is executed by the CPU 31 and cooperates with the Web browser 19 of the MFP 1 to enable the Web browser 19 to perform a browsing operation or the like. Note that the Web application 39 may be downloaded from the Web server device 37 to the MFP 1 and the CPU 21 or the CPU 11 of the MFP 1 may execute the downloaded Web application 39.

  In the example of the embodiment, the OS of the main unit 10 and the OS of the operation unit 20 are different from each other in order to keep the functions independent. That is, the main body 10 and the operation unit 20 operate independently of each other with different operating systems. For example, it is also possible to use Linux (registered trademark) as the OS on the main body 10 side and to use Android (Android (registered trademark)) as the OS on the operation unit 20 side.

  By operating the main unit 10 and the operation unit 20 with different operating systems, communication between the main unit 10 and the operation unit 20 is performed not as inter-process communication in a common device but as communication between different devices. The operation (command communication) of transmitting the input (the instruction content from the user) received by the operation unit 20 to the main body 10 and the operation of the main body 10 notifying the operation unit 20 of an event correspond to the operation. Here, the function of the main body 10 can be used by the operation unit 20 performing command communication to the main body 10. In addition, the event notified from the main body 10 to the operation unit 20 includes an execution state of an operation in the main body 10, contents set on the main body 10, and the like.

  Next, the MFP 1 of the embodiment can extend the function of the Web browser 19 provided in the operation unit 20 by installing the function developed by the user without updating the software. FIG. 2 is a software configuration diagram for implementing such a function expansion operation of the Web browser 19. In FIG. 2, “Web browser 19” and “OS 50 on smart device” are, for example, provided in MFP 1 and provided by the manufacturer of MFP 1. The OS 50 is an example of a control program. On the other hand, the “Web application 39” and the “script execution unit 51” are parts developed and provided by an application developer and a third vendor of the maker of the MFP 1 that provides a solution to the user.

  The additional script 52 of the script execution unit 51 is a so-called plug-in module developed by the user and installed in the operation unit 20 or the like. The user generates an additional script 52 by describing a desired operation specification and a command sentence for causing the script execution unit 51 to perform processing. The script execution unit 51 is an example of an execution unit. The additional script 52 is an example of an additional program.

  Generally, a Web browser of a personal computer (PC) employs a function extension method using a plug-in format, and provides an API for the plug-in. However, an OS such as Android (Android) or IOS (iOS (registered trademark)) provided mainly in a smart device such as the operation unit 20 does not have a plug-in mechanism. For this reason, the application developer and the third vendor on the maker of the MFP 1 cannot add (extend) the function of the Web browser using the plug-in.

  For this reason, the manufacturer of the MFP 1 according to the embodiment prepares the general-purpose APIs 55a, 55b, 56a, 56b, 58a, and 58b for connecting the Web application 39 and the script execution unit 51 to the Web browser 19 in advance. .

  The general-purpose APIs 55a and 55b between the Web application 39 and the Web browser 19 are examples of a first interface unit, and are provided in a language such as a JAVA (registered trademark) script that can be handled by the Web application 39. The general-purpose APIs 56a, 56b, 58a, and 58b between the Web browser 19 and the script execution unit 51 are an example of a second interface unit, and are provided in a language that can be executed by the OS 50 on the smart device. For example, when the OS 50 is Android (registered trademark), the general-purpose APIs 56a, 56b, 58a, and 58b are described and provided in the language of JAVA (registered trademark) script. When the OS 50 is IOS (i.e., iOS (registered trademark)), the general-purpose APIs 56a, 56b, 58a, and 58b are described and provided in the language of Objective-C (Objective-C).

  Further, when the script execution unit 51 is activated, the installed additional script 52 is compiled into an executable form and is made executable. The Web browser 19 acquires a request from the Web application 39 via the general-purpose APIs 55a and 55b. At this time, the Web application 39 notifies the Web browser 19 via the general-purpose APIs 55a and 55b of the request generated by the data indicating the script execution unit 51 to which the request is sent and the data to be passed to the script execution unit 51.

  The Web browser 19 transmits, via the general-purpose APIs 56a and 56b, the request acquired from the Web application 39 to the script execution unit 51 in which the request destination additional script 52 is installed. The script execution unit 51 executes the script general-purpose API 57 (or the script general-purpose API 59) of the additional script 52 that can be executed as described above. With this series of flows, an extended function by the additional script 52 described by the user can be provided to the user.

  Note that the number of the additional scripts 52 may be one or more. Even when a plurality of additional scripts 52 exist, the Web application 39 can specify the additional script 52 to be used, so that a desired function of the additional script 52 can be used.

  The additional script 52 is stored in a storage area provided for each user. The Web browser 19 changes the additional script 52 to be called according to the user. The storage area of the additional script 52 for each user is determined by the Web browser 19 acquiring the user logged in to the main body 10 from the main body 10.

  Next, a standard operation flow of the Web application 39, the Web browser 19, and the additional script 52 is shown in the sequence diagram of FIG. As a premise, the additional script 52 is installed in the script execution unit 51 in advance and is in a usable state. In this state, the process is started from step S1. In step S1, the Web application 39 notifies the Web browser 19 of the request destination and the transmission data via the general-purpose APIs 55a and 55b. The request destination is, for example, the additional script 52.

  Next, in step S2, the Web browser 19 acquires information of the logged-in user from the main body 10, and determines an additional script 52 that can be used by the logged-in user. Next, in step S3, the Web browser 19 notifies the script execution unit 51 of the transmission data via the general-purpose APIs 56a and 56b.

  In step S4, the script execution unit 51 notifies the additional script 52, which has been converted into the execution format, of transmission data using the script general-purpose API 57 (or the script general-purpose API 59) at the time of startup. If necessary, the additional script 52 notifies the script execution unit 51 of the processing result as shown in step S5. If necessary, as shown in step S6, the script execution unit 51 notifies the Web browser 19 of the processing result. In this case, the Web browser 19 notifies the Web application 39 of the processing result from the additional script 52 as shown in step S7.

  Next, FIG. 4 is a flowchart showing a flow in which the Web browser 19 processes a request of the script general-purpose API 57. In the flowchart of FIG. 4, first, in step S11, the web browser 19 receives a request destination and transmission data from the web application 39 via the general-purpose APIs 55a and 55b. The request destination is, for example, the additional script 52.

  Next, in step S12, the Web browser 19 acquires the information of the logged-in user from the main body 10, and determines the additional script 52 corresponding to the logged-in user as a transmission data transmission destination. Next, in step S13, the Web browser 19 separates the request destination and the transmission data received from the Web application 39. In step S14, the script execution unit 51 determines whether or not there is an additional script 52 to be requested. If it is determined that there is no additional script 52 to be requested (step S14: No), the processing of the flowchart in FIG.

  On the other hand, if it is determined that the additional script 52 to be requested exists (step S14: Yes), the process proceeds to step S15. In step S15, the script execution unit 51 determines whether or not there is a notification transmitted from the additional script 52 of the request destination. If it is determined that there is no notification from the additional script 52 of the request destination (step S15: No), the processing of the flowchart in FIG. On the other hand, if it is determined that the notification has been received from the additional script 52 of the request destination (step S15: Yes), the process proceeds to step S16.

  In step S16, the script execution unit 51 acquires a notification from the additional script 52. Finally, in step S17, the Web browser 19 transmits a notification from the additional script 52 to the Web application 39, and ends the processing of the flowchart in FIG.

  Next, FIG. 5 shows a configuration that further embodies the configuration shown in FIG. FIG. 5 shows a software configuration for enabling use of an NFC device that is not supported by the Web browser 19. Devices such as a camera unit, a microphone unit, and a GPS (Global Positioning System) are provided as standard in today's smart devices, but the Web browser does not support these devices. The example illustrated in FIG. 5 is an example in which an NFC (Near Field Communication: Near Field Communication) device 62 provided on a smart device (the operation unit 20) can be used from the Web application 39 by the Web browser 19.

  In this case, an NFC control plug-in (NFC control script) 61 for controlling the NFC device 62 is installed in the operation unit 20 in advance, and a script general API 57 defined by the Web browser 19 is supported. Further, as described above, the Web browser 19 is compatible with the general-purpose APIs 55b and 56a, and can be used at any time from the Web application 39.

  Further, the Web application 39 recognizes the specification of data to be transmitted to the NFC control script 61, and can make a request in a predetermined language such as a JAVA (registered trademark) script. Further, registration is performed in advance so that the Web browser 19 can receive a notification via the general-purpose APIs 55a and 55b. Further, it is assumed that the expected movement of the NFC control script 61 differs for each login user. Further, as described above, the NFC control script 61 is installed in a management area different for each user in advance.

  FIG. 6 is a sequence diagram illustrating a flow in which the Web application 39 acquires the connection status of the NFC device 62. First, in step S21, the Web application 39 registers an additional script with which communication is desired in the Web browser 19. In this example, a function of a JAVA (registered trademark) script for notification is registered so as to receive a notification from the NFC control script 61. Even if a plurality of additional scripts (a plurality of NFC control scripts) exist, the Web browser 19 sends only a notification (communication) corresponding to the pre-registered additional script to the Web application 39. Thereby, the load of the notification processing applied to the Web application 39 can be reduced. When acquiring all the notifications, the Web application 39 skips the process of step S21 (it is not necessary to perform the process).

  Next, in step S22, the Web application 39 uses the API to acquire the connection status of the device connected to the NFC device 62. In step S23, the web browser 19 acquires the information of the login user from the main body 10. For example, when the user indicated by “USER002” in FIG. 5 has logged in to the main body 10, the Web browser 19 executes the NFC control script 61 stored in the management area prepared for the user of “USER002”. Determine as the request destination. The Web browser 19 acquires a request to the NFC control script 61 via the general-purpose APIs 55a and 55b, and requests the script execution unit 51 to acquire the connection status of the other party in step S24.

  In step S25, the script execution unit 51 transmits the NFC control script 61 in the execution format to the script general API 57. The NFC control script 61 obtains a request for obtaining the connection status of the other party, and checks the status of the NFC device 62. Then, in step S26, the NFC control script 61 notifies the script execution unit 51 of the destination connection status using the script general-purpose API 57. In step S27, the script execution unit 51 notifies the Web browser 19 of the connection status of the other party using the general-purpose API 56b. Finally, in step S28, the Web browser 19 notifies the Web application 39 of the notification from the NFC control script 61 using a callback function.

  Next, a sequence diagram of FIG. 7 shows a flow of notifying a change in the connection status of the NFC device 62. In the sequence diagram of FIG. 7, in step S31, the NFC control script 61 detects a change in acquisition of the other party connection status, and sends a change notification of the other party connection status to the script execution unit 51 using the script general-purpose API 57. Do.

  In step S32, the script execution unit 51 uses the general-purpose API 56b to notify the Web browser 19 of a change in the connection status of the other party. In step S33, the Web browser 19 determines the NFC control script 61 of the management area that has transmitted the change notification. If the Web browser 19 determines that the notification is a change notification from the NFC control script 61 of the management area corresponding to the currently logged-in user, the Web browser 19 notifies the Web application 39 of the change in the connection status of the other party using the callback function. I do.

  Next, a sequence diagram of FIG. 8 shows a flow of notifying the plurality of Web applications 39a and 39b that the connection status of the NFC device 62 has been changed. In the sequence diagram of FIG. 8, in step S41, the NFC control script 61 detects a change in the acquisition of the connection status of the other party, and notifies the script execution unit 51 of the change in the connection status of the other party using the script general-purpose API 57. .

  Next, in step S42, the script execution unit 51 sends a change notification of the connection status of the other party to the web browser 19 using the general-purpose API 56b. The Web browser 19 determines the NFC control script 61 of the management area that has transmitted the change notification. In step S43, if the Web browser 19 determines that the notification is a change notification from the NFC script 61 of the management area of the currently logged-in user, the Web browser 19 notifies the first Web application 39a of the change using a callback function. . In addition, when the Web browser 19 detects, for example, the second Web application 39b that requires another notification, the Web browser 19 performs a change notification using a callback function as illustrated in step S44.

  As is apparent from the above description, the MFP 1 according to the embodiment is described between the Web application 39 and the Web browser 19 in a language such as a JAVA (registered trademark) script that can be handled by the Web application 39. General-purpose APIs 55a and 55b are provided. Further, general-purpose APIs 56a and 56b described in a language that can be handled by the OS of the operation unit 20 are provided between the Web browser 19 and the script execution unit 51. The script execution unit 51 compiles the installed additional script 52 into an executable format at the time of startup, and makes it executable.

  The Web browser 19 acquires a request from the Web application 39 via the general-purpose APIs 55a and 55b. The Web browser 19 transmits data to the script execution unit 51, which is the request destination notified from the Web application 39. The script execution unit 51 executes the transmitted data using the script general-purpose API 57 of the additional script 52 which is in an executable state. Thus, the function of the additional script 52 written by the user can be added to the Web browser 19 without updating the browser software, and the function of the Web browser 19 can be easily extended.

  The additional script 52 is stored in a storage area provided for each user. The Web browser 19 recognizes the logged-in user by inquiring the logged-in user of the main body 10, and changes the additional script 52 to be called according to the user. As a result, it is possible to prevent the Web application 39 from executing useless processing, and to prevent the inconvenience of reducing the response.

  When a plurality of additional scripts 52 exist, the Web application 39 can use each of the additional scripts 52 at the same time. Further, when there are a plurality of additional scripts 52 and there is an additional script 52 registered in advance for the Web application 39, the Web browser 19 transmits the Web application 39 to the additional script registered in advance. Only give the corresponding notification. Thereby, the load of the notification processing applied to the Web application 39 can be reduced.

  Further, a request from the Web browser 19 can be notified to one or a plurality of Web applications 39. For this reason, the Web application 39 can acquire a request from the Web browser 19 by an event acquisition method instead of acquiring a request by a polling method.

  As described above, the information processing program that enables the functions of the Web browser 19 provided in the operation unit 20 to be extended by installing the functions developed by the user without updating the software is in an installable format or an executable form. The file may be provided in a form of a file in a recording medium readable by a computer device such as a CD-ROM or a flexible disk (FD). Further, the information processing program may be provided by being recorded on a computer-readable recording medium such as a CD-R, a DVD, a Blu-ray Disc (registered trademark), and a semiconductor memory. DVD is an abbreviation for “Digital Versatile Disk”. Further, the information processing program may be provided via a network such as the Internet. Further, the information processing program may be downloaded via a network, installed in the operation unit 20 (or the main body 10), and executed. Further, the information processing program may be provided by being incorporated in a ROM or the like in the device in advance. Further, part or all of the information processing program may be realized by hardware such as an IC (semiconductor integrated circuit).

  The above embodiments have been presented by way of example, and are not intended to limit the scope of the invention. This new embodiment can be implemented in other various forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention.

  For example, MFP 1 in the embodiment is an example of a device to which the present invention is applied. Therefore, the present invention may be applied to devices other than the MFP 1, such as a projector device, a video conference system, or a digital camera device.

  The embodiments and the modifications of the embodiments are included in the scope and the gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

1 MFP (MFP)
10 body 11 CPU
12 ROM
13 RAM
14 HDD
15 Communication I / F
16 Connection I / F
17 Engine section 18 System bus 19 Web browser 20 Operation section 21 CPU
22 ROM
23 RAM
24 Flash memory 25 Communication I / F
26 Connection I / F
27 operation panel 28 system bus 30 communication path 31 CPU
32 ROM
33 RAM
34 HDD
35 Communication I / F
38 System bus 39 Web application 40 Network 51 Script execution unit 52 Additional script 55a General-purpose API
55b General-purpose API
56a General-purpose API
56b General-purpose API
57 Script General API
58a General-purpose API
58b General-purpose API
59 Script General API
61 NFC control script 62 NFC device

JP 2011-141684 A

Claims (13)

A web browser that requests execution of a predetermined process to a web application provided by a server device on a network, or requests execution of a predetermined process to the web application downloaded from the server device; Equipment
A first interface unit for allowing the web application to request the web browser for a connection status of an NFC device connected to the device;
An execution unit that is additionally installed in the device and executes an additional program capable of acquiring a connection status of an NFC device connected to the device;
A second interface unit for notifying the Web browser of the connection status of the NFC device connected to the device, acquired by the additional program,
Information is transmitted / received between the Web application and the Web browser via the first interface unit, and information is transmitted / received between the Web browser and the execution unit via the second interface unit. The device wherein the Web application acquires the connection status of the NFC device acquired by the additional program via the first interface unit and the second interface unit by performing transmission / reception. . The execution unit separately stores a plurality of the additional programs,
The said Web browser performs communication corresponding to the additional program specified from the Web application among the additional programs individually stored in the execution unit, between the Web applications. Equipment described in. The apparatus according to claim 2, wherein the Web application communicates with each of the additional programs. The apparatus according to claim 2, wherein the Web browser transmits information from each of the additional programs to the Web application. Comprising a plurality of the Web applications,
The device according to any one of claims 1 to 4, wherein the Web browser transmits information from the additional program to each of the Web applications. The device according to claim 2, wherein the information includes information for confirming a connection status of a destination of the communication. A web browser that requests execution of a predetermined process to a web application provided by a server device on a network, or requests execution of a predetermined process to the web application downloaded from the server device; Image forming apparatus,
A first interface unit for allowing the Web application to request the Web browser for a connection status of an NFC device connected to the image forming apparatus;
An execution unit that is additionally installed on the image forming apparatus and executes an additional program capable of acquiring a connection status of an NFC device connected to the image forming apparatus;
A second interface unit for notifying the Web browser of the connection status of the NFC device connected to the image forming apparatus, obtained by the additional program,
Information is transmitted / received between the Web application and the Web browser via the first interface unit, and information is transmitted / received between the Web browser and the execution unit via the second interface unit. By transmitting and receiving, the Web application acquires the connection status of the NFC device acquired by the additional program via the first interface unit and the second interface unit. Forming equipment. A main body having a first OS and an image forming function;
An operation unit that includes a second OS and the Web browser and executes the Web application;
The said additional program for the said Web application to acquire the said connection status via the said Web browser is additionally installed in the said operation part operated by the said 2nd OS. Image forming apparatus. The Web browser included in the operation unit including the second OS acquires information of a user who is logged in to the image forming apparatus from the main body having the first OS, and is used by a logged-in user. The image forming apparatus according to claim 8, wherein a possible additional script is determined. The first interface unit is provided as a JAVA (registered trademark) script that can be handled by the Web application executed by the Web browser in an operation unit including the second OS;
The image forming apparatus according to claim 8, wherein the second interface unit is provided in a language executable by the second OS. A web browser that requests execution of a predetermined process to a web application provided by a server device on a network, or requests execution of a predetermined process to the web application downloaded from the server device; Information processing method of the image forming apparatus,
A first interface unit for allowing the Web application to request the Web browser for a connection status of an NFC device connected to the image forming apparatus;
An execution unit that is additionally installed on the image forming apparatus and executes an additional program capable of acquiring a connection status of an NFC device connected to the image forming apparatus;
A second interface unit for notifying the Web browser of the connection status of the NFC device connected to the image forming apparatus, obtained by the additional program,
Information is transmitted / received between the Web application and the Web browser via the first interface unit, and information is transmitted / received between the Web browser and the execution unit via the second interface unit. By transmitting and receiving, the Web application acquires the connection status of the NFC device acquired by the additional program via the first interface unit and the second interface unit. Processing method. A web browser that requests execution of a predetermined process to a web application provided by a server device on a network, or requests execution of a predetermined process to the web application downloaded from the server device; Information processing program for causing a computer of the image forming apparatus to function,
Said computer,
A first interface unit for allowing the Web application to request the Web browser for a connection status of an NFC device connected to the image forming apparatus;
An execution unit that is additionally installed on the image forming apparatus and executes an additional program capable of acquiring a connection status of an NFC device connected to the image forming apparatus;
Causing the Web browser to function as a second interface unit for notifying the connection status of the NFC device connected to the image forming apparatus acquired by the additional program to the web browser;
Information is transmitted / received between the Web application and the Web browser via the first interface unit, and information is transmitted / received between the Web browser and the execution unit via the second interface unit. By transmitting and receiving, the Web application acquires the connection status of the NFC device acquired by the additional program via the first interface unit and the second interface unit. Processing program. Requests execution of predetermined processing to a server device on a network and a Web application provided by the server device, or requests execution of predetermined processing to the Web application downloaded from the server device An information processing system comprising a device having a Web browser
A first interface unit for allowing the web application to request the web browser for a connection status of an NFC device connected to the device;
An execution unit that is additionally installed in the device and executes an additional program capable of acquiring a connection status of an NFC device connected to the device;
A second interface unit for notifying the Web browser of the connection status of the NFC device connected to the device, acquired by the additional program ,
Information is transmitted / received between the Web application and the Web browser via the first interface unit, and information is transmitted / received between the Web browser and the execution unit via the second interface unit. By transmitting and receiving, the Web application acquires the connection status of the NFC device acquired by the additional program via the first interface unit and the second interface unit. Processing system.

Images