JP2021152796A - Method of making push notification to a plurality of applications running on printer - Google Patents

Abstract

To provide a push notification system for solving a problem of, in an MFP where a plurality of applications run in a printer, not knowing which application installed in the printer to notify when push notifications of server-side changes are made to the printer.SOLUTION: A push notification server manages the push data in units of printer and application running on the printer. By including the application identifier in the push data, the printer can identify which application in the printer should receive the push notification.SELECTED DRAWING: Figure 1

Description

How to push notifications to multiple applications running on the printer, and programs

In recent years, the form of cloud computing in which a server provides a service to a client has attracted attention. The main feature of cloud computing is that it uses many computing resources to perform data conversion and data processing in a distributed manner, and requests from many clients are processed in parallel by distributed parallel processing. Vendors that implement Web services on the cloud computing environment that realizes this cloud computing and provide a wide variety of services are becoming crowded. In the development of cloud services, by effectively utilizing the services already provided on the Web and providing new functions, it will be superior in terms of development speed and development cost.

Even in the cloud service linked with the MFP (MultiFactionPrinter), the cloud service has been developed for each function, and the application on the MFP has come to be configured to utilize the cloud service necessary for realizing the function.

However, if a plurality of applications on the MFP individually link with the cloud service, the development cost will be different and the MFP resources (communication resources, memory, CPU, etc.) will be consumed. Therefore, it is conceivable to use a common mechanism for push notifications that are common to a plurality of applications, but there is a problem that it is not clear to which application the push notifications should be notified.

Conventionally, a method of displaying various server information on a printer screen by push-notifying only a server address (URL) has been disclosed (see, for example, Patent Document 1).

JP-A-2007-886655

In the conventional technology, it is possible to flexibly cooperate with the server by push-notifying only the address (URL) of the server, but it is not possible to determine which application in the printer needs the address (URL).

In an MFP (Multifunction Printer) in which a plurality of applications run in a printer, there is a problem that even if a server-side change is notified to the printer by push notification, it is not possible to notify which application installed in the printer.

An object of the present invention is to provide a push notification system that allows a printer to specify to which application in the printer the push notification should be transmitted.

In order to achieve the above object, the present invention is a push notification system in which a plurality of applications run on a printer and manage push notifications to those applications, and the push notification server operates on the printer and the printer. It has a means for accepting updates of push data for each application and holding push data for each of the printer and the application running on the printer, and has a device ID which is an identifier of the printer and an application identifier which operates on the printer. It is characterized in that a push notification is performed together with the push data.

According to the present invention, the push notification server manages push data for each printer and each application running on the printer. By including the application identifier in the push data, the printer can identify which application in the printer to send the push notification to.

The system block diagram which concerns on embodiment of this invention. Hardware configuration diagram of each device. Hardware configuration diagram of each device. Software configuration diagram. Software configuration diagram. Software configuration diagram. Software configuration diagram. The figure which shows the table structure managed by the push notification server. The figure which shows the table structure managed by the device management server. The figure which shows the table structure managed by the backup application server. The figure which shows the table structure managed by the device management application. The figure which shows the table structure managed by the backup application. The figure which shows the backup interval acquisition flow at the time of starting a backup application. Diagram showing the push notification flow from the backup application server to the backup application.

Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings.

[Embodiment 1]
<System configuration>
FIG. 1 is a diagram showing an overall configuration of a form system according to an embodiment of the present invention.

In FIG. 1, the printer 102 can access the Internet 100 via the local network 101 and access the servers 103 to 105. The push notification server 103 is a server that controls push notifications to the printer 102. The push notification server 103 receives a push notification request from the device management server 104 and performs a push notification for the printer 102. The device management server 104 is a server that manages the printer 102. The backup application 105 is a server that manages backups of data and settings in the printer 102.

Here, each of the servers 103 to 105 is published on the Internet as a cloud service redundant with a plurality of servers, but in the present embodiment, each server is configured as one for simplification of the explanation.

<Hardware configuration of printer 102>
FIG. 2a is a hardware configuration diagram of the printer 102. Each component of the hardware is connected to the system bus 200.

