Network devices, methods, and programs

Abstract

This system allows users to become aware of the presence of a network device when they approach it, without requiring them to configure their device settings for network device notifications on each user's device. [Solution] The network device includes a notification means that, when the device is in a state that satisfies predetermined state conditions, causes a push notification to a user terminal that has installed software as a progressive web application for providing information about the state, and a re-notification means that, after a push notification has been sent to the user terminal by the notification means, causes another push notification to the user terminal when the user terminal is located within a range that satisfies predetermined range conditions relative to the device.

Description

Technical Field

[0001] The present invention relates to network devices, methods, and programs.

Background Art

[0002] Conventionally, a network device that notifies a user terminal, which is a terminal used by a user, of information regarding the device itself is known. Also, a technique for notifying a user terminal according to the user's location is known. Patent Document 1 discloses a technique in which an information processing device as a network device determines whether to notify a user of requirements according to a change in the user's location information.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, when a notification is made from a network device to a user terminal, the user may forget the requirements notified on the user terminal. In this case, for example, even when a notification is made from a network device to a user terminal while the user is away from the network device, when the user approaches the network device, the user may not recognize the existence of this network device. Also, for example, a notification from a network device to a user terminal may be realized by installing application software such as a native app on the user terminal. In this case, since it is necessary to set the notification from the network device for each user terminal on the user terminal, the settings regarding the notification from the network device to the user terminal are complicated. The present invention aims to allow users to become aware of the presence of a network device when they approach it, without requiring each user terminal to configure settings for notifications from the network device. [Means for solving the problem]

[0005] To solve the above problems, the present invention provides a network device comprising: a notification means that, when the device satisfies predetermined state conditions, causes a push notification to a user terminal on which software as a progressive web application for providing information about the state is installed; and a re-notification means that, after the push notification has been sent to the user terminal by the notification means, causes a push notification to be sent to the user terminal again when the user terminal is located within a range that satisfies predetermined range conditions relative to the device. [Effects of the Invention]

[0006] According to the present invention, it is possible to make a user aware of the presence of a network device when they approach it, without requiring each user terminal to configure settings for notifications from network devices. [Brief explanation of the drawing]

[0007] [Figure 1] This is an overall diagram of the function provision system. [Figure 2] (A) is a diagram showing the hardware configuration of the equipment, (B) is a diagram showing the hardware configuration of the user terminal, and (C) is a diagram showing the hardware configuration of the server device. [Figure 3] (A) is a diagram showing the functional configuration of the equipment, (B) is a diagram showing the functional configuration of the user terminal, and (C) is a diagram showing the functional configuration of the server device. [Figure 4] This is a diagram showing the reception screen. [Figure 5] This is a sequence diagram showing the flow of processing performed by the device, the user terminal, and the server device. [Figure 6] This is a flowchart illustrating the re-notification process. [Figure 7] This is a diagram showing the screen. [Figure 8] This is a diagram showing the screen. [Figure 9] (A) is a diagram showing the initial notification image, and (B) is a diagram showing the second notification image. [Figure 10] (A) is a diagram showing the hardware configuration of the transmitter, and (B) is a diagram showing the functional configuration of the transmitter. [Figure 11] This is a sequence diagram showing the flow of processing performed by the device, user terminal, server device, and transmitter. [Figure 12] (A) is a diagram showing the re-notification screen, and (B) is a diagram showing the group screen. [Figure 13] This is a diagram showing the top screen. [Modes for carrying out the invention]

[0008] (First Embodiment) Embodiments of the present invention will be described below with reference to the drawings. Figure 1 is an overall configuration diagram of the function provision system 1. The function provision system 1 is a system that provides at least a part of the functions of a network device, which is a device capable of communication, to a user's terminal connected to the network device. In this embodiment, the function of the network device provided to the user's terminal is the function of monitoring the status of the network device. The device provides the user's terminal with the information to be monitored by notifying the user's terminal. Examples of network devices include image processing devices such as multifunction peripherals (MFPs). However, the device used as a network device may be a different device from an image processing device, such as a network router, surveillance camera, digital medical device, automobile, delivery box or locker, etc. The function provision system 1 comprises a device 101, a user terminal 102 which is a terminal used by the user, and a server device 103 used for notifications from the device 101 to the user terminal 102. The device 101, the user terminal 102, and the server device 103 are connected via a network 100.

[0009] Device 101, as an example of a network device, is the device whose status is monitored. Hereinafter, we assume that device 101 is a multifunction printer with functions such as printing, faxing, copying, scanning, and data transmission. Device 101 provides a function to the user terminal 102 that allows it to check the status of device 101, perform job operations, and configure various settings. This function is called a remote user interface (hereinafter referred to as remote UI). Here, device 101 is equipped with a web server (not shown) that can provide the remote UI internally. In this embodiment, the mechanism for providing functions from device 101 is implemented using Progressive Web Apps (PWAs). A PWA is a technology that allows web applications on a website to be used as if they were applications running on the user terminal 102. A PWA is application software that can be downloaded and installed via a web browser, built using common web technologies such as HTML, CSS, JavaScript, and Web Assembly. Furthermore, with PWAs, users do not need to download and install them on the user terminal 102 from an application store provided by, for example, an operating system (OS) vendor. For example, if a website is PWA-compatible, a user can access that website using the browser on the user terminal 102 and download the PWA to use it. The content of the PWA can also be freely designed by the website provider. In addition, by utilizing the Service Worker function, PWAs can also realize push notifications to the user terminal 102 and the display of icons on the home screen from an application server built by the website provider, etc. This push notification is implemented via a push server provided by the browser vendor, utilizing the specified APIs supported by the user terminal 102's OS and browser. A Service Worker is a script that runs as a background process.

[0010] In this embodiment, when a change occurs in the state of the monitored object, device 101 instructs the server device 103 to send a push notification to the user terminal 102, thereby causing the user terminal 102 to receive the push notification. Furthermore, after sending the push notification, if the user terminal 102 approaches, device 101 will send another push notification to the approaching user terminal 102. In the illustrated example, three devices 101 are provided in the function providing system 1, but it is not limited thereto. The number of devices 101 provided in the function providing system 1 may be any number as long as it is one or more.

[0011] The user terminal 102 receives notifications from the device 101. More specifically, when the user terminal 102 detects its approach to the device 101, the user terminal 102 requests a notification from the approached device 101 and receives the notification from the device 101 in response to the request. Examples of the information terminal 101 include computer devices such as a PC, a smartphone, and a tablet terminal. A web browser is installed in the user terminal 102. The user terminal 102 connects to the URL of the remote UI using the web browser by, for example, the user entering the IP address of the device 101 into the web browser. Also, the user terminal 102 installs a PWA corresponding to the website (terminal site) connected via the web browser. In the illustrated example, only one user terminal 102 is provided in the function providing system 1, but it is not limited thereto. The number of user terminals 102 provided in the function providing system 1 may be any number as long as it is one or more. Also, a user terminal 102 may be provided for each user in the function providing system 1.

[0012] Hereinafter, it is assumed that the device 101 transmits a beacon signal around, and the approach to the device 101 is detected by the user terminal 102 when the beacon signal transmitted from the device 101 is received by the user terminal 102.

[0013] The server device 103 is a server device 103 prepared for the browser vendor to provide a push service by PWA. When the server device 103 receives an instruction for a push notification from the device 101, the server device 103 realizes a push notification from the device 101 to the user terminal 102 by sending a push notification to the user terminal 102 that is the target of the instruction. In addition, the server device 103 manages the position of the device 101 and notifies the user terminal 102 of the position of the device 101. In this embodiment, push notification to the user terminal 102 and notification of the position of the device 101 to the user terminal 102 are performed by a single server device 103, but it is not limited to this. Push notification to the user terminal 102 and notification of the position of the device 101 to the user terminal 102 may be performed by different server devices.

[0014] The network 100 is not particularly limited as long as data can be transmitted and received. Examples of the network 100 include the Internet, LAN (Local Area Network), WAN (Wide Area Network), telephone line, dedicated digital line, ATM or frame relay line, cable TV line, wireless line for data broadcasting, and the like. Also, the communication line used for data transmission and reception may be wired or wireless. Also, the network 100 connecting the device 101 and the user terminal 102 and the network 100 connecting the device 101 and the user terminal 102 and the server device 103 may be the same network or different networks.

[0015] FIG. 2(A) is a diagram showing the hardware configuration of the device 101. The device 101 includes a CPU 201, a ROM 202, a RAM 203, a storage device 204, a network I / F 205, a device control 207, a printing unit 208, an input / output I / F 209, and an input / output device 210. The CPU 201, the ROM 202, the RAM 203, the storage device 204, the network I / F 205, the device control 207, the input / output I / F 209, and the input / output device 210 are connected via a bus 206, respectively. The CPU 201 carries the program stored in the ROM 202 and controls the entire device 101. The RAM 203 functions as the CPU 201's memory and work area, storing information indicating the detected state of the device 101, various counter information, wear status information of consumable parts, various logs, etc. The network I / F 205 communicates with the user terminal 102 and the server device 103. The device control 207 controls the printing unit 208 according to print requests, etc. The CPU 201, together with the ROM 202 and RAM 203, performs program execution processing and also processes the recording of image data on a recording medium such as the storage device 204. The storage device 204 functions as an external storage device and stores image data, etc. Alternatively, the storage device 204 may store the above-mentioned information as if it were stored in the RAM 203, instead of the RAM 203. The input / output device 210 receives information input from the user (scan, button input, etc.) and outputs information. An example of the input / output device 210 is a device such as a touch panel consisting of an operation unit receiving unit and a display unit.

