JP2009029102A - Information processing apparatus, information processing method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform the response of a packet with respect to a network, in such a state that a power-saving mode is maintained. <P>SOLUTION: An information processing apparatus includes: a PF 23 which judges whether or not the packet received from the network is a reply request packet not requiring a process to be performed by the information processing apparatus, during operation in any of a plurality of power-saving modes; a PE 24 which generates a response packet to the received packet, in such a state that the power-saving mode when the packet is received is maintained, when the received packet is a reply request packet not requiring a process to be performed by the information processing apparatus; and an MAC 22 which returns the generated response packet via the network to the source of the reply request packet. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an image forming apparatus, a device equipped with a network device, a network scanner, a network printer, an information processing device including a multifunction device equipped with a network, an information processing method, and a program.

  Conventionally, a printer controller that converts print information transmitted from a printer and a host into output image data and outputs the output image data, a power supply device for supplying power to the printer and the printer controller, and a power supply device to a load on the printer 2. Description of the Related Art An energy-saving standby image forming apparatus (for example, see Patent Document 1) provided with means for switching power feeding to an energy saving mode / operation mode is known.

  In addition, conventionally, when receiving a broadcast packet (ARP packet) or receiving a specific pattern during the energy saving mode (power saving mode), immediately returning from the energy saving mode and receiving a packet by PING, There is known an information processing apparatus (for example, see Patent Document 2) that returns from an energy saving mode and processes a response to PING.

  Here, PING is a program that diagnoses a network based on data such as the presence / absence of a reply from the device and response time by sending an ICMP echo request packet to the device to be investigated by the ICMP protocol.

JP 2001-328313 A Japanese Patent Laid-Open No. 2005-041214

  However, in the information processing apparatus disclosed in Patent Document 1, when responding to a packet received from the network, it is necessary to cancel the power consumption mode and return to the normal operation mode. There was a problem of being low.

  Further, in the information processing apparatus disclosed in Patent Document 2, when responding to a PING packet received from the network, the power-saving mode is canceled to return to the normal operation mode, and a CPU with high power consumption, Since the memory is used to respond to PING for relatively simple processing, there is a problem that the power saving effect is low.

  The present invention has been made in view of the above, and an object of the present invention is to enable a packet response to a network while maintaining a power consumption mode.

An information processing apparatus according to the present invention that solves the problems described above and operates in one of the plurality of power saving modes and a control unit that operates the information processing apparatus in a plurality of types of power saving modes. A packet determination unit for determining whether or not a packet received from the network is a return request packet that does not require processing addressed to the information processing device, and the received packet performs processing addressed to the information processing device. A packet generation unit that generates a response packet for the received packet while maintaining a power saving mode when receiving the packet when the packet is a return request packet that is not required, Further, based on the content of the received packet, it is determined whether the received packet requests a return of predetermined information, Serial packet generation unit, when the received packet is requesting a return of predetermined information, and generates the response packet including the predetermined information.
The present invention also relates to a method and program executed by the above apparatus.

  According to the present invention, it is possible to perform a packet response to the network even while maintaining the power consumption mode.

  In the information processing apparatus and the information processing method according to the present invention, when a PING packet is received during the power saving mode, the power saving state is maintained, and a response to the PING is performed without using a CPU or memory that consumes a large amount of power. By doing so, power consumption can be reduced.

  In addition, the program according to the present invention can realize a function for enabling a computer to respond to a packet with respect to a network even when the power-saving mode is maintained.

  Exemplary embodiments of an information processing apparatus, an information processing method, and a program according to the present invention will be explained below in detail with reference to the accompanying drawings.

(Embodiment 1)
FIG. 1 is a block diagram illustrating a functional configuration including a controller board 1 that controls a printer of the information processing apparatus according to the first embodiment and a printing unit 2.

  The printer controller board 1 includes an application specific integrated circuit (ASIC) 10, a memory 11 including a DDR-SDRAM, and various packet data (hereinafter abbreviated as “packets”) between the network. Physical layer unit (PHY: PHY, hereinafter abbreviated as “PHY”) 12 for transmitting and receiving, PHY clock generation unit 13, ASIC clock generation unit 14, recording medium 15, operation unit (Operation Panel: OP, hereinafter) (Abbreviated as “OP”) 16, hard disk device (HDD) 17, board power control unit 18, external power control unit 19, nonvolatile memory (RAM) 36, first ROM 37 storing programs and data. The second ROM 38 storing the MAC address is mounted. As the recording medium 15, various media including a memory card (Memory Card, registered trademark) and a secure digital card (Secure Digital Card: SD card, registered trademark) can be used.

  The first ROM 37 stores two programs and data. The two programs are a first program that operates when the power is turned on and a second program that is started from the first program. When the power is turned on, the CPU 20 executes the first program on the first ROM 37 and loads the second program onto the memory 11. The second program loaded on the memory 11 is executed after executing the first program.

  After starting the second program, the CPU 20 uses the MAC address stored in the second ROM 38 as the request source hardware address (SHA) (55 in FIG. 13 described later) in the register section of the PE 24 (register section 51 in FIG. 13 described later). ).

  The RAM 36 stores the IP address of this printer, and the IP address can be changed by a request from the OP 16. The changed IP address is stored in the RAM 36 by the CPU 20. Since the RAM 36 is a non-volatile memory, the contents can be retained even when the power is turned off. Further, the CPU 20 stores the IP address on the RAM 36 in the request source IP address (SIP) (56 in FIG. 13 described later) in the register section of the PE 24 (register unit 51 in FIG. 13 described later).

  The ASIC 10 includes a CPU 20 that is a main control unit, a memory interface unit (hereinafter abbreviated as “MEMI / F”) 21 for exchanging data with the memory 11, and a media access control unit (Media Access Control) that communicates with the PHY 12. MAC, hereinafter abbreviated as “MAC”) 22, packets output from MAC 22, packet filter unit (hereinafter abbreviated as “PF”) 23 for selecting the type of the packet, packets output from PF 23 Network packet engine processing unit (hereinafter abbreviated as “PE”) 24, data processed by PE 24 and data from internal bus (Internal Bus) 34 are received, one of which is received by MAC 22 Selector (SEL) 2 to send to It is equipped with.

  In addition, the CG 26, a data transfer interface (I / F) unit (hereinafter abbreviated as “I / F”) 27 including a PCI interface (I / F) unit, and a recording medium interface for reading / writing data from / to the recording medium 15 Unit (hereinafter abbreviated as “memory card I / F unit”), recording medium interface (I / F) unit (hereinafter abbreviated as “recording medium I / F”) 28, and operation panel interface unit for controlling input / output of OP16 (Hereinafter abbreviated as “OPEI / F”) 29, a hard disk drive interface unit (hereinafter abbreviated as “HDD I / F”) 30 for controlling reading and writing of data with respect to the HDD 17, a general-purpose input / output interface unit (hereinafter “I / OI”). / F ") 31). For example, if the recording medium is a memory card, the recording medium I / F 28 is a memory card interface unit (Memory Card I / F) unit.

  Further, a power management unit (hereinafter abbreviated as “PM”) 32 and a timer 33 that control power supply from a power source (not shown) to the internal and external parts of the controller board 1 are mounted.

  Inside the ASIC 10, there are a power off area 35, an area where the power supply from the power source can be controlled by the PM 32, and an area other than the power off area 35 where power is always supplied. is there.

  The power-off area 35 includes the I / F 27, the recording medium I / F 28, the OPEI / F 29, the HDD I / F 30, and the I / OI / F 31, and is an area that includes portions not directly related to the network operation.

  The controller board 1 is connected to a printing unit (Plotter) 2 via a bus 3, and is connected to an internal bus 34 via an I / F 27 of the ASIC 10.

  After the printer is turned on, the PM 32 of the ASIC 10 has a normal operation mode related to power supply, which will be described in detail later, and an energy saving mode (also referred to as a “low power consumption mode”) which is a different type of power saving mode. The controller mode (low power consumption mode and controller mode is one type of power saving mode) is selected from among three types of modes to supply and stop power to the CPU 20, and the power off area inside the ASIC 10 The power supply to each part in 35 is stopped and the board power control unit 18 and the external power control unit 19 are controlled.

  The PM 32 also controls the power consumption of the memory 11 via the MEMI / F 21 by notifying the MEMI / F 21 of the transition to one of the above three modes. Note that the PM 32 also has a function of shifting the CPU 20 to the suspend mode with low power consumption, and may notify the CPU 20 to enter the suspend mode and cancel the suspend mode.

  In the printer of this embodiment, a case where two types of power saving modes different from the energy saving mode and the controller mode will be described as power saving modes. However, when other different types of power saving modes can be executed, The processing described later can also be performed in this mode.

  In the control of the power consumption of the memory 11, when the mode is shifted to the energy saving mode, the PM 32 shifts the memory 11 to the self-refresh mode via the MEMI / F 21, and the memory 11 stores information on the state before the shift to the energy saving mode. , Shift to energy saving mode.

  Further, when shifting to the normal operation mode or the controller mode, the PM 32 shifts the memory 11 to the normal operation mode via the MEMI / F 21, and the memory 11 can be accessed via the internal bus 34. At that time, when the memory 11 returns from the energy saving mode to the normal operation mode, the memory 11 returns to the information of the state before the transition to the energy saving mode.

  Next, a process of shifting to each mode relating to power supply in the printer will be described. FIG. 2 is a transition diagram of transition to each mode related to power supply in the printer shown in FIG.

  In each mode relating to power supply in the printer, the normal operation mode M1 for supplying power for the entire printer, and supplying power to a part of the printer and stopping the power supply to the other parts to reduce power consumption. As power consumption modes to be performed, there are an energy saving mode (hereinafter abbreviated as “energy saving mode”) M2 and a controller mode M3.

  First, when a power button (not shown) of the printer is turned on, power from the power source is supplied to the ASIC 10 and the PM 32 sets the normal operation mode M1. In the normal operation M1 mode, the PM 32 supplies power from the power source to the CPU 20 and the memory 11 as usual. Furthermore, power supply to each part (I / F 27, recording medium I / F 28, OPEI / F 29, HDD I / F 30, I / OI / F 31) in the power-off area 35 is started, the board power control unit 18, external power The control unit 19 supplies power to each part inside and outside the controller board 1. Then, the ASIC 10 starts control of the entire printer.

  Further, when the normal operation mode M1 is entered, the PM 32 starts the timer 33, and the PF 23 makes this printer (own station) from the network even if the time of the timer 33 exceeds a predetermined time set in advance from the setting of the normal operation mode M1. When no packet addressed is received and all the applications running on the CPU 20 are in an idle state, the process shifts to the energy saving mode M2.

  The absence of reception of a packet addressed to the printer (own station) can be recognized by an empty flag from the buffer of the PF 23 (a buffer 42 in FIG. 12 described later).

  Similarly, the controller mode M3 shifts to the energy saving mode M2.

  When the PM 32 shifts the power consumption mode to the energy saving mode, the PM 32 sets the CPU 20 and the memory 11 to the low power consumption mode. Furthermore, the supply of power to each unit in the power-off area 35 inside the ASIC 10 is stopped, and the board power control unit 18 stops the supply of power from the power source to the recording medium 15, OP16, and HDD 17, and external power The control unit 19 stops the supply of power from the power source to each unit (not shown except the printing unit 2) including the printing unit 2 outside the controller board 1. The PHY 12 and the PHY clock generation unit 13 are always supplied with power after the printer is turned on.

  When the MAC 22 receives a packet from the network via the PHY 12, the MAC 22 outputs the packet to the PF 23. The PF 23 examines the contents of the packet, discards a packet not addressed to the own printer (addressed to the own station), and is addressed to the own station. If the packet is to be processed by PE 24, it is sent to PE 24.

  The packet to be processed by the PE 24 includes, for example, an IP packet ARP request (Address Resolution Protocol Request, hereinafter abbreviated as “ARP request”). The above-mentioned ARP (ARP) is an address resolution protocol.

  When the PE 24 receives the ARP request, the PE 24 generates an ARP response packet (ARP response, hereinafter abbreviated as “ARP response”) based on the content of the ARP request, and passes the ARP response packet through the SEL 25 and the MAC 22. Then, the data is transferred from the PHY 12 to the network.

  Other packets to be processed by the PE 24 include a “Ping command” of a packet arrival confirmation command transmitted from the host side. When this Ping command is received from the host side, it is returned to the host for confirmation of reception.

  First, when the packet received from the network is a non-print request packet during the energy saving mode, the PF 23 notifies the PM 32, and the PM 32 sets the power consumption mode to the controller mode and shifts from the energy saving mode to the controller mode. . When the power consumption mode is the controller mode, the PM 32 sets the CPU 20 and the memory 11 to the normal mode.

  Further, the supply of power from the power supply to each part of the power-off area 35 in the ASIC 10 is stopped, and the power supply from the power supply to the recording medium 15, OP16, and HDD 17 is stopped by the board power control unit 18, and the external The power control unit 19 stops supplying power from the power source to each unit including the printing unit 2.

