Program and information processing system

Abstract

To provide a program and an information processing system for associating a specific facility with an information device.SOLUTION: A program causes a computer to execute a process including associating a meeting room 32 with a first MFP 18A based on a combination of a utilization time at which a user UR uses the meeting room 32 and a use time at which an information device used by the user UR is used before the utilization time, and a predetermined determination criterion.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a program and an information processing system. [Background technology]

[0002] For example, Patent Document 1 discloses a system including a plurality of client terminals and a receiving service system that receives data from the plurality of client terminals, the receiving service system having a first receiving means that receives data that is subject to predetermined processing, and a second receiving means that receives data that is not subject to the predetermined processing. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-144763 Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure aims to provide a program and an information processing system that associate a specific facility with an information device. [Means for solving the problem]

[0005] The program of the first aspect causes a computer to associate a specific facility with an information device based on a combination of the time when a user used the specific facility and the time when the user used an information device before the time when the user used the specific facility, and based on predetermined judgment criteria.

[0006] The program of a second aspect is the program according to the first aspect, and further includes acquiring a usage time when an information device located within a predetermined range from the specific facility was used.

[0007] The program of the third aspect is a program according to the first or second aspect, in which the time of use is obtained together with identification information from the usage history of the information device, and the time of use is combined with the time of use if the identification information satisfies a predetermined condition.

[0008] A fourth aspect of the program is the program according to any one of the first to third aspects, wherein the associating is performed based on a predetermined number or more of the combinations.

[0009] A fifth aspect of the program is the program according to the fourth aspect, wherein when the time elapsed from the use time to the use time falls within a predetermined time range, the use time and the use time are combined.

[0010] A sixth aspect of the program is the program according to the fifth aspect, wherein when the number of the combined combinations is less than a predetermined number, the time range of the predetermined elapsed time is changed.

[0011] A seventh aspect of the program is a program described in any one of the fourth to sixth aspects, wherein the predetermined judgment criteria include a degree of association between the specific facility and the information device, determined based on the attributes of the user in the combination.

[0012] The program of the eighth aspect causes a computer to execute the following steps: when a person who plans to use the specific facility registers a process to be performed using any information device including the information device, determine the information device to perform the process based on the result obtained by the association described in any one of the first to seventh aspects.

[0013] The information processing system of the ninth aspect includes a processor, and the processor performs the process of associating the specific facility with the information device based on a combination of the usage time when a user used the specific facility and the usage time when the information device used by the user before the usage time, and predetermined judgment criteria. [Effects of the Invention]

[0014] According to the program of the first aspect, it is possible to associate a specific facility with an information device.

[0015] According to the program of the second aspect, it is possible to reduce the risk of associating information devices with low relevance with a specific facility, compared to when attempting to associate all information devices.

[0016] According to the program of the third aspect, the risk of associating information devices with low relevance with specific facilities can be reduced compared to when association is performed based on combinations regardless of the identification information contained in the usage history.

[0017] According to the program of the fourth aspect, the risk of associating information devices with low relevance with a specific facility can be reduced compared to when association is performed even when the number of combinations does not meet a predetermined number.

[0018] According to the program of the fifth aspect, it is possible to reduce the risk of associating an information device with low relevance with a specific facility, compared to when the association is performed regardless of the amount of time that has passed.

[0019] According to the program of the sixth aspect, it is possible to reduce the risk of associating an information device with low relevance with a specific facility, compared to when association is performed regardless of the number of combinations.

[0020] According to the program of the seventh aspect, it is possible to reduce the risk of associating an information device with low relevance with a specific facility, compared to when association is performed regardless of the attributes of the user.

[0021] According to the program of the eighth aspect, even if a person who intends to use the facility does not know the information device associated with the facility, the person who intends to use the facility can use the information device associated with the facility.

[0022] According to the information processing system of the ninth aspect, it is possible to associate a specific facility with an information device. [Brief explanation of the drawings]

[0023] [Figure 1] FIG. 1 is a diagram illustrating an information output system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram illustrating a configuration of a cloud server according to an embodiment of the present disclosure. [Figure 3] FIG. 1 is a diagram illustrating an information processing system according to an embodiment of the present disclosure. [Figure 4] 10A and 10B are diagrams illustrating a procedure for associating a specific facility with an information device according to an embodiment of the present disclosure, and are diagrams illustrating examples of the locations of the specific facility and the information device. [Figure 5] FIG. 10 is a diagram illustrating MFP operation history data according to an embodiment of the present disclosure. [Figure 6] FIG. 10 is a diagram illustrating movement history data according to an embodiment of the present disclosure. [Figure 7] FIG. 10 is a diagram illustrating usage history data of a specific facility according to an embodiment of the present disclosure. [Figure 8] FIG. 10 is a flow diagram illustrating a procedure for estimating the position of a user operating an information device according to an embodiment of the present disclosure. [Figure 9] FIG. 10 is a diagram illustrating a location information list of an information device according to an embodiment of the present disclosure. [Figure 10] FIG. 10 is a flow diagram illustrating a procedure for estimating the position of an information device according to an embodiment of the present disclosure. [Figure 11] FIG. 10 is a diagram illustrating a user attribute information table according to an embodiment of the present disclosure. [Figure 12] FIG. 10 is a diagram illustrating an attribute coefficient table according to an embodiment of the present disclosure. [Figure 13A] 10 is a portion of a flow diagram illustrating a procedure for associating a specific facility with an information device according to an embodiment of the present disclosure. [Figure 13B] 13B is a portion of a flow diagram illustrating a procedure for associating a specific facility with an information device according to an embodiment of the present disclosure, following FIG. 13A. [Figure 14] FIG. 10 is a diagram illustrating an elapsed time evaluation table according to an embodiment of the present disclosure. [Figure 15] FIG. 10 is a diagram illustrating a procedure for calculating a relevance assessment table according to an embodiment of the present disclosure. [Figure 16] FIG. 10 is a diagram illustrating a calculation result of a relevance assessment table according to an embodiment of the present disclosure. [Figure 17] FIG. 10 is a diagram illustrating an association result table according to an embodiment of the present disclosure. [Figure 18] FIG. 10 is a flow diagram illustrating a procedure for causing an associated information device to execute processing when a user using a specific facility uses the information device, based on the association results obtained by the procedure for associating a specific facility with an information device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0024] An example of an embodiment of the present disclosure will be described below with reference to the drawings. In each drawing, the same or equivalent components and parts are designated by the same reference numerals. Furthermore, the dimensional proportions in the drawings are exaggerated for the sake of explanation and may differ from the actual proportions.