[0016] Figure 2(B) shows the hardware configuration of user terminal 102. User terminal 102 has a CPU 301, RAM 302, ROM 303, storage device 304, network interface 305, input / output interface 308, and input / output device 308. The CPU 301, RAM 302, ROM 303, storage device 304, network interface 305, and input / output interface 308 are each connected via bus 306. The CPU 301 executes programs stored in the ROM 303 and controls the entire user terminal 102. The CPU 301 also performs program execution processing together with the RAM 302 and ROM 303. The RAM 302 functions as the memory and work area of ​​the CPU 301. The storage device 304 functions as an external storage device and stores various information. The storage device 304 also stores various information in place of the RAM 302. The network interface 305 communicates with the device 101 and the server device 103. The input / output device 308 is a device such as a touch panel consisting of an operation input / output input / output interface 307 that inputs and outputs information.

[0017] Figure 2(C) shows the hardware configuration of the server device 103. The server device 103 has a CPU 401, RAM 402, ROM 403, storage device 404, and network I / F 405. The CPU 401, RAM 402, ROM 403, storage device 404, and network I / F 405 are each connected via a bus 406. The CPU 401 executes programs stored in the ROM 403 and controls the entire server device 103. The CPU 401 also performs program execution processing together with the RAM 402 and ROM 403. The RAM 402 functions as the memory and work area of ​​the CPU 401. The storage device 404 functions as an external storage device and stores various information. The storage device 404 also stores various information in place of the RAM 402. The network interface 405 communicates with the device 101 and the user terminal 102.

[0018] Figure 3(A) shows the functional configuration of device 101. Device 101 includes a transmitting / receiving unit 501, a device management unit 502, an operation reception unit 503, a job execution unit 504, a detection unit 505, a location management unit 506, and a control unit 507. The transmitting / receiving unit 501 communicates with external devices such as the user terminal 102 and the server device 103 to send and receive information to and from these external devices. Protocols such as SMTP, HTTP / HTTPS, SMNP, FTP, and SMB are used for sending and receiving information. The transmitting / receiving unit 501 also emits beacon signals to its surroundings.

[0019] The device management unit 502 manages information about device 101 in the ROM 202, RAM 203, and storage device 204. Information about device 101 managed by the device management unit 502 includes identification information of device 101, firmware version, network information such as IP address, various counter information, and wear status information of consumable parts. The beacon signal transmitted to the transmitting / receiving unit 501 includes the identification information of device 101 managed by the device management unit 502. Counter information includes information indicating the value detected by a sensor (not shown) as the number of pages printed by device 101. Wear status information includes information indicating the wear status of components constituting device 101, and information indicating the remaining toner amount in device 101. Furthermore, information about device 101 managed by the device management unit 502 may also include the operation history of device 101 (job execution history, operation history, etc.) or history information representing various abnormal states of device 101 (error history, alarm history, etc.).

[0020] The job execution unit 503 controls the equipment 101 during job execution, such as print jobs and scan jobs. For example, when executing a print job, the job execution unit 503 generates and outputs print data to be passed to the printing unit 208. The operation reception unit 504 receives operations from the user's user terminal 102. The detection unit 505 detects the occurrence of a predetermined state of the device 101. Examples of predetermined states of the device 101 include abnormal states accompanied by errors or alarms. Examples of abnormal states accompanied by errors or alarms include states where a highly urgent error such as a hard disk error has occurred, states where a paper jam has occurred, states where a warning alarm indicating low toner level has been issued, and states where the toner is empty. Alternatively, a predetermined state of the device 101 may include states where the toner bottle has been replaced or where the firmware of the device 101 has been updated. When the detection unit 505 detects the occurrence of a predetermined state of the device 101, it notifies the control unit 507 of information indicating the detected state. The detection unit 505 also detects the resolution of a predetermined state in the device 101 after it has entered that predetermined state. The states of the device 101 detected by the detection unit 505, such as predetermined states and states where predetermined states have been resolved, are managed by the device management unit 502 as history information of the state of the device 101. In the following, the state of a predetermined device 101 detected by the detection unit 505, which is to be notified to the control unit 507 by the detection unit 505, may be referred to as the "detection state."

[0021] The location management unit 506 manages location information indicating the location of the device 101. This location information includes information indicating the point where the device 101 is located, and information indicating the building, floor, room, etc., where the device 101 is installed. The location information may be generated by a user inputting information to the device 101. Furthermore, if the device 101 has a detection means such as GPS for detecting its location, the detection means may generate the location information. The location management unit 506 also manages the location information in association with identification information that identifies the device 101. The location management unit 506 transmits the associated location information and identification information to the server device 103.

[0022] As an example of a control means, the control unit 507 causes a push notification to the user terminal 102. Specifically, when the control unit 507 is notified by the detection unit 505 that a detection state has occurred, it sends an instruction to the server device 103 to send a push notification to the user terminal 102, along with information identifying the user terminal 102 that is the target of the push notification, thereby causing the push notification to be sent. Therefore, the control unit 507 can also be considered as a notification means that causes a push notification to be sent to the user terminal 102. Furthermore, the control unit 507 causes the user terminal 102 to send another push notification. After the control unit 507 sends the initial push notification to the user terminal 102 upon receiving notification from the detection unit 505 that a detection state has occurred, the control unit 507 sends another push notification to the user terminal 102 when the user terminal 102 approaches the device 101. Therefore, the control unit 507 can also be seen as a means of sending a second push notification to the user terminal 102.

[0023] Furthermore, the control unit 507 functions as an application server and provides web content in response to requests from the user terminal 102. The web content includes information for display on a web browser on the user terminal 102, as well as Service Workers and other similar elements. Furthermore, the control unit 507 associates the location information of the device 101, which is managed by the location management unit 506, with instruction information indicating instructions for a user terminal 102 approaching the device 101 and identification information of the device 101, and transmits it to the server device 103. In this embodiment, the instruction indicated in the instruction information is an instruction to request the device 101 to send a push notification from the device 101 to the user terminal 102. In addition, the control unit 507 includes information necessary for communication with the device 101, such as endpoint information, in the instruction information in order to have the device that acquired the instruction information communicate with the device 101. Note that the instruction indicated in the instruction information is not limited to an instruction to request a push notification from the device 101. The instruction indicated in the instruction information may be an instruction to output information to the user terminal 102, etc.

[0024] The communication unit 501 of device 101 is implemented by the network interface 205. The device management unit 502, job execution unit 503, detection unit 505, location management unit 506, and control unit 507 of device 101 are implemented by the CPU 201 loading a program stored in the ROM 202 or storage device 204 into the RAM 203 and executing it. The operation reception unit 504 of device 101 is implemented by the input / output device 210.

[0025] Figure 3(B) shows the functional configuration of the server device 103. The server device 103 includes a transmitting / receiving unit 511, a management unit 512, and a control unit 513. The transmitting / receiving unit 511 transmits and receives information to and from an external device. The management unit 512 manages the device 101 and the user terminal 102. When the management unit 512 obtains location information, identification information, and instruction information of the device 101 from the control unit 507 of the device 101, it manages the location identified from the obtained location information as the location of the device 101, and also manages each of the obtained pieces of information. Furthermore, when the management unit 512 receives a request from the user terminal 102 to register as a target for receiving push notifications from the device 101, it manages the requested user terminal 102 as a target for push notifications. The control unit 513 transmits the location information and instruction information of device 101, obtained from the control unit 507 of device 101, to the user terminal 102 that has received the beacon signal from device 101. In addition, when the control unit 513 receives an instruction for push notification from the control unit 507 of device 101, it sends a push notification to the user terminal 102 that is the target of the instruction.

[0026] Figure 3(C) shows the functional configuration of the user terminal 102. The user terminal 102 includes a transmitting / receiving unit 521, an operation reception unit 522, a location management unit 523, and a control unit 524. The transmitting / receiving unit 521 transmits and receives information to and from an external device. The operation reception unit 522 receives operations from the user's user terminal 102. The location management unit 523 manages the location of the device 101. When the location management unit 523 receives a beacon signal from the device 101 at the transmitting / receiving unit 521, it transmits the identification information of the device 101 contained in the received beacon signal to the control unit 513 of the server device 103. The location management unit 523 then receives location information and instruction information associated with the transmitted identification information from the control unit 513, and manages the location identified from the received location information as the location of the device 101.