Reference numeral 201 denotes a CPU that controls the entire device, and controls access to various devices connected to the system bus 200 in an integrated manner. This control is based on a control program or the like stored in the ROM 202 or a control program or resource data (resource information) stored in the external memory 206 connected via the disk controller (DKC205). Reference numeral 203 denotes a RAM that functions as a main memory, a work area, or the like of the CPU 201, and is configured so that the memory capacity can be expanded by an optional RAM connected to an expansion port (not shown). Reference numeral 210 denotes an external storage means that functions as a large-capacity memory, and stores 330 to 337 programs described later according to the present invention.

Reference numeral 209 is an operation panel (operation unit), which displays a screen and receives a user's operation instruction via the screen. In addition, buttons for setting the operation mode of the printer 102, displaying the operating status of the printer 102, specifying copying, and the like, and a display unit such as a liquid crystal panel are also arranged. Reference numeral 204 denotes a network interface card (NIC), which exchanges data with an external device via the interface 204. The print engine 208 shown in this figure utilizes a known printing technique, and suitable implementation systems include, for example, an electrophotographic method (laser beam method), an inkjet method, a sublimation method (thermal transfer) method, and the like. .. The raster controller of 207 is a controller that converts print data in PDL language / PDF language into image data. The device I / F of 211 is a connection I / F with an external device that can be connected by USB or the like.

<Server hardware configuration>
FIG. 2b is a diagram showing an example of the hardware configuration of each server of 103 to 105.

Unless otherwise specified, the present invention can be applied to a single device or a system composed of a plurality of devices as long as the functions of the present invention can be executed. Further, unless otherwise specified, the present invention can be applied to a system in which a connection is made via a network such as LAN or WAN and processing is performed as long as the function of the present invention can be executed. In this embodiment, it is assumed that each component is connected by the system bus 219.

Reference numeral 220 denotes a CPU which is a control device of the information processing device, and executes an application program, a print driver program, an operating system, and a mobile print system program of the present invention stored in the storage device 226. Further, the CPU 220 controls the RAM 222 to temporarily store information, files, and the like necessary for program execution. Further, the CPU 220 opens various registered windows based on a command instructed by a mouse cursor or the like (not shown) on the display 227, and executes various data processing.

Reference numeral 221 is a ROM which is a storage means, and internally stores various data such as a program such as a basic I / O program, font data used in document processing, and template data. The 222 is a RAM that is a temporary storage means, and functions as a main memory, a work area, or the like of the CPU 220. Reference numeral 224 is a display control unit, which controls information output on the display 227. Reference numeral 225 is an input control unit, which controls information input from the keyboard 228, and the information processing device exchanges data with an external device via the input control unit 225. 226 is one of the external storage means, which is a storage device that functions as a large-capacity memory, and stores an application program, a print driver program, an OS, and the like. Reference numeral 228 is a keyboard which is an instruction input means, and is for a user to input an instruction or the like to each server. Reference numeral 227 is a display which is a display means, and displays a command or the like input from the keyboard 228.

<Software configuration of push notification server 103>
FIG. 3a is a software configuration diagram of the push notification server 103. Each software module is stored in the storage device 226 shown in FIG. 2, and is loaded into the RAM 222 by the CPU 220 and executed as described above.

The MQTT broker 300 provides various interfaces of the push notification server 103 by the MQTT (Message Queue Telemetry Transport) protocol, and verifies the validity of the received information. Since the MQTT protocol can reduce the transfer data size, it is suitable for the purpose of continuously transmitting and receiving small data.

The Web server 301 provides various interfaces of the push notification server 103 by the HTTP (Hypertext Transfer Protocol) protocol, and verifies the validity of the received information. The HTTP protocol is a protocol that is used as standard on the Web, and is suitable for cooperation between servers and cooperation between Web Browser and servers.

Although the protocol is different between the MQTT broker 300 and the Web server 301, the functions provided by the push notification server 103 in various interfaces are the same and can be selected by the client.

The topic information management unit 302 manages the client information 400, the subscription information 410, and the push notification information 420 described with reference to FIG. 4, and stores them in the storage 303. Further, the topic information management unit 302 performs a push notification to the client via the MQTT broker 300 and the Web server 301 based on the information to be managed.

<Software configuration of device management server 104>
FIG. 3b is a software configuration diagram of the device management server 104. Each software module is stored in the storage device 226 shown in FIG. 2, and is loaded into the RAM 222 by the CPU 220 and executed as described above.