[0025] In the following description and drawings, a symbol indicated by adding a single alphabetic character to a number indicates that the symbol indicated by the same number alone is equivalent to a corresponding configuration. For example, "18A" and "18B" in FIG. 1 indicate that they are equivalent to the configuration indicated by "18." For this reason, a configuration indicated by adding a single alphabetic character may be named with a "first," "second," etc., to distinguish it from equivalent configurations. In other words, there may be multiple configurations corresponding to a symbol indicated by adding a single alphabetic character, not just those shown in the drawings.

[0026] In the following description, the term "user" refers to any person who uses the information output system or the information processing system according to this embodiment in some way, without being limited to a specific person. In other words, the term "user" includes people with different job titles, such as "officer" or "employee," and people who use only either the information output system or the information processing system.

[0027] [Embodiment] 1 shows an example of an information output system 10 according to this embodiment. As shown below, an overview of the information output system 10 and a method for preparing the same will be described.

[0028] 1. Overview of the information output system 1, an information output system 10 according to this embodiment includes a cloud server 14 connected to the Internet 16 and an MFP 18 (Multi Function Printer), which is an example of an information device. Also, as shown in FIG. 1, a user UR uses the information output system 10 by communicating with the cloud server 14 via the Internet 16.

[0029] As an example, MFP 18 is located at a first location 42 where a local network 40 is installed. As shown in FIG. 1 , multiple MFPs 18 are connected to local network 40. MFP 18 has a function of accepting a print job via Internet 16 and forming an image on a document, and a function of reading the image from the document as image data and transmitting it to cloud server 14. In the following description, MFP 18 may have any configuration as long as it is connectable to cloud server 14 via Internet 16, and it does not matter whether MFP 18 is a homogeneous device or a heterogeneous device.

[0030] 2 is a block diagram showing the configuration of the main parts of cloud server 14 in this embodiment. Note that cloud server 14 basically has the same configuration as a general computer.

[0031] The cloud server 14 includes a CPU 91 (Central Processing Unit), a ROM 93 (Read Only Memory), a RAM 92 (Random Access Memory), a communication unit 94, and the like.

[0032] The CPU 91 is a device that controls the overall operation of the cloud server 14, and is an example of a "processor" in this embodiment. The ROM 93 stores various control programs, various parameters, etc. in advance. The RAM 92 is used as a work area when the CPU 91 executes various programs. The communication unit 94 is connected to the Internet 16 (see FIG. 1 ), and transmits and receives various data to and from other devices connected to the Internet 16, such as the movement history recording unit 26, operation history recording unit 28, usage history recording unit 24, and MFP 18. The various units of the cloud server 14 are connected to one another by a bus (not shown).

[0033] In cloud server 14, CPU 91 accesses ROM 93 and RAM 92 and executes processing in accordance with the contents of the program. Furthermore, cloud server 14 controls the transmission and reception of communication data via communication unit 94 using CPU 9152A. Note that cloud server 14 may be connected to Internet 16 in any manner as long as it is capable of communicating with MFP 18.

[0034] 1, the user UR is at a second location 44 that is outside the range of the local network 40 of the first location 42 and is a location distant from the first location 42, such as between a head office and a branch office, or between a permanent location and a remote location. For the user UR at the second location 44, the first location 42 is a place where the presence or absence of information devices, the structure of the facilities, etc. cannot be known in detail.

[0035] In this embodiment, user UR transmits document data PD from second location 44 to cloud server 14 to use one of the MFPs 18 located at first location 42. Next, after transmitting document data PD to cloud server 14, user UR moves from second location 44 to first location 42. Then, at first location 42, user UR receives printed matter PT with document data PD attached from first MFP 18A, which has been determined as the MFP 18 that will output document data PD by the process executed by cloud server 14.

[0036] As described above, in the information output system 10 of this embodiment, the user UR does not specify a specific MFP 18, and the cloud server 14 executes processing to determine one of the multiple MFPs 18. Here, a method by which the information output system 10 according to this embodiment determines one of the MFPs 18 will be described, including a preparation method therefor, with reference to FIGS. 3 to 18 as appropriate.

[0037] 2. Information Processing System Configuration Fig. 3 is a diagram showing the configuration of an information processing system 12 according to this embodiment, which is responsible for the preparation method for the information output system 10. Fig. 4 is a diagram showing an example of the locations of a specific facility and information devices according to this embodiment. The "specific facility" described in this embodiment is, for example, the first conference room 32A, which is part of the interior of the building 30.

[0038] As shown in FIG. 4, the interior of building 30 is partitioned by walls into a first office room 33A, a second office room 33B, a first conference room 32A, a second conference room 32B, and an executive office 34. The MFPs 18 are located at a distance from one another. As shown in FIG. 4, first conference room 32A is larger than second conference room 32B, and therefore first conference room 32A is used more frequently than second conference room 32B. Therefore, as shown by footprints FP, a user UR who uses first conference room 32A prints a document on first MFP 18A and then enters first conference room 32A with the printed matter PT. As shown in FIG. 4, second MFP 18B is installed near second conference room 32B, but is far from first conference room 32A, and therefore is used infrequently by users UR who use first conference room 32A.

[0039] The executive room 34 is adjacent to the first conference room 32A across a wall, and an executive MR is permanently stationed in the executive room 34. A third MFP 18C is also disposed inside the executive room 34. Therefore, the third MFP 18C is a device that is exclusively used by the executive MR among the users UR who use the building 30.

[0040] 3, the information processing system 12 according to this embodiment collects location information PI of a user UR who owns a mobile device 36. As shown in FIG. 3, the information processing system 12 is connected to a usage history recording unit 24, an operation history recording unit 28, and a movement history recording unit 26 via the Internet 16.

[0041] The operation history recording unit 28 records the usage history of each MFP 18 used by a person. More specifically, as shown in FIG. 5, the operation history recording unit 28 records MFP operation history data 48 for each MFP 18. As shown in FIG. 5, the MFP operation history data 48 records, for example, a "user" indicating the user UR who used the MFP 18, a "printing date and time" indicating the date and time the MFP 18 was used, and a "file name" which is an example of identification information for the printed data. The "printing date and time" indicating the date and time the MFP 18 was used is an example of a "time of use" in this embodiment. As shown in FIG. 5, a new record 49 is added to the MFP operation history data 48 each time the MFP 18 is used. That is, each record 49 is an example of a "usage history" in this embodiment.