[0027] The control unit 524 requests a push notification from the device 101 according to the instructions indicated in the instruction information acquired by the location management unit 523. The control unit 524 also manages application software, including PWAs. For example, if the operation reception unit 522 receives an operation from a user instructing the installation of a PWA in a web browser, the control unit 524 installs the PWA. In this case, the control unit 524 stores information such as the PWA icon image and the URL as the connection destination. Also, if the transmission / reception unit 521 receives a push notification from the server device 103, the control unit 524 displays the contents of the received push notification on the input / output device 308. Furthermore, the control unit 524 launches the PWA in response to the user's operation on the user terminal 102 or instructions from the device 101.

[0028] Figure 4 shows the reception screen 700. The reception screen 700 is a screen for receiving settings related to PWA. In this embodiment, the control unit 507 of the device 101 displays the reception screen 700 on the input / output device 210 of the device 101. However, the control unit 507 may also display the reception screen 700 on a device other than the device 101, such as a terminal used by the administrator of the function provision system 1. The reception screen 700 displays the user reception unit 702, the notification reception unit 703, and the setting reception image 704.

[0029] The user reception unit 702 accepts requests for PWA use from the user terminal 102. When the user reception unit 702 is selected by the administrator, the PWA becomes available for use by the user terminal 102. The notification receiving unit 703 accepts requests for push notifications from device 101 to user terminal 102. When the notification receiving unit 703 is selected by the administrator, push notifications from device 101 to user terminal 102 become possible. The setting reception image 704 accepts settings related to push notifications when the notification reception unit 703 is selected. The setting reception image 704 shows the initial notification reception image 705 and the re-notification reception image 720.

[0030] The initial notification reception image 705 accepts settings for the first push notification that occurs when the detection unit 505 detects the occurrence of a detection state. The first push notification that occurs when the detection unit 505 detects the occurrence of a detection state may be referred to as the initial push notification below. The initial notification reception image 705 shows the error notification reception unit 710, the function reception unit 7100, the depletion notification reception unit 711, the depletion status reception unit 7110, and the warning notification reception unit 712.

[0031] The error notification receiving unit 710 receives the occurrence of an error in device 101 as the target for the initial push notification. When the error notification receiving unit 710 is selected by the administrator, an initial push notification is sent from device 101 to the user terminal 102 when an error occurs in device 101. The function reception unit 7100 receives the occurrence of an error related to a specific function in the device 101 as the target for the initial push notification. When a function reception unit 7100 is selected by the administrator, an initial push notification is sent from the device 101 to the user terminal 102 if an error occurs related to the function targeted by the selected function reception unit 7100. In the illustrated example, four function reception units 7100 are shown. The functions targeted by these four function reception units 7100 are "Print," "Scanner," "Fax," and "Paper Feed (Paper Related)." In the illustrated example, the function reception units 7100 for "Print," "Fax," and "Paper Feed (Paper Related)" are selected, while the function reception unit 7100 for "Scanner" is not selected. Each time the error notification receiving unit 710 is selected, all function receiving units 7100 are repeatedly selected and deselected.

[0032] The consumable notification receiving unit 711 receives notifications of specific conditions related to the consumables of the device 101 as targets for the initial push notification. When the consumable notification receiving unit 711 is selected, an initial push notification is sent from the device 101 to the user terminal 102 when a specific condition related to the consumables of the device 101 occurs. The consumption status reception unit 7110 receives notifications for the occurrence of specific conditions in consumable parts of the device 101, which are to be used for the initial push notification. When a consumption status reception unit 7110 is selected by the administrator, an initial push notification is sent from the device 101 to the user terminal 102 when a specific condition occurs in the part targeted by the selected consumption status reception unit 7110. In the illustrated example, three consumption status reception units 7110 are shown. The first consumption status reception unit 7110 receives an initial push notification when the amount of toner remaining in the toner bottle decreases to a predetermined amount. The predetermined amount can be any amount, but for example, it may be half the amount of a full bottle. The second consumption status reception unit 7110 receives an initial push notification when the toner in the toner bottle becomes empty. The third consumption notification reception unit 7110 receives an initial push notification when the toner box that collects used toner becomes full of toner. In the illustrated example, the consumption status receiving unit 7110 is selected to detect when the toner level has decreased to a predetermined amount, and to detect when the toner bottle is empty. On the other hand, the consumption status receiving unit 7110 is not selected to detect when the toner box is full of toner. Each time a consumption notification receiving unit 711 is selected, all consumption notification receiving units 7110 are repeatedly selected and deselected.

[0033] The Precursor Notification Reception Unit 712 receives the occurrence of a condition in which a precursor to component failure has been detected in the device 101 as the target for the initial push notification. When the Precursor Notification Reception Unit 712 is selected, if a condition in which a precursor to component failure has been detected occurs in the detection means (not shown) for detecting a precursor to component failure in the device 101, the device 101 sends the initial push notification to the user terminal 102.

[0034] The re-notification reception image 720 accepts settings for subsequent push notifications after the initial push notification has been sent. The subsequent push notification after the initial push notification may be referred to as a re-push notification below. The re-notification reception image 720 shows the error notification reception unit 730, the function reception unit 7300, the depletion notification reception unit 740, the depletion status reception unit 7400, the warning notification reception unit 750, and the recommended image 708.

[0035] The error notification receiving unit 730 receives the occurrence of an error in device 101 as a target for a follow-up push notification. When the error notification receiving unit 730 is selected by the administrator, if an error occurs in device 101, a follow-up push notification is sent from device 101 to the user terminal 102. The function reception unit 7300 receives notifications for errors related to specific functions in the device 101, which are then sent as targets for re-push notifications. When a function reception unit 7300 is selected by the administrator, if an error occurs in a function targeted by the selected function reception unit 7300, a re-push notification is sent from the device 101 to the user terminal 102. In the illustrated example, four function reception units 7300 are shown. The functions targeted by these four function reception units 7300 are "Print," "Scanner," "Fax," and "Paper Feed (Paper Related)." In the illustrated example, the function reception units 7300 for "Print," "Fax," and "Paper Feed (Paper Related)" are selected, while the function reception unit 7300 for "Scanner" is not selected.

[0036] In this embodiment, the function receiving unit 7300 can only be selected for errors of the same function that were received by the function receiving unit 7100 as targets for push notifications. In other words, for errors of functions that were not received by the function receiving unit 7100 as targets for push notifications, the function receiving unit 7300 cannot be selected. For example, since the "Print" function receiving unit 7100 is selected, the selection of the "Print" function receiving unit 7300 is accepted. On the other hand, since the "Scanner" function receiving unit 7100 is selected, the selection of the "Scanner" function receiving unit 7300 is not accepted. Furthermore, function receiving units 7300 that cannot be selected, such as the "Scanner" function receiving unit 7300, are displayed in a different color (gray in the illustrated example) than the function receiving units 7300 that can be selected. Furthermore, in this embodiment, each time the error notification receiving unit 730 is selected, the selection and deselection of all function receiving units 7300 whose selection is accepted is repeated.

[0037] The consumable notification receiving unit 740 receives notifications regarding specific conditions related to the consumables of the device 101, and identifies them as targets for re-push notifications. When the consumable notification receiving unit 740 is selected, a re-push notification is sent from the device 101 to the user terminal 102 when a specific condition related to the consumables of the device 101 occurs. The consumption status reception unit 7400 receives notifications for specific conditions in consumable parts of the device 101, which are then used for re-push notifications. When a consumption status reception unit 7400 is selected by the administrator, a re-push notification is sent from the device 101 to the user terminal 102 when a specific condition occurs in a part that is the target of the selected consumption status reception unit 7400. In the illustrated example, three consumption status reception units 7400 are shown. The first consumption status reception unit 7400 receives a re-push notification when the amount of toner remaining in the toner bottle decreases to a predetermined amount. The predetermined amount can be any amount, but for example, it may be half the amount of a full bottle. The second consumption status reception unit 7400 receives a re-push notification when the toner in the toner bottle becomes empty. The third consumption notification reception unit 7400 receives a re-push notification when the toner box that collects used toner becomes full of toner. In the illustrated example, a consumption status receiving unit 7400 that detects when the toner level has decreased to a predetermined amount and a consumption status receiving unit 7400 that detects when the toner bottle is empty are selected. On the other hand, a consumption status receiving unit 7400 that detects when the toner box is full of toner is not selected.

[0038] In this embodiment, the consumption status receiving unit 7400 can only be selected for the same status as that received by the consumption status receiving unit 7110 as the target of a push notification. In other words, for statuses that have not been received by the consumption status receiving unit 7110 as the target of a push notification, the consumption status receiving unit 7400 cannot be selected. Furthermore, the consumption status receiving unit 7400 for which selection is not accepted is displayed in a different color (gray in the illustrated example) than the consumption status receiving unit 7400 for which selection is accepted. Furthermore, in this embodiment, each time a consumption notification receiving unit 740 is selected, the selection and deselection of all consumption notification receiving units 7400 whose selection is accepted is repeated.

[0039] The Precursor Notification Reception Unit 750 receives notifications of the occurrence of a condition in which a precursor to component failure has been detected in the device 101, and identifies it as a target for a re-push notification. When the Precursor Notification Reception Unit 750 is selected, a condition in which a precursor to component failure has been detected occurs in the detection means (not shown) that detects precursors to component failure in the device 101, and a re-push notification is sent from the device 101 to the user terminal 102. In this embodiment, the selection of the premonitory notification receiving unit 750 is accepted only when the premonitory notification receiving unit 712 is selected.

