JP2015056007A - Communication system, information processing device, peripheral device, communication control method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a communication system that flexibly controls a polling cycle for load reduction purposes because loads of networks and constituent devices are added as information processing devices connected to peripheral devices increase.SOLUTION: A communication system includes: a peripheral device; and an information processing device. The communication system comprises change means for corresponding to the number of the information processing devices to change an interval of polling to be performed to th peripheral device by the information processing device, and the communication system further comprises response means for, when the number of the information processing devices polling an inquiry content of the same category to be managed by management means is plural, transmitting a response packet corresponding to the polling of the inquiry content to one of the plurality of information processing devices.

Description

  The present invention relates to a communication system, an information processing device, a peripheral device, a communication control method, and a program that perform polling.

  In recent years, there has been a remarkable development in computer technology and network communication technology, and the spread of networks has been progressing not only in offices but also in homes. As terminals forming these networks, not only information processing apparatuses such as PCs but also peripheral devices such as printers and scanners are equipped with network functions.

  2. Description of the Related Art Conventionally, there is a method in which an information processing device polls a peripheral device as a method for acquiring an event occurrence status in the peripheral device connected by a network. That is, in a system composed of an information processing device as a client and a peripheral device as a server, in order to detect the occurrence of an event in the peripheral device, the information processing device is periodically This is a method of transmitting an inquiry request packet.

  Here, as a typical event in the peripheral device, there is a push scan service. The push scan service is a function of determining an information processing apparatus that transmits scan data by an operation on the peripheral device side, and transmitting the scan data to the information processing apparatus in accordance with a scan instruction (Patent Document 1). In this method, a time difference corresponding to a polling period occurs at a maximum from the occurrence of an event to the detection. Accordingly, a shorter polling cycle is desirable, but the load on the network and component devices increases accordingly. Conversely, if the polling cycle is increased, the time difference from the occurrence of the push scan event to the detection is increased, delaying the processing to be performed when the event occurs, leading to a decrease in usability. In view of this, unnecessary traffic can be reduced by changing the polling cycle from the information processing device to the peripheral device according to the operation status of the peripheral device (Patent Document 2).

JP-A-11-355481 JP 2007-219956 A

  However, conventionally, no consideration is given to the case where the number of information processing devices connected to peripheral devices increases. Therefore, there has been a problem that the load on the network and the component devices increases as the number of information processing devices connected to the peripheral devices increases.

  An object of the present invention is to solve such conventional problems. An object of the present invention is to provide a communication system, an information processing device, a peripheral device, a communication control method, and a program that flexibly control a polling cycle according to a change in the number of devices that perform polling in view of the above points. And

  In order to solve the above problem, a communication system according to the present invention is a communication system including a peripheral device and an information processing device, and the information processing device performs the peripheral device on the peripheral device according to the number of the information processing devices. And changing means for changing the polling interval.

  According to the present invention, the polling cycle can be flexibly controlled in accordance with the change in the number of devices that perform polling.