[0042] As shown in Fig. 3, the movement history recording unit 26 records location information PI of a user UR who moves while carrying a mobile device 36. More specifically, as shown in Fig. 6, the movement history recording unit 26 records the location information PI of the mobile device 36 as movement history data 50. As an example, the movement history data 50 records the coordinates of "latitude," "longitude," and "altitude," which are the location information PI of the mobile device 36, and the "time" when the location information PI was acquired.

[0043] As shown in FIG. 7 , the usage history recording unit 24 records the date and time of use by a person who used the conference room 32. More specifically, as shown in FIG. 7 , the usage history recording unit 24 records the usage history for each conference room 32 as usage history data 54. For example, the usage history data 54 records a "user," who is a person who used the conference room 32, and the date and time the conference room 32 was used. Also, as shown in FIG. 7 , the usage history data 54 records a record 49 that is added each time the conference room 32 is used. Note that the method for recording the usage history data 54 is not particularly limited as long as the usage history data 54 records the time when the user UR was in the conference room 32. For example, the usage history data 54 records the date and time when the electronic lock of the conference room 32 was unlocked when the user UR used the conference room 32. In other words, the electronic lock creates the usage history data 54 of the user UR's use of the conference room 32.

[0044] 3. Method for estimating MFP installation location Next, a method in which the CPU 91 of the cloud server 14 in this embodiment estimates the installation location of the MFP 18 will be described with reference to Fig. 8 to Fig. 10. As shown in Fig. 8 and Fig. 10, the cloud server 14 in this embodiment executes a procedure for acquiring location information that can be estimated as location information of the MFP, and a procedure for estimating the installation location of the MFP from multiple pieces of location information.

[0045] (Procedure for acquiring location information that can be estimated as MFP location information) Fig. 8 shows, as processing executed by the CPU 91 according to this embodiment, a procedure for acquiring location information that can be estimated as the location information of the MFP based on the MFP operation history data 48 of the MFP 18 and the movement history data 50 of the user UR. Fig. 9 also shows that the location information PI of the MFP 18 estimated based on the movement history data 50 is recorded as an MFP location information list 52. As shown in Fig. 9, the MFP location information list 52 for the MFP 18 records the location information PI estimated as the actual location of each MFP 18. The MFP location information list 52 for the MFP 18 is also recorded for each MFP 18. Here, as an example, the process of generating the record enclosed in a bold frame in Fig. 9 (record No. 257) will be described.

[0046] First, in step S102, CPU 91 acquires the job history of MFP 18. More specifically, CPU 91 acquires MFP operation history data 48 of any of MFPs 18 shown in Fig. 5 from operation history recording unit 28. Here, as an example, as shown in Fig. 5, CPU 91 acquires first MFP operation history data 48A, which is the operation history of first MFP 18A. Then, CPU 91 proceeds to step S104.

[0047] Next, in step S104, the CPU 91 extracts record 49 included in the job history of MFP 18 acquired in step S102, and acquires the user name and usage date and time included in record 49. Here, as shown in Fig. 5, the CPU 91 extracts record 49 surrounded by a bold frame from among the records 49 included in the MFP operation history data 48, and acquires that the user name is "User A" and the print date and time is "2024-02-13 20:27:23". The CPU 91 then proceeds to step S106.

[0048] Next, in step S106, the CPU 91 acquires the movement history of the user UR acquired in step S104 from the movement history recording unit 26. More specifically, the CPU 91 acquires the movement history data 50 corresponding to the user UR name acquired in step S104 from the movement history recording unit 26. Here, as shown in FIG. 6, the CPU 91 acquires the movement history data 50 of "user A" from the movement history recording unit 26. Then, the CPU 91 proceeds to step S108.

[0049] Next, in step S108, the CPU 91 acquires location information PI immediately before the date and time of use from the acquired movement history data 50. More specifically, the CPU 91 acquires, from the records 49 included in the movement history data 50, the record 49 for the time immediately before the date and time of use acquired in step S104. Here, as shown in FIG. 6, the CPU 91 extracts, from the movement history data 50, the record 49 surrounded by a bold frame, which includes the value "2024-02-13 20:23:45", which is immediately before the time acquired in step S104. The CPU 91 also acquires, as location information PI, the latitude, longitude, and altitude of the location of user A in the record 49. The CPU 91 then proceeds to step S110.

[0050] Next, in step S110, the CPU 91 adds the acquired location information PI of the user UR to the MFP location information list 52 as shown in Fig. 9. More specifically, the CPU 91 adds the location, longitude, and altitude acquired in step S108 to the MFP location information list 52. Here, as shown in Fig. 9, the CPU 91 adds the location information PI of the user A acquired in step S108 as the record surrounded by a thick frame in the MFP location information list 52 of the first MFP 18A selected in step S102.

[0051] In the above-described procedure, CPU 91 acquires position information PI that can be estimated as position information PI of MFP 18, and creates MFP position information list 52 of MFP 18. Note that created MFP position information list 52 is recorded in ROM 93 of cloud server 14, for example.

[0052] Note that the procedure for acquiring location information that can be estimated as the location information of the MFP in this description is not performed just once, but is performed as many times as the number of records included in MFP operation history data 48. Also, the procedure for acquiring location information that can be estimated as the location information of the MFP in this description is not performed just once, but is performed for each MFP 18 whose operation history recording unit 28 includes MFP operation history data 48.

[0053] (Procedure for estimating the installation location of an MFP from multiple pieces of location information) 10 shows a procedure for estimating the installation location of an MFP from multiple pieces of location information as processing executed by CPU 91 according to this embodiment. Note that, here, an example will be described in which the processing is executed in a state in which multiple records are recorded in MFP location information list 52.

[0054] First, in step S202, the CPU 91 acquires the MFP position information list 52 of the MFP 18. More specifically, the CPU 91 acquires the MFP position information list 52 of the MFP 18, which was recorded in step S110, from the ROM 93. Then, the CPU 91 proceeds to step S204.