[0040] Recommended image 708 provides recommendations for whether to include a device 101 in the re-push notification and whether to exclude it from the re-push notification, depending on the status of the device 101. Recommended image 708 includes a selected recommended image 760, a recommendation reception unit 761, a non-selected recommended image 762, and a non-recommendation reception unit 763. The recommended selection image 760 recommends that the state shown in the recommendation reception unit 761 be targeted for a push notification. In other words, the recommended selection image 760 recommends selecting the recommendation reception unit 761. In the illustrated example, the recommended selection image 760 shows the text, "The following selection is recommended." The recommendation reception unit 761 receives notifications for conditions that have been recommended as targets for re-push notifications. When the recommendation reception unit 761 is selected by the administrator, a re-push notification is sent from the device 101 to the user terminal 102 when a condition that is targeted by the selected recommendation reception unit 761 occurs. In the illustrated example, the recommendation reception unit 761 displays the text "User-responsive" indicating a condition that will become a target for re-push notifications when selected. The recommendation reception unit 761 also displays the text "Notification for physical confirmation only" and "Prepared for response, awaiting user response (toner / parts delivered, etc.)" which are examples of conditions that will become targets for re-push notifications when selected.

[0041] The non-selection recommendation image 762 recommends that the state indicated in the non-recommendation reception unit 763 not be targeted for further push notifications. In other words, the non-selection recommendation image 762 recommends not selecting the non-recommendation reception unit 763. In the illustrated example, the non-selection recommendation image 762 displays the text, "We recommend not selecting below." The non-recommendation reception unit 763 accepts the occurrence of a condition that is recommended not to be subject to a re-push notification as a target for a re-push notification. When the non-recommendation reception unit 763 is selected by the administrator, a re-push notification is sent from the device 101 to the user terminal 102 when a condition that is subject to the selected recommendation reception unit 761 occurs. In the illustrated example, two non-recommendation reception units 763 are shown. The first non-recommendation reception unit 763 accepts the occurrence of a condition where preparation for a response is underway, in other words, where preparation for a response is not yet complete, as a target for a re-push notification. The second non-recommendation reception unit 763 accepts the occurrence of a condition where a person to repair the device 101 is scheduled to be dispatched to the location where the device 101 is installed as a target for a re-push notification.

[0042] The conditions under which selections for initial push notifications and subsequent push notifications are accepted in the settings acceptance image 704 are determined according to the type of device 101, such as network routers, surveillance cameras, digital medical devices, automobiles, delivery boxes, lockers, etc.

[0043] Figure 5 is a sequence diagram showing the processing flow performed by device 101, user terminal 102, and server device 103. The processes in steps 600 to 601 of Figure 5 (hereinafter sometimes referred to as "S") are related to the registration of the location of the device 101 by the server device 103. The processes in steps 602 to 607 of Figure 5 are related to the registration of the user terminal 102 as the target of push notifications by the server device 103. The processes in steps 610 to 613 of Figure 5 are related to the initial push notification. The processes in steps 620 to 627 of Figure 5 are related to the subsequent push notification.

[0044] First, we will explain the process related to the registration of the location of the device 101 by the server device 103. The control unit 507 of device 101 transmits location information, identification information, and instruction information to the server device 103 and requests the server device 103 to register the location of device 101 (S600). The management unit 512 of the server device 103 acquires location information, identification information, and instruction information transmitted from the device 101 via the transmission / reception unit 511. The management unit 512 then registers the location identified from the acquired location information as the location of the device 101 identified from the acquired identification information (S601). The management unit 512 also manages each of the acquired pieces of information.

[0045] Next, we will explain the process related to registering the user terminal 102 as a target for push notifications by the server device 103. The user enters the URL of the website used to install the PWA into the user terminal 102. In this case, the control unit 524 of the user terminal 102 requests the device 101 to display the web content in the user terminal 102's web browser (S602). The control unit 507 of the device 101 transmits web content in response to a request from the user terminal 102 (S603).

[0046] The control unit 524 of the user terminal 102 displays the web content transmitted from the device 101 on the input / output device 308 (S604). The web content displayed on the input / output device 308 at this time includes UI information and PWA information. The UI information (terminal site) consists of, for example, HTML, JavaScript, and CSS. The PWA information includes the components of the PWA, such as the Service Worker and the manifest file. The manifest file is a file that describes the installation settings of the PWA. The PWA information may also include a beacon receiving function. The beacon receiving function is a function that receives beacon signals transmitted from the device 101. By having a beacon receiving function, the user terminal 102 receives the beacon signal transmitted from the device 101 and transmits the identification information contained in the received beacon signal to the server device 103 to request the location information of the device 101 identified from this identification information. If the PWA information includes a beacon receiving function, the user terminal 102 does not need to install a native application to receive beacon signals. Therefore, the burden on the user in configuring the user terminal 102 to receive re-push notifications is reduced. The beacon reception function may be included in the PWA information as part of a Service Worker function that runs in the background process of the user terminal 102, or it may be included as a background process separate from the Service Worker.

[0047] When the user instructs the user terminal 102 to install the PWA, the control unit 524 of the user terminal 102 executes the PWA installation (S605). The control unit 524 of the user terminal 102 requests the server device 103 to register the user terminal 102 as a target for push notifications from the device 101, based on the manifest file (S606). When the management unit 512 of the server device 103 receives a request from the user terminal 102, it registers the user terminal 102 as a target for push notifications from the device 101, thereby managing the user terminal 102 as a target for push notifications (S607).

[0048] Furthermore, when the control unit 524 of the user terminal 102 requests registration for push notifications from the server device 103, it may transmit information identifying the user to be registered. The management unit 512 of the server device 103 may then register only the users for whom registration has been requested from the user terminal 102 as targets for push notifications. In this case, when a user registered as a target for push notifications is logged into the user terminal 102, a push notification will be sent to the user terminal 102. On the other hand, when a user not registered as a target for push notifications is logged into the user terminal 102, no push notification will be sent to the user terminal 102. The control unit 524 of the user terminal 102 may also determine whether or not a user is a target for push notifications based on the logged-in user. Furthermore, push notifications may be sent to user terminal 102 regardless of which user is logged in to user terminal 102. In this case, if a user who is not registered as a target for push notifications is logged in to user terminal 102, the control unit 524 may not display the contents of the push notification on user terminal 102. Then, when a user who is registered as a target for push notifications logs in to user terminal 102, the control unit 524 may display the contents of the push notification on user terminal 102.

[0049] Next, we will explain the process related to the initial push notification. When a state of device 101 that is predetermined as the target of detection by the detection unit 505 of device 101 occurs, the detection unit 505 detects the state that has occurred in device 101 (S610). Hereinafter, it is assumed that the state detected by the detection unit 505 is set on the reception screen 700 as the state to be targeted for the initial push notification.

[0050] The control unit 507 of device 101 sends a push notification instruction to the server device 103, along with information indicating the content of the push notification (S611). When the control unit 513 of the server device 103 receives instructions from the device 101, it sends a push notification to the user terminal 102, which is registered with the management unit 512 as a target for push notifications, according to the instructions received from the device 101 (S612). In other words, the control unit 513 forwards the push notification received from the device 101 to the user terminal 102. When the Service Worker, which is running in the background via the control unit 524 of the user terminal 102, receives a push notification via the transmitting / receiving unit 521, it displays the content of the received re-push notification on the input / output device 308 (S613).

[0051] Next, we will explain the process related to re-push notifications. In the following, it is assumed that the state detected in step 610 is set as a state that is eligible for re-push notification on the reception screen 700. It is also assumed that the state detected in step 610 continues until the re-push notification is sent. After the initial push notification is sent, the transmitting / receiving unit 501 of device 101 transmits a beacon signal to the surrounding area (S620). This beacon signal is not received by user terminals 102 located far from device 101, but is received by user terminals 102 located close to device 101. The transmitting / receiving unit 501 also continuously transmits beacon signals.

[0052] When a user approaches device 101, the transmitting / receiving unit 521 of the user terminal 102 held by the user receives a beacon signal (S621). The location management unit 523 of the user terminal 102 transmits the identification information of the device 101 contained in the beacon signal received by the transmitting / receiving unit 521 to the server device 103, thereby requesting the location information of the device 101 identified from the identification information (S622). When the control unit 513 of the server device 103 obtains identification information from the user terminal 102 via the transmitting / receiving unit 511, it transmits the location information and instruction information of the device 101 identified from the obtained identification information to the user terminal 102 (S623).