1 is a block diagram showing a schematic configuration of an MFP. It is a block diagram which shows schematic structure of PC. 1 is a diagram illustrating a schematic configuration of a network system including an MFP and a PC. It is a figure which shows the transmission setting screen of PC registration request packet and inquiry request packet. It is a figure which shows the structure of the frame format of the various request packets which PC transmits to MFP. It is a figure which shows the value which the packet identifier shown in FIG. 5 takes, and its content. FIG. 3 is a diagram illustrating a frame format configuration of various response packets transmitted from the MFP to the PC in the first embodiment. It is a figure which shows the value which the packet identifier shown in FIG. 7 takes, and its content. It is a figure which shows the value which the response code shown in FIG. 7 takes, and its content. It is a figure which shows the structure of the frame format of the request / response packet transmitted / received between PC. It is a figure which shows the value which the packet identifier shown in FIG. 10 takes, and its content. It is a figure which shows the flow of the packet exchange between MFP and several PC. FIG. 10 is another diagram showing a flow of packet exchange between the MFP and a plurality of PCs. It is a flowchart which shows the procedure of the detailed process of PC. 5 is a flowchart illustrating a detailed processing procedure of the MFP. FIG. 10 is a diagram illustrating a frame format configuration of various response packets transmitted from the MFP to the PC in the second embodiment. It is a figure which shows the flow of the packet exchange between MFP and several PC. 5 is a flowchart illustrating a detailed processing procedure of the MFP. FIG. 10 is a diagram illustrating a frame format configuration of various response packets transmitted from the MFP to the PC in the third embodiment. It is a figure which shows the flow of the packet exchange between MFP and several PC. 2 is a diagram illustrating an example of an operation panel including a display unit and an operation unit of an MFP. FIG. 6 is a diagram showing a PC selection screen for selecting a scan data transmission destination PC in the MFP. FIG. 6 is a diagram illustrating an example of PC information stored in an MFP. FIG.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the following embodiments do not limit the present invention according to the claims, and all combinations of features described in the present embodiments are not necessarily essential to the solution means of the present invention. . The same constituent elements are denoted by the same reference numerals, and the description thereof is omitted.

  First, an image forming apparatus such as an MFP (Multi Function Peripheral) that is commonly used in the embodiments described below, an information processing apparatus that performs information processing such as a PC, and a configuration of a communication system including them will be described. To do. In this embodiment, the multi-function peripheral device will be described as an example of the peripheral device. However, the peripheral device may be a scanner device that does not have a printer function or a storage function.

  FIG. 1 is a block diagram showing a schematic configuration of the MFP. The MFP 100 has a printer function, a scanner function, and a storage function, and can provide each function service via a network. In the MFP 100, the printer function is realized by the printer unit 101, the scanner function is realized by the scanner unit 102, and the storage function is realized by the memory card mounting unit 103 and the memory card 104. The printer unit 101 prints print data received from the outside, image data stored in the memory card 104, and the like on a recording medium such as printing paper by an inkjet recording method, an electrophotographic recording method, or the like. The scanner unit 102 optically reads a document set on a document table, converts it into electronic data, converts it into a specified file format, and transmits it to an external device via a network. The copy service transfers image data generated by reading a document placed on a document table with the scanner unit 102 to the printer unit 101, and the printer unit 101 prints the document data on printing paper. It is also possible to read and edit a file stored in the memory card 104 by an external device connected via a network and store the edited file in the memory card from the external device.

  The MFP 100 further includes a central control device (CPU) 105 for controlling each part of the MFP, and a program memory 106 such as a ROM that stores program codes read by the CPU 105. Furthermore, a work memory 107 such as a RAM for temporarily storing or buffering image data or the like when each service is executed, a display unit 108 such as an LCD, and an operation unit 109 including switches described later are provided. Furthermore, a network communication unit 110 for connecting the MFP 100 to a network to perform various communications and a network connection unit 111 for connecting the network communication unit 110 to a network medium are provided. The network communication unit 110 corresponds to at least one of a wired LAN and a wireless LAN. In the case of wired LAN compatibility, the network connection unit 111 is a connector for connecting a wired LAN cable to the MFP 100, for example. In the case of wireless LAN compatibility, the network connection unit 111 is an antenna, for example.

  Further, the MFP 100 includes a memory 112 such as a nonvolatile flash memory in order to store transmission source information of packets received by the network communication unit 110. Each unit of MFP 100 described above is connected to be communicable with each other via signal line 113. The network communication unit 110 includes a timer 114 that measures time. Furthermore, the MFP 100 includes a USB communication unit 115 for communicating with an external PC via a USB (Universal Serial Bus) interface. The USB connection unit 116 is a USB connection unit including a USB connector.

  FIG. 2 is a block diagram showing a schematic configuration of the PC. In FIG. 2, the CPU 201 controls each unit of the PC 200. In the disk device 202, an application program read by the CPU 201, an OS (Operation System), and the like are installed, and various files are also stored. The disk reader 203 reads the contents of an external storage medium such as a CD-ROM. The memory 204 is a memory for the CPU 201 to temporarily store data as necessary, and to perform buffering and the like. The display unit 205 is a display unit configured by an LCD or the like, and the operation unit 206 is an operation unit configured by a keyboard, a pointing device, or the like. The network communication unit 207 connects the PC 200 to the network and performs various communications with the outside. The network connection unit 208 connects the network communication unit 207 to a network medium such as a LAN.

  Similar to MFP 100, network communication unit 207 and network connection unit 208 correspond to at least one of a wired LAN and a wireless LAN. Similar to the network communication unit 110 and the network connection unit 111 built in the MFP 100, the necessary functions and forms are taken according to the corresponding LAN. The signal line 209 connects the units in FIG. 2 so that they can communicate with each other. The USB communication unit 210 communicates with various peripheral devices via a USB interface. The USB connection unit 211 is a USB connection unit including a USB connector. The timer 212 is built in the CPU 201 and measures the passage of time. Further, a counter 213 is provided in the memory 204.

  3 is a block diagram showing a schematic configuration of a communication system including MFP 100 shown in FIG. 1 and PC 200 shown in FIG. In FIG. 3, an MFP 150 is an MFP having the same function as the MFP 100, and a plurality of PCs 300, 301, and 302 are PCs having the same function as the PC 200. Network 310 connects MFPs 100 and 150 and PCs 200, 300, 301, and 302 so that they can communicate with each other. The network 310 may be a wired LAN or a wireless LAN. Further, the number of PCs connected to the network 310 is not limited to the example shown in FIG. 3, and may be three or less or may be five or more. Similarly, the number of MFPs connected to the network 310 is not limited to two, and may be one or three or more. Hereinafter, when simply referred to as MFP, it represents at least one of MFP 100 and MFP 150. Further, when simply referred to as a PC, it represents at least one of the PC 200, the PC 300, the PC 301, and the PC 302.

  FIG. 21 shows a layout configuration of operation panel 2100 including display unit 108 and operation unit 109 of MFP 100 shown in FIG. In FIG. 21, an LCD screen 2101 is an LCD screen corresponding to the display unit 108. Also. Keys 2102 to 2112 are key operation units operated by the user in the operation unit 109. A key 2102 is a power key for instructing each unit of the MFP 100 to select power ON / OFF, a key 2103 is a copy key for starting copying of the MFP 100, and 2104 is a scan key for requesting a push scan operation of the MFP 100. is there.

  The push scan refers to a service that transmits scan data obtained by reading a document placed on a document table to a designated PC by using the operation of the MFP 100 as a trigger. To which PC the scan data is transmitted or in what file format can be selected by the user operating an arrow key 2110 and a decision key 2112 described later while viewing the LCD screen 2101. .

  A key 2105 is a memory card for starting a service such as printing (memory card printing) and displaying an image file stored in the MFP 100 when the memory card 104 is attached to the MFP 100. Key. A key 2106 is a color start key for starting execution of copying, push scanning, memory card printing, and the like in color. A key 2107 is a monochrome start key for starting execution of copying, push scanning, memory card printing, and the like in monochrome. A key 2108 is a cancel key for canceling copy, push scan, memory card printing, and the like that have been started. A key 2110 is an arrow key for searching for a menu to be set or a file to be printed or displayed in the memory card 104. A key 2111 is a return key for use in returning the menu screen to the previous screen, and a key 2112 is a determination key for selecting and determining an item displayed by the cursor on the LCD screen 2101. .

  FIG. 22 is a diagram showing a PC selection screen for selecting a scan data transmission destination PC displayed on the LCD screen 2101 of the MFP when the push scan is executed. When the scan key 2104 is pressed on the operation panel 2100 of the MFP, the display on the LCD screen 2101 is switched to the display shown in FIG. The displays 2201, 2202, and 2203 are display examples of PC information stored in the PC 100 in a PC registration request packet reception process (S606 in FIG. 15 described later). For example, it is displayed in a format of ““ login name ”@“ PC name ””. A display 2204 is a shaded display unit, and is moved up and down by an arrow key 2110. When the enter key 2112 is pressed, the computer name and login name that are shaded by the shaded display unit 2204 are selected as the push scan destination. The user presses the scan key 2104, then selects the push scan destination PC from the LCD screen 2101, presses the enter key 2112, and finally pushes the color start key or monochrome start key. This is called an operation.

  FIG. 23 is a diagram illustrating information of each PC stored in a predetermined area of the work memory 107 based on the PC registration packet received from the PC by the MFP. In FIG. 23, an area 2300 is a predetermined area of the work memory 107. An area 2301 is an area for storing the management number of each PC that has received the PC registration request packet. An area 2302 stores the computer name and login name of each PC that has received the PC registration request packet. An area 2303 is an area for storing the IP address of each PC that has received the PC registration request packet. Areas 2304, 2305, and 2305 are management numbers assigned to the PCs being registered. Areas 2307, 2308, and 2309 are the computer name and login name of each PC being registered. Areas 2310, 2311 and 312, are IP addresses of the PCs being registered. In this way, the MFP assigns management numbers in the order of registration, and manages the computer name, login name, and IP address. When the registration is canceled, the management number, computer name, login name, and IP address of the released PC are deleted from the predetermined area of the work memory 107, and the management number is reassigned so as to fill the deleted management number. The table shown in FIG. 23 corresponds to, for example, the type of inquiry content polled from each PC. In the following embodiment, the table in FIG. 23 corresponds to an inquiry by polling from each PC regarding the presence or absence of a push scan operation, for example. Hereinafter, each embodiment realized in the communication system having the above-described configuration will be described.