The non-print request packet includes http (HyperText Transfer).
Protocol), SNMP (Simple Network Management)
Protocol). SNMP uses UDP (User Datagram Protocol).

  Details of the contents of the SNMP are described in a standard document that is a specification of a standard protocol defined by IETF (Internet Engineering Task Force) including RFC 1155, RFC 1157, and RFC 1213, and thus description thereof is omitted.

  MIB (Management Information Block) information defined in RFC1213 is information that is disclosed to inform the outside of the state of the device itself, and can be acquired from the outside using the SNMP. The printer device information (MIB information) is set in the memory 11.

  If the MIB information in the memory 11 is updated before shifting from the normal operation mode to the controller mode or the energy saving mode, the normal MIB information can be accessed in the controller mode.

  Next, when the packet received from the network is the print request packet during the energy saving mode or the controller mode, the PF 23 notifies the PM 32, and the PM 32 shifts from the energy saving mode or the controller mode to the normal operation mode. Control.

  The print request packet includes, for example, LPD (TCP Port 515), FTP (TCP Port 21), and HP network printer compatible protocol (TCP Port 9100) (the above protocols are registered trademarks).

  Even if a non-print request packet is received in the normal operation mode, the controller mode is not entered.

  Next, the types of packets that the printer receives from the network will be described.

1. Ethernet packet ("Ethernet" is a registered trademark)
FIG. 3 is an explanatory diagram of the structure of the frame format of the Ethernet packet. FIG. 4 is an explanatory diagram showing an example of the data contents of each field in the Ethernet frame.

  The Ethernet packet includes a preamble, a destination MAC address, a source MAC address, a type, data, and FCS.

As shown in FIG. 4, the preamble is information indicating the start of a frame having a data length of 64 bits (8 bytes), and “10” is alternately input so that the last two bits become “11”. The MAC address and the source MAC address are respectively the address of the packet destination device (for example, a communication device including this printer) and the address of the packet sender device, both of which have a data length of 48 bits (6 bytes). . The MAC (Media Access Control) is defined in IEEE 802-1990.

  The destination MAC address includes a unicast address that identifies each communication device in the network, a broadcast address that targets communication devices in the entire broadcast domain in the network, and each in a group of predetermined communication devices in the network. There is a multicast address that is targeted for communication equipment.

  In the case of the broadcast address, all bits are 1. The above types are IPv4 protocol for 0x0800, ARP protocol for 0x0806, IPv6 protocol for 0x86DD, AppleTalk protocol for 0x809B, and IPX (NetWare) protocol for 0x8037, 0x8191. Indicates the NetBIOS / NetBEUI protocol (the above protocols are registered trademarks).

  FIG. 5 is a diagram showing the correspondence between both frames when an ARP packet is constructed from the Ethernet packet. As shown in FIG. 5A, an Ethernet packet includes a preamble, a destination MAC address, a source MAC address, a type, data, and an FCS, and the destination MAC address, the source MAC address, and the type constitute an Ethernet header. To do. The data can be specified in a length of 46 to 1500 bytes, and the FCS is a checksum generated by a CRC-32 polynomial.

  As shown in FIG. 5B, when an ARP packet is configured from the Ethernet packet, the ARP request includes the data of the Ethernet packet in the ARP packet and 1 is stored in the operation code field in the ARP packet. Indicates a packet, and when 2 is stored, indicates an ARP response packet. Further, as indicated by a wavy line in the figure, 0x0806 of data indicating the ARP protocol may be added at the head.

2. ARP packet When IP is described in the following description, it means IPv4. FIG. 6 is an explanatory diagram showing the format of the ARP packet, and FIG. 7 is an explanatory diagram showing an example of the data contents of each field in the ARP packet.

  As shown in FIG. 6, the ARP packet includes a hardware type field, a protocol type field, a hardware address length (HLEN) field, a protocol address length (PLEN) field, an operation code field, a transmission source hardware address field, and a transmission source. It consists of an IP address field, a destination hardware address field, and a destination IP address field.

  As shown in FIG. 7, the hardware type field has a data length of 16 bits, and stores 0x0001 when indicating an Ethernet packet. The protocol type field has a data length of 16 bits, uses an IP address, and stores 0x0800 when indicating the IPv4 protocol.

  The hardware address length field has a data length of 8 bits and stores 6-byte data indicating the MAC address. For example, 0x06. The protocol address length field has a data length of 8 bits, and stores 0x04 when indicating the IPv4 protocol.

  The operation code field has a data length of 16 bits. When it is 1, it indicates an ARP request, and when it is 2, it indicates an ARP reply. The transmission source hardware address field, the transmission source IP address field, the destination hardware address field, and the destination IP address field have data lengths of 48, 32, 48, and 32, respectively. An address, a destination hardware address, and a destination IP address are stored.