[0055] Next, in step S204, the CPU 91 extracts a predetermined number of records from the MFP location information list 52 of the MFP 18. More specifically, the CPU 91 extracts multiple records with newer recording dates and times (records with larger No. values) from the location information PI log. Then, the CPU 91 proceeds to step S206.

[0056] Next, in step S206, the CPU 91 calculates the median value of latitude from the records extracted in step S204. More specifically, the CPU 91 acquires the latitude for each record extracted in step S204, and calculates the median value when the acquired latitude values ​​are arranged in order. For example, if records No. 255 to No. 259 in FIG. 9 are extracted, the value "35° 41' 19.49" N" of No. 258 in FIG. 9 is calculated. Then, the CPU 91 proceeds to step S208.

[0057] Next, in step S208, the CPU 91 calculates the median value of the longitudes from the records extracted in step S204. More specifically, the CPU 91 acquires the longitude for each record extracted in step S204, and calculates the median value when the acquired longitude values ​​are sorted in order. For example, if records No. 255 to No. 259 in FIG. 9 are extracted, the value "139°42'16.33"E" of No. 259 in FIG. 9 is calculated. Then, the CPU 91 proceeds to step S210.

[0058] Next, in step S210, the CPU 91 calculates the median value of the altitude from the records extracted in step S204. More specifically, the CPU 91 obtains the altitude for each record extracted in step S204, and calculates the median value when the obtained altitude values ​​are sorted in order. For example, if records No. 255 to No. 259 in FIG. 9 are extracted, the value "15.41 m" for No. 257 in FIG. 9 is calculated. The CPU 91 then proceeds to step S212.

[0059] Next, in step S212, the CPU 91 estimates the latitude, longitude, and altitude calculated in steps S206 to S210 as the position of the MFP 18. More specifically, the CPU 91 estimates the position indicated by "35°41'19.50"N," "139°42'16.33"E," and "15.41 m," calculated in the respective procedures described above, as the installation position of the first MFP 18A.

[0060] In this way, the CPU 91 estimates the installation position of the MFP 18 from the multiple pieces of position information PI. Note that, in the above procedure, the CPU 91 has been described taking an example of estimating the installation position of the first MFP 18A, but the CPU 91 similarly estimates the installation positions of the other MFPs 18. In addition, the estimated installation positions of the MFPs 18 are recorded in the ROM 93 of the cloud server 14, for example.

[0061] In the above procedure, the installation location of the MFP 18 has been described as an example of an information device, but the object from which the position information PI is acquired is not limited to an MFP. That is, the position information PI of the conference room 32 may also be estimated in a similar manner based on the usage history data 54 of the conference room 32 shown in FIG. 7 and the movement history data 50 shown in FIG. 6. In other words, in the conference room 32 shown in FIG. 4, the device that creates the usage history data 54 of the conference room 32 (the electronic lock in the example described above) is also an example of an information device in this embodiment. The object from which the position information PI is acquired may also be the conference room. That is, the object from which the position information PI is acquired is not limited to an information device.

[0062] Furthermore, there is no particular limitation on when the CPU 91 executes the procedure for estimating the installation location of the MFP 18. For example, the CPU 91 may execute the procedure periodically or when it determines that the MFP 18 has been added to the network.

[0063] When the estimation is performed periodically, it is assumed that the CPU 91 estimates the installation location of the MFP 18, for example, on the same date every month. When the estimation is performed when it is determined that the MFP 18 has been added to the network, it is assumed that the CPU 91 estimates the installation location of the MFP 18, for example, when it determines that a connection to the network has been established for the new MFP 18. Similarly, it is assumed that the estimation of the installation location of the MFP 18 is performed when it determines that a connection to the network has been established again after the MFP 18 has been disconnected from the network. By performing the estimation at these times, even if the installation location of the MFP 18 has been changed, the CPU 91 will estimate the new installation location of the MFP 18 by performing the estimation periodically.

[0064] In the above description, the installation location of MFP 18 is estimated based on MFP location information list 52, but the operation of CPU 91 in this embodiment is not limited to this. For example, when CPU 91 determines that user UR has operated MFP 18 to execute a print job, CPU 91 may determine the installation location of MFP 18 based on location information PI of portable device 36 carried by the user who operated MFP 18.

[0065] 4. Associating the conference room with the MFP 4, when a printed matter PT is created from an MFP 18 when using a conference room 32, it is preferable that the MFP 18 that executes the print job be associated with the conference room 32. For example, in the example of FIG. 4, if a user UR using the conference room 32 is not an executive, it is difficult for the user UR to create a printed matter PT using a third MFP 18C located inside the executive room 34.

[0066] Here, the CPU 91 of the information processing system 12 according to this embodiment associates the installation position of the MFP 18 estimated in the above process with the conference room 32. The procedure for associating the conference room 32 with the MFP 18 will be described with reference to FIGS.

[0067] (Setting user attribute similarity) 11 shows a user attribute information table 56 in this embodiment, which associates the names of users UR who use the MFP 18 with the attributes of the users UR. The user attribute information table 56 records the names of users in association with the attributes of the users (including job titles, etc.). In other words, "employee" and "officer" are examples of user attributes in this embodiment. The user attribute information table 56 is, for example, recorded in the ROM 93 of the cloud server 14.

[0068] 12 shows an attribute coefficient table 58 in this embodiment that associates the attributes of a user UR who uses the MFP 18 with the similarity (approximation) between other attributes. For example, the first attribute coefficient table 58A records, as a coefficient, the degree to which other attributes are similar to the attribute of "employee." For example, FIG. 12 shows that, because "employee" and "executive" have different job titles, the coefficient of "executive" is set to be small. That is, in this embodiment, the relationship between the attributes and coefficients combined in the attribute coefficient table 58 is an example of the degree of relevance in this embodiment. In addition, the user attribute information table 56 is, for example, recorded in the ROM 93 of the cloud server 14.

[0069] As shown in Figure 12, the similarity of one attribute to the other does not have to be the same, the reason for which will be explained later.

[0070] 13A to 17, a method in which the CPU 91 in this embodiment associates the MFP 18 with the conference room 32 will be described. The CPU 91 in this embodiment executes a procedure for associating the MFP with the conference room based on the time when the MFP 18 was used and the time when the conference room 32 was used.