[Example 1]
FIG. 4 is a setting screen for an application operating on the PC. Each PC transmits a PC registration request packet and an inquiry request packet to the MFP to monitor the push scan operation. When an occurrence of a push scan operation is received from the MFP, an application (hereinafter referred to as a scanner driver) that reads the document on the document table is called from the MFP. In FIG. 4, a screen 400 is a setting screen for setting and displaying whether or not to transmit a PC registration request packet and an inquiry request packet to each MFP. A check box 401 is a check box for displaying whether or not to transmit a PC registration request packet and an inquiry request packet to the MFP 100 and the setting state thereof. Similarly, the check box 402 is a check box for displaying whether or not to transmit a PC registration request packet and an inquiry request packet to the MFP 150 and the setting state thereof. Each PC transmits a PC registration request packet and an inquiry request packet to the MFP 100 or 150 corresponding to the check box 401 or 402 with a check.

  In the setting screen shown in FIG. 4, MFP 100 and MFP 150 are displayed. However, if there is another scanner driver installed on the PC and communicable, it is displayed on setting screen 400 together with a check box as in MFP 100 and MFP 150. Is done. A button 403 is an OK button for validating the setting change, and a button 404 is a cancel button for invalidating the setting change. This application may be automatically started immediately after installation or after installation by turning on the PC. Alternatively, the application may be activated by the user selecting the application like a general application.

  FIG. 5 is a configuration example of various request packets transmitted from the PC to the MFP. Packets 500 shown in FIG. 5 are various request packets transmitted from the PC to the MFP. An area 501 is an area in which a destination address of the request packet 500, that is, an MFP address (for example, a MAC address) is stored. The area 502 is an area in which the transmission source address of the request packet 500, that is, the MAC address assigned to the network communication unit of the PC that transmitted the request packet is stored. An area 503 is an area in which packet lengths of areas 504 and 505 described later are stored. An area 504 is an area in which a packet identifier determined in advance is stored in a packet transmitted and received between the PC and the MFP. An area 505 is an area in which the computer name of the transmission source PC of the request packet 500 and the name of the currently logged-in user are stored in a format such as ““ login name @ computer name ””, for example.

  FIG. 6 is a diagram showing the value taken by the packet identifier of the request packet in the area 504 and its contents. If the packet identifier in the area 504 is “01”, the packet 500 is a PC registration request packet. If the packet identifier is “02”, the packet 500 is an inquiry request packet. If the packet identifier is “03”, the packet 500 is a PC release request packet. If the packet identifier is “04”, the packet 500 is an event transfer request packet. If the packet identifier is “05”, the packet 500 is a scan data request packet. If the packet identifier is “06”, the packet 500 is a PC registration completion request packet. If the packet identifier is “07”, the packet 500 is a PC release completion request packet.

  FIG. 7 is a diagram showing a configuration example of a response packet that the MFP transmits to the PC in response to each request packet shown in FIG. A packet 700 shown in FIG. 7 is a response packet transmitted from the MFP to the PC. An area 701 is an area in which the destination address of the response packet 700 is stored. For example, when the MFP 100 is a response packet to the request packet 500 received from the PC 200, an area in which a value obtained by copying the transmission source address 502 of the request packet 500, that is, the MAC address assigned to the network communication unit 207 of the PC 200 is stored. It is. An area 702 is an area in which the transmission source address of the response packet 700, that is, the MAC address of the MFP is stored. The area 703 is an area in which the total packet length of areas 704, 705, 706, and 707, which will be described later, is stored. An area 704 is an area in which a packet identifier determined in advance is stored in a packet transmitted and received between the MFP and the PC. An area 705 is an area for storing a response code that represents the response content as a code. An area 706 is an area in which an address of a PC designated as a transmission destination of image data when a push scan occurs is stored. An area 707 is an area in which the registered number of PCs currently managed by the MFP is stored.

  FIG. 8 is a diagram showing values taken by the packet identifiers of the response packets in the area 704 and their contents. If the packet identifier in the area 704 is “11”, it is a PC registration response packet responding to the PC registration request packet of FIG. If the packet identifier is “12”, it is an inquiry response packet in response to the inquiry request packet of FIG. If the packet identifier is “13”, it is a PC release response packet in response to the PC release request packet of FIG. If the packet identifier is “14”, it is a scan data packet in response to the event transfer response packet of FIG. If the packet identifier is “15”, it is a scan data packet including scan data in response to the scan data request packet of FIG. If the packet identifier is “16”, it is a PC registration completion response packet in response to the PC registration completion request packet of FIG. If the packet identifier is “17”, it is a PC release completion response packet in response to the PC release completion request packet of FIG.

  FIG. 9 is a diagram showing the value taken by the response content code 705 and its content. When the inquiry response packet is transmitted, if no push scan operation is performed, “03” is set. When the inquiry response packet is transmitted, if a push scan operation is detected before the inquiry request packet is received, “04” is set. Further, when a PC registration request packet or a PC deletion request packet is received from any PC, “01” is displayed when the MFP accepts the corresponding request, and “02” when the request is not accepted.

  FIG. 10 is a diagram illustrating a configuration example of various request / response packets transmitted and received between PCs. A packet 1000 illustrated in FIG. 10 is various request packets transmitted from the PC to another PC or various response packets received from the other PC by the PC. An area 1001 is an area in which the destination address of the request / response packet 1000, that is, the MAC address assigned to the network communication unit 207 of the transmission destination PC is stored. The area 1002 is an area in which the transmission source address of the request / response packet 1000, that is, the MAC address assigned to the network communication unit 207 of the PC that transmitted the request / response packet is stored. An area 1003 is an area in which packet lengths of areas 1004 and 1005 described later are stored. An area 1004 is an area in which a packet identifier determined in advance is stored in a packet transmitted and received between PCs. An area 1005 is an area in which an address (for example, a MAC address) of an MFP that executes push scan is stored.

  FIG. 11 is a diagram showing values taken by the packet identifier in the area 1004 and the contents thereof. If the packet identifier of the area 1004 is “05”, the packet 1000 is an event transfer request packet. If the packet identifier is “06”, the packet 1000 is a PC registration completion request packet. This is used in Example 2. If the packet identifier is “07”, the packet 1000 is a PC release completion request packet. This is also used in Example 2. If the packet identifier is “15”, the packet 1000 is an event transfer response packet that responds to the event transfer request packet. If the packet identifier is “16”, the packet 1000 is a PC registration completion response packet that responds to the PC registration completion request packet. This will also be described in the second embodiment. If the packet identifier is “17”, the packet 1000 is a PC release completion response packet responding to the PC release completion request packet. This will also be described in the second embodiment.

  FIG. 12 is a communication control sequence chart showing a packet exchange flow for the MFP 100, the PC 200, and the PC 300 to communicate via the network 310, and for each PC to poll for the presence or absence of a push scan operation. It is assumed that a printer driver, a scanner driver, and the application described with reference to FIG. 4 are installed in the disk device 202 of the PC 200. Further, in the setting screen 400 of the PC 200, it is assumed that a check box 401 of the MFP 100 is checked as shown in FIG. The PC 300 is the same as the PC 200.

  When the application is activated, the PC 200 transmits a PC registration request packet to the MFP 100 (S101). Here, the timer 212 is started to measure the first period T1. It is assumed that the PC registration response packet from MFP 100 has not been received when the first period T1 has elapsed. As the factors, for example, the MP 100 is not activated or the network communication between the PC 200 and the MFP 100 is not normal. In that case, the PC 200 transmits a PC registration request packet to the MFP 100 again (S102), and measures the passage of the first period T1. When the MFP 100 receives the PC registration request packet from the PC 200 but cannot register, the MFP 100 transmits a PC registration response packet in which “02” is set in the response code 705 to the PC 200 (S103). When receiving the PC registration response packet in which “02” is set in the response code 705 from the MFP 100, the PC 200 waits for the first period T1 to elapse and then transmits the PC registration request packet to the MFP 100 again (S104). ).

  When the MFP 100 receives the PC registration request packet from the PC 200 and is ready to register, the MFP 100 acquires address information from the transmission source address 502, acquires a computer name and login name from the computer name 505, and registers them (described later). S606 in FIG. 15). Then, a PC registration response packet in which “01” is set in the response code 705 is transmitted to the PC 200 (S105). When receiving a PC registration response packet in which “01” is set in the response code 705 from the MFP 100, the PC 200 transmits a polling inquiry request packet for inquiring whether the push scan operation is performed to the MFP 100 (S106). .

  When the MFP 100 receives the inquiry request packet from the PC 200 and the push scan operation is not executed, the MFP 100 transmits an inquiry response packet in which “03” is set to the response code 705 to the PC 200 (S107, S109). At this time, since only the PC 200 is registered in the MFP 100, “1” is set in the registered PC number 707 of the inquiry response packet to be transmitted. When receiving an inquiry response packet in which “03” is set in the response code 705 from the MFP 100, the PC 200 acquires the second period T2 from the number of PCs “1” stored in the registered PC number 707, Wait for the elapse of period T2. Thereafter, an inquiry request packet is transmitted again to the MFP 100 (S108).

  On the other hand, when the application is activated, the PC 300 transmits a PC registration request packet to the MFP 100 (S201). When the MFP 100 receives the PC registration request packet from the PC 300 and is ready to register, the MFP 100 acquires address information from the transmission source address 502, acquires a computer name and login name from the computer name 505, and registers them ( S606 in FIG. 16 described later). Then, a PC registration response packet in which “01” is set in the response code 705 is transmitted to the PC 300 (S202). When the PC 300 receives a PC registration response packet in which “01” is set in the response code 705 from the MFP 100, the PC 300 transmits a polling inquiry request packet for inquiring whether there is a push scan operation to the MFP 100 (S203). ).

  Similarly, after the PC 300 is registered in the MFP 100, the PC 200 transmits an inquiry request packet for inquiring whether the push scan operation has been performed to the MFP 100 (S110). When the MFP 100 receives the inquiry request packet from the PC 200 and the push scan operation is not executed, the MFP 100 transmits an inquiry response packet in which “03” is set in the response code 705 to the PC 200. (S111, S113, S115). At this time, since the PC 200 and the PC 300 are registered in the MFP 100, “2” is set in the registered PC number 707 of the inquiry response packet to be transmitted.

  The same applies to the PC 300. When the MFP 100 receives the inquiry request packet from the PC 300 and the push scan operation has not been executed, the MFP 100 transmits a response packet in which “03” is set in the response code 705 to the PC 300 (S204, S206). At this time, since the PC 200 and the PC 300 are registered in the MFP 100, “2” is set in the registered PC number 707 of the inquiry response packet to be transmitted.

  When the PC 200 receives an inquiry response packet in which “03” is set in the response code 705 from the MFP 100, the PC 200 sets the second period T3 from the number of PCs “2” registered in the MFP 100 stored in the registered PC number 707. Obtain and wait for the second period to elapse. Thereafter, an inquiry request packet is transmitted again to the MFP 100 (S114, S116).

  The PC 300 performs the same processing. When the PC 300 receives an inquiry response packet in which “03” is set in the response code 705 from the MFP 100, the PC 300 sets the second cycle T3 from the number of PCs “2” registered in the MFP 100 stored in the registered PC number 807. Obtain and wait for the second period to elapse. Thereafter, an inquiry request packet is transmitted again to the MFP 100 (S205).

  When the application is terminated or the check box 401 of the MP 100 is unchecked on the application setting screen 400, the PC 300 transmits a PC release request packet to the MFP 100 (S207). When the MFP 100 receives the PC release request packet from the PC 300, the MFP 100 deletes the stored address information, computer name, and login name of the PC 300 (S617 in FIG. 15 described later). Then, a PC deletion response packet in which “01” is set in the response code 805 is transmitted to the PC 300 (S208).

  Even after the PC 300 is released from the MFP 100, the PC 200 transmits an inquiry request packet for inquiring of the MFP 100 whether or not there is a push scan operation (S116). When the MFP 100 receives the inquiry request packet from the PC 200 and the push scan operation is not executed, the MFP 100 transmits an inquiry response packet in which “03” is set to the response code 705 to the PC 200 (S117, S119). At this time, since only the PC 200 is registered in the MFP 100, “1” is set in the registered PC number 707 of the inquiry response packet to be transmitted.

  When the PC 200 receives the inquiry response packet in which “03” is set in the response code 805 from the MFP 100, the PC 200 calculates the second period T2 from the number of PCs “1” registered in the MFP 100 stored in the registered PC number 807. And waits for the second period to elapse. Thereafter, an inquiry request packet is transmitted to the MFP 100 at regular time intervals (S118, S120).

  In this way, in this embodiment, when there is a change in the registered number of PCs notified from the MFP, each PC can control the polling cycle according to the registered number. The second period is acquired from the number of PCs registered in the MFP 100. The smaller the number of PCs, the smaller the period, and the larger the number. In this embodiment, for example, when the number of registered PCs is “1”, the second period is 2 seconds, and when the number of registered PCs is “2”, the second period is 4 seconds and the number of registered PCs is “3”. In the case of “,” the second cycle may be predetermined by a table or the like so that the network traffic becomes 0.5 times / second, such as 6 seconds. Furthermore, a lower limit value and an upper limit value may be set in the second period.

  Next, while the PC 200 and the PC 300 communicate with the MFP 100 via the network 310 and the inquiry request packet is transmitted every second period as described above, a push scan operation is performed and the push scan is performed. The processing until execution is performed will be described.

  FIG. 13 is a communication control sequence chart showing the flow of packet exchange performed for execution of push scan when MFP 100, PC 200, and PC 300 communicate with each other via network 310. As described above, the PC 200 and the PC 300 transmit an inquiry request packet to the MFP 100 every second cycle T3 (S301, S303, S403, S405, and S407). The MFP 100 transmits an inquiry response packet in which “03” is set to the response code 705 to the PC 200 and PC 300 while the push scan operation is not performed on the MFP 100 (S302, S404).

  Here, it is assumed that a push scan operation in which the PC 200 is designated as a scan data transmission destination is performed at time t1. Then, when the MFP 100 responds to the inquiry request packet (S303) received from the PC 200 first after the time t1, that is, after the occurrence of the push scan operation, the response code 705 is “04” and the push scan is performed. An inquiry response packet in which the address of the PC 200 is stored in the transmission destination address 706 is transmitted to the PC 200 (S304).

  When receiving an inquiry response packet in which “04” is set in the response code 705 from the MFP 100, the PC 200 confirms the address stored in the push scan transmission destination 706. If the address is its own address, that is, the address of the PC 200, the scanner driver is activated and a scan data request packet is transmitted to the MFP 100 (S305).

  Upon receiving the scan data request packet from the PC 200, the MFP 100 clears the push scan operation flag. Then, the scanned image data is transmitted to the PC 200 as a scan data packet (S306). When responding to an inquiry request packet (S405, S407) from the PC 300 thereafter, an inquiry response packet in which “03” is set in the response code 705 is transmitted to the PC 300 (S406, S408). Upon receiving all desired scan data from the MFP 100, the PC 200 transmits an inquiry request packet to the MFP 100 again every second cycle T3 (S307).

  Here, it is assumed that a push scan operation in which the PC 300 is designated as a scan data transmission destination is performed at time t2. Then, when the MFP 100 responds to the inquiry request packet (S307) received from the PC 200 first after time t2, the response code 705 is “04”, and the address of the PC 300 is set to the push scan transmission destination address 706. The stored inquiry response packet is transmitted to the PC 200 (S308). Then, the push scan operation flag is cleared. Further, when responding to the inquiry request packet (S409) received from the PC 300 later, an inquiry response packet in which “03” is set in the response code 705 is transmitted to the PC 300 (S410).

  When the PC 200 receives an inquiry response packet in which “04” is set in the response code 705 from the MFP 100, the PC 200 confirms the address stored in the push scan transmission destination address 806. If the address is not its own address, that is, the address of the PC 200, an event transfer request packet is transmitted to the destination address, in this case, the address of the PC 300 (S309). Thereafter, an inquiry request packet is transmitted to the MFP 100 every second cycle T3 (S311).

  When receiving the event transfer request packet from the PC 200, the PC 300 transmits an event transfer response packet to the PC 200 (S310). Then, the scanner driver is activated and a scan data request packet is transmitted to the MFP 100 (S411). Upon receiving the scan data request packet from the PC 300, the MFP 100 transmits the scanned image data as a scan data response packet to the PC 300 (S412). Upon receiving all desired scan data from the MFP 100, the PC 300 transmits an inquiry request packet to the MFP 100 every second cycle T3 (S413).

  FIG. 14 is a flowchart showing a detailed processing procedure of the PC 200 and the PC 300 in the sequence charts shown in FIGS. 12 and 13. The processing illustrated in FIG. 14 is realized by the CPU 201 controlling each unit, for example.

  First, the CPU 201 activates an application (S501), and determines whether or not the check box 401 of the MFP 100 is checked on the setting screen 400 (S502). If it is determined that it is checked, a PC registration request packet is transmitted to the checked MFP 100 (S503).

  Next, the timer 212 is started (S504), and reception of a PC registration response packet is awaited (S505). When the PC registration response packet is received, it is determined whether or not the response code is “01” (S506). If it is determined to be “01”, an inquiry request packet is transmitted to MFP 100 that transmitted the PC registration response packet (S507). If the PC registration response packet cannot be received or if the response code of the received PC registration response packet is “02”, a timeout of the first period is awaited (S517). Further, it is determined whether or not the check box 401 of the MFP 100 on the setting screen 400 is checked (S518). If it is determined that it is checked, a PC registration request packet is transmitted again to the MFP 100 (S503). If it is determined that it is not checked, the process proceeds to S515.

  After transmitting the inquiry request packet (S507), the timer 212 is restarted (S508), and reception of an inquiry response packet is awaited (S509). When the inquiry response packet is received, it is determined whether or not the response code is “04” (whether a push scan operation has occurred) (S510). If it is determined that it is not “04”, it is determined whether or not an event transfer request packet has been received from another PC (S511). If it is determined that the event transfer request packet has not been received, the second period is acquired from the number of PCs registered in the MFP 100 stored in the registered PC number 807 of the received inquiry response packet (S512). (S513).

  If the response code of the inquiry response packet received in S510 is “04”, it is further determined whether or not the address stored in the push scan transmission destination address 806 belongs to another PC (S519). If it is determined that it is an address of another PC, an event transfer request packet is transmitted to the address stored in the push scan destination address (S521). Here, the event transfer packet may not be transmitted when the current number of registered PCs is equal to or less than a predetermined number. On the other hand, if it is determined that the address is not the address of another PC but the address of the own PC, a scan process is performed (S520). In this scan process, the PC designates scan settings for the MFP, the MFP reads an image according to the scan settings, and the PC receives the image data. The scan process is also performed when an event transfer request packet is received from another PC in S511 (S520).

  If the inquiry response packet is not received in S509, it is determined whether or not the check box 401 of the MFP 100 on the setting screen 400 is checked (S514). In addition, after the processing of S513, S520, and S521, the process proceeds to S514.

  If the check box 401 of the MFP 100 is checked in S514, the inquiry request packet is transmitted again to the MFP 100 (S507). If it is not checked, a PC release request packet is transmitted to the MFP 100 (S515). Finally, it is determined whether or not to terminate the application (S516). If the application is to be terminated, the packet exchange process with the MFP is terminated. If not, the process proceeds to S502.

  FIG. 15 is a flowchart showing a detailed processing procedure of MFP 100 in the sequence charts shown in FIGS. 12 and 13. The process illustrated in FIG. 15 is realized by the CPU 105 controlling each unit, for example. First, when the MFP 100 is activated (S601), the CPU 105 waits for a PC registration request packet from the PC (S602). If a PC registration request packet has been received, it is determined whether the computer name and login name stored in the computer name 505 of the PC registration request packet can be registered (S603). If it is determined that the registration is possible, a PC registration response packet in which “01” is set in the response code is transmitted to the requesting PC (S604). On the other hand, if it is determined that the registration is not possible, a PC registration response packet having a response code set to “02” is transmitted to the requesting PC (S605), and the PC registration request packet is again waited (S602). . If there is no PC registration request packet in S602, the process proceeds to an inquiry request packet standby process (S608).

  The MFP 100 stores the computer name, login name, and address information of the PC that transmitted the PC registration request packet in a predetermined area of the work memory 107 (S606). Through such processing, the number of PCs currently connected to the MFP 100 can be managed and grasped by counting the number of PC information registered in the work memory 107. Subsequently, the timer 114 is activated and waits for an inquiry request packet from the registered PC (S608). If an inquiry request packet is received, the time measurement by the timer 114 is stopped, and it is determined whether or not a push scan operation is being executed (S609).

  If the push scan operation is not executed, “03” is set in the response code, and an inquiry response packet in which the registered PC number 807 is set to the current registered PC number is transmitted to the requesting PC. (S614).

  Subsequently, it is confirmed that the power of the MFP 100 is turned off (S618). If not, the eleventh time measurement by the timer 114 is started again, and the process returns to S602. On the other hand, if a push scan operation is being executed, an inquiry response packet is set in which “04” is set in the response code and the address of the PC designated as the push scan image destination is set in the push scan destination address 806. The message is transmitted to the original (S610). If the inquiry request transmission source address and the push scan transmission destination address are not matched, for example, “03” is set in the response code, and the number of registered PCs 807 is currently being registered. An inquiry response packet in which the number of PCs is set is transmitted to the requesting PC.

  On the other hand, if the inquiry request packet is not received during the eleventh time counting in S608, it is determined whether or not a PC deletion request packet has been received (S611). If a PC deletion request packet has been received, the time measurement by the timer 114 is stopped, and it is determined whether the MFP 100 is in a state in which registration information can be deleted (S612). If the registration information can be deleted, a PC deletion response packet in which “01” is set in the response code is transmitted to the request source (S616). Then, the computer name, login name, and address information requested to be deleted are deleted from the predetermined area of the work memory 107 (S617). Subsequently, it is confirmed that the MFP is turned off (S618). If not, the process returns to S602.

  On the other hand, if the registration information cannot be deleted, a PC deletion response packet in which “02” is set in the response code is transmitted to the request source (S613). Subsequently, it is confirmed that the MFP is turned off (S618). If it is not OFF, the eleventh time measurement by the timer 114 is started again, and the process returns to S602.

  If neither the inquiry request packet nor the PC deletion request packet is received, it is determined whether or not the eleventh time has elapsed (S615). Here, when the eleventh time has elapsed, the computer name, login name, and address information of each PC stored in the predetermined area of the work memory 107 is deleted (S617), and the power of the MFP is confirmed to be turned off (S617). If it is not OFF (S618), the process returns to S602. On the other hand, if it has not yet timed out, it is confirmed that the MFP is turned off (S618). If not, the process returns to S602. If it is confirmed in S618 that the MFP is turned off, the processing of this processing in FIG. 15 ends.