3. IP Packet FIG. 8 is an explanatory diagram showing the format of the IP packet, and FIG. 9 is an explanatory diagram showing an example of the data contents of each field of the IP header in the IP packet.

As shown in FIG. 8, an IP packet is composed of a header part (IP header) and a data part. The header part is a version (Version) field, a header length (IHL) field, a service type (Type Of Service) field, and a packet length. (Total
Length field, identifier field, flags field, fragment offset field, time to live field, protocol number field, header checksum field, header checksum field, transmission It consists of an original IP address (Source Address) field and a destination IP address (Destination Address) field.

  Further, an option may be attached, and padding is performed so that the data length of the field including the option (Options) and padding (Padding) is a multiple of 32 bits. Normally no options are used.

  FIG. 9 shows the data length of each field, an example value, and a remark. In particular, the version field has a data length of 4 bits and stores 4 in the case of the IPv4 protocol and 6 in the case of the IPv6 protocol. The header length field has a data length of 4 bits and is 20 bytes in the case of the IPv4 protocol.

  In the survival time field, the value of the lifetime of the packet on the network is stored, and the value is decremented by 1 every time it passes through the router, and when it reaches 0, the packet is discarded. Since the details are described in RFC2200, the description is omitted.

  The service type is described in RFC 791 and the details of the protocol number are described in RFC 1700.

  The value stored in the identifier field is used as an identifier when restoring the fragment. The flag field stores a value indicating control related to packet division.

4). TCP Packet FIG. 10 is a diagram showing the correspondence between frames when an IP packet and a TCP packet are constructed from the Ethernet packet. FIG. 11 is an explanatory diagram showing the format of a TCP packet.

  As shown in FIG. 10A, an Ethernet packet is composed of a preamble, a destination MAC address, a source MAC address, a type, data, and an FCS, and the destination MAC address, the source MAC address, and the type constitute an Ethernet header. To do. The data can be specified in a length of 46 to 1500 bytes, and the FCS is a checksum generated by a CRC-32 polynomial.

  As shown in FIG. 10B, when an IP packet is configured from the Ethernet packet, an IP header and Ethernet packet data are included in the IP packet. Further, as indicated by a wavy line in the figure, 0x0800 of data indicating the IP protocol may be added to the head.

  As shown in FIG. 10C, when a TCP packet is configured from the IP packet, the TCP header and the IP packet data are included in the TCP packet. In the TCP header, the code bit includes FIN in the 0th bit, SYN in the 1st bit, RST in the 2nd bit, PSH in the 3rd bit, ACK in the 4th bit, and URG in the 5th bit. Further, as indicated by a wavy line in the figure, 6 of data indicating the TCP protocol may be added to the head.

  As shown in FIG. 11, a TCP packet is composed of a TCP header portion (TCP header) and a data portion, a source port number (Source Port, 16 bits) field, a destination port number (Destination Port, 16 bits) field, and a sequence. Number (Sequence Number, 32 bits) field, Acknowledgment Number (Acknowledgement Number, 32 bits) field, Data Offset (Data Offset, 4 bits) field, Reserved (Reserved, 6 bits) field, Code bits (6 bits) field, Window size (16-bit) field, checksum (Checksum, 16-bit) field, urgent pointer (Urgent Pointer) Consisting of 16-bit) field.

  In addition, there may be options and padding, followed by data. The port numbers of the source port number and the destination port number stored in the source port number field and the destination port number field are used for application identification. In addition, there is a number (published by RFC1700) determined as a standard as a well-known port number. The details of TCP are described in RFC793, and thus the description thereof is omitted.