[0053] When the control unit 524 of the user terminal 102 acquires location information and instruction information via the transmitting / receiving unit 521, it requests a re-push notification from the device 101 at the location identified from the location information, based on the instruction identified from the instruction information (S624). When the control unit 507 of device 101 receives a request for a re-push notification from the user terminal 102, it sends an instruction to send a re-push notification and an instruction to activate the PWA, along with information identifying the user terminal 102 that made the request, to the server device 103 (S625). When the control unit 513 of the server device 103 receives an instruction from the device 101, it sends a re-push notification to the user terminal 102 that requested a re-push notification from the device 101, and also sends an instruction to activate the PWA (S626). The Service Worker, which is running in the background via the control unit 524 of the user terminal 102, displays the content of the received push notification on the input / output device 308 when it receives a re-push notification via the transmitting / receiving unit 521. Also, if the PWA is not running on the user terminal 102 at this time, the control unit 524 starts the PWA in response to instructions from the server device 103 (S627).

[0054] In the example above, the user terminal 102 communicates with the server device 103 (S622, S623) and then requests a re-push notification from the device 101, resulting in a re-push notification from the device 101. However, the method is not limited to this. For example, if user terminal 102 communicates with server device 103 based on receiving a beacon signal, server device 103 may notify device 101 that the beacon signal has been received by user terminal 102. In this case, device 101 may send a re-push notification instruction to server device 103 along with information identifying the user terminal 102 that made the request, thereby performing a re-push notification.

[0055] Figure 6 is a flowchart showing the flow of the re-notification process. The re-notification process is the process by which device 101 sends a second push notification to the user terminal 102 that received the initial push notification. In this embodiment, after the initial push notification has been sent, if device 101 is transmitting a beacon signal (see S620 in Figure 5), the re-notification process is started. The control unit 507 of the device 101 determines whether or not a request for a re-push notification has been received from the user terminal 102 (S801). As long as the negative result persists (No in S801), the process in step 801 is repeated. Furthermore, if the control unit 507 receives a request for a second push notification from the user terminal 102 (Yes in S801), it determines whether the detection state that triggered the initial push notification is still in effect (S802). The control unit 507 determines whether the detection state that triggered the initial push notification is still in effect from the history of the status of the device 101 managed by the device management unit 502.

[0056] If the detection state that triggered the initial push notification is still present (Yes in S802), proceed to the next step. The control unit 507 determines whether the detection state that triggered the initial push notification is set as a state eligible for a re-push notification on the reception screen 700 (S803). The control unit 507 determines whether the detection state that triggered the initial push notification is set as a state eligible for a re-push notification on the reception screen 700 based on whether it is selected in the re-notification reception image 720 on the reception screen 700. If the detection state that triggered the initial push notification is set to be a state that is eligible for a re-push notification (Yes in S803), the process proceeds to the next step. The control unit 507 determines whether the time limit has elapsed since the initial push notification or re-push notification was sent to the user terminal 102 (S804). The time limit is a period during which push notifications are restricted in order to prevent frequent push notifications from being sent from the device 101 to the user terminal 102. The time limit can be any amount, but for example, it may be 5 minutes.

[0057] If the time limit has elapsed since the initial push notification or re-push notification was sent from device 101 to user terminal 102 (Yes in S804), the control unit 507 instructs server device 103 to send a re-push notification and start the PWA (S805). The process in step 805 is the same as the process in step 625 shown in Figure 5. As a result, server device 103 sends a re-push notification to user terminal 102 and starts the PWA on user terminal 102. Additionally, if the detection state is not ongoing (No in S802), if the detection state is not set to be eligible for a re-push notification (No in S803), or if the time limit has not elapsed since the push notification was sent (No in S804), the re-notification process will end without a re-push notification being sent.

[0058] If the detection state is not maintained (No in S802), or if the detection state is not set to be a state that is eligible for a re-push notification (No in S803), the control unit 507 terminates the transmission of the beacon signal by the transmitting / receiving unit 501. However, if the detection state is not set to be a state that is eligible for a re-push notification (No in S803), the control unit 507 may prevent the transmitting / receiving unit 501 from transmitting a beacon signal after the initial push notification has been sent. Furthermore, if the time limit has not elapsed since the push notification was sent (No in S804), the re-notification process will end while the beacon signal transmission by the transmitting / receiving unit 501 continues. In this case, the re-notification process will start again.

[0059] Figure 7 shows the screen 650 displayed on the input / output device 308 in step 604 of Figure 5. Button 651 is displayed when the terminal site displayed on the input / output device 308 can be installed as a PWA. Dialog 652 is displayed to confirm with the user whether or not to install the PWA. Note that dialog 652 may also be displayed when button 651 is pressed by the user. Button 653 is pressed by the user to install the PWA. When button 653 is pressed, the PWA is installed on the user terminal 102.

[0060] Figure 8 shows an example of screen 660 of the remote UI (terminal site) that the PWA displays on the input / output device 308 when the PWA is installed on the user terminal 102. The content displayed on screen 660 in Figure 8 is the same as that displayed on screen 650 in Figure 7, but it differs from the display of a normal web browser, for example, the address bar is not displayed, making it appear as if the user is operating a native application. Note that when a user launches an installed PWA, screen 660 as shown in Figure 8 is also displayed on the input / output device 308 of the user terminal 102.

[0061] Figure 9(A) shows the initial notification image 670. The initial notification image 670 is the image displayed on the input / output device 308 of the user terminal 102 when the initial push notification is made. In other words, the initial notification image 670 is the content that is notified to the user terminal 102 as the initial push notification. The initial notification image 670 shows the type notification unit 671, the content notification unit 672, and the device notification unit 673. The type notification unit 671 displays the text "Error occurred," which is the type of state that occurred in the device 101, and the text "Print," which is the type of function to which the state is affected. The content notification unit 672 displays the details of the condition that occurred in the device 101. In the illustrated example, the content notification unit 672 displays the text, "No paper available." The device notification unit 673 displays information that identifies the device 101.

[0062] Figure 9(B) shows the re-notification image 680. The re-notification image 680 is the image displayed on the input / output device 308 of the user terminal 102 when a re-push notification is issued. In other words, the re-notification image 680 is the content that is notified to the user terminal 102 as a re-push notification. The re-notification image 680 shows the number of times image 681, the type notification unit 682, the period notification unit 683, the content notification unit 684, the device notification unit 685, and the warning level notification unit 686. The count image 681 shows the number of times push notifications were sent to the user terminal 102 as a result of the occurrence of a detection state. In the illustrated example, the count image 681 shows the text "2nd time" indicating that the number of push notifications was 2. The type notification unit 682 displays the text "Error occurred," which is the type of state that occurred in the device 101, and the text "Print," which is the type of function to which the state is affected. The type notification unit 682 also displays the text "From 12:00 on April 10, 2024," which is the start date of the detection state that triggered the re-push notification.

[0063] The period notification unit 683 indicates the period that has elapsed since the detection condition that triggered the re-push notification occurred. In the illustrated example, the period notification unit 683 displays the text "0 days 2 hours 10 minutes". The contents of the content notification unit 684 and the device notification unit 685 are the same as the contents of the content notification unit 672 and the device notification unit 673 of the initial notification image 670. The warning level notification unit 686 displays the warning level indicated by the push notification. In this embodiment, the warning level indicated by the push notification is set to one of 1 to 3 depending on the number of push notifications sent to the user terminal 102 when a detection state occurs. Furthermore, the warning level increases as the number of push notifications increases, and a higher warning level indicates a higher degree of warning. In the illustrated example, the warning level notification unit 686 displays the text "Warning Level: 2 (Action Required)".

[0064] In this embodiment, the content displayed on the user terminal 102 differs between the initial push notification and the subsequent push notification, but this is not limited to this. Even when an initial push notification is sent, the same content as the subsequent notification image 680 may be displayed on the user terminal 102. Similarly, even when a subsequent push notification is sent, the same content as the initial notification image 670 may be displayed on the user terminal 102.

[0065] As described above, in this embodiment, the control unit 507 of the device 101 sends a push notification to the user terminal 102, which has the PWA software installed for providing status information, when the device 101 is in a state that satisfies predetermined status conditions. Status conditions include the detection of the status of the device 101, which is the target of the push notification, by the detection unit 505. The state of the device 101 that satisfies the status conditions is the state selected in the initial notification reception image 705 (see Figure 4). After the push notification has been sent to the user terminal 102, the control unit 507 sends another push notification to the user terminal 102 if the user terminal 102 is located within a range that satisfies predetermined range conditions relative to the device 101. Range conditions include the recognition that the user terminal 102 is approaching the device 101. The range that satisfies the range conditions is the range in which the user terminal 102 can receive the beacon signal. In this case, unlike when notifications are sent from device 101 to user terminal 102 via application software such as a native app, there is no need to configure notification settings on user terminal 102. Therefore, without requiring each user terminal 102 to configure notifications from device 101, users approaching device 101, which has a requirement to be notified to user terminal 102, can be made aware of the presence of device 101.

[0066] Furthermore, when the control unit 507 sends a push notification to the user terminal 102, if the user terminal 102 has not launched the PWA software, the control unit 507 launches the PWA software on the user terminal 102. In this case, if a second push notification is sent, the user will no longer need to perform an action to launch the PWA in addition to the action to check the content of the second push notification.

[0067] Furthermore, when issuing a second push notification, the control unit 507 may launch the PWA software on the user terminal 102 on the condition that the user has performed a predetermined operation on the user terminal 102. A predetermined operation could be the user selecting the second notification image 680 (see Figure 9(B)). Alternatively, the predetermined operation could be an operation in which the user instructs the launch of the PWA when a second push notification is issued on the launch acceptance screen (not shown) displayed on the user terminal 102. In this case, the PWA is prevented from being launched unintentionally by the user.