[Example 2]
The configurations of MFP and PC, applications, and the like used in the present embodiment are the same as those described with reference to FIGS. The general format of various request packets transmitted from the PC to the MFP is the same as the description in FIGS. Hereinafter, differences from the first embodiment will be described.

  FIG. 16 is a diagram showing an example of a schematic format of a response packet transmitted by the MFP in response to each request packet shown in FIG. A packet 1600 shown in FIG. 16 is a response packet transmitted from the MFP to the PC. The details are the same as those described for the regions 701 to 706 in FIG.

  FIG. 17 is a communication control sequence chart showing a packet exchange flow for polling the presence / absence of a push scan operation when MFP 100, PC 200, and PC 300 communicate via network 310. It is assumed that a printer driver, a scanner driver, and the application described with reference to FIG. 4 are installed in the disk device 202 of the PC 200. Further, in the setting screen 400 of the PC 200, it is assumed that a check box 401 of the MFP 100 is checked as shown in FIG. The PC 300 is the same as the PC 200.

  When the application is activated, the PC 200 initializes the registered PC counter 213 to zero and transmits a PC registration request packet to the MFP 100 (S701). When the MFP 100 receives the PC registration request packet from the PC 200 and is ready to register, the MFP 100 registers the address information, computer name, and login name of the PC 200 (corresponding to S606 in FIG. 15 described above). Then, a PC registration response packet in which “01” is set in the response code 805 is transmitted to the PC 200 (S702).

  When receiving a PC registration response packet in which “01” is set in the response code 805 from the MFP 100, the PC 200 transmits a PC registration completion request packet to all PCs on the network (S703), and the registered PC counter 213. Is incremented to plus one. Since the PC 300 is not registered in the MFP 100 at this time, the PC 300 completes the received PC registration completion request packet.

  Next, the PC 200 transmits an inquiry request packet for inquiring about the presence or absence of the push scan operation to the MFP 100 (S704, S706, S708). When the MFP 100 receives the inquiry request packet from the PC 200 and the push scan operation is not executed, the MFP 100 transmits an event inquiry response packet in which “03” is set in the response code 805 to the PC 200 (S705, S707, S709). ). During this time, the registered PC counter 213 of the PC 200 is “1”, which is used to calculate the second period T2, wait for the elapse of the second period T2 after receiving the event inquiry response packet, and wait for the event inquiry. The request packet is transmitted to MFP 100 again.

  When the application is activated, the PC 300 initializes the registered PC counter 213 to zero and transmits a PC registration request packet to the MFP 100 (S801). When the MFP 100 receives the PC registration request packet from the PC 300 and is ready to register, the MFP 100 registers the address information, computer name, and login name of the PC 300 (corresponding to S606 in FIG. 15 described above). Then, a PC registration response packet in which “01” is set in the response code 805 is transmitted to the PC 300 (S802).

  When the PC 300 receives a PC registration response packet in which “01” is set in the response code 805 from the MFP 100, the PC 300 transmits a PC registration completion request packet to all PCs on the network (S803), and the registered PC counter 213. Is incremented to plus one.

  Since the PC 200 is registered in the MFP 100 at this time, when the PC registration completion request packet is received, the registration PC counter 213 is incremented by 1, and a PC registration completion response packet is transmitted to the requesting PC 300. (S804). When receiving the PC registration completion response packet, the PC 300 increments the registered PC counter 213 to plus 1.

  At this time, the registered PC counters 213 of the PCs 200 and 300 are both “2”. Using this, the second period T3 is calculated, and after the inquiry response packet is received, the inquiry request packet is transmitted to the MFP 100 again after the second period elapses (S710, S711, S712, S713, S714, S715, S805, S806, S807, S808).

  When the application is terminated or the check box 401 of the MFP 100 is unchecked on the application setting screen 400, the PC 300 transmits a PC release request packet to the MFP 100 (S809).

  When the MFP 100 receives the PC release request packet from the PC 300, the MFP 100 deletes the stored address information, computer name, and login name of the PC 300 (corresponding to S606 in FIG. 15 described above). Then, a PC deletion response packet in which “01” is set in the response code 805 is transmitted to the PC 300 (S810).

  When the PC 300 receives a PC release response packet in which “01” is set in the response code 805 from the MFP 100, the PC 300 transmits a PC release completion request packet to all PCs on the network (S811). Since the PC 200 is registered in the MFP 100 at this time, when the PC cancellation completion request packet is received, the registered PC counter 213 is decremented to minus 1, and a PC cancellation completion response packet is transmitted to the requesting PC 300. (S812). As a result, the registered PC counter of the PC 200 becomes “1”, which is used to calculate the second period T2, wait for the elapse of the second period after receiving the inquiry response packet, and inquire the MFP 100 again. The request packet is transmitted to the MFP (S716, S717, S718).

  FIG. 18 is a flowchart showing a procedure of update processing of the registered PC counter 213 of the PC 200 and PC 300 in the sequence chart shown in FIG. The processing illustrated in FIG. 18 is realized by the CPU 201 controlling each unit, for example. First, the CPU 201 of each PC initializes the registered PC counter 213 to zero (S901). Then, it is determined whether or not to transmit a PC registration completion request packet to all other PCs on the network (S902). Here, if it is determined to be transmitted, the CPU 201 increments the registered PC counter to plus 1 after transmitting the PC registration completion request packet (S903).

  Next, the third timer is started (S904), and it waits for the reception of the PC registration completion response packet (S905) until it times out at a predetermined third period corresponding to the third timer (S907). When the PC registration completion response packet is received, the registered PC counter 213 is incremented by 1 (S906).

  Next, reception of a PC registration completion request packet from another PC is determined (S908). If it is determined that the registration has been received, the registered PC counter 213 is incremented by 1 and a PC registration completion response packet is transmitted to the requesting PC (S910).

  Next, it is determined whether a PC release completion request packet has been received (S911). If it is determined that the received PC has been received, the registered PC counter 213 is decremented to minus 1 (S912), and a PC release completion response packet is transmitted to the requesting PC (S913). Finally, it is determined whether a PC release completion request packet is transmitted to all PCs on the network (S914). Here, if it is determined not to transmit, the processing from S908 is repeated, and if it is determined to transmit, this processing of FIG. 18 is terminated.

  In the present embodiment, the number of PCs registered in the MFP 100 is updated by communication between the PC 200 and the PC 300, respectively. Therefore, even when MFP 100 does not have a management function for the number of registered PCs, each PC can grasp the number of PCs registered in MFP 100 and change the second period according to the number of PCs.