[0071] (Procedure for associating an MFP with a conference room) 13A and 13B show a procedure in which CPU 91 in this embodiment associates MFP 18 with conference room 32 based on the time when MFP 18 was used and the time when conference room 32 was used. In this explanation, the time when MFP 18 was used and the time when conference room 32 was used are assumed to be the same as those shown in Figures 5 and 7. In this embodiment, it is assumed that the specific location of conference room 32 is estimated by applying mutatis mutandis the procedure for acquiring location information that can be estimated as the location information of the MFP and the procedure for estimating the installation location of the MFP from multiple pieces of location information in the above explanation.

[0072] First, in step S302, the CPU 91 acquires usage history data 54 of a specific conference room 32. More specifically, the CPU 91 acquires MFP operation history data 48 of any of the conference rooms 32 shown in FIG. 7 from the usage history recording unit 24. Here, as an example, as shown in FIG. 7, the CPU 91 acquires first usage history data 54A, which is the usage history of the first conference room 32A. Then, the CPU 91 proceeds to step S304.

[0073] Next, in step S304, the CPU 91 extracts a record included in the usage history of the conference room 32 acquired in step S302, and acquires the user name and usage date and time included in the record. Here, as shown in FIG. 7, the CPU 91 extracts the record surrounded by a bold frame from the records included in the first usage history data 54A, and acquires that the user name is "User A" and the usage date and time is "2024-02-13 20:29:45." Note that in this embodiment, the usage date and time in the usage history data 54 is an example of the "usage time" in this embodiment. Then, the CPU 91 proceeds to step S306.

[0074] Next, in step S306, the CPU 91 acquires all MFP operation history data 48 of MFPs 18 located within a designated range from the conference room 32 designated in step S302. Note that the designated range may be set in any manner as long as it includes location information PI of the conference room 32, i.e., the range expected to be used by a user UR who uses the conference room 32, such as the distance relative to the latitude, longitude, and altitude of the conference room 32. Here, the designated range is defined based on the distance relative to the latitude and longitude of the conference room 32, thereby including the first MFP 18A, the second MFP 18B, and the third MFP 18C. As a result, the CPU 91 acquires MFP operation history data 48 of the first MFP 18A, the second MFP 18B, and the third MFP 18C from the operation history recording unit 28, as shown in FIG. 5. Then, the CPU 91 proceeds to step S308.

[0075] Next, in step S308, CPU 91 extracts records 49 that are expected to be used in conference room 32 from the acquired MFP operation history data 48. More specifically, CPU 91 extracts records 49 that are expected to be used in conference room 32 based on file name FN included in MFP operation history data 48. Then, CPU 91 proceeds to step S310.

[0076] Next, in step S310, the CPU 91 further extracts records 49 whose user name matches the user name from the extracted records 49. More specifically, the CPU 91 extracts records 49 whose user name matches the user name of "User A" acquired in step S304 from the records 49 extracted in step S308. The CPU 91 then proceeds to step S312.

[0077] Next, in step S312, the CPU 91 further identifies, from among the acquired records 49, the record 49 whose print date and time is immediately before the usage date and time. More specifically, from among the records 49 extracted in step S310, the CPU 91 identifies the record 49 whose print date and time is immediately before "2024-02-13 20:29:45" acquired in step S304. Through this procedure, the record 49 surrounded by a thick frame shown in FIG. 5 is extracted. Then, the CPU 91 proceeds to step S314.

[0078] Next, in step S314, the CPU 91 determines whether the elapsed time from the print date and time of the identified record 49 to the use date and time is within a threshold range. More specifically, the CPU 91 calculates the time elapsed from the print date and time of the record 49 identified in step S312 to the use date and time of the record 49 extracted in step S304. In this case, the calculated time is 142 seconds. If the CPU 91 makes a positive determination in step S314, the process proceeds to step S316. On the other hand, if the CPU 91 makes a negative determination in step S314, the process proceeds to step S318.

[0079] The threshold for the elapsed time is set appropriately based on the expected time that will elapse from when the document is printed until the conference room 32 is used. For example, if the MFP 18 is far from the conference room 32, the elapsed time is expected to be long, and therefore the threshold is set large; if the MFP 18 is close to the conference room 32, the elapsed time is expected to be short, and therefore the threshold is set small.

[0080] Next, in step S316, the CPU 91 refers to the user attributes and then adds a record to the elapsed time evaluation table 60. More specifically, by referring to the user attribute information table 56, the CPU 91 acquires that the attribute of "User A", the user acquired in step S304, is "Employee". Then, as shown in FIG. 14, the CPU 91 adds a record to the elapsed time evaluation table 60, together with the user attributes and the name of the MFP 18. Then, the CPU 91 proceeds to step S318.

[0081] Next, in step S318, the CPU 91 determines whether there are any usage history records that have not been extracted in step S304. If the CPU 91 determines yes in step S318, it proceeds to step S304. On the other hand, if the CPU 91 determines no in step S318, it proceeds to step S320.

[0082] Next, in step S320, the CPU 91 temporarily stores the elapsed time evaluation table 60 created up to step S318 in the RAM 92. More specifically, the CPU 91 temporarily stores the elapsed time evaluation table 60 having a plurality of records as shown in Fig. 14 in the RAM 92. Then, the CPU 91 proceeds to step S322.

[0083] Next, in step S322, the CPU 91 determines the number of records contained in the elapsed time evaluation table 60 created up to step S318. If the CPU 91 determines that the number of records contained in the elapsed time evaluation table 60 is appropriate, the process proceeds to step S330. If the CPU 91 determines that the number of records contained in the elapsed time evaluation table 60 is too large, the process proceeds to step S324. If the CPU 91 determines that the number of records contained in the elapsed time evaluation table 60 is too small, the process proceeds to step S326. If the CPU 91 determines that the number of records contained in the elapsed time evaluation table 60 is too small and has never made a negative determination in step S314, the process of associating the MFP 18 with the conference room 32 ends.

[0084] Next, in step S324, the CPU 91 narrows the range of the threshold for the elapsed time from the print date and time to the use date and time. More specifically, the CPU 91 narrows the range of the threshold referenced in step S314, thereby increasing the frequency of negative determinations in step S314. Then, the CPU 91 proceeds to step S328.

[0085] Next, in step S328, the CPU 91 initializes the elapsed time table temporarily stored in step S320. In other words, the CPU 91 deletes all records added in step S320. Then, the CPU 91 proceeds to step S302.