[0068] Furthermore, if a PWA is launched in response to a re-push notification, the terminal site cached on the user terminal 102 or the terminal site provided by device 101 will be displayed on the user terminal 102. Also, if the terminal site's PWA is running in the background when the re-push notification is made, screen 660 will be displayed on the top screen of the user terminal 102, and a re-notification image 680 may be displayed in front of screen 660. Whether or not to display via PWA during such background operation may be set uniformly by the administrator on device 101, or it may be set individually for each user terminal 102. Whether or not to display via PWA during background operation may also be determined depending on the content of the push notification.

[0069] Furthermore, in this embodiment, the state conditions include a first state condition and a second state condition that is different from the first state condition. The first state condition is when the detection unit 505 detects the state of the device 101 that is the target of the re-push notification. The second state condition is when the detection unit 505 detects the state of the device 101 that is the target of the initial push notification but not the re-push notification. The control unit 507 then sends a re-push notification to the user terminal 102 at a location that satisfies the range condition when the device 101 is in a state that satisfies the first state condition. The control unit 507 also restricts the re-push notification to the user terminal 102 at a location that satisfies the range condition when the device 101 is in a state that satisfies the second state condition. In this case, whether or not a second push notification is sent after the initial push notification can be switched depending on the state occurring in device 101.

[0070] In particular, in this embodiment, the control unit 507 displays a reception screen 700 that accepts a selection of which state will satisfy the first condition (see Figure 4). The reception screen 700 then displays information recommending that a specific state be selected as the state that satisfies the first condition. Examples of information recommending that a specific state be selected as the state that satisfies the first condition include the selection recommendation image 760 and the recommendation reception unit 761. A specific state is a state that is accepted as the target for a re-push notification when the recommendation reception unit 761 is selected. In this case, the user can be prompted to select a specific state for device 101 that will help prevent them from forgetting about it through a follow-up push notification.

[0071] Furthermore, after a push notification is sent to the user terminal 102, the user terminal 102 may be located within a range that satisfies the range conditions. In this case, if the device 101 does not meet the state conditions (No in S802 of Figure 6), the control unit 507 restricts sending another push notification to the user terminal 102. In this case, it is prevented that a re-push notification will be sent even if device 101 is not in a state where it is eligible for a re-push notification.

[0072] Furthermore, if a predetermined amount of time has not elapsed since the push notification was sent to the user terminal 102, the control unit 507 will restrict sending another push notification to the user terminal 102, even if the user terminal 102 is located within the range that satisfies the range conditions. The predetermined amount of time may include a time limit. In this case, compared to a configuration where a push notification is sent again regardless of the time elapsed since the initial push notification to the user terminal 102, the frequency of push notifications is suppressed, thus reducing the burden on the user in checking push notifications.

[0073] Furthermore, the information that is re-notified via push notification includes information regarding the start time when the device 101 met the state conditions, information corresponding to the time elapsed since the device 101 met the state conditions, and information corresponding to the number of times a push notification was sent to the user terminal 102. The type notification unit 682 is an example of information regarding the start time when the device 101 met the state conditions. The period notification unit 683 and the warning level notification unit 686 are examples of information corresponding to the time elapsed since the device 101 met the state conditions. The count image 681 and the warning level notification unit 686 are examples of information corresponding to the number of times a push notification was sent to the user terminal 102. In this case, the information that is re-notified via push notification only needs to include at least one of the above-mentioned pieces of information. Even in this case, the user can be made aware of the state that has occurred in device 101.

[0074] (Second Embodiment) Next, the function provision system 1 of the second embodiment will be described. The first and second embodiments are similar in that the user terminal 102 requests a re-push notification from the device 101 based on receiving a beacon signal, and the device 101 then sends a re-push notification to the user terminal 102. On the other hand, in the first embodiment, the user terminal 102's approach to the device 101 was detected by the user terminal 102 receiving a beacon signal transmitted from the device 101, and a re-push notification was sent based on this detection. In contrast, in the second embodiment, the user terminal 102's approach to the device 101 is detected in stages, and a re-push notification is sent from the device 101 to the user terminal 102 at each stage in which the approach is detected. Examples of the user terminal 102's staged approach to the device 101 include approaching the building where the device 101 is installed, approaching the same floor as the device 101 within the building, and approaching the same room as the device 101 within the building. In the second embodiment, a description of the configuration of the function-providing system 1 that differs from that of the first embodiment will be given, and the description of the configuration of the function-providing system 1 that is the same as that of the first embodiment will be omitted.

[0075] Figure 10(A) shows the hardware configuration of the transmitter 104 provided in the function provision system 1 of the second embodiment. The transmitter 104 is a beacon signal transmitter. In other words, in this embodiment, the transmitter 104, not the device 101, transmits the beacon signal. The transmitter 104 is provided at the entrance of the building where the device 101 is located, the entrance of the floor in the building where the device 101 is located, the entrance of the room in the building where the device 101 is located, etc. In other words, the transmitter 104 is provided at each stage in detecting the approach of the user terminal 102 to the device 101. The transmitter 104 is also connected to the device 101, the user terminal 102, and the server device 103 via the network 100. As shown in Figure 10(A), the transmitter 104 has a CPU 901, ROM 902, RAM 903, storage device 904, and network I / F 905. The CPU 901, ROM 902, RAM 903, storage device 904, and network I / F 905 are each connected via a bus 906.

[0076] The CPU 901 controls the entire transmitter 104 by executing a program stored in the ROM 902. The ROM 902 stores the aforementioned program and location information indicating the position of the transmitter 104. The RAM 903 functions as the memory and work area of ​​the CPU 901 and stores information indicating the settings of the transmitter 104 and various logs. The network I / F 905 communicates with external devices via the network 100. The CPU 901 performs program execution processing together with the ROM 902 and RAM 903, and also performs processing to record information on recording media such as the storage device 904. The storage device 904 functions as an external storage device and can store information indicating the settings of the transmitter 104 and various logs in place of the RAM 903.

[0077] Figure 10(B) shows the functional configuration of the transmitter 104. The transmitter 104 includes a transmitting / receiving unit 921, a management unit 922, and a control unit 923. The transmitting / receiving unit 921 transmits and receives information to and from external devices. The transmitting / receiving unit 921 also transmits beacon signals to the surrounding area. The management unit 922 manages information generated by the transmitter 104 and information acquired by the transmitter 104. For example, the management unit 922 manages location information indicating the location of the transmitter 104, identification information to identify the transmitter 104, firmware version, network information such as IP address, and information for communicating with the server device 103. The management unit 922 may also manage the operation history of the transmitter 104, including error history.

[0078] The control unit 923 requests the server device 103 to register the location of the transmitter 104 by associating the location information and identification information managed by the management unit 922 and transmitting it to the server device 103. The control unit 923 also includes the location information of the transmitter 104, managed by the management unit 922, in the beacon signal transmitted by the transmitting / receiving unit 921. The control unit 923 may also function as an application server. In this case, the control unit 923 may provide a website screen to the user terminal 102 and accept instructions from the user to register the transmitter 104 with the server device 103 on the provided website screen. For example, when the user enters the IP address of the server device 103 on the website screen displayed on the user terminal 102, the control unit 923 communicates with the server device 103 and requests the server device 103 to register the transmitter 104.

[0079] Figure 11 is a sequence diagram showing the processing flow performed by device 101, user terminal 102, server device 103, and transmitter 104. In the following, it is assumed that the function provision system 1 is equipped with two devices 101, consisting of a first device 101 and a second device 101. The processes in steps 1000 to 1005 of Figure 11 relate to the registration of the transmitter 104 and the device 101 by the server device 103. Furthermore, the processes in steps 1020 to 1028 of Figure 11 relate to the re-push notification process. Note that the processes related to the registration of the user terminal 102 as the target of the push notification by the server device 103 and the initial push notification in this embodiment are the same as in the first embodiment, and therefore their explanation is omitted.

[0080] First, we will explain the process related to the registration of the transmitter 104 and the device 101 by the server device 103. The control unit 923 of the transmitter 104 transmits location information and identification information to the server device 103 and requests the server device 103 to register the location of the transmitter 104 (S1000). When the management unit 512 of the server device 103 acquires location information and identification information transmitted from the transmitter 104 via the transmitting / receiving unit 511, it registers the location identified from the acquired location information as the location of the transmitter 104 identified from the acquired identification information (S1001). The management unit 512 also manages each of the acquired pieces of information. Note that steps 1000 and 1001 are performed for each transmitter 104.