Example 3
The configurations of MFP and PC, applications, and the like used in the present embodiment are the same as those described with reference to FIGS. The general format of various request packets transmitted from the PC to the MFP is the same as the description in FIGS. Hereinafter, differences from the first and second embodiments will be described.

  FIG. 19 is a diagram showing an example of a schematic format of a response packet that the MFP transmits to the PC in response to each request packet shown in FIG. A packet 1900 shown in FIG. 19 is a response packet transmitted from the MFP to the PC. The areas 701 to 707 are the same as those described in FIG. An area 1901 is an area for storing the management number of each PC managed by the MFP (corresponding to 2401 in FIG. 24 described above). An area 1902 stores a time difference between the time when the inquiry request is received and the latest time when the inquiry request is received from the PC having the management number “1”.

  FIG. 20 is a sequence chart showing a flow of packet exchange performed for polling the presence / absence of a push scan operation by the MFP 100, the PC 200, and the PC 300 communicating via the network 310. It is assumed that a printer driver, a scanner driver, and the application described with reference to FIG. 4 are installed in the disk device 202 of the PC 200. Further, in the setting screen 400 of the PC 200, it is assumed that a check box 401 of the MFP 100 is checked as shown in FIG. The same applies to the PC 300.

  The PC 200 transmits an inquiry request packet for inquiring the presence or absence of the push scan operation to the MFP 100 (S1001, S1003, S1005). When the MFP 100 receives the inquiry request packet from the PC 200 and the push scan operation is not executed, the MFP 100 transmits an inquiry response packet in which “03” is set in the response code 805 to the PC 200 (S1002, S1004, S1006). . At this time, since only the PC 200 is registered in the MFP 100, “1” is set in the registered PC number 707 of the inquiry response packet to be transmitted. Further, “1” is set in the management number 1901 and “0” is set in the time difference 1902. This is because the management number of the PC 200 is “1”, and the time when the inquiry request from the PC 200 is received is the same as the latest time when the inquiry request is received from the PC with the management number “1”. During this period, the number of registered PCs 707 is “1”, which is used to calculate the second period T2, and after receiving the inquiry response packet, wait for the second period T2 to elapse and send the inquiry request packet again to the MFP 100. Send to. Therefore, the MFP 100 receives the inquiry request packet at the second cycle T2.

  The PC 300 transmits a PC registration request packet to the MFP 100 (S1101). When the MFP 100 receives the PC registration request packet from the PC 300 and is in a state where it can be registered, the MFP 100 registers the address information, computer name, and login name of the PC 300 (corresponding to S606 in FIG. 15 described above). Then, a PC registration response packet in which “01” is set in the response code 805 is transmitted to the PC 300 (S1102).

  The PC 200 transmits an inquiry request packet for inquiring the presence or absence of the push scan operation to the MFP 100 (S1007, S1009, S1011, and S1013). When the MFP 100 receives the inquiry request packet from the PC 200 and the push scan operation is not executed, the MFP 100 transmits an inquiry response packet in which “03” is set to the response code 805 to the PC 200 (S1008, S1010, S1012,. S1014). At this time, since the PC 200 and the PC 300 are registered in the MFP 100, “2” is set in the registered PC number 707 of the inquiry response packet to be transmitted. Further, “1” is set in the management number 1901 and “0” is set in the time difference 1902. During this period, the number of registered PCs 707 is “2”, which is used to calculate the second period T3. After receiving the inquiry response packet, the second time period T3 is waited for, and the inquiry request packet is sent again to the MFP 100. Send to.

  On the other hand, the PC 300 transmits an inquiry response packet to the MFP 100 (S1103). When the MFP 100 receives the inquiry request packet from the PC 300 and the push scan operation has not been executed, the MFP 100 transmits an inquiry response packet in which “03” is set in the response code 805 to the PC 300 (S1104). At this time, since the PC 200 and the PC 300 are registered in the MFP 100, “2” is set in the registered PC number 707 of the inquiry response packet to be transmitted. Further, “2” is set in the management number 1901, and the difference “t4− between the time t4 when the inquiry request is received (S1103) and the time t3 when the inquiry request packet from the immediately preceding PC 200 is received (S1007) is set as the time difference 1902. t3 "is set.

  The PC 300 calculates the second period T3 using the registered PC number 707 of the received response packet. Further, an adjustment time Tw for finely adjusting the time for transmitting the next inquiry response packet is calculated. It is desirable from the viewpoint of the response speed of push scan that the event inquiry request packets received by the MFP 100 from the PC 200 and the PC 300 are equally spaced at T3 / 2. Here, if the interval between the time t3 at which the inquiry request packet is received from the PC 200 and the time t4 at which the inquiry request packet is received from the PC 300 is shorter than T3 / 2, the MFP next receives the inquiry request packet. Becomes a long interval after (T3- (t4-t3)). In the present embodiment, the interval is finely adjusted with the adjustment time Tw, and the reception of the event inquiry request packet described above is set at substantially equal intervals. The adjustment time Tw is calculated from the following equation (1).