[0086] In step S326, the CPU 91 expands the range of the threshold for the elapsed time from the print date and time to the use date and time. More specifically, the CPU 91 expands the range of the threshold referenced in step S314, thereby increasing the frequency of positive determinations in step S314. The CPU 91 then proceeds to step S328.

[0087] Then, in step S330, the CPU 91 acquires the attribute coefficient table 58. More specifically, the CPU 91 acquires the user attribute information table 56 from the ROM 93. Then, the CPU 91 proceeds to step S332.

[0088] Next, in step S332, the CPU 91 calculates the relevance evaluation table 62 for each attribute based on the elapsed time evaluation table 60 and the attribute coefficient table 58. More specifically, as shown in Fig. 15, the CPU 91 creates the relevance evaluation table 62 for each attribute for the records included in the elapsed time evaluation time table created up to step S318, based on the attributes and coefficients listed in the attribute coefficient table 58. Note that, as shown in Fig. 15, the relevance evaluation table 62 records, for each attribute, a combination of an "MFP name" and a "total score" indicating the evaluation result.

[0089] For example, FIG. 15 shows the state in which calculations are being performed for the first record and the second record in the elapsed time evaluation table 60. In the first record, the user attribute is "employee" and the 18 MFPs are "first MFPs." In the first attribute table, the coefficient for the "employee" attribute is "1.00," so 1.00 is added to the score for "first MFP" in the first relevance evaluation table 62A, which is the relevance evaluation table 62 for employee EE. In the second attribute table, the coefficient for the "employee" attribute is "0.20," so 0.20 is added to the score for "first MFP" in the second relevance evaluation table 62B, which is the relevance evaluation table 62 for executive MRs. Similarly, for the second record, 0.10 is added to the score for "third MFP" in the first relevance evaluation table 62A, and 1.00 is added to the score for "third MFP" in the second relevance evaluation table 62B.

[0090] In this way, in step S332, the CPU 91 performs the above calculations for the records in the elapsed time evaluation table 60, and creates the relevance evaluation table 62 for each attribute as shown in Fig. 16. Then, the CPU 91 proceeds to step S334.

[0091] Next, in step S334, the CPU 91 creates an association result table 64 in which the MFP 18 with the highest score in the relevance assessment table 62 for each attribute is associated with the conference room 32. More specifically, the CPU 91 determines the MFP 18 names with the highest scores for each attribute in the relevance assessment table 62 for each attribute calculated in step S332, as shown in bold in Fig. 16. Then, the CPU 91 enters the MFP 18 names with the highest scores for each attribute in the "MFP name" column of the association result table 64, as shown in Fig. 17.

[0092] Furthermore, the CPU 91 stores, as an example, the association result table 64 created in step S334 in the ROM 93. Then, the CPU 91 ends the procedure for associating the MFP 18 with the conference room 32.

[0093] By performing the above procedure up to step S334, the CPU 91 creates the association result table 64, thereby associating the MFP 18 with the conference room 32 for each attribute. For example, in Fig. 17, it is shown that the first conference room 32A and the first MFP 18A are associated with the user UR having the attributes of "employee," "employee of another branch office," and "guest user." Also, for example, in Fig. 17, it is shown that the first conference room 32A and the third MFP 18C are associated with the user UR having the attribute of "executive."

[0094] 12, in the present embodiment, in the first attribute coefficient table 58A corresponding to "employee," the attribute of "executive" is set so that the coefficient is the smallest for the attribute of "employee." In other words, the attribute of "executive" is set so that it has a lower similarity to the attribute of "employee" than the attributes of "employee employee at another branch office" and "guest user." As a result, an MFP 18 that is easily usable by a user UR of an "employee employee at another branch office" or a user UR with the attribute of "guest user" can be set as an MFP 18 that is easily usable by a user UR with the attribute of "employee."

[0095] Furthermore, in second attribute coefficient table 58B corresponding to "executive," the coefficient for the "employee" attribute is set to be small relative to the "executive" attribute, but is set to be larger than the coefficients for attributes of external persons such as "employee of another branch office" and "guest user." As a result, an MFP 18 that is easy to use for a user UR of an "employee of another branch office" or a user UR with the attribute of a "guest user" can be set as an MFP 18 that is difficult to use for a user UR with the attribute of an "executive" from the standpoint of security risks, etc. Similarly, an MFP 18 that is easy to use for a user UR with the attribute of an "employee" can be set as an MFP 18 that is somewhat easy to use for a user UR with the attribute of an "executive."

[0096] 5. Processing procedure by MFP Next, in this embodiment, when the CPU 91 receives document data PD from a user, a procedure for causing an MFP associated with a conference room to print the document data will be described with reference to Fig. 18. In other words, a procedure for a user UR to print document data PD using an MFP 18 associated with a conference room will be described.

[0097] (Procedure for printing document data to the MFP associated with the conference room) FIG. 18 shows a procedure in which the CPU 91 in this embodiment causes the MFP 18 to execute a print job based on the association result table 64 when a process for executing printing using the MFP 18 is registered.

[0098] First, in step S402, the CPU 91 attempts to acquire the association result table 64. More specifically, the CPU 91 attempts to acquire the association result table 64 created in step S334 in the procedure for associating the MFP 18 with the conference room 32 described above. Then, the CPU 91 proceeds to step S404.

[0099] Next, in step S404, the CPU 91 determines whether or not an association result table 64 exists. If the determination in step S404 is affirmative, the CPU 91 proceeds to step S406. On the other hand, if the determination in step S404 is negative, the CPU 91 ends the procedure for causing the MFP 18 associated with the conference room 32 to print the document data PD.

[0100] Next, in step S406, the CPU 91 identifies the attributes of the prospective user and the associated MFP 18. More specifically, when the CPU 91 receives a print job, it identifies the MFP 18 that corresponds to the attributes of the user UR who has registered the print job and who plans to use the first conference room 32A, by acquiring the MFP 18 from the association result table 64. Then, the CPU 91 proceeds to step S408.

[0101] Next, in step S408, the CPU 91 transmits the print job to the MFP 18 identified in step S406. In other words, by transmitting the print job to the MFP 18, the CPU 91 makes the MFP 18 available to the user UR who plans to use the conference room 32. Then, the CPU 91 ends the procedure of causing the MFP 18 associated with the conference room 32 to print the document data PD.