5). UDP Packet FIG. 12 is an explanatory diagram showing the format of a UDP packet.

  The UDP packet includes a transmission source port number (16 bits) field, a destination port number (16 bits) field, a segment length (16 bits) field, a checksum (16 bits) field, and data.

  The port numbers of the source port number and the destination port number stored in the source port number field and the destination port number field are used for application identification. In addition, there is a number (published by RFC1700) determined as a standard as a well-known port number. Details of UDP are described in RFC 768, and thus description thereof is omitted.

  Next, the PF 23 will be described. FIG. 13 is a block diagram showing an example of the internal configuration of the PF 23 shown in FIG. The PF 23 is composed of an address filter 40, a pattern filter 41, and a buffer 42.

  A unicast address and a multicast address can be registered in the address filter 40. In addition, it is possible to set an address of a device including the accessible printing unit 2 in the printer.

  The address filter 40 refers to the type of packet input from the MAC 22, determines the type of the packet from the type, passes only the packet of the accessible device, sends it to the pattern filter 41, and discards the other packets. Select. Regardless of the setting of the address filter 40, the broadcast packet is passed and sent to the pattern filter 41.

  The pattern filter 41 includes a mask area and a non-mask area. The mask area is a matching condition regardless of the packet value. In the non-mask area, comparison data can be set in byte units. The mask area can be set in units of bytes.

  The sum of the data length of the mask area and the data length of the non-mask area becomes the pattern filter length. For example, the pattern filter length is 64 bytes. A value of pattern offset 1 can be set in the pattern filter 41. The pattern offset 1 is the offset length from the start of the Ethernet frame.

  When the filtering by the pattern filter 41 is started from the type of the Ethernet frame, the value obtained by adding the destination MAC address length and the source MAC address is the length of the pattern offset 1.

  A pattern offset 2 indicates an offset from the head of the pattern filter 41. One byte from the pattern offset can be filtered bit by bit by the bit mask value. Bits for which 1 is set as the bit mask value are mask areas.

  The pattern filter 41 determines whether the packet received from the address filter 40 is a non-print request packet or a print request packet. If the packet is a non-print request packet, the pattern filter 41 notifies the PM 32 to that effect. Notifies PM 32 of the fact and outputs the packet after filtering to the buffer 42. If the packet received from the address filter 40 is an ARP request packet, a PE_ON signal is sent to the SEL 25 and the ARP request packet is output to the PE 24.

  The buffer 42 temporarily stores the packet filtered by the pattern filter 41 and transmits it to each unit that performs processing via the internal bus 34. Also, the fact that there is no packet received by the PF 23 can be understood by the fact that an empty flag (empty flag), which is an empty flag indicating that the buffer 42 of the PF 23 is empty, becomes active.

  When the pattern of the ARP request packet is set in the pattern filter 41, the PE_ON signal can be activated. That is, when the ARP request packet is received, the PE_ON signal becomes active, and the PE 24 makes an ARP reply response.

  When the PE_ON signal is not active, after passing through the PF 23, it is stored in the memory 11 via the MEMI / F 21 and processed by the CPU 20. When a print request or non-print request packet other than the ARP request packet is received, the PE_ON signal is not activated.

  Next, the PE 24 will be described. FIG. 14 is a block diagram for explaining the internal processing of the PE 24. The PE 24 includes a packet analysis unit 50, a register unit 51, and a packet generation unit 52.

  The packet analysis unit 50 inputs the ARP request packet from the PF 23.

  The ARP request packet is sent from the destination MAC address field 60, SHA61, ARP62, hardware type field 63, protocol field 64, MAC address length field 65, protocol address length field 66, ARP request field 67, SHA68, SIP69, DHA70, DIP71. Become.

  The packet analysis unit 50 analyzes each value of the request source hardware address (SHA) field 68 and the request source IP address (SIP) field 69 in the ARP request packet, and outputs the destination hardware address (DHA) of the register unit 51. A request source hardware address (SHA) is set in 53 and a request source IP address (SIP) is set in the destination IP address (DIP) 54. In addition, the CPU 20 sets the printer hardware address in the request source hardware address (SHA) 55 of the register unit 51 in advance, and sets the printer IP address in the request source IP address (SIP) 56. deep.

  The packet generation unit 52 generates an ARP response packet including an Ethernet header 80 and an ARP reply packet 81. The Ethernet header 80 includes a destination hardware address (DHA) field 82, a request source hardware address field (SHA) 83, and a type field 84, and a value read from the destination hardware address (DHA) 53 of the register unit 51. The values read from the request source hardware address (SHA) 55 are set in the SHA 83 in the DHA 82. In the type field 84, 0x0806 indicating an ARP packet is set.

  An ARP reply packet 81 is set as the data part.

  In the hardware type field 85 of the ARP reply packet 81, 1 is set in the case of Ethernet. The protocol field 86 is set to 0x0800 because TCP / IP is used. 6 is set in the MAC address length field 87. The protocol address length field 88 is set to 4 because IPv4 is used. In the OP field 89, 2 indicating ARP reply is set.

  In the request source hardware address field 90, the value of the SHA 55 of the register unit 51, in the request source IP address field 91, the value of the SIP 56 in the register unit 51, and in the destination hardware address field 92, the value of the register unit 51. The value of DHA 53 and the value of DIP 54 of register 51 are set in destination IP address field 93, respectively.

  Since the FCS of the Ethernet packet is automatically generated by the MAC 22, it is not necessary for the packet generator 52 to generate it. In order to transmit the ARP response packet generated by the packet generation unit 52 to the network, when the PE_ON signal output from the PF 23 becomes active, the SEL 25 transmits the ARP response packet output from the PE 24 to the MAC 22. When the PE_ON signal is inactive, data from the internal bus 34 is input to the MAC 25.

  As described above, the ARP response packet generated by the packet generation unit 52 is transmitted to the network via the SEL 25, the MAC 22, and the PHY 12.

  Next, an example of TCP packet filtering processing in the PF 23 will be described. FIG. 15 is an explanatory diagram of an example of a TCP packet that is passed through the filtering process in the PF 23. 15A shows the format of the TCP packet. As shown in FIG. 15B, the pattern filter 41 of the PF 23 adds the destination MAC address length and the source MAC address length as the pattern offset 1. Set the value.

  The pattern filter 41 refers to the first 16-bit type of the TCP packet. In the case of a TCP packet, 0x0800 indicating the IP protocol is set as the above type.

  Furthermore, a comparison value with the IP header of the TCP packet is set. The TCP protocol number is set as the protocol number of the IP header, the IP address of this printer is set as the destination IP address, and the other IP headers are set as mask areas (shaded portions in the figure). Further, a comparison value with the TCP header is set, a port number of an application to be used is set as a destination port number of the TCP header, and a comparison value with a code bit of the TCP header is set.

  Next, a description will be given of a setting for allowing a TCP packet having a SYN bit of 1 as a connection establishment request to pass by the pattern filter 41. In the TCP packet, the code bit is present in the 14th byte from the head of the TCP header, so the pattern offset 2 is set to 13 in the pattern filter 41 as shown in FIG.

  If 0x02 is set in the 14th byte of the pattern filter 41, it can be compared with the SYN of the code bit of the TCP packet shown in FIG. Further, when the bit mask value is set to 0xC2, a TCP packet having a code bit SYN of 1 can be passed.

  The other part corresponding to the header area of the TCP packet is a mask area (the hatched part in the figure). Further, the part after the bit masking shown in FIG. 15B is also set in the mask area (the hatched part in the figure).

  In the case of an http application, the destination port number is set to 80, and in the case of LPD as a printing protocol, the destination port number is set to 515. When filtering bits other than SYN, for example, ACK, the bit mask value may be changed to 0xD0.

  When the destination port number 515 of the LPD application, which is a printing protocol, is set in the pattern filter 41, when a TCP corresponding thereto is received, the print request signal is activated and notified to the PM 32.

  Next, an example of UDP packet filtering processing in the PF 23 will be described. FIG. 16 is an explanatory diagram of an example of a UDP packet that is passed through the filtering process in the PF 23. FIG. 16A shows an example of a UDP packet. As shown in FIG. 16B, the pattern filter 41 of the PF 23 adds the destination MAC address length and the source MAC address length as the pattern offset 1. Set the value. The pattern filter 41 refers to the first 16-bit type of the UDP packet. In the case of a UDP packet, 0x0800 indicating the IP protocol is set as the above type.

  Further, a comparison value with the IP header of the UDP packet is set. The UDP protocol number is set as the protocol number of the IP header, the IP address of the printer is set as the destination IP address, and the other IP headers are set as mask areas (shaded portions in the figure).

  Furthermore, the comparison value with the UDP header is set, the port number of the application to be used is set as the destination port number of the UDP header, and the other UDP header area is a mask area (the hatched portion in the figure). To do. Further, the part after the UDP header area is also set as a mask area (the hatched part in the figure).

  If the port number of the application that accesses the MIB information using the SNMP protocol is set as the destination port number, when the MIB information is visited, it can be filtered by the port filter.

  Next, an example of ARP packet filtering processing in the PF 23 will be described. FIG. 17 is an explanatory diagram of an example of an ARP packet that is passed through the filtering process in the PF 23. 17A shows an example of an ARP packet. As shown in FIG. 17B, the pattern filter 41 of the PF 23 is set to 0 as the pattern offset 1, and the frame of the ARP packet is started. Allow comparison.

  First, the comparison value of the Ethernet header of the ARP packet is set in the pattern filter 41. Further, since the ARP protocol is broadcast to the destination MAC address that is the first part of the frame, 1 is set in all bits. Further, the source MAC address is set as a mask area (the hatched portion in the figure).

  Since 0x0806 indicating the ARP protocol is set in the Ethernet header type, a comparison value with the ARP packet type is set in the pattern filter 41. After that, the hardware type is 1, the protocol field is IP, the MAC address length is 6, the protocol address is IPv4, 4 and the operation code is set to 1 indicating an ARP request.

  Mask areas (shaded portions in the figure) are set in the transmission source hardware address (SHA), transmission source IP address (SIP), and destination hardware address area (DHA), respectively. The IP address of this printer is set as the destination IP address (DIP), and the remaining portion is set as a mask area (the hatched portion in the figure).

  With the above settings, filtering can be performed when an ARP request packet is broadcast to this printer. When the destination port number 80 of the http application that is a non-printing protocol and the SNMP protocol are set in the pattern filter 41, when a corresponding ARP request packet is received, the non-printing request signal is activated and notified to the PM 32. When the ARP packet is set in the pattern filter 41, the PE_ON signal to the SEL 25 is activated when the ARP request packet is received.

  Since this printer performs part of packet processing for the network not by CPU processing but by the network packet processing unit, the power consumption mode of each unit including the CPU other than the network packet processing unit can be maintained, so that power consumption Can be further reduced.

  Further, since the power consumption mode is changed according to the packet, the energy saving effect can be improved. Furthermore, since the CPU is built in the ASIC, the power consumption can be further reduced.