Tw = (D−1) × T / N−Tx (1)
Here, D is a value stored in the management number 1901. T is the calculated second period. N is a value stored in the registered PC number 707. Tx is a value stored in the time difference 1902. Therefore, Tw calculated by the PC 300 is T3 / 2- (t4-t3). As is apparent from the equation (1), Tw calculated by the PC 200 that receives the management number 1901 with “1” is always zero.

  After receiving the inquiry response packet (S1104), the PC 300 transmits the inquiry request packet to the MFP 100 again after the second period T3 and the adjustment time Tw have elapsed (S1105). When the PC 300 receives the inquiry response packet from the MFP 100 (S1106), the adjustment time Tw is calculated. At this time, from Equation (1), Tw is (2-1) × T3 / 2−T3 / 2 = zero. Become. That is, Tw is zero when the inquiry request packet transmitted by the PC 200 and the inquiry request packet transmitted by the PC 300 are transmitted to the MFP 100 at equal intervals. Therefore, after the elapse of the second cycle T3, an inquiry request packet is transmitted to the MFP 100 (S1107). The same applies to S1108 and S1109.

  As described above, in this embodiment, the push scan can be executed with the most efficient response by finely adjusting the transmission timing of the inquiry request packet transmitted from each PC to the MFP.

    The present invention is also realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.

  As a storage medium for supplying the program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, a DVD, or the like is used. it can.

  In addition, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also the OS running on the computer based on the instruction of the program code performs the actual processing. Needless to say, a case where the function of the above-described embodiment is realized by performing part or all of the processing, is also included.

  Furthermore, after the program code read from the storage medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function is based on the instruction of the program code. It goes without saying that the CPU of the expansion board or function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing.