[0102] In step S408, the CPU 91 may notify the user UR who plans to use the MFP 18 of the MFP 18 that sent the print job. More specifically, the CPU 91 may notify the user UR who plans to use the MFP 18 of the MFP 18 that will output the printed matter PT by notifying the user UR's portable device 36 of the name of the MFP 18 that sent the print job.

[0103] According to the information output system 10 and the information processing system 12 described above in this embodiment, the following actions and effects can be obtained.

[0104] (Action and effect) The program according to this embodiment combines, in the cloud server 14, the usage date and time in the usage history data 54 when the user UR used the first conference room 32A and the printing date and time using the MFP 18 used by the user UR before the usage date and time in the usage history data 54. Then, based on the combination and predetermined criteria, the cloud server 14 is caused to associate the first conference room 32A with the MFP 18. Therefore, according to the program according to this embodiment, it is possible to associate the first conference room 32A with the associated MFP 18.

[0105] Furthermore, the program according to this embodiment causes cloud server 14 to acquire the usage dates and times in usage history data 54 for MFPs 18 located within a predetermined range from first conference room 32A. Therefore, according to the program according to this embodiment, it is possible to reduce the risk of associating an MFP 18 with low relevance with first conference room 32A, compared to when attempting to associate all MFPs 18.

[0106] Furthermore, the program according to this embodiment acquires the file name FN from the record 49 along with the print date and time, and if the file name FN satisfies a predetermined condition, combines the usage date and time in the usage history data 54 with the print date and time in the cloud server 14. Therefore, according to the program according to this embodiment, it is possible to reduce the risk of associating a less relevant MFP 18 with the first conference room 32A, compared to when association is performed based on a combination regardless of the file name FN included in the record 49.

[0107] Furthermore, the program according to this embodiment causes the cloud server 14 to execute the association when the number of combinations is equal to or greater than a predetermined number. The program according to this embodiment reduces the impact of records 49 that are to be removed from the association when, for example, an unexpected use is performed, compared to when the association is executed even when the number of combinations is less than the predetermined number. This reduces the risk of associating a less relevant MFP 18 with the first conference room 32A.

[0108] Furthermore, the program according to this embodiment causes cloud server 14 to associate first conference room 32A with MFP 18 when the elapsed time from the usage date and time to the printing date and time in usage history data 54 for the combination falls within a predetermined time range. Then, according to the program according to this embodiment, association is prioritized for an MFP 18 with a shorter time from the printing date and time to the usage date and time in usage history data 54, and with a higher degree of association. Therefore, compared to when association is performed regardless of the elapsed time, it is possible to reduce the risk of associating an MFP 18 with a low degree of association with first conference room 32A.

[0109] Furthermore, the program according to this embodiment causes the cloud server 14 to change the range of the elapsed time when the number of combinations is less than a predetermined number. The program according to this embodiment prevents the number of combinations from being too small to relatively suppress the influence of the record 49 to be removed from the association. Therefore, compared to when the association is performed regardless of the number of combinations, it is possible to reduce the risk of associating a less relevant MFP 18 with the first conference room 32A.

[0110] Furthermore, the program according to this embodiment causes the cloud server 14 to determine the association between the first conference room 32A and the MFP 18 based on the attributes of the users in the combination. According to the program according to this embodiment, when the MFPs 18s used for each user attribute are differentiated, it is possible to prevent a user UR with one attribute from being associated with an MFP 18 primarily used by a user UR with another attribute. Therefore, compared to when the association is performed regardless of the attributes of the user UR, it is possible to reduce the risk of associating an MFP 18 with low association with the first conference room 32A.

[0111] Furthermore, when it is determined that a user UR who plans to use the conference room 32 has registered document data PD, the program according to this embodiment causes the cloud server 14 to determine the MFP 18 that will execute the print job based on the result of the association. Therefore, according to the program according to this embodiment, even if the user UR who plans to use the conference room 32 does not know the MFP 18 associated with the first conference room 32A, the MFP 18 can be used.

[0112] Furthermore, the information processing system 12 according to this embodiment combines, in the cloud server 14, the usage date and time in the usage history data 54 when the user UR used the conference room 32 and the printing date and time using the MFP 18 used by the user UR before the usage date and time in the usage history data 54. Then, based on the combination and predetermined criteria, the cloud server 14 associates the first conference room 32A with the MFP 18. Therefore, the information processing system 12 according to this embodiment can associate the first conference room 32A with the associated MFP 18.

[0113] <Variations> In the above description, CPU 91 acquires usage history data 54 for MFPs 18 within a predetermined distance from conference room 32 as the predetermined range, but the operation of the program according to this embodiment is not limited to this. For example, CPU 91 may detect MFPs 18 connected to the same local network 40 from their IP addresses or the like to acquire usage history data 54 from the MFPs 18, and set the detected MFPs 18 as the target MFP.

[0114] In the above description, the CPU 91 combines the print date and time with the usage date and time of the conference room 32 when the file name FN in the usage history data 54 is considered to be for use of the conference room 32, but the operation of the program according to this embodiment is not limited to this. For example, the CPU 91 may combine the print date and time immediately preceding the usage date and time of the conference room 32 with the usage date and time of the conference room 32 without taking the file name FN into consideration.

[0115] In the above description, the CPU 91 creates the association result table 64 when the number of records in the elapsed time evaluation table 60 is within a predetermined range, but the operation of the program according to this embodiment is not limited to this. For example, the CPU 91 may create the association result table 64 regardless of the number of records in the elapsed time evaluation table 60.

[0116] In the above description, the CPU 91 adds a record to the elapsed time evaluation table 60 if the elapsed time from the printing date and time to the date and time the conference room 32 is used falls within a predetermined time range, but the operation of the program according to this embodiment is not limited to this. For example, the CPU 91 may combine the printing date and time immediately preceding the date and time the conference room 32 is used with the date and time the conference room 32 is used, regardless of the elapsed time from the printing date and time to the date and time the conference room 32 is used.

[0117] In the above description, the CPU 91 changes the range of the elapsed time from the printing date and time to the usage date and time of the conference room 32 when the number of records in the elapsed time evaluation table 60 is less than the predetermined number, but the operation of the program according to this embodiment is not limited to this. For example, the CPU 91 may create the association result table 64 without changing the range of the elapsed time even when the number of records in the elapsed time evaluation table 60 is less than the predetermined number.