[0081] Next, the control unit 507 of the first device 101 transmits identification information to the server device 103 and requests the server device 103 to register the device 101 (S1002). When the management unit 512 of the server device 103 obtains the identification information transmitted from the first device 101 via the transmitting / receiving unit 511, it registers the first device 101, which is identified from the obtained identification information, in association with the location of the transmitter 104 (S1003). The location of the transmitter 104 associated at this time is the location registered with the server device 103 in step 1001. Next, the control unit 507 of the second device 101 transmits identification information to the server device 103 and requests the server device 103 to register the device 101 (S1004). When the management unit 512 of the server device 103 receives the identification information transmitted from the second device 101 via the transmitting / receiving unit 511, it registers the second device 101, which is identified from the acquired identification information, in association with the location of the transmitter 104 (S1005). The location of the transmitter 104 associated at this time is the location registered with the server device 103 in step 1001. In this embodiment, for example, an administrator inputs the location information of a transmitter 104 to be registered in association with device 101 into device 101, and the location information input into device 101 is transmitted to the server device 103 along with a request to register device 101. This establishes an association between device 101 and the location of transmitter 104.

[0082] Furthermore, in the following, it is assumed that both the first device 101 and the second device 101 are registered with the server device 103 in association with the location information of the same transmitter 104 installed at the entrance of the building in which the first device 101 and the second device 101 are installed. In this embodiment, when the server device 103 associates and registers multiple devices 101 with the location information of the same transmitter 104, it registers one of the registered devices 101 as the representative device 101. Which device 101 is registered as the representative may be determined by the administrator's instructions. Alternatively, the device 101 that is initially registered by the server device 103 (the first device 101 in the above example) may be registered as the representative device 101.

[0083] Next, we will explain the process related to re-push notifications. After the initial push notification is sent, the transmitting / receiving unit 921 of the transmitter 104 transmits a beacon signal to the surrounding area (S1020). The transmitting / receiving unit 921 also continuously transmits beacon signals. When a user approaches the transmitter 104, the transmitting / receiving unit 521 of the user terminal 102 held by the user receives the beacon signal (S1021). The location management unit 523 of the user terminal 102 transmits the location information of the transmitter 104, which is included in the beacon signal received by the transmitting / receiving unit 521, to the server device 103, and also requests the server device 103 to send a re-push notification to the user terminal 102 (S1022).

[0084] When the control unit 513 of the server device 103 obtains location information from the user terminal 102 via the transmitting / receiving unit 511, it requests information for a re-push notification from the device 101 registered in the management unit 512 in association with the obtained location information. In this example, the control unit 513 requests information for a re-push notification from the first device 101 (S1023). Upon receiving the request, the control unit 507 of the first device 101 sends the information to be notified to the user terminal 102 as a re-push notification, along with the re-push notification instruction, to the server device 103 (S1024). Furthermore, the control unit 513 requests information for a re-push notification from the second device 101 (S1025). Upon receiving the request, the control unit 507 of the second device 101 sends the information to be notified to the user terminal 102 as a re-push notification, along with the re-push notification instruction, to the server device 103 (S1025).

[0085] When the control unit 513 of the server device 103 receives instructions from the device 101, it sends the information obtained from the device 101 as information to be notified to the user terminal 102 to the user terminal 102 that requested the re-push notification, thereby performing a re-push notification (S1027). When the Service Worker, which is running in the background via the control unit 524 of the user terminal 102, receives a re-push notification via the transmitting / receiving unit 521, it displays the contents of the received re-push notification on the input / output device 308 (1028).

[0086] As mentioned above, the server device 103 may be instructed to send re-push notifications from multiple devices 101 associated with the same location information. In this case, re-push notifications may be sent to the PWA of each user terminal 102 corresponding to each device 101, or re-push notifications may be sent only to the PWA of the device 101 registered as representative by the server device 103. If re-push notifications are sent only to the PWA of the device 101 registered as representative by the server device 103, the inconvenience to the user is reduced by preventing re-push notifications from being sent to the PWA of each user terminal 102 corresponding to each device 101.

[0087] Furthermore, if a re-push notification is sent only to the PWA of the representative device 101, the content of the re-push notification sent may include the content of the re-push notification for each device 101. In this case, for example, the control unit 513 of the server device 103 generates a group website (including PWA installation information) that groups the re-push notifications for each device 101. Then, when the control unit 513 sends a re-push notification to the PWA of the representative device 101 on the user terminal 102, it includes the URL information of the group website in the content of this re-push notification. In this case, the user can confirm the re-push notification for each device 101 from the URL information of the group website displayed on the user terminal 102.

[0088] In this embodiment, when the transmitter 104 starts transmitting a beacon signal, it notifies the device 101 of the start of beacon signal transmission. Upon receiving the notification from the transmitter 104, the device 101 performs a re-notification process (see Figure 6). Also in this embodiment, when the device 101 receives a request for information for a re-push notification from the server device 103, an affirmative result is obtained in step 801 (Yes in S801).

[0089] Next, we will describe the image displayed on the input / output device 308 of the user terminal 102 when a re-push notification is made in this embodiment. In the following description, we will explain the case when re-push notifications are made from the first device 101 and the second device 101, as explained using Figure 11. Figure 12(A) shows the re-notification screen 1100. The re-notification screen 1100 is the screen displayed on the user terminal 102 when a re-push notification is sent. In other words, the re-notification screen 1100 is the information that is notified to the user terminal 102 as a re-push notification. The re-notification screen 1100 shows the target section 1101 and the site notification section 1102.

[0090] The target section 1101 displays information regarding the target of the re-push notification. Specifically, the target section 1101 displays location information of the transmitter 104 associated with the device 101 that sent the re-push notification, information indicating the location of the transmitter 104, and information identifying the device 101 that is registered as a representative in the server device 103. The site notification unit 1102 displays URL information for group websites that group the re-push notifications for each device 101.

[0091] When the user selects the site notification unit 1102, the input / output device 308 of the user terminal 102 displays the group screen 1110, as shown in Figure 12(B). The group screen 1110 is a group website screen where the content of the re-push notification for each device 101 can be checked. The group screen 1110 shows a button 1111 and a group notification unit 1112. Button 1111 is displayed when the group website screen shown on the input / output device 308 can be installed as a PWA. The group notification unit 1112 displays the content of the notification requirements on the group website. Buttons 1113 and 1114 displayed on the group notification unit 1112 are buttons for checking the detailed content of notifications from the first device 101 and the second device 101, respectively. In other words, the group notification unit 1111 displays a button for checking the detailed content of the notification from each device 101 that has sent a re-push notification. When this button is selected, the PWA of the terminal site of the device 101 corresponding to the selected button is launched, and the content of the re-push notification from device 101 is displayed.

[0092] Figure 13 shows the top screen 1120 displayed on the user terminal 102 after the group website's PWA has been installed on the user terminal 102 (after installation due to the selection of button 1111). The top screen 1120 displays icons for each function of the user terminal 102. The top screen 1120 also displays a group icon 1125. The group icon 1125 is the icon for the group website's PWA and is displayed after the group website's PWA is installed by selecting button 1111 (see Figure 12(B)). The group icon 1125 gives the appearance of multiple native apps grouped together.

[0093] When the user long-presses the group icon 1125, a pop-up image 1126 is displayed on the top screen 1120. The pop-up image 1126 shows the first device icon 1127, which is the PWA icon for the first device 101, and the second device icon 1128, which is the PWA icon for the second device 101. When the user clicks the first device icon 1127, the PWA on the terminal site of the first device 101 is launched. Similarly, when the user clicks the second device icon 1128, the PWA on the terminal site of the second device 101 is launched.

[0094] In this embodiment, the PWA icons for the terminal site of device 101 are grouped together, thereby reducing the effort required for users to search for the icon for each device 101.

[0095] Furthermore, as described above, the function provision system 1 of this embodiment detects the approach of the user terminal 102 to the device 101 in stages, and a re-push notification is sent from the device 101 to the user terminal 102 at each stage where approach is detected. For example, suppose that transmitters 104 are installed at the entrance of the building where the device 101 is located, and at the entrance of the room in the building where the device 101 is located. In this case, after the initial push notification is sent, the device 101 sends a re-push notification to the user terminal 102 based on the user terminal 102 approaching the building entrance and receiving a beacon signal transmitted from the transmitter 104 installed at the building entrance. Subsequently, the device 101 sends another re-push notification to the user terminal 102 based on the user terminal 102 approaching the entrance of the room in the building where the device 101 is located and receiving a beacon signal from the transmitter 104 installed at the room entrance. In other words, the range conditions include a first range condition and a second range condition, which is defined as the user terminal 102 being located in a range closer to the device 101 than the first range condition. An example of the first range condition is that the user terminal 102 is deemed to be approaching the entrance of the building where the device 101 is located, but not approaching the entrance of the room where the device 101 is located. An example of a range that satisfies the first range condition is that the user terminal 102 can receive a beacon signal from the transmitter 104 at the entrance of the building, but not from the transmitter 104 at the entrance of the room. An example of the second range condition is that the user terminal 102 is deemed to be approaching the entrance of the room where the device 101 is located. An example of a range that satisfies the second range condition is that the user terminal 102 can receive a beacon signal from the transmitter 104 at the entrance of the room. Then, after the initial push notification has been sent, if the user terminal 102 is located within the range that satisfies the first range condition but does not satisfy the second range condition, the control unit 507 will send another push notification to the user terminal 102. Subsequently, if the user terminal 102 is located within the range that satisfies the second range condition, the control unit 507 will send another push notification to the user terminal 102. In this case, the user can be made aware that they are approaching the device 101 in stages.