Claims (16)

A communication system comprising a peripheral device and an information processing device,
Changing means for changing a time interval of polling performed by the information processing apparatus on the peripheral device according to the number of the information processing apparatuses;
A communication system characterized by the above.   2. The communication system according to claim 1, wherein the changing unit increases the time interval as the number of the information processing devices increases, and decreases the time interval as the number decreases. The information processing apparatus further includes a table associating the number of the information processing apparatuses with the time interval,
The communication system according to claim 1, wherein the changing unit changes the time interval with reference to the table. The peripheral device is:
The communication according to any one of claims 1 to 3, further comprising management means for managing the number of information processing devices that are polling the peripheral device for the same type of inquiry content. system. The peripheral device is:
When there are a plurality of information processing devices that are polling the same type of inquiry content managed by the management means, a response packet corresponding to the polling of the inquiry content is sent out of the plurality of information processing devices. 5. The communication system according to claim 4, further comprising response means for transmitting to one. The information processing apparatus includes:
When a response to polling is received from the peripheral device, the device further includes a transfer unit that processes the response when the response is to the own device, and transfers the response to the other device when the response is to the other device. The communication system according to claim 1. The polling packet is a packet for inquiring about the presence or absence of a push scan operation in the peripheral device,
The response means transmits the response packet to the information processing apparatus corresponding to the polling packet received first after the occurrence of the push scan operation.
The communication system according to claim 5 or 6. A communication control method executed in a communication system including a peripheral device and an information processing device,
A changing step of changing a polling interval performed by the information processing device on the peripheral device according to the number of the information processing devices;
A communication control method characterized by comprising: A peripheral device capable of communicating with an information processing device,
Notification means for notifying the number of information processing devices that are polling the peripheral device to the information processing device that is polling;
A peripheral device comprising: A communication control method executed in a peripheral device capable of communicating with an information processing device,
A notification step in which the notification means of the peripheral device notifies the information processing device that performs polling of the number of information processing devices that are polling the peripheral device;
A communication control method characterized by comprising: An information processing apparatus capable of communicating with a peripheral device,
Changing means for changing a polling time interval according to the number of information processing devices that are polling the peripheral device,
An information processing apparatus comprising: Requesting the peripheral device for registration as the information processing device performing the polling, and further comprising a notification means for notifying the other information processing device of the request,
The changing means acquires the number based on the notification from another information processing apparatus, and changes the time interval according to the number.
The information processing apparatus according to claim 11.   When a response to polling is received from the peripheral device, the device further includes a transfer unit that processes the response when the response is to the own device, and transfers the response to the other device when the response is to the other device. The information processing apparatus according to claim 11. A communication control method executed in an information processing apparatus capable of communicating with a peripheral device,
The changing step of changing the polling interval according to the number of information processing devices in which the changing means of the information processing device is polling the peripheral device;
A communication control method characterized by comprising:   The program for functioning a computer as a means of the peripheral device of Claim 9.   The program for functioning a computer as a means of the information processing apparatus according to claim 11.

Images