[0118] In the above description, the CPU 91 uses the attribute coefficient table 58 to associate the conference room 32 with the MFP 18 for each user attribute to create the association result table 64, but the operation of the program according to this embodiment is not limited to this. For example, the CPU 91 may associate the conference room 32 with the MFP 18 regardless of the user attribute.

[0119] In the above description, when a user UR who plans to use conference room 32 sends document data PD to cloud server 14, a print job is sent to MFP 18 associated with conference room 32, but the operation of the program according to this embodiment is not limited to this. For example, the CPU 91 may automatically notify a user UR who plans to use conference room 32 of the MFP 18 associated with conference room 32, and send the print job when an input from user UR is received.

[0120] In the above description, the CPU 91 associates the conference room 32 with the MFP 18 and transmits a print job to the MFP 18 associated with the conference room 32, but the information processing system 12 according to the present embodiment is not limited to this. For example, the association of the conference room 32 with the MFP 18 and the transmission of a print job to the MFP 18 associated with the conference room 32 based on the contents of the association result table 64 may each be performed by separate processors.

[0121] In these modified examples, the same functions and effects as those described above can be obtained.

[0122] The above describes an embodiment of the present disclosure with reference to the accompanying drawings. However, it is clear that a person with ordinary knowledge in the field of technology to which the present disclosure pertains can conceive of various modifications or applications within the scope of the technical ideas set forth in the claims, and it is understood that these also naturally fall within the technical scope of the present disclosure.

[0123] Further preferred aspects of the present disclosure will be described below.

[0124] (((1))) Associating the specific facility with the information device based on a combination of a time when the user used the specific facility and a time when the user used the information device before the time when the user used the specific facility and a predetermined criterion for judgment; A program that causes a computer to execute the following.

[0125] (((2))) acquiring a usage time when an information device located within a predetermined range from the specific facility was used; The program described in (((1))).

[0126] (((3))) acquiring the time of use together with identification information from the usage history of the information device, and combining the time of use with the identification information when the identification information satisfies a predetermined condition; The program according to (((1))) or (((2))).

[0127] (((4))) performing the associating based on a predetermined number or more of the combinations; A program according to any one of (((1))) to (((3))).

[0128] (((5))) combining the use time and the use time when the elapsed time from the use time to the use time falls within a predetermined time range; The program according to (((4))).

[0129] (((6))) changing the time range of the predetermined elapsed time when the number of the combined combinations is less than a predetermined number; The program according to (((5))).

[0130] (((7))) the predetermined criteria include a degree of association between the specific facility and the information device, the degree being determined based on attributes of the users in the combination; A program according to any one of (((4))) to (((6))).

[0131] (((8))) When a person who plans to use the specific facility registers a process to be executed using any one of the information devices including the information device, determining the information device that will execute the process based on a result obtained by associating the information device according to any one of ((1))) to (((7))); A program that causes a computer to execute the following.

[0132] (((9))) a processor; Equipped with the processor associates the specific facility with the information device based on a combination of a usage time when the user used the specific facility and a usage time when the user used an information device before the usage time, and a predetermined determination criterion; An information processing system that executes the above.

[0133] According to the program (((1))), it is possible to associate a specific facility with an information device. According to the program of (((2))), it is possible to reduce the risk of associating information devices with low relevance with a specific facility, compared to when attempting to associate all information devices. According to the program (((3))), the risk of associating information devices with low relevance with a specific facility can be reduced compared to when association is performed based on a combination regardless of the identification information contained in the usage history. According to the program related to (((4))), the risk of associating information devices with low relevance with a specific facility can be reduced compared to when association is performed even when the number of combinations does not reach a predetermined number. According to the program of (((5))), the risk of associating an information device with low relevance with a specific facility can be reduced compared to when the association is performed regardless of the amount of time that has passed. According to the program of (((6))), the risk of associating information devices with low relevance with a specific facility can be reduced compared to when association is performed regardless of the number of combinations. According to the program of (((7))), the risk of associating an information device with low relevance with a specific facility can be reduced compared to when the association is performed regardless of the attributes of the user. According to the program (((8))), a person who intends to use the facility can use an information device associated with a specific facility even if he or she does not know the information device associated with the specific facility. According to the information processing system of (((9))), it is possible to associate a specific facility with an information device. [Explanation of symbols]

[0134] 10 Information Output System 12 Information processing system (an example of an information processing system) 14 Cloud Server 16. Internet 18 MFP (an example of information equipment) 24 Usage history recording section 26 Movement history recording section 28 Operation history recording section 30 Buildings 32 Conference Room (an example of a specific facility) 33 Room 34 Executive Room 36 Portable devices (examples of portable devices) 40 Local Network 42 First Place 44 Second Location 48 MFP operation history data 49 records (example of operation history) 50 Movement history data (Example of movement history data) 52 Log list (an example of multiple pieces of location information) 54 Usage history data 56 User attribute information data 58 Attribute Coefficient Table 60 Elapsed Time Evaluation Table 62 Relevance Assessment Table 64 Association result table (an example of the results obtained by association) 91 CPU (an example of a processor) 92 RAM 93 ROM 94 Communications Department

Claims

1. Associating the specific facility with the information device based on a combination of a time when the user used the specific facility and a time when the user used the information device before the time when the user used the specific facility and a predetermined criterion for judgment; A program that causes a computer to execute the following.

2. acquiring a usage time when an information device located within a predetermined range from the specific facility was used; The program according to claim 1 .

3. acquiring the time of use together with identification information from the usage history of the information device, and combining the time of use with the identification information when the identification information satisfies a predetermined condition; The program according to claim 1 .

4. performing the associating based on a predetermined number or more of the combinations; The program according to claim 1 .

5. combining the use time and the use time when the elapsed time from the use time to the use time falls within a predetermined time range; The program according to claim 4.

6. changing the time range of the predetermined elapsed time when the number of the combined combinations is less than a predetermined number; The program according to claim 5 .

7. the predetermined criteria include a degree of association between the specific facility and the information device, the degree being determined based on attributes of the users in the combination; The program according to claim 4.

8. When a person who is planning to use the specific facility registers a process to be executed using any one of the information devices including the information device, determining an information device to execute the process based on a result obtained by associating the information device according to any one of claims 1 to 7; A program that causes a computer to execute the following.

9. a processor; Equipped with the processor associates the specific facility with the information device based on a combination of a usage time when the user used the specific facility and a usage time when the user used an information device before the usage time, and a predetermined determination criterion; An information processing system that executes the above.

Images