Reference numeral 310 denotes a Web server, which provides various interfaces of the device management server 104 by the HTTP protocol and verifies the validity of the received information. Reference numeral 311 is a device information management unit, which manages the device information 500 described with reference to FIG. Reference numeral 313 is storage, and information held by the device management server 104 is stored.

<Software configuration of backup application server 105>
FIG. 3c is a software configuration diagram of the backup application server 105. Each software module is stored in the storage device 226 shown in FIG. 2, and is loaded into the RAM 222 by the CPU 220 and executed as described above.

Reference numeral 320 denotes a Web server, which provides various interfaces of the backup application server 105 with the HTTP protocol and verifies the validity of the received information. Reference numeral 321 is a backup information management unit, which manages the backup application information 600 and the backup information 610 described with reference to FIG. Reference numeral 322 denotes storage, which stores information held by the backup application server 105.

<Software configuration of printer 102>
FIG. 3d is a software configuration diagram of the printer 102.

The printer 102 controls each application by the CPU 201 executing the OS stored in the ROM 202 or the external memory 206. Here, 330 is the OS, and a real-time OS is generally used, but nowadays, a general-purpose OS such as Linux (registered trademark) may be used. Next, 331 is a virtual machine, for example Java® VM is well known. The virtual machine 331 is a virtual application execution environment that operates as an application controlled by the OS.

The application management framework 332 has a function of managing the life cycle of the managed application running on the application execution environment provided by the virtual machine 331. It also has an I / F that controls the life cycle of applications and an I / F publishing function that mediates processing requests between applications. The life cycle shall indicate the state of the application including installation, start, stop, and uninstallation of the application. The application management framework 332 in this embodiment will be described as OSGi® defined by the OSGi (Open Services Gateway initiative) Alliance.

The application management application 333, the device management application 334, and the backup application 335 are applications that operate in the application execution environment provided by the virtual machine 331. These applications are identified by the Application ID and are life cycle managed by the application management framework 332. 333 is an application management application that receives and executes various applications from users and start requests via a control I / F for life cycle management published by the application management framework 332.

Here, the device management application 334 and the backup application 335 may be included in the printer 102 by default. It may also be installed later via the application management application 333 and the application management framework 332.

<Data managed by push notification server 103>
FIG. 4 is a data table stored in the external memory by the push notification server 103. These data tables may be configured to be stored in another server configured to be communicable via the Internet 100 or the local network 101 instead of the external memory of the push notification server 103. The data table held by the push notification server 103 includes client information 400, subscription information 410, and push notification information 420.

In the client information 400, the push notification server 103 manages a client for push notification. Reference numeral 401 denotes a client ID, which is an identifier that uniquely identifies the client to be pushed by the push notification server 103.

The subscription information 410 is recorded by the push notification server 103 when the push data subscription request is received. Reference numeral 411 is a client ID, which is an identifier uniquely identifying the client to which the push notification server 103 has subscribed to push data. The subscription topic name 412 is the topic name that the client wants to receive the push notification specified in the push data subscription request. A wildcard (*) can be specified for the subscription topic name 402.

The push notification information 420 manages the data to be pushed by the push notification server 103. 421 is an identifier that uniquely identifies the push data, and is stored in the format of (device ID_application ID). 422 is an example of push data related to push data ID 411. The status information in the push data example 422 is composed of a message and a reported, and the message stores the setting value to be changed, and the reported stores the setting value for which the change is accepted. The metadata information is additional data of the status information and stores the update time (timestamp) of the set value.

When the push data 422 is changed, the push notification server 103 identifies the subscription topic name 412 that matches the push data ID 421 from the subscription information 410, and pushes the push data to the client ID 411.

<Data of device management server 104>
FIG. 5 is a data table stored in the external memory by the device management server 104. These data tables may be configured to be stored in another server configured to be communicable via the Internet 100 or the local network 101 instead of the external memory of the device management server 104. The data table held by the device management server 104 includes device information 500.

The device ID 501 in the device information 500 is an identifier that the device management server 104 uniquely identifies the device.

<Data of backup application server 105>
FIG. 6 is a data table stored in the external memory by the backup application server 105. These data tables may be configured to be stored in another server configured to be communicable via the Internet 100 or the local network 101 instead of the external memory of the backup application server 105.