[0096] In this disclosure, the location of device 101 is determined by the user terminal 102 when beacon signals transmitted from device 101 or transmitter 104 are received by the user terminal 102, but this is not limited to this. For example, the positional relationship between user terminal 102 and device 101 may be determined by device 101 or user terminal 102 having GPS functionality, or by device 101 and user terminal 102 communicating via Wi-Fi®. In this case, the determination of whether user terminal 102 is located within a range that satisfies the range conditions (range condition, first range condition, second range condition) may be made by user terminal 102 or by device 101. Alternatively, the determination of whether user terminal 102 is located within a range that satisfies the range conditions (range condition, first range condition, second range condition) may be made by server device 103 notified by user terminal 102 or device 101 regarding the positional relationship between user terminal 102 and device 101. Even in these cases, the device 101 can cause the user terminal 102 to re-push notification via the server device 103, depending on whether the user terminal 102 is located within a range that satisfies the range conditions, first range conditions, second range conditions, etc.

[0097] Furthermore, the content of the push notification is not limited to the examples described above. The push notification may include information indicating the state described above as a state detected by the detection unit 505.

[0098] Furthermore, this disclosure describes the content of push notifications when device 101 is a multifunction printer. In this disclosure, the function provision system 1 provides push notifications with content appropriate to the type of device 101, such as a network router, surveillance camera, digital medical device, automobile, delivery box, locker, etc. For example, if device 101 is a car, the content of the push notification could include malfunctions of car parts (burnt-out lamps, flat tires, etc.), mileage, and warnings. Warnings could include warnings about increased risk of vehicle or part failure when the usage period after part replacement reaches a predetermined value, warnings about an upcoming vehicle inspection, and warnings that a predetermined period has passed since the last inspection. Furthermore, if device 101 is a delivery box or locker, the content of the push notification could include that there are delivered items or stored items inside, that the storage period has exceeded a predetermined value, or that device 101 has malfunctioned. In addition, delivery persons or storage persons may be able to register the contents of delivered items or stored items in the delivery box or locker. In this case, the content of the push notification may be determined according to the registered contents. For example, if the delivered items or stored items are food or beverages, the content of the push notification may be set to encourage the recipient to take out the food or beverages, taking into account that they have an expiration date.

[0099] Furthermore, the present invention also includes cases in which a software program that realizes the functions of the above-described embodiments is supplied directly from a recording medium or via wired / wireless communication to a system or device having a computer capable of executing the program, and the program is executed. Therefore, in order to realize the functional processing described above in relation to the present invention using a computer, the program code itself supplied to and installed on the computer also realizes the present invention. In other words, the computer program itself for realizing the functional processing of the present invention is also included in the present invention. In this case, the form of the program is not limited as long as it has the functionality of a program, such as object code, a program executed by an interpreter, or script data supplied to an OS. As a recording medium for supplying the program, for example, a hard disk, a magnetic recording medium such as magnetic tape, an optical / magneto-optical storage medium, or a non-volatile semiconductor memory may be used. Furthermore, as a method of supplying the program, a method can be considered in which a computer program forming the present invention is stored on a server on a computer network, and a connected client computer downloads the computer program and programs it. Furthermore, based on the instructions of the program code, an operating system or similar device running on the computer may perform some or all of the actual processing, thereby realizing each of the functions of the embodiment described above. In addition, the program code read from the storage medium may be written to the memory of a function expansion board inserted into the computer or a function expansion unit connected to the computer. Then, based on the instructions of that program code, a CPU or similar device in that function expansion board or function expansion unit may perform some or all of the actual processing. Even in this case, each of the functions of the embodiment described above will be realized.

[0100] This embodiment includes the following configuration. (Composition 1) A first acquisition means for acquiring process information indicating a verification process for verifying the resolution of problems that occurred in the processing of the equipment, A second acquisition means for acquiring information indicating the verification process which is identified as essential for the verification in accordance with the results identified as the cause of the aforementioned problem, A third acquisition means for acquiring information indicating an alternative process to replace the verification process, A control means for displaying information about the alternative process when the verification process identified from the process information acquired by the first acquisition means includes an alternative process which is a verification process that is not essential for the verification and can be replaced by the alternative process, An information provision system equipped with the necessary features. (Configuration 2) The process to be replaced is a process that requires direct operation of the equipment, The information provision system according to Configuration 1, wherein the alternative process is performed by operating other devices connected to the device via a network, without requiring direct operation of the device. (Composition 3) The substitute process is a process that requires inputting user information relating to the user of the equipment into another device. The information provision system according to configuration 1 or 2, wherein the alternative process is a process that does not require the input of user information. (Composition 4) The information provision system according to any one of configurations 1 to 3, wherein the control means restricts the display of information indicating the substitute process when displaying the information relating to the substitute process. (Composition 5) The control means displays the information relating to the alternative process together with the information indicating the alternative process, according to any one of configurations 1 to 4. (Composition 6) The information provision system according to any one of configurations 1 to 5, wherein the control means, when displaying the information relating to the alternative process, displays the information relating to the alternative process in a different color from the information relating to the verification process, or displays information indicating that the alternative process is a substitute for the process being replaced. (Composition 7) The information provision system according to any one of configurations 1 to 6, wherein the control means displays information relating to the alternative process, and displays information relating to the difference between the operations included in the alternative process and the operations included in the alternative process.

[0101] Although the present invention has been described in detail above based on its preferred embodiments, the present invention is not limited to the above embodiments, and various modifications are possible in accordance with the spirit of the present invention, and these modifications are not excluded from the scope of the present invention. [Explanation of symbols]

[0102] 1...Function provision system, 101...Equipment, 102...User terminal, 103...Server device

Claims

1. A notification means that, when the device is in a state that satisfies predetermined state conditions, sends a push notification to a user terminal that has installed software as a progressive web application for providing information about the said state, After a push notification has been sent to the user terminal by the notification means, if the user terminal is located within a range that satisfies predetermined range conditions relative to the device, a re-notification means is provided to send another push notification to the user terminal. A network device characterized by having the following features.

2. The network device according to claim 1, further comprising control means for causing the user terminal to start the software as a progressive web application when the re-notification means causes the user terminal to send another push notification, if the user terminal has not started the software as a progressive web application.

3. The network device according to claim 2, characterized in that the control means starts the software as a progressive web application on the user terminal, on the condition that a predetermined operation is performed on the user terminal by the user.

4. The aforementioned state conditions include a first state condition and a second state condition that is different from the first state condition. The network device according to claim 1, characterized in that the re-notification means causes the user terminal located at a location satisfying the range condition to send another push notification when the device is in the state that satisfies the first state condition, and restricts further push notifications to the user terminal located at a location satisfying the range condition when the device is in the state that satisfies the second state condition.

5. The system further includes a control means for displaying a reception screen that accepts a selection of which of the aforementioned states satisfies the first state condition, The network device according to claim 4, characterized in that the reception screen displays information recommending that a specific state be selected as the state that satisfies the first state condition.

6. The network device according to claim 1, wherein the re-notification means restricts further push notifications to the user terminal when the user terminal is located within the range that satisfies the range condition after a push notification has been made to the user terminal, and the device itself is in the state that does not satisfy the state condition.

7. The network device according to claim 1, characterized in that the re-notification means restricts further push notifications to the user terminal even if the user terminal is located within the range that satisfies the range conditions, if a predetermined amount of time has not elapsed since the push notification was sent to the user terminal.

8. The network device according to claim 1, characterized in that the information pushed to the user terminal by the re-notification means includes at least one of the following: information regarding the start time when the device itself entered a state that satisfies the state condition; information corresponding to the time elapsed since the device entered the state that satisfies the state condition; and information corresponding to the number of times a push notification has been made to the user terminal.

9. The aforementioned range conditions include a first range condition and a second range condition which is defined as the user terminal being located within a range closer to the device than the first range condition. The aforementioned re-notification means is, After a push notification has been sent to the user terminal by the notification means, if the user terminal is located within the range that satisfies the first range condition but does not satisfy the second range condition, the push notification is sent to the user terminal again. The network device according to claim 1, characterized in that, after a push notification is sent to the user terminal in response to the user terminal being located in a range that satisfies the first range condition but does not satisfy the second range condition, the network device is sent to the user terminal again when the user terminal is located in a range that satisfies the second range condition.

10. The process includes: when a network device is in a state that satisfies predetermined state conditions, a push notification is sent to a user terminal that has installed software as a progressive web application for providing information about the said state; After a push notification has been sent to the user terminal, if the user terminal is located within a range that satisfies predetermined range conditions for the network device, the step of sending another push notification to the user terminal, A method having

11. On the computer, A function that, when a network device is in a state that meets predetermined state conditions, sends a push notification to a user terminal that has installed software as a progressive web application to provide information about the said state. A function to send another push notification to the user terminal if, after a push notification has been sent to the user terminal, the user terminal is located within a range that satisfies predetermined range conditions relative to the network device, A program to achieve this.

Images