(Embodiment 2)
FIG. 18 is a block diagram illustrating a functional configuration including the controller board 1801 that controls the printer of the information processing apparatus according to the second embodiment and the printing unit 2.

  As in the first embodiment, the controller board 1801 of the printer includes an ASIC 1810, a memory 11 including a DDR-SDRAM, a network PHY 12, a PHY clock generator 13, and an ASIC for transmitting and receiving various packets to and from the network. Clock generator 14, recording medium 15, OP16, hard disk device (HDD) 17, board power controller 18, external power controller 19, nonvolatile memory (RAM) 36, first ROM 37 storing programs and data, MAC A second ROM 38 in which an address is stored is mounted.

  As in the first embodiment, the ASIC 1810 includes a CPU 20, a MEMI / F 21, a MAC 22, a PF 1823, a PE 1824, and a selector (SEL) 25 that are main control units. Here, in the present embodiment, the PF 1823 and the PE 1824 are different from those in the first embodiment, and other configurations are the same as those in the first embodiment.

  The PF 1823 examines the contents of the packet received by the MAC 22 from the network via the PHY 12 and discards the packet not addressed to the own printer (addressed to the own station). If the packet addressed to the own station is a packet to be processed by the PE 1824, Send to PE1824.

  The packet to be processed by the PE 1824 includes, for example, an IP packet ARP request (Address Resolution Protocol Request, hereinafter abbreviated as “ARP request”). The above-mentioned ARP (ARP) is an address resolution protocol.

  When the PE 1824 receives the ARP request, the PE 1824 generates an ARP response packet based on the content of the ARP request, and transfers the ARP response packet from the PHY 12 to the network via the SEL 25 and the MAC 22.

  Other packets to be processed by the PE 1824 include a “PING command” of a packet arrival confirmation command transmitted from the host side. When this PING command is received from the host side, it is returned to the host for confirmation of reception.

  The formats of the Ethernet frame, ARP packet, IP packet, TCP packet, and UDP packet that the printer receives from the network are the same as those in the first embodiment. In the present embodiment, an ICMP packet is further received.

  FIG. 19 is a diagram illustrating a format of an IP packet and an ICMP packet in an Ethernet frame. As shown in FIG. 19A, the Ethernet frame is composed of a preamble, a destination MAC address, a source MAC address, a type, data, and an FCS, and the destination MAC address, the source MAC address, and the type constitute an Ethernet header. To do. The data can be specified in a length of 46 to 1500 bytes, and the FCS is a checksum generated by a CRC-32 polynomial.

  When configuring an IP packet, as shown in FIG. 19B, an IP header and data are included in the data of the Ethernet frame. Further, as indicated by the wavy line in the figure, the type of the Ethernet header indicates 0x0800 of data indicating the IP protocol.

  When the ICMP packet is configured, as shown in FIG. 19C, the ICPM packet is encapsulated in the data portion of the IP packet, and the type of the ICMP packet, the ICMP header, and the data are included. The type is “8” in the case of an ICMP echo request (echo request) packet, and “0” in the case of an ICMP echo reply (echo response) packet. In the ICMP header, “0” is always stored as a code bit in the ICMP echo request packet and the ICMP echo reply packet. Furthermore, the data has an arbitrary length, but usually has a data length of 64 bytes. Further, as indicated by the wavy line in the figure, the protocol of the IP header indicates 1 of data indicating the ICMP protocol.

  FIG. 20 is an explanatory diagram showing the format of an ICMP echo request and an ICMP echo reply packet. An ICMP echo request and an ICMP echo reply packet include a message type field, a code field, a checksum field, an identifier field, a sequence number field, and data.

  Since the ICMP echo packet is a publicly described description, the detailed description thereof is omitted, but the message type field stores “8” in the case of the ICMP echo request packet described above and “0” in the case of the ICMP echo reply packet. It is an area. As described above, the code field is an area that always stores “0” in the case of the ICMP echo request packet and the ICMP echo reply packet.

  Next, the PF1823 will be described. FIG. 21 is a block diagram showing an example of the internal configuration of the PF 1823 shown in FIG. The PF 1823 is composed of an address filter 2140, a pattern filter 2141, and a buffer 42.

  A unicast address and a multicast address can be registered in the address filter 2140. In addition, it is possible to set an address of a device including the accessible printing unit 2 in the printer.

  The address filter 2140 refers to the type of the packet input from the MAC 22, determines the type of the packet from the type, passes only the packet of the accessible device and sends it to the pattern filter 2141, and discards the other packets. Select. In the address filter 2140 of this embodiment, in addition to the packet type determined by the address filter 40 of the first embodiment, whether the packet is an ICMP packet is determined from the packet type. Regardless of the setting of the address filter 2140, the broadcast packet is passed and sent to the pattern filter 2141.

  The pattern filter 2141 includes a mask area and a non-mask area as in the first embodiment. The processing by the pattern filter 2141 is performed in the same manner as in the first embodiment. As in the first embodiment, the pattern filter 2141 determines whether the packet received from the address filter 2140 is a non-print request packet or a print request packet. In this embodiment, the received packet is an ICMP packet. If there is, it is determined that the request is a non-print request. The buffer 42 has the same function as in the first embodiment.

  Next, the PE1824 will be described. The internal processing in PE 1824 when filtering ARP packets is the same as in the first embodiment. That is, the PE 1824 includes a packet analysis unit 50, a register unit 51, and a packet generation unit 52, and each function is the same as that of the first embodiment.

  Next, an example of TCP packet filtering processing in the PF 1823 will be described. FIG. 22 is an explanatory diagram of an example of a TCP packet that is passed through the filtering process in the PF 1823. 22A shows the network frame format of the TCP packet. As shown in FIG. 22B, the pattern filter 2141 of the PF 1823 has a destination MAC address length and a source MAC address as the pattern offset 1. Set the value with the length added.

  The pattern filter 41 refers to the first 16-bit type of the TCP packet. In the case of a TCP packet as the above type, 0x0800 indicating the IP protocol is set in the first 16 bits.

  Furthermore, a comparison value with the IP header of the TCP packet is set. IPv4 4 is set in the version (Ver) of the IP header, 5 is set in the header length, the TCP protocol number is set in the protocol number, and the IP address (local address) of the printer is set in the destination IP address. The other IP headers are set as mask areas (shaded portions in the figure).

  Further, a comparison value with the TCP header is set, a port number of an application to be used is set as a destination port number of the TCP header, and a comparison value with a code bit of the TCP header is set.

  Next, a description will be given of a setting for allowing a TCP packet having a SYN bit of 1 as a connection establishment request to pass by the pattern filter 2141. In the TCP packet, the code bit is present in the 14th byte from the head of the TCP header, so the pattern offset 2 is set to 13 in the pattern filter 2141 as shown in FIG.

  When 0x02 is set in the 14th byte of the pattern filter 41, it can be compared with the code bit SYN of the TCP packet shown in FIG.

  Further, when the bit mask value is set to 0xC2, a TCP packet having a code bit SYN of 1 can be passed.

  The other part corresponding to the header area of the TCP packet is a mask area (the hatched part in the figure). Further, the part after the bit masking shown in FIG. 22B is also set in the mask area (the hatched part in the figure). In the case of an http application, the destination port number is set to 80, and in the case of LPD as a printing protocol, the destination port number is set to 515. When filtering bits other than SYN, for example, ACK, the bit mask value may be changed to 0xD0.

  When the destination port number 515 of the LPD application, which is a printing protocol, is set in the pattern filter 2141, when the TCP corresponding thereto is received, the print request signal is activated and notified to the PM 32.

  Next, an example of UDP packet filtering processing in the PF 1823 will be described. FIG. 23 is an explanatory diagram of an example of a UDP packet that is passed through the filtering process in the PF 1823.

  23A shows an example of a network frame format of a UDP packet. As shown in FIG. 23B, the pattern filter 2141 of the PF 23 has a destination MAC address length and a transmission source as a pattern offset 1. A value obtained by adding the MAC address length is set.

  The pattern filter 2141 refers to the first 16-bit type of the UDP packet. In the case of a UDP packet as the above type, 0x0800 indicating the IP protocol is set in the first 16 bits.

  Further, a comparison value with the IP header of the UDP packet is set. IPv4 4 is set in the version (Ver) of the IP header, 5 is set in the header length, the UDP protocol number is set in the protocol number, and the IP address (local address) of the printer is set in the destination IP address. The other IP headers are set as mask areas (shaded portions in the figure).

  Furthermore, the comparison value with the UDP header is set, the port number of the application to be used is set as the destination port number of the UDP header, and the other UDP header area is a mask area (the hatched portion in the figure). To do.

  Further, the part after the UDP header area is also set as a mask area (the hatched part in the figure).

  If the port number of the application that accesses the MIB information using the SNMP protocol is set as the destination port number, when the MIB information is visited, it can be filtered by the port filter.

  An example of the ARP packet that is passed through the filtering process in the PF 1823 is the same as that in the first embodiment.

  Next, the processing of the PE 1824 when making a PING response will be described. FIG. 24 is a block diagram for explaining internal processing in PE 1824 when filtering ICMP packets, and the same reference numerals are given to portions common to FIG. 14 of the first embodiment.

  The internal configuration of the PE 1824 in this process includes a packet analysis unit 2450, a register unit 51, and a packet generation unit 2552. Here, the register unit 51 is the same as that of the first embodiment. Here, the ICMP echo request packet from the PF 1823 is input to the packet analysis unit 2450.

  The ICMP echo request packet is composed of 100 to 118 fields.

  The packet analysis unit 2450 analyzes each value of the request source hardware address (SHA) in the field 101 of the Ethernet header and the request source IP address (SIP) in the field 111 of the IP header in the ICMP echo request packet. The requesting hardware address (SHA) is set in the destination hardware address (DHA) 53 of the unit 51, and the requesting IP address (SIP) is set in the destination IP address (DIP) 54.

  The IP data type field 113 stores “8” indicating an ICMP echo request packet.

  In addition, the CPU 20 sets the printer hardware address in the request source hardware address (SHA) 55 of the register unit 51 in advance, and sets the printer IP address in the request source IP address (SIP) 56. deep.

  The packet generator 2452 creates an ICMP echo reply packet. First, in creating the Ethernet header, the request source hardware address (SHA) set in the DHA 53 of the register unit 51 and the hardware address set in the SHA 55 are used as the DHA of the Ethernet header of the ICMP echo reply packet of the packet generation unit 52. Field 120 and SHA field 121, respectively.

  Also, 0x800 indicating the IP of the ICMP echo request packet type field 102 is copied to the ICMP echo reply packet field 122 of the packet generation unit 2452.

  Next, the IP header of the ICMP echo reply packet of the packet generator 2452 is created. First, the data in the fields 103 to 109 of the ICMP echo request packet of the packet analysis unit 2450 are copied to the fields 123 to 127 and 129 of the IP header of the ICMP echo reply packet of the packet generation unit 2452, respectively. Also, 255 is set in the TTL of the field 128. Further, a checksum is calculated after the copying and set in the field 130 of the ICMP echo reply packet.

  The checksum may be calculated using a known technique (for example, a 1's complement calculation method described in the book “Mastering TCP / IP Application” published by Ohm).

  Further, SIP 56 data of the register unit 51 is set in the SIP field 131, and DIP 54 data of the register unit 51 is set in the DIP field 132.

  Next, IP data of the ICMP echo reply packet of the packet generation unit 2452 is created. First, the ICMP echo reply packet type field 133 of the packet generator 2452 is set to “0” indicating the ICMP echo reply packet.

  Also, the code field 134 of the ICMP echo reply packet of the packet generator 52 is set to “0”, the checksum of the IP data is calculated, and set in the checksum (CheckSUM) field 135. The checksum may be calculated using a known technique (for example, a 1's complement calculation method described in the book “Mastering TCP / IP Application” published by Ohm).

  Further, the identifier data in the field 116 of the ICMP echo request packet of the packet analysis unit 2450 is copied to the field 136 of the ICMP echo reply packet of the packet generation unit 2452, and the sequence of the field 117 of the ICMP echo request packet in the packet analysis unit 2450 The data of the number is copied to the field 137 of the ICMP echo reply packet of the packet generation unit 2452, and the data of the field 118 of the ICMP echo request packet of the packet analysis unit 2450 is copied to the field 138 of the ICMP echo reply packet of the packet generation unit 2452. make a copy. In this way, it is possible to generate and respond to an ICMP echo reply packet without using the CPU and memory of the printer main body.

  Next, an example of ICMP packet filtering processing in the PF 1823 will be described. FIG. 25 is an explanatory diagram of an example of an ICMP packet that is passed through the filtering process of the PF 1823.

  FIG. 25 (a) shows the format of the network frame of the ICMP echo request packet. The format of the IP header in the data is the version (Ver), header length, service as shown in FIG. 25 (b). From each field storing values of type, packet length, identifier, flag, fragment, lifetime, protocol (in this case, “01” indicating ICMP), header checksum, source IP address, and destination IP address Become. Further, as shown in FIG. 25C, the format in the IP data is a type (in this case, type = 8 indicating an ICMP echo request packet), a code (always 0), a checksum, an identifier, and a sequence number. , And ICMP fields. The above type is 0 when indicating an ICMP echo reply packet.

  In the pattern filter 2141 of the PF 1823, as shown in FIG. 25D, a value obtained by adding the field length of the destination MAC address and the field length of the source MAC address is set as the pattern offset 1.

  The pattern filter 2141 sets “0x0800” indicating the IP protocol stored in the Ethernet header type of the Ethernet frame shown in FIG. 25A in the first 16 bits after the pattern offset 1. Also, “4” indicating IPv4 stored in the version (Ver) field of the IP header of the Ethernet frame shown in FIG. 25B, and “5” stored in the header length field of the IP header. Set.

  Furthermore, the ICMP protocol number is set as the protocol number, the IP address of the printer is set as the local IP address as the destination IP address, and “8” indicating the ICMP echo request packet is set as the ICMP type. The header is set as a mask area (the hatched portion in the figure).

  However, the comparison value len of the IP header packet length is set to 92 bytes or less.

  The 92 bytes are for the case where the ICMP data size is 64 bytes and the IP header length is 20 bytes.

  By setting as described above, when the packet data from the network is monitored by the PF 23 and the PF 1823 receives ICMP packet data of 64 bytes or less, it is detected that the packet is an ICMP echo request packet by PING. The PE 1824 can be notified.

  Then, an ICMP echo reply packet corresponding to the ICMP echo request packet is output via the network while maintaining the power saving mode, and a PING response can be made to the host device that has transmitted the ICMP echo request packet.

  In addition, when the size of the ICMP packet data exceeds 64 bytes, the PF 1823 notifies the PM 32 that the non-print request packet has been received and accumulates it in the buffer 42.

  In this case, processing is performed after transitioning to another power saving mode. Since the size of the ICMP packet data is usually 64 bytes, it is practically problematic to design the circuit so as to detect that the ICMP packet data is a PING packet only when the ICMP packet data is 64 in order to simplify the hardware. There is no.

  Next, the case where the destination IP address is a multicast address registered in the address filter will be described. In the case of registered multicast addresses, it is only necessary to prepare the number of registered filters and set the registered multicast address as the destination IP address. The setting is the same as the above setting except for the setting of the destination IP address.

  When an ICMP echo request packet (ICMP data size is 64 bytes or less) is set in the pattern filter 2141, the PE_ON signal becomes active when an ICMP echo request packet (ICMP data size is 64 bytes or less) is received.

  In order to transmit the packet generated by the packet generation unit 2452 described above, when the PE_ON signal output from the PF 1823 becomes active, the selector (SEL) 25 transmits the output from the PE 1824 to the MAC 22. When the PE_ON signal is inactive, data from the internal bus 34 is input to the MAC 22.

  First, when the pattern of the ARP request packet is set in the pattern filter 2141 of the PF 1823, the PE_ON signal can be activated. That is, when the ARP request packet is received, the PE_ON signal becomes active, and the PE 1824 generates an ARP reply packet and outputs it to the transmission source device of the ARP request packet.

  When an ICMP echo request packet (ICMP data size is 64 bytes or less) is received, the PE_ON signal becomes active, and the PE 24 generates an ICMP echo reply packet and outputs it to the device that sent the ICMP echo request packet. To do.

  On the other hand, when the PE_ON signal is not active, after passing through the PF 1823, the signal is stored in the memory 11 via the MEMI / F 21 and processed by the CPU 20.

  Further, when a non-print request packet other than a print request packet, an ARP request packet, and an ICMP echo request packet (ICMP data size is 64 bytes or less) is received, the PE_ON signal is not activated.

  As described above, the response Ethernet packet generated by the packet generation unit 2452 is transmitted to the host device that is the transmission source of the request packet as described above via the selector (SEL) 25, the MAC 22, and the PHY 12.

  In this way, when the received packet requests the return of predetermined information, a response packet is created by incorporating a part of the received packet information without using the printer CPU and memory. Since the response process is performed, it is possible to reduce the power consumption of the CPU and the memory of the printer main body.

  Further, since the response is made when the size of the received packet is equal to or smaller than the predetermined size, the hardware cost of the printer can be reduced, so that the power consumption can be reduced and the cost can be reduced. Furthermore, during the controller mode and energy-saving energy mode, the printer's main CPU and memory are not used, and a response packet is created by incorporating a part of the received packet information. The power consumption of the CPU and memory of the main body can be reduced.

  Further, since the packet identifier can be generated without using the CPU and memory of the printer, the power consumption can be reduced. Furthermore, since the sequence number of the packet can be generated without using the CPU and memory of the printer, power consumption can be reduced. Furthermore, since the ICMP header of the packet can be generated without using the CPU and memory of the printer, the power consumption can be reduced.

  Since this printer performs part of packet processing for the network not by CPU processing but by the network packet processing unit, the power-saving mode of each unit including the CPU other than the network packet processing unit can be maintained. Can be further reduced. Moreover, since the power-saving mode is changed according to the packet, the energy saving effect can be improved.

  Furthermore, since the CPU is built in the ASIC, the power consumption can be further reduced.

  In the above-described embodiment, the printer having the energy saving mode and the controller mode has been described as the power saving mode. However, in the information processing apparatus including the printer, there are various types of power saving modes other than the energy saving mode and the controller mode. Although there are modes, the present invention can be implemented in the same manner as described above for information processing apparatuses that implement these modes.

(Embodiment 3)
FIG. 26 is a block diagram illustrating a functional configuration including a controller board 2601 that controls the printer of the information processing apparatus according to the third embodiment and the printing unit 2.

  As in the first embodiment, the printer controller board 2601 includes an ASIC 2610, a memory 11 including a DDR-SDRAM, a network PHY 12, a PHY clock generator 13, and an ASIC for transmitting and receiving various packets to and from the network. Clock generator 14, recording medium 15, OP16, hard disk device (HDD) 17, board power controller 18, external power controller 19, nonvolatile memory (RAM) 36, first ROM 37 storing programs and data, MAC A second ROM 38 in which an address is stored is mounted.

  As in the first and second embodiments, the ASIC 2610 includes a CPU 20, a MEMI / F 21, a MAC 22, a PF 1823, a PE 1824, and a selector (SEL) 25 that are main control units. Here, in the present embodiment, PF1823 and PE1824 are different from those in the first and second embodiments, and other configurations are the same as those in the first and second embodiments.

  The PF 2623 checks the contents of the packet received by the MAC 22 from the network via the PHY 12, discards the packet not addressed to the own printer (addressed to the own station), and if the packet addressed to the own station is a packet to be processed by the PE 2624. Send to PE2624.

  That is, the pattern filter of PF2623 determines whether the packet received from the address filter is a non-print request packet or a print request packet, as in the first and second embodiments. In this embodiment, the received packet Is an SNMP protocol MIB (Management Information Block) request packet, it is determined that the request is a non-print request.

  In the present embodiment, the packet to be processed by the PE 2624 includes a MIB request packet in addition to the types of packets described in the first and second embodiments. When receiving a MIB request packet from the host side, the PE 2624 of the PF 2623 sends a reply to the host for confirmation of reception.

  Next, an example of TCP packet filtering processing in the PF 2623 will be described. FIG. 27 is an explanatory diagram of an example of a packet that is passed through the filtering process in the PF 2623.

  In the pattern filter (not shown) of the PF 2623, a value obtained by adding the destination MAC address length and the source MAC address length is set as the pattern offset 1 shown in FIG. The pattern filter of PF2623 refers to the 16-bit type at the beginning of the packet. In the case of a TCP packet as the above type, 0x0800 indicating the IP protocol is set in the first 16 bits.

  The comparison value of the IP header is set in the next field of the type of the Ethernet header. The IPv4 version is set to 4 in the IP header, the header length is set to 5, the UDP protocol number is set to the protocol number, and the IP address of the MFP / LP is set to the destination IP address. Other IP headers are set as mask areas.

  In the next field, the comparison value of the UDP header is set. Set the port number of the application to be used as the destination port number of the UDP header. In the case of the MIB response, since the SNMP protocol is used, the SNMP port number 161 is set. The UDP header area is a mask area.

  MIB data necessary for the MIB response is set in the UDP data portion. The MIB data to be set is the following value of SNMPv2.

mib-2.5.2.3.2.2.1.1
mib-2.25.3.5.1.1.1.1
mib-2.25.3.5.1.1.2.1
Since the data length of the request ID of the MIB request is variable, four patterns are set for each request ID. MIB data other than the request ID of the MIB request is set in the pattern filter, and the request ID portion is set in the mask area.

  FIG. 28 is a block diagram showing the internal structure of PE2623. As shown in FIG. 28, the PE 2623 includes a packet analysis unit 2850, an ARP reply packet generation unit 2853, a PING reply packet generation unit 2854, an IP packet generation unit 2852, a selector 2859, and an Ethernet frame header generation unit 2860. It has.

  The ARP reply packet generation unit 2853 generates an ARP reply packet, and specifically has the same function as the packet generation unit 52 of the first embodiment. The PING reply packet generation unit 2854 generates a PING packet, and specifically has the same function as the packet generation unit of the second embodiment.

  The packet analysis unit 2850 receives the MIB request packet data from the PF 2623. 29A to 29D are explanatory diagrams illustrating details of the MIB request packet. Fig. 29-1 shows an MIB request packet when the request ID length is 1, Fig. 29-2 shows an MIB request packet when the request ID length is 2, and Fig. 29-3 shows an MIB request packet when the request ID length is 3. FIG. 29-4 shows an MIB request packet when the request ID length is 4. The request ID part (shaded part in the figure) is a mask area.

  The packet analysis unit 2850 can detect the MIB request packets corresponding to the four types of request ID lengths by setting the four patterns of MIB requests.

  The packet transferred from the PF 2623 is analyzed by the packet analysis unit 2850, and the transmission source port number and request ID of the UDP header are transferred to the identification data generation unit 2855 of the IP packet generation unit 2852. Further, the transmission source hardware address (SHA) of the Ethernet header is set in the DHA of the register unit 2851, and the transmission source IP address (SIP) of the IP header is set in the DIP of the register unit 2851.

  Here, the IP packet generation unit 2852 generates an IP packet of the MIB response, and includes an identification data generation unit 2855, an MIB response packet generation unit 2856, a UDP header generation unit 2857, and an IP header generation unit 2858. I have.

  The identification data generation unit 2855 receives the transmission source port number and request ID of the UDP header, and transmits the transmission source port number, request ID type, length (len_reqed), and REQID of the UDP header to the MIB response packet generation unit 2856. Forward.

  The MIB response packet generation unit 2856 generates an MIB response packet serving as a UDP data portion. FIG. 30 is an explanatory diagram showing detailed processing of the MIB response packet generation unit 2856.

  The MIB response packet generation unit 2856 sets the type, length, SNMP version, community name, and PDU TYPE in the SNMP message 1. The MIB response packet generation unit 2856 sets 4d as the initial value of the length because the request ID of the MIB response packet has a variable length.

  The MIB response packet generator 2856 sets A2 indicating that it is a GET reply because it is an MIB response in the type of PDU TYPE. The MIB response packet generation unit 2856 sets 0a as the initial value of the length of the PDU TYPE.

  Also, the MIB response packet generation unit 2856 sets the type, length (len_reqed), and REQID of the request ID received from the identification data generation unit 2855.

  The MIB response packet generation unit 2856 sets the same value as the MIB request filter setting for the error status and error index of the PDU.

  Also, the MIB response packet generation unit 2856 sets the following PDU object data by the CPU.

Data 1: mib-2.25.3.2.2.1.5.1
Data 2: mib-2.25.3.5.1.1.1.1
Data 3: mib-2.25.3.5.1.1.2.1
When the MIB request packet is received during the energy saving mode, the CPU shifts to the controller mode only at the first MIB response and the CPU sets object data. The CPU also sets the type and length of the object data 1, 2, and 3, and the type and length (len_objid) of the entire object data.

  Next, the MIB response packet generation unit 2856 calculates the data length of the MIB data. When the CPU sets the length of the entire object data (len_objid), the total of the length of the entire object data (len_objid) and the length of the request ID (len_requested) is calculated as len3 in ADD3. Next, the MIB response packet generation unit 2856 calculates, in ADD2, the sum of the initial values (0a) of the lengths of len3 and PDU TYPE as len2, and resets len2 to the length of PDU TYPE. Further, the MIB response packet generation unit 2856 calculates, in ADD3, the sum of the initial length (4d) of the SNMP message 1 and len2 as len1, and resets len1 to the length of the SNMP message 1.

  As described above, the MIB response packet generator 2856 generates the MIB response packet. Here, the MIB response packet is SNMP data and becomes the UDP data portion as described above.

  The UDP header generation unit 2857 adds a UDP header to the MIB response packet as the UDP data unit. The IP header generation unit 2858 adds an IP header to the MIB response packet to which the UDP header is added, completes the MIB response IP packet, and sends the IP packet to the selector 2859.

  FIG. 31 is an explanatory diagram showing an IP packet of the MIB response. As shown in FIG. 31, the UDP header generation unit 2857 generates a source port number (SPN), a destination port number (DPN), a segment length (len), and a checksum (SUM), and a UDP header of the MIB response packet. Set as. The UDP header generation unit 2857 sets 161 indicating SNMP in the transmission source port number (SPN). The UDP header generation unit 2857 sets the destination port number acquired from the identification data generation unit 2855 as the destination port number (DPN). The UDP header generation unit 2857 sets the MIB response packet length (len1 + 1), which is SNMP data, as the segment length (len). The UDP header generation unit 2857 sets a value indicating 16's complement of the MIB response packet, which is the header and UDP data, in the checksum (SUM).

  The IP header generation unit 2858 generates the IP header of the IP packet, and adds the IP header to the MIB response packet in which the UDP header is set as described above.

  The IP header generation unit 2858 previously sets the MFP / LP's own station IP address in the SIP of the register unit 2851 and the MFP / LP's own station hardware address in the SHA of the register unit 2851. In addition, the IP header generation unit 2858 presets 0x800 indicating IP in the TYPE of the register unit 2851.

  Then, the IP header generation unit 2858 sets 4 for the IP head version and 5 for the header length. Further, the IP header generation unit 2858 sets 0 to the service type (TOS) of the IP header. The IP header generation unit 2858 sets the sum of the IP header length, the UDP header length, and the UDP data length in the packet length (len) of the IP head. The IP header generation unit 2858 sets the source IP address (SIP) from the SIP in the register unit and the destination IP address (DIP) from the DIP in the register unit.

  The IP header generation unit 2858 sets the identifier generated by the identification data generation unit 2855 as the identifier (ID) of the IP header. The identifier (ID) is newly generated by the identification data generation unit 2855 every time an IP packet is transmitted. Alternatively, the IP ID from the packet analysis unit 2850 may be transferred to the identification data generation unit 2855 and used as an identifier (ID) by the IP header generation unit 2858. Furthermore, the IP header generation unit 2858 can uniquely generate an identifier (ID). For example, the initial value when the power is turned on may be 0, and the new identifier (ID) = old identifier (ID) +1 may be generated.

  The IP header generation unit 2858 sets the flag as non-dividable and no subsequent fragment, and sets the fragment offset to 0. The IP header generation unit 2858 sets the maximum value 255 to the survival time. The IP header generation unit 2858 sets 17 as a value indicating UDP in the protocol. The IP header generation unit 2858 calculates the checksum of the IP header and data in the header checksum (SUM). The header option is not generated.

  The selector 2859 selects any one of the ARP reply packet sent from the ARP reply packet generator 2858, the PING reply packet sent from the PING reply packet generator 2854, and the IP packet sent from the IP packet generator 2852. This is sent to the ether frame header generation unit 2860. When the MIB request is received and the MIB response is made, the selector 2859 selects an IP packet transmitted from the IP packet generation unit 2852.

  The ether frame header generation unit 2860 generates an ether frame header by acquiring the destination MAC address from the DHA set in the register unit 2851, the transmission source MAC address from the SHA, and the type from the TYPE and adding them to the IP packet.

  Since the FCS of the Ethernet packet is automatically generated by the MAC 22, it is not necessary to generate it by the Ethernet frame header generation unit 2860.

  When the MIB request is received during the energy saving mode, the controller mode is shifted only to the first MIB response. Therefore, the first MIB response is performed in the controller mode, and the output of the PE 2624 is selected from the PM 32 to the selector (SEL) 25. . When the first MIB response is completed, the controller mode is shifted to the energy saving mode.

  If there is the same MIB request as the previous time during the energy saving mode, the MIB response is made without changing from the energy saving mode to the controller mode. Since the MIB request is the same as the previous one, it is not necessary for the CPU to set again the following object data of the PDU, and the MIB response packet generated last time is used.

Data 1: mib-2.25.3.2.2.1.5.1
Data 2: mib-2.25.3.5.1.1.1.1
Data 3: mib-2.25.3.5.1.1.2.1
Data generated by the UDP header generation unit 2857, the IP header generation unit 2858, and the Ethernet frame header generation unit 2860 can be generated in the same manner as the previous time.

  The generated Ethernet frame packet is transferred to the MA 22C via the selector (SEL) 25 and output from the PHY 12.

  As described above, since the MIB response is performed in the energy saving mode in response to the second and subsequent MIB requests, the power consumption at the time of the MIB request can be reduced.

  In the energy saving mode, the output of PE 2624 is selected from PM 32 to selector (SEL) 25. In the PM 32, when shifting from the energy saving mode to the normal mode or the controller mode, the selector (SEL) 25 selects the data from the internal bus 34 and inputs it to the MAC 22 instead of the output of the PE 2624.

  As described above, in the printer according to the third embodiment, the UDP header of the packet, that is, the SNMP data can be generated without using the CPU and the memory of the printer, so that power consumption can be reduced.

  In the first to third embodiments, the printer having the energy saving mode and the controller mode is described as the power saving mode. However, in the information processing apparatus including the printer, the power saving mode is not limited to the energy saving mode and the controller mode. However, the present invention can be implemented in the same manner as described above for an information processing apparatus that implements these modes.

  It should be noted that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. In addition, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

FIG. 2 is a block diagram illustrating a functional configuration of the printer according to the first embodiment. FIG. 6 is a transition diagram of transition to each mode related to power supply in the printer of the first embodiment. It is explanatory drawing of the structure of the frame format of an Ethernet packet. It is explanatory drawing which shows an example of the data content of each field in an Ethernet frame. It is a figure which shows the correspondence of both frames in the case of comprising an ARP packet from an Ethernet packet. It is explanatory drawing which shows the format of an ARP packet. It is explanatory drawing which shows an example of the data content of each field in an ARP packet. It is explanatory drawing which shows the format of an IP packet. It is explanatory drawing which shows an example of the data content of each field of the IP header in an IP packet. It is a figure which shows the correspondence of each flame | frame in the case of comprising an IP packet and a TCP packet from an Ethernet packet. It is explanatory drawing which shows the format of a TCP packet. It is explanatory drawing which shows the format of a UDP packet. 3 is a block diagram illustrating an example of an internal configuration of a PF according to Embodiment 1. FIG. FIG. 3 is a block diagram for explaining an internal process of a PE according to the first embodiment. 6 is an explanatory diagram of an example of a TCP packet that is passed through a PF filtering process according to Embodiment 1. FIG. 6 is an explanatory diagram of an example of a UDP packet that is passed through the filtering process of the PF according to Embodiment 1. FIG. 6 is an explanatory diagram of an example of an ARP packet that is passed through the PF filtering process according to Embodiment 1. FIG. FIG. 4 is a block diagram illustrating a functional configuration of a printer according to a second embodiment. It is a figure which shows the format of the IP packet and ICMP packet in an Ethernet frame. It is explanatory drawing which shows the format of an ICMP echo request packet and an ICMP echo reply packet. 6 is a block diagram illustrating an example of an internal configuration of a PF according to Embodiment 2. FIG. 10 is an explanatory diagram of an example of a TCP packet that is passed through a PF filtering process according to Embodiment 2. FIG. 6 is an explanatory diagram of an example of a UDP packet that is passed through a PF filtering process according to Embodiment 2. FIG. It is a block diagram with which it uses for description of the internal process in PE in the case of filtering an ICMP packet. FIG. 10 is an explanatory diagram of an example of an ICMP packet that is passed through a PF filtering process according to the second embodiment. FIG. 6 is a block diagram illustrating a functional configuration of a printer according to a third embodiment. FIG. 10 is an explanatory diagram of an example of a packet that is passed through a filtering process in the PF according to the third embodiment. It is a block diagram which shows the internal structure of PE of Embodiment 3. It is explanatory drawing which shows the detail of a MIB request packet in case request ID length is 1. FIG. It is explanatory drawing which shows the detail of a MIB request packet in case request ID length is 2. FIG. It is explanatory drawing which shows the detail of a MIB request packet in case request ID length is 3. FIG. It is explanatory drawing which shows the detail of a MIB request packet in case request ID length is 4. FIG. FIG. 10 is an explanatory diagram showing detailed processing of an MIB response packet generation unit 2856. It is explanatory drawing which shows the IP packet of a MIB response.

Explanation of symbols

1: Controller board 2: Printing unit 3: Bus 10: ASIC
11: Memory 12: PHY
13: PHY clock generation unit 14: ASIC clock generation unit 15: Recording medium 16: OP
17: HDD
18: Board power control unit 19: External power control unit 20: CPU
21: MEMI / F
22: MAC
23: PF
24: PE
25: SEL
26: CG
27: I / F
28: Recording medium I / F
29: OPEI / F
30: HDD I / F
31: I / OI / F
32: PM
33: Timer 34: Internal bus 35: Power-off area 36: RAM
37: First ROM
38: Second ROM
40: Address filter 41: Pattern filter 42: Buffer 50: Packet analysis unit 51: Register unit 52: Packet generation unit M1: Normal operation mode M2: Energy saving mode M3: Controller mode

Claims (13)

An information processing apparatus,
A control unit for operating the information processing apparatus in a plurality of types of power saving modes;
A packet that determines whether or not a packet received from the network is a return request packet that does not require processing addressed to the information processing apparatus while operating in any one of the plurality of types of power saving modes. A determination unit;
When the received packet is a return request packet that does not require processing addressed to the information processing apparatus, a response packet is generated for the received packet while maintaining the power saving mode when the packet is received A packet generator,
The packet determination unit further determines whether the received packet requests a return of predetermined information based on the content of the received packet,
The information processing apparatus, wherein the packet generation unit generates the response packet including the predetermined information when the received packet requests a return of predetermined information.   The information processing apparatus according to claim 1, further comprising: a packet return unit that returns the generated response packet via the network.   The information processing apparatus according to claim 1, wherein the predetermined information is identification information of the information processing apparatus.   The information processing apparatus according to claim 3, wherein the identification information is a sequence number.   The information processing apparatus according to claim 1, wherein the predetermined information is ICMP protocol data.   The information processing apparatus according to claim 1, wherein the predetermined information is UDP protocol data.   The information processing apparatus according to claim 6, wherein the UDP protocol data is SNMP protocol data.   The information processing apparatus according to claim 7, wherein the SNMP protocol data is MIB information. The plurality of types of power saving modes include a controller mode in which power is supplied to the control unit to operate the information processing device, and an energy saving mode in which power is supplied to a part of the control unit to operate the information processing device. Mode and
When returning the response packet including the predetermined information as the first SNMP protocol data, the control unit operates the information processing apparatus in the controller mode, and transmits the SNMP protocol data for the second and subsequent times as the predetermined packet. 8. The information processing apparatus according to claim 7, wherein when the response packet including information is returned, the information processing apparatus is operated in an energy saving mode.   The information processing apparatus according to claim 1, wherein the packet determination unit, the packet generation unit, and the packet return unit are mounted on a single ASIC.   The information processing apparatus according to claim 1, wherein a size of the received packet is equal to or smaller than a predetermined size. An information processing method executed by an information processing apparatus,
The information processing apparatus includes a control unit that operates the information processing apparatus in a plurality of types of power saving modes.
A packet that determines whether or not a packet received from the network is a return request packet that does not require processing addressed to the information processing apparatus while operating in any one of the plurality of types of power saving modes. A decision step;
When the received packet is a return request packet that does not require processing addressed to the information processing apparatus, a response packet is generated for the received packet while maintaining the power saving mode when the packet is received A packet generation step,
The packet determining step further determines whether or not the received packet requests a return of predetermined information based on the content of the received packet;
The packet generation step generates the response packet including the predetermined information when the received packet requests the return of predetermined information. Computer
A control unit for operating the computer in a plurality of types of power saving modes;
A packet determination unit that determines whether a packet received from the network is a return request packet that does not require processing addressed to the computer while operating in any one of the plurality of power saving modes. When,
Packet generation for generating a response packet for the received packet in a state where the power saving mode at the time of receiving the packet is maintained when the received packet is a return request packet not requiring processing for the computer Function as a part,
The packet determination unit further determines whether the received packet requests a return of predetermined information based on the content of the received packet,
The program, wherein the packet generation unit generates the response packet including the predetermined information when the received packet requests return of predetermined information.

Images