The data table held by the backup application server 105 includes backup application information 600 and backup information 610. In the backup application information 600, the application ID of the backup application 335 that accesses the backup application server 105 is registered. In this embodiment, Application ID2, which is an application ID of backup application 335, is registered.

The device ID 611, the backup interval 612, the time stamp 613, and the backup data file path 614 are registered in the backup information 610. The device ID 611 is an identifier of the device (printer 102) that backed up. The backup interval 612 is an interval of time during which the backup application 335 performs the backup process. The time stamp 613 is the last update time of the backup interval 612. The backup data file path is a storage location for the backup data file received by the backup application server 105 from the backup application 335.

<Data of device management application 334>
FIG. 7 is a data table stored in the external memory by the device management application 334. These data tables may be configured to be stored in another server configured to be communicable via the Internet 100 or the local network 101 instead of the external memory of the device management application 334.

The data table held by the device management application 334 includes device management application information 700, subscription information 710, and push notification information 720. The device management application information 700 is composed of the application ID 701 and the client ID 702. In the present embodiment, the application ID 701 of the device management application 334 is the Application ID 1. The client ID 702 is issued by the push notification server 103.

The device management application 334 receives the client ID 401 by executing the client registration in the push notification server 103 when the application is started.

The subscription information 710 is recorded by the device management application 334 when the push data subscription request is received. Reference numeral 711 is an application ID, which is an identifier that uniquely identifies the application in the printer 102 to which the device management application 334 has subscribed to push data. The push notification information 720 manages the data to be push-notified by the device management application 334. 721 is an identifier that uniquely identifies the push data, and is stored in the format of (device ID_application ID). 722 is an example of a push data file related to push data ID 721. The contents of the push data file example 722 are the same as those of the push data example 422.

<Data of backup application 335>
FIG. 8 is a data table stored in the external memory by the backup application 335. These data tables may be configured to be stored in another server configured to be communicable via the Internet 100 or the local network 101 instead of the external memory of the backup application 335. The data table held by the backup application 335 includes backup application information 800 and backup information 810.

The application ID 801 of the backup application information 800 holds the application ID of the backup application 335. In the present embodiment, the application ID 801 of the backup application 335 is the Application ID 2. The backup information 810 is a backup interval 811 of the time when the backup application 335 executes the backup process, and a time stamp 812 which is the last update time of the backup interval 811.

<Backup interval acquisition flow when backup application 335 is started>
FIG. 9 is a flow of acquiring the latest backup interval from the device management application 334 when the backup application 335 is started.

In step S9.1, the backup application 335 is started. In step S9.2, the backup application 335 requests the device management application 334 to acquire push data. In step S9.3, the device management application 334 identifies the application ID for which the push data acquisition request has been requested. In the present embodiment, the Application ID 2 which is the application ID of the backup application 335 can be specified.

In step S9.4, the device management application 334 identifies the push data from the push notification information. The format of the push data ID 721 is (device ID_application ID), and the push data ID 721 can be specified by the device ID of the printer 102 on which the device management application 334 operates and the application ID specified in step S9.3.

In step S9.5, the device management application 334 responds to the backup application 335 with the push data associated with the push data ID 721 identified in step S9.4. If the push data ID 721 cannot be identified in step S9.4, the device management application 334 responds with empty data in step S9.5. In this embodiment, the push data includes a backup interval (backup_interval).

In step S9.6, when the backup application 335 receives the push data, the backup information 810 is updated by the backup_interval of the desired included in the push data. Further, the backup application 335 updates the time stamp 812 (timestamp) with the metadata of backup_interval included in the push data.

In step S9.7, the backup application 335 sends a push notification to the device management application 334. The data push-notified by the backup application 335 is obtained by updating the back-up_interval of the supported push data received in step S9.5 at the backup interval 811. It also updates the metadata timestamp.

In step S9.8, the device management application 334 updates the push data file 722 with the push data received in step S9.7. In step S9.9, the backup application 335 requests the device management application 334 to subscribe to push data. In step S9.10, the device management application 334 identifies the application ID of the backup application 335. In step S9.11, the device management application 334 registers the application ID specified in step S9.10 in the subscription information 710.

<Push notification flow from backup application server 105 to backup application 335>
FIG. 10 is a flow in which the backup application server 105 receives the backup interval update and transmits the update information to the backup application 335 by push notification.

In step S10.1, the backup application server 105 accepts a change in the backup interval of the specific printer 102 (device ID). In step S10.2., The backup application server 105 makes a push notification request to the device management server 104. In the push notification request, the device ID of step S10.1, the backup interval, and the application ID 601 of the backup application information 600 are specified.

In step S10.3., The device management server 104 requests the push notification server 103 to update the push data. In the push data update request, the push data ID (device ID_application ID) created from the device ID and application ID received in step S10.3, and the backup interval are specified.

In step S10.4, the push notification server 103 identifies the push data 422 from the push notification information 420 using the push data ID (device ID_application ID) received in step S10.3. Then, the push notification server 103 updates the backup_interval of the message of the push data 422 to the backup interval received in step S10.3.

In step S10.5, the push notification server 103 confirms from the subscription information 410 whether or not there is a subscription topic name 412 corresponding to the push data ID (device ID_application ID) received in step S10.3. If the corresponding subscription topic name 412 does not exist, the processing after step S10.6 is not performed. If there is a corresponding subscription topic name 412, the push notification in step S10.6 or later is performed to the client ID 411.

In step S10.6, the push notification server 103 performs push notification to the client ID 411 specified in step S10.5. In this embodiment, it is the device management application 334 that receives the push notification. For the push notification, the push data ID 421 (device ID_application ID) updated in step S10.4 and the push data 422 are specified.

In step S10.7, the device management application 334 updates the push notification information 720 with the push data ID (device ID_application ID) and the push data received in step S10.6.

Then, the device management application 334 identifies the application ID from the push data ID (device ID_application ID) received in step S10.6, and confirms whether the application ID is registered in the subscription information 710. If the application ID is not registered in the subscription information 710, the device management application 334 does not perform the processing after step S10.8. When the application ID is registered in the subscription information 710, the device management application 334 performs the processes after step S10.8.

In step S10.8, the device management application 334 pushes the push data to the application ID specified in step S10.7. In this embodiment, the backup application 335 is notified by push notification.

In step S10.9, the backup application 335 stores the backup_interval of the desired in the push data received in the push notification of step S10.8 in the backup information 810. Further, the backup application 335 updates the time stamp 812 (timestamp) with the metadata of backup_interval included in the push data.

In step S10.10, the backup application 335 sends a push notification to the device management application 334. The data push-notified by the backup application 335 is obtained by updating the back-up_interval of the supported push data received in step S10.8 at the backup interval 811. It also updates the metadata timestamp.

In step S10.11, the device management application 334 updates the push data file 722 with the push data received in step S10.10. The push data ID 721 (device ID_application ID) is generated from the device ID of the printer 102 on which the device management application 334 operates and the application ID of the backup application 335 that was push-notified in step S10.10.

In step S10.12, the device management application 334 makes a push data update request to the push notification server 103. In the push data update request, the push data ID (device ID_application ID) updated in step S10.11 and the push data are specified. In step S10.13, the push notification server 103 updates the push notification information 420 with the push data ID (device ID_application ID) and the push data received in the push data update request in step S10.12.

As described above, the push notification server 103 manages the push data for each printer 102 and the application operating on the printer, so that the application for push notification can be specified.

Further, since the device management application 334 on the printer 102 caches the push data in a file, other applications on the printer 102 can acquire the push data regardless of the network connection state.

102 Printer 103 Push Notification Server 104 Device Management Server 105 Backup Application Server 334 Device Management Application 335 Backup Application

Claims (3)

In a push notification system where multiple applications run on the printer and manage push notifications to those applications.
The push notification server has a means for accepting updates of push data for each of the printer and the application running on the printer, and holding the push data for each of the printer and the application running on the printer.
A push notification system characterized in that a device ID, which is an identifier of the printer, and an application identifier operating on the printer are push-notified together with the push data. The device management application has a means for receiving push notification subscription requests from other applications running on the printer and managing push notification subscription information for each application.
The push notification system according to claim 1, wherein the device management application identifies an application based on an application identifier included in the push notification from the push notification server, and performs push notification to the specified application. The push notification according to claim 1, wherein the device management application receives a push data acquisition request from another application operating on the printer and responds with cache information of push data included in the device management application. system